RE: 8201 - Clarify required and optional operations

Is this the exact text you think should go into the spec, or are you 
assuming we'll pretty it up a bit (like add an intro sentence, etc...) ? I 
agree with the general direction though.

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/19/2009 05:18 PM

To
Doug Davis/Raleigh/IBM@IBMUS, "public-ws-resource-access@w3.org" 
<public-ws-resource-access@w3.org>
cc

Subject
RE: 8201 - Clarify required and optional operations






Thinking a bit more about this, how about:
 
·       Event source endpoint
o   MUST support Subscribe operation.
o   MAY send SubscriptionEnd message to an endpoint that supports 
SubscriptionEnd operation, if reference to such an endpoint is supplied 
when the subscription was created.
·       Subscription manager endpoint
o   MUST support Renew, GetStatus, and Unsubscribe operations.
·       Endpoint that supports SubscriptionEnd portType, if a reference to 
such an endpoint is supplied when the subscription was created
o   MUST support SubscriptionEnd operation.
·       An event subscriber MAY use Subscribe, Renew, GetStatus, and 
Unsubscribe operations.
 
Thanks.
 
From: public-ws-resource-access-request@w3.org 
[mailto:public-ws-resource-access-request@w3.org] On Behalf Of Doug Davis
Sent: Tuesday, November 17, 2009 4:03 PM
To: public-ws-resource-access@w3.org
Subject: RE: 8201 - Clarify required and optional operations
 

I hope you mean: 
Subscribe, Renew, Unsubscribe  and GetStatus operations defined in this 
specification MUST be supported by compliant implementations. the 
SubscriptionEnd operation defined in this specification MAY be supported 
by compliant implementations. 

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> 
11/17/2009 06:37 PM 


To
Doug Davis/Raleigh/IBM@IBMUS, "public-ws-resource-access@w3.org" <
public-ws-resource-access@w3.org> 
cc

Subject
RE: 8201 - Clarify required and optional operations
 








I agree. 
  
Further, in order to avoid two normative keywords in a single sentence, I 
propose [2]. 
  
[2] Revised 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 MAY be 
supported by compliant implementations. 
  
From: public-ws-resource-access-request@w3.org 
[mailto:public-ws-resource-access-request@w3.org] On Behalf Of Doug Davis
Sent: Tuesday, November 17, 2009 12:30 PM
To: public-ws-resource-access@w3.org
Subject: 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.