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

2004/ws/addressing ws-addr-core.html,1.24,1.25 ws-addr-soap.html,1.29,1.30 ws-addr-wsdl.html,1.24,1.25

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 18 May 2005 19:53:45 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1DYUbx-0002p1-HO@lionel-hutz.w3.org>

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

Modified Files:
	ws-addr-core.html ws-addr-soap.html ws-addr-wsdl.html 
Log Message:
Updated to sync with XML

Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -d -r1.24 -r1.25
*** ws-addr-wsdl.html	22 Apr 2005 22:39:41 -0000	1.24
--- ws-addr-wsdl.html	18 May 2005 19:53:43 -0000	1.25
***************
*** 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>
***************
*** 66,71 ****
          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="#N101C3">Indicating Use of WS-Addressing</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#N101CB">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#N101FA">WSDL SOAP Module</a><br>4. <a href="#actioninwsdl"> Associating Action with WSDL Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#explicitaction"> Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4. <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.1 <a href="#wsdl11oneway">One-way</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.3 <a href="#wsdl11notification">Notification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#wsdl20inonly">In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3 <a href="#wsdl2inout">In-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5 <a href="#wsdl20outonly">Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.7 <a href="#wsdl20outin">Out-in</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#references"> References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N10B29">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N10B33">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N10B3D">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
--- 66,71 ----
          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="#N65987">Indicating Use of WS-Addressing</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#N65995">UsingAddressing Extension Element</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#N66042">WSDL SOAP Module</a><br>4. <a href="#actioninwsdl"> Associating Action with WSDL Operations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#explicitaction"> Explicit Association</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4. <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.1 <a href="#wsdl11oneway">One-way</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.3 <a href="#wsdl11notification">Notification</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.1 <a href="#wsdl20inonly">In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.3 <a href="#wsdl2inout">In-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.5 <a href="#wsdl20outonly">Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.7 <a href="#wsdl20outin">Out-in</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#references"> References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N68393">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N68403">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N68413">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 194,198 ****
                      "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
--- 194,198 ----
                      "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
***************
*** 233,237 ****
                      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
--- 233,237 ----
                      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
***************
*** 267,271 ****
                  </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
--- 267,271 ----
                  </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
***************
*** 300,309 ****
          <div class="div1">
              
! <h2><a name="N101C3"></a>3. Indicating Use of WS-Addressing</h2>
              <p>This specification supports two mechanisms for indicating, in a WSDL
                  description, that the endpoint conforms to the WS-Addressing specification. </p>
              <div class="div2">
                  
! <h3><a name="N101CB"></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.
--- 300,309 ----
          <div class="div1">
              
! <h2><a name="N65987"></a>3. Indicating Use of WS-Addressing</h2>
              <p>This specification supports two mechanisms for indicating, in a WSDL
                  description, that the endpoint conforms to the WS-Addressing specification. </p>
              <div class="div2">
                  
! <h3><a name="N65995"></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.
***************
*** 341,345 ****
                      address with a value different from the anonymous URI.</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"
--- 341,345 ----
                      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"
***************
*** 353,357 ****
                  </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;
--- 353,357 ----
                  </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;
***************
*** 371,375 ****
              <div class="div2">
                  
! <h3><a name="N101FA"></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 
--- 371,375 ----
              <div class="div2">
                  
! <h3><a name="N66042"></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 
***************
*** 382,386 ****
                      the following URI: http://www.w3.org/@@@@/@@/addressing/module</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><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"
--- 382,386 ----
                      the following URI: 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"
***************
*** 415,419 ****
                  <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;
--- 415,419 ----
                  <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;
***************
*** 434,438 ****
                      action for the output of this same operation is 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;
--- 434,438 ----
                      action for the output of this same operation is 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;
***************
*** 461,465 ****
                      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]
--- 461,465 ----
                      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]
***************
*** 468,472 ****
                  <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]
--- 468,472 ----
                  <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]
***************
*** 555,559 ****
                  <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>
--- 555,559 ----
                  <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>
***************
*** 588,592 ****
                      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]
--- 588,592 ----
                      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]
***************
*** 595,599 ****
                  <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]Fault:[fault name]
--- 595,599 ----
                  <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]Fault:[fault name]
***************
*** 648,652 ****
                  <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>
--- 648,652 ----
                  <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>
***************
*** 677,681 ****
                      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>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
--- 677,681 ----
                      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>
  &lt;definitions targetNamespace="http://example.com/stockquote" ...&gt;
***************
*** 694,698 ****
                      <p>According to the rules defined in <a href="http://www.w3.org/TR/wsdl#_names">Section 2.4.5</a> of WSDL
                          1.1, if the name attribute is absent for the input of a request response
!                         operation the default value is the name of the operation "Request" appended.</p>
                      <p> [input name] = GetLastTradePriceRequest</p>
                      <p>Likewise, the output defaults to the operation name with "Response" appended.</p>
--- 694,698 ----
                      <p>According to the rules defined in <a href="http://www.w3.org/TR/wsdl#_names">Section 2.4.5</a> of WSDL
                          1.1, if the name attribute is absent for the input of a request response
!                         operation the default value is the name of the operation with "Request" appended.</p>
                      <p> [input name] = GetLastTradePriceRequest</p>
                      <p>Likewise, the output defaults to the operation name with "Response" appended.</p>
***************
*** 1026,1030 ****
                          </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">
--- 1026,1030 ----
                          </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">
***************
*** 1082,1086 ****
                          </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>
--- 1082,1086 ----
                          </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>
***************
*** 1248,1252 ****
                      Gudgin, J. J. Moreau, J. Schlimmer, S. Weerawarana, Editors. World Wide Web
                      Consortium, 3 August 2004. This version of the WSDL 2.0 specification is
!                     http://www.w3.org/TR/2004/WD-wsdl20-20040803. The <a href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</a> is
                      available at http://www.w3.org/TR/wsdl20.</dd>
                  <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
--- 1248,1252 ----
                      Gudgin, J. J. Moreau, J. Schlimmer, S. Weerawarana, Editors. World Wide Web
                      Consortium, 3 August 2004. This version of the WSDL 2.0 specification is
!                     http://www.w3.org/TR/2005/WD-wsdl20-20050510. The <a href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</a> is
                      available at http://www.w3.org/TR/wsdl20.</dd>
                  <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
***************
*** 1322,1336 ****
              <div class="div2">
                  
! <h3><a name="N10B29"></a>B.1 Changes Since Second Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></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 resoluion to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added resolution to issue 45</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N10B33"></a>B.2 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="N10B3D"></a>B.3 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>
--- 1322,1336 ----
              <div class="div2">
                  
! <h3><a name="N68393"></a>B.1 Changes Since Second Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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><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 resolution to issue 45</td></tr></table>
              </div>
              <div class="div2">
                  
! <h3><a name="N68403"></a>B.2 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="N68413"></a>B.3 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>

Index: ws-addr-core.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -C2 -d -r1.24 -r1.25
*** ws-addr-core.html	22 Apr 2005 20:17:46 -0000	1.24
--- ws-addr-core.html	18 May 2005 19:53:43 -0000	1.25
***************
*** 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 - Core</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 - Core</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 - Core</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 - Core</h1>
***************
*** 70,79 ****
          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="#eprs">Endpoint References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#eprinfomodel">Information Model for Endpoint References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#eprinfoset">Endpoint Reference XML Infoset Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#eprcomp">Endpoint Reference Comparison</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#eprlifecycle">Endpoint Reference Lifecycle</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.5 <a href="#eprextensibility">Endpoint Reference Extensibility</a><br>3. <a href="#msgaddrprops">Message Addressing Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#msgaddrpropsinfoset">XML Infoset Representation of Message Addressing Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.1.1 <a hrf="#compiri">Comparing IRIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#formreplymsg">Formulating a Reply Message</a><br>4. <a href="#securityconsiderations">Security Considerations</a><br>5. <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="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N105E3">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N105ED">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N105F7">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
  <h2><a name="tocRange"></a>1. Introduction</h2>
!             <p>Web Services Addressing (WS-Addressing) defines two constructs, message addressing
                  properties and endpoint references, that normalize the information typically
                  provided by transport protocols and messaging systems in a way that is independent
--- 70,79 ----
          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="#eprs">Endpoint References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#eprinfomodel">Information Model for Endpoint References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#eprinfoset">Endpoint Reference XML Infoset Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#eprcomp">Endpoint Reference Comparison</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#eprlifecycle">Endpoint Reference Lifecycle</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.5 <a href="#eprextensibility">Endpoint Reference Extensibility</a><br>3. <a href="#msgaddrprops">Message Addressing Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#abstractmaps">Abstract Property Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#msgaddrpropsinfoset">XML Infoset Representation of MessageAddressing Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#compiri">Comparing IRIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#formreplymsg">Formulating a Reply Message</a><br>4. <a href="#securityconsiderations">Security Considerations</a><br>5. <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="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N67090">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N67100">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N67110">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
  <h2><a name="tocRange"></a>1. Introduction</h2>
!             <p>Web Services Addressing 1.0 - Core (WS-Addressing) defines two constructs, message addressing
                  properties and endpoint references, that normalize the information typically
                  provided by transport protocols and messaging systems in a way that is independent
***************
*** 91,121 ****
              <p>The following example illustrates the use of these mechanisms in a SOAP 1.2 message
                  being sent from http://example.com/business/client1 to
!                 http://example.com/fabrikam/Purchasing:</p>
              <div class="exampleOuter">
!                 <p class="exampleHead" style="text-align: left"><i><span>Example 1-1. </span>Use of message addressing properties in a SOAP 1.2 message.</i></p>
                  <div class="exampleInner"><pre>
! (001) &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"      
                  xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"&gt;
! (002)   &lt;S:Header&gt;
! (003)    &lt;wsa:MessageID&gt;http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA&lt;/wsa:MessageID&gt;
! (004)    &lt;wsa:ReplyTo&gt;
! (005)      &lt;wsa:Address&gt;http://example.com/business/client1&lt;/wsa:Address&gt;
! (006)    &lt;/wsa:ReplyTo&gt;
! (007)    &lt;wsa:To&gt;http://example.com/fabrikam/Purchasing&lt;/wsa:To&gt;
! (008)    &lt;wsa:Action&gt;http://example.com/fabrikam/SubmitPO&lt;/wsa:Action&gt;
! (009)   &lt;/S:Header&gt;
! (010)   &lt;S:Body&gt;
! (011)     ...
! (012)   &lt;/S:Body&gt;
! (013) &lt;/S:Envelope&gt;
  </pre></div>
