- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 27 Oct 2009 19:44:46 -0400
- To: public-ws-resource-access@w3.org
- Message-ID: <OF4AA77001.21EF39AB-ON8525765C.0081752D-8525765C.008272FF@us.ibm.com>
While adding the text for issues 7586, 7588 and 7828 I noticed that we saved a lot of space in wsenum and wseventing by not repeating the definition of the children elements when we define the Renew operation - we just point people back to Susbcribe/Enumerate. For example, ws-enum Renew says: Components of the outline listed above are additionally constrained as for a request to create an enumeration (see 3.1 Enumerate) with the following addition(s): However, for some reason on the Response side of the Renew operation (for both specs) we do mention the GrantedExpires element: Components of the outline listed above are constrained as for a response to an Enumerate request (see 3.1 Enumerate) with the following addition: [Body]/wsen:RenewResponse/wsen:GrantedExpires If the requested expiration is a duration, then the implied start of that duration is the time when the data source starts processing the Renew request. Notice that 1) we point people back to Enumerate, and 2) the text for GrantedExpires doesn't really add anything beyond what Enumerate already says for this element. If people are ok with it, I'd like to just remove this extra/semi-duplicate definition of GrantedExpires from Renew for both Eventing and Enum - in both cases people will be directed back to the Enumerate/Subscribe operation so nothing should be lost and we avoid possible inconsistencies in the specs. Its worth noting that we do this for GetStatus in both specs already. I'll wait a couple of days and if no one objects I'll make the update as an editorial tweak. 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.
Received on Tuesday, 27 October 2009 23:45:22 UTC