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

2004/ws/addressing ws-addr-wsdl.html,1.45,1.46

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 28 Apr 2006 15:11:18 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1FZUco-0004wb-LB@lionel-hutz.w3.org>

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

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

Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -C2 -d -r1.45 -r1.46
*** ws-addr-wsdl.html	28 Apr 2006 13:44:29 -0000	1.45
--- ws-addr-wsdl.html	28 Apr 2006 15:11:16 -0000	1.46
***************
*** 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 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>
--- 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>
***************
*** 64,75 ****
                  and messages. Web Services Addressing 1.0 - WSDL Binding (this document) defines how the abstract
                  properties defined in Web Services Addressing 1.0 - Core are described using WSDL.</p>
!             <p>The classes of products for which this specification is designed to be
!                 relevant include WSDL and WS-Addressing EPR consumers.</p>
          </div><div>
  <h2><a name="status">Status of this Document</a></h2><p><strong>This document is an editors' copy that has
          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="#N102D5">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="#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="#N104BE">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>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;4.3.1 <a href="#refpiwsdlcm">WSDL 2.0 Component Model Changes</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>&nsp;&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></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="#N10D4E">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N10D58">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N10D62">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N10D6C">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
--- 64,75 ----
                  and messages. Web Services Addressing 1.0 - WSDL Binding (this document) defines how the abstract
                  properties defined in Web Services Addressing 1.0 - Core are described using WSDL.</p>
!             <p>The classes of products for which this specification is designed to be relevant
!                 include WSDL and WS-Addressing EPR consumers.</p>
          </div><div>
  <h2><a name="status">Status of this Document</a></h2><p><strong>This document is an editors' copy that has
          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="#N66265">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="#N66461">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="#N66798">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></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="#N68958">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.2 <a href="#N68968">Changes Since Third Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.3 <a href="#N68978">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.4 <a href="#N68988">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;C.5 <a href="#N68998">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 202,218 ****
                          <dd>
                              <p>An NCName that identifies one endpoint amongst the set identified by
!                                 the service name above. An endpoint is represented by an endpoint
!                                 in WSDL 2.0 or, for backwards compatibility, a port in WSDL 1.1.
!                                 When this attribute is specified, the EPR is considered to be
!                                 specific to the endpoint or port it identifies.</p>
                          </dd>
                      
                  </dl>
!                 <p>The element information items defined above are used in an EPR's metadata section.
!                     The following shows an example endpoint reference. This references the interface
!                     named "ghns:reservationInterface" at the endpoint IRI
                      "http://greath.example.com/2004/reservation". 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
--- 202,218 ----
                          <dd>
                              <p>An NCName that identifies one endpoint amongst the set identified by
!                                 the service name above. An endpoint is represented by an endpoint in
!                                 WSDL 2.0 or, for backwards compatibility, a port in WSDL 1.1. When
!                                 this attribute is specified, the EPR is considered to be specific to
!                                 the endpoint or port it identifies.</p>
                          </dd>
                      
                  </dl>
!                 <p>The element information items defined above are used in an EPR's metadata
!                     section. The following shows an example endpoint reference. This references the
!                     interface named "ghns:reservationInterface" at the endpoint IRI
                      "http://greath.example.com/2004/reservation". 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
***************
*** 253,257 ****
                      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
--- 253,257 ----
                      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
***************
*** 281,285 ****
                  </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
--- 281,285 ----
                  </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
***************
*** 313,328 ****
                  
  <h3><a name="uaee"></a>3.1 <code>UsingAddressing</code>  Extension Element</h3>
!                 <p>
!                     WS-Addressing defines an empty global element,
!                     wsaw:UsingAddressing, that can be used to indicate
!                     that an endpoint conforms to the WS-Addressing
!                     specification.  The wsdl:required attribute MAY be
!                     used to indicate whether WS-Addressing Message
!                     Addressing Properties are required in messages
!                     received from service requesters. <a href="#mappresence">Table 3-1</a> outlines the requirements on
!                     messages sent from an endpoint based on the
!                     contents of any preceding input message and how
!                     the use of addressing is indicated in the WSDL.
!                 </p>
                  <a name="mappresence"></a><table border="1">
                      <caption>Table 3-1. MAPs Present in output message when wsaw:UsingAddressing is present</caption>
--- 313,323 ----
                  
  <h3><a name="uaee"></a>3.1 <code>UsingAddressing</code>  Extension Element</h3>