!                 <p>Lines (002) to (009) represent the header of the SOAP message where the
                      mechanisms defined in the specification are used. The body is represented by
!                     lines (010) to (012).</p>
!                 <p>Lines (003) to (008) contain the message information header blocks. Specifically,
!                     line (002) specifies the identifier for this message and lines (004) to (006)
                      specify the endpoint to which replies to this message should be sent as an
!                     Endpoint Reference. Line (007) specifies the address URI of the ultimate
!                     receiver of this message. Line (008) specifies an action URI identifying
                      expected semantics.</p>
              </div>
--- 91,122 ----
              <p>The following example illustrates the use of these mechanisms in a SOAP 1.2 message
                  being sent from http://example.com/business/client1 to
!                 http://example.com/fabrikam/Purchasing (see Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]
!                 for more information on the use of WS-Addressing in SOAP):</p>
              <div class="exampleOuter">
!                 <p style="text-align: left" class="exampleHead"><i><span>Example 1-1. </span>Use of message addressing properties in a SOAP 1.2 message.</i></p>
                  <div class="exampleInner"><pre>
! (01) &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"      
                  xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"&gt;
! (02)   &lt;S:Header&gt;
! (03)    &lt;wsa:MessageID&gt;http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA&lt;/wsa:MessageID&gt;
! (04)    &lt;wsa:ReplyTo&gt;
! (05)      &lt;wsa:Address&gt;http://example.com/business/client1&lt;/wsa:Address&gt;
! (06)    &lt;/wsa:ReplyTo&gt;
! (07)    &lt;wsa:To&gt;http://example.com/fabrikam/Purchasing&lt;/wsa:To&gt;
! (08)    &lt;wsa:Action&gt;http://example.com/fabrikam/SubmitPO&lt;/wsa:Action&gt;
! (09)   &lt;/S:Header&gt;
! (10)   &lt;S:Body&gt;
! (11)     ...
! (12)   &lt;/S:Body&gt;
! (13) &lt;/S:Envelope&gt;
  </pre></div>
!                 <p>Lines (02) to (09) represent the header of the SOAP message where the
                      mechanisms defined in the specification are used. The body is represented by
!                     lines (10) to (12).</p>
!                 <p>Lines (03) to (08) contain the message information header blocks. Specifically,
!                     line (02) specifies the identifier for this message and lines (04) to (06)
                      specify the endpoint to which replies to this message should be sent as an
!                     endpoint reference. Line (07) specifies the address URI of the ultimate
!                     receiver of this message. Line (08) specifies an action URI identifying
                      expected semantics.</p>
              </div>
***************
*** 132,136 ****
                  <p>When describing concrete XML schemas [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>], this specification uses the notational convention of
                      WS-Security [<cite><a href="#WS-Security">WS-Security</a></cite>]. Specifically, each member of an
!                     element's [children] or [attributes] property is described using an XPath-like
                      notation (e.g., /x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates
                      the presence of an element wildcard (&lt;xs:any/&gt;). The use of @{any}
--- 133,137 ----
                  <p>When describing concrete XML schemas [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>], this specification uses the notational convention of
                      WS-Security [<cite><a href="#WS-Security">WS-Security</a></cite>]. Specifically, each member of an
!                     Element Information Item's [children] or [attributes] property is described using an XPath-like
                      notation (e.g., /x:MyHeader/x:SomeProperty/@value1). The use of {any} indicates
                      the presence of an element wildcard (&lt;xs:any/&gt;). The use of @{any}
***************
*** 143,148 ****
                  <p> This specification uses a number of namespace prefixes throughout; they are
                      listed in <a href="#nsprefix">Table 1-1</a>. Note that the choice of any namespace
!                     prefix is arbitrary and not semantically significant (see [<cite><a href="#XMLNS">XML Namespaces</a></cite>
!                     ]).</p>
                  <a name="nsprefix"></a><table summary="Namespace prefixes usage in this specification" border="1">
                      <caption>Table 1-1. Prefixes and Namespaces used in this specification</caption>
--- 144,149 ----
                  <p> This specification uses a number of namespace prefixes throughout; they are
                      listed in <a href="#nsprefix">Table 1-1</a>. Note that the choice of any namespace
!                     prefix is arbitrary and not semantically significant (see 
!                     [<cite><a href="#XMLNS">XML Namespaces</a></cite>]).</p>
                  <a name="nsprefix"></a><table summary="Namespace prefixes usage in this specification" border="1">
                      <caption>Table 1-1. Prefixes and Namespaces used in this specification</caption>
***************
*** 166,177 ****
                      </tbody>
                  </table><br>
!                 <p>WS-Addressing may be used with SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>] as described
                      in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. WS-Addressing may be used
!                     with WSDL [<cite><a href="#WSDL20">WSDL 2.0</a></cite>] described services as described in
                          Web Services Addressing 1.0 - WSDL Binding[<cite><a href="#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>]. Examples in this
                      specification use an XML 1.0 [<cite><a href="#XML10">XML 1.0</a></cite>] representation but this is
                      not a requirement.</p>
                  <p>All information items defined by this specification are identified by the XML
!                     namespace URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>] "http://www.w3.org/@@@@/@@/addressing". A normative XML Schema
                          [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document can be
                      obtained by dereferencing the XML namespace URI.</p>
--- 167,178 ----
                      </tbody>
                  </table><br>
!                 <p>WS-Addressing may be used with SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>, <cite><a href="#SOAP11">SOAP 1.1</a></cite>] as described
                      in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. WS-Addressing may be used
