RE: [ws-dd-comment] SOAP 1.2 HTTP transport binding URI conflict

Dear Stephan,

Thank you for submitting your comment on Public Review Draft 01 of the DPWS specification regarding the SOAP 1.2 HTTP transport binding. Your comment was registered in the WS-DD issue database as issue number PR002, and discussed on a recent WS-DD TC teleconference.

The Technical Committee reviewed the relevant documents. We found that the WSDL 1.1 SOAP 1.2 binding specification provides specific guidance on how to bind WSDL 1.1 to SOAP 1.2. Basic Profile 1.1 [1] and 2.0 [2] both require use of the WSDL 1.1 SOAP 1.2 binding URI; many implementations that support WSDL 1.1 adhere to Basic Profile guidelines about use of this URI for the WSDL 1.1 SOAP 1.2 binding. The provisions in DPWS are consistent with these guidelines. Based on these considerations, the TC has decided to not pursue the issue further.

Thanks again for reviewing the documents.

Best regards,

Toby Nixon

Co-chair, OASIS WS-DD TC

[1] Basic Profile 1.1: http://www.ws-i.org/Profiles/BasicProfile-1.1.html

[2] Basic Profile 2.0: http://www.ws-i.org/Profiles/BasicProfile-2_0(WGD).html

-----Original Message-----

From: Stephan Poehlsen [mailto:poehlsen@itm.uni-luebeck.de]

Sent: Tuesday, February 10, 2009 5:22 AM

To: ws-dd-comment@lists.oasis-open.org

Subject: [ws-dd-comment] SOAP 1.2 HTTP transport binding URI conflict

Hello,

in DPWS 1.1 public review draft 1 section 1.5 Normative References there are two conflicting entries I think: [SOAP 1.2, Part 2] and [WSDL Binding for SOAP 1.2]

In [SOAP 1.2, Part 2] section 7.2 "Binding Name" it says:

This binding is identified by the URI[...]:

* "http://www.w3.org/2003/05/soap/bindings/HTTP/"

In [WSDL Binding for SOAP 1.2] section 3.1 "wsoap12:binding Element": /wsoap12:binding/@transport

The value of the REQUIRED transport attribute (of type xs:anyURI) indicates which transport of SOAP this binding corresponds to. The URI value "http://schemas.xmlsoap.org/soap/http" corresponds to the HTTP binding. Other URIs may be used here to indicate other transports (such as SMTP, FTP, etc.).

The comment from the W3C team can be found on: http://www.w3.org/Submission/2006/05/Comment#wsdl11comment. In the last paragraph of the "WSDL 1.1 Binding Extension for SOAP 1.2" section they say:

A characteristic of this SOAP 1.2 binding of WSDL 1.1 is that it uses the http://schemas.xmlsoap.org/soap/http URI as the identifier for HTTP as the transport of SOAP; this is the URI which was introduced by WSDL 1.1 to identify the SOAP 1.1 HTTP binding. This is interesting as the SOAP 1.2 HTTP binding defines a URI for its identification (http://www.w3.org/2003/05/soap/bindings/HTTP/) already, and Architecture of the World Wide Web, Volume One points out that URI aliases should be avoided.

I discovered the problem, because the SUN Metro stack for example uses the [SOAP 1.2, Part 2] variant and had problems with WSDL files generated with some the available DPWS stacks that took the [WSDL Binding for SOAP 1.2] way.

I propose to use the [SOAP 1.2, Part 2] way and remove the [WSDL Binding for SOAP 1.2] reference. That way it is on track with the W3C and the SUN Java6SE SDK for example.

I am glad to hear from you,

Stephan

Stephan Pöhlsen

University of Lübeck Phone: +49 451 500-5386

Institute of Telematics Fax: +49 451 500-5382

Ratzeburger Allee 160 poehlsen@itm.uni-luebeck.de

D-23538 Lübeck, Germany http://www.itm.uni-luebeck.de

Toby Nixon | Senior Standards Program Manager | Windows Device and Storage Technologies | Microsoft Corporation

toby.nixon@microsoft.com | www.microsoft.com | V: +1 425 706 2792 | M: +1 206 790 6377 | F: +1 425 708 4811

ws-dd-comment message