!                 <p> WS-Addressing defines an empty global element, wsaw:UsingAddressing, that can be
!                     used to indicate that an endpoint conforms to the WS-Addressing specification.
!                     The wsdl:required attribute MAY be used to indicate whether WS-Addressing
!                     Message Addressing Properties are required in messages received from service
!                     requesters. <a href="#mappresence">Table 3-1</a> outlines the requirements on messages
!                     sent from an endpoint based on the contents of any preceding input message and
!                     how the use of addressing is indicated in the WSDL. </p>
                  <a name="mappresence"></a><table border="1">
                      <caption>Table 3-1. MAPs Present in output message when wsaw:UsingAddressing is present</caption>
***************
*** 340,344 ****
                              <td rowspan="1" colspan="1">REQUIRED</td>
                          </tr>
!                           <tr>
                              <td rowspan="1" colspan="1">No</td>
                              <td rowspan="1" colspan="1">Fault</td>
--- 335,339 ----
                              <td rowspan="1" colspan="1">REQUIRED</td>
                          </tr>
!                         <tr>
                              <td rowspan="1" colspan="1">No</td>
                              <td rowspan="1" colspan="1">Fault</td>
***************
*** 348,380 ****
                      </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 and allows use 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
!                     can extend the semantics of the endpoint's WSDL
!                     binding. </p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
--- 343,363 ----
                      </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 and allows use 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 can extend the semantics
!                     of the endpoint's WSDL binding. </p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
***************
*** 388,392 ****
                  </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="reservationSOAPBinding"
                          type="tns:reservationInterface"&gt;
--- 371,375 ----
                  </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="reservationSOAPBinding"
                          type="tns:reservationInterface"&gt;
***************
*** 407,474 ****
                      
  <h4><a name="wsdl20_usingaddressing"></a>3.1.1 WSDL 2.0 Component Model Changes</h4>
! 
! 		    <table border="1" summary="Editorial note: HH"><tr><td width="50%" valign="top" align="left"><b>Editorial note: HH</b></td><td width="50%" valign="top" align="right">&nbsp;</td></tr><tr><td valign="top" align="left" colspan="2">This has NOT been approved by the WG yet.</td></tr></table>
! 
!                     <p>Use of WS-Addressing adds the following property to the WSDL 2.0
!                         component model:</p>
                      <ul>
                          <li>
!                             <p>{addressing} OPTIONAL, of type
!                             <code>xs:token</code> with one of the
!                             values "required" or
!                             "optional", to the Binding
!                             and Endpoint components. When present, the
!                             property indicates that the use of
!                             addressing has been declared.
! 			    </p>
! 			</li>
! 		    </ul>
! 
! 		    <p><a href="#tab_addressing_Mapping">Table 3-2</a> shows the
! 		    mapping from the XML representation to the WSDL
! 		    2.0 component model.</p>
! 
! 		    <a name="tab_addressing_Mapping"></a><table border="1">
! 		      <caption>Table 3-2. Mapping from XML Representation to Binding and Endpoint components Extension Properties</caption>
! 		      <tbody>
! 			<tr>
! 			  <th rowspan="1" colspan="1">Property</th>
! 			  <th rowspan="1" colspan="1">Value</th>
! 			</tr>
! 			<tr>
! 			  <td rowspan="1" colspan="1">{addressing}</td>
! 			  <td rowspan="1" colspan="1">
! 			    If a <code>wsaw:UsingAddresing</code> 
! 			    extension element is present:
! 			    <ul>
! 			      <li><p>if a
! 			    <code>wsdl:required</code>  <em>attribute information item</em> is present
! 			    and has a value of "true",
! 			    then "required"</p></li>
! 			      <li><p>otherwise
! 			    "optional"</p></li>
! 			    </ul>
! 			  </td>
! 			</tr>
! 		      </tbody>
! 		    </table><br>
! 
! 		    <p><a href="#mappresence">Table 3-1</a> summarizes the
!                             meaning of the property as detailed in section <a href="#uaee"><b>3.1 UsingAddressing Extension Element</b></a>.</p>
! 
                  </div>
                  <div class="div3">
                      
! <h4><a name="N102D5"></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.2.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">
--- 390,444 ----
                      
  <h4><a name="wsdl20_usingaddressing"></a>3.1.1 WSDL 2.0 Component Model Changes</h4>