!                     with WSDL [<cite><a href="#WSDL20">WSDL 2.0</a></cite>, <cite><a href="#WSDL11">WSDL 1.1</a></cite>] described services as described in
                          Web Services Addressing 1.0 - WSDL Binding[<cite><a href="#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>]. Examples in this
                      specification use an XML 1.0 [<cite><a href="#XML10">XML 1.0</a></cite>] representation but this is
                      not a requirement.</p>
                  <p>All information items defined by this specification are identified by the XML
!                     namespace URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>] <a href="http://www.w3.org/@@@@/@@/addressing">http://www.w3.org/@@@@/@@/addressing</a>. A normative XML Schema
                          [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document can be
                      obtained by dereferencing the XML namespace URI.</p>
***************
*** 238,249 ****
                                  generated.</p>
                              <p>The metadata embedded in an EPR is not necessarily a complete
!                                 statement of the metadata pertaining to the endpoint.Moreover, while
                                  embedded metadata is necessarily valid at the time the EPR is
                                  initially created it may become stale at a later point in time.</p>
!                             <p>To deal with conflicts between the embedded metadata of two EPRs, or
                                  between embedded metadata and metadata obtained from a different
                                  source, or to ascertain the current validity of embedded metadata,
                                  mechanisms that are outside of the scope of this specification, such
!                                 as EPR life cycle information <a href="#eprlifecycle"><b>2.4 Endpoint Reference Lifecycle</b></a> or
                                  retrieval of metadata from an authoritative source, SHOULD be
                              used.</p>
--- 239,251 ----
                                  generated.</p>
                              <p>The metadata embedded in an EPR is not necessarily a complete
!                                 statement of the metadata pertaining to the endpoint. Moreover, while
                                  embedded metadata is necessarily valid at the time the EPR is
                                  initially created it may become stale at a later point in time.</p>
!                             <p>To deal with conflicts between the embedded metadata of two EPRs
!                                 that have the same [address], or
                                  between embedded metadata and metadata obtained from a different
                                  source, or to ascertain the current validity of embedded metadata,
                                  mechanisms that are outside of the scope of this specification, such
!                                 as EPR life cycle information (see <a href="#eprlifecycle"><b>2.4 Endpoint Reference Lifecycle</b></a>) or
                                  retrieval of metadata from an authoritative source, SHOULD be
                              used.</p>
***************
*** 257,261 ****
                  <p>This section defines an XML Infoset-based representation for an endpoint
                      reference as both an XML type (wsa:EndpointReferenceType) and as an XML element
!                     (&lt;wsa:EndpointReference&gt;).</p>
                  <p>The wsa:EndpointReferenceType type is used wherever a Web service endpoint is
                      referenced. The following describes the contents of this type:</p>
--- 259,266 ----
                  <p>This section defines an XML Infoset-based representation for an endpoint
                      reference as both an XML type (wsa:EndpointReferenceType) and as an XML element
!                     (&lt;wsa:EndpointReference&gt;). For brevity simple XML terms are used, e.g. 
!                     'element' instead of 'element information item' - this is not intended to 
!                     constrain use of the constructs defined in this section to textual XML
!                     representations.</p>
                  <p>The wsa:EndpointReferenceType type is used wherever a Web service endpoint is
                      referenced. The following describes the contents of this type:</p>
***************
*** 352,358 ****
                  </dl>
                  <p>The following shows an example endpoint reference. This element references the
!                     the endpoint at the URI "http://example.com/www.fabrikam/acct".</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 xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"&gt;
--- 357,363 ----
                  </dl>
                  <p>The following shows an example endpoint reference. This element references the
!                     the endpoint at the URI "http://example.com/fabrikam/acct".</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 xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"&gt;
***************
*** 426,430 ****
              <p> The basic interaction pattern from which all others are composed is "one way". In
                  this pattern a source sends a message to a destination without any further
!                 definition of the interaction. "Request Reply" is a common interaction pattern that
                  consists of an initial message sent by a source endpoint (the request) and a
                  subsequent message sent from the destination of the request back to the source (the
--- 431,435 ----
              <p> The basic interaction pattern from which all others are composed is "one way". In
                  this pattern a source sends a message to a destination without any further
!                 definition of the interaction. "Request/Reply" is a common interaction pattern that
                  consists of an initial message sent by a source endpoint (the request) and a
                  subsequent message sent from the destination of the request back to the source (the
***************
*** 439,442 ****
--- 444,452 ----
                  require additional message addressing properties to augment the facilities provided
                  here. </p>
+  
+             <div class="div2">
+                 
+ <h3><a name="abstractmaps"></a>3.1 Abstract Property Definitions</h3>
+             
              <p>Message addressing properties collectively augment a message with the following
                  abstract properties to support one way, request reply, and other interaction
***************
*** 462,466 ****
                              message. If a reply is expected, a message MUST contain a [reply
                              endpoint]. The sender MUST use the contents of the [reply endpoint] to
!                             formulate the reply message as defined in <a href="#formreplymsg"><b>3.2 Formulating a Reply Message</b></a>.
                              If this property is present, the [message id] property is REQUIRED.</p>
                      </dd>
--- 472,476 ----
                              message. If a reply is expected, a message MUST contain a [reply
                              endpoint]. The sender MUST use the contents of the [reply endpoint] to
!                             formulate the reply message as defined in <a href="#formreplymsg"><b>3.3 Formulating a Reply Message</b></a>.
                              If this property is present, the [message id] property is REQUIRED.</p>
                      </dd>
***************
*** 470,474 ****
                      <dd>
                          <p>An endpoint reference for the intended receiver for faults related to
!                             this message. When formulating a fault message as defined in <a href="#formreplymsg"><b>3.2 Formulating a Reply Message</b></a>, the sender MUST use the contents of the [fault
                              endpoint], when present, of the message being replied to formulate the
                              fault message. If this property is present, the [message id] property is
--- 480,484 ----
                      <dd>
                          <p>An endpoint reference for the intended receiver for faults related to
!                             this message. When formulating a fault message as defined in <a href="#formreplymsg"><b>3.3 Formulating a Reply Message</b></a>, the sender MUST use the contents of the [fault
                              endpoint], when present, of the message being replied to formulate the
                              fault message. If this property is present, the [message id] property is
***************
*** 482,486 ****
                              message.</p>
                          <p>It is RECOMMENDED that the value of the [action] property is an IRI
!                             identifying an input, output, or fault message within a WSDL port type.
                              An action may be explicitly or implicitly associated with the
                              corresponding WSDL definition. Web Services Addressing 1.0 - WSDL Binding[<cite><a href="#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>] describes the mechanisms of association.</p>
--- 492,496 ----
                              message.</p>
                          <p>It is RECOMMENDED that the value of the [action] property is an IRI
!                             identifying an input, output, or fault message within a WSDL interface.
                              An action may be explicitly or implicitly associated with the
                              corresponding WSDL definition. Web Services Addressing 1.0 - WSDL Binding[<cite><a href="#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>] describes the mechanisms of association.</p>
***************
*** 492,496 ****
                          <p>An absolute IRI that uniquely identifies this message in time and space.
                              No two messages with a distinct application intent may share a [message
!                             id] property. A message MAY be retransmitted for any purpose including
                              communications failure and MAY use the same [message id] property. The
                              value of this property is an opaque IRI whose interpretation beyond
--- 502,506 ----
                          <p>An absolute IRI that uniquely identifies this message in time and space.
                              No two messages with a distinct application intent may share a [message
!                             id] property. A message MAY be retransmitted for any reason including
                              communications failure and MAY use the same [message id] property. The
                              value of this property is an opaque IRI whose interpretation beyond
***************
*** 548,573 ****
                  endpoint. To allow these "anonymous" endpoints to send and receive messages,
                  WS-Addressing defines the following well-known URI for use by endpoints that cannot
!                 have a stable, resolvable IRI: "http://www.w3.org/@@@@/@@/addressing/role/anonymous"
              </p>
              <p>Requests whose [reply endpoint], [source endpoint] and/or [fault endpoint] use this
                  address MUST provide some out-of-band mechanism for delivering replies or faults
                  (e.g. returning the reply on the same transport connection).</p>
              <div class="div2">
                  
! <h3><a name="msgaddrpropsinfoset"></a>3.1 XML Infoset Representation of Message Addressing Properties</h3>
                  <p>Message addressing properties provide end-to-end characteristics of a message
                      that can be easily secured as a unit. These properties are immutable and not
                      intended to be modified along a message path. </p>
!                 <p>The following shows the XML Infoset representation of message addressing
!                     properties:</p>
                  <div class="exampleInner"><pre>
- &lt;wsa:MessageID&gt;xs:anyURI &lt;/wsa:MessageID&gt;
- &lt;wsa:RelatesTo RelationshipType="xs:anyURI"?&gt;xs:anyURI&lt;/wsa:RelatesTo&gt;
  &lt;wsa:To&gt;xs:anyURI&lt;/wsa:To&gt;
- &lt;wsa:Action&gt;xs:anyURI&lt;/wsa:Action&gt;
  &lt;wsa:From&gt;endpoint-reference&lt;/wsa:From&gt;
  &lt;wsa:ReplyTo&gt;endpoint-reference&lt;/wsa:ReplyTo&gt;
  &lt;wsa:FaultTo&gt;endpoint-reference&lt;/wsa:FaultTo&gt;
! &lt;wsa:ReferenceParameters&gt;xs:any*&lt;/wsa:FaultTo&gt;
                      </pre></div>
                  <p>The following describes the attributes and elements listed in the schema overview
--- 558,585 ----
                  endpoint. To allow these "anonymous" endpoints to send and receive messages,
                  WS-Addressing defines the following well-known URI for use by endpoints that cannot
!                 have a stable, resolvable IRI: "http://www.w3.org/@@@@/@@/addressing/address/anonymous"
              </p>
              <p>Requests whose [reply endpoint], [source endpoint] and/or [fault endpoint] use this
                  address MUST provide some out-of-band mechanism for delivering replies or faults
                  (e.g. returning the reply on the same transport connection).</p>
+             </div>
+             
              <div class="div2">
                  
! <h3><a name="msgaddrpropsinfoset"></a>3.2 XML Infoset Representation of Message Addressing Properties</h3>
                  <p>Message addressing properties provide end-to-end characteristics of a message
                      that can be easily secured as a unit. These properties are immutable and not
                      intended to be modified along a message path. </p>
!                 <p>The following shows the XML Infoset representation of the message addressing
!                     properties define in <a href="#abstractmaps"><b>3.1 Abstract Property Definitions</b></a>:</p>
                  <div class="exampleInner"><pre>
  &lt;wsa:To&gt;xs:anyURI&lt;/wsa:To&gt;
  &lt;wsa:From&gt;endpoint-reference&lt;/wsa:From&gt;
  &lt;wsa:ReplyTo&gt;endpoint-reference&lt;/wsa:ReplyTo&gt;
  &lt;wsa:FaultTo&gt;endpoint-reference&lt;/wsa:FaultTo&gt;
! &lt;wsa:Action&gt;xs:anyURI&lt;/wsa:Action&gt;
! &lt;wsa:MessageID&gt;xs:anyURI &lt;/wsa:MessageID&gt;
! &lt;wsa:RelatesTo RelationshipType="xs:anyURI"?&gt;xs:anyURI&lt;/wsa:RelatesTo&gt;
! &lt;wsa:ReferenceParameters&gt;xs:any*&lt;/wsa:ReferenceParameters&gt;
                      </pre></div>
                  <p>The following describes the attributes and elements listed in the schema overview
***************
*** 575,609 ****
                  <dl>
                      
!                         <dt class="label"> /wsa:MessageID</dt>
!                         <dd>
!                             <p>This OPTIONAL element (of type xs:anyURI) conveys the [message id]
!                                 property. This element MUST be present if wsa:ReplyTo or wsa:FaultTo
!                                 is present.</p>
!                         </dd>
!                     
!                 </dl>
!                 <dl>
!                     
!                         <dt class="label"> /wsa:RelatesTo</dt>
                          <dd>
!                             <p>This OPTIONAL (repeating) element information item contributes one
!                                 abstract [relationship] property value, in the form of a (IRI, IRI)
!                                 pair. The [children] property of this element (which is of type
!                                 xs:anyURI) conveys the [message id] of the related message. This
!                                 element MUST be present if the message is a reply.</p>
                          </dd>
                      
-                 </dl>
-                 <dl>
                      
!                         <dt class="label"> /wsa:RelatesTo/@RelationshipType</dt>
                          <dd>
!                             <p>This OPTIONAL attribute (of type xs:anyURI) conveys the relationship
!                                 type as an IRI. When absent, the implied value of this attribute is
!                                     "http://www.w3.org/@@@@/@@/addressing/reply".</p>
                          </dd>
                      
-                 </dl>
-                 <dl>
                      
                          <dt class="label"> /wsa:ReplyTo</dt>
--- 587,605 ----
                  <dl>
                      
!                         <dt class="label"> /wsa:To</dt>
                          <dd>
!                             <p>This OPTIONAL element (of type xs:anyURI) provides the value for the
!                                 [destination] property. If this element is NOT present then the
!                                 value of the [destination] property is
!                                 "http://www.w3.org/@@@@/@@/addressing/address/anonymous".</p>
                          </dd>
                      
                      
!                         <dt class="label"> /wsa:From</dt>
                          <dd>
!                             <p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides
!                                 the value for the [source endpoint] property.</p>
                          </dd>
                      
                      
                          <dt class="label"> /wsa:ReplyTo</dt>
***************
*** 615,658 ****
                          </dd>
                      
-                 </dl>
-                 <dl>
                      
!                         <dt class="label"> /wsa:From</dt>
                          <dd>
                              <p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides
!                                 the value for the [source endpoint] property.</p>
                          </dd>
                      
-                 </dl>
-                 <dl>
                      
!                         <dt class="label"> /wsa:FaultTo</dt>
                          <dd>
!                             <p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides
!                                 the value for the [fault endpoint] property. If this element is
!                                 present, wsa:MessageID MUST be present.</p>
                          </dd>
                      
-                 </dl>
-                 <dl>
                      
!                         <dt class="label"> /wsa:To</dt>
                          <dd>
!                             <p>This OPTIONAL element (of type xs:anyURI) provides the value for the
!                                 [destination] property. If this element is NOT present then the
!                                 value of the [destination] property is
!                                     "http://www.w3.org/@@@@/@@/addressing/role/anonymous".</p>
                          </dd>
                      
-                 </dl>
-                 <dl>
                      
!                         <dt class="label"> /wsa:Action</dt>
                          <dd>
!                             <p>This REQUIRED element of type xs:anyURI conveys the value of the
!                                 [action] property.</p>
                          </dd>
                      
                      
                          <dt class="label"> /[reference parameters]*</dt>
                          <dd>
--- 611,656 ----
                          </dd>
                      
                      
!                         <dt class="label"> /wsa:FaultTo</dt>
                          <dd>
                              <p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides
!                                 the value for the [fault endpoint] property. If this element is
!                                 present, wsa:MessageID MUST be present.</p>
                          </dd>
                      
                      
!                         <dt class="label"> /wsa:Action</dt>
                          <dd>
!                             <p>This REQUIRED element of type xs:anyURI conveys the value of the
!                                 [action] property.</p>
                          </dd>
                      
                      
!                         <dt class="label"> /wsa:MessageID</dt>
                          <dd>
!                             <p>This OPTIONAL element (of type xs:anyURI) conveys the [message id]
!                                 property. This element MUST be present if wsa:ReplyTo or wsa:FaultTo
!                                 is present.</p>
                          </dd>
                      
                      
!                         <dt class="label"> /wsa:RelatesTo</dt>
                          <dd>
!                             <p>This OPTIONAL (repeating) element information item contributes one
!                                 abstract [relationship] property value, in the form of a (IRI, IRI)
!                                 pair. The [children] property of this element (which is of type
!                                 xs:anyURI) conveys the [message id] of the related message. This
!                                 element MUST be present if the message is a reply.</p>
                          </dd>
                      
                      
+                         <dt class="label"> /wsa:RelatesTo/@RelationshipType</dt>
+                         <dd>
+                             <p>This OPTIONAL attribute (of type xs:anyURI) conveys the relationship
+                                 type as an IRI. When absent, the implied value of this attribute is
+                                     "http://www.w3.org/@@@@/@@/addressing/reply".</p>
+                         </dd>
+                     
+                      
                          <dt class="label"> /[reference parameters]*</dt>
                          <dd>
***************
*** 668,672 ****
                  <div class="div3">
                      
! <h4><a name="compiri"></a>3.1.1 Comparing IRIs</h4>
                      <p>The values of the Message Addressing Properties [action], [message id], and
                          [relationship] are absolute IRIs. The purpose of these IRIs is primarily
--- 666,670 ----
                  <div class="div3">
                      
! <h4><a name="compiri"></a>3.2.1 Comparing IRIs</h4>
                      <p>The values of the Message Addressing Properties [action], [message id], and
                          [relationship] are absolute IRIs. The purpose of these IRIs is primarily
***************
*** 676,685 ****
                      <p>Comparison of [destination] property values is out of scope, other than using
                          simple string comparison to detect whether the value is anonymous, that is,
!                         where [destination] has the value "http://www.w3.org/@@@@/@@/addressing/role/anonymous".</p>
                  </div>
              </div>
              <div class="div2">
                  
! <h3><a name="formreplymsg"></a>3.2 Formulating a Reply Message</h3>
                  <p>The reply to a WS-Addressing compliant request message MUST be compliant to
                      WS-Addressing and is constructed according to the following rules:</p>
--- 674,683 ----
                      <p>Comparison of [destination] property values is out of scope, other than using
                          simple string comparison to detect whether the value is anonymous, that is,
!                         where [destination] has the value "http://www.w3.org/@@@@/@@/addressing/address/anonymous".</p>
                  </div>
              </div>
              <div class="div2">
                  
! <h3><a name="formreplymsg"></a>3.3 Formulating a Reply Message</h3>
                  <p>The reply to a WS-Addressing compliant request message MUST be compliant to
                      WS-Addressing and is constructed according to the following rules:</p>
***************
*** 730,734 ****
                      properties serialized as header blocks in a SOAP 1.2 message:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Example request message.</i></p>
                      <div class="exampleInner"><pre>
  &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
--- 728,732 ----
                      properties serialized as header blocks in a SOAP 1.2 message:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-1. </span>Example request message.</i></p>
                      <div class="exampleInner"><pre>
  &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
***************
*** 739,743 ****
        &lt;wsa:Address&gt;http://example.com/business/client1&lt;/wsa:Address&gt;
      &lt;/wsa:ReplyTo&gt;
!     &lt;wsa:To S:mustUnderstand="1"&gt;mailto:fabrikam@example.com&lt;/wsa:To&gt;
      &lt;wsa:Action&gt;http://example.com/fabrikam/mail/Delete&lt;/wsa:Action&gt;
    &lt;/S:Header&gt;
--- 737,741 ----
        &lt;wsa:Address&gt;http://example.com/business/client1&lt;/wsa:Address&gt;
      &lt;/wsa:ReplyTo&gt;
!     &lt;wsa:To&gt;mailto:fabrikam@example.com&lt;/wsa:To&gt;
      &lt;wsa:Action&gt;http://example.com/fabrikam/mail/Delete&lt;/wsa:Action&gt;
    &lt;/S:Header&gt;
***************
*** 772,776 ****
                  <p>The following example illustrates a reply to the above message:</p>
                  <div class="exampleOuter">
!                     <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Example response message.</i></p>
                      <div class="exampleInner"><pre>
  &lt;S:Envelope
--- 770,774 ----
                  <p>The following example illustrates a reply to the above message:</p>
                  <div class="exampleOuter">
!                     <p style="text-align: left" class="exampleHead"><i><span>Example 3-2. </span>Example response message.</i></p>
                      <div class="exampleInner"><pre>
  &lt;S:Envelope
***************
*** 780,784 ****
      &lt;wsa:MessageID&gt;http://example.com/someotheruniquestring&lt;/wsa:MessageID&gt;
      &lt;wsa:RelatesTo&gt;http://example.com/someuniquestring&lt;/wsa:RelatesTo&gt;
!     &lt;wsa:To S:mustUnderstand="1"&gt;http://example.com/business/client1&lt;/wsa:To&gt;
      &lt;wsa:Action&gt;http://example.com/fabrikam/mail/DeleteAck&lt;/wsa:Action&gt;
    &lt;/S:Header&gt;
--- 778,782 ----
      &lt;wsa:MessageID&gt;http://example.com/someotheruniquestring&lt;/wsa:MessageID&gt;
      &lt;wsa:RelatesTo&gt;http://example.com/someuniquestring&lt;/wsa:RelatesTo&gt;
!     &lt;wsa:To&gt;http://example.com/business/client1&lt;/wsa:To&gt;
      &lt;wsa:Action&gt;http://example.com/fabrikam/mail/DeleteAck&lt;/wsa:Action&gt;
    &lt;/S:Header&gt;
***************
*** 815,823 ****
              <p>Users of WS-Addressing and EPRs (i.e., entities creating, consuming or receiving
                  Message Addressing Properties and EPRs) SHOULD only use EPRs from sources they
!                 trust. For example, such users might only use EPRs that are signed by parties the
!                 user of the EPR trusts, or have some out-of-band means of establishing trust.</p>
!             <p>EPRs and message addressing properties SHOULD be integrity protected to prevent
!                 tampering. Such optional integrity protection might be provided by transport,
!                 message level signature, and use of an XML digital signature within EPRs.</p>
              <p>To prevent information disclosure, EPR issuers SHOULD NOT put sensitive information
                  into the [address] or [reference parameters] properties.</p>
--- 813,823 ----
              <p>Users of WS-Addressing and EPRs (i.e., entities creating, consuming or receiving
                  Message Addressing Properties and EPRs) SHOULD only use EPRs from sources they
!                 trust. For example, such users might rely on the presence of a verifiable
!                 signature by a trusted party over the EPR, or an out-of-band means 
!                 of establishing trust, to determine whether they should use a
!                 particular EPR.</p>
!             <p>EPRs and message addressing properties SHOULD be integrity-protected to prevent
!                 tampering. Such optional integrity protection might be provided by the transport,
!                 a message level signature, or use of an XML digital signature within EPRs.</p>
              <p>To prevent information disclosure, EPR issuers SHOULD NOT put sensitive information
                  into the [address] or [reference parameters] properties.</p>
***************
*** 826,830 ****
                  for purposes of replay detection, the message identifier is combined with other
                  data, such as a timestamp, so that a legitimate retransmission of the message is not
!                 confused with a replay attack.</p>
          </div>
          <div class="div1">
--- 826,833 ----
                  for purposes of replay detection, the message identifier is combined with other
                  data, such as a timestamp, so that a legitimate retransmission of the message is not
!                 confused with a replay attack. It is also advisable to use message identifiers that are not
!                 predictable, to prevent attackers from constructing and sending
!                 an unsolicited reply to an outstanding request without having to 
!                 see the actual request message.</p>
          </div>
          <div class="div1">
***************
*** 841,845 ****
                      Gudgin, J. J. Moreau, J. Schlimmer, S. Weerawarana, Editors. World Wide Web
                      Consortium, 3 August 2004. This version of the WSDL 2.0 specification is
!                     http://www.w3.org/TR/2004/WD-wsdl20-20040803. The <a href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</a> is
                      available at http://www.w3.org/TR/wsdl20.</dd>
                  <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
--- 844,848 ----
                      Gudgin, J. J. Moreau, J. Schlimmer, S. Weerawarana, Editors. World Wide Web
                      Consortium, 3 August 2004. This version of the WSDL 2.0 specification is
!                     http://www.w3.org/TR/2005/WD-wsdl20-20050510. The <a href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</a> is
                      available at http://www.w3.org/TR/wsdl20.</dd>
                  <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
***************
*** 848,853 ****
                      http://www.ietf.org/rfc/rfc2119.txt. </dd>
                  <dt class="label"><a name="RFC3987"></a>[IETF RFC 3987] </dt><dd>
!                     M. Duerst, M. Suignard, "Internationalized Resource Identifiers (IRIs)", January
!                     2005. (See <cite><a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a></cite>.)</dd>
                  <dt class="label"><a name="XML10"></a>[XML 1.0] </dt><dd>
                      <cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup Language (XML) 1.0 (Third Edition)</a></cite>, T.
--- 851,856 ----
                      http://www.ietf.org/rfc/rfc2119.txt. </dd>
                  <dt class="label"><a name="RFC3987"></a>[IETF RFC 3987] </dt><dd>
! 				  <cite><a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a></cite>
!                     M. Duerst, M. Suignard, January 2005. Available at http://www.ietf.org/rfc/rfc3987.txt.</dd>
                  <dt class="label"><a name="XML10"></a>[XML 1.0] </dt><dd>
                      <cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup Language (XML) 1.0 (Third Edition)</a></cite>, T.
***************
*** 887,890 ****
--- 890,898 ----
                          1.2 Part 1: Messaging Framework"</a> is available at
                      http://www.w3.org/TR/soap12-part1/. </dd>
+                 <dt class="label"><a name="SOAP11"></a>[SOAP 1.1] </dt><dd>Don Box,
+                     et al, <cite><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">Simple Object Access Protocol (SOAP)
+                         1.1</a></cite>, May 2000.</dd>
+                 <dt class="label"><a name="WSDL11"></a>[WSDL 1.1] </dt><dd>E. Christensen, et al, <cite><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">Web Services Description Language (WSDL)
+                         1.1</a></cite>, March 2001.</dd>
                  <dt class="label"><a name="WS-Security"></a>[WS-Security] </dt><dd> OASIS, <cite><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">Web Services Security: SOAP Message Security</a></cite>,
                      March 2004.</dd>
***************
*** 912,917 ****
              <div class="div2">
                  
! <h3><a name="N105E3"></a>B.1 Changes Since Second Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-04-22 @ 18:26</td><td>mhadley</td><td>Added resolution to lc22 - clarified ignore rule for extension attributes.</td></tr><tr><td>2005-04-22 @ 18:24</td><td>mhadley</td><td>Added resolution to lc21 - removed HTTP specific restriction on use of anonymous URI in [destination] for replies only.</td></tr><tr><td>2005-04-22 @ 18:18</td><td>mhadley</td><td>Added resolution to lc19 - clarified that [destination] value comparison is out of scope except for using simple string comparison to determine whether the anonymous destination is being used.</td></tr><tr><td>2005-04-22 @ 18:12</td><td>mhadley</td><td>Added resolution to lc18 - simplified description of wsa:To and wsa:Action elements</td></tr><tr><td>2005-04-22 @ 18:04</td><td>mhadley</td><td>Added resolution to lc17 - clarified that anonymous destination URI is not just for use in replies</td></tr><tr><td>2005-04-22 @ 18:01</td><td>mhadley</td><td>Added rsolution to lc16 and lc54 - removed suggestion that required was required to use [destination] and [action] properties for dispatch</td></tr><tr><td>2005-04-22 @ 17:55</td><td>mhadley</td><td>Added resolution to lc15 - clarified cardinality of [relationship] properties using predefined reply URI</td></tr><tr><td>2005-04-22 @ 17:50</td><td>mhadley</td><td>Added resolution to lc14 - clarified reply IRI targetting</td></tr><tr><td>2005-04-22 @ 17:41</td><td>mhadley</td><td>Added resolution to lc13 - clarified wording in  description of metadata</td></tr><tr><td>2005-04-22 @ 17:38</td><td>mhadley</td><td>Added resolution to lc12 - removed data encoding from description of reference parameters</td></tr><tr><td>2005-04-22 @ 17:30</td><td>mhadley</td><td>Added resolution to lc10 and lc11 - clarified types and opacity of reference parameters</td></tr><tr><td>2005-04-22 @ 17:25</td><td>mhadley</td><td>Added resolution to lc9 - changed IRI to absolute IRI where appropriate</td></tr><tr><td>2005-04-22 @ 16:16</td><td>hadley</td><td>Added resolution to lc8 - changed IRI to URI where used to refer to IRIs in the specification that are actually URIs</td></tr><tr><td>2005-04-22 @ 15:49</td><td>mhadley</td><td>Added resolution to lc7 - fixed editorial nits</td></tr><tr><td>2005-04-22 @ 15:32</td><td>mhadley</td><td>Added resolution to lc3 - removed single extensibility point from infoset representation to avoid impression that other extenisibility points are not also valid</td></tr><tr><td>2005-04-22 @ 15:06</td><td>mhadley</td><td>Added resolution to lc2 - assorted editorial changes</td></tr><tr><td>2005-03-30 @ 21:02</td><td>plehegar</td><td>Removed some extra blanks
  Added the note from David Hull at
    http://lists.w3.org/Archives/Public/public-ws-addressing/2005Mar/0254.html
--- 920,925 ----
              <div class="div2">
                  
! <h3><a name="N67090"></a>B.1 Changes Since Second Working Draft</h3>
!                 <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-05-18 @ 19:49</td><td>mhadley</td><td>Added lc81 resolution - remove mustUnderstand attributes from examples</td></tr><tr><td>2005-05-18 @ 19:35</td><td>mhadley</td><td>Added lc51 resolution - reordered property list to match order in core</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-05-18 @ 18:58</td><td>mhadley</td><td>Added lc97 resolution - Endpoint Reference to endpoint reference</td></tr><tr><td>2005-05-18 @ 18:56</td><td>mhadley</td><td>Added lc95 resolution - added WSDL 1.1 citation to introduction</td></tr><tr><td>2005-05-18 @ 18:51</td><td>mhadley</td><td>Added lc94 resolution - changed element to Element Information Item</td></tr><tr><td>2005-05-18 @ 18:48</td><td>mhadley</td><td>Added lc93 resolution - added ref to soap binding document prior to soap example in introduction</td></tr><tr><td>2005-0-18 @ 18:44</td><td>mhadley</td><td>Added lc92 resolution - clarified document being referenced in introduction</td></tr><tr><td>2005-05-18 @ 18:40</td><td>mhadley</td><td>Added lc80 resolution - made abstract properties into a separate list</td></tr><tr><td>2005-05-18 @ 18:34</td><td>mhadley</td><td>Added lc74 resolution - added suggested security consideration</td></tr><tr><td>2005-05-18 @ 18:24</td><td>mhadley</td><td>Added lc63 resolution - editorial fixes to security section</td></tr><tr><td>2005-05-18 @ 18:19</td><td>mhadley</td><td>Added lc44 resolution - changed and to or in security section</td></tr><tr><td>2005-05-18 @ 18:17</td><td>mhadley</td><td>Added lc43 resolution - added ref to SOAP 1.1</td></tr><tr><td>2005-05-18 @ 18:12</td><td>mhadley</td><td>Added lc42 resolution - reordered infoset representation to match order of abstract properties</td></tr><tr><td>2005-05-18 @ 18:03</td><td>mhadley</td><td>Added lc67 resolution - made namespace uri a link</td></tr><tr><td>2005-05-18 @ 17:58</td><td>hadley</td><td>Added lc64 resolution - numerous editorial fixes</td></tr><tr><td>2005-05-16 @ 20:28</td><td>mgudgin</td><td>Fixed mismatched endtag in Section 3.1</td></tr><tr><td>2005-05-16 @ 20:16</td><td>mgudgin</td><td>Fixed reference to RFC3987 to match format of other biblio entries</td></tr><tr><td>2005-04-22 @ 18:26</td><td>mhadley</td><td>Added resolution to lc22 - clarified ignore rule for extension attributes.</td></tr><tr><td>2005-04-22 @ 18:24</td><td>mhadley</td><td>Added resolution to lc21 - removed HTTP specific restriction on use of anonymous URI in [destination] for replies only.</td></tr><tr><td>2005-04-22 @ 18:18</td><td>mhadley</td><td>Added resolution to lc19 - clarified that [destination] value comparison is out of scope except for using simple string comparison to determine whether the anonymous destination is being used.</td></tr><tr><td>2005-04-22 @ 18:12</td><td>mhadley</td><td>Added resolution to lc18 - simplified description of wsa:To and wsa:Action elements</td></tr><tr><td>200-04-22 @ 18:04</td><td>mhadley</td><td>Added resolution to lc17 - clarified that anonymous destination URI is not just for use in replies</td></tr><tr><td>2005-04-22 @ 18:01</td><td>mhadley</td><td>Added resolution to lc16 and lc54 - removed suggestion that required was required to use [destination] and [action] properties for dispatch</td></tr><tr><td>2005-04-22 @ 17:55</td><td>mhadley</td><td>Added resolution to lc15 - clarified cardinality of [relationship] properties using predefined reply URI</td></tr><tr><td>2005-04-22 @ 17:50</td><td>mhadley</td><td>Added resolution to lc14 - clarified reply IRI targetting</td></tr><tr><td>2005-04-22 @ 17:41</td><td>mhadley</td><td>Added resolution to lc13 - clarified wording in  description of metadata</td></tr><tr><td>2005-04-22 @ 17:38</td><td>mhadley</td><td>Added resolution to lc12 - removed data encoding from description of reference parameters</td></tr><tr><td>2005-04-22 @ 17:30</td><td>mhadley</td><td>Added resolution to lc10 and lc11 - clarified types and opcity of reference parameters</td></tr><tr><td>2005-04-22 @ 17:25</td><td>mhadley</td><td>Added resolution to lc9 - changed IRI to absolute IRI where appropriate</td></tr><tr><td>2005-04-22 @ 16:16</td><td>mhadley</td><td>Added resolution to lc8 - changed IRI to URI where used to refer to IRIs in the specification that are actually URIs</td></tr><tr><td>2005-04-22 @ 15:49</td><td>mhadley</td><td>Added resolution to lc7 - fixed editorial nits</td></tr><tr><td>2005-04-22 @ 15:32</td><td>mhadley</td><td>Added resolution to lc3 - removed single extensibility point from infoset representation to avoid impression that other extenisibility points are not also valid</td></tr><tr><td>2005-04-22 @ 15:06</td><td>mhadley</td><td>Added resolution to lc2 - assorted editorial changes</td></tr><tr><td>2005-03-30 @ 21:02</td><td>plehegar</td><td>Removed some extra blanks
  Added the note from David Hull at
    http://lists.w3.org/Archives/Public/public-ws-addressing/2005Mar/0254.html
***************
*** 921,930 ****
              <div class="div2">
                  
! <h3><a name="N105ED"></a>B.2 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-23 @ 21:13</td><td>mgudgin</td><td>Incorporated resolution of issue i014; edits to Section 2.3</td></tr><tr><td>2005-01-23 @ 20:52</td><td>mgudgin</td><td>Incorporated resolution of issue i006; made wsa:To optional</td></tr><tr><td>2005-01-23 @ 19:32</td><td>mgudgin</td><td>Incorporated resolution of Issue i001 by removing Reference Properties</td></tr><tr><td>2005-01-17 @ 02:13</td><td>mgudgin</td><td>Incorporated Paco's proposal for resolving Issue 038</td></tr><tr><td>2005-01-16 @ 22:40</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</td></tr><tr><td>2004-12-17 @ 16:08</td><td>mhadley</td><td>Improved readability of introduction</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>Switched 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="N105F7"></a>B.3 Changes Since Submission</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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-22 @ 15:40</td><td>mhadley</td><td>Removed reference to WS-Policy</td></tr><tr><td>2004-11-15 @ 19:43</td><td>mhadley</td><td>Fixed some inter and intra spec references.</td></tr><tr><td>2004-11-12 @ 21:19</td><td>mgudgin</td><td>Removed TBD sections</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 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</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>
--- 929,938 ----
              <div class="div2">
                  
! <h3><a name="N67100"></a>B.2 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-23 @ 21:13</td><td>mgudgin</td><td>Incorporated resolution of issue i014; edits to Section 2.3</td></tr><tr><td>2005-01-23 @ 20:52</td><td>mgudgin</td><td>Incorporated resolution of issue i006; made wsa:To optional</td></tr><tr><td>2005-01-23 @ 19:32</td><td>mgudgin</td><td>Incorporated resolution of Issue i001 by removing Reference Properties</td></tr><tr><td>2005-01-17 @ 02:13</td><td>mgudgin</td><td>Incorporated Paco's proposal for resolving Issue 038</td></tr><tr><td>2005-01-16 @ 22:40</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</td></tr><tr><td>2004-12-17 @ 16:08</td><td>mhadley</td><td>Improved readability of introduction</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>Switched 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="N67110"></a>B.3 Changes Since Submission</h3>
                  <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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-22 @ 15:40</td><td>mhadley</td><td>Removed reference to WS-Policy</td></tr><tr><td>2004-11-15 @ 19:43</td><td>mhadley</td><td>Fixed some inter and intra spec references.</td></tr><tr><td>2004-11-12 @ 21:19</td><td>mgudgin</td><td>Removed TBD sections</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 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</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>

Index: ws-addr-soap.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** ws-addr-soap.html	13 May 2005 18:59:19 -0000	1.29
--- ws-addr-soap.html	18 May 2005 19:53:43 -0000	1.30
***************
*** 67,75 ****
          no official standing.</strong></p><p></p></div>
    <hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro"> 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="#s12feature">SOAP 1.2 Addressing 1.0 Feature</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#s12featurename">Feature Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#s12featuredesc">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#s12featureprops">Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#s12featureinteractions">Interactions with Other SOAP Features</a><br>3. <a href="#s12module">SOAP 1.2 Addressing 1.0 Module</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#s12modulename">Module Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#s12moduledesc">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#additionalinfoset">Additional Infoset Items</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.4 <a href="#bindrefp">Binding Message Addressing Properies</a><br>4. <a href="#s11ext">SOAP 1.1 Addressing 1.0 Extension</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#s11extname">Extension Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#s11extdesc">Description</a><br>5. <a href="#faults">Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#missingmapfault"> Message Addressing Header Required</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.3 <a href="#destinationfault"> Destination Unreachable</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.4 <a href="#actionfault"> Action Not Supported</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>6. <a href="#securityconsiderations">Security Considerations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#intseccons">Additional Considerations for SOAP Intermediaries</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="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N66860">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N66870">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N66880">Changes Since Submission</a><br></p></div><hr><div class="body">
      <div class="div1">
        
! <h2><a name="intro"></a>1.  Introduction</h2>
        <p>Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>] defines a set
          of abstract properties and an XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] representation thereof to reference Web
--- 67,75 ----
          no official standing.</strong></p><p></p></div>
    <hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">2. <a href="#intro"> 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>1. <a href="#s12feature">SOAP 1.2 Addressing 1.0 Feature</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#s12featurename">Feature Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#s12featuredesc">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#s12featureprops">Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#s12featureinteractions">Interactions with Other SOAP Features</a><br>1. <a href="#s12module">SOAP 1.2 Addressing 1.0 Module</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#s12modulename">Module Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#s12moduledesc">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#additionalinfoset">Additional Infoset Items</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.4 <a href="#bindrefp">Binding Message Addressing Properies</a><br>1. <a href="#s11ext">SOAP 1.1 Addressing 1.0 Extension</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#s11extname">Extension Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#s11extdesc">Description</a><br>1. <a href="#faults">Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#missingmapfault"> Message Addressing Header Required</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.3 <a href="#destinationfault"> Destination Unreachable</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.4 <a href="#actionfault"> Action Not Supported</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>1. <a href="#securityconsiderations">Security Considerations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#intseccons">Additional Considerations for SOAP Intermediaries</a><br>3. <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="#changelog">Change Log</a> (Non-Normative)<br>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N66866">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N66876">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N66886">Changes Since Submission</a><br></p></div><hr><div class="body">
      <div class="div1">
        
! <h2><a name="intro"></a>2.  Introduction</h2>
        <p>Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>] defines a set
          of abstract properties and an XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] representation thereof to reference Web
***************
*** 86,114 ****
            message.</i></p>
          <div class="exampleInner"><pre>
! (001) &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"      
                  xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"&gt;
! (002)   &lt;S:Header&gt;
! (003)    &lt;wsa:MessageID&gt;http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA&lt;/wsa:MessageID&gt;
! (004)    &lt;wsa:ReplyTo&gt;
! (005)      &lt;wsa:Address&gt;http://example.com/business/client1&lt;/wsa:Address&gt;
! (006)    &lt;/wsa:ReplyTo&gt;
! (007)    &lt;wsa:To&gt;http://example.com/fabrikam/Purchasing&lt;/wsa:To&gt;
! (008)    &lt;wsa:Action&gt;http://example.com/fabrikam/SubmitPO&lt;/wsa:Action&gt;
! (009)   &lt;/S:Header&gt;
! (010)   &lt;S:Body&gt;
! (011)     ...
! (012)   &lt;/S:Body&gt;
! (013) &lt;/S:Envelope&gt;
  </pre></div>
!         <p>Lines (002) to (009) represent the header of the SOAP message
            where the mechanisms defined in the specification are used.
!           The body is represented by lines (010) to (012).</p>
!         <p>Lines (003) to (008) contain the message addressing
            properties serialized as SOAP header blocks. Specifically,
!           line (003) specifies the identifier for this message and lines
!           (004) to (006) specify the endpoint to which replies to this
!           message should be sent as an Endpoint Reference. Line (007)
            specifies the address URI of the ultimate receiver of this
!           message. Line (008) specifies an action URI identifying
            expected semantics.</p>
        </div>
--- 86,114 ----
            message.</i></p>
          <div class="exampleInner"><pre>
! (01) &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"      
                  xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"&gt;
! (02)   &lt;S:Header&gt;
! (03)    &lt;wsa:MessageID&gt;http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA&lt;/wsa:MessageID&gt;
! (04)    &lt;wsa:ReplyTo&gt;
! (05)      &lt;wsa:Address&gt;http://example.com/business/client1&lt;/wsa:Address&gt;
! (06)    &lt;/wsa:ReplyTo&gt;
! (07)    &lt;wsa:To&gt;http://example.com/fabrikam/Purchasing&lt;/wsa:To&gt;
! (08)    &lt;wsa:Action&gt;http://example.com/fabrikam/SubmitPO&lt;/wsa:Action&gt;
! (09)   &lt;/S:Header&gt;
! (10)   &lt;S:Body&gt;
! (11)     ...
! (12)   &lt;/S:Body&gt;
! (13) &lt;/S:Envelope&gt;
  </pre></div>
!         <p>Lines (02) to (09) represent the header of the SOAP message
            where the mechanisms defined in the specification are used.
!           The body is represented by lines (10) to (12).</p>
!         <p>Lines (03) to (08) contain the message addressing
            properties serialized as SOAP header blocks. Specifically,
!           line (03) specifies the identifier for this message and lines
!           (04) to (06) specify the endpoint to which replies to this
!           message should be sent as an Endpoint Reference. Line (07)
            specifies the address URI of the ultimate receiver of this
!           message. Line (08) specifies an action URI identifying
            expected semantics.</p>
        </div>
***************
*** 140,144 ****
            throughout; they are listed in <a href="#nsrefs">Table 1-1</a>. Note
            that the choice of any namespace prefix is arbitrary and not
!           semantically significant (see [<cite><a href="#XMLNS">XML Namespaces</a></cite> ]).</p>
          <a name="nsrefs"></a><table border="1" summary="Namespace prefixes usage in this specification">
            <caption>Table 1-1. Prefixes and Namespaces used in this specification</caption>
--- 140,144 ----
            throughout; they are listed in <a href="#nsrefs">Table 1-1</a>. Note
            that the choice of any namespace prefix is arbitrary and not
!           semantically significant (see [<cite><a href="#XMLNS">XML Namespaces</a></cite>]).</p>
          <a name="nsrefs"></a><table border="1" summary="Namespace prefixes usage in this specification">
            <caption>Table 1-1. Prefixes and Namespaces used in this specification</caption>
***************
*** 180,184 ****
          <p>All information items defined by this specification are
            identified by the XML namespace URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>]
