- From: Gilbert Pilz <gilbert.pilz@oracle.com>
- Date: Mon, 21 Dec 2009 11:18:07 -0800
- To: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Received on Monday, 21 December 2009 19:19:59 UTC
A large part of this issue is about what it means for one spec to normatively reference another spec. That's a pretty big subject but, in the context of this issue I construe it in the following way: 1.) Except for WS-Frag, the specs produced by WS-RA all include WSDL definitions. These WSDL definitions must comply with the requirements in Section 4, "Service Description", of BP 1.1 [1] which, as far as I am aware, they do. 2.) In addition to this, several of our specs discuss or hint at the possibility of implementations that produce/provide WSDLs that are refinements or extensions to the WSDLs defined in our specs. For example, a service that supported WS-Transfer might, if asked correctly, provide a consumer with a WSDL that extends the W3C version of the WS-Transfer WSDL to include a SOAP binding of the "Resource" portType along with a service/port for that service's endpoint. This WSDL must also comply with the requirements in Section 4. 3.) End-user WSDLs are free to comply (or not) with the requirements in Section 4 of BP 1.1 as they see fit. [1] http://www.ws-i.org/Profiles/BasicProfile-1.1.html - gp
Received on Monday, 21 December 2009 19:19:59 UTC