!                     <table border="1" summary="Editorial note: HH"><tr><td align="left" valign="top" width="50%"><b>Editorial note: HH</b></td><td align="right" valign="top" width="50%">&nbsp;</td></tr><tr><td colspan="2" align="left" valign="top">This has NOT been approved by the WG yet.</td></tr></table>
!                     <p>Use of WS-Addressing adds the following property to the WSDL 2.0 component
!                         model:</p>
                      <ul>
                          <li>
!                             <p>{addressing} OPTIONAL, of type <code>xs:token</code> with one of the
!                                 values "required" or "optional", to
!                                 the Binding and Endpoint components. When present, the property
!                                 indicates that the use of addressing has been declared. </p>
!                         </li>
!                     </ul>
!                     <p><a href="#tab_addressing_Mapping">Table 3-2</a> shows the mapping from the XML
!                         representation to the WSDL 2.0 component model.</p>
!                     <a name="tab_addressing_Mapping"></a><table border="1">
!                         <caption>Table 3-2. Mapping from XML Representation to Binding and Endpoint components
!                             Extension Properties</caption>
!                         <tbody>
!                             <tr>
!                                 <th rowspan="1" colspan="1">Property</th>
!                                 <th rowspan="1" colspan="1">Value</th>
!                             </tr>
!                             <tr>
!                                 <td rowspan="1" colspan="1">{addressing}</td>
!                                 <td rowspan="1" colspan="1"> If a <code>wsaw:UsingAddresing</code>  extension element is present: <ul>
!                                         <li>
!                                             <p>if a <code>wsdl:required</code>  <em>attribute information item</em> is present
!                                                 and has a value of "true", then
!                                                   "required"</p>
!                                         </li>
!                                         <li>
!                                             <p>otherwise "optional"</p>
!                                         </li>
!                                     </ul>
!                                 </td>
!                             </tr>
!                         </tbody>
!                     </table><br>
!                     <p><a href="#mappresence">Table 3-1</a> summarizes the meaning of the property as
!                         detailed in section <a href="#uaee"><b>3.1 UsingAddressing Extension Element</b></a>.</p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="N66265"></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">
***************
*** 492,499 ****
                      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>
--- 462,470 ----
                      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>
***************
*** 520,524 ****
                      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;
--- 491,495 ----
                      in WSDL 1.1, or as a binding operation extension element in WSDL 2.0.</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-3. </span> Indicating use of anonymous addresses using wsaw:Anonymous. </i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" type="tns:reservationInterface"&gt;
  &nbsp; &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
***************
*** 572,583 ****
                  <p> In WSDL 2.0, a SOAP Module component can be used to declare the use of the
                      WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a
!                     SOAP Module component is semantically equivalent to the {addressing}
!                     property defined in section <a href="#wsdl20_usingaddressing"><b>3.1.1 WSDL 2.0 Component Model Changes</b></a>. Note that this module is only meaningful when
!                     used on WSDL components where the {addressing} property is allowed,
!                     i.e. as a member of the {soap modules} property of a Binding component.</p>
                  <p>The WS-Addressing 1.0 SOAP Module is described in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] and is identified with the following URI:
                      http://www.w3.org/2005/08/addressing/module</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </span>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
--- 543,555 ----
                  <p> In WSDL 2.0, a SOAP Module component can be used to declare the use of the
                      WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a
!                     SOAP Module component is semantically equivalent to the {addressing} property
!                     defined in section <a href="#wsdl20_usingaddressing"><b>3.1.1 WSDL 2.0 Component Model Changes</b></a>. Note that this
!                     module is only meaningful when used on WSDL components where the {addressing}
!                     property is allowed, i.e. as a member of the {soap modules} property of a
!                     Binding component.</p>
                  <p>The WS-Addressing 1.0 SOAP Module is described in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] and is identified with the following URI:
                      http://www.w3.org/2005/08/addressing/module</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-4. </span>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</i></p>
                      <div class="exampleInner"><pre>&lt;binding name="reservationSOAPBinding" 
      interface="tns:reservationInterface"
***************
*** 603,625 ****
              <div class="div2">
                  
