W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > April to June 2005

2004/ws/addressing ws-addr-wsdl.html,1.23,1.24

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 22 Apr 2005 22:39:43 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1DP6oJ-0001eS-7p@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv6319

Modified Files:
	ws-addr-wsdl.html 
Log Message:
sync with xml

Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -C2 -d -r1.23 -r1.24
*** ws-addr-wsdl.html	22 Mar 2005 16:22:02 -0000	1.23
--- ws-addr-wsdl.html	22 Apr 2005 22:39:41 -0000	1.24
***************
*** 66,71 ****
          no official standing.</strong></p><p></p></div>
      <hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange"> Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation"> Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#actioninwsdl"> Associating Action with WSDL Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#explicitaction"> Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>4. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#WSDL11MEPS">WSDL 1.1 Messag Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#wsdl11oneway">One-way</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.3 <a href="#wsdl11notification">Notification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#wsdl20inonly">In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.3 <a href="#wsdl20inout">In-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.5 <a href="#wsdl20outonly">Out-only/a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.7 <a href="#wsdl20outin">Out-in</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>5. <a href="#references"> References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N10AB1">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N10ABB">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N10AC5">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
--- 66,71 ----
          no official standing.</strong></p><p></p></div>
      <hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange"> Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation"> Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#N101C3">Indicating Use of WS-Addressing</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#N101CB">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#N101FA">WSDL SOAP Module</a><br>4. <a href="#actioninwsdl"> Associating Action with WSDL Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#explicitaction"> Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4. <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.1 <a href="#wsdl11oneway">One-way</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.3 <a href="#wsdl11notification">Notification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#wsdl20inonly">In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3 <a href="#wsdl2inout">In-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5 <a href="#wsdl20outonly">Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.7 <a href="#wsdl20outin">Out-in</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#references"> References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N10B29">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N10B33">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N10B3D">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 75,81 ****
                  reference Web service endpoints and to facilitate end-to-end addressing of endpoints
                  in messages. Web Services Addressing 1.0 - WSDL Binding (this document) defines how the abstract
!                 properties defined in Web Services Addressing 1.0 - Core are described using WSDL. WS-Addressing is 
! 			designed to be able to work with WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0</a></cite>] and also (for backwards 
! 			compatibility with WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] described services.</p>
              <div class="div2">
                  
--- 75,81 ----
                  reference Web service endpoints and to facilitate end-to-end addressing of endpoints
                  in messages. Web Services Addressing 1.0 - WSDL Binding (this document) defines how the abstract
!                 properties defined in Web Services Addressing 1.0 - Core are described using WSDL. WS-Addressing
!                 is designed to be able to work with WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0</a></cite>] and also (for
!                 backwards compatibility with WSDL 1.1 [<cite><a href="#WSDL11">WSDL 1.1</a></cite>] described services.</p>
              <div class="div2">
                  
***************
*** 129,136 ****
                              <td rowspan="1" colspan="1">http://www.w3.org/2001/XMLSchema</td>
                          </tr>
                      </tbody>
                  </table><br>
!                 <p>WS-Addressing is defined in terms of the XML Information Set [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]. WS-Addressing may be used with
!                     SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>] as described in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. The examples in this specification use an XML 1.0
                          [<cite><a href="#XML10">XML 1.0</a></cite>] representation but this is not a requirement.</p>
                  <p>All information items defined by this specification are identified by the XML
--- 129,148 ----
                              <td rowspan="1" colspan="1">http://www.w3.org/2001/XMLSchema</td>
                          </tr>
+                         <tr>
+                             <td rowspan="1" colspan="1">wsdl</td>
+                             <td rowspan="1" colspan="1">Either http://www.w3.org/2004/08/wsdl or
+                                 http://schemas.xmlsoap.org/wsdl/ depending on context</td>
+                         </tr>
+                         <tr>
+                             <td rowspan="1" colspan="1">wsdl20</td>
+                             <td rowspan="1" colspan="1">http://www.w3.org/2004/08/wsdl</td>
+                         </tr>
+                         <tr>
+                             <td rowspan="1" colspan="1">wsdl11</td>
+                             <td rowspan="1" colspan="1">http://schemas.xmlsoap.org/wsdl/</td>
+                         </tr>
                      </tbody>
                  </table><br>
!                 <p>WS-Addressing is defined in terms of the XML Information Set [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]. WS-Addressing may be used with SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>] as described in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. The examples in this specification use an XML 1.0
                          [<cite><a href="#XML10">XML 1.0</a></cite>] representation but this is not a requirement.</p>
                  <p>All information items defined by this specification are identified by the XML
***************
*** 217,223 ****
                      service component is also provided inside a descriptions or definitions
                      component, then the ServiceName SHOULD match the name of (one or more of) the
