W3C home > Mailing lists > Public > public-ws-desc-eds@w3.org > June 2004

2002/ws/desc/wsdl20 wsdl20-bindings.html,1.30,1.31 wsdl20-bindings.xml,1.35,1.36

From: Sanjiva Weerawarana <sweeraw@dev.w3.org>
Date: Wed, 23 Jun 2004 07:20:46 +0000
To: public-ws-desc-eds@w3.org
Message-Id: <20040623072046.6EC4F4A845@hutz.w3.org>

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv26650

Modified Files:
	wsdl20-bindings.html wsdl20-bindings.xml 
Log Message:
marching thru editorial AIs

Index: wsdl20-bindings.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -C2 -d -r1.35 -r1.36
*** wsdl20-bindings.xml	23 Jun 2004 06:06:34 -0000	1.35
--- wsdl20-bindings.xml	23 Jun 2004 07:20:43 -0000	1.36
***************
*** 307,310 ****
--- 307,354 ----
        <!-- +++++++++ -->
  
+       <div2 id="soap-defaults">
+         <head>Default Binding Rules</head>
+ 
+         <ulist>
+           <item><p><emph>Payload Construction.</emph> When formulating
+           the SOAP envelope to be transmitted the contents of the
+           payload (i.e., the contents of the <el>soap:Body</el> &EII;
+           of the SOAP envelope) MUST be what is defined by the
+           corresponding Message Reference component, subject to
+           optimization of MTOM <bibref ref="MTOM"/> if that feature is
+           in use. The following default binding rules MUST be adhered to:</p>
+           <ulist>
+             <item><p>If the value of the {message content model}
+             property of the Message Reference component is
+             <emph>#any</emph> then the payload MAY be any one XML
+             element.</p></item>
+ 
+             <item><p>If the value is <emph>#none</emph> then the
+             payload MUST be empty.</p></item>
+ 
+             <item><p>If the value is <emph>#element</emph> then the
+             payload will be the &EII; identified by the the {element}
+             property of the Message Reference component.</p></item>
+  
+             <item> <p>If the Message Reference component is declared
+             using a non-XML type system (as considered in the Types
+             section of <bibref ref="WSDL-PART1"/>) then additional
+             binding rules MUST be defined to indicate how to map those
+             components into the SOAP envelope. </p></item>
+           </ulist></item>
+ 
+           <item><p><emph>SOAPAction.</emph> If a value for the {soap
+           action} property of a Binding Operation component has not
+           been specified then the SOAP Action Feature (see <bibref
+           ref="SOAP12-PART2"/>) has no value assigned by the Binding
+           component.</p></item>
+ 
+           <item><p><emph></emph></p></item>
+         </ulist>
+ 
+       </div2>
+ 
+       <!-- +++++++++ -->
+ 
        <div2 id="soap-binding-decl">
          <head>Indicating a SOAP Binding</head>
***************
*** 464,485 ****
          </div3>
        </div2>
-       <!-- +++++++++ -->
-       <div2 id="soap-defaults">
-         <head>Default Binding Rules</head>
-         <p>When formulating the SOAP envelope to be transmitted the contents
- of the payload (i.e., the contents of the <el>soap:Body</el>
-           &EII; of
- the SOAP envelope) MUST be what is defined by the corresponding
- Message Reference component.  If the value of the {message
- content model} property of the Message Reference component is
- <emph>#any</emph> then the payload MAY be any one XML element. If the
- value is <emph>#none</emph> then the payload MUST be empty. Finally if
- the value is <emph>#element</emph> then the payload will be the &EII;
- identified by the the {element} property of the Message Reference
- component.</p>
-         <p>If the Message Reference component is declared using a non-XML type
- system (as considered in the Types section of <bibref ref="WSDL-PART1"/>) then additional binding rules MUST be defined to
- indicate how to map those components into the SOAP envelope. </p>
-       </div2>
  
        <!-- +++++++++ -->
--- 508,511 ----
***************
*** 2169,2172 ****
--- 2195,2201 ----
  	    available at http://www.w3.org/TR/soap12-part2/.
  	  </bibl>