! <h3><a name="destinwsdl"></a>4.1 Destination</h3>
!                 <p>The value of the [destination] 
!                     message addressing property for a message sent to
!                     an endpoint typically matches the value of the {address} property of the endpoint
!                     component (WSDL 2.0) or the address value provided by the relevant port
!                     extension (WSDL 1.1). For a SOAP 1.1 port described using WSDL 1.1, the value is
!                     provided by the location attribute of the soap11:address extension element.</p>
!                 <p>Additional runtime information could override the value of the [destination] message
!                     addressing property for messages sent to an endpoint, e.g. a runtime exchange might
!                     result in a redirection to a different EPR. Note that WS-Addressing does not define any normative
!                     mechanism for such redirection.</p>
              </div>
              <div class="div2">
                  
! <h3><a name="actioninwsdl"></a>4.2 Action</h3>
                  <p>WS-Addressing defines two mechanisms to associate a value of the [action]
                      property with input, output and fault elements within a WSDL description:
!                     explicit and defaulting. Explicit association is described in section <a href="#explicitaction"><b>4.2.1 Explicit Association</b></a>; action defaulting (where a unique value for the
!                     [action] property is automatically generated) is described in section <a href="#defactionwsdl11"><b>4.2.4  Default Action Pattern for WSDL 1.1</b></a> for WSDL 1.1 and section <a href="#defactionwsdl20"><b>4.2.2 Default Action Pattern for WSDL 2.0</b></a> for WSDL 2.0.</p>
                  <p>Ensuring that there is sufficient information within a message to distinguish
                      which WSDL operation it is associated with is specified as a best practice in
--- 575,633 ----
              <div class="div2">
                  
! <h3><a name="eprinendpoint"></a>4.1 Extending WSDL Endpoints with an EPR</h3>
!                 <p>A wsdl20:endpoint or wsdl11:port element MAY be extended using a child
!                     wsa:EndpointReference element. When extended this way, the [address] property of
!                     the child EPR must match the {address} property of the endpoint component (WSDL
!                     2.0) or the address value provided by the relevant port extension (WSDL 1.1).
!                     For example, in a SOAP 1.1 port described using WSDL 1.1, the location attribute
!                     of a soap11:address element (if present) must have the same value as the
!                     wsa:Address child element of the wsa:EndpointReference element.</p>
!                 <div class="div3">
!                     
! <h4><a name="N66461"></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>
!                     <ul>
!                         <li>
!                             <p> A property of the Endpoint component, named {endpoint reference}.
!                                 This property is of type wsa:EndpointReference, with a cardinality
!                                 of 1. The property has the value of the wsa:EndpointReference
!                                 element used as a child of wsdl20:endpoint, if any. If no such
!                                 extension exists, this property is absent.</p>
!                         </li>
!                     </ul>
!                 </div>
              </div>
              <div class="div2">
                  
! <h3><a name="destinwsdl"></a>4.2 Destination</h3>
!                 <p>The value of the [destination] message addressing property for a message sent to
!                     an endpoint typically matches the value of the {address} property of the
!                     endpoint component (WSDL 2.0) or the address value (if any) provided by the
!                     relevant port extension (WSDL 1.1). For a SOAP 1.1 port described using WSDL
!                     1.1, the value is provided by the location attribute of the soap11:address
!                     extension element. For an endpoint or port extended with an EPR (see <a href="#eprinendpoint"><b>4.1 Extending WSDL Endpoints with an EPR</b></a>), the value is provided by the [address] property of
!                     the EPR.</p>
!                 <p>Additional runtime information could override the value of the [destination]
!                     message addressing property for messages sent to an endpoint, e.g. a runtime
!                     exchange might result in a redirection to a different EPR. Note that
!                     WS-Addressing does not define any normative mechanism for such redirection.</p>
!             </div>
!             <div class="div2">
!                 
! <h3><a name="refpinwsdl"></a>4.3 Reference Parameters</h3>
!                 <p>When a wsa:EndpointReference element is present in a wsdl20:endpoint or a
!                     wsdl11:port element (see <a href="#eprinendpoint"><b>4.1 Extending WSDL Endpoints with an EPR</b></a>), the value of the
!                     [reference parameters] message addressing property for a message sent to an
!                     endpoint MUST include the contents of the wsa:ReferenceParameters element, if
!                     one exists within that EPR.</p>
!             </div>
!             <div class="div2">
!                 
! <h3><a name="actioninwsdl"></a>4.4 Action</h3>
                  <p>WS-Addressing defines two mechanisms to associate a value of the [action]
                      property with input, output and fault elements within a WSDL description:
