RE: [wsdm] Questions on using WSDM event format

["Sedukhin, Igor S" <Igor.Sedukhin@ca.com>]

One more we got: 2.6 messageType includes wef:Event and myResourceEvent and it is applicable to case b

 

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749 

 

---

From: Sedukhin, Igor S
Sent: Monday, November 15, 2004 2:05 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] Questions on using WSDM event format

 

1. How do we represent custom/specialized/resource-specific events

 

        a. a specific event messaage element is declared as an extension of the WSDM event type e.g.

 

                <my:ResourceEvent>

                    <wef:eventId>...

                    <wef:priority>...

                    <my:otherInformation>...

                    <my:moreInformation>...

                </my:ResourceEvent>

 

        b. a specific event message element is declared and contained in WSDM event element e.g.

 

                <wef:BaseEvent>

                    <wef:eventId>...

                    <wef:priority>...

                    <my:ResourceEvent>

                        <my:otherInformation>...

                        <my:moreInformation>...

                    </my:ResourceEvent>

                </wef:BaseEvent>

 

2. How do we represent topics for these events

 

    1. case b and wstop:messageTypes points to wef:BaseEvent element and explanation in the text of the specification says that my:ResourceEvent must be present in the open content

            --  this is apparently not very friendly as a baked-in undrstanding of what events are produced by the topic is necessary. No machine-processible description available.

 

    2. case b and wstop:messaageTypes points to my:ResourceEvent and text explains that it must be wrapped in the wef:BaseEvent element

            -- machine-processible, but implementation semantics is baked-in

 

    3. case a and wstp:messageTypes points to my:ResourceEvent. no explanation is necessary in the text

            - machine-processible

 

    4. case b and wstop:messageTypes points to wef:BaseEvent element and wstop:MessaagePattern declares that my:ResourceEvent element must be present in the open content

            - machine-processible

            - requires understanding of the dialectable query expression

 

    5. case b and wstop:messageTypes indicates both wef:BaseEvent and my:ResourceEvent

            - implementation approach is not clear.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749