!           "http://www.w3.org/@@@@/@@/addressing". A normative XML Schema [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document
            can be obtained by dereferencing the XML namespace URI.</p>
        </div>
--- 180,184 ----
          <p>All information items defined by this specification are
            identified by the XML namespace URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>]
!           <a href="http://www.w3.org/@@@@/@@/addressing">http://www.w3.org/@@@@/@@/addressing</a>. A normative XML Schema [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document
            can be obtained by dereferencing the XML namespace URI.</p>
        </div>
***************
*** 186,190 ****
      <div class="div1">
        
! <h2><a name="s12feature"></a>2. SOAP 1.2 Addressing 1.0 Feature</h2>
        <p>This section defines the SOAP 1.2 Addressing 1.0 Feature.</p>
        <div class="div2">
--- 186,190 ----
      <div class="div1">
        
! <h2><a name="s12feature"></a>1. SOAP 1.2 Addressing 1.0 Feature</h2>
        <p>This section defines the SOAP 1.2 Addressing 1.0 Feature.</p>
        <div class="div2">
***************
*** 244,248 ****
            
            
!             <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/MessageId</dt>
              <dd>
                <p>Corresponds to the abstract [message id] property.</p>
--- 244,254 ----
            
            
!             <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/Action</dt>
!             <dd>
!               <p>Corresponds to the abstract [action] property.</p>
!             </dd>
!           
!           
!             <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/MessageID</dt>
              <dd>
                <p>Corresponds to the abstract [message id] property.</p>