!                     explicit and defaulting. Explicit association is described in section <a href="#explicitaction"><b>4.4.1 Explicit Association</b></a>; action defaulting (where a unique value for the
!                     [action] property is automatically generated) is described in section <a href="#defactionwsdl11"><b>4.4.4  Default Action Pattern for WSDL 1.1</b></a> for WSDL 1.1 and section <a href="#defactionwsdl20"><b>4.4.2 Default Action Pattern for WSDL 2.0</b></a> for WSDL 2.0.</p>
                  <p>Ensuring that there is sufficient information within a message to distinguish
                      which WSDL operation it is associated with is specified as a best practice in
***************
*** 628,632 ****
                  <div class="div3">
                      
! <h4><a name="explicitaction"></a>4.2.1 Explicit Association</h4>
                      <p>WS-Addressing defines a global attribute, wsaw:Action, that can be used to
                          explicitly define the value of the [action] property for messages in a WSDL
--- 636,640 ----
                  <div class="div3">
                      
! <h4><a name="explicitaction"></a>4.4.1 Explicit Association</h4>
                      <p>WS-Addressing defines a global attribute, wsaw:Action, that can be used to
                          explicitly define the value of the [action] property for messages in a WSDL
***************
*** 651,655 ****
                      <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 wsa:Action value in a WSDL 2.0 description.</i></p>
                          <div class="exampleInner"><pre>
  &lt;description targetNamespace="http://greath.example.com/2004/schemas/resSvc" ...&gt;
--- 659,663 ----
                      <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 wsa:Action value in a WSDL 2.0 description.</i></p>
                          <div class="exampleInner"><pre>
  &lt;description targetNamespace="http://greath.example.com/2004/schemas/resSvc" ...&gt;
***************
*** 667,675 ****
                      </div>
                      <p>The action for the input of the opCheckAvailability operation within the
!                         SreservationInterface is explicitly defined to be http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability.
!                         The action for the output of this same operation is
                          http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</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://greath.example.com/2004/schemas/resSvc" ...&gt;
--- 675,684 ----
                      </div>
                      <p>The action for the input of the opCheckAvailability operation within the
!                         SreservationInterface is explicitly defined to be
!                         http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability. The action
!                         for the output of this same operation is
                          http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</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://greath.example.com/2004/schemas/resSvc" ...&gt;
***************
*** 688,703 ****
                      </div>
                      <p>The action for the input of the opCheckAvailability operation within the
!                         reservationInterface port type is explicitly defined to be http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability.
!                         The action for the output of this same operation is
                          http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="defactionwsdl20"></a>4.2.2 Default Action Pattern for WSDL 2.0</h4>
                      <p>In the absence of the wsa:Action attribute, the following pattern is used in
                          WSDL 2.0 documents to construct a default action for inputs and outputs. The
                          general form of an action URI is as follows:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][interface name][delimiter][operation name][direction token]
--- 697,713 ----
                      </div>
                      <p>The action for the input of the opCheckAvailability operation within the
!                         reservationInterface port type is explicitly defined to be
!                         http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability. The action
!                         for the output of this same operation is
                          http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
                  </div>
                  <div class="div3">
                      
! <h4><a name="defactionwsdl20"></a>4.4.2 Default Action Pattern for WSDL 2.0</h4>
                      <p>In the absence of the wsa:Action attribute, the following pattern is used in
                          WSDL 2.0 documents to construct a default action for inputs and outputs. The
                          general form of an action URI is as follows:</p>
                      <div class="exampleOuter">
!                         <p 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]
***************
*** 706,710 ****
                      <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]
--- 716,720 ----
                      <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]
***************
*** 795,799 ****
                      <p>For example consider the following WSDL excerpt:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
                              names.</i></p>
                          <div class="exampleInner"><pre>
--- 805,809 ----
                      <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>
***************
*** 823,837 ****
                  <div class="div3">
                      
! <h4><a name="N104BE"></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>
                      <ul>
                          <li>
!                             <p>A property of the Interface Message
!                                 Reference and Interface Fault components named {action}. The
!                                 property is of type xs:anyURI. The
!                                 property value is the value of the wsaw:Action attribute information item, if present;
!                                 otherwise the default value computed following the rules from
!                                 section <a href="#defactionwsdl20"><b>4.2.2 Default Action Pattern for WSDL 2.0</b></a>.</p>
                          </li>
                      </ul>
--- 833,846 ----
                  <div class="div3">
                      
! <h4><a name="N66798"></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>
                      <ul>
                          <li>