!                     WSDL service(s) included therein; the endpoint (port) name SHOULD match as well if
!                     present. The behavior of an EPR consumer when the ServiceName doesn&rsquo;t match an
!                     embedded description is undefined.</p>
                  <div class="exampleOuter">
                      <p class="exampleHead" style="text-align: left"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
--- 229,235 ----
                      service component is also provided inside a descriptions or definitions
                      component, then the ServiceName SHOULD match the name of (one or more of) the
!                     WSDL service(s) included therein; the endpoint (port) name SHOULD match as well
!                     if present. The behavior of an EPR consumer when the ServiceName doesn&rsquo;t match
!                     an embedded description is undefined.</p>
                  <div class="exampleOuter">
                      <p class="exampleHead" style="text-align: left"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
***************
*** 228,232 ****
    &lt;wsa:Address&gt;http://example.com/fabrikam/acct&lt;/wsa:Address&gt;
    &lt;wsa:Metadata
!       xmlns:wsdli="http://www.w3.org/@@@@/@@/wsdl-instance"
        wsdli:wsdlLocation="http://example.com/fabrikam http://example.com/fabrikam.wsdl"&gt;
      &lt;wsdl20:description  
--- 240,244 ----
    &lt;wsa:Address&gt;http://example.com/fabrikam/acct&lt;/wsa:Address&gt;
    &lt;wsa:Metadata
!       xmlns:wsdli="http://www.w3.org/2004/08/wsdl-instance"
        wsdli:wsdlLocation="http://example.com/fabrikam http://example.com/fabrikam.wsdl"&gt;
      &lt;wsdl20:description  
***************
*** 234,238 ****
          xmlns:fabrikam="http://example.com/fabrikam"
          xmlns:abc="http://www.abccorp.com/"
!         xmlns:wsdl20="http://www.w3.org/2004/12/wsdl"&gt;
        &lt;wsdl20:import namespace="http://example.com/fabrikam/"
            location="http://example.com/fabrikam/fabrikam.wsdl/"/&gt;
--- 246,250 ----
          xmlns:fabrikam="http://example.com/fabrikam"
          xmlns:abc="http://www.abccorp.com/"
!         xmlns:wsdl20="http://www.w3.org/2004/08/wsdl"&gt;
        &lt;wsdl20:import namespace="http://example.com/fabrikam/"
            location="http://example.com/fabrikam/fabrikam.wsdl/"/&gt;
***************
*** 266,270 ****
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns:iiop="http://www.iiop.org/"
!         xmlns:wsdl11="http://www.w3.org/@@@@/@@/wsdl"&gt;
        &lt;wsdl11:import namespace="http://example.com/fabrikam"  
            location="http://example.com/fabrikam/fabrikam.wsdl"/&gt;
--- 278,282 ----
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns:iiop="http://www.iiop.org/"
!         xmlns:wsdl11="http://schemas.xmlsoap.org/wsdl/"&gt;
        &lt;wsdl11:import namespace="http://example.com/fabrikam"  
            location="http://example.com/fabrikam/fabrikam.wsdl"/&gt;
***************
*** 288,292 ****
          <div class="div1">
              
! <h2><a name="actioninwsdl"></a>3.  Associating Action with WSDL Operations</h2>
              <p>Ensuring that there is sufficient information within a message to distinguish which
                  WSDL operation it is associated with is specified as a best practice in WSDL
--- 300,401 ----
          <div class="div1">
              