+           <bibl id="MTOM" key="SOAP Message Transmission Optimization Mechanism" href="http://www.w3.org/TR/2004/WD-soap12-mtom-20040608" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest">
+             <titleref xlink:type="simple" xlink:show="new" xlink:actuate="onRequest">SOAP Message Transmission Optimization Mechanism</titleref>, N. Mendelsohn, M. Nottingham, and H. Ruellan, Editors. World Wide Web Consortium, Working Draft 8 June 2004.
+           </bibl>
            <bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2000/REC-xml-20001006" xlink:type="simple" xlink:show="replace" xlink:actuate="onRequest">
              <titleref xlink:type="simple" xlink:show="new" xlink:actuate="onRequest">Extensible Markup Language (XML) 1.0 (Second
***************
*** 2355,2358 ****
--- 2384,2397 ----
   <td>20040623</td>
   <td>SW</td>
+  <td>Fixed up soapaction default rules</td>
+ </tr>
+ <tr>
+  <td>20040623</td>
+  <td>SW</td>
+  <td>Allowed use of MTOM for payload serialization</td>
+ </tr>
+ <tr>
+  <td>20040623</td>
+  <td>SW</td>
   <td>Fixed up the wsoap:protocol section</td>
  </tr>

Index: wsdl20-bindings.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-bindings.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -C2 -d -r1.30 -r1.31
*** wsdl20-bindings.html	23 Jun 2004 06:06:34 -0000	1.30
--- wsdl20-bindings.html	23 Jun 2004 07:20:43 -0000	1.31
***************
*** 83,88 ****
    <hr><div class="toc">
  <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#soap-binding">WSDL SOAP Binding</a><br>3. <a href="#http-binding">WSDL HTTP Binding</a><br>4. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Part 3 Change Log</a> (Non-Normative)<br></p></div><hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notcon">Notational Conventions</a><br>2. <a href="#soap-binding">WSDL SOAP Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#soap-syntax">XML Syntax Summary (Non-Normative)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#soap-binding-decl">Indicating a SOAP Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#soap-protocol">Specifying the SOAP Protocol</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.1 <a href="#soap-binding-decl-xml">XML Representation for Specifying the SOAP Protocol</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.3.2 <a href="#soap-binding-decl-mapping">Mapping Between Binding Component Extension Properties
!           and XML Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#soap-defaults">Default Binding Rules</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.5 <a href="#soap-module-decl">SOAP Module</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.1 <a href="#soap-module-decl-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.2 <a href="#soap-module-decl-property">SOAP Module Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.3 <a href="#soap-module-decl-xml">XML Representation of SOAP Module Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.4 <a href="#soap-module-decl-mapping">Mapping Between SOAP Module's XML Representation to Component
  Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.6 <a href="#soap-fault-decl">Indicating a SOAP Fault</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.6.1 <a href="#soap-fault-decl-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.6.2 <a href="#soap-fault-decl-property">SOAP Fault Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.6.3 <a href="#soap-fault-decl-xml">XML Representation of SOAP Fault Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.6.4 <a href="#soap-fault-decl-mapping">Mapping Between SOAP Fault's XML Representation to Component
  Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.7 <a href="#soap-operation-decl">Indicating a SOAP Operation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.7.1 <a href="#soap-operation-decl-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.7.2 <a href="#soap-operation-decl-property">SOAP Operation Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.7.3 <a href="#soap-operation-decl-xml">XML Representation of SOAP Operation Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.7.4 <a href="#soap-operation-decl-mapping">Mapping Between SOAP Operation's XML Representation to Component
--- 83,88 ----
    <hr><div class="toc">
  <h2><a name="shortcontents">Short Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>2. <a href="#soap-binding">WSDL SOAP Binding</a><br>3. <a href="#http-binding">WSDL HTTP Binding</a><br>4. <a href="#References">References</a><br>A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Part 3 Change Log</a> (Non-Normative)<br></p></div><hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro">Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notcon">Notational Conventions</a><br>2. <a href="#soap-binding">WSDL SOAP Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#soap-syntax">XML Syntax Summary (Non-Normative)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#soap-defaults">Default Binding Rules</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#soap-binding-decl">Indicating a SOAP Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#soap-protocol">Specifying the SOAP Protocol</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.1 <a href="#soap-binding-decl-xml">XML Representation for Specifying the SOAP Protocol</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.4.2 <a href="#soap-binding-decl-mapping">Mapping Between Binding Component Extension Properties
!           and XML Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.5 <a href="#soap-module-decl">SOAP Module</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.1 <a href="#soap-module-decl-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.2 <a href="#soap-module-decl-property">SOAP Module Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.3 <a href="#soap-module-decl-xml">XML Representation of SOAP Module Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.5.4 <a href="#soap-module-decl-mapping">Mapping Between SOAP Module's XML Representation to Component
  Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.6 <a href="#soap-fault-decl">Indicating a SOAP Fault</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.6.1 <a href="#soap-fault-decl-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.6.2 <a href="#soap-fault-decl-property">SOAP Fault Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.6.3 <a href="#soap-fault-decl-xml">XML Representation of SOAP Fault Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.6.4 <a href="#soap-fault-decl-mapping">Mapping Between SOAP Fault's XML Representation to Component
  Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.7 <a href="#soap-operation-decl">Indicating a SOAP Operation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.7.1 <a href="#soap-operation-decl-relate">Relationship to WSDL Component Model</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.7.2 <a href="#soap-operation-decl-property">SOAP Operation Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.7.3 <a href="#soap-operation-decl-xml">XML Representation of SOAP Operation Component</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;2.7.4 <a href="#soap-operation-decl-mapping">Mapping Between SOAP Operation's XML Representation to Component
***************
*** 330,334 ****
        <div class="div2">
          
! <h3><a name="soap-binding-decl"></a>2.2 Indicating a SOAP Binding</h3>
  
          <p>A Binding component (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>])
