This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
WS-Eventing defines a GetStatus() operation to return the current Expires time of the subscription. While this information is useful, its a bit puzzling why this is the only bit of information allowed to be queried. For example, why not allow people to ask for the current filter, delivery or format information? Likewise, why is the Expires time the only property allowed to be updated? If there are properties of a delivery mode that need to be updated, why should someone be forced to unsubscribe and resubscribe just to make this change? Proposal: 1 - Remove GetStatus and Renew operations. 2 - Define a minimum XML represenation of a Subscription Manager resource, which, btw, would look a lot like the Body of the Subscribe. 3 - Mention in WS-Eventing how WS-Transfer can be used to query/update the Subscription Manager's XML representation 4 - Like the GetStatus/Renew operation - the use of Transfer (or even exposing a Subscription Manager as a 'resource') will be totally optional. This will also better align WS-Eventing with the rest/web architecture by clearly defining what is at the Subscription Manager EPR. Side note: Its not clear to me if this same issue should be opened against Enumeration. While it feels like it should, Enum is slightly different in that an Enumeration Context is passed around - meaning that no state needs to be maintained on the server (if it doesn't want to).
proposal point 1 removed by consensus
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009May/0159.html
discussed 2009-05-19
Minor tweak to the proposal (new text in ***) 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 *** - thus allowing access to the other properties of the Subscription*** . 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: ...
discussed on 2009-07-28, propose decision in a week (maybe)
proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0079.html