Re: 8201 - Clarify required and optional operations

2 minor tweaks:
1 - s/optional/OPTIONAL/
2 - make GetStatus required.

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.



Ram Jeyaraman <Ram.Jeyaraman@microsoft.com> 
Sent by: public-ws-resource-access-request@w3.org
11/17/2009 03:25 PM

To
"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
cc

Subject
8201 - Clarify required and optional operations






http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201
 
I had an action item from the previous meeting to write up a more concrete 
proposal for this issue. Here is a suggested text for WS-Eventing. The 
same pattern can be applied for other specifications.
 
[1] Proposal for WS-Eventing
 
Add to Section 3.5 Compliance:
 
Subscribe, Renew, and Unsubscribe  operations defined in this 
specification MUST be supported by compliant implementations. GetStatus 
and SubscriptionEnd operations defined in this specification are optional 
and MAY be supported by compliant implementations.