--- 330,378 ----
        <div class="div2">
          
! <h3><a name="soap-defaults"></a>2.2 Default Binding Rules</h3>
! 
!         <ul>
!           <li><p><em>Payload Construction.</em> When formulating
!           the SOAP envelope to be transmitted the contents of the
!           payload (i.e., the contents of the <code>soap:Body</code>  <em>element information item</em>
!           of the SOAP envelope) MUST be what is defined by the
!           corresponding Message Reference component, subject to
!           optimization of MTOM [<cite><a href="#MTOM">SOAP Message Transmission Optimization Mechanism</a></cite>] if that feature is
!           in use. The following default binding rules MUST be adhered to:</p>
!           <ul>
!             <li><p>If the value of the {message content model}
!             property of the Message Reference component is
!             <em>#any</em> then the payload MAY be any one XML
!             element.</p></li>
! 
!             <li><p>If the value is <em>#none</em> then the
!             payload MUST be empty.</p></li>
! 
!             <li><p>If the value is <em>#element</em> then the
!             payload will be the <em>element information item</em> identified by the the {element}
!             property of the Message Reference component.</p></li>
!  
!             <li> <p>If the Message Reference component is declared
!             using a non-XML type system (as considered in the Types
!             section of [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]) then additional
!             binding rules MUST be defined to indicate how to map those
!             components into the SOAP envelope. </p></li>
!           </ul></li>
! 
!           <li><p><em>SOAPAction.</em> If a value for the {soap
!           action} property of a Binding Operation component has not
!           been specified then the SOAP Action Feature (see [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>]) has no value assigned by the Binding
!           component.</p></li>
! 
!           <li><p><em></em></p></li>
!         </ul>
! 
!       </div>
! 
!       
! 
!       <div class="div2">
!         
! <h3><a name="soap-binding-decl"></a>2.3 Indicating a SOAP Binding</h3>
  
          <p>A Binding component (defined in [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>])
***************
*** 342,346 ****
        <div class="div2">
          
