Issue 28 proposal

Hi, here is a proposal for resolving the long-standing issue 28 [1].

The issue deals with the fact that in SOAP there may be multiple
different bindings to any given transport and the 'transport' attribute
doesn't seem to distinguish between them.

I'd add to this issue the distinction that some people make between
'transport' and 'application' protocols, specifically HTTP being the
latter.

I propose that we simply rename the 'transport' attribute to 'protocol',
its value being the binding name as specified by the particular Protocol
Binding specification (for SOAP 1.2 HTTP binding - from the Candidate
Rec, it is "http://www.w3.org/2002/12/soap/bindings/HTTP/" (see [2]).
Thus the WSDL spec would no longer create its own names for protocols.

Best regards,

                   Jacek Kopecky

                   Senior Architect
                   Systinet Corporation
                   http://www.systinet.com/




[1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x28
[2] http://www.w3.org/TR/soap12-part2/#http-bindname

Received on Friday, 18 April 2003 03:45:13 UTC