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

2004/ws/addressing ws-addr-wsdl.html,1.50,1.51

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 14 Jan 2007 20:34:31 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1H6C3j-0006VO-OY@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-wsdl.html 
Log Message:
Updated to show the candidate new version (removing UsingAddressing and SOAP module)

Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.50
retrieving revision 1.51
diff -C 2 -d -r1.50 -r1.51
*** ws-addr-wsdl.html	10 Jan 2007 11:33:21 -0000	1.50
--- ws-addr-wsdl.html	14 Jan 2007 20:34:29 -0000	1.51
***************
*** 71,76 ****
          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="#uaee">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#wsdl20_usingaddressing">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#wspolicyassertions">WS-Policy Assertions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#wspolicyaddressing">Addressing Assertion</a><br>&nbsp;&nbsp;&nbsp;&nbp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.2 <a href="#wspolicyanonresponses">AnonymousResponses Assertion</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.3 <a href="#wspolicynonanonresponses">NonAnonymousResponses Assertion</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.4 <a href="#N10336">Using both AnonymousResponses and NonAnonymousResponses</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.5 <a href="#N10345">Examples (Compact Form)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.6 <a href="#N1037D">Examples (Normal Form)</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="#eprinendpoint">Extending WSDL Endpoints with an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#N103E6">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#destinwsdl">Destination</a><br>&nbsp;&nbs;&nbsp;&nbsp;4.3 <a href="#refpinwsdl">Reference Parameters</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.4 <a href="#actioninwsdl">Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.4.1 <a href="#explicitaction">Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.4.3 <a href="#N1053A">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.4.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;&nbp;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="#wsdl2outoptionalin">Out-optional-in</a><br>6. <a href="#conformance">Conformance</a><br>7. <a href="#references"> References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#N10C2B">Normative</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.2 <a href="#N10D9C">Informative</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="#N10E2A">Changes Since Candidate Recommendation Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N10E34">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N10E3E">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N10E48">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.5 <a href="#N10E52">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.6 <a href="#N10E5C">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
--- 71,76 ----
          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="#wspolicyassertions">WS-Policy Assertions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#wspolicyaddressing">Addressing Assertion</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#wspolicyanonresponses">AnonymousResponses Assertion</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.3 <a href="#wspolicynonanonresponses">NonAnonymousResponsesAssertion</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.4 <a href="#N10259">Using both AnonymousResponses and NonAnonymousResponses</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.5 <a href="#N10268">Examples (Compact Form)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.6 <a href="#N102A0">Examples (Normal Form)</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#eprinendpoint">Extending WSDL Endpoints with an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#N102EC">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#destinwsdl">Destination</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.3 <a href="#refpinwsdl">Reference Parameters</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.4 <a href="#actioninwsdl">Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.4.1 <a href="#explicitaction">Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;44.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.4.3 <a href="#N10440">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.4.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="#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="#conformance">Conformance</a><br>7. <a href="#references"> References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.1 <a href="#N10B2E">Normative</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.2 <a href="#N10C9F">Informative</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="#N10D2D">Changes Since Candidate Recommendation Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N10D37">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N10D41">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N10D4B">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.5 <a href="#N10D55">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.6 <a href="#N10D5F">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 317,450 ****
              
  <h2><a name="indicatinguse"></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="uaee"></a>3.1 <code>UsingAddressing</code>  Extension Element</h3>
!                 <p> WS-Addressing defines an empty global element, wsam:UsingAddressing, that can 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. <a href="#mappresence">Table 3-1</a> outlines the requirements on messages
!                     sent from an endpoint based on the contents of any preceding input message and
!                     how the use of addressing is indicated in the WSDL. </p>
!                 <a name="mappresence"></a><table border="1">
!                     <caption>Table 3-1. MAPs Present in output message when wsam:UsingAddressing is present</caption>
!                     <thead>
!                         <tr>
!                             <th rowspan="1" colspan="1">MAPs in Input message</th>
!                             <th rowspan="1" colspan="1">wsdl:required="true" {addressing}=required</th>
!                             <th rowspan="1" colspan="1">wsdl:required="false" {addressing}=optional</th>
!                         </tr>
!                     </thead>
!                     <tbody>
!                         <tr>
!                             <td rowspan="1" colspan="1">Yes</td>
!                             <td rowspan="1" colspan="1">REQUIRED</td>
!                             <td rowspan="1" colspan="1">REQUIRED</td>
!                         </tr>
!                         <tr>
!                             <td rowspan="1" colspan="1">No</td>
!                             <td rowspan="1" colspan="1">Fault</td>
!                             <td rowspan="1" colspan="1">OPTIONAL. If using SOAP, MAP headers MUST NOT have a
!                                 soap:mustUnderstand attribute with a value of "true"</td>
!                         </tr>
!                     </tbody>
!                 </table><br>
!                 <p>If WS-A is engaged, use of the message addressing properties MUST be fully
!                     compliant with this specification; in particular, senders MUST use all message
!                     addressing properties mandated by the Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing Core</a></cite>], applicable WS-Addressing protocol bindings (e.g.
!                         Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing SOAP Binding</a></cite>]), and this specification,
!                     and MUST follow all applicable WS-Addressing normative requirements. </p>
!                 <p>The wsam:UsingAddressing element SHOULD appear as a child of the wsdl:binding
!                     element. Alternatively, the wsam: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 wsam:UsingAddressing element indicates that the applicable
!                     WS-Addressing specifications are supported and allows use of anonymous or
!                     non-anonymous URIs as addresses in an EPR. Specifically, when included in a SOAP
!                     binding, the wsam: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 Binding</a></cite>].The presence of this element can extend the semantics
!                     of the endpoint's WSDL binding. </p>
!                 <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsam:UsingAddressing in WSDL 2.0</i></p>
!                     <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
!     interface="tns:reservationInterface"
!     type="http://www.w3.org/2006/01/wsdl/soap"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
!   &lt;wsam: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 wsam:UsingAddressing in WSDL 1.1</i></p>
!                     <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding"
!                         type="tns:reservationInterface"&gt;
!   &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
!   &lt;wsam:UsingAddressing wsdl:required="true" /&gt;
!   &lt;operation name="opCheckAvailability"&gt;
!     &lt;soap:operation soapaction="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability" /&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 class="div3">
!                     
! <h4><a name="wsdl20_usingaddressing"></a>3.1.1 WSDL 2.0 Component Model Changes</h4>
!                     <p>Use of WS-Addressing adds the following property to the WSDL 2.0 component
!                         model:</p>
!                     <ul>
!                         <li>
!                             <p>{addressing} OPTIONAL, of type <code>xs:token</code> with one of the
!                                 values "required" or "optional", to
!                                 the Binding and Endpoint components. When present, the property
!                                 indicates that the use of addressing has been declared. </p>
!                         </li>
!                     </ul>
!                     <p><a href="#tab_addressing_Mapping">Table 3-2</a> shows the mapping from the XML
!                         representation to the WSDL 2.0 component model.</p>
!                     <a name="tab_addressing_Mapping"></a><table border="1">
!                         <caption>Table 3-2. Mapping from XML Representation to Binding and Endpoint components
!                             Extension Properties</caption>
!                         <tbody>
!                             <tr>
!                                 <th rowspan="1" colspan="1">Property</th>
!                                 <th rowspan="1" colspan="1">Value</th>
!                             </tr>
!                             <tr>
!                                 <td rowspan="1" colspan="1">{addressing}</td>
!                                 <td rowspan="1" colspan="1"> If a <code>wsam:UsingAddresing</code>  extension element is present: <ul>
!                                         <li>
!                                             <p>if a <code>wsdl:required</code>  <em>attribute information item</em> is present
!                                                 and has a value of "true", then
!                                                   "required"</p>
!                                         </li>
!                                         <li>
!                                             <p>otherwise "optional"</p>
!                                         </li>
!                                     </ul>
!                                 </td>
!                             </tr>
!                         </tbody>
!                     </table><br>
!                     <p><a href="#mappresence">Table 3-1</a> summarizes the meaning of the property as
!                         detailed in section <a href="#uaee"><b>3.1 UsingAddressing Extension Element</b></a>.</p>
!                 </div>
!             </div>
              <div class="div2">
                  
! <h3><a name="wspolicyassertions"></a>3.2 WS-Policy Assertions</h3>
                  <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right">&nbsp;</td></tr><tr><td valign="top" align="left" colspan="2">open issue on policy attachment options</td></tr></table>
!                 <p>Another mechanism for indicating that a binding or endpoint  conforms to the WS-Addressing specification is through the use of the
!                     Web Services Policy - Framework [<cite><a href="#WSPolicy">WS Policy 1.5 - Framework</a></cite>] and Web Services
!                     Policy - Attachment [<cite><a href="#WSPolicyAttachment">WS Policy 1.5 - Attachment</a></cite>] specifications. This
!                     specification defines three policy assertions.</p>
                  <p>For WSDL 1.1, these assertions may be attached to <code>wsdl11:port</code> or
                      <code>wsdl11:binding</code>. For WSDL 2.0, they may be attached to
--- 317,332 ----
              
  <h2><a name="indicatinguse"></a>3. Indicating Use of WS-Addressing</h2>
!             <p>This specification supports a mechanism for indicating, in a WSDL description, that
!                 the endpoint conforms to the WS-Addressing specification. That mechanism uses
!                 WS-Policy Framework [<cite><a href="#WSPolicy">WS Policy 1.5 - Framework</a></cite>].</p>
              <div class="div2">
                  
! <h3><a name="wspolicyassertions"></a>3.1 WS-Policy Assertions</h3>
                  <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right">&nbsp;</td></tr><tr><td valign="top" align="left" colspan="2">open issue on policy attachment options</td></tr></table>
!                 <p>The mechanism for indicating that a binding or endpoint conforms to the
!                     WS-Addressing specification is through the use of the Web Services Policy -
!                     Framework [<cite><a href="#WSPolicy">WS Policy 1.5 - Framework</a></cite>] and Web Services Policy - Attachment
!                         [<cite><a href="#WSPolicyAttachment">WS Policy 1.5 - Attachment</a></cite>] specifications. This specification
!                     defines three policy assertions.</p>
                  <p>For WSDL 1.1, these assertions may be attached to <code>wsdl11:port</code> or
                      <code>wsdl11:binding</code>. For WSDL 2.0, they may be attached to
***************
*** 452,467 ****
                  <div class="div3">
                      
! <h4><a name="wspolicyaddressing"></a>3.2.1 Addressing Assertion</h4>
                      <p>The wsam:Addressing policy assertion is a nested policy container assertion.
!                         The meaning of this assertion when present in a policy alternative is that
                          WS-Addressing is required to communicate with the subject. In order to
                          indicate that the subject supports WS-Addressing but does not require its
                          use, an additional policy alternative should be provided which does not
                          contain this assertion. This may be done in WS-Policy compact form by adding
!                         the attribute wsp:Optional="true" to the Addressing assertion. </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wspolicyanonresponses"></a>3.2.2 AnonymousResponses Assertion</h4>
                      <p>The wsam:AnonymousResponses element MAY be used as a policy assertion nested
                          within the wsam:Addressing assertion in accordance with the rules laid down
--- 334,349 ----
                  <div class="div3">
                      
! <h4><a name="wspolicyaddressing"></a>3.1.1 Addressing Assertion</h4>
                      <p>The wsam:Addressing policy assertion is a nested policy container assertion.
!                         The meaning of this assertion, when present in a policy alternative, is that
                          WS-Addressing is required to communicate with the subject. In order to
                          indicate that the subject supports WS-Addressing but does not require its
                          use, an additional policy alternative should be provided which does not
                          contain this assertion. This may be done in WS-Policy compact form by adding
!                         the attribute wsp:Optional="true" to the wsam:Addressing assertion. </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wspolicyanonresponses"></a>3.1.2 AnonymousResponses Assertion</h4>
                      <p>The wsam:AnonymousResponses element MAY be used as a policy assertion nested
                          within the wsam:Addressing assertion in accordance with the rules laid down
***************
*** 475,482 ****
                          anonymous URI as an address; it simply indicates the lack of any affirmation
                          of support for anonymous URIs. </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wspolicynonanonresponses"></a>3.2.3 NonAnonymousResponses Assertion</h4>
                      <p>The wsam:NonAnonymousResponses element MAY be used as a policy assertion
                          nested within the Addressing assertion in accordance with the rules laid
--- 357,367 ----
                          anonymous URI as an address; it simply indicates the lack of any affirmation
                          of support for anonymous URIs. </p>
+                     <p>The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
+                         value of [address] in place of the anonymous URI; this value MUST be
+                         accepted.</p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wspolicynonanonresponses"></a>3.1.3 NonAnonymousResponses Assertion</h4>
                      <p>The wsam:NonAnonymousResponses element MAY be used as a policy assertion
                          nested within the Addressing assertion in accordance with the rules laid
***************
*** 493,500 ****
                          endpoint will not accept request messages with response endpoint EPRs that
                          contain something other than the anonymous URI address. </p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="N10336"></a>3.2.4 Using both AnonymousResponses and NonAnonymousResponses</h4>
                      <p>If both AnonymousResponses and NonAnonymousResponses are supported, and the
                          intention is to allow either to be used, care should be taken to ensure that
--- 378,387 ----
                          endpoint will not accept request messages with response endpoint EPRs that
                          contain something other than the anonymous URI address. </p>
+                     <p>The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
+                         value of [address] in place of a non-anonymous address; this value MUST be accepted.</p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="N10259"></a>3.1.4 Using both AnonymousResponses and NonAnonymousResponses</h4>
                      <p>If both AnonymousResponses and NonAnonymousResponses are supported, and the
                          intention is to allow either to be used, care should be taken to ensure that
***************
*** 512,518 ****
                  <div class="div3">
                      
! <h4><a name="N10345"></a>3.2.5 Examples (Compact Form)</h4>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing wsp:Optional="true"&gt;
--- 399,405 ----
                  <div class="div3">
                      
! <h4><a name="N10268"></a>3.1.5 Examples (Compact Form)</h4>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing wsp:Optional="true"&gt;
***************
*** 522,526 ****
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </span>Subject requires WS-Addressing, no statement on supported response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing&gt;
--- 409,413 ----
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Subject requires WS-Addressing, no statement on supported response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing&gt;
***************
*** 530,534 ****
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-5. </span>Subject supports WS-Addressing, explicitly (and optionally) supports anonymous and non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing wsp:Optional="true"&gt;
--- 417,421 ----
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span>Subject supports WS-Addressing, explicitly (and optionally) supports anonymous and non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing wsp:Optional="true"&gt;
***************
*** 541,545 ****
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-6. </span>Subject requires WS-Addressing, requires explicit support of anonymous or non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing&gt;
--- 428,432 ----
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </span>Subject requires WS-Addressing, requires explicit support of anonymous or non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing&gt;
***************
*** 554,558 ****
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-7. </span>Subject requires WS-Addressing and use of non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing&gt;
--- 441,445 ----
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-5. </span>Subject requires WS-Addressing and use of non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsam:Addressing&gt;
***************
*** 566,572 ****
                  <div class="div3">
                      
! <h4><a name="N1037D"></a>3.2.6 Examples (Normal Form)</h4>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-8. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
--- 453,459 ----
                  <div class="div3">
                      
! <h4><a name="N102A0"></a>3.1.6 Examples (Normal Form)</h4>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-6. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
***************
*** 585,589 ****
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-9. </span>Subject requires WS-Addressing, no statement on supported response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
--- 472,476 ----
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-7. </span>Subject requires WS-Addressing, no statement on supported response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
***************
*** 601,605 ****
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-10. </span>Subject supports WS-Addressing, explicitly (and optionally) supports anonymous and non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
--- 488,492 ----
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-8. </span>Subject supports WS-Addressing, explicitly (and optionally) supports anonymous and non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
***************
*** 652,656 ****
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-11. </span>Subject requires WS-Addressing, requires explicit support of anonymous or non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
--- 539,543 ----
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-9. </span>Subject requires WS-Addressing, requires explicit support of anonymous or non-anonymous response EPRs</i></p>
                          <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
***************
*** 681,685 ****
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-12. </span>Subject requires WS-Addressing and use of non-anonymous response EPRs</i></p>
  <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
--- 568,572 ----
                      </div>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 3-10. </span>Subject requires WS-Addressing and use of non-anonymous response EPRs</i></p>
  <div class="exampleInner"><pre>&lt;wsp:Policy&gt;
      &lt;wsp:ExactlyOne&gt;
***************
*** 700,729 ****
                  </div>                
              </div>
-             <div class="div2">
-                 
- <h3><a name="wsdlsoapmodule"></a>3.3 WSDL SOAP Module</h3>
-                 <p> In WSDL 2.0, a SOAP Module component can 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} property
-                     defined in section <a href="#wsdl20_usingaddressing"><b>3.1.1 WSDL 2.0 Component Model Changes</b></a>. Note that this
-                     module is only meaningful when used on WSDL components where the {addressing}
-                     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 Binding</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-13. </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/2006/01/wsdl/soap"
-     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
-   &lt;wsoap:module uri="http://www.w3.org/2005/08/addressing/module" required="true" /&gt;
-   &lt;operation ref="tns:opCheckAvailability"
-       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"&gt;
-   &lt;/operation&gt;
-   &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
- &lt;/binding&gt;</pre></div>
-                 </div>
-             </div>
          </div>
          <div class="div1">
--- 587,590 ----
***************
*** 746,750 ****
                  <div class="div3">
                      
! <h4><a name="N103E6"></a>4.1.1 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following OPTIONAL properties to the WSDL 2.0
                          component model:</p>
--- 607,611 ----
                  <div class="div3">
                      
! <h4><a name="N102EC"></a>4.1.1 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following OPTIONAL properties to the WSDL 2.0
                          component model:</p>
***************
*** 1000,1004 ****
                  <div class="div3">
                      
! <h4><a name="N1053A"></a>4.4.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>
--- 861,865 ----
                  <div class="div3">
                      
! <h4><a name="N10440"></a>4.4.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>
***************
*** 1683,1689 ****
                  obeys the structural constraints defined in that section.</p>
              <p> A WSDL description conforms to this specification when it incorporates directly or
!                 indirectly one or more of the <a href="#wspolicyassertions"><b>3.2 WS-Policy Assertions</b></a> or the <a href="#wsdlsoapmodule"><b>3.3 WSDL SOAP Module</b></a> markers, and obeys the structural constraints defined in
!                 section <a href="#indicatinguse"><b>3. Indicating Use of WS-Addressing</b></a> appropriate to that marker, and those defined
!                 in section <a href="#actioninwsdl"><b>4.4 Action</b></a>. </p>
              <p> An endpoint conforms to this specification if it has a conformant WSDL description
                  associated with it, and receives and emits messages in accordance with the
--- 1544,1550 ----
                  obeys the structural constraints defined in that section.</p>
              <p> A WSDL description conforms to this specification when it incorporates directly or
!                 indirectly the <a href="#wspolicyassertions"><b>3.1 WS-Policy Assertions</b></a> marker, and obeys the structural
!                 constraints defined in section <a href="#indicatinguse"><b>3. Indicating Use of WS-Addressing</b></a> appropriate to that
!                 marker, and those defined in section <a href="#actioninwsdl"><b>4.4 Action</b></a>. </p>
              <p> An endpoint conforms to this specification if it has a conformant WSDL description
                  associated with it, and receives and emits messages in accordance with the
***************
*** 1695,1699 ****
              <div class="div2">
                  
! <h3><a name="N10C2B"></a>7.1 Normative</h3>
                  <dl>
  		  <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
--- 1556,1560 ----
              <div class="div2">
                  
! <h3><a name="N10B2E"></a>7.1 Normative</h3>
                  <dl>
  		  <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
***************
*** 1798,1802 ****
              <div class="div2">
                  
! <h3><a name="N10D9C"></a>7.2 Informative</h3>
                  <dl>
                      <dt class="label"><a name="WSPolicyPrimer"></a>[WS Policy 1.5 - Primer] </dt><dd>
--- 1659,1663 ----
              <div class="div2">
                  
! <h3><a name="N10C9F"></a>7.2 Informative</h3>
                  <dl>
                      <dt class="label"><a name="WSPolicyPrimer"></a>[WS Policy 1.5 - Primer] </dt><dd>
***************
*** 1874,1904 ****
              <div class="div2">
                  
! <h3><a name="N10E2A"></a>C.1 Changes Since Candidate Recommendation Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2007-01-10 @ 11:26</td><td>trogers</td><td>Changed the namespace and namespace prefix for this document
  Corrected introduction and conformance section</td></tr><tr><td>2007-01-05 @ 14:20</td><td>trogers</td><td>Implemented the resolutions of CR33 and CR44: policy assertions for using addressing and anon/non-anon responses</td></tr><tr><td>2007-01-03 @ 12:28</td><td>trogers</td><td>Implemented the resolution of CR30 - SOAPAction not empty or absolute IRI makes the document invalid</td></tr><tr><td>2007-01-03 @ 11:38</td><td>trogers</td><td>Implemented CR26 and CR28 about the rules for populating the [action] property.</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10E34"></a>C.2 Changes Since Last Call Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-05-04 @ 12:33</td><td>mhadley</td><td>Split the references into normative and informative, fixed a few editorial glitches</td></tr><tr><td>2006-04-28 @ 15:09</td><td>mhadley</td><td>Added new change log section for LC issues</td></tr><tr><td>2006-04-28 @ 15:04</td><td>mhadley</td><td>Incorporated resolution to issue lc132 - reworked section 4 to allow use of EPRs as WSDL endpoint/port extensions</td></tr><tr><td>2006-04-28 @ 13:40</td><td>trogers</td><td>Implemented the resolution of LC131, simplifying table 3.1 to remove discussion of UsingAddressing not present.</td></tr><tr><td>2006-04-28 @ 13:25</td><td>trogers</td><td>Implemented the resolution of LC129, removing the default for wsaw:Anonymous</td></tr><tr><td>2006-04-28 @ 13:09</td><td>trogers</td><td>Implemented LC124, adding Conformance section.</td></tr><tr><td>2006-04-26 @ 15:34</td><td>mhadley</td><td>Added resolution of issue lc122 - added (..m) notation to wsaw:InterfaceName, wsaw:ServiceName and wsaw:ServiceName/@EndpointName descriptions</td></tr><tr><td>2006-04-26 @ 15:28</td><td>mhadley</td><td>Added resolution of issue lc123 - changed all the examples to be based on the one used in the WSDL 2.0 primer</td></tr><tr><td>2006-04-17 @ 10:27</td><td>trogers</td><td>Removed MUST from section 4.1 concerning the value of [destination] (LC130)</td></tr><tr><td>2006-04-17 @ 10:14</td><td>trogers</td><td>Marking UsingAddressing using &lt;el&gt; tag to show that it is not a typo in heading 3.1 (LC126)</td></tr><tr><td>2006-04-17 @ 10:05</td><td>trogers</td><td>Added the class of product specification to the Abstract (LC125)</td></tr><tr><td>2006-04-17 @ 09:46</td><td>trogers</td><td>Applied the changes required for LC120 - typo in intro and correcting wsa:Action/wsaw:Action.</td></tr><tr><td>2006-04-17 @ 09:34</td><td>trogers</td><td>Applied the changes required for LC119.</td></tr><tr><td>2006-04-17 @ 08:42</td><td>trogers</td><td>Changed the {refeence parameters} property from REQUIRED to OPTIONAL in the component model. This completes LC116.</td></tr><tr><td>2006-03-27 @ 19:48</td><td>mhadley</td><td>Used alternate words instead of lowercase RFC2119 terms</td></tr><tr><td>2006-03-20 @ 15:05</td><td>mhadley</td><td>Fixed a typo in example generated fault action</td></tr><tr><td>2006-03-15 @ 22:56</td><td>trogers</td><td>Implemented the resolution of LC116: added section describing the {reference parameters} property.</td></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 o 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 a typo: 'by by' to 'by'</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10E3E"></a>C.3 Changes Since Third Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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 imacts 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>005-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 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 editoria 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="N10E48"></a>C.4 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="N10E52"></a>C.5 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="N10E5C"></a>C.6 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>
--- 1735,1765 ----
              <div class="div2">
                  
! <h3><a name="N10D2D"></a>C.1 Changes Since Candidate Recommendation Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2007-01-14 @ 20:31</td><td>trogers</td><td>removed UsingAddressing and SOAP module, updated conformance to suit, added None URI as acceptable</td></tr><tr><td>2007-01-10 @ 11:26</td><td>trogers</td><td>Changed the namespace and namespace prefix for this document
  Corrected introduction and conformance section</td></tr><tr><td>2007-01-05 @ 14:20</td><td>trogers</td><td>Implemented the resolutions of CR33 and CR44: policy assertions for using addressing and anon/non-anon responses</td></tr><tr><td>2007-01-03 @ 12:28</td><td>trogers</td><td>Implemented the resolution of CR30 - SOAPAction not empty or absolute IRI makes the document invalid</td></tr><tr><td>2007-01-03 @ 11:38</td><td>trogers</td><td>Implemented CR26 and CR28 about the rules for populating the [action] property.</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10D37"></a>C.2 Changes Since Last Call Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-05-04 @ 12:33</td><td>mhadley</td><td>Split the references into normative and informative, fixed a few editorial glitches</td></tr><tr><td>2006-04-28 @ 15:09</td><td>mhadley</td><td>Added new change log section for LC issues</td></tr><tr><td>2006-04-28 @ 15:04</td><td>mhadley</td><td>Incorporated resolution to issue lc132 - reworked section 4 to allow use of EPRs as WSDL endpoint/port extensions</td></tr><tr><td>2006-04-28 @ 13:40</td><td>trogers</td><td>Implemented the resolution of LC131, simplifying table 3.1 to remove discussion of UsingAddressing not present.</td></tr><tr><td>2006-04-28 @ 13:25</td><td>trogers</td><td>Implemented the resolution of LC129, removing the default for wsaw:Anonymous</td></tr><tr><td>2006-04-28 @ 13:09</td><td>trogers</td><td>Implemented LC124, adding Conformance section.</td></tr><tr><td>2006-04-26 @ 15:34</td><td>mhadley</td><td>Added resolution of issue lc122 - added (..m) notation to wsaw:InterfaceName, wsaw:ServiceName and wsaw:ServiceName/@EndpointName descriptions</td></tr><tr><td>2006-04-26 @ 15:28</td><td>mhadley</td><td>Added resolution of issue lc123 - changed all the examples to be based on the one used in the WSDL 2.0 primer</td></tr><tr><td>2006-04-17 @ 10:27</td><td>trogers</td><td>Removed MUST from section 4.1 concerning the value of [destination] (LC130)</td></tr><tr><td>2006-04-17 @ 10:14</td><td>trogers</td><td>Marking UsingAddressing using &lt;el&gt; tag to show that it is not a typo in heading 3.1 (LC126)</td></tr><tr><td>2006-04-17 @ 10:05</td><td>trogers</td><td>Added the class of product specification to the Abstract (LC125)</td></tr><tr><td>2006-04-17 @ 09:46</td><td>trogers</td><td>Applied the changes required for LC120 - typo in intro and correcting wsa:Action/wsaw:Action.</td></tr><tr><td>2006-04-17 @ 09:34</td><td>trogers</td><td>Applied the changes required for LC119.</td></tr><tr><td>2006-04-17 @ 08:42</td><td>trogers</td><td>Changed the {refeence parameters} property from REQUIRED to OPTIONAL in the component model. This completes LC116.</td></tr><tr><td>2006-03-27 @ 19:48</td><td>mhadley</td><td>Used alternate words instead of lowercase RFC2119 terms</td></tr><tr><td>2006-03-20 @ 15:05</td><td>mhadley</td><td>Fixed a typo in example generated fault action</td></tr><tr><td>2006-03-15 @ 22:56</td><td>trogers</td><td>Implemented the resolution of LC116: added section describing the {reference parameters} property.</td></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 o 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 a typo: 'by by' to 'by'</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10D41"></a>C.3 Changes Since Third Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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 imacts 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>005-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 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 editoria 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="N10D4B"></a>C.4 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="N10D55"></a>C.5 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="N10D5F"></a>C.6 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 Sunday, 14 January 2007 20:34:37 GMT

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