! <h3><a name="soap-protocol"></a>2.3 Specifying the SOAP Protocol</h3>
  
          <p>The SOAP protocol (see SOAP Protocol Binding Framework
--- 386,390 ----
        <div class="div2">
          
! <h3><a name="soap-protocol"></a>2.4 Specifying the SOAP Protocol</h3>
  
          <p>The SOAP protocol (see SOAP Protocol Binding Framework
***************
*** 367,371 ****
          <div class="div3">
            
! <h4><a name="soap-binding-decl-xml"></a>2.3.1 XML Representation for Specifying the SOAP Protocol</h4>
            <div class="exampleInner"><pre>&lt;definitions &gt;
    &lt;binding  name="<em>xs:NCName</em>" interface="<em>xs:QName</em>"? type="<em>xs:anyURI</em>"
--- 411,415 ----
          <div class="div3">
            
! <h4><a name="soap-binding-decl-xml"></a>2.4.1 XML Representation for Specifying the SOAP Protocol</h4>
            <div class="exampleInner"><pre>&lt;definitions &gt;
    &lt;binding  name="<em>xs:NCName</em>" interface="<em>xs:QName</em>"? type="<em>xs:anyURI</em>"
***************
*** 392,396 ****
          <div class="div3">
            
! <h4><a name="soap-binding-decl-mapping"></a>2.3.2 Mapping Between Binding Component Extension Properties
            and XML Representation</h4>
  
--- 436,440 ----
          <div class="div3">
            
! <h4><a name="soap-binding-decl-mapping"></a>2.4.2 Mapping Between Binding Component Extension Properties
            and XML Representation</h4>
  
***************
*** 413,435 ****
          </div>
        </div>
-       
-       <div class="div2">
-         
- <h3><a name="soap-defaults"></a>2.4 Default Binding Rules</h3>
-         <p>When formulating the SOAP envelope to be transmitted the contents
- of the payload (i.e., the contents of the <code>soap:Body</code> 
-           <em>element information item</em> of
- the SOAP envelope) MUST be what is defined by the corresponding
- Message Reference component.  If the value of the {message
- content model} property of the Message Reference component is
- <em>#any</em> then the payload MAY be any one XML element. If the
- value is <em>#none</em> then the payload MUST be empty. Finally if
- the value is <em>#element</em> then the payload will be the <em>element information item</em>
- identified by the the {element} property of the Message Reference
- component.</p>
-         <p>If the Message Reference component is declared using a non-XML type
- system (as considered in the Types section of [<cite><a href="#WSDL-PART1">WSDL 2.0 Core Language</a></cite>]) then additional binding rules MUST be defined to
- indicate how to map those components into the SOAP envelope. </p>
-       </div>
  
        
--- 457,460 ----
***************
*** 1269,1273 ****
          </table><br>
          <p>
- 
  	    Mechanisms that are outside the scope of this specification
  	    MAY modify the serialization format of the <a title="instance_data" href="#instance_data">instance data</a> corresponding to
--- 1294,1297 ----
***************
*** 2144,2147 ****
--- 2168,2174 ----
  	    available at http://www.w3.org/TR/soap12-part2/.
  	  </dd>
+           <dt class="label"><a name="MTOM"></a>[SOAP Message Transmission Optimization Mechanism] </dt><dd>
+             <cite><a href="http://www.w3.org/TR/2004/WD-soap12-mtom-20040608">SOAP Message Transmission Optimization Mechanism</a></cite>, N. Mendelsohn, M. Nottingham, and H. Ruellan, Editors. World Wide Web Consortium, Working Draft 8 June 2004.
+           </dd>
            <dt class="label"><a name="XML10"></a>[XML 1.0] </dt><dd>
              <cite><a href="http://www.w3.org/TR/2000/REC-xml-20001006">Extensible Markup Language (XML) 1.0 (Second
***************
*** 2300,2303 ****
--- 2327,2345 ----
  
  <tr>
+  <td rowspan="1" colspan="1">20040623</td>
+  <td rowspan="1" colspan="1">SW</td>
+  <td rowspan="1" colspan="1">Fixed up soapaction default rules</td>
+ </tr>
+ <tr>
+  <td rowspan="1" colspan="1">20040623</td>
+  <td rowspan="1" colspan="1">SW</td>
+  <td rowspan="1" colspan="1">Allowed use of MTOM for payload serialization</td>
+ </tr>
+ <tr>
+  <td rowspan="1" colspan="1">20040623</td>
+  <td rowspan="1" colspan="1">SW</td>
+  <td rowspan="1" colspan="1">Fixed up the wsoap:protocol section</td>
+ </tr>
+ <tr>
   <td rowspan="1" colspan="1">20040618</td>
   <td rowspan="1" colspan="1">SW</td>
Received on Wednesday, 23 June 2004 03:20:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:31:22 UTC