!                             <p>A property of the Interface Message Reference and Interface Fault
!                                 components named {action}. The property is of type xs:anyURI. The
!                                 property value is the value of the wsaw:Action attribute information
!                                 item, if present; otherwise the default value computed following the
!                                 rules from section <a href="#defactionwsdl20"><b>4.4.2 Default Action Pattern for WSDL 2.0</b></a>.</p>
                          </li>
                      </ul>
***************
*** 839,849 ****
                  <div class="div3">
                      
! <h4><a name="defactionwsdl11"></a>4.2.4  Default Action Pattern for WSDL 1.1</h4>
                      <p>A default pattern is also defined for backwards compatibility with WSDL 1.1.
!                         In the absence of the wsaw:Action attribute, the following pattern is used to
!                         construct a default action for inputs and outputs. The general form of an
                          action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p class="exampleHead" style="text-align: left"><i><span>Example 4-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
                          <div class="exampleInner"><pre>
  [target namespace][delimiter][port type name][delimiter][input|output name]
--- 848,858 ----
                  <div class="div3">
                      
! <h4><a name="defactionwsdl11"></a>4.4.4  Default Action Pattern for WSDL 1.1</h4>
                      <p>A default pattern is also defined for backwards compatibility with WSDL 1.1.
!                         In the absence of the wsaw:Action attribute, the following pattern is used
!                         to construct a default action for inputs and outputs. The general form of an
                          action IRI is as follows:</p>
                      <div class="exampleOuter">
!                         <p 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]
***************
*** 852,856 ****
                      <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]
--- 861,865 ----
                      <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]
***************
*** 907,911 ****
                      <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>
--- 916,920 ----
                      <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>
***************
*** 928,933 ****
                          <p> [fault name] = InvalidDate</p>
                          <p>Applying the pattern above with these values we have:</p>
!                         <p>input action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/CheckAvailability</p>
!                         <p>output action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/Availability</p>
                          <p>fault action =
                              http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailability/Fault/InvalidDate</p>
--- 937,944 ----
                          <p> [fault name] = InvalidDate</p>
                          <p>Applying the pattern above with these values we have:</p>
!                         <p>input action =
!                             http://greath.example.com/2004/wsdl/resSvc/reservationInterface/CheckAvailability</p>
!                         <p>output action =
!                             http://greath.example.com/2004/wsdl/resSvc/reservationInterface/Availability</p>
                          <p>fault action =
                              http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailability/Fault/InvalidDate</p>
***************
*** 936,940 ****
                          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>
--- 947,951 ----
                          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>
***************
*** 968,996 ****
                  </div>
              </div>
-             <div class="div2">
-                 
- <h3><a name="refpinwsdl"></a>4.3 Reference Parameters</h3>
-                 <p>The wsa:ReferenceParameters element (see Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>]) MAY be used as an extension child element of the
-                     wsdl20:endpoint or wsdl11:port elements. When present, the value of the
-                     [reference parameters] message addressing property for a message sent to an
-                     endpoint MUST include the contents of the wsa:ReferenceParameters WSDL extension
-                     element.</p>
-                 <div class="div3">
-                     
- <h4><a name="refpinwsdlcm"></a>4.3.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>
-                     <ul>
-                         <li>
-                             <p>A property of the Endpoint component, named {reference parameters}.
-                                 This property is of type xs:any, with a cardinality of 0 to
-                                 unbounded. The property has the value of the [reference parameters]
-                                 message addressing property, if present; there is no default value -
-                                 if the [reference parameters] message addressing property is not
-                                 present, this property is likewise absent.</p>
-                         </li>
-                     </ul>
-                 </div>             
-             </div>
          </div>
          <div class="div1">
--- 979,982 ----
***************
*** 1003,1008 ****
  <h3><a name="WSDL11MEPS"></a>5.1 WSDL 1.1 Message Exchange Patterns</h3>
                  <p> For backwards compatibility, this section describes which of the core message
!                     properties are mandatory  for messages in the various MEPs defined by
!                     WSDL 1.1. </p>
                  <div class="div3">
                      
--- 989,993 ----
  <h3><a name="WSDL11MEPS"></a>5.1 WSDL 1.1 Message Exchange Patterns</h3>
                  <p> For backwards compatibility, this section describes which of the core message
!                     properties are mandatory for messages in the various MEPs defined by WSDL 1.1. </p>
                  <div class="div3">
                      
