- From: Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>
- Date: Fri, 6 Nov 2009 15:11:27 +0000
- To: Doug Davis <dug@us.ibm.com>, "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
- Message-ID: <503546C5699C1144BDEA0D0DFFE7F8811815E5D3@TK5EX14MBXC112.redmond.corp.microsoft.>
Hi Doug, Ø 1 - in the "Compliance" section add a paragraph saying which ops are optional vs required This (option 1) would make required/optional operations very clear. In addition, it would be useful if the individual operation descriptions state whether the operation is required/optional (option 2). Thanks. From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Doug Davis Sent: Friday, November 06, 2009 6:43 AM To: public-ws-resource-access@w3.org Subject: 8201: Clarify required and optional operations Ram, I think issue 8201 is a good idea. Do you have a proposal for how you think this should look in the specs? I see 2 options: 1 - in the "Compliance" section add a paragraph saying which ops are optional vs required 2 - at the top of each operation's section add a sentence stating which that operation is required or optional. WS-Transfer has this in the compliance section: A compliant SOAP Node that implements a resource MUST provide the Get operation as defined in this specification, and MAY provide the Put and Delete operations. While MEX say this in the GetMetadata section: A service endpoint MAY support the GetMetadata request. Either works but we should be consistent across all the specs. thanks -Doug ______________________________________________________ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | dug@us.ibm.com<mailto:dug@us.ibm.com> The more I'm around some people, the more I like my dog.
Received on Friday, 6 November 2009 15:12:03 UTC