scenario flow

I wanted to make sure my thinking about the overall flow of the scenario 
doc aligns with other people's thinking before I update the doc.
Let's say that a client is provided a URL to the "Animal tagging service" 
(ATS).  Does the following make sense:

- ATS.getWSDL() to get the WSDL for the ATS
- ATS.getMetadata( ... ), putMetadata(), deleteMetadata() to retrieve, 
update, delete metadata about the ATS
- ATS.Subscribe( ... )  to receive notifications about the animals - 
subEPR is returned
        - each event MAY include an "Animal EPR" to an Animal (aEPR)
- subEPR.unsubscribe(), e.renew(),...  processes the Eventing ops for this 
one subscription
- subEPR.getWSDL(), xxxMetadata() to get/modify the metadata about a 
particular subscription
- ATS.Enumerate( ... ) to cursor over the current set of animals
        - each item MAY include an "Animal EPR" to an Animal (aEPR)
- ATS.release(), en.renew() ... to process the Enum ops 
- aEPR.Get(), Put(), Delete() will retrieve, modify, delete the XML for an 
Animal
- ATS.Create() will create a new animal and return an aEPR to it
- aEPR.getWSDL(), xxxMetadata() to get/modify the metadata about a 
particular Animal

Does this sound right?  Mainly I wanted to make sure that one URL was all 
that was needed to kick this off - from there subsequent EPRs should be 
derived from the specified operations.

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.