LC29D resolution

To fulfill my action item listed as

?         2004-09-23: DaveO to add more descriptive text 

                      regarding LC29d.

 

On http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC29d

 

 

Old Text:

*         Mechanisms that are outside the scope of this specification
MAY modify the serialization format of the instance data
<http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#instance_data#in
stance_data>  corresponding to the output message. An example of such
modification is the combination of the serialization as
application/x-www-form-urlencoded and the SOAP-Response Message Exchange
Pattern
<http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#soapresmep>
([SOAP 1.2 Part 2: Adjuncts
<http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#SOAP12-PART2#SOA
P12-PART2> ], Section 6.3).

 

Proposed resolution

*         Mechanisms other than setting the serialization properties MAY
modify the serialization format of the instance data
<http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#instance_data#in
stance_data>  corresponding to the message. An example of such
modification is the WSDL SOAP Binding HTTP URI Serialization rules
http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#soap-defaults.
This binding specifies that the SOAP-Response Message Exchange Pattern
<http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#soapresmep>
([SOAP 1.2 Part 2: Adjuncts
<http://www.w3.org/TR/2004/WD-wsdl20-bindings-20040803/#SOAP12-PART2#SOA
P12-PART2> ], Section 6.3) only supports input message serialization as
application/x-www-form-urlencoded.  Other examples of such mechanisms
are other message exchange patterns or bindings.

 

Cheers,

Dave