RE: Issue 117 - DPWS - Merge R019 and R2020

[Dan Driscoll <Dan.Driscoll@microsoft.com>]

This fix makes sense--we have defined an interoperable baseline binding as SOAP 1.2 doc-lit; a literal interpretation of the existing restrictions would allow someone to advertise a "conforming" service that does not implement this baseline.  The proposed change appears to properly address that problem.

Thanks Antoine!
--D

-----Original Message-----
From: Ram Jeyaraman [mailto:Ram.Jeyaraman@microsoft.com]
Sent: Monday, December 15, 2008 6:35 PM
To: ws-dd@lists.oasis-open.org
Subject: [ws-dd] Issue 117 - DPWS - Merge R019 and R2020

This issue is assigned the number 117. For further discussions on this issue, please refer to this issue number or use this thread.

-----Original Message-----
From: Antoine Mensch [mailto:antoine.mensch@odonata.fr]
Sent: Saturday, December 13, 2008 3:15 AM
To: Ram Jeyaraman
Subject: NEW Issue - DPWS - Merge R019 and R2020

Doc: DPWS CD1
Line: 644-650

Description:

The following requirements constrain the type of bindings that may
appear in a WSDL for hosted services:

R2019: A HOSTED SERVICE MUST at least include a document-literal Binding
for each portType in its WSDL.

Because the document-literal SOAP Binding is more general than an
rpc-literal SOAP Binding, there is no requirement to use anything other
than the document-literal Binding.

R2020: A HOSTED SERVICE MUST at least include a WSDL Binding for SOAP
1.2 for each portType in its WSDL.

R2028: A HOSTED SERVICE is not required to include any WSDL bindings for
SOAP 1.1 in its WSDL.


A bad-mannered HOSTED SERVICE could decide to offer a SOAP1.1
document-literal binding and a SOAP1.2 rpc-literal binding and still be
compliant with the above.
In addition, R2028 is not formally expressed as a requirement (it is
actually a non-requirement cancelling a BP1.1 requirement), and could
probably be removed or transformed into explanatory text.

Proposed resolution:

Replace R2019 with:

R2019: A HOSTED SERVICE MUST at least include a document-literal Binding
for SOAP 1.2 over HTTP for each portType in its WSDL.

Remove R2020 and R2028.

Replace the explanatory text:
Since this profile brings SOAP 1.2 into scope, it is sufficient to bind
to that version of SOAP. There is no requirement to bind to other SOAP
versions and thus R2028 updates R2401 in [BP 1.1, Section 4
<#bp11section4>] to SOAP 1.2.
With:
Since this profile brings SOAP 1.2 into scope, it is sufficient to bind
to that version of SOAP. Thus, R2019 updates R2401 in [BP 1.1, Section 4
<#bp11section4>] to SOAP 1.2, and implies that a HOSTED SERVICE is not
required to include any WSDL bindings for SOAP 1.1 in its WSDL.



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php