W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > January to March 2006

2004/ws/addressing ws-addr-wsdl.html,1.37,1.38

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 13 Mar 2006 13:56:05 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1FInWn-0008Cp-TZ@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-wsdl.html 
Log Message:
Sync with XML after applying the resolutions of LC109, LC110, LC111, LC113.

Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.37
retrieving revision 1.38
diff -C2 -d -r1.37 -r1.38
*** ws-addr-wsdl.html	3 Mar 2006 14:11:11 -0000	1.37
--- ws-addr-wsdl.html	13 Mar 2006 13:56:03 -0000	1.38
***************
*** 1,3 ****
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
  <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - WSDL Binding</title><style type="text/css">
  code           { font-family: monospace; }
--- 1,3 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - WSDL Binding</title><style type="text/css">
  code           { font-family: monospace; }
***************
*** 45,49 ****
  div.exampleHeader { font-weight: bold;
                      margin: 4px}
! </style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="alternate" title="" href="" type=""><link rel="contents" href="#contents"></head><body>
      <div class="head">
  <h1>Web Services Addressing 1.0 - WSDL Binding</h1>
--- 45,49 ----
  div.exampleHeader { font-weight: bold;
                      margin: 4px}
! </style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link type="" href="" title="" rel="alternate"><link href="#contents" rel="contents"></head><body>
      <div class="head">
  <h1>Web Services Addressing 1.0 - WSDL Binding</h1>
***************
*** 68,73 ****
          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="#indicatinguse">Indicating Use of WS-Addressing</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#N66024">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#N66188">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#N66206">Other Uses of UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#anonelement"> Anonymous Element </a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbs;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#N66289">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#N66308">WSDL SOAP Module</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#destinwsdl">Destination</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#actioninwsdl">Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#explicitaction">Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.3 <a href="#N66645">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.3 <a href="#refpinwsdl">Reference Parameters</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbs;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="#wsdl20inout">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;&nsp;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 name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#actioncompatibility">Compatibility of [action] with previous versions of WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#N68778">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N68788">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N68798">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N68808">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
--- 68,73 ----
          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="#indicatinguse">Indicating Use of WS-Addressing</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#N101E8">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#N1028C">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#N1029E">Other Uses of UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#anonelement"> Anonymous Element </a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbs;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#N102F1">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#wsdlsoapmodule">WSDL SOAP Module</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#destinwsdl">Destination</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#actioninwsdl">Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#explicitaction">Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.3 <a href="#N10456">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.3 <a href="#refpinwsdl">Reference Parameters</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nsp;&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="#wsdl20inout">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="#actioncompatibility">Compatibility of [action] with previous versions of WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#N10CAE">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N10CB8">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N10CC2">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N10CCC">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 212,216 ****
                      "http://example.com/fabrikam/acct". Note the use of the WSDL[<cite><a href="#WSDL20">WSDL 2.0</a></cite>] wsdlLocation attribute.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 212,216 ----
                      "http://example.com/fabrikam/acct". Note the use of the WSDL[<cite><a href="#WSDL20">WSDL 2.0</a></cite>] wsdlLocation attribute.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 251,255 ****
                      an embedded description is undefined.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 251,255 ----
                      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>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 285,289 ****
                  </div>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-3. </span>An EPR containing WSDL 1.1 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 285,289 ----
                  </div>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 2-3. </span>An EPR containing WSDL 1.1 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 323,327 ****
              <div class="div2">
                  
! <h3><a name="N66024"></a>3.1 UsingAddressing Extension Element</h3>
                  <p>
                      WS-Addressing defines an empty global element,
--- 323,327 ----
              <div class="div2">
                  
! <h3><a name="N101E8"></a>3.1 UsingAddressing Extension Element</h3>
                  <p>
                      WS-Addressing defines an empty global element,
***************
*** 401,405 ****
                      binding. </p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><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"
--- 401,405 ----
                      binding. </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"
***************
*** 413,417 ****
                  </div>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><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;
--- 413,417 ----
                  </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;
***************
*** 430,440 ****
                  <div class="div3">
                      
! <h4><a name="N66188"></a>3.1.1 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
                          component model:</p>
                      <ul>
                          <li>
!                             <p>A property of the binding or endpoint named {addressing required} of
!                                 type xs:boolean. The property value is the value of the
                                  wsdl:required attribute information item on the wsaw:UsingAddressing
                                  extension element, if present; otherwise "false".</p>
--- 430,440 ----
                  <div class="div3">
                      
! <h4><a name="N1028C"></a>3.1.1 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
                          component model:</p>
                      <ul>
                          <li>
!                             <p>A property {addressing required} of type xs:boolean, to the
!                                 Binding and Endpoint components. The property value is the value of the
                                  wsdl:required attribute information item on the wsaw:UsingAddressing
                                  extension element, if present; otherwise "false".</p>