! <h2><a name="N101C3"></a>3. Indicating Use of WS-Addressing</h2>
!             <p>This specification supports two mechanisms for indicating, in a WSDL
!                 description, that the endpoint conforms to the WS-Addressing specification. </p>
!             <div class="div2">
!                 
! <h3><a name="N101CB"></a>3.1 UsingAddressing Extension Element</h3>
!                 <p>WS-Addressing defines an empty global element, wsaw:UsingAddressing, that may be
!                     used to indicate that an endpoint conforms to the WS-Addressing specification.
!                     The wsdl:required attribute MAY be used to indicate whether WS-Addressing Message
!                     Addressing Properties are required in messages received from service requesters.</p>
!                 <p>A wsaw:UsingAddressing element with a wsdl:required attribute whose value is
!                     "true" indicates that messages exchanged with the endpoint MUST contain
!                     WS-Addressing Message Addressing Properties. A wsaw:UsingAddressing element with
!                     a wsdl:required attribute whose value is "false" indicates that the endpoint
!                     will accept input messages with or without WS-Addressing header blocks, and MAY
!                     generate output messages containing WS-Addressing headers. If a SOAP binding is
!                     used and WS-Addressing header blocks are not present in an input message then
!                     WS-Addressing header blocks encoded in the corresponding output message MUST NOT
!                     be required to be understood using the SOAP mustUnderstand mechanism.</p>
!                 <p>The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding
!                     element. Alternatively, the wsaw:UsingAddressing element MAY instead be included
!                     as a child of the wsdl20:endpoint (or wsdl11:port) when an endpoint intends to
!                     indicate compliance with WS-Addressing for a specific endpoint only.</p>
!                 <p>The inclusion of the wsaw:UsingAddressing element indicates that the applicable
!                     WS-Addressing specifications are supported within the constraints of the WSDL
!                     binding being used. That is, uses of the WS-Addressing specifications that may
!                     violate or are inconsistent with the semantics of the endpoint's WSDL binding
!                     are not supported unless explicitly stated by some other mechanism.</p>
!                 <p>Specifically, when included in a SOAP binding, the wsaw:UsingAddressing marker
!                     identifies the use of Web Services Addressing 1.0 bound to SOAP as defined by
!                         Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>].</p>
!                 <p>The presence of the wsaw:UsingAddressing element in the binding or
!                     endpoint (port) components of the endpoint description does not change the semantics
!                     of the binding. E.g. in the case of the WSDL SOAP/HTTP synchronous 
!                     binding for request-response
!                     operations, the presence of the wsaw:UsingAddressing element does not change 
!                     the requirement that the response message be sent
!                     over the same HTTP channel over which the request was received. In this case, 
!                     the wsa:replyTo header in the request MUST NOT contain an
!                     address with a value different from the anonymous URI.</p>
!                 <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</i></p>
!                     <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
!     interface="tns:reservationInterface"
!     type="http://www.w3.org/2004/08/wsdl/soap12"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
!   &lt;wsaw:UsingAddressing wsdl:required="true" /&gt;
!   &lt;operation ref="tns:opCheckAvailability"
!       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response" /&gt;
!   &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
! &lt;/binding&gt;</pre></div>
!                 </div>
!                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 1.1</i></p>
!                     <div class="exampleInner"><pre>&lt;binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"&gt;
!   &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
!   &lt;wsaw:UsingAddressing wsdl:required="true" /&gt;
!   &lt;operation name="GetLastTradePrice"&gt;
!     &lt;soap:operation soapaction="http://example.com/GetLastTradePrice" /&gt;
!     &lt;input&gt; 
!       &lt;soap:body use="literal" /&gt;
!     &lt;/input&gt; 
!     &lt;output&gt;
!       &lt;soap:body use="literal" /&gt;
!     &lt;/output&gt;
!   &lt;/operation&gt;
! &lt;/binding&gt;</pre></div>
!                 </div>
!            </div>
!             <div class="div2">
!                 
! <h3><a name="N101FA"></a>3.2 WSDL SOAP Module</h3>
!                 <p>In WSDL 2.0, the wsoap:module construct may be used to declare the use of
!                     the WS-Addressing 1.0 Module for the SOAP binding. The meaning of such a 
!                     wsoap:module declaration is
!                     semantically equivalent to wsaw:UsingAddressing in this case. Note
!                     that this module is not meaningful when used on WSDL constructs where
!                     wsaw:UsingAddressing is not allowed.</p>
!                 <p>The WS-Addressing 1.0 SOAP Module is described in 
!                     Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] and is identified with 
!                     the following URI: http://www.w3.org/@@@@/@@/addressing/module</p>
!                 <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</i></p>
!                     <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
!     interface="tns:reservationInterface"
!     type="http://www.w3.org/2004/08/wsdl/soap12"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
!   &lt;wsoap:module uri="http://www.w3.org/@@@@/@@/addressing/module" required="true" /&gt;
!   &lt;operation ref="tns:opCheckAvailability"
!       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response" /&gt;
!   &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
! &lt;/binding&gt;</pre></div>
!                 </div>
!             </div>
!         </div>
!         <div class="div1">
!             
! <h2><a name="actioninwsdl"></a>4.  Associating Action with WSDL Operations</h2>
              <p>Ensuring that there is sufficient information within a message to distinguish which
                  WSDL operation it is associated with is specified as a best practice in WSDL
***************
*** 295,305 ****
              <p>WS-Addressing defines two mechanisms to associate a value of the [action] property
                  with input, output and fault elements within a WSDL description: explicit and
!                 defaulting. Explicit association is described in section <a href="#explicitaction"><b>3.1  Explicit Association</b></a>; action defaulting (where a unique value for the [action] property is
!                 automatically generated) is described in section <a href="#defactionwsdl11"><b>3.3  Default Action Pattern for WSDL 1.1</b></a>
!                 for WSDL 1.1 and section <a href="#defactionwsdl20"><b>3.2 Default Action Pattern for WSDL 2.0</b></a> for WSDL 2.0.</p>
              <div class="div2">
                  
