- From: Doug Davis <dug@us.ibm.com>
- Date: Mon, 18 May 2009 20:19:56 -0400
- To: public-ws-resource-access@w3.org
- Message-ID: <OF1A3BFD43.5F4AB20A-ON852575BB.0000390C-852575BB.0001D5E5@us.ibm.com>
Based on last week's call here is some proposed text for issue 6724:
- - - - - - - - - - - - - - - - - - - - - - -
Appendix B: Subscription Manager Resource Model
A Subscription Manager can choose to allow for retrieval and update of the
Expires time of a subscription through the use of the GetStatus and Renew
operations. If it wishes it MAY also choose to expose the Subscription
Manager itself as a resource that can be accessed using resource access
specifications such as WS-Transfer. This specification places no
requirements on implementations with respect to which operations (if any)
that it supports. Nor does this specification require that
implementations support updates to all properties of the resource.
However, if the Subscription Manager chooses to expose the Subscription
Manager as a resource then it MUST support the wse:Subscription schema
defined by this specification. The outline for a Subscription Manager
resource is:
<wse:Subscription>
<wse:EndTo> endpoint-reference </wse:EndTo> ?
<wse:Delivery Mode="xs:anyURI"? ...> xs:any* </wse:Delivery>
<wse:Format Name="xs:anyURI"? > xs:any* </wse:Format>
<wse:Expires> (xs:dateTime | xs:duration) </wse:Expires> ?
<wse:Filter Dialect="xs:anyURI"? ...> xs:any* </wse:Filter> ?
xs:any*
</wse:Subscription>
- - - - - - - - - - - - - - - - - - - - - - -
And add this xsd to the eventing.xsd.
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, 19 May 2009 00:20:38 UTC