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

2004/ws/addressing ws-addr-wsdl.html,1.31,1.32

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 08 Jan 2006 23:15:22 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1Evjkw-0004eb-FY@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-wsdl.html 
Log Message:
Updated to match the XML - this is the version including Umit's addition of the Anonymous element.

Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -C2 -d -r1.31 -r1.32
*** ws-addr-wsdl.html	22 Nov 2005 21:33:42 -0000	1.31
--- ws-addr-wsdl.html	8 Jan 2006 23:15:20 -0000	1.32
***************
*** 1,3 ****
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
  <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - WSDL Binding</title><style type="text/css">
  code           { font-family: monospace; }
--- 1,3 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - WSDL Binding</title><style type="text/css">
  code           { font-family: monospace; }
***************
*** 45,49 ****
  div.exampleHeader { font-weight: bold;
                      margin: 4px}
! </style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="alternate" title="" href="" type=""><link rel="contents" href="#contents"></head><body>
      <div class="head">
  <h1>Web Services Addressing 1.0 - WSDL Binding</h1>
--- 45,49 ----
  div.exampleHeader { font-weight: bold;
                      margin: 4px}
! </style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link type="" href="" title="" rel="alternate"><link href="#contents" rel="contents"></head><body>
      <div class="head">
  <h1>Web Services Addressing 1.0 - WSDL Binding</h1>
***************
*** 58,61 ****
--- 58,62 ----
              <dd>Marc Hadley, Sun Microsystems, Inc</dd>
              <dd>Tony Rogers, Computer Associates International, Inc</dd>
+             <dd>&Uuml;mit Yal&ccedil;inalp, SAP AG </dd>
          </dl><p>This document is also available in these non-normative formats: <a href=""></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&nbsp;&copy;&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div>
  <h2><a name="abstract">Abstract</a></h2>
***************
*** 67,72 ****
          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="#N66018">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#N66188">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#N66207">WSDL SOAP Module</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#destinwsdl">Destination</a><br>&nbsp;&nsp;&nbsp;&nbsp;4.2 <a href="#actioninwsdl">Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#explicitaction">Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.3 <a href="#N66541">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.3 <a href="#refpinwsdl">Reference Parameters</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&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;&bsp;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="#wsd20outoptionalin">Out-optional-in</a><br>6. <a href="#references"> References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#actioncompatibility">Compatibility of [action] with previous versions of WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#N68664">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N68674">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N68684">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N68694">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
--- 68,73 ----
          no official standing.</strong></p><p></p></div>
      <hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange"> Introduction</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation"> Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#indicatinguse">Indicating Use of WS-Addressing</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#N101E8">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a href="#N1028C">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#N1029F"> Anonymous Element </a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#N102DB">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#N102EE">WSL SOAP Module</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#destinwsdl">Destination</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#actioninwsdl">Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.1 <a href="#explicitaction">Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.3 <a href="#N1043C">WSDL 2.0 Component Model Changes</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.2.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.3 <a href="#refpinwsdl">Reference Parameters</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&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="#wsdl20robustoutony">Robust Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.7 <a href="#wsdl20outin">Out-in</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#references"> References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#actioncompatibility">Compatibility of [action] with previous versions of WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;C.1 <a href="#N10C87">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N10C91">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N10C9B">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N10CA5">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 211,215 ****
                      "http://example.com/www.fabrikam/acct". Note the use of the WSDL[<cite><a href="#WSDL20">WSDL 2.0</a></cite>] wsdlLocation attribute.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 212,216 ----
                      "http://example.com/www.fabrikam/acct". Note the use of the WSDL[<cite><a href="#WSDL20">WSDL 2.0</a></cite>] wsdlLocation attribute.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 250,254 ****
                      an embedded description is undefined.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 251,255 ----
                      an embedded description is undefined.</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 284,288 ****
                  </div>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 2-3. </span>An EPR containing WSDL 1.1 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
--- 285,289 ----
                  </div>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 2-3. </span>An EPR containing WSDL 1.1 metadata</i></p>
                      <div class="exampleInner"><pre>
  &lt;wsa:EndpointReference
***************
*** 322,333 ****
              <div class="div2">
                  
! <h3><a name="N66018"></a>3.1 UsingAddressing Extension Element</h3>
!                 <p>WS-Addressing defines an empty global element, wsaw:UsingAddressing, that may be
!                     used to indicate that an endpoint conforms to the WS-Addressing specification.
!                     The wsdl:required attribute MAY be used to indicate whether WS-Addressing
!                     Message Addressing Properties are required in messages received from service
!                     requesters. <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</caption>
--- 323,339 ----
              <div class="div2">
                  
