W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > November 2009

RE: 8201 - Clarify required and optional operations

From: Doug Davis <dug@us.ibm.com>
Date: Mon, 30 Nov 2009 09:45:38 -0500
To: Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>
Cc: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Message-ID: <OF0D1D76B5.A42950CE-ON8525767E.0050159F-8525767E.005116AF@us.ibm.com>
In thinking more about this one... I'm not sure it makes a lot of sense to 
say which operations are required vs optional in both the Compliance 
section and section where each op is defined.  The optionality of each op 
is really not any more special than any other requirement in the spec. And 
since the Compliance section already says:
        An implementation is not compliant with this specification if it 
fails to satisfy one or more of the MUST or REQUIRED level requirements 
defined herein.
I don't see the value in calling out one MUST over another.  To that end, 
I propose that we tweak the start of each section that defines an op/msg. 
Using Transfer Get as an example, it current start with:
3.1 Get
This specification defines one Web service operation (Get) for fetching a 
one-time snapshot of the representation of a resource.

We could change it to be:
3.1 Get
This specification defines one Web service operation (Get) for fetching a 
one-time snapshot of the representation of a resource. This operation MUST 
be supported by compliant implementations.

And Put, which would be optional, would look like:
3.2 Put
This specification defines one Web service operation (Put) for updating a 
resource by providing a replacement representation. This operation MAY be 
supported by compliant implementations.

And the table would be:
WS-Eventing:
Subscribe       Required
Renew           Required
GetStatus       Required
Unsubscribe     Required
SubscriptionEnd Optional

WS-Enumeration:
Enumerate       Required
Pull            Required
Renew           Required
GetStatus       Required
Release         Required
EnumerationEnd  Optional

WS-MEX:
GetMetadata     Optional

WS-Transfer:
Get             Required
Put             Optional
Delete          Optional
Create          Optional

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/20/2009 10:28 AM

To
Doug Davis/Raleigh/IBM@IBMUS
cc
"public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Subject
RE: 8201 - Clarify required and optional operations






Here is a concrete version:
 
An event source MUST support Subscribe operation. An event source MAY send 
SubscriptionEnd message to an endpoint that supports SubscriptionEnd 
operation, if reference to such an endpoint is supplied when the 
subscription was created. An Subscription manager endpoint MUST support 
Renew, GetStatus, and Unsubscribe operations. An endpoint that supports 
SubscriptionEnd portType, if a reference to such an endpoint is supplied 
when the subscription was created, MUST support SubscriptionEnd operation. 
An event subscriber MAY use Subscribe, Renew, GetStatus, and Unsubscribe 
operations.
 
Thanks.
 
From: Doug Davis [mailto:dug@us.ibm.com] 
Sent: Thursday, November 19, 2009 3:52 PM
To: Ram Jeyaraman
Cc: public-ws-resource-access@w3.org
Subject: 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. 
 
Received on Monday, 30 November 2009 14:46:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:15 GMT