

New Issue: UsingAddressing with other bindings than our SOAP binding.

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Fri, 30 Sep 2005 10:03:49 -0700
Message-ID: <37D0366A39A9044286B2783EB4C3C4E831ED79@RED-MSG-10.redmond.corp.microsoft.com>
Currently section 3.1 of the WSDL binding defines the use of
wsaw:UsingAddressing in a WSDL SOAP binding as engaging our SOAP binding
spec.  However, it also can be used in other bindings, say the WSDL 2.0
HTTP binding, to indicate that addressing is engaged.  However, there is
not a spec that describes this behavior.  Furthermore, if a spec did
exist there would not be a hard requirement to use that spec.  If there
were two specs, there would be an ambiguity as to which one was engaged.


So in practice, the extension is insufficient to indicate the specific
details necessary to use WS-Addressing other than for our SOAP binding.
An author of a spec for another binding would need to extend
wsaw:UsingAddressing, or introduce their own extension.  The latter
appears no more difficult than the former, and allows engagement of WSDL
extensibility mechanisms (e.g. wsdl:required) directly.


I propose that we define wsaw:UsingAddressing as engaging our SOAP
binding only.  Use with any other type of binding is undefined.


--  Jonathan Marsh  --  jmarsh@microsoft.com
<mailto:jmarsh@microsoft.com>   --

Received on Friday, 30 September 2005 17:03:53 GMT
