- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Mon, 4 Oct 2004 09:46:41 -0700
- To: "Asir Vedamuthu" <asirv@webmethods.com>, <public-ws-desc-comments@w3.org>
- Cc: "Wes Moulder" <Wes@webMethods.com>
The editors have incorporated this fix into the latest editorial draft
[1]
If we don't hear from you by Oct 15th, we'll assume this satisfactorily
resolves your issue [2].
[1]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-bindings.
html?content-type=text/html;%20charset=utf-8#soap-binding
[2] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC15
> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of Asir Vedamuthu
> Sent: Monday, August 23, 2004 6:17 PM
> To: 'public-ws-desc-comments@w3.org'
> Cc: Wes Moulder
> Subject: Editorial: {http location} feature
>
>
> This is an editorial issue. I am writing it on behalf of Wes Moulder,
> webMethods.
>
> ref:
http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#soap-binding
>
> The last para in this section describes the use of {http location}
feature
> within SOAP binding:
>
> "When the SOAP Message Exchange Pattern is the SOAP Response MEP, the
> Binding Operation may use the {http location} property defined in 3.6
> Binding Operations. When such a location is specified, the Endpoint
> component also follows the rules for constructing the address from the
> {address} property and the {http location} property values."
>
> To avoid confusion, we request you to list {http location} as the
fifth
> bullet along with,
> {http version}
> {http transfer coding}
> {http cookies}
> {http authentication scheme}
>
> Regards,
> Asir S Vedamuthu
> asirv at webmethods dot com
> http://www.webmethods.com/
Received on Monday, 4 October 2004 16:47:12 UTC