- From: Doug Davis <dug@us.ibm.com>
- Date: Mon, 27 Apr 2009 09:18:23 -0400
- To: public-ws-resource-access@w3.org
- Message-ID: <OFA54003EA.B24F9110-ON852575A5.004765F8-852575A5.00491C71@us.ibm.com>
Per my AI [1] here are the differences between the Compliance sections of the 5 specs - just the differences are listed below: - - - - - - - - - - - - - - - - - - - Transfer: Specifically, 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. In any given request-response message exchange, the responses generated by the service server MUST use the same WS-Addressing namespace binding that was used in the request. MEX: Support for the GetMetadata operation by a Web service is optional. If metadata about a Web service endpoint is referenced by a Metadata Reference, which is a [WS-Addressing] endpoint reference, then the Metadata Reference MUST refer to a [WS-Transfer] resource. The referred resource MAY also support other resource management and access specifications (e.g. HTTP, WS-ResourceFramework). Eventings: SOAP is not a requirement for using the constructs defined in this specification. - - - - - - - - - - - - - - - - - - - Seems to me that the 2nd paragraph of Transfer (the "In any given..." one), and the text for Eventing should be removed. We should also find a more consistent (and better) way to say which operations (for all specs) are required vs optional. [1] http://www.w3.org/2002/ws/ra/tracker/actions/58 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.
Received on Monday, 27 April 2009 13:19:08 UTC