***************
*** 263,272 ****
              </dd>
            
-           
-             <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/Action</dt>
-             <dd>
-               <p>Corresponds to the abstract [action] property.</p>
-             </dd>
-           
          </dl>
        </div>
--- 269,272 ----
***************
*** 278,291 ****
            http://www.w3.org/@@@@/@@/addressing/feature/Action property of the SOAP 1.2 Addressing
            1.0 feature MUST be identical to it. Failure to have an
!           identical value results in an Invalid Message Addressing
!           Property fault (see <a href="#invalidmapfault"><b>5.1  Invalid Addressing Header</b></a>.</p>
        </div>
      </div>
      <div class="div1">
        
! <h2><a name="s12module"></a>3. SOAP 1.2 Addressing 1.0 Module</h2>
        <p>The SOAP 1.2 Addressing 1.0 Module defines a set of SOAP header
          blocks to support the SOAP 1.2 Addressing 1.0 Feature described
!         in <a href="#s12feature"><b>2. SOAP 1.2 Addressing 1.0 Feature</b></a>. To ensure interoperability with
          a broad range of devices, all conformant implementations that
          include support for SOAP 1.2 MUST support the SOAP 1.2
--- 278,291 ----
            http://www.w3.org/@@@@/@@/addressing/feature/Action property of the SOAP 1.2 Addressing
            1.0 feature MUST be identical to it. Failure to have an
!           identical value results in an Invalid Addressing
!           Header fault (see <a href="#invalidmapfault"><b>5.1  Invalid Addressing Header</b></a>.</p>
        </div>
      </div>
      <div class="div1">
        
! <h2><a name="s12module"></a>1. SOAP 1.2 Addressing 1.0 Module</h2>
        <p>The SOAP 1.2 Addressing 1.0 Module defines a set of SOAP header
          blocks to support the SOAP 1.2 Addressing 1.0 Feature described
!         in <a href="#s12feature"><b>1. SOAP 1.2 Addressing 1.0 Feature</b></a>. To ensure interoperability with
          a broad range of devices, all conformant implementations that
          include support for SOAP 1.2 MUST support the SOAP 1.2
***************
*** 305,309 ****
          
  <h3><a name="s12moduledesc"></a>3.2 Description</h3>
!         <p>The SOAP 1.2 Addressing 1.0 Feature (see <a href="#s12feature"><b>2. SOAP 1.2 Addressing 1.0 Feature</b></a>) defines a set of SOAP properties and
            their correspondence to the abstract message addressing
            properties defined by Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>]. The SOAP 1.2 Addressing 1.0 Module
--- 305,309 ----
          
  <h3><a name="s12moduledesc"></a>3.2 Description</h3>
!         <p>The SOAP 1.2 Addressing 1.0 Feature (see <a href="#s12feature"><b>1. SOAP 1.2 Addressing 1.0 Feature</b></a>) defines a set of SOAP properties and
            their correspondence to the abstract message addressing
            properties defined by Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>]. The SOAP 1.2 Addressing 1.0 Module
