Re: WS-Eventing interop scenario v0.0.3

I'd like to suggest that we test the extensibility of ws-eventing but 
adding an optional element to the Subscribe that allows a Subscriber to 
indicate when events are to be sent.  For example, if I'm reading the doc 
correctly, right now events are supposed to be sent at a fixed interval 
for all animals.  This is good for some folks, but others may only want to 
get notifications when something non-obvious happens - ie. something other 
than "the animal moved".   Perhaps only be notified when the animal goes 
into a location it shouldn't or something like that.  This will test the 
notion of someone adding extension to one of our operations and it may, or 
may not, include a mU=1 header.  We can use this to test the various 
behaviours that can be associated with this - including an event source 
not supporting it at all.

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.



Gilbert Pilz <gilbert.pilz@oracle.com> 
Sent by: public-ws-resource-access-request@w3.org
12/06/2010 07:42 PM

To
"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
cc

Subject
WS-Eventing interop scenario v0.0.3






I've fleshed out some more of the tests with sequence diagrams and 
conformance statements. Except for the details on what the WSDLs and event 
descriptions look like, this is pretty much finished.

I know we're supposed to roll all of the scenario descriptions up into one 
big document, bu I'm a bit worried that the resulting document will be 
unwieldy.

~ gp[attachment "ws-eventing-scenario-v0.0.3.pdf" deleted by Doug 
Davis/Raleigh/IBM]