- From: Doug Davis <dug@us.ibm.com>
- Date: Mon, 27 Sep 2010 10:03:26 -0400
- To: Gilbert Pilz <gilbert.pilz@oracle.com>
- Cc: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
- Message-ID: <OF875C99BB.AEEADE17-ON852577AB.004D1E6B-852577AB.004D396B@us.ibm.com>
Nice catch on the Expires issue. Seems to me that it would be good for the spec to mandate that whatever choice the event source makes that it be consistent across all operations. Sounds like a new issues to me. 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 09/21/2010 06:45 PM To "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org> cc Subject WS-Eventing optionality analysis Attached is an analysis of the optionality of the various operations/messages and features in WS-Eventing. I'm not sure if this format is the best for displaying this information. I tried to color code things: black is required, blue is required for one party but not another, red is optional for both parties. Sub-elements/sub-features are scoped to the optionality of there containing element/feature. For example, event sources are required to support expiration values using xs:duration iff they support wse:Expires, but subscribers may elect to use xs:dateTime values - so xs:duration is blue (required for event source, optional for subscriber) scoped by a red element/feature (wse:Expires). If anyone has a better suggestion on how to display this info, please speak up. One issue that writing this analysis brought up is the granularity of options. In the case of WS-Eventing this only impacts subscription expiration, but it might impact the other spec differently. For WS-Eventing the question is, "If you are an event source that supports wse:Subscribe/wse:Expires are your subscription manager therefor required to support wse:Renew/wse:Expires?" Put another way, "Can I have a subscription manager that supports wse:Renew/wse:Expires even though my event source doesn't support wse:Subscribe/wse:Expires?" ~ gp[attachment "ws-eventing-optionality-analysis.odt" deleted by Doug Davis/Raleigh/IBM]
Received on Monday, 27 September 2010 14:04:54 UTC