***************
*** 323,327 ****
            in the message. Note that the message addressing properties
            gathered by an intermediary when receiving a SOAP message do
!           not necessarily get replayed as MAPs when resending the
            message along the message path. A message MUST NOT contain
            more than one wsa:To, wsa:ReplyTo, wsa:FaultTo, wsa:Action,
--- 323,327 ----
            in the message. Note that the message addressing properties
            gathered by an intermediary when receiving a SOAP message do
!           not necessarily get replayed as message addressing properties when resending the
            message along the message path. A message MUST NOT contain
            more than one wsa:To, wsa:ReplyTo, wsa:FaultTo, wsa:Action,
***************
*** 397,400 ****
--- 397,401 ----
  &lt;wsa:EndpointReference
       xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"
+      xmlns:wsaw="http://www.w3.org/@@@@/@@/addressing/wsdl"
       xmlns:fabrikam="http://example.com/fabrikam"
       xmlns:wsdli="http://www.w3.org/2004/08/wsdl-instance"
***************
*** 439,446 ****
      <div class="div1">
        
! <h2><a name="s11ext"></a>4. SOAP 1.1 Addressing 1.0 Extension</h2>
        <p>The SOAP 1.1 Addressing 1.0 Extension defines a set of SOAP
          header blocks to support the SOAP 1.2 Addressing 1.0 Feature
