- From: Asir Vedamuthu <asirv@webmethods.com>
- Date: Tue, 24 Aug 2004 07:31:27 -0400
- To: "'public-ws-desc-comments@w3.org'" <public-ws-desc-comments@w3.org>
ref: [1] http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#soap-defaults [2] http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#_http_x-www-form-urle ncoded "If the {soap mep} property of the Binding Operation component has the value "http://www.w3.org/2003/05/soap/mep/soap-response/" then the URI to execute the HTTP GET against MUST be generated using the HTTP binding's rules for generating a URI for HTTP GET (see 3. WSDL HTTP Binding). The input serialization format of x-www-form-urlencoded is the only supported serialization format for HTTP GET in the SOAP Response Message Exchange Pattern." [1] "This serialization format is designed to allow a Web Service to produce a URI based on the instance data of input messages. It may only be used for interface operation using the URI Style format as defined in 3.9.1 URI Style." It appears to me that there is a strong relationship between the value of Message Reference.{style} and {soap mep} properties. Particularly, if {soap mep} has the value "http://www.w3.org/2003/05/soap/mep/soap-response/" then {style} must be http://www.w3.org/2004/08/wsdl/style/uri Is that true? If so, shall we state it? And, shall we establish a default binding rule? Are there too many iffs? Regards, Asir S Vedamuthu asirv at webmethods dot com http://www.webmethods.com/
Received on Tuesday, 24 August 2004 11:32:08 UTC