! <h3><a name="N101E8"></a>3.1 UsingAddressing Extension Element</h3>
!                 <p>
!                     WS-Addressing defines an empty global element,
!                     wsaw:UsingAddressing, that may be used to indicate
!                     that an endpoint conforms to the WS-Addressing
!                     specification.  The wsdl:required attribute MAY be
!                     used to indicate whether WS-Addressing Message
!                     Addressing Properties are required in messages
!                     received from service requesters. <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</caption>
***************
*** 367,397 ****
                      </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</a></cite>]), and this specification,
!                     and MUST follow all applicable WS-Addressing normative requirements.</p>
!                 <p>The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding
!                     element. Alternatively, the wsaw:UsingAddressing element MAY instead be included
!                     as a child of the wsdl20:endpoint (or wsdl11:port) when an endpoint intends to
!                     indicate compliance with WS-Addressing for a specific endpoint only.</p>
!                 <p>The inclusion of the wsaw:UsingAddressing element indicates that the applicable
!                     WS-Addressing specifications are supported within the constraints of the WSDL
!                     binding being used. That is, uses of the WS-Addressing specifications that may
!                     violate or are inconsistent with the semantics of the endpoint's WSDL binding
!                     are not supported unless explicitly stated by some other mechanism.</p>
!                 <p>Specifically, when included in a SOAP binding, the wsaw:UsingAddressing marker
!                     identifies the use of Web Services Addressing 1.0 bound to SOAP as defined by
!                         Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>].</p>
!                 <p>The presence of the wsaw:UsingAddressing element in the binding or endpoint
!                     (port) components of the endpoint description does not change the semantics of
!                     the binding. E.g. in the case of the WSDL SOAP/HTTP synchronous binding for
!                     request-response operations, the presence of the wsaw:UsingAddressing element
!                     does not change the requirement that the response message be sent over the same
!                     HTTP channel over which the request was received. In this case, the wsa:replyTo
!                     header in the request MUST NOT contain an address with a value different from
!                     the anonymous URI.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
--- 373,407 ----
                      </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</a></cite>]),
!                     and this specification, and MUST follow all
!                     applicable WS-Addressing normative requirements.
!                 </p>
!                 <p>The wsaw:UsingAddressing element SHOULD appear as a
!                     child of the wsdl:binding element. Alternatively,
!                     the wsaw:UsingAddressing element MAY instead be
!                     included as a child of the wsdl20:endpoint (or
!                     wsdl11:port) when an endpoint intends to indicate
!                     compliance with WS-Addressing for a specific
!                     endpoint only.</p>
!                 <p>The inclusion of the wsaw:UsingAddressing element
!                     indicates that the applicable WS-Addressing
!                     specifications are supported within the
!                     constraints of the WSDL binding being used. This
!                     inclusion allows the usage of anonymous or
!                     non-anonymous URIs as addresses in an EPR.
!                     Specifically, when included in a SOAP binding, the
!                     wsaw:UsingAddressing marker identifies the use of
!                     Web Services Addressing 1.0 bound to SOAP as
!                     defined by Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>].The presence of this element
!                     may 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 wsaw:UsingAddressing in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
***************
*** 405,409 ****
                  </div>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-2. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 1.1</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"&gt;
    &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
--- 415,419 ----
                  </div>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 1.1</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType"&gt;
    &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
***************
*** 422,426 ****
                  <div class="div3">
                      
! <h4><a name="N66188"></a>3.1.1 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
                          component model:</p>
--- 432,436 ----
                  <div class="div3">
                      
! <h4><a name="N1028C"></a>3.1.1 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
                          component model:</p>
***************
*** 437,441 ****
              <div class="div2">
                  
! <h3><a name="N66207"></a>3.2 WSDL SOAP Module</h3>
                  <p>In WSDL 2.0, the wsoap:module construct may be used to declare the use of the
                      WS-Addressing 1.0 Module for the SOAP binding. The meaning of such a
--- 447,544 ----
              <div class="div2">
                  