!         described in <a href="#s12feature"><b>2. SOAP 1.2 Addressing 1.0 Feature</b></a>. To ensure
          interoperability with a broad range of devices, all conformant
          implementations that include support for SOAP 1.1 MUST support
--- 440,447 ----
      <div class="div1">
        
! <h2><a name="s11ext"></a>1. SOAP 1.1 Addressing 1.0 Extension</h2>
        <p>The SOAP 1.1 Addressing 1.0 Extension defines a set of SOAP
          header blocks to support the SOAP 1.2 Addressing 1.0 Feature
!         described in <a href="#s12feature"><b>1. SOAP 1.2 Addressing 1.0 Feature</b></a>. To ensure
          interoperability with a broad range of devices, all conformant
          implementations that include support for SOAP 1.1 MUST support
***************
*** 461,465 ****
          
  <h3><a name="s11extdesc"></a>4.2 Description</h3>
!         <p>The SOAP 1.2 Addressing 1.0 Feature (see <a href="#s12feature"><b>2. SOAP 1.2 Addressing 1.0 Feature</b></a>) defines a set of SOAP properties and
            their correspondence to the abstract message addressing
            properties defined by Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>]. The SOAP 1.1 Addressing 1.0 Extension
--- 462,466 ----
          
  <h3><a name="s11extdesc"></a>4.2 Description</h3>
!         <p>The SOAP 1.2 Addressing 1.0 Feature (see <a href="#s12feature"><b>1. SOAP 1.2 Addressing 1.0 Feature</b></a>) defines a set of SOAP properties and
            their correspondence to the abstract message addressing
            properties defined by Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>]. The SOAP 1.1 Addressing 1.0 Extension
***************
*** 468,472 ****
            binds each element information item to a SOAP header block.
            The SOAP 1.1 Addressing 1.0 Extension operates as described in
!             <a href="#s12module"><b>3. SOAP 1.2 Addressing 1.0 Module</b></a> with the following exceptions:</p>
          <dl>
            
--- 469,473 ----
            binds each element information item to a SOAP header block.
            The SOAP 1.1 Addressing 1.0 Extension operates as described in
!             <a href="#s12module"><b>1. SOAP 1.2 Addressing 1.0 Module</b></a> with the following exceptions:</p>
          <dl>
            
***************
*** 490,494 ****
      <div class="div1">
        
! <h2><a name="faults"></a>5. Faults</h2>
        <p>The faults defined in this section are generated if the
          condition stated in the preamble in each subsection is met.</p>
--- 491,495 ----
      <div class="div1">
        
! <h2><a name="faults"></a>1. Faults</h2>
        <p>The faults defined in this section are generated if the
          condition stated in the preamble in each subsection is met.</p>
***************
*** 543,547 ****
        </pre></div>
        </div>
!       <p>The SOAP 1.1 fault is less expressive and map only [Subcode]
          and [Reason]. These the properties bind to a SOAP 1.1 fault as
          follows:</p>
--- 544,548 ----
        </pre></div>
        </div>
!       <p>The SOAP 1.1 fault is less expressive and maps only [Subcode]
          and [Reason]. These the properties bind to a SOAP 1.1 fault as
          follows:</p>
***************
*** 616,620 ****
            either due to some transient issue or a permanent failure. </p>
          <p>The endpoint may optionally include a RetryAfter parameter in
!           the detail. The source should not retransmit the message until
            this duration has passed.</p>
          <p> [Code] S:Receiver</p>
--- 617,621 ----
            either due to some transient issue or a permanent failure. </p>
          <p>The endpoint may optionally include a RetryAfter parameter in
!           the detail. The source SHOULD NOT retransmit the message until
            this duration has passed.</p>
          <p> [Code] S:Receiver</p>
***************
*** 630,642 ****
              <dt class="label">/wsa:RetryAfter</dt>
              <dd>
!               <p>This element (of type xs:nonNegativeInteger) is a
                  suggested minimum duration in milliseconds to wait
                  before retransmitting the message. If this element is
                  omitted from the detail, the value is infinite.</p>
!               <table border="1" summary="Editorial note: M Hadley"><tr><td align="left" valign="top" width="50%"><b>Editorial note: M Hadley</b></td><td align="right" valign="top" width="50%">&nbsp;</td></tr><tr><td colspan="2" align="left" valign="top">The WG seeks feedback on the choice of
!                   nonNegativeInteger for this element. Other types
!                   considered included unsignedLong, unsignedInt and
!                   duration.</td></tr></table>
!             </dd>
            
          </dl>
--- 631,639 ----
              <dt class="label">/wsa:RetryAfter</dt>
              <dd>
!               <p>This element (of type xs:unsignedLong) is a
                  suggested minimum duration in milliseconds to wait
                  before retransmitting the message. If this element is
                  omitted from the detail, the value is infinite.</p>
!              </dd>
            
          </dl>
***************
*** 654,658 ****
      <div class="div1">
        
! <h2><a name="securityconsiderations"></a>6. Security Considerations</h2>
        <p>WS-Addressing message addressing properties serialized as SOAP
          headers (wsa:To, wsa:Action et al.) including those headers
--- 651,655 ----
      <div class="div1">
        
! <h2><a name="securityconsiderations"></a>1. Security Considerations</h2>
        <p>WS-Addressing message addressing properties serialized as SOAP
          headers (wsa:To, wsa:Action et al.) including those headers
***************
*** 662,666 ****
        <p>When receiving a SOAP message, certain SOAP headers may be
          resulting from the serialization of an EPR's [reference
!         parameters] property. The SOAP message receiver MAY perform
          additional security and sanity checks to prevent unintended
          actions.</p>
--- 659,663 ----
        <p>When receiving a SOAP message, certain SOAP headers may be
          resulting from the serialization of an EPR's [reference
!         parameters] property. The SOAP message receiver can perform
          additional security and sanity checks to prevent unintended
          actions.</p>
***************
*** 681,685 ****
      <div class="div1">
        
! <h2><a name="references"></a>7.  References</h2>
        <dl>
          <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
--- 678,682 ----
      <div class="div1">
        
! <h2><a name="references"></a>3.  References</h2>
        <dl>
          <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
***************
*** 695,699 ****
            Weerawarana, Editors. World Wide Web Consortium, 3 August
            2004. This version of the WSDL 2.0 specification is
!           http://www.w3.org/TR/2004/WD-wsdl20-20040803. The <a href="http://www.w3.org/TR/wsdl20">latest version of WSDL
              2.0</a> is available at http://www.w3.org/TR/wsdl20.</dd>
          <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
--- 692,696 ----
            Weerawarana, Editors. World Wide Web Consortium, 3 August
            2004. This version of the WSDL 2.0 specification is
!           http://www.w3.org/TR/2005/WD-wsdl20-20050510. The <a href="http://www.w3.org/TR/wsdl20">latest version of WSDL
              2.0</a> is available at http://www.w3.org/TR/wsdl20.</dd>
          <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
***************
*** 702,708 ****
            Task Force, June 1999. Available at
            http://www.ietf.org/rfc/rfc2119.txt. </dd>
!         <dt class="label"><a name="RFC3987"></a>[RFC 3987] </dt><dd> M. Duerst, M.
!           Suignard, "Internationalized Resource Identifiers (IRIs)",
!           January 2005. (See <cite><a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a></cite>.)</dd>
          <dt class="label"><a name="XML10"></a>[XML 1.0] </dt><dd>
            <cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup Language (XML) 1.0 (Third
--- 699,705 ----
            Task Force, June 1999. Available at
            http://www.ietf.org/rfc/rfc2119.txt. </dd>
! 		  <dt class="label"><a name="RFC3987"></a>[IETF RFC 3987] </dt><dd>
! 			<cite><a href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a></cite>
! 		  M. Duerst, M. Suignard, January 2005. Available at http://www.ietf.org/rfc/rfc3987.txt.</dd>
          <dt class="label"><a name="XML10"></a>[XML 1.0] </dt><dd>
            <cite><a href="http://www.w3.org/TR/2004/REC-xml-20040204">Extensible Markup Language (XML) 1.0 (Third
***************
*** 789,803 ****
        <div class="div2">
          
! <h3><a name="N66860"></a>B.1 Changes Since Second Working Draft</h3>
!         <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-05-13 @ 18:56</td><td>mhadley</td><td>Added resolutions to issues 33 and 34: editorial corrections to binding MAP to SOAP headers and new rule against multiple headers targetted at same recipient</td></tr><tr><td>2005-05-05 @ 18:10</td><td>mhadley</td><td>Added issue 28 resolution: fixed use of mixed notation and indirect terminology for MAPs in Binding Message Addressing Properties section</td></tr><tr><td>2005-05-05 @ 17:39</td><td>mhadley</td><td>Added resolution to issues 26 and 36: Clarified use of invalid map fault for mismatched wsa:Action and SOAPAction; renamed and clarified invalid map and missing map faults.</td></tr><tr><td>2005-04-22 @ 20:01</td><td>mhadley</td><td>Added resolution to lc32 - added note warning of infoset changes due to IsReferenceParameter addition when binding [reference parameter] to SOAP.</td></tr><tr><td>2005-04-22 @ 19:51</td><td>mhadley</td><td>Added resolution to lc31 - clarfied what to do if a reference parameter already has an IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:46</td><td>mhadley</td><td>Added resolution to lc30 - added new section for definition of IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:26</td><td>mhadley</td><td>Added resolution to lc29 - capitalized first character of IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:07</td><td>mhadley</td><td>Added resolution to lc27 - clarified confusing use of XML infoset terminology in XML representation of properties.</td></tr><tr><td>2005-04-22 @ 18:58</td><td>mhadley</td><td>Added resolution to lc24 - editorial nits.</td></tr><tr><td>2005-04-22 @ 18:49</td><td>mhadley</td><td>Added resolution to lc23 - changed IRI to URI for constant values that are URIs.</td></tr><tr><td>2005-04-22 @ 15:27</td><td>mhadley</td><td>Added resolution to lc1 - clarified impact of omitting [message id], [reply endpoint] and [fault endpoint] on fault message generation</td></tr><tr><t>2005-04-12 @ 13:17</td><td>mhadley</td><td>Fixed closing element in example</td></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Added sentence about SOAP 1.1 to section 4</td></tr><tr><td>2005-03-18 @ 23:21</td><td>mgudgin</td><td>s/Addresssing/Addressing</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 @ 03:16</td><td>mhadley</td><td>Incorporated additional issue resolution text for issues 7 and 44 from H. Haas.</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-09 @ 07:11</td><td>mhadley</td><td>Fixed example that didn't reflect the chnage from wsa:Type to wsa:isReferenceParameter</td></tr><tr><td>2005-03-08 @ 20:50</td><td>mhadley</td><td>Added resolution to issue 53 (schema tweaks)</td></tr><tr><td>2005-03-02 @ 21:18</td><td>mhadley</td><td>Added resolution to issue 4</td></tr><tr><td>2005-03-02 @ 20:30</td><td>mhadley</td><t>Added resolution to issue 7</td></tr><tr><td>2005-03-02 @ 19:36</td><td>mhadley</td><td>Added resolution to issues 22 and 51/</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-17 @ 15:37</td><td>mhadley</td><td>Added issue 47 resolution</td></tr><tr><td>2005-02-15 @ 22:06</td><td>mhadley</td><td>Fixed some references to message information headers to message information properties</td></tr></table>
        </div>
        <div class="div2">
          
! <h3><a name="N66870"></a>B.2 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-24 @ 20:22</td><td>mgudgin</td><td>Removed spurious reference to section 3.3.2 from Section 3</td></tr><tr><td>2005-01-23 @ 21:11</td><td>mgudgin</td><td>Incorporated resolution of issue i008; added wsa:Type attribute to reference parameters</td></tr><tr><td>2005-01-20 @ 13:10</td><td>mgudgin</td><td>Removed text from first paragraph of section 3 per resolution of issue i040</td></tr><tr><td>2005-01-16 @ 22:41</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</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>Switched 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="N66880"></a>B.3 Changes Since Submission</h3>
          <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-11-24 @ 15:32</td><td>mhadley</td><td>Added note that addressing is backwards compatible with SOAP 1.1</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-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 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</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>
        </div>
--- 786,800 ----
        <div class="div2">
          
! <h3><a name="N66866"></a>B.1 Changes Since Second Working Draft</h3>
!         <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-05-18 @ 19:44</td><td>mhadley</td><td>Added lc59 resolution - added missing namespace declaration in example</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:37</td><td>mhadley</td><td>Added lc52 resolution - MessageId to MessageID</td></tr><tr><td>2005-05-18 @ 19:35</td><td>mhadley</td><td>Added lc51 resolution - reordered property list to match order in core</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-05-18 @ 19:16</td><td>mhadley</td><td>Added lc38 resolution - nonNegativeInteger to unsignedLong for RetryAfter</td></tr><tr><td>2005-05-18 @ 18:03</td><td>mhadley</td><td>Added lc67 resolution - made namespace uri a link</td></tr><tr><td>2005-05-18 @ 17:58</td><td>mhadley</td><tdAdded lc64 resolution - numerous editorial fixes</td></tr><tr><td>2005-05-16 @ 20:20</td><td>mgudgin</td><td>Fixed reference to RFC3987 to match format of other biblio entries</td></tr><tr><td>2005-05-13 @ 18:56</td><td>mhadley</td><td>Added resolutions to issues 33 and 34: editorial corrections to binding MAP to SOAP headers and new rule against multiple headers targetted at same recipient</td></tr><tr><td>2005-05-05 @ 18:10</td><td>mhadley</td><td>Added issue 28 resolution: fixed use of mixed notation and indirect terminology for MAPs in Binding Message Addressing Properties section</td></tr><tr><td>2005-05-05 @ 17:39</td><td>mhadley</td><td>Added resolution to issues 26 and 36: Clarified use of invalid map fault for mismatched wsa:Action and SOAPAction; renamed and clarified invalid map and missing map faults.</td></tr><tr><td>2005-04-22 @ 20:01</td><td>mhadley</td><td>Added resolution to lc32 - added note warning of infoset changes due to IsReferenceParameter addition when binding [reference parameter] o SOAP.</td></tr><tr><td>2005-04-22 @ 19:51</td><td>mhadley</td><td>Added resolution to lc31 - clarified what to do if a reference parameter already has an IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:46</td><td>mhadley</td><td>Added resolution to lc30 - added new section for definition of IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:26</td><td>mhadley</td><td>Added resolution to lc29 - capitalized first character of IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:07</td><td>mhadley</td><td>Added resolution to lc27 - clarified confusing use of XML infoset terminology in XML representation of properties.</td></tr><tr><td>2005-04-22 @ 18:58</td><td>mhadley</td><td>Added resolution to lc24 - editorial nits.</td></tr><tr><td>2005-04-22 @ 18:49</td><td>mhadley</td><td>Added resolution to lc23 - changed IRI to URI for constant values that are URIs.</td></tr><tr><td>2005-04-22 @ 15:27</td><td>mhadley</td><td>Added resolution to lc1 - clarified impact of omiting [message id], [reply endpoint] and [fault endpoint] on fault message generation</td></tr><tr><td>2005-04-12 @ 13:17</td><td>mhadley</td><td>Fixed closing element in example</td></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Added sentence about SOAP 1.1 to section 4</td></tr><tr><td>2005-03-18 @ 23:21</td><td>mgudgin</td><td>s/Addresssing/Addressing</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 @ 03:16</td><td>mhadley</td><td>Incorporated additional issue resolution text for issues 7 and 44 from H. Haas.</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-09 @ 07:11</td><td>mhadley</td><td>Fixed example that didn't reflect the chnage from wsa:Type to wsa:isReferenceParameter</td></tr><tr><td>2005-03-08 @ 20:50</td><td>mhadley</td><td>Added resolution to issue 53 (schema tweaks)</td></tr><tr><td>2005-03-02 @ 21:18</td><td>mhdley</td><td>Added resolution to issue 4</td></tr><tr><td>2005-03-02 @ 20:30</td><td>mhadley</td><td>Added resolution to issue 7</td></tr><tr><td>2005-03-02 @ 19:36</td><td>mhadley</td><td>Added resolution to issues 22 and 51/</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-17 @ 15:37</td><td>mhadley</td><td>Added issue 47 resolution</td></tr><tr><td>2005-02-15 @ 22:06</td><td>mhadley</td><td>Fixed some references to message information headers to message information properties</td></tr></table>
        </div>
        <div class="div2">
          
! <h3><a name="N66876"></a>B.2 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-24 @ 20:22</td><td>mgudgin</td><td>Removed spurious reference to section 3.3.2 from Section 3</td></tr><tr><td>2005-01-23 @ 21:11</td><td>mgudgin</td><td>Incorporated resolution of issue i008; added wsa:Type attribute to reference parameters</td></tr><tr><td>2005-01-20 @ 13:10</td><td>mgudgin</td><td>Removed text from first paragraph of section 3 per resolution of issue i040</td></tr><tr><td>2005-01-16 @ 22:41</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</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>Switched 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="N66886"></a>B.3 Changes Since Submission</h3>
          <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-11-24 @ 15:32</td><td>mhadley</td><td>Added note that addressing is backwards compatible with SOAP 1.1</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-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 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</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>
        </div>
Received on Wednesday, 18 May 2005 19:58:01 GMT

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