! <h3><a name="explicitaction"></a>3.1  Explicit Association</h3>
!                 <p>WS-Addressing defines a global attribute, wsa:Action, that may be used to
                      explicitly define the value of the [action] property for messages in a WSDL
                      description. The type of the attribute is xs:anyURI and it is used as an
--- 404,413 ----
              <p>WS-Addressing defines two mechanisms to associate a value of the [action] property
                  with input, output and fault elements within a WSDL description: explicit and
!                 defaulting. Explicit association is described in section <a href="#explicitaction"><b>4.1  Explicit Association</b></a>; action defaulting (where a unique value for the [action]
!                 property is automatically generated) is described in section <a href="#defactionwsdl11"><b>4.3  Default Action Pattern for WSDL 1.1</b></a> for WSDL 1.1 and section <a href="#defactionwsdl20"><b>4.2 Default Action Pattern for WSDL 2.0</b></a> for WSDL 2.0.</p>
              <div class="div2">
                  
! <h3><a name="explicitaction"></a>4.1  Explicit Association</h3>
!                 <p>WS-Addressing defines a global attribute, wsaw:Action, that may be used to
                      explicitly define the value of the [action] property for messages in a WSDL
                      description. The type of the attribute is xs:anyURI and it is used as an
***************
*** 307,311 ****
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Explicit specification of wsa:Action value in a WSDL 2.0 description.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 415,419 ----
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-1. </span>Explicit specification of wsaw:Action value in a WSDL 2.0 description.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 314,320 ****
      &lt;operation name="GetLastTradePrice" pattern="http://www.w3.org/2004/08/wsdl/in-out"&gt;
        &lt;input element="tns:GetTradePricesInput" messageLabel="In"
!             wsa:Action="http://example.com/GetQuote"/&gt;
        &lt;output element="tns:GetTradePricesOutput" messageLabel="Out"
!             wsa:Action="http://example.com/Quote"/&gt;
      &lt;/operation&gt;
    &lt;/interface&gt;
--- 422,428 ----
      &lt;operation name="GetLastTradePrice" pattern="http://www.w3.org/2004/08/wsdl/in-out"&gt;
        &lt;input element="tns:GetTradePricesInput" messageLabel="In"
!             wsaw:Action="http://example.com/GetQuote"/&gt;
        &lt;output element="tns:GetTradePricesOutput" messageLabel="Out"
!             wsaw:Action="http://example.com/Quote"/&gt;
      &lt;/operation&gt;
    &lt;/interface&gt;
***************
*** 326,330 ****
                      action for the output of this same operation is http://example.com/Quote.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Explicit specification of wsa:Action value in a WSDL 1.1 description.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 434,438 ----
                      action for the output of this same operation is http://example.com/Quote.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-2. </span>Explicit specification of wsa:Action value in a WSDL 1.1 description.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 333,339 ****
      &lt;operation name="GetLastTradePrice"&gt;
        &lt;input message="tns:GetTradePricesInput"
!             wsa:Action="http://example.com/GetQuote"/&gt;
        &lt;output message="tns:GetTradePricesOutput"
!             wsa:Action="http://example.com/Quote"/&gt;
      &lt;/operation&gt;
    &lt;/portType&gt;
--- 441,447 ----
      &lt;operation name="GetLastTradePrice"&gt;
        &lt;input message="tns:GetTradePricesInput"
!             wsaw:Action="http://example.com/GetQuote"/&gt;
        &lt;output message="tns:GetTradePricesOutput"
!             wsaw:Action="http://example.com/Quote"/&gt;
      &lt;/operation&gt;
    &lt;/portType&gt;
***************
*** 348,357 ****
              <div class="div2">
                  
! <h3><a name="defactionwsdl20"></a>3.2 Default Action Pattern for WSDL 2.0</h3>
                  <p>In the absence of the wsa:Action attribute, the following pattern is used in WSDL
                      2.0 documents to construct a default action for inputs and outputs. The general
                      form of an action URI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][operation name][direction token]
--- 456,465 ----
              <div class="div2">
                  
! <h3><a name="defactionwsdl20"></a>4.2 Default Action Pattern for WSDL 2.0</h3>
                  <p>In the absence of the wsa:Action attribute, the following pattern is used in WSDL
                      2.0 documents to construct a default action for inputs and outputs. The general
                      form of an action URI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][operation name][direction token]
***************
*** 360,364 ****
                  <p>For fault messages, the general form of an action IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </span>Structure of default wsa:Action IRI for faults</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][fault name]
--- 468,472 ----
                  <p>For fault messages, the general form of an action IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-4. </span>Structure of default wsa:Action IRI for faults</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][fault name]
***************
*** 447,451 ****
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-5. </span>Example WSDL without explicit wsa:Action values with explicit message
                          names.</i></p>
                      <div class="exampleInner"><pre>
