{http location} ignored on SOAP request-response MEP?

I was just looking at Adjuncts 5.10.4 [1], and see that for the SOAP
request-response MEP the immediate destination is "the value of the WSDL
{address
<http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html#propert
y-Endpoint.address> } property of the Endpoint
<http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html#compone
nt-Endpoint>  component."

 

For the SOAP response MEP the immediate destination is "the value of the
WSDL {address
<http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html#propert
y-Endpoint.address> } property, modified by the {http
<http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.htm
l#property-BindingOperation.httplocation>  location} property following the
rules described in section
<http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.htm
l?foo=:;content-type=text/html;%20charset=utf-8#_http_x-www-form-urlencoded#
_http_x-www-form-urlencoded> 6.7.2 Serialization as
application/x-www-form-urlencoded."

 

>From this I infer the {http location} is ignored for the SOAP
request-response MEP, including (after CR114 closure) the use of in-only and
robust-in-only WSDL MEPs.

 

Is this intentional?  I recall discussing using URI templates with POST,
where the body would contain the full data and the URI might carry some
duplicates.  Also, disabling {http location} for POST seems quite unRESTful.

 

If this is simply an editorial mistake, then we should copy the {http
location} handling text above into the SOAP request-response MEP
description.

 

[1]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.html
?foo=:;content-type=text/html;%20charset=utf-8#wsdl-mep-soap-mep

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com