***************
*** 1195,1200 ****
                  
  <h3><a name="WSDL20MEPS"></a>5.2 WSDL 2.0 Message Exchange Patterns</h3>
!                 <p> This section describes which of the core message properties are mandatory
!                     for messages in the various MEPs defined by WSDL 2.0 [<cite><a href="#WSDL20Adj">WSDL 2.0 Adjuncts</a></cite>]. </p>
                  <div class="div3">
                      
--- 1180,1185 ----
                  
  <h3><a name="WSDL20MEPS"></a>5.2 WSDL 2.0 Message Exchange Patterns</h3>
!                 <p> This section describes which of the core message properties are mandatory for
!                     messages in the various MEPs defined by WSDL 2.0 [<cite><a href="#WSDL20Adj">WSDL 2.0 Adjuncts</a></cite>]. </p>
                  <div class="div3">
                      
***************
*** 1532,1540 ****
                  indirectly one or more of the <a href="#uaee"><b>3.1 UsingAddressing Extension Element</b></a> or the <a href="#wsdlsoapmodule"><b>3.3 WSDL SOAP Module</b></a> markers, and obeys the structural constraints defined in
                  section <a href="#indicatinguse"><b>3. Indicating Use of WS-Addressing</b></a> appropriate to that marker, and those defined
!                 in section <a href="#actioninwsdl"><b>4.2 Action</b></a>. </p>
              <p> An endpoint conforms to this specification if it has a conformant WSDL description
                  associated with it, and receives and emits messages in accordance with the
                  constraints defined in sections <a href="#mapvaluesinwsdl"><b>4. Specifying Message Addressing Properties in WSDL</b></a> and <a href="#WSDLMEPS"><b>5. WS-Addressing and WSDL Message Exchange Patterns</b></a>. </p>
!         </div>     
          <div class="div1">
              
--- 1517,1525 ----
                  indirectly one or more of the <a href="#uaee"><b>3.1 UsingAddressing Extension Element</b></a> or the <a href="#wsdlsoapmodule"><b>3.3 WSDL SOAP Module</b></a> markers, and obeys the structural constraints defined in
                  section <a href="#indicatinguse"><b>3. Indicating Use of WS-Addressing</b></a> appropriate to that marker, and those defined
!                 in section <a href="#actioninwsdl"><b>4.4 Action</b></a>. </p>
              <p> An endpoint conforms to this specification if it has a conformant WSDL description
                  associated with it, and receives and emits messages in accordance with the
                  constraints defined in sections <a href="#mapvaluesinwsdl"><b>4. Specifying Message Addressing Properties in WSDL</b></a> and <a href="#WSDLMEPS"><b>5. WS-Addressing and WSDL Message Exchange Patterns</b></a>. </p>
!         </div>
          <div class="div1">
              
***************
*** 1542,1548 ****
              <dl>
                  <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
!                     <cite><a href="ws-addr-core.html">Web Services Addressing 1.0 - Core</a></cite>, M. Gudgin, M. Hadley, T. Rogers, Editors.</dd>
                  <dt class="label"><a name="WSADDR-SOAP"></a>[WS-Addressing-SOAP] </dt><dd>
!                     <cite><a href="ws-addr-soap.html">Web Services Addressing 1.0 - SOAP Binding</a></cite>, M. Gudgin, M. Hadley, T. Rogers, Editors.</dd>
                  <dt class="label"><a name="WSDL20"></a>[WSDL 2.0] </dt><dd>
                      <cite><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060106/">Web Services Description Language (WSDL) Version 2.0 Part 1: Core
--- 1527,1535 ----
              <dl>
                  <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
!                     <cite><a href="ws-addr-core.html">Web Services Addressing 1.0 - Core</a></cite>, M. Gudgin, M. Hadley, T. Rogers,
!                     Editors.</dd>
                  <dt class="label"><a name="WSADDR-SOAP"></a>[WS-Addressing-SOAP] </dt><dd>
!                     <cite><a href="ws-addr-soap.html">Web Services Addressing 1.0 - SOAP Binding</a></cite>, M. Gudgin, M. Hadley, T. Rogers,
!                     Editors.</dd>
                  <dt class="label"><a name="WSDL20"></a>[WSDL 2.0] </dt><dd>
                      <cite><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060106/">Web Services Description Language (WSDL) Version 2.0 Part 1: Core
***************
*** 1552,1560 ****
                      available at http://www.w3.org/TR/wsdl20.</dd>
                  <dt class="label"><a name="WSDL20Adj"></a>[WSDL 2.0 Adjuncts] </dt><dd>
!                     <cite><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/">Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts</a></cite>,
! 		    R. Chinnici, H. Haas, A. Lewis, J. J. Moreau, D. Orchard, S. Weerawarana,
!                     Editors. World Wide Web Consortium, 6 January 2006. This version of the WSDL 2.0
!                     Adjuncts specification is 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="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 Levels</a></cite>,
--- 1539,1548 ----
                      available at http://www.w3.org/TR/wsdl20.</dd>
                  <dt class="label"><a name="WSDL20Adj"></a>[WSDL 2.0 Adjuncts] </dt><dd>
!                     <cite><a href="http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060106/">Web Services Description Language (WSDL) Version 2.0 Part 2:
!                     Adjuncts</a></cite>, R. Chinnici, H. Haas, A. Lewis, J. J. Moreau, D. Orchard,
!                     S. Weerawarana, Editors. World Wide Web Consortium, 6 January 2006. This version
!                     of the WSDL 2.0 Adjuncts specification is
!                     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="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 Levels</a></cite>,
***************
*** 1670,1689 ****
              <div class="div2">
                  
! <h3><a name="N10D4E"></a>C.1 Changes Since Third Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-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 (n..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 {reference 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: aded 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 on Robust In-Only</td></tr><tr><td>2006-03-03 @ 14:10</td><td>mhadley</td><td>Fixed editor list in references</td></tr><tr><td>2006-03-03 @ 13:48</td><td>mhadley</td><td>Added resolution to LC115 - definition to description for WSDL 2.0</td></tr><tr><td>2006-03-03 @ 13:45</td><td>mhadley</td><td>Added resolution to LC114 - typos</td></tr><tr><td>2006-02-22 @ 14:22</td><td>mhadley</td><td>Fixed a typo: 'by by' to 'by'</d></tr><tr><td>2006-02-13 @ 20:15</td><td>mhadley</td><td>Removed ed notes</td></tr><tr><td>2006-02-13 @ 16:56</td><td>mhadley</td><td>A few grammar fixes and noted that wsaw:Anonymous with a value of optional is equivalent to the default.</td></tr><tr><td>2006-02-13 @ 16:45</td><td>mhadley</td><td>Added resolution to issue 70, soften language on defining value of [destination] to allow runtime override.</td></tr><tr><td>2006-02-13 @ 15:50</td><td>mhadley</td><td>Added resolution to issue 66, explicit note that wsaw:UsingAddressing could be used outside WSDL, e.g. in a policy framework</td></tr><tr><td>2006-01-19 @ 20:37</td><td>mhadley</td><td>Fixed some grammar errors</td></tr><tr><td>2006-01-08 @ 23:14</td><td>trogers</td><td>Umit's description of the Anonymous element added; Umit added to editor list.</td></tr><tr><td>2005-11-22 @ 21:29</td><td>mhadley</td><td>Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model</td></tr><tr><td>2005-11-07 @ 7: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. Addd clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resoluion - 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="N10D58"></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="N10D62"></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="N10D6C"></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>
--- 1658,1682 ----
              <div class="div2">
                  
! <h3><a name="N68958"></a>C.1 Changes Since Last Call Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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 (n..m) notation to wsaw:InterfaceName, wsaw:ServiceName and wsaw:ServiceName/@EndpointName descriptions</td></tr><tr><td>2006-04-26 @ 15:28</td><d>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 {reference parameters} property from REQUIRED to OPTIONAL in the component model. This completes LC116.</td></tr><tr><td>2006-03-27 @ 19:48</td><td>madley</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 on Robust In-Only</td></tr><tr><td>2006-03-03 @ 14:10</td><td>mhadley</td><td>Fixed editor list in references</td></tr><tr><td>2006-03-03 @ 13:48/td><td>mhadley</td><td>Added resolution to LC115 - definition to description for WSDL 2.0</td></tr><tr><td>2006-03-03 @ 13:45</td><td>mhadley</td><td>Added resolution to LC114 - typos</td></tr><tr><td>2006-02-22 @ 14:22</td><td>mhadley</td><td>Fixed a typo: 'by by' to 'by'</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N68968"></a>C.2 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="N68978"></a>C.3 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="N68988"></a>C.4 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="N68998"></a>C.5 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, 28 April 2006 15:11:37 GMT

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