--- 555,559 ----
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
                          names.</i></p>
                      <div class="exampleInner"><pre>
***************
*** 475,484 ****
              <div class="div2">
                  
! <h3><a name="defactionwsdl11"></a>3.3  Default Action Pattern for WSDL 1.1</h3>
                  <p>In the absence of the wsa:Action attribute, the following pattern is used to
                      construct a default action for inputs and outputs. The general form of an action
                      IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][input|output name]
--- 583,592 ----
              <div class="div2">
                  
! <h3><a name="defactionwsdl11"></a>4.3  Default Action Pattern for WSDL 1.1</h3>
                  <p>In the absence of the wsa:Action attribute, the following pattern is used to
                      construct a default action for inputs and outputs. The general form of an action
                      IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][input|output name]
***************
*** 487,491 ****
                  <p>For fault messages, the general form of an action IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-7. </span>Structure of default wsa:Action IRI for faults</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][operation name]Fault:[fault name]
--- 595,599 ----
                  <p>For fault messages, the general form of an action IRI is as follows:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-7. </span>Structure of default wsa:Action IRI for faults</i></p>
                      <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][operation name]Fault:[fault name]
***************
*** 540,544 ****
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-8. </span>Example WSDL without explicit wsa:Action values with explicit message
                          names.</i></p>
                      <div class="exampleInner"><pre>
--- 648,652 ----
                  <p>For example consider the following WSDL excerpt:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-8. </span>Example WSDL without explicit wsa:Action values with explicit message
                          names.</i></p>
                      <div class="exampleInner"><pre>
***************
*** 569,573 ****
                      not present. Consider the following example:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-9. </span>Example WSDL without explicit wsa:Action values or explicit message names.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 677,681 ----
                      not present. Consider the following example:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 4-9. </span>Example WSDL without explicit wsa:Action values or explicit message names.</i></p>
                      <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 600,618 ****
          <div class="div1">
              
! <h2><a name="WSDLMEPS"></a>4. WS-Addressing and WSDL Message Exchange Patterns</h2>
              <p> This section describes which of the core message properties are mandatory or
                  optional for messages in the various MEPs defined by WSDL 1.1 and WSDL 2.0. </p>
              <div class="div2">
                  
! <h3><a name="WSDL11MEPS"></a>4.1 WSDL 1.1 Message Exchange Patterns</h3>
                  <p> This section describes which of the core message properties are mandatory or
                      optional for messages in the various MEPs defined by WSDL 1.1. </p>
                  <div class="div3">
                      
! <h4><a name="wsdl11oneway"></a>4.1.1 One-way</h4>
                      <p>This is a straightforward one-way message. No responses are expected but
                          related messages could be sent as part of other message exchanges.</p>
                      <table border="1">
!                         <caption>Table 4-1. Message addressing properties for one way message.</caption>
                          <tbody>
                              <tr>
--- 708,726 ----
          <div class="div1">
              
! <h2><a name="WSDLMEPS"></a>5. WS-Addressing and WSDL Message Exchange Patterns</h2>
              <p> This section describes which of the core message properties are mandatory or
                  optional for messages in the various MEPs defined by WSDL 1.1 and WSDL 2.0. </p>
              <div class="div2">
                  
! <h3><a name="WSDL11MEPS"></a>5.1 WSDL 1.1 Message Exchange Patterns</h3>
                  <p> This section describes which of the core message properties are mandatory or
                      optional for messages in the various MEPs defined by WSDL 1.1. </p>
                  <div class="div3">
                      
! <h4><a name="wsdl11oneway"></a>5.1.1 One-way</h4>
                      <p>This is a straightforward one-way message. No responses are expected but
                          related messages could be sent as part of other message exchanges.</p>
                      <table border="1">
!                         <caption>Table 5-1. Message addressing properties for one way message.</caption>
                          <tbody>
                              <tr>
***************
*** 670,678 ****
                  <div class="div3">
                      
! <h4><a name="wsdl11requestresponse"></a>4.1.2 Request-Response</h4>
                      <p> This is request-response. A reply is expected hence mandating [reply
                          endpoint] in the request message. The response message might be a fault. </p>
                      <table border="1">
!                         <caption>Table 4-2. Message addressing properties for request message.</caption>
                          <tbody>
                              <tr>
--- 778,786 ----
                  <div class="div3">
                      
! <h4><a name="wsdl11requestresponse"></a>5.1.2 Request-Response</h4>
                      <p> This is request-response. A reply is expected hence mandating [reply
                          endpoint] in the request message. The response message might be a fault. </p>
                      <table border="1">
!                         <caption>Table 5-2. Message addressing properties for request message.</caption>
                          <tbody>
                              <tr>
