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

2004/ws/addressing ws-addr-wsdl.html,1.48,1.49

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 05 Jan 2007 14:23:32 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1H2pym-0000Rd-PB@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-wsdl.html 
Log Message:
Sync'ed to editor's draft after implementing CR33 and CR34.

Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -C 2 -d -r1.48 -r1.49
*** ws-addr-wsdl.html	3 Jan 2007 13:20:37 -0000	1.48
--- ws-addr-wsdl.html	5 Jan 2007 14:23:30 -0000	1.49
***************
*** 70,75 ****
          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;&nbsp;&nbsp;&nbsp;&nbsp;3.1.2 <a href="#N102E0">Other Uses of UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#anonelement"> Anonymous Element </a><br>&nbsp;&nbsp;&nsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#wsdl20_anonymous">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="#eprinendpoint">Extending WSDL Endpoints with an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.1.1 <a href="#N103A7">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;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="#N104FB">WSDL 2.0 Component Model hanges</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>&nsp;&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="#N10BEC">Normative</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.2 <a href="#N10D2B">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="#N10DA0">Changes Since Candidate Recommendation Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N10DAA">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N10DB4">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N10DBE">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.5 <a href="#N10DC8">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.6 <a href="#N10DD2">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
--- 70,75 ----
          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="#N10323">Examples (Compact Form)</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.5 <a href="#N1035B">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="#N103C4">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>&bsp;&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="#N10518">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="#wsdl11soliciresponse">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;&bsp;&nbsp;&nbsp;7.1 <a href="#N10C09">Normative</a><br>&nbsp;&nbsp;&nbsp;&nbsp;7.2 <a href="#N10D93">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="#N10E08">Changes Since Candidate Recommendation Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N10E12">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N10E1C">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N10E26">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.5 <a href="#N10E30">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.6 <a href="#N10E3A">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 433,543 ****
                          detailed in section <a href="#uaee"><b>3.1 UsingAddressing Extension Element</b></a>.</p>
                  </div>
-                 <div class="div3">
-                     
- <h4><a name="N102E0"></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 and that of related
-                         elements and attributes including wsaw:Anonymous (see <a href="#anonelement"><b>3.2  Anonymous Element </b></a>) and wsaw:Action (see <a href="#explicitaction"><b>4.4.1 Explicit Association</b></a>) in such contexts is semantically equivalent to the use of
-                         wsaw:UsingAddressing as a WSDL extension.</p>
-                     <p>Note that the association of wsaw:UsingAddressing to WSDL constructs where
-                         the wsaw:UsingAddressing WSDL extension element is not allowed is not
-                         meaningful.</p>
-                 </div>
              </div>
              <div class="div2">
                  
! <h3><a name="anonelement"></a>3.2  Anonymous Element </h3>
!                 <p> WS-Addressing defines a wsaw:Anonymous element that is only used in conjunction
!                     with wsaw:UsingAddressing (or its equivalent wsoap:module, see section <a href="#wsdlsoapmodule"><b>3.3 WSDL SOAP Module</b></a>) element. The usage of
!                     wsaw:Anonymous element is associated with the usage constraints specified for
!                     the wsaw:UsingAddressing element. Hence, it MUST NOT contain the wsdl:required
!                     attribute. </p>
!                 <p>A WSDL or policy based service description that includes the wsaw:UsingAddressing
!                     but no wsaw:Anonymous marker makes no assertion regarding a requirement or a
!                     constraint in the use of the anonymous URI in EPRs contained in messages sent to
!                     the endpoint. In this cases, endpoint service descriptions have to rely on
!                     additional metadata, such as WSDL bindings or additional policy assertions, to
!                     indicate any requirements or restrictions on the use of the anonymous URI by
!                     clients. However, in the absence of additional metadata, clients of the endpoint
!                     MAY assume that the service endpoint follows the behavior indicated by the
!                     'optional' value of the wsaw:Anonymous marker. An endpoint SHOULD send a
!                     wsa:OnlyAnonymousAddressSupported or a wsa:OnlyNonAnonymousAddressSupported
!                     fault back to the client if a message received includes a response epr with an
!                     [address] that is unsupported by the endpoint. </p>
!                 <p>The wsaw:Anonymous element, if present, MUST have one of three distinct values
!                     that indicate three different levels of support for handling anonymous addresses
!                     in EPRs. In the following text, the term response endpoint EPR refers to the
!                     [reply endpoint] and [fault endpoint] message addressing properties
!                     collectively. </p>
!                 <ul>
!                     <li>
!                         <p>"optional": This value indicates that a response endpoint EPR in a
!                             request message MAY contain an anonymous URI as an address. </p>
!                     </li>
!                     <li>
!                         <p>"required":This value indicates that all response endpoint EPRs in a
!                             request message MUST always use anonymous URI as an address. </p>
!                         <p>If a response endpoint EPR does not contain the anonymous URI as an
!                             address value, then a predefined InvalidAddressingHeader fault defined
!                             in Web Services Addressing 1.0 - SOAP Binding [<cite><a href="#WSADDR-SOAP">WS-Addressing SOAP Binding</a></cite>] MUST be generated. </p>
!                     </li>
!                     <li>
!                         <p>"prohibited":This value indicates that any response EPRs in a request
!                             message MUST NOT use anonymous URI as an address.</p>
!                         <p>If a response endpoint EPR contains the anonymous URI as an address
!                             value, then a predefined InvalidAddressingHeader fault defined in Web
!                             Services Addressing 1.0 - SOAP Binding [<cite><a href="#WSADDR-SOAP">WS-Addressing SOAP Binding</a></cite>]
!                             MUST be generated. </p>
!                     </li>
!                 </ul>
!                 <p>This element MAY appear as a child of an operation element in a binding element
!                     in WSDL 1.1, or as a 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="reservationSOAPBinding" type="tns:reservationInterface"&gt;
! &nbsp; &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
! &nbsp; &lt;wsaw:UsingAddressing wsdl:required="true" /&gt;
! &nbsp; &lt;operation name="opCheckAvailability"&gt;
! &nbsp;&nbsp;&nbsp; &lt;soap:operation soapaction="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability" /&gt;
! &nbsp;&nbsp;&nbsp; &lt;input&gt;
! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;soap:body use="literal" /&gt;
! &nbsp;&nbsp;&nbsp; &lt;/input&gt;
! &nbsp;&nbsp;&nbsp; &lt;output&gt;
! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;soap:body use="literal" /&gt;
! &nbsp;&nbsp;&nbsp; &lt;/output&gt;
! &nbsp;&nbsp;&nbsp; &lt;wsaw:Anonymous&gt;required&lt;/wsaw:Anonymous&gt;
! &nbsp; &lt;/operation&gt;
! &lt;/binding&gt;
! </pre></div>
                  </div>
                  <div class="div3">
                      
! <h4><a name="wsdl20_anonymous"></a>3.2.1 WSDL 2.0 Component Model Changes</h4>
!                     <p>Use of the Anonymous element adds the following property to the WSDL 2.0
!                         component model: </p>
!                     <ul>
!                         <li>
!                             <p>{anonymous addresses} OPTIONAL, of type xs:string, to the Binding
!                                 Operation component.</p>
!                         </li>
!                     </ul>
!                     <p><a href="#tab_anonymous_Mapping">Table 3-3</a> shows the mapping from the XML
!                         representation to the WSDL 2.0 component model.</p>
!                     <a name="tab_anonymous_Mapping"></a><table border="1">
!                         <caption>Table 3-3. Mapping from XML Representation to Binding Operation component
!                             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">{anonymous addresses}</td>
!                                 <td rowspan="1" colspan="1"> The value of the <code>wsaw:Anonymous</code>  <em>element information item</em>, if present.
!                                     Otherwise, it is not present. </td>
!                             </tr>
!                         </tbody>
!                     </table><br>
                  </div>
              </div>
              <div class="div2">
--- 433,688 ----
                          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>
!                 <p>Another mechanism for indicating that a binding or endpoint <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> 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 the following three policy assertions.</p>
!                 <div class="div3">
!                     
! <h4><a name="wspolicyaddressing"></a>3.2.1 Addressing Assertion</h4>
!                     <p>The wsaw: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 wsaw:AnonymousResponses element MAY be used as a policy assertion nested
!                         within the wsaw:Addressing assertion in accordance with the rules laid down
!                         by WS-Policy Framework 1.5 section 4.3.2. The appearance of this element
!                         within a policy alternative indicates that the endpoint will accept request
!                         messages with response endpoint EPRs that contain the anonymous URI
!                         ("http://www.w3.org/2005/08/addressing/anonymous") as the value of
!                         [address]. The absence of the wsaw:AnonymousResponses policy assertion
!                         within a policy alternative does <b>not</b> indicate that the endpoint will
!                         not accept request messages with response endpoint EPRs that contain the
!                         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 wsaw:NonAnonymousResponses element MAY be used as a policy assertion
!                         nested within the Addressing assertion in accordance with the rules laid
!                         down by WS-Policy Framework 1.5 section 4.3.2. The appearance of this
!                         element within a policy alternative indicates that the endpoint will accept
!                         request messages with response endpoint EPRs that contain something other
!                         than the anonymous URI as the value of [address]. This assertion is
!                         deliberately vague; its presence indicates that a non-anonymous addresses
!                         might be accepted but doesn't constrain what such an address might look
!                         like. A receiver can still reject a request that contains an address that it
!                         doesn't understand or that requires a binding it doesn't support. As with
!                         the other assertions, the absence of the wsaw:NonAnonymousResponses policy
!                         assertion within a policy alternative does <b>not</b> indicate that the
!                         endpoint will not accept request messages with response endpoint EPRs that
!                         contain something other than the anonymous URI address. </p>
! 
!                 <p>NOTE: If both AnonymousResponses and NonAnonymousResponses are supported and the
!                     intention is to allow either to be used care should be taken to ensure there is
!                     an alternative which includes just AnonymousResponses as a nested assertion and
!                     an alternative with just NonAnonymousResponses as a nested assertion so that a
!                     subject which supports only one will have a compatible policy [<cite><a href="#WSPolicyPrimer">WS Policy 1.5 - Primer</a></cite> section 3.4].</p>
!                 <p> Also, given that the lack of either of these assertions (AnonymousResponses and
!                     NonAnonymousResponses) does not indicate lack of support, it is suggested that a
!                     subject that does not have a strict compatibility requirement that an
!                     interacting subject understands or is concerned with these assertions provides
!                     an alternative without either assertion. </p>
                  </div>
+                 <div class="div3">
+                     
+ <h4><a name="N10323"></a>3.2.4 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;wsaw:Addressing wsp:Optional="true"&gt;
+         &lt;wsp:Policy&gt;&lt;/wsp:Policy&gt;
+     &lt;/wsaw:Addressing&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </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;wsaw:Addressing&gt;
+         &lt;wsp:Policy&gt;&lt;/wsp:Policy&gt;
+     &lt;/wsaw:Addressing&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </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;wsaw:Addressing wsp:Optional="true"&gt;
+         &lt;wsp:Policy&gt;
+             &lt;wsaw:AnonymousResponses wsp:Optional="true"/&gt;
+             &lt;wsaw:NonAnonymousResponses wsp:Optional="true"/&gt;
+         &lt;/wsp:Policy&gt;
+     &lt;/wsaw:Addressing&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </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;wsaw:Addressing&gt;
+         &lt;wsp:Policy&gt;
+             &lt;wsp:ExactlyOne&gt;
+                 &lt;wsaw:AnonymousResponses wsp:Optional="true"/&gt;
+                 &lt;wsaw:NonAnonymousResponses wsp:Optional="true"/&gt;
+             &lt;/wsp:ExactlyOne&gt;
+         &lt;/wsp:Policy&gt;
+     &lt;/wsaw:Addressing&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </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;wsaw:Addressing&gt;
+         &lt;wsp:Policy&gt;
+             &lt;wsaw:NonAnonymousResponses/&gt;
+         &lt;/wsp:Policy&gt;
+     &lt;/wsaw:Addressing&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </div>                                        
+                 </div>                
+                 <div class="div3">
+                     
+ <h4><a name="N1035B"></a>3.2.5 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;
+         &lt;wsp:All/&gt;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All/&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+     &lt;/wsp:ExactlyOne&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </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;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All/&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+     &lt;/wsp:ExactlyOne&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </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;
+         &lt;wsp:All/&gt;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All/&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All&gt;
+                             &lt;wsaw:AnonymousResponses/&gt;
+                         &lt;/wsp:All&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All&gt;
+                             &lt;wsaw:NonAnonymousResponses/&gt;
+                         &lt;/wsp:All&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All&gt;
+                             &lt;wsaw:AnonymousResponses/&gt;
+                             &lt;wsaw:NonAnonymousResponses/&gt;
+                         &lt;/wsp:All&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+     &lt;/wsp:ExactlyOne&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </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;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All&gt;
+                             &lt;wsaw:AnonymousResponses/&gt;
+                         &lt;/wsp:All&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All&gt;
+                             &lt;wsaw:NonAnonymousResponses/&gt;
+                         &lt;/wsp:All&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+     &lt;/wsp:ExactlyOne&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </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;
+         &lt;wsp:All&gt;
+             &lt;wsaw:Addressing&gt;
+                 &lt;wsp:Policy&gt;
+                     &lt;wsp:ExactlyOne&gt;
+                         &lt;wsp:All&gt;
+                             &lt;wsaw:NonAnonymousResponses/&gt;
+                         &lt;/wsp:All&gt;
+                     &lt;/wsp:ExactlyOne&gt;
+                 &lt;/wsp:Policy&gt;
+             &lt;/wsaw:Addressing&gt;
+         &lt;/wsp:All&gt;
+     &lt;/wsp:ExactlyOne&gt;
+ &lt;/wsp:Policy&gt;</pre></div>
+                     </div>                                        
+                 </div>                
              </div>
              <div class="div2">
***************
*** 554,558 ****
                      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"
--- 699,703 ----
                      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"
***************
*** 588,592 ****
                  <div class="div3">
                      
! <h4><a name="N103A7"></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>
--- 733,737 ----
                  <div class="div3">
                      
! <h4><a name="N103C4"></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>
***************
*** 842,846 ****
                  <div class="div3">
                      
! <h4><a name="N104FB"></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>
--- 987,991 ----
                  <div class="div3">
                      
! <h4><a name="N10518"></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>
***************
*** 1537,1541 ****
              <div class="div2">
                  
! <h3><a name="N10BEC"></a>7.1 Normative</h3>
                  <dl>
  		  <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
--- 1682,1686 ----
              <div class="div2">
                  
! <h3><a name="N10C09"></a>7.1 Normative</h3>
                  <dl>
  		  <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
***************
*** 1571,1574 ****
--- 1716,1738 ----
                          http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/. The <a href="http://www.w3.org/TR/wsdl20-adjuncts">latest version of WSDL 2.0
                              Adjuncts</a> is available at http://www.w3.org/TR/wsdl20-adjuncts.</dd>
+                     <dt class="label"><a name="WSPolicy"></a>[WS Policy 1.5 - Framework] </dt><dd>
+                         <cite><a href="http://www.w3.org/TR/2006/WD-ws-policy-20061117/">Web Services Policy 1.5 - Framework</a></cite>, Asir S Vedamuthu,
+                         David Orchard, Maryann Hondo, Toufic Boubez, Prasad Yendluri, Editors. World
+                         Wide Web Consortium, 17 November 2006. This version of the WS-Policy
+                         Framework is http://www.w3.org/TR/2006/WD-ws-policy-20061117. The <a href="http://www.w3.org/TR/ws-policy">latest version of WS Policy
+                             Framework</a> is available at http://www.w3.org/TR/ws-policy </dd>
+                     <dt class="label"><a name="WSPolicyAttachment"></a>[WS Policy 1.5 - Attachment] </dt><dd>
+                         <cite><a href="http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117/">Web Services Policy 1.5 - Attachment</a></cite>, Asir S Vedamuthu,
+                         David Orchard, Maryann Hondo, Toufic Boubez, Prasad Yendluri, Editors. World
+                         Wide Web Consortium, 17 November 2006. This version of the WS-Policy
+                         Attachment is http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117. The <a href="http://www.w3.org/TR/ws-policy-attach">latest version of WS Policy
+                             Attachment</a> is available at http://www.w3.org/TR/ws-policy-attach </dd>
+                     <dt class="label"><a name="WSPolicyPrimer"></a>[WS Policy 1.5 - Primer] </dt><dd>
+                         <cite><a href="http://www.w3.org/TR/2006/WD-ws-policy-primer-20061018/">Web Services Policy 1.5 - Attachment</a></cite>, Asir S Vedamuthu,
+                         David Orchard, Maryann Hondo, Toufic Boubez, Prasad Yendluri, Editors. World
+                         Wide Web Consortium, 18 November 2006. This version of the WS-Policy Primer
+                         is http://www.w3.org/TR/2006/WD-ws-policy-primer-20061018. The <a href="http://www.w3.org/TR/ws-policy-primer">latest version of WS Policy
+                             Primer</a> is available at http://www.w3.org/TR/ws-policy-primer
+                     </dd>
                      <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
                          <cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate Requirement
***************
*** 1628,1632 ****
              <div class="div2">
                  
! <h3><a name="N10D2B"></a>7.2 Informative</h3>
                  <dl>
                      <dt class="label"><a name="WS-Security"></a>[WS-Security] </dt><dd> OASIS, <cite><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">Web Services Security: SOAP Message Security</a></cite>,
--- 1792,1796 ----
              <div class="div2">
                  
! <h3><a name="N10D93"></a>7.2 Informative</h3>
                  <dl>
                      <dt class="label"><a name="WS-Security"></a>[WS-Security] </dt><dd> OASIS, <cite><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">Web Services Security: SOAP Message Security</a></cite>,
***************
*** 1697,1726 ****
              <div class="div2">
                  
! <h3><a name="N10DA0"></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-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="N10DAA"></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="N10DB4"></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="N10DBE"></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="N10DC8"></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="N10DD2"></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>
--- 1861,1890 ----
              <div class="div2">
                  
! <h3><a name="N10E08"></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-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="N10E12"></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="N10E1C"></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="N10E26"></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="N10E30"></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="N10E3A"></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 Friday, 5 January 2007 14:23:56 GMT

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