- From: Hugo Haas <hugo@dev.w3.org>
- Date: Fri, 23 Jul 2004 09:45:38 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20
In directory homer:/tmp/cvs-serv1756
Modified Files:
wsdl20-bindings.xml
Log Message:
Did some fixes to address 226: committing them, but about to change this as
per Asir's suggestion. Now that the binding is organized functionally, I agree
with Asir.
Index: wsdl20-bindings.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.xml,v
retrieving revision 1.75
retrieving revision 1.76
diff -C2 -d -r1.75 -r1.76
*** wsdl20-bindings.xml 23 Jul 2004 09:20:26 -0000 1.75
--- wsdl20-bindings.xml 23 Jul 2004 09:45:36 -0000 1.76
***************
*** 246,267 ****
component.</p>
! <p>A subset of the HTTP components specified in the HTTP
! Binding may be expressed in a SOAP binding when the SOAP binding
! uses HTTP as the underlying protocol. The components that are
! allowed are the ones that contain properties that describe the
! underlying protocol. The components and allowed properties are:
! http:binding with version, cookies, defaultTransferCoding;
! http:operation with defaultTransferCoding; http:input with
! transferCoding; http:output with transferCoding; and
! http:service with authenticationType and
! authenticationRealm.</p>
<p>When the SOAP Message Exchange Pattern is the SOAP Response
! MEP, the binding operation may contain an http:operation with a
! location attribute that follows the http:operation location
! attributes construction rules. When such a location is
! specified, the wsdl:endpoint also follows the rules for
! constructing the address from the wsdl:address and
! http:operation location values.</p>
<!-- +++++++++ -->
--- 246,273 ----
component.</p>
! <p>A subset of the HTTP properties specified in the HTTP Binding
! defined in section <specref ref="http-binding"/> may be
! expressed in a SOAP binding when the SOAP binding uses HTTP as
! the underlying protocol. The properties that are allowed are
! the ones that describe the underlying protocol.</p>
!
! <ulist>
! <item><p>{http version} as defined in <specref
! ref="http-version-decl"/></p></item>
! <item><p>{http transfer coding} as defined in <specref
! ref="http-transfer-coding-decl"/></p></item>
! <item><p>{http cookies} as defined in <specref
! ref="http-cookies-decl"/></p></item>
! <item><p>{http authentication scheme} and {http authentication
! realm} as defined in <specref
! ref="http-auth-decl"/></p></item>
! </ulist>
<p>When the SOAP Message Exchange Pattern is the SOAP Response
! MEP, the Binding Operation may use the {http location} property
! defined in <specref ref="http-operation-decl"/>. When such a
! location is specified, the Endpoint component also follows the
! rules for constructing the address from the &endpoint-address-p;
! property and the {http location} property values.</p>
<!-- +++++++++ -->
***************
*** 1119,1123 ****
<ulist>
! <item><p><emph>HTTP Request Generation.</emph>
When formulating the HTTP message to be transmitted, the
contents of the payload (i.e. the contents of the HTTP message
--- 1125,1129 ----
<ulist>
! <item><p><emph>Payload construction.</emph>
When formulating the HTTP message to be transmitted, the
contents of the payload (i.e. the contents of the HTTP message
Received on Friday, 23 July 2004 05:45:49 UTC