***************
*** 726,730 ****
                      </table><br>
                      <table border="1">
!                         <caption>Table 4-3. Message addressing properties for response message.</caption>
                          <tbody>
                              <tr>
--- 834,838 ----
                      </table><br>
                      <table border="1">
!                         <caption>Table 5-3. Message addressing properties for response message.</caption>
                          <tbody>
                              <tr>
***************
*** 782,795 ****
                  <div class="div3">
                      
! <h4><a name="wsdl11notification"></a>4.1.3 Notification</h4>
                      <p>From the WS-Addressing perspective this MEP is the same as One-way. The
!                         properties defined in <a href="#wsdl11oneway"><b>4.1.1 One-way</b></a> apply to this MEP also.
                      </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl11solicitresponse"></a>4.1.4 Solicit-response</h4>
                      <p>From the WS-Addressing perspective this MEP is the same as Request-response.
!                         The properties defined in <a href="#wsdl11requestresponse"><b>4.1.2 Request-Response</b></a> apply to
                          this MEP also.</p>
                  </div>
--- 890,903 ----
                  <div class="div3">
                      
! <h4><a name="wsdl11notification"></a>5.1.3 Notification</h4>
                      <p>From the WS-Addressing perspective this MEP is the same as One-way. The
!                         properties defined in <a href="#wsdl11oneway"><b>5.1.1 One-way</b></a> apply to this MEP also.
                      </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl11solicitresponse"></a>5.1.4 Solicit-response</h4>
                      <p>From the WS-Addressing perspective this MEP is the same as Request-response.
!                         The properties defined in <a href="#wsdl11requestresponse"><b>5.1.2 Request-Response</b></a> apply to
                          this MEP also.</p>
                  </div>
***************
*** 797,810 ****
              <div class="div2">
                  
! <h3><a name="WSDL20MEPS"></a>4.2 WSDL 2.0 Message Exchange Patterns</h3>
                  <p> This section describes which of the core message properties are mandatory or
                      optional for messages in the various MEPs defined by WSDL 2.0. </p>
                  <div class="div3">
                      
! <h4><a name="wsdl20inonly"></a>4.2.1 In-only</h4>
                      <p>This is a straightforward one-way message. No responses are expected but
                          related messages could be sent as part of other message exchanges.</p>
                      <table border="1">
!                         <caption>Table 4-4. Message addressing properties for in message.</caption>
                          <tbody>
                              <tr>
--- 905,918 ----
              <div class="div2">
                  
! <h3><a name="WSDL20MEPS"></a>5.2 WSDL 2.0 Message Exchange Patterns</h3>
                  <p> This section describes which of the core message properties are mandatory or
                      optional for messages in the various MEPs defined by WSDL 2.0. </p>
                  <div class="div3">
                      
! <h4><a name="wsdl20inonly"></a>5.2.1 In-only</h4>
                      <p>This is a straightforward one-way message. No responses are expected but
                          related messages could be sent as part of other message exchanges.</p>
                      <table border="1">
!                         <caption>Table 5-4. Message addressing properties for in message.</caption>
                          <tbody>
                              <tr>
***************
*** 862,871 ****
                  <div class="div3">
                      
! <h4><a name="wsdl20robustinonly"></a>4.2.2 Robust In-only</h4>
                      <p> This one-way MEP allows fault messages. The [message id] property is needed
                          in the initial message in order to be able to correlate any fault with that
                          message. </p>
                      <table border="1">
!                         <caption>Table 4-5. Message addressing properties for in message.</caption>
                          <tbody>
                              <tr>
--- 970,979 ----
                  <div class="div3">
                      
! <h4><a name="wsdl20robustinonly"></a>5.2.2 Robust In-only</h4>
                      <p> This one-way MEP allows fault messages. The [message id] property is needed
                          in the initial message in order to be able to correlate any fault with that
                          message. </p>
                      <table border="1">
!                         <caption>Table 5-5. Message addressing properties for in message.</caption>
                          <tbody>
                              <tr>
***************
*** 921,925 ****
                              also be required ?</td></tr></table>
                      <table border="1">
!                         <caption>Table 4-6. Message addressing properties for fault message.</caption>
                          <tbody>
                              <tr>
--- 1029,1033 ----
                              also be required ?</td></tr></table>
                      <table border="1">
!                         <caption>Table 5-6. Message addressing properties for fault message.</caption>
                          <tbody>
                              <tr>
***************
*** 979,987 ****
                  <div class="div3">
                      
! <h4><a name="wsdl20inout"></a>4.2.3 In-out</h4>
                      <p> This is a two-way MEP. A reply is expected hence mandating [reply endpoint]
                          in the request message. The response message might be a fault. </p>
                      <table border="1">
!                         <caption>Table 4-7. Message addressing properties for in message.</caption>
                          <tbody>
                              <tr>
--- 1087,1095 ----
                  <div class="div3">
                      
! <h4><a name="wsdl20inout"></a>5.2.3 In-out</h4>
                      <p> This is a two-way MEP. A reply is expected hence mandating [reply endpoint]
                          in the request message. The response message might be a fault. </p>
                      <table border="1">
!                         <caption>Table 5-7. Message addressing properties for in message.</caption>
                          <tbody>
                              <tr>
***************
*** 1035,1039 ****
                      </table><br>
                      <table border="1">
!                         <caption>Table 4-8. Message addressing properties for out message.</caption>
                          <tbody>
                              <tr>
--- 1143,1147 ----
                      </table><br>
                      <table border="1">
!                         <caption>Table 5-8. Message addressing properties for out message.</caption>
                          <tbody>
                              <tr>
***************
*** 1091,1127 ****
                  <div class="div3">
                      
! <h4><a name="wsdl20inoptionalout"></a>4.2.4 In-optional-out</h4>
                      <p> This MEP differs from the In-out MEP in that the subsequent message is
                          optional. This difference doesn't affect the message properties so the
!                         properties defined in <a href="#wsdl20inout"><b>4.2.3 In-out</b></a> apply to this MEP also
                      </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20outonly"></a>4.2.5 Out-only</h4>
                      <p> From the WS-Addressing perspective this MEP is the same as In-only. The
!                         properties defined in <a href="#wsdl20inonly"><b>4.2.1 In-only</b></a> apply to this MEP also.
                      </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20robustoutonly"></a>4.2.6 Robust Out-only</h4>
                      <p> From the WS-Addressing perspective this MEP is the same as Robust In-only.
!                         The properties defined in <a href="#wsdl20robustinonly"><b>4.2.2 Robust In-only</b></a> apply to this
                          MEP also. </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20outin"></a>4.2.7 Out-in</h4>
                      <p> From the WS-Addressing perspective this MEP is the same as In-out. The
!                         properties defined in <a href="#wsdl20inout"><b>4.2.3 In-out</b></a> apply to this MEP also.
                      </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20outoptionalin"></a>4.2.8 Out-optional-in</h4>
                      <p>This MEP differs from the Out-in MEP in that the subsequent message is
                          optional. This difference doesn't affect the message properties so the
!                         properties defined in <a href="#wsdl20inout"><b>4.2.3 In-out</b></a> apply to this MEP
                      also</p>
                  </div>
--- 1199,1235 ----
                  <div class="div3">
                      
! <h4><a name="wsdl20inoptionalout"></a>5.2.4 In-optional-out</h4>
                      <p> This MEP differs from the In-out MEP in that the subsequent message is
                          optional. This difference doesn't affect the message properties so the
!                         properties defined in <a href="#wsdl20inout"><b>5.2.3 In-out</b></a> apply to this MEP also
                      </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20outonly"></a>5.2.5 Out-only</h4>
                      <p> From the WS-Addressing perspective this MEP is the same as In-only. The
!                         properties defined in <a href="#wsdl20inonly"><b>5.2.1 In-only</b></a> apply to this MEP also.
                      </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20robustoutonly"></a>5.2.6 Robust Out-only</h4>
                      <p> From the WS-Addressing perspective this MEP is the same as Robust In-only.
!                         The properties defined in <a href="#wsdl20robustinonly"><b>5.2.2 Robust In-only</b></a> apply to this
                          MEP also. </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20outin"></a>5.2.7 Out-in</h4>
                      <p> From the WS-Addressing perspective this MEP is the same as In-out. The
!                         properties defined in <a href="#wsdl20inout"><b>5.2.3 In-out</b></a> apply to this MEP also.
                      </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20outoptionalin"></a>5.2.8 Out-optional-in</h4>
                      <p>This MEP differs from the Out-in MEP in that the subsequent message is
                          optional. This difference doesn't affect the message properties so the
!                         properties defined in <a href="#wsdl20inout"><b>5.2.3 In-out</b></a> apply to this MEP
                      also</p>
                  </div>
***************
*** 1130,1134 ****
          <div class="div1">
              
! <h2><a name="references"></a>5.  References</h2>
              <dl>
                  <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
--- 1238,1242 ----
          <div class="div1">
              
! <h2><a name="references"></a>6.  References</h2>
              <dl>
                  <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
***************
*** 1152,1157 ****
                      <cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup Language (XML) 1.0 (Third Edition)</a></cite>, T.
                      Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
!                     Consortium, 4 February 2004. This version of the XML
!                     1.0 Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The <a href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</a> is
                      available at http://www.w3.org/TR/REC-xml. </dd>
                  <dt class="label"><a name="XMLNS"></a>[XML Namespaces] </dt><dd>
--- 1260,1265 ----
                      <cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup Language (XML) 1.0 (Third Edition)</a></cite>, T.
                      Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
!                     Consortium, 4 February 2004. This version of the XML 1.0 Recommendation is
!                     http://www.w3.org/TR/2004/REC-xml-20040204. The <a href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</a> is
                      available at http://www.w3.org/TR/REC-xml. </dd>
                  <dt class="label"><a name="XMLNS"></a>[XML Namespaces] </dt><dd>
***************
*** 1162,1182 ****
                          XML</a> is available at http://www.w3.org/TR/REC-xml-names. </dd>
                  <dt class="label"><a name="XMLInfoSet"></a>[XML Information Set] </dt><dd>
!                     <cite><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20011024">XML Information Set</a></cite>, J. Cowan and R. Tobin, Editors. World
!                     Wide Web Consortium, 24 October 2001. This version of the XML Information Set
!                     Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The <a href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
                          Set</a> is available at http://www.w3.org/TR/xml-infoset. </dd>
                  <dt class="label"><a name="XMLSchemaP1"></a>[XML Schema Structures] </dt><dd>
!                     <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema Part 1: Structures Second Edition</a></cite>, H. Thompson, D. Beech, M.
!                     Maloney, and N. Mendelsohn, Editors. World Wide
! 		    Web Consortium, 28 October 2004. This
!                     version of the XML Schema Part 1 Recommendation is
                      http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
                      1</a> is available at http://www.w3.org/TR/xmlschema-1. </dd>
                  <dt class="label"><a name="XMLSchemaP2"></a>[XML Schema Datatypes] </dt><dd>
!                     <cite><a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20041028/">XML Schema Part 2: Datatypes Second Edition</a></cite>, P. Byron and A. Malhotra,
!                     Editors. World Wide Web Consortium, 28 October 2004. This version of the XML Schema
!                     Part 2 Recommendation is http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The
!                         <a href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
!                         Part 2</a> is available at http://www.w3.org/TR/xmlschema-2. </dd>
                  <dt class="label"><a name="SOAP12-PART1"></a>[SOAP 1.2 Part 1: Messaging Framework] </dt><dd>
                      <cite><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">SOAP Version 1.2 Part 1: Messaging Framework</a></cite>, M. Gudgin, M.
--- 1270,1290 ----
                          XML</a> is available at http://www.w3.org/TR/REC-xml-names. </dd>
                  <dt class="label"><a name="XMLInfoSet"></a>[XML Information Set] </dt><dd>
!                     <cite><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/">XML Information Set (Second Edition)</a></cite>, J. Cowan and R.
!                     Tobin, Editors. World Wide Web Consortium, 4 February 2004. This version of the
!                     XML Information Set Recommendation is
!                     http://www.w3.org/TR/2004/REC-xml-infoset-20040204/. The <a href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
                          Set</a> is available at http://www.w3.org/TR/xml-infoset. </dd>
                  <dt class="label"><a name="XMLSchemaP1"></a>[XML Schema Structures] </dt><dd>
!                     <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema Part 1: Structures Second Edition</a></cite>, H. Thompson,
!                     D. Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 28
!                     October 2004. This version of the XML Schema Part 1 Recommendation is
                      http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
                      1</a> is available at http://www.w3.org/TR/xmlschema-1. </dd>
                  <dt class="label"><a name="XMLSchemaP2"></a>[XML Schema Datatypes] </dt><dd>
!                     <cite><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema Part 2: Datatypes Second Edition</a></cite>, P. Byron and
!                     A. Malhotra, Editors. World Wide Web Consortium, 28 October 2004. This version
!                     of the XML Schema Part 2 Recommendation is
!                     http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema Part
!                     2</a> is available at http://www.w3.org/TR/xmlschema-2. </dd>
                  <dt class="label"><a name="SOAP12-PART1"></a>[SOAP 1.2 Part 1: Messaging Framework] </dt><dd>
                      <cite><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">SOAP Version 1.2 Part 1: Messaging Framework</a></cite>, M. Gudgin, M.
***************
*** 1214,1228 ****
              <div class="div2">
                  
! <h3><a name="N10AB1"></a>B.1 Changes Since Second Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added reolution to issue 45</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10ABB"></a>B.2 Changes Since First Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Swtched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10AC5"></a>B.3 Changes Since Submission</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
  Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
--- 1322,1336 ----
              <div class="div2">
                  
! <h3><a name="N10B29"></a>B.1 Changes Since Second Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 16:11</td><td>mhadley</td><td>Incorporated resoluion to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added resolution to issue 45</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10B33"></a>B.2 Changes Since First Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Swtched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10B3D"></a>B.3 Changes Since Submission</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
  Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
Received on Friday, 22 April 2005 22:39:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:40 GMT