***************
*** 444,448 ****
                  <div class="div3">
                      
! <h4><a name="N66206"></a>3.1.2 Other Uses of UsingAddressing Extension Element</h4>
                      <p>The wsaw:UsingAddressing element may also be used in other contexts  
                          (e.g., as a policy assertion in a policy framework). Its use  
--- 444,448 ----
                  <div class="div3">
                      
! <h4><a name="N1029E"></a>3.1.2 Other Uses of UsingAddressing Extension Element</h4>
                      <p>The wsaw:UsingAddressing element may also be used in other contexts  
                          (e.g., as a policy assertion in a policy framework). Its use  
***************
*** 521,525 ****
                 binding operation extension element in WSDL 2.0.</p>
                 <div class="exampleOuter">
! 	           <p style="text-align: left" class="exampleHead"><i><span>Example 3-3. </span> Indicating use of anonymous addresses using wsaw:Anonymous. </i></p>
  		   <div class="exampleInner"><pre>&lt;binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"&gt;
  &nbsp; &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
--- 521,525 ----
                 binding operation extension element in WSDL 2.0.</p>
                 <div class="exampleOuter">
! 	           <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span> Indicating use of anonymous addresses using wsaw:Anonymous. </i></p>
  		   <div class="exampleInner"><pre>&lt;binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"&gt;
  &nbsp; &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
***************
*** 541,545 ****
                 <div class="div3">
                     
! <h4><a name="N66289"></a>3.2.1 WSDL 2.0 Component Model Changes</h4>
  		   <p>Use of the Anonymous element adds the following REQUIRED properties to the WSDL 2.0 component model: </p>
                     <ul>
--- 541,545 ----
                 <div class="div3">
                     
! <h4><a name="N102F1"></a>3.2.1 WSDL 2.0 Component Model Changes</h4>
  		   <p>Use of the Anonymous element adds the following REQUIRED properties to the WSDL 2.0 component model: </p>
                     <ul>
***************
*** 552,565 ****
              <div class="div2">
                  
! <h3><a name="N66308"></a>3.3 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/2005/08/addressing/module</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-4. </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"
--- 552,566 ----
              <div class="div2">
                  
! <h3><a name="wsdlsoapmodule"></a>3.3 WSDL SOAP Module</h3>
!                 <p> In WSDL 2.0, a SOAP Module component may be used to declare the use of the
!                     WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a
!                     SOAP Module component is semantically equivalent to the {addressing required}
!                     property defined in section 3.1.1. Note that this module is only meaningful when
!                     used on WSDL components where the {addressing required} property is allowed,
!                     i.e. as a member of the {soap modules} property of a Binding component.</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/2005/08/addressing/module</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </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"
***************
*** 633,637 ****
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><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;description targetNamespace="http://example.com/stockquote" ...&gt;
--- 634,638 ----
                      <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;description targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 653,657 ****
                          http://example.com/Quote.</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><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;
--- 654,658 ----
                          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;
***************
*** 681,685 ****
                          general form of an action URI is as follows:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><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]
--- 682,686 ----
                          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]
***************
*** 688,692 ****
                      <p>For fault messages, the general form of an action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><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]
--- 689,693 ----
                      <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]
***************
*** 777,781 ****
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
--- 778,782 ----
                      <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>
***************
*** 805,809 ****
                  <div class="div3">
                      
! <h4><a name="N66645"></a>4.2.3 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
                          component model:</p>
--- 806,810 ----
                  <div class="div3">
                      
! <h4><a name="N10456"></a>4.2.3 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
                          component model:</p>
***************
*** 827,831 ****
                          action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><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]
--- 828,832 ----
                          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]
***************
*** 834,838 ****
                      <p>For fault messages, the general form of an action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><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][delimiter]Fault[delimiter][fault name]
--- 835,839 ----
                      <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][delimiter]Fault[delimiter][fault name]
***************
*** 889,893 ****
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-8. </span>Example WSDL without explicit wsa:Action values with explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
--- 890,894 ----
                      <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>
***************
*** 918,922 ****
                          is not present. Consider the following example:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-9. </span>Example WSDL without explicit wsa:Action values or explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
--- 919,923 ----
                          is 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>
***************
*** 1256,1260 ****
                              <tr>
                                  <td rowspan="1" colspan="1">[reply endpoint]</td>
!                                 <td align="center" rowspan="1" colspan="1">N</td>
                                  <td rowspan="1" colspan="1">Intended receiver for replies to this message. Unused in this
                                      MEP, but may be included to facilitate longer running message
--- 1257,1261 ----
                              <tr>
                                  <td rowspan="1" colspan="1">[reply endpoint]</td>
!                                 <td align="center" rowspan="1" colspan="1">N*</td>
                                  <td rowspan="1" colspan="1">Intended receiver for replies to this message. Unused in this
                                      MEP, but may be included to facilitate longer running message
***************
*** 1263,1267 ****
                              <tr>
                                  <td rowspan="1" colspan="1">[fault endpoint]</td>
!                                 <td align="center" rowspan="1" colspan="1">N</td>
                                  <td rowspan="1" colspan="1">Intended receiver for faults related to this message.</td>
                              </tr>
--- 1264,1268 ----
                              <tr>
                                  <td rowspan="1" colspan="1">[fault endpoint]</td>
!                                 <td align="center" rowspan="1" colspan="1">N*</td>
                                  <td rowspan="1" colspan="1">Intended receiver for faults related to this message.</td>
                              </tr>
***************
*** 1281,1284 ****
--- 1282,1287 ----
                          </tbody>
                      </table><br>
+                     <p>* Note that at least one of [fault endpoint] or [reply endpoint] is required
+                         for this MEP, so that a fault can be sent if necessary.</p>
                      <table border="1">
                          <caption>Table 5-6. Message addressing properties for fault message.</caption>
***************
*** 1618,1637 ****
              <div class="div2">
                  
! <h3><a name="N68778"></a>C.1 Changes Since Third Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-11-22 @ 21:29</td><td>mhadley</td><td>Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model</td></tr><tr><td>2005-11-07 @ 07:08</td><td>mhadley</td><td>Added resolution to issue 65, [action] defaults to same as SOAPAction in absence of wsaw:Action</td></tr><tr><td>2005-11-07 @ 06:44</td><td>mhadley</td><td>Updated resolution to issues 56, 57</td></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)/td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new sectin in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N68788"></a>C.2 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="N68798"></a>C.3 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="N68808"></a>C.4 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>
--- 1621,1640 ----
              <div class="div2">
                  
! <h3><a name="N10CAE"></a>C.1 Changes Since Third Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-03-13 @ 13:30</td><td>trogers</td><td>Added the resolution of LC113: clarifying section 3.3 WSDL SOAP module.</td></tr><tr><td>2006-03-13 @ 13:19</td><td>trogers</td><td>Added the resolution of LC111: clarifying the {addressing required} property.</td></tr><tr><td>2006-03-13 @ 13:03</td><td>trogers</td><td>Altered changelog limit from start of 2006 to end of 2006.</td></tr><tr><td>2006-03-13 @ 12:59</td><td>trogers</td><td>Added resolution of LC109: specify that at least one of reply or fault endpoint is required on Robust In-Only</td></tr><tr><td>2006-03-03 @ 14:10</td><td>mhadley</td><td>Fixed editor list in references</td></tr><tr><td>2006-03-03 @ 13:48</td><td>mhadley</td><td>Added resolution to LC115 - definition to description for WSDL 2.0</td></tr><tr><td>2006-03-03 @ 13:45</td><td>mhadley</td><td>Added resolution to LC114 - typos</td></tr><tr><td>2006-02-22 @ 14:22</td><td>mhadley</td><td>Fixed  typo: 'by by' to 'by'</td></tr><tr><td>2006-02-13 @ 20:15</td><td>mhadley</td><td>Removed ed notes</td></tr><tr><td>2006-02-13 @ 16:56</td><td>mhadley</td><td>A few grammar fixes and noted that wsaw:Anonymous with a value of optional is equivalent to the default.</td></tr><tr><td>2006-02-13 @ 16:45</td><td>mhadley</td><td>Added resolution to issue 70, soften language on defining value of [destination] to allow runtime override.</td></tr><tr><td>2006-02-13 @ 15:50</td><td>mhadley</td><td>Added resolution to issue 66, explicit note that wsaw:UsingAddressing could be used outside WSDL, e.g. in a policy framework</td></tr><tr><td>2006-01-19 @ 20:37</td><td>mhadley</td><td>Fixed some grammar errors</td></tr><tr><td>2006-01-08 @ 23:14</td><td>trogers</td><td>Umit's description of the Anonymous element added; Umit added to editor list.</td></tr><tr><td>2005-11-22 @ 21:29</td><td>mhadley</td><td>Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model</td><tr><tr><td>2005-11-07 @ 07:08</td><td>mhadley</td><td>Added resolution to issue 65, [action] defaults to same as SOAPAction in absence of wsaw:Action</td></tr><tr><td>2005-11-07 @ 06:44</td><td>mhadley</td><td>Updated resolution to issues 56, 57</td></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in examle fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley<td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10CB8"></a>C.2 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="N10CC2"></a>C.3 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="N10CCC"></a>C.4 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 Monday, 13 March 2006 13:56:28 GMT

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