Re: WS-Eventing interop scenario v0.0.3

Gil - I like the shape of this so far.  And I think adding in the other 
specs won't be too bad.  Here's how I see that it can play out....
- define the shape of the animal's tag data/xsd
- move the eventing specific stuff into a section titled something like 
"Receiving Notifications" - just so the Eventing stuff is separate from 
the stuff below
- define the shape of the event data - this seems like it should be 
related to the tag xsd - could even be the same thing to make things 
easier
- add a section that talks about how tags/animals can be added. modified 
or deleted - pulls in Transfer/Frag - might also cause a event to be sent
- add a section that talks about how a client can enumerate over the list 
of tags/animals - pulls in Enum
- add a section that talks about a client can use MEX to determine which 
of the features are supported (events, enum, transfer,....)

Since you've already stated that there's a predefined set of tags known to 
the system, it seems to me that any of the specs can be tested in 
isolation of the others.
If people are ok with this I can take a stab at doing this.

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]