! <h3><a name="N1029F"></a>3.2  Anonymous Element </h3>
!                 <p>
! 		WS-Addressing defines a wsaw:Anonymous element that
! 		may be only be used in conjunction with
! 		wsaw:UsingAddressing (or its equivalent wsoap:module)
! 		element. The usage of wsaw:Anonymous element is
! 		associated with the usage constraints specified for
! 		wsaw:UsingAddressing element. Hence, it MUST NOT
! 		contain the wsdl:required attribute.
!                 </p>
!                 <p>The inclusion of wsaw:Anonymous without inclusion
!                 of wsaw:UsingAddressing has no normative intent and is
!                 only informational. In other words, the inclusion of
!                 wsaw:Anonymous element in WSDL alone does not imply a
!                 requirement on clients to use Message Addressing
!                 Properties in messages it sends to the service. A
!                 client, however, MAY include Message Addressing
!                 Properties in the messages it sends, either on its own
!                 initiative or as described by other elements of the
!                 service contract, regardless of the presence or
!                 absence of wsaw:UsingAddressing element.
!                 </p>
!                 <p>The wsaw:Anonymous element MAY have 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 endpoints 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</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</a></cite>] MUST be
! 			generated. </p>
!                     </li>
! 	       </ul>
!                <p>This element MAY appear as a child of 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="StockQuoteSoapBinding" type="tns:StockQuotePortType"&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="GetLastTradePrice"&gt;
! &nbsp;&nbsp;&nbsp; &lt;soap:operation soapaction="http://example.com/GetLastTradePrice" /&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;
! &nbsp; &lt;operation name="someOther"&gt;...&lt;/operation&gt;
! &lt;/binding&gt;
! </pre></div>
!                </div>
!                <div class="div3">
!                    
! <h4><a name="N102DB"></a>3.2.1 WSDL 2.0 Component Model Changes</h4>
! 		   <p>Use of Anonymous element adds the following REQUIRED properties to the WSDL 2.0 component model: </p>
!                    <ul>
! 		       <li>
! 		           <p>A property of the binding operation component {anonymous required} of type xs:string. The property value is the value of the wsaw:Anonymous element information item, if present; otherwise "optional". </p>
!                        </li>
!                    </ul>
!                 </div>
!             </div>
!             <div class="div2">
!                 
! <h3><a name="N102EE"></a>3.3 WSDL SOAP Module</h3>
                  <p>In WSDL 2.0, the wsoap:module construct may be used to declare the use of the
                      WS-Addressing 1.0 Module for the SOAP binding. The meaning of such a
***************
*** 446,450 ****
                      http://www.w3.org/@@@@/@@/addressing/module</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-3. </span>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
--- 549,553 ----
                      http://www.w3.org/@@@@/@@/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"
***************
*** 453,457 ****
    &lt;wsoap:module uri="http://www.w3.org/@@@@/@@/addressing/module" required="true" /&gt;
    &lt;operation ref="tns:opCheckAvailability"
!       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response" /&gt;
    &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
  &lt;/binding&gt;</pre></div>
--- 556,562 ----
    &lt;wsoap:module uri="http://www.w3.org/@@@@/@@/addressing/module" required="true" /&gt;
    &lt;operation ref="tns:opCheckAvailability"
!       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"&gt;
!     &lt;wsaw:Anonymous&gt;required&lt;/wsaw:Anonymous&gt;
!   &lt;/operation&gt;
    &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
  &lt;/binding&gt;</pre></div>
***************
*** 511,515 ****
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-1. </span>Explicit specification of wsaw:Action value in a WSDL 2.0 description.</i></p>
                          <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 616,620 ----
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-1. </span>Explicit specification of wsaw:Action value in a WSDL 2.0 description.</i></p>
                          <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 531,535 ****
                          http://example.com/Quote.</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-2. </span>Explicit specification of wsa:Action value in a WSDL 1.1 description.</i></p>
                          <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 636,640 ----
                          http://example.com/Quote.</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-2. </span>Explicit specification of wsa:Action value in a WSDL 1.1 description.</i></p>
                          <div class="exampleInner"><pre>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 559,563 ****
                          general form of an action URI is as follows:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][operation name][direction token]
--- 664,668 ----
                          general form of an action URI is as follows:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][operation name][direction token]
***************
*** 566,570 ****
                      <p>For fault messages, the general form of an action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-4. </span>Structure of default wsa:Action IRI for faults</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][fault name]
--- 671,675 ----
                      <p>For fault messages, the general form of an action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-4. </span>Structure of default wsa:Action IRI for faults</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][fault name]
***************
*** 655,659 ****
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
--- 760,764 ----
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
***************
*** 683,687 ****
                  <div class="div3">
                      
! <h4><a name="N66541"></a>4.2.3 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
                          component model:</p>
--- 788,792 ----
                  <div class="div3">
                      
! <h4><a name="N1043C"></a>4.2.3 WSDL 2.0 Component Model Changes</h4>
                      <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
                          component model:</p>
***************
*** 705,709 ****
                          action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][input|output name]
--- 810,814 ----
                          action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][input|output name]
***************
*** 712,716 ****
                      <p>For fault messages, the general form of an action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-7. </span>Structure of default wsa:Action IRI for faults</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][operation name][delimiter]Fault[delimiter][fault name]
--- 817,821 ----
                      <p>For fault messages, the general form of an action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-7. </span>Structure of default wsa:Action IRI for faults</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][operation name][delimiter]Fault[delimiter][fault name]
***************
*** 767,771 ****
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-8. </span>Example WSDL without explicit wsa:Action values with explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
--- 872,876 ----
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-8. </span>Example WSDL without explicit wsa:Action values with explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
***************
*** 796,800 ****
                          is not present. Consider the following example:</p>
                      <div class="exampleOuter">
!                         <p style="text-align: left" class="exampleHead"><i><span>Example 4-9. </span>Example WSDL without explicit wsa:Action values or explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
--- 901,905 ----
                          is not present. Consider the following example:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-9. </span>Example WSDL without explicit wsa:Action values or explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
***************
*** 1159,1163 ****
                          </tbody>
                      </table><br>
!                     <table border="1" summary="Editorial note: MJH"><tr><td align="left" valign="top" width="50%"><b>Editorial note: MJH</b></td><td align="right" valign="top" width="50%">&nbsp;</td></tr><tr><td colspan="2" align="left" valign="top">Given that [message id] is mandatory above, should [fault endpoint]
                              also be required ?</td></tr></table>
                      <table border="1">
--- 1264,1268 ----
                          </tbody>
                      </table><br>
!                     <table border="1" summary="Editorial note: MJH"><tr><td width="50%" valign="top" align="left"><b>Editorial note: MJH</b></td><td width="50%" valign="top" align="right">&nbsp;</td></tr><tr><td valign="top" align="left" colspan="2">Given that [message id] is mandatory above, should [fault endpoint]
                              also be required ?</td></tr></table>
                      <table border="1">
***************
*** 1215,1219 ****
                          </tbody>
                      </table><br>
!                     <table border="1" summary="Editorial note: MJH"><tr><td align="left" valign="top" width="50%"><b>Editorial note: MJH</b></td><td align="right" valign="top" width="50%">&nbsp;</td></tr><tr><td colspan="2" align="left" valign="top">Should [fault endpoint] be prohibited in the above ? This would
                              prevent getting a fault in response to a fault.</td></tr></table>
                  </div>
--- 1320,1324 ----
                          </tbody>
                      </table><br>
!                     <table border="1" summary="Editorial note: MJH"><tr><td width="50%" valign="top" align="left"><b>Editorial note: MJH</b></td><td width="50%" valign="top" align="right">&nbsp;</td></tr><tr><td valign="top" align="left" colspan="2">Should [fault endpoint] be prohibited in the above ? This would
                              prevent getting a fault in response to a fault.</td></tr></table>
                  </div>
***************
*** 1494,1513 ****
              <div class="div2">
                  
! <h3><a name="N68664"></a>C.1 Changes Since Third Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-11-22 @ 21:29</td><td>mhadley</td><td>Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model</td></tr><tr><td>2005-11-07 @ 07:08</td><td>mhadley</td><td>Added resolution to issue 65, [action] defaults to same as SOAPAction in absence of wsaw:Action</td></tr><tr><td>2005-11-07 @ 06:44</td><td>mhadley</td><td>Updated resolution to issues 56, 57</td></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)/td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new sectin in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N68674"></a>C.2 Changes Since Second Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added reolution to issue 45</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N68684"></a>C.3 Changes Since First Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Swtched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N68694"></a>C.4 Changes Since Submission</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
  Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
--- 1599,1618 ----
              <div class="div2">
                  
! <h3><a name="N10C87"></a>C.1 Changes Since Third Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-11-22 @ 21:29</td><td>mhadley</td><td>Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model</td></tr><tr><td>2005-11-07 @ 07:08</td><td>mhadley</td><td>Added resolution to issue 65, [action] defaults to same as SOAPAction in absence of wsaw:Action</td></tr><tr><td>2005-11-07 @ 06:44</td><td>mhadley</td><td>Updated resolution to issues 56, 57</td></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)/td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new sectin in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10C91"></a>C.2 Changes Since Second Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added reolution to issue 45</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10C9B"></a>C.3 Changes Since First Working Draft</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Swtched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10CA5"></a>C.4 Changes Since Submission</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
  Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
Received on Sunday, 8 January 2006 23:15:46 GMT

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