WWW/2002/ws/ra/edcopies wsenum.html,1.26,1.27 wsenum.xml,1.17,1.18 wseventing.html,1.31,1.32 wseventing.xml,1.22,1.23 wsmex.html,1.29,1.30 wsmex.xml,1.20,1.21 wsrt.html,1.26,1.27 wsrt.xml,1.15,1.16 wst.html,1.24,1.25 wst.xml,1.20,1.21

Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv12062

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
	wsmex.html wsmex.xml wsrt.html wsrt.xml wst.html wst.xml 
Log Message:
First part of 6666


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- wst.xml	19 Mar 2009 14:11:56 -0000	1.20
+++ wst.xml	23 Mar 2009 19:38:29 -0000	1.21
@@ -237,7 +237,7 @@
                 <loc href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</loc>
               </td>
               <td>
-                <bibref ref="WsAddressing"/>
+                <bibref ref="AddrCore"/>
               </td>
             </tr>
             <tr>
@@ -351,9 +351,55 @@
        XML namespace prefixes (see <specref ref="xmlnamespaces"/>) are used 
        to indicate the namespace of the element being defined.
       </p>
-          </item>
-        </ulist>
-      </div2>
+     </item>
+    </ulist>
+
+    <p>
+     In addition to Message Information Header properties
+     <bibref ref="AddrCore"/>,
+     this specification uses the following properties to define messages:
+    </p>
+
+    <glist>
+     <gitem>
+      <label> <kw>[Headers]</kw> </label>
+      <def>
+       <p> Unordered message headers. </p>
+      </def>
+     </gitem>
+
+     <gitem>
+      <label> <kw>[Action]</kw> </label>
+      <def>
+       <p> The value to be used for the wsa:Action URI. </p>
+      </def>
+     </gitem>
+
+     <gitem>
+      <label> <kw>[Body]</kw> </label>
+      <def>
+       <p> A message body. </p>
+      </def>
+     </gitem>
+    </glist>
+
+    <p>
+     These properties bind to a SOAP Envelope as follows:
+    </p>
+
+    <example>
+     <eg>&lt;s:Envelope&gt;
+  &lt;s:Header&gt;
+    <kw>[Headers]</kw>
+    &lt;wsa:Action&gt;<kw>[Action]</kw>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<kw>[Body]</kw>&lt;/s:Body&gt;
+&lt;/s:Envelope&gt;</eg>
+    </example>
+
+   </div2>
+
       <div2 id="compliance">
         <head>Compliance</head>
         <p>An implementation is not compliant with this specification if it fails to
@@ -380,7 +426,7 @@
       <p>
        All messages defined by this specification MUST be sent
        to a Web service that is addressable by an EPR
-       <bibref ref="WsAddressing"/>.
+       <bibref ref="AddrCore"/>.
       </p>
 
       <div2 id="Get">
@@ -1450,12 +1496,16 @@
      </titleref>
      , M. Gudgin, et al, June 2003.
     </bibl>
-        <bibl key="WS-Addressing" id="WsAddressing" href="http://www.w3.org/2005/08/addressing/">
-          <titleref>
-      W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
-     </titleref>
-     , May 2006.
+
+    <bibl key="WS-Addressing" id="AddrCore"
+     href="http://www.w3.org/2005/08/addressing/">
+      <titleref>
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+      </titleref>
+      , May 2006.
     </bibl>
+
+
         <bibl key="WS-Policy" id="WsPolicy" href="http://schemas.xmlsoap.org/ws/2004/09/policy">
           <titleref>
       S. Bajaj, et al, "Web Services Policy Framework (WS-Policy)," 
@@ -1783,6 +1833,13 @@
          <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</loc>
         </td>
        </tr>
+       <tr>
+        <td> 2009/03/23 </td>
+        <td> DD </td>
+        <td> Added resolution of issue 
+         <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</loc>
+        </td>
+       </tr>
       </tbody>
      </table>
     </div1>

Index: wsrt.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- wsrt.xml	19 Mar 2009 14:11:55 -0000	1.15
+++ wsrt.xml	23 Mar 2009 19:38:29 -0000	1.16
@@ -460,7 +460,7 @@
       <tr>
        <td> wsa </td>
        <td> http://www.w3.org/2005/08/addressing </td>
-       <td> <bibref ref="WsAddressing"/> </td>
+       <td> <bibref ref="AddrCore"/> </td>
       </tr>
       <tr>
        <td> wsmex </td>
@@ -589,10 +589,10 @@
       </p>
      </item>
     </ulist>
-    
+
     <p>
      In addition to Message Information Header properties
-     <bibref ref="WsAddressing"/>, 
+     <bibref ref="AddrCore"/>,
      this specification uses the following properties to define messages:
     </p>
 
@@ -600,7 +600,7 @@
      <gitem>
       <label> <kw>[Headers]</kw> </label>
       <def>
-       <p>Unordered message headers. </p>
+       <p> Unordered message headers. </p>
       </def>
      </gitem>
 
@@ -618,19 +618,19 @@
       </def>
      </gitem>
     </glist>
-    
+
     <p>
      These properties bind to a SOAP Envelope as follows:
     </p>
 
     <example>
      <eg>&lt;s:Envelope&gt;
- &lt;s:Header&gt;
-  <kw>[Headers]</kw>
-  &lt;wsa:Action&gt;<kw>[Action]</kw>&lt;/wsa:Action&gt;
-  ...
- &lt;/s:Header&gt;
- &lt;s:Body&gt;<kw>[Body]</kw>&lt;/s:Body&gt;
+  &lt;s:Header&gt;
+    <kw>[Headers]</kw>
+    &lt;wsa:Action&gt;<kw>[Action]</kw>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<kw>[Body]</kw>&lt;/s:Body&gt;
 &lt;/s:Envelope&gt;</eg>
     </example>
     
@@ -670,7 +670,7 @@
    <p>
     All messages defined by this specification MUST be sent
     to a Web service that is addressable by an EPR
-    <bibref ref="WsAddressing"/>.
+    <bibref ref="AddrCore"/>.
    </p>
 
    <div2 id="fragments">
@@ -2074,7 +2074,7 @@
     The faults defined in this section are generated if the condition
     stated in the preamble is met. Faults are targeted at a
     destination endpoint according to the fault handling rules defined
-    in <bibref ref="WsAddressing"/>.
+    in <bibref ref="AddrCore"/>.
    </p>
    
    <p>
@@ -2167,7 +2167,7 @@
     
     <p>
      The SOAP bindings for this fault are defined in 
-     <bibref ref="WsAddressing"/>.
+     <bibref ref="AddrCore"/>.
     </p>
    </div2>
 
@@ -2183,7 +2183,7 @@
     
     <p>
      The SOAP bindings for this fault are defined in 
-     <bibref ref="WsAddressing"/>.
+     <bibref ref="AddrCore"/>.
     </p>
    </div2>
 
@@ -2762,12 +2762,12 @@
      , M. Gudgin, et al, June 2003.
     </bibl>
 
-    <bibl key="WS-Addressing" id="WsAddressing"
+    <bibl key="WS-Addressing" id="AddrCore"
      href="http://www.w3.org/2005/08/addressing/">
-     <titleref>
-      W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
-     </titleref>
-     , May 2006.
+      <titleref>
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+      </titleref>
+      , May 2006.
     </bibl>
 
     <bibl key="WSDL 1.1" id="Wsdl11"
@@ -3770,6 +3770,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6548">6548</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/03/23 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- wseventing.html	19 Mar 2009 14:14:22 -0000	1.31
+++ wseventing.html	23 Mar 2009 19:38:29 -0000	1.32
@@ -1,6 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Eventing (WS-Eventing)</title><style type="text/css">
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Eventing (WS-Eventing)</title><style type="text/css">
 code           { font-family: monospace; }
 
 div.constraint,
@@ -30,63 +28,58 @@
 div.exampleWrapper { margin: 4px }
 div.exampleHeader { font-weight: bold;
                     margin: 4px}
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css" /></head><body><div class="head">
-<h1><a name="title" id="title"></a>Web Services Eventing (WS-Eventing)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd>
-    <a href="http://www.w3.org/TR/ws-eventing">http://www.w3.org/TR/ws-eventing
-   </a>
-  </dd><dt>Previous version:</dt><dd>
-   <a href="http://www.w3.org/TR/2009/WD-ws-eventing-20090317">http://www.w3.org/TR/2009/WD-ws-eventing-20090317
-   </a>
-  </dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr /><div>
-<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
+<h1><a name="title" id="title"/>Web Services Eventing (WS-Eventing)</h1>
+<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-eventing">http://www.w3.org/TR/ws-eventing
+   </a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-eventing-20090317">http://www.w3.org/TR/2009/WD-ws-eventing-20090317</a></dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consrtium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
     This specification describes a protocol that allows Web
     services to subscribe to or accept subscriptions for event
     notification messages.
    </p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
+<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
         no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br />
-2 <a href="#intro">Introduction</a><br />
-&nbsp;&nbsp;&nbsp;2.1 <a href="#reqs">Requirements</a><br />
-&nbsp;&nbsp;&nbsp;2.2 <a href="#DeliveryModes">Delivery Modes</a><br />
-&nbsp;&nbsp;&nbsp;2.3 <a href="#SubMgr">Subscription Managers</a><br />
-&nbsp;&nbsp;&nbsp;2.4 <a href="#example">Example</a><br />
-3 <a href="#notterms">Notations and Terminology</a><br />
-&nbsp;&nbsp;&nbsp;3.1 <a href="#conventions">Notational Conventions</a><br />
-&nbsp;&nbsp;&nbsp;3.2 <a href="#namespaces">XML Namespaces</a><br />
-&nbsp;&nbsp;&nbsp;3.3 <a href="#terms">Terminology</a><br />
-&nbsp;&nbsp;&nbsp;3.4 <a href="#compliance">Compliance</a><br />
-4 <a href="#SubMsgs">Subscription Messages</a><br />
-&nbsp;&nbsp;&nbsp;4.1 <a href="#Subscribe">Subscribe</a><br />
-&nbsp;&nbsp;&nbsp;4.2 <a href="#Renew">Renew</a><br />
-&nbsp;&nbsp;&nbsp;4.3 <a href="#GetStatus">GetStatus</a><br />
-&nbsp;&nbsp;&nbsp;4.4 <a href="#Unsubscribe">Unsubscribe</a><br />
-&nbsp;&nbsp;&nbsp;4.5 <a href="#SubscriptionEnd">Subscription End</a><br />
-5 <a href="#Notifications">Notifications</a><br />
-6 <a href="#Faults">Faults</a><br />
-&nbsp;&nbsp;&nbsp;6.1 <a href="#ModeUnavailable">DeliveryModeRequestedUnavailable</a><br />
-&nbsp;&nbsp;&nbsp;6.2 <a href="#InvalidExpirationTime">InvalidExpirationTime</a><br />
-&nbsp;&nbsp;&nbsp;6.3 <a href="#UnsupportedExpirationType">UnsupportedExpirationType</a><br />
-&nbsp;&nbsp;&nbsp;6.4 <a href="#FilteringNotSupported">FilteringNotSupported</a><br />
-&nbsp;&nbsp;&nbsp;6.5 <a href="#FilteringRequestedUnavailable">FilteringRequestedUnavailable</a><br />
-&nbsp;&nbsp;&nbsp;6.6 <a href="#EventSourceUnableToProcess">EventSourceUnableToProcess</a><br />
-&nbsp;&nbsp;&nbsp;6.7 <a href="#UnableToRenew">UnableToRenew</a><br />
-&nbsp;&nbsp;&nbsp;6.8 <a href="#InvalidMessage">InvalidMessage</a><br />
-&nbsp;&nbsp;&nbsp;6.9 <a href="#DeliveryFormatRequestedUnavailable">DeliveryFormatRequestUnavailable</a><br />
-7 <a href="#Security">Security Considerations</a><br />
-&nbsp;&nbsp;&nbsp;7.1 <a href="#MessageSecurity">Message Security</a><br />
-&nbsp;&nbsp;&nbsp;7.2 <a href="#AccessControl">Access Control</a><br />
-8 <a href="#ImplConsideration">Implementation Considerations</a><br />
-9 <a href="#acks">Acknowledgements</a><br />
-10 <a href="#refs">References</a><br />
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br/>
+2 <a href="#intro">Introduction</a><br/>
+&nbsp;&nbsp;&nbsp;2.1 <a href="#reqs">Requirements</a><br/>
+&nbsp;&nbsp;&nbsp;2.2 <a href="#DeliveryModes">Delivery Modes</a><br/>
+&nbsp;&nbsp;&nbsp;2.3 <a href="#SubMgr">Subscription Managers</a><br/>
+&nbsp;&nbsp;&nbsp;2.4 <a href="#example">Example</a><br/>
+3 <a href="#notterms">Notations and Terminology</a><br/>
+&nbsp;&nbsp;&nbsp;3.1 <a href="#conventions">Notational Conventions</a><br/>
+&nbsp;&nbsp;&nbsp;3.2 <a href="#namespaces">XML Namespaces</a><br/>
+&nbsp;&nbsp;&nbsp;3.3 <a href="#terms">Terminology</a><br/>
+&nbsp;&nbsp;&nbsp;3.4 <a href="#compliance">Compliance</a><br/>
+4 <a href="#SubMsgs">Subscription Messages</a><br/>
+&nbsp;&nbsp;&nbsp;4.1 <a href="#Subscribe">Subscribe</a><br/>
+&nbsp;&nbsp;&nbsp;4.2 <a href="#Renew">Renew</a><br/>
+&nbsp;&nbsp;&nbsp;4.3 <a href="#GetStatus">GetStatus</a><br/>
+&nbsp;&nbsp;&nbsp;4.4 <a href="#Unsubscribe">Unsubscribe</a><br/>
+&nbsp;&nbsp;&nbsp;4.5 <a href="#SubscriptionEnd">Subscription End</a><br/>
+5 <a href="#Notifications">Notifications</a><br/>
+6 <a href="#Faults">Faults</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#ModeUnavailable">DeliveryModeRequestedUnavailable</a><br/>
+&nbsp;&nbsp;&nbsp;6.2 <a href="#InvalidExpirationTime">InvalidExpirationTime</a><br/>
+&nbsp;&nbsp;&nbsp;6.3 <a href="#UnsupportedExpirationType">UnsupportedExpirationType</a><br/>
+&nbsp;&nbsp;&nbsp;6.4 <a href="#FilteringNotSupported">FilteringNotSupported</a><br/>
+&nbsp;&nbsp;&nbsp;6.5 <a href="#FilteringRequestedUnavailable">FilteringRequestedUnavailable</a><br/>
+&nbsp;&nbsp;&nbsp;6.6 <a href="#EventSourceUnableToProcess">EventSourceUnableToProcess</a><br/>
+&nbsp;&nbsp;&nbsp;6.7 <a href="#UnableToRenew">UnableToRenew</a><br/>
+&nbsp;&nbsp;&nbsp;6.8 <a href="#InvalidMessage">InvalidMessage</a><br/>
+&nbsp;&nbsp;&nbsp;6.9 <a href="#DeliveryFormatRequestedUnavailable">DeliveryFormatRequestUnavailable</a><br/>
+7 <a href="#Security">Security Considerations</a><br/>
+&nbsp;&nbsp;&nbsp;7.1 <a href="#MessageSecurity">Message Security</a><br/>
+&nbsp;&nbsp;&nbsp;7.2 <a href="#AccessControl">Access Control</a><br/>
+8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
+9 <a href="#acks">Acknowledgements</a><br/>
+10 <a href="#refs">References</a><br/>
 </p>
-<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#Metadata">Service Metadata for Eventing</a><br />
-B <a href="#Schema">XML Schema</a><br />
-C <a href="#WSDL">WSDL</a><br />
-D <a href="#changelog">Change Log</a><br />
-</p></div><hr /><div class="body"><div class="div1">
-<h2><a name="composable" id="composable"></a>1 Composable Architecture</h2><p>
+<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Metadata">Service Metadata for Eventing</a><br/>
+B <a href="#Schema">XML Schema</a><br/>
+C <a href="#WSDL">WSDL</a><br/>
+D <a href="#changelog">Change Log</a><br/>
+</p></div><hr/><div class="body"><div class="div1">
+<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
     By using the XML, SOAP <a href="#SOAP11">[SOAP 1.1]</a>,
     <a href="#SOAP121">[SOAP 1.2]</a>, and WSDL <a href="#WSDL11">[WSDL 1.1]</a>
     extensibility models, the Web service
@@ -97,7 +90,7 @@
     and/or transacted message delivery and to express Web service and
     client policy.
    </p></div><div class="div1">
-<h2><a name="intro" id="intro"></a>2 Introduction</h2><p>
+<h2><a name="intro" id="intro"/>2 Introduction</h2><p>
     Web services often want to receive messages when events occur
     in other services and applications. A mechanism for registering
     interest is needed because the set of Web services interested in
@@ -124,7 +117,7 @@
     the delivery mechanisms capable of being supported by this
     specification.
    </p><div class="div2">
-<h3><a name="reqs" id="reqs"></a>2.1 Requirements</h3><p>
+<h3><a name="reqs" id="reqs"/>2.1 Requirements</h3><p>
      This specification intends to meet the following requirements:
     </p><ul><li><p>
        Define means to create and delete event subscriptions.
@@ -152,7 +145,7 @@
        limited to) both SOAP 1.1 <a href="#SOAP11">[SOAP 1.1]</a>
        and SOAP 1.2 <a href="#SOAP121">[SOAP 1.2]</a> Envelopes.
       </p></li></ul></div><div class="div2">
-<h3><a name="DeliveryModes" id="DeliveryModes"></a>2.2 Delivery Modes</h3><p>
+<h3><a name="DeliveryModes" id="DeliveryModes"/>2.2 Delivery Modes</h3><p>
      While the general pattern of asynchronous, event-based
      messages is extremely common, different applications often
      require different event message delivery mechanisms. For
@@ -191,7 +184,7 @@
      element. Use of unwrapped format indicates that notification messages
      are not wrapped.
     </p></div><div class="div2">
-<h3><a name="SubMgr" id="SubMgr"></a>2.3 Subscription Managers</h3><p>
+<h3><a name="SubMgr" id="SubMgr"/>2.3 Subscription Managers</h3><p>
      In some scenarios the event source itself manages the
      subscriptions it has created. In other scenarios, for example a
      geographically distributed publish-and-subscribe system, it may
@@ -213,11 +206,10 @@
      whether it is the event source itself or some separate Web
      service.
     </p></div><div class="div2">
-<h3><a name="example" id="example"></a>2.4 Example</h3><p>
-     <a href="#Table1">Example 2-1</a> lists a hypothetical request to create a 
+<h3><a name="example" id="example"/>2.4 Example</h3><p><a href="#Table1">Example 2-1</a> lists a hypothetical request to create a 
      subscription for storm warnings.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table1" id="Table1"></a>Example 2-1: Hypothetical request to create a subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope
+<div class="exampleHeader"><a name="Table1" id="Table1"/>Example 2-1: Hypothetical request to create a subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -264,11 +256,10 @@
      pattern where the event sink lists a reference parameter (Line 26)
      that identifies the subscription and will be included in each
      notification.
-    </p><p>
-     <a href="#Table2">Example 2-2</a> lists a hypothetical response to the request in
+    </p><p><a href="#Table2">Example 2-2</a> lists a hypothetical response to the request in
      <a href="#Table1">Example 2-1</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table2" id="Table2"></a>Example 2-2: Hypothetical response to a subscribe request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope
+<div class="exampleHeader"><a name="Table2" id="Table2"/>Example 2-2: Hypothetical response to a subscribe request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -306,11 +297,11 @@
      indicates the subscription will expire in 30 hours unless
      renewed.
     </p></div></div><div class="div1">
-<h2><a name="notterms" id="notterms"></a>3 Notations and Terminology</h2><p>
+<h2><a name="notterms" id="notterms"/>3 Notations and Terminology</h2><p>
     This section specifies the notations, namespaces, and
     terminology used in this specification.
    </p><div class="div2">
-<h3><a name="conventions" id="conventions"></a>3.1 Notational Conventions</h3><p>
+<h3><a name="conventions" id="conventions"/>3.1 Notational Conventions</h3><p>
      The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
      "OPTIONAL" in this document are to be interpreted as described in
@@ -344,41 +335,40 @@
        XML namespace prefixes (see <a href="#Table3">Table 3-1</a>)
        are used to indicate the namespace of the element being
        defined.
-      </p></li></ul></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"></a>3.2 XML Namespaces</h3><p>
+      </p></li></ul><p>
+     In addition to Message Information Header properties
+     <a href="#AddrCore">[WS-Addressing]</a>,
+     this specification uses the following properties to define messages:
+    </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+     These properties bind to a SOAP Envelope as follows:
+    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope&gt;
+  &lt;s:Header&gt;
+    <b>[Headers]</b>
+    &lt;wsa:Action&gt;<b>[Action]</b>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt;
+&lt;/s:Envelope&gt;</pre></div></div></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>3.2 XML Namespaces</h3><p>
      The XML namespace URI that MUST be used by implementations of
      this specification is:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-evt">http://www.w3.org/2009/02/ws-evt</a></pre></div></div><p>
-     <a href="#Table3">Table 3-1</a> lists XML namespaces that are used in this
+    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-evt">http://www.w3.org/2009/02/ws-evt</a></pre></div></div><p><a href="#Table3">Table 3-1</a> lists XML namespaces that are used in this
      specification. The choice of any namespace prefix is arbitrary
      and not semantically significant.
-    </p><a name="Table3" id="Table3"></a><table border="1"><caption>Table 3-1:  Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td>s</td><td>(Either SOAP 1.1 or 1.2)</td><td>(Either SOAP 1.1 or 1.2)</td></tr><tr><td>s11</td><td>
-        <a href="http://schemas.xmlsoap.org/soap/envelope/">
+    </p><a name="Table3" id="Table3"/><table border="1"><caption>Table 3-1:  Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td>s</td><td>(Either SOAP 1.1 or 1.2)</td><td>(Either SOAP 1.1 or 1.2)</td></tr><tr><td>s11</td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">
          http://schemas.xmlsoap.org/soap/envelope/
-        </a>
-       </td><td>SOAP 1.1 <a href="#SOAP11">[SOAP 1.1]</a></td></tr><tr><td>s12</td><td>
-        <a href="http://www.w3.org/2003/05/soap-envelope">
+        </a></td><td>SOAP 1.1 <a href="#SOAP11">[SOAP 1.1]</a></td></tr><tr><td>s12</td><td><a href="http://www.w3.org/2003/05/soap-envelope">
          http://www.w3.org/2003/05/soap-envelope
-        </a>
-       </td><td>SOAP 1.2 <a href="#SOAP121">[SOAP 1.2]</a></td></tr><tr><td>wsdl</td><td>
-        <a href="http://schemas.xmlsoap.org/wsdl/">
+        </a></td><td>SOAP 1.2 <a href="#SOAP121">[SOAP 1.2]</a></td></tr><tr><td>wsdl</td><td><a href="http://schemas.xmlsoap.org/wsdl/">
          http://schemas.xmlsoap.org/wsdl/
-        </a>
-       </td><td>WSDL <a href="#WSDL11">[WSDL 1.1]</a></td></tr><tr><td>wsa</td><td>
-        <a href="http://www.w3.org/2005/08/addressing">
+        </a></td><td>WSDL <a href="#WSDL11">[WSDL 1.1]</a></td></tr><tr><td>wsa</td><td><a href="http://www.w3.org/2005/08/addressing">
          http://www.w3.org/2005/08/addressing
-        </a>
-       </td><td>WS-Addressing <a href="#WSAddressing">[WS-Addressing]</a></td></tr><tr><td>wse</td><td>
-        <a href="http://www.w3.org/2009/02/ws-evt">
+        </a></td><td>WS-Addressing <a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td>wse</td><td><a href="http://www.w3.org/2009/02/ws-evt">
          http://www.w3.org/2009/02/ws-evt
-        </a>
-       </td><td>This specification</td></tr><tr><td>xs</td><td>
-        <a href="http://www.w3.org/2001/XMLSchema">
+        </a></td><td>This specification</td></tr><tr><td>xs</td><td><a href="http://www.w3.org/2001/XMLSchema">
          http://www.w3.org/2001/XMLSchema
-        </a>
-       </td><td>
-        XML Schema <a href="#XMLSchema1">[XML Schema, Part 1]</a>, <a href="#XMLSchema2">[XML Schema, Part 2]</a>
-       </td></tr></tbody></table><p>
+        </a></td><td>
+        XML Schema <a href="#XMLSchema1">[XML Schema, Part 1]</a>, <a href="#XMLSchema2">[XML Schema, Part 2]</a></td></tr></tbody></table><p>
      The working group intends to update the value of the Web Services
      Enumeration namespace URI each time a new version of this document is
      published until such time that the document reaches Candidate
@@ -395,7 +385,7 @@
       http://www.w3.org/2005/07/13-nsuri
       </a>.
     </p></div><div class="div2">
-<h3><a name="terms" id="terms"></a>3.3 Terminology</h3><dl><dt class="label"> Delivery Mode </dt><dd><p>
+<h3><a name="terms" id="terms"/>3.3 Terminology</h3><dl><dt class="label"> Delivery Mode </dt><dd><p>
         The mechanism by which event messages are delivered from
         the source to the sink.
        </p></dd><dt class="label"> Event Source </dt><dd><p>
@@ -416,7 +406,7 @@
         status of, renew, and/or delete subscriptions on behalf of an
         event source.
        </p></dd></dl></div><div class="div2">
-<h3><a name="compliance" id="compliance"></a>3.4 Compliance</h3><p>
+<h3><a name="compliance" id="compliance"/>3.4 Compliance</h3><p>
      An implementation is not compliant with this specification if
      it fails to satisfy one or more of the MUST or REQUIRED level
      requirements defined herein. A SOAP Node MUST NOT use the XML
@@ -431,7 +421,7 @@
      normative outlines, which in turn takes precedence over the XML
      Schema and WSDL descriptions.
     </p></div></div><div class="div1">
-<h2><a name="SubMsgs" id="SubMsgs"></a>4 Subscription Messages</h2><p>
+<h2><a name="SubMsgs" id="SubMsgs"/>4 Subscription Messages</h2><p>
     To create, renew, and delete subscriptions, subscribers send
     request messages to event sources and subscription managers.
    </p><p>
@@ -460,9 +450,9 @@
    </p><p>
     All messages defined by this specification MUST be sent
     to a Web service that is addressable by an EPR
-    <a href="#WSAddressing">[WS-Addressing]</a>.
+    <a href="#AddrCore">[WS-Addressing]</a>.
    </p><div class="div2">
-<h3><a name="Subscribe" id="Subscribe"></a>4.1 Subscribe</h3><p>
+<h3><a name="Subscribe" id="Subscribe"/>4.1 Subscribe</h3><p>
      To create a subscription, a subscriber sends a request message
      of the following form to an event source:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope ...&gt; 
@@ -590,7 +580,7 @@
         source MAY generate a wse:FilteringRequestedUnavailable fault
         indicating that the requested filter dialect is not
         supported.
-       </p></dd><dt class="label"><a name="Dialect" id="Dialect"></a> /s:Envelope/s:Body/*/wse:Filter/@Dialect </dt><dd><p>
+       </p></dd><dt class="label"><a name="Dialect" id="Dialect"/> /s:Envelope/s:Body/*/wse:Filter/@Dialect </dt><dd><p>
         Implied value is "http://www.w3.org/TR/1999/REC-xpath-19991116".
        </p><p>
         While an XPath predicate expression provides great
@@ -617,7 +607,7 @@
           /s:Envelope/s:Body/*/wse:Filter.
          </p></li></ul></dd></dl><p>
      Other message information headers defined by WS-Addressing
-     <a href="#WSAddressing">[WS-Addressing]</a> MAY be included in
+     <a href="#AddrCore">[WS-Addressing]</a> MAY be included in
      the request and response messages, according to the usage and
      semantics defined in WS-Addressing.
     </p><p>
@@ -678,11 +668,10 @@
      request MUST fail, and the event source MAY generate a
      wse:EventSourceUnableToProcess fault indicating that the request
      was not accepted.
-    </p><p>
-     <a href="#Table4">Example 4-1</a> lists another hypothetical request to create a
+    </p><p><a href="#Table4">Example 4-1</a> lists another hypothetical request to create a
      subscription.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table4" id="Table4"></a>Example 4-1: Second hypothetical request to create a subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
+<div class="exampleHeader"><a name="Table4" id="Table4"/>Example 4-1: Second hypothetical request to create a subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -745,11 +734,10 @@
     </p><p>
      Lines (42-45) indicate the event sink only wants weather
      reports where topic is storms, using a custom filter dialect.
-    </p><p>
-     <a href="#Table5">Example 4-2</a> lists a hypothetical response to the request in
+    </p><p><a href="#Table5">Example 4-2</a> lists a hypothetical response to the request in
      <a href="#Table4">Example 4-1</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table5" id="Table5"></a>Example 4-2: Hypothetical response to second subscribe request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
+<div class="exampleHeader"><a name="Table5" id="Table5"/>Example 4-2: Hypothetical response to second subscribe request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -796,7 +784,7 @@
      than the requested expiration (Line (41) of 
      <a href="#Table4">Example 4-1</a>).
     </p></div><div class="div2">
-<h3><a name="Renew" id="Renew"></a>4.2 Renew</h3><p>
+<h3><a name="Renew" id="Renew"/>4.2 Renew</h3><p>
      To update the expiration for a subscription, subscription
      managers MUST support requests to renew subscriptions.
     </p><p>
@@ -854,11 +842,10 @@
     </p><p>
      Other components of the outline above are not further
      constrained by this specification.
-    </p><p>
-     <a href="#Table6">Example 4-3</a> lists a hypothetical request to renew the 
+    </p><p><a href="#Table6">Example 4-3</a> lists a hypothetical request to renew the 
      subscription created in <a href="#Table5">Example 4-2</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table6" id="Table6"></a>Example 4-3: Hypothetical request to renew second subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
+<div class="exampleHeader"><a name="Table6" id="Table6"/>Example 4-3: Hypothetical request to renew second subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -892,11 +879,10 @@
      <a href="#Table5">Example 4-2</a>. Line (25) in <a href="#Table6">Example 4-3</a>
      indicates the request is to extend the
      subscription until 26 June 2004 at 9:07 PM Pacific.
-    </p><p>
-     <a href="#Table7">Example 4-4</a> lists a hypothetical response to the request in
+    </p><p><a href="#Table7">Example 4-4</a> lists a hypothetical response to the request in
      <a href="#Table6">Example 4-3</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table7" id="Table7"></a>Example 4-4: Hypothetical response to renew request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope
+<div class="exampleHeader"><a name="Table7" id="Table7"/>Example 4-4: Hypothetical response to renew request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -920,7 +906,7 @@
      subscription has been extended only until 26 June 2004 at
      noon.
     </p></div><div class="div2">
-<h3><a name="GetStatus" id="GetStatus"></a>4.3 GetStatus</h3><p>
+<h3><a name="GetStatus" id="GetStatus"/>4.3 GetStatus</h3><p>
      To get the status of a subscription, the subscriber sends a
      request of the following form to the subscription manager:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope ...&gt; 
@@ -963,11 +949,10 @@
      a response to a renew request (see <a href="#Renew"><b>4.2 Renew</b></a>).
      Other components of the outline above are not further
      constrained by this specification.
-    </p><p>
-     <a href="#Table8">Example 4-5</a> lists a hypothetical request to get the 
+    </p><p><a href="#Table8">Example 4-5</a> lists a hypothetical request to get the 
      status of the subscription created in <a href="#Table5">Example 4-2</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table8" id="Table8"></a>Example 4-5: Hypothetical request to get the status of the second subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope
+<div class="exampleHeader"><a name="Table8" id="Table8"/>Example 4-5: Hypothetical request to get the status of the second subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -997,11 +982,10 @@
      a subscription. Lines (16-21) indicate that the request is sent
      to the subscription manager for the subscription created in
      <a href="#Table5">Example 4-2</a>.
-    </p><p>
-     <a href="#Table9">Example 4-6</a> lists a hypothetical response to the request in
+    </p><p><a href="#Table9">Example 4-6</a> lists a hypothetical response to the request in
      <a href="#Table8">Example 4-5</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table9" id="Table9"></a>Example 4-6: Hypothetical response to get status request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
+<div class="exampleHeader"><a name="Table9" id="Table9"/>Example 4-6: Hypothetical response to get status request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -1024,7 +1008,7 @@
      Line (17) in <a href="#Table9">Example 4-6</a> indicates the
      subscription will expire on 26 June 2004 at noon.
     </p></div><div class="div2">
-<h3><a name="Unsubscribe" id="Unsubscribe"></a>4.4 Unsubscribe</h3><p>
+<h3><a name="Unsubscribe" id="Unsubscribe"/>4.4 Unsubscribe</h3><p>
      Though subscriptions expire eventually, to minimize resources,
      the subscribing event sink SHOULD explicitly delete a
      subscription when it no longer wants notifications associated
@@ -1067,11 +1051,10 @@
 &lt;/s:Envelope&gt; </pre></div></div><p>
      Components of the outline listed above are not further
      constrained by this specification.
-    </p><p>
-     <a href="#Table10">Example 4-7</a> lists a hypothetical request to delete the
+    </p><p><a href="#Table10">Example 4-7</a> lists a hypothetical request to delete the
      subscription created in <a href="#Table5">Example 4-2</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table10" id="Table10"></a>Example 4-7: Hypothetical unsubscribe request to delete second subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
+<div class="exampleHeader"><a name="Table10" id="Table10"/>Example 4-7: Hypothetical unsubscribe request to delete second subscription</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt"
@@ -1101,11 +1084,10 @@
      message is a request to delete a subscription. Lines (16-21)
      indicate that the request is addressed to the manager for the
      subscription created in <a href="#Table5">Example 4-2</a>.
-    </p><p>
-     <a href="#Table11">Example 4-8</a> lists a hypothetical response to the request in
+    </p><p><a href="#Table11">Example 4-8</a> lists a hypothetical response to the request in
      <a href="#Table10">Example 4-7</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table11" id="Table11"></a>Example 4-8: Hypothetical response to unsubscribe request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
+<div class="exampleHeader"><a name="Table11" id="Table11"/>Example 4-8: Hypothetical response to unsubscribe request</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing" &gt;
 (04)   &lt;s12:Header&gt;
@@ -1119,7 +1101,7 @@
 (12)   &lt;/s12:Header&gt;
 (13)   &lt;s12:Body /&gt;
 (14) &lt;/s12:Envelope&gt;</pre></div></div></div><div class="div2">
-<h3><a name="SubscriptionEnd" id="SubscriptionEnd"></a>4.5 Subscription End</h3><p>
+<h3><a name="SubscriptionEnd" id="SubscriptionEnd"/>4.5 Subscription End</h3><p>
      If the event source terminates a subscription unexpectedly,
      the event source SHOULD send a Subscription End SOAP message to
      the endpoint reference indicated when the subscription was
@@ -1179,18 +1161,17 @@
         for the unexpected subscription termination.
        </p></dd></dl><p>
      Other message information headers defined by WS-Addressing
-     <a href="#WSAddressing">[WS-Addressing]</a> MAY be included in
+     <a href="#AddrCore">[WS-Addressing]</a> MAY be included in
      the message, according to the usage and semantics defined in
      WS-Addressing.
     </p><p>
      Other components of the outline above are not further
      constrained by this specification.
-    </p><p>
-     <a href="#Table12">Example 4-9</a> lists a hypothetical SubscriptionEnd message
+    </p><p><a href="#Table12">Example 4-9</a> lists a hypothetical SubscriptionEnd message
      corresponding to an early termination of the subscription created
      in <a href="#Table4">Example 4-1</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table12" id="Table12"></a>Example 4-9: Hypothetical subscription end message</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
+<div class="exampleHeader"><a name="Table12" id="Table12"/>Example 4-9: Hypothetical subscription end message</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:wse="http://www.w3.org/2009/02/ws-evt" 
@@ -1218,7 +1199,7 @@
      Lines (26-28) indicate that the event source was going off
      line.
     </p></div></div><div class="div1">
-<h2><a name="Notifications" id="Notifications"></a>5 Notifications</h2><p>
+<h2><a name="Notifications" id="Notifications"/>5 Notifications</h2><p>
     This specification does not constrain notifications because
     any message MAY be a notification.
    </p><p>
@@ -1227,16 +1208,15 @@
     header blocks in the Subscribe request, in the
     /s:Envelope/s:Body/wse:Subscribe/wse:NotifyTo/wsa:ReferenceParameters
     element; per WS-Addressing 
-    <a href="#WSAddressing">[WS-Addressing]</a>, the event source MUST include
+    <a href="#AddrCore">[WS-Addressing]</a>, the event source MUST include
     each such literal SOAP header block in every notification sent to
     the endpoint addressed by
     /s:Envelope/s:Body/wse:Subscribe/wse:NotifyTo.
-   </p><p>
-    <a href="#Table13">Example 5-1</a> lists a hypothetical notification message sent as
+   </p><p><a href="#Table13">Example 5-1</a> lists a hypothetical notification message sent as
     part of the subscription created by the subscribe request in
     <a href="#Table4">Example 4-1</a>.
    </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="Table13" id="Table13"></a>Example 5-1: Hypothetical notification message</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
+<div class="exampleHeader"><a name="Table13" id="Table13"/>Example 5-1: Hypothetical notification message</div><div class="exampleInner"><pre>(01) &lt;s12:Envelope 
 (02)     xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04)     xmlns:ew="http://www.example.com/warnings"
@@ -1274,7 +1254,7 @@
     <a href="#Table4">Example 4-1</a>). Line (15) matches the filter in the
     subscribe request (Lines (42-45) in <a href="#Table4">Example 4-1</a>).
    </p></div><div class="div1">
-<h2><a name="Faults" id="Faults"></a>6 Faults</h2><p>
+<h2><a name="Faults" id="Faults"/>6 Faults</h2><p>
     All fault messages defined in this specification MUST be sent
     according to the rules described in WS-Addressing section 4. They
     are sent to the [fault endpoint], if present and valid. Otherwise
@@ -1329,77 +1309,67 @@
   &lt;/S11:Fault&gt;
  &lt;/S11:Body&gt;
 &lt;/S11:Envelope&gt; </pre></div></div><div class="div2">
-<h3><a name="ModeUnavailable" id="ModeUnavailable"></a>6.1 DeliveryModeRequestedUnavailable</h3><p>
+<h3><a name="ModeUnavailable" id="ModeUnavailable"/>6.1 DeliveryModeRequestedUnavailable</h3><p>
      This fault is sent when a Subscribe request specifies a
      delivery mode that is not supported by the event source.
      Optionally, this fault may contain a list of supported delivery
      mode URIs in the Detail property.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:DeliveryModeRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested delivery mode is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
         &lt;wse:SupportedDeliveryMode&gt; +
-        <br />
-        <em>Optional; one per delivery mode supported by the
-        receiver</em>
-       </td></tr></tbody></table></div><div class="div2">
-<h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"></a>6.2 InvalidExpirationTime</h3><p>
+        <br/><em>Optional; one per delivery mode supported by the
+        receiver</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"/>6.2 InvalidExpirationTime</h3><p>
      This fault is sent when a Subscribe request specifies an
      expiration time that is in the past or an expiration duration of
      zero.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:InvalidExpirationTime</td></tr><tr><td><b>[Reason]</b></td><td>The expiration time requested is invalid.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="UnsupportedExpirationType" id="UnsupportedExpirationType"></a>6.3 UnsupportedExpirationType</h3><p>
+<h3><a name="UnsupportedExpirationType" id="UnsupportedExpirationType"/>6.3 UnsupportedExpirationType</h3><p>
      This fault is sent when a Subscribe request specifies an
      expiration time and the event source is only capable of accepting
      expiration durations; for instance, if the event source does not
      have access to absolute time.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnsupportedExpirationType</td></tr><tr><td><b>[Reason]</b></td><td>Only expiration durations are supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="FilteringNotSupported" id="FilteringNotSupported"></a>6.4 FilteringNotSupported</h3><p>
+<h3><a name="FilteringNotSupported" id="FilteringNotSupported"/>6.4 FilteringNotSupported</h3><p>
      This fault is sent when a Subscribe request contains a filter
      and the event source does not support filtering.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>Filtering is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="FilteringRequestedUnavailable" id="FilteringRequestedUnavailable"></a>6.5 FilteringRequestedUnavailable</h3><p>
+<h3><a name="FilteringRequestedUnavailable" id="FilteringRequestedUnavailable"/>6.5 FilteringRequestedUnavailable</h3><p>
      This fault is sent when a Subscribe request specifies a filter
      dialect that the event source does not support. Optionally, this
      fault may contain a list of supported filter dialect URIs in the
      Detail property.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested filter dialect is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
         &lt;wse:SupportedDialect&gt; + 
-        <br />
-        <em>Optional; one per filter dialect supported by the
-        receiver</em>
-       </td></tr></tbody></table></div><div class="div2">
-<h3><a name="EventSourceUnableToProcess" id="EventSourceUnableToProcess"></a>6.6 EventSourceUnableToProcess</h3><p>
+        <br/><em>Optional; one per filter dialect supported by the
+        receiver</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="EventSourceUnableToProcess" id="EventSourceUnableToProcess"/>6.6 EventSourceUnableToProcess</h3><p>
      This fault is sent when the event source is not capable of
      fulfilling a Subscribe request for local reasons unrelated to the
      specific request.
-    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Receiver</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EventSourceUnableToProcess</td></tr><tr><td><b>[Reason]</b></td><td>
-        <em>Text explaining the failure; e.g., "The event
-        source has too many subscribers".</em>
-       </td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="UnableToRenew" id="UnableToRenew"></a>6.7 UnableToRenew</h3><p>
+    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Receiver</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EventSourceUnableToProcess</td></tr><tr><td><b>[Reason]</b></td><td><em>Text explaining the failure; e.g., "The event
+        source has too many subscribers".</em></td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="UnableToRenew" id="UnableToRenew"/>6.7 UnableToRenew</h3><p>
      This fault is sent when the event source is not capable of
      fulfilling a Renew request for local reasons unrelated to the
      specific request.
-    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Receiver</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnableToRenew</td></tr><tr><td><b>[Reason]</b></td><td>
-        <em>Text explaining the failure; e.g., "The event
-        source has too many subscribers".</em>
-       </td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="InvalidMessage" id="InvalidMessage"></a>6.8 InvalidMessage</h3><p>
+    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Receiver</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnableToRenew</td></tr><tr><td><b>[Reason]</b></td><td><em>Text explaining the failure; e.g., "The event
+        source has too many subscribers".</em></td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="InvalidMessage" id="InvalidMessage"/>6.8 InvalidMessage</h3><p>
      If a request message does not comply with the corresponding
      outline listed above, the request MUST fail and the event source
      or subscription manager MAY generate the following fault
      indicating that the request is invalid:
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:InvalidMessage</td></tr><tr><td><b>[Reason]</b></td><td>The message is not valid and cannot be processed.</td></tr><tr><td><b>[Detail]</b></td><td><em>The invalid message</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"></a>6.9 DeliveryFormatRequestUnavailable</h3><p>
+<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"/>6.9 DeliveryFormatRequestUnavailable</h3><p>
      This fault is sent when a Subscribe request specifies a delivery 
      mode that is not supported by the event source. Optionally, this 
      fault may contain a list of supported delivery mode URIs in the 
      Detail property.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:DeliveryFormatRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested delivery format is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
         &lt;wse:SupportedDeliveryFormat&gt; +
-        <br />
-        <em> Optional, one per delivery format supported by the receiver.</em>
-       </td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="Security" id="Security"></a>7 Security Considerations</h2><div class="div2">
-<h3><a name="MessageSecurity" id="MessageSecurity"></a>7.1 Message Security</h3><p>
+        <br/><em> Optional, one per delivery format supported by the receiver.</em></td></tr></tbody></table></div></div><div class="div1">
+<h2><a name="Security" id="Security"/>7 Security Considerations</h2><div class="div2">
+<h3><a name="MessageSecurity" id="MessageSecurity"/>7.1 Message Security</h3><p>
      It is strongly RECOMMENDED that the communication between
      services be secured using the mechanisms described in WS-Security
      <a href="#WSSecurity">[WS-Security]</a>. In order to properly
@@ -1407,7 +1377,7 @@
      included in the signature. Specifically, any headers identified
      in the <code>&lt;wse:NotifyTo&gt;</code> element and standard
      messaging headers, such as those from WS-Addressing 
-     <a href="#WSAddressing">[WS-Addressing]</a>, need to be signed with the
+     <a href="#AddrCore">[WS-Addressing]</a>, need to be signed with the
      body in order to "bind" the two together. For messages with empty
      bodies, the <code>&lt;s12:Body&gt;</code> element should be
      signed so content cannot be added in transit.
@@ -1472,7 +1442,7 @@
        sequencing, can also be used to prevent replay of application
        messages.
       </p></li></ul></div><div class="div2">
-<h3><a name="AccessControl" id="AccessControl"></a>7.2 Access Control</h3><p>
+<h3><a name="AccessControl" id="AccessControl"/>7.2 Access Control</h3><p>
      It is important for event sources to properly authorize
      requests. This is especially true for Subscribe requests, as
      otherwise the ability to subscribe on behalf of a third-party
@@ -1498,7 +1468,7 @@
      that are not reachable from the Internet have less need to
      control Subscribe requests.
     </p></div></div><div class="div1">
-<h2><a name="ImplConsideration" id="ImplConsideration"></a>8 Implementation Considerations</h2><p>
+<h2><a name="ImplConsideration" id="ImplConsideration"/>8 Implementation Considerations</h2><p>
     Implementations SHOULD generate expirations in subscribe and
     renew request and response messages that are significantly larger
     than expected network latency.
@@ -1509,7 +1479,7 @@
     notifications after receiving an unsubscribe response
     message.
    </p></div><div class="div1">
-<h2><a name="acks" id="acks"></a>9 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>9 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
       Ashok Malhotra (Oracle Corp.),
@@ -1531,88 +1501,72 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"></a>10 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"></a>RFC2119</dt><dd>
-      <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>10 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
        Key words for use in RFCs to Indicate Requirement Levels
       </cite></a>
       , S. Bradner, March 1997.
-      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>SOAP 1.1</dt><dd>
-      <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP 1.1</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
        Simple Object Access Protocol (SOAP) 1.1
       </cite></a>
       , D. Box, et al, May 2000.
-      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP121" id="SOAP121"></a>SOAP 1.2</dt><dd>
-      <a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
+      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP 1.2</dt><dd><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
        SOAP Version 1.2 Part 1: Messaging Framework
       </cite></a>
       , M. Gudgin, et al, June 2003.
-      (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="WSAddressing" id="WSAddressing"></a>WS-Addressing</dt><dd>
-      <a href="http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/"><cite>
-       Web Services Addressing (WS-Addressing)
+      (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/2005/08/addressing/"><cite>
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
       </cite></a>
-      , D. Box et al, August 2004.
-      (See http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/.)</dd><dt class="label"><a name="MEX" id="MEX"></a>WS-MetadataExchange</dt><dd>
-      <a href="http://www.w3.org/2009/02/ws-mex"><cite>
+      , May 2006.
+      (See http://www.w3.org/2005/08/addressing/.)</dd><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/2009/02/ws-mex"><cite>
        Web Services Metadata Exchange (WS-MetadataExchange)
       </cite></a>
       , K. Ballinger, et al, September 2004.
-      (See http://www.w3.org/2009/02/ws-mex.)</dd><dt class="label"><a name="WSPolicy" id="WSPolicy"></a>WS-Policy</dt><dd>
-      <a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
+      (See http://www.w3.org/2009/02/ws-mex.)</dd><dt class="label"><a name="WSPolicy" id="WSPolicy"/>WS-Policy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
        Web Services Policy Framework (WS-Policy)
       </cite></a>
       , S. Bajaj, et al, September 2004.
-      (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WSReliableMessaging" id="WSReliableMessaging"></a>WS-ReliableMessaging</dt><dd>
-      <a href="http://schemas.xmlsoap.org/ws/2005/02/rm"><cite>
+      (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WSReliableMessaging" id="WSReliableMessaging"/>WS-ReliableMessaging</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/02/rm"><cite>
        Web Services Reliable Messaging Protocol (WS-ReliableMessaging)
       </cite></a>
       , R. Bilorusets, et al, February 2005.
-      (See http://schemas.xmlsoap.org/ws/2005/02/rm.)</dd><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"></a>WS-SecureConversation</dt><dd>
-      <a href="http://schemas.xmlsoap.org/ws/2005/02/sc"><cite>
+      (See http://schemas.xmlsoap.org/ws/2005/02/rm.)</dd><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/02/sc"><cite>
        Web Services Secure Conversation Language (WS-SecureConversation)
       </cite></a>
       , S. Anderson, et al, February 2005.
-      (See http://schemas.xmlsoap.org/ws/2005/02/sc.)</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"></a>WS-Security</dt><dd>
-      <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
+      (See http://schemas.xmlsoap.org/ws/2005/02/sc.)</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"/>WS-Security</dt><dd><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
        Web Services Security: SOAP Message Security 1.0
       </cite></a>
       , A. Nadalin, et al, March 2004.
-      (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"></a>WS-SecurityPolicy</dt><dd>
-      <a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
+      (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"/>WS-SecurityPolicy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
        Web Services Security Policy Language (WS-SecurityPolicy), Version 1.1
       </cite></a>
       , G. Della-Libera, et al, July 2005.
-      (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="WSTrust" id="WSTrust"></a>WS-Trust</dt><dd>
-      <a href="http://schemas.xmlsoap.org/ws/2005/02/trust"><cite>
+      (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="WSTrust" id="WSTrust"/>WS-Trust</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/02/trust"><cite>
        Web Services Trust Language (WS-Trust)
       </cite></a>
       , S. Anderson, et al, February 2005.
-      (See http://schemas.xmlsoap.org/ws/2005/02/trust.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"></a>WSDL 1.1</dt><dd>
-      <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+      (See http://schemas.xmlsoap.org/ws/2005/02/trust.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL 1.1</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
        Web Services Description Language (WSDL) 1.1
       </cite></a>
       , E. Christensen, et al, March 2001.
-      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"></a>XML Infoset</dt><dd>
-      <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
+      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
        XML Information Set
       </cite></a>
       , J. Cowan, et al, February 2004.
-      (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"></a>XML Schema, Part 1</dt><dd>
-      <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
+      (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XML Schema, Part 1</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
        XML Schema Part 1: Structures
       </cite></a>
       , H. Thompson, et al, October 2004.
-      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"></a>XML Schema, Part 2</dt><dd>
-      <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
+      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XML Schema, Part 2</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
        XML Schema Part 2: Datatypes
       </cite></a>
       , P. Biron, et al, October 2004.
-      (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="XPath1" id="XPath1"></a>XPath 1.0</dt><dd>
-      <a href="http://www.w3.org/TR/1999/REC-xpath-19991116"><cite>
+      (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="XPath1" id="XPath1"/>XPath 1.0</dt><dd><a href="http://www.w3.org/TR/1999/REC-xpath-19991116"><cite>
        XML Path Language (XPath) Version 1.0
       </cite></a>
       , J. Clark, et al, November 1999.
       (See http://www.w3.org/TR/1999/REC-xpath-19991116.)</dd></dl></div></div><div class="back"><div class="div1">
-<h2><a name="Metadata" id="Metadata"></a>A Service Metadata for Eventing</h2><p>
+<h2><a name="Metadata" id="Metadata"/>A Service Metadata for Eventing</h2><p>
     In order to obtain the event-related metadata that describes a
     service, the mechanisms described in WS-MetadataExchange
     <a href="#MEX">[WS-MetadataExchange]</a> should be used. The
@@ -1711,7 +1665,7 @@
     Editor's Note: We anticipate that this WSDL extension
     may change in subsequent versions of this specification.
    </p></div><div class="div1">
-<h2><a name="Schema" id="Schema"></a>B XML Schema</h2><p>
+<h2><a name="Schema" id="Schema"/>B XML Schema</h2><p>
     A normative copy of the XML Schema <a href="#XMLSchema1">[XML Schema, Part 1]</a>,
     <a href="#XMLSchema2">[XML Schema, Part 2]</a> description for this specification may be
     retrieved from the following address:
@@ -1927,7 +1881,7 @@
  
   &lt;xs:attribute name="EventSource" type="xs:boolean" /&gt;
 &lt;/xs:schema&gt; </pre></div></div></div><div class="div1">
-<h2><a name="WSDL" id="WSDL"></a>C WSDL</h2><p>
+<h2><a name="WSDL" id="WSDL"/>C WSDL</h2><p>
     A normative copy of the WSDL <a href="#WSDL11">[WSDL 1.1]</a>
     description can be retrieved from the following address:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-evt/eventing.wsdl">http://www.w3.org/2009/02/ws-evt/eventing.wsdl</a></pre></div></div><p>
@@ -2035,32 +1989,19 @@
     &lt;/wsdl:operation&gt;
   &lt;/wsdl:portType&gt;
 &lt;/wsdl:definitions&gt;</pre></div></div></div><div class="div1">
-<h2><a name="changelog" id="changelog"></a>D Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a>
-      </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a>
-      </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6427">6427</a>
-      </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6459">6459</a>
-      </td></tr><tr><td> 2009/03/09 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6397">6397</a>
-      </td></tr><tr><td> 2009/03/09 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6426">6426</a>
-      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a>
-      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6498">6498</a>
-      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a>
-      </td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a>
-      </td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6400">6400</a>
-      </td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6400">6400</a>
-      </td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6428">6428</a>
-      </td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6687">6687</a>
-      </td></tr></tbody></table></div></div></body></html>
+<h2><a name="changelog" id="changelog"/>D Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6427">6427</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6459">6459</a></td></tr><tr><td> 2009/03/09 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6397">6397</a></td></tr><tr><td> 2009/03/09 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6426">6426</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6498">6498</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a></td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6400">6400</a></td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6400">6400</a></td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6428">6428</a></td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6687">6687</a></td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsrt.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -d -r1.26 -r1.27
--- wsrt.html	19 Mar 2009 14:14:23 -0000	1.26
+++ wsrt.html	23 Mar 2009 19:38:29 -0000	1.27
@@ -1,6 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Resource Transfer (WS-RT)</title><style type="text/css">
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Resource Transfer (WS-RT)</title><style type="text/css">
 code           { font-family: monospace; }
 
 div.constraint,
@@ -30,76 +28,71 @@
 div.exampleWrapper { margin: 4px }
 div.exampleHeader { font-weight: bold;
                     margin: 4px}
[...1003 lines suppressed...]
@@ -2162,12 +2130,9 @@
     &lt;/wsdl:operation&gt;
   &lt;/wsdl:portType&gt;
 &lt;/wsdl:definitions&gt;</pre></div></div></div><div class="div1">
-<h2><a name="changelog" id="changelog"></a>E Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6412">6412</a>
-      </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a>
-      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a>
-      </td></tr><tr><td> 2009/03/12 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6548">6548</a>
-      </td></tr></tbody></table></div></div></body></html>
+<h2><a name="changelog" id="changelog"/>E Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6412">6412</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/12 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6548">6548</a></td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- wst.html	19 Mar 2009 14:14:23 -0000	1.24
+++ wst.html	23 Mar 2009 19:38:29 -0000	1.25
@@ -1,6 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Transfer (WS-Transfer)</title><style type="text/css">
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Transfer (WS-Transfer)</title><style type="text/css">
 code           { font-family: monospace; }
 
 div.constraint,
@@ -30,45 +28,40 @@
 div.exampleWrapper { margin: 4px }
 div.exampleHeader { font-weight: bold;
                     margin: 4px}
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css" /></head><body><div class="head">
-<h1><a name="title" id="title"></a>Web Services Transfer (WS-Transfer)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd>
-    <a href="http://www.w3.org/TR/ws-transfer">http://www.w3.org/TR/ws-transfer
-   </a>
-  </dd><dt>Previous version:</dt><dd>
-    <a href="http://www.w3.org/TR/2009/WD-ws-transfer-20090317">http://www.w3.org/TR/2009/WD-ws-transfer-20090317
-    </a>
-  </dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr /><div>
-<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
+<h1><a name="title" id="title"/>Web Services Transfer (WS-Transfer)</h1>
+<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-transfer">http://www.w3.org/TR/ws-transfer
+   </a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-transfer-20090317">http://www.w3.org/TR/2009/WD-ws-transfer-20090317</a></dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consrtium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
     This specification describes a general SOAP-based protocol for accessing
     XML representations of Web service-based resources.
    </p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
+<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
         no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br />
-&nbsp;&nbsp;&nbsp;1.1 <a href="#reqs">Requirements</a><br />
-2 <a href="#Notations_and_Terminology">Terminology and Notation</a><br />
-&nbsp;&nbsp;&nbsp;2.1 <a href="#terminology">Terminology</a><br />
-&nbsp;&nbsp;&nbsp;2.2 <a href="#namespaces">XML Namespaces</a><br />
-&nbsp;&nbsp;&nbsp;2.3 <a href="#conven">Notational Conventions</a><br />
-&nbsp;&nbsp;&nbsp;2.4 <a href="#compliance">Compliance</a><br />
-3 <a href="#resourceOperations">Resource Operations</a><br />
-&nbsp;&nbsp;&nbsp;3.1 <a href="#Get">Get</a><br />
-&nbsp;&nbsp;&nbsp;3.2 <a href="#Put">Put</a><br />
-&nbsp;&nbsp;&nbsp;3.3 <a href="#Delete">Delete</a><br />
-4 <a href="#Resource_Factory_Operations">Resource Factory Operations</a><br />
-&nbsp;&nbsp;&nbsp;4.1 <a href="#Factory_Create">Create</a><br />
-5 <a href="#Faults">Faults</a><br />
-&nbsp;&nbsp;&nbsp;5.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br />
-6 <a href="#Security_Considerations">Security Considerations</a><br />
-7 <a href="#acks">Acknowledgements</a><br />
-8 <a href="#refs">References</a><br />
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br/>
+&nbsp;&nbsp;&nbsp;1.1 <a href="#reqs">Requirements</a><br/>
+2 <a href="#Notations_and_Terminology">Terminology and Notation</a><br/>
+&nbsp;&nbsp;&nbsp;2.1 <a href="#terminology">Terminology</a><br/>
+&nbsp;&nbsp;&nbsp;2.2 <a href="#namespaces">XML Namespaces</a><br/>
+&nbsp;&nbsp;&nbsp;2.3 <a href="#conven">Notational Conventions</a><br/>
+&nbsp;&nbsp;&nbsp;2.4 <a href="#compliance">Compliance</a><br/>
+3 <a href="#resourceOperations">Resource Operations</a><br/>
+&nbsp;&nbsp;&nbsp;3.1 <a href="#Get">Get</a><br/>
+&nbsp;&nbsp;&nbsp;3.2 <a href="#Put">Put</a><br/>
+&nbsp;&nbsp;&nbsp;3.3 <a href="#Delete">Delete</a><br/>
+4 <a href="#Resource_Factory_Operations">Resource Factory Operations</a><br/>
+&nbsp;&nbsp;&nbsp;4.1 <a href="#Factory_Create">Create</a><br/>
+5 <a href="#Faults">Faults</a><br/>
+&nbsp;&nbsp;&nbsp;5.1 <a href="#InvalidRepresentation">InvalidRepresentation</a><br/>
+6 <a href="#Security_Considerations">Security Considerations</a><br/>
+7 <a href="#acks">Acknowledgements</a><br/>
+8 <a href="#refs">References</a><br/>
 </p>
-<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br />
-B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br />
-C <a href="#ChangeLog">Change Log</a><br />
-</p></div><hr /><div class="body"><div class="div1">
-<h2><a name="intro" id="intro"></a>1 Introduction</h2><p>This specification defines a mechanism for acquiring XML-based
+<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
+B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
+C <a href="#ChangeLog">Change Log</a><br/>
+</p></div><hr/><div class="body"><div class="div1">
+<h2><a name="intro" id="intro"/>1 Introduction</h2><p>This specification defines a mechanism for acquiring XML-based
     representations of entities using the Web service infrastructure. It defines
     two types of entities:</p><ul><li><p>Resources, which are entities addressable by an endpoint reference that
         provide an XML representation</p></li><li><p>Resource factories, which are Web services that can create a new
@@ -106,51 +99,29 @@
     associated with the endpoint reference. When the Action URIs defined by
     this specification are used, such extension specifications must also allow
     the basic processing models defined herein.</p><div class="div2">
-<h3><a name="reqs" id="reqs"></a>1.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>Provide a SOAP-based protocol for managing resources and their
+<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>This specification intends to meet the following requirements:</p><ul><li><p>Provide a SOAP-based protocol for managing resources and their
         representations.
         </p></li><li><p>Minimize additional mechanism beyond the current Web Services
          architecture.
         </p></li></ul></div></div><div class="div1">
-<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"></a>2 Terminology and Notation</h2><div class="div2">
-<h3><a name="terminology" id="terminology"></a>2.1 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>A Web service that is addressable by an endpoint reference as defined
+<h2><a name="Notations_and_Terminology" id="Notations_and_Terminology"/>2 Terminology and Notation</h2><div class="div2">
+<h3><a name="terminology" id="terminology"/>2.1 Terminology</h3><dl><dt class="label">Resource</dt><dd><p>A Web service that is addressable by an endpoint reference as defined
          in WS-Addressing and that can be represented by an XML Infoset using
          the Get and Put operations defined in this specification.</p></dd><dt class="label">Resource factory</dt><dd><p>A Web service that is capable of creating new resources using the
          Create operation defined in this specification.</p></dd></dl></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"></a>2.2 XML Namespaces</h3><p>
+<h3><a name="namespaces" id="namespaces"/>2.2 XML Namespaces</h3><p>
      The XML Namespace URI that MUST be used by implementations of this
      specification is:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></pre></div></div><p>
-          <a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are 
+    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></pre></div></div><p><a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are 
      used in this specification. The
      choice of any namespace prefix is arbitrary and not semantically
      significant.
-    </p><a name="xmlnamespaces" id="xmlnamespaces"></a><table border="1" cellpadding="5"><caption>Table 2-1: 
+    </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1" cellpadding="5"><caption>Table 2-1: 
       Prefixes and XML Namespaces used in this specification.
-     </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wst </td><td>
-                <a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a>
-              </td><td>
+     </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wst </td><td><a href="http://www.w3.org/2009/02/ws-tra">http://www.w3.org/2009/02/ws-tra</a></td><td>
         This specification
-       </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td>
-                <a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a>
-              </td><td>
-                <a href="#Soap11">[SOAP 1.1]</a>
-              </td></tr><tr><td> s12 </td><td>
-                <a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a>
-              </td><td>
-                <a href="#Soap12">[SOAP 1.2]</a>
-              </td></tr><tr><td> wsa </td><td>
-                <a href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</a>
-              </td><td>
-                <a href="#WsAddressing">[WS-Addressing]</a>
-              </td></tr><tr><td> wsdl </td><td>
-                <a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a>
-              </td><td>
-                <a href="#Wsdl11">[WSDL 1.1]</a>
-              </td></tr><tr><td> xs </td><td>
-                <a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>
-              </td><td> 
-               XML Schema <a href="#XmlSchemaPart1">[XML Schema, Part 1]</a>, <a href="#XmlSchemaPart2">[XML Schema, Part 2]</a>
-              </td></tr></tbody></table><p>
+       </td></tr><tr><td> s </td><td> Either SOAP 1.1 or 1.2 </td><td> SOAP </td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">http://schemas.xmlsoap.org/soap/envelope/</a></td><td><a href="#Soap11">[SOAP 1.1]</a></td></tr><tr><td> s12 </td><td><a href="http://www.w3.org/2003/05/soap-envelope">http://www.w3.org/2003/05/soap-envelope</a></td><td><a href="#Soap12">[SOAP 1.2]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</a></td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl/">http://schemas.xmlsoap.org/wsdl/</a></td><td><a href="#Wsdl11">[WSDL 1.1]</a></td></tr><tr><td> xs </td><td><a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a></td><td> 
+               XML Schema <a href="#XmlSchemaPart1">[XML Schema, Part 1]</a>, <a href="#XmlSchemaPart2">[XML Schema, Part 2]</a></td></tr></tbody></table><p>
          The working group intends to update the value of the Web Services
          Enumeration namespace URI each time a new version of this document is
          published until such time that the document reaches Candidate
@@ -167,7 +138,7 @@
           http://www.w3.org/2005/07/13-nsuri
          </a>.
        </p></div><div class="div2">
-<h3><a name="conven" id="conven"></a>2.3 Notational Conventions</h3><p>
+<h3><a name="conven" id="conven"/>2.3 Notational Conventions</h3><p>
      The keywords "MUST", "MUST NOT",
      "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED",
@@ -203,8 +174,21 @@
       </p></li><li><p>
        XML namespace prefixes (see <a href="#xmlnamespaces">Table 2-1</a>) are used 
        to indicate the namespace of the element being defined.
-      </p></li></ul></div><div class="div2">
-<h3><a name="compliance" id="compliance"></a>2.4 Compliance</h3><p>An implementation is not compliant with this specification if it fails to
+      </p></li></ul><p>
+     In addition to Message Information Header properties
+     <a href="#AddrCore">[WS-Addressing]</a>,
+     this specification uses the following properties to define messages:
+    </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+     These properties bind to a SOAP Envelope as follows:
+    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope&gt;
+  &lt;s:Header&gt;
+    <b>[Headers]</b>
+    &lt;wsa:Action&gt;<b>[Action]</b>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt;
+&lt;/s:Envelope&gt;</pre></div></div></div><div class="div2">
+<h3><a name="compliance" id="compliance"/>2.4 Compliance</h3><p>An implementation is not compliant with this specification if it fails to
      satisfy one or more of the MUST or REQUIRED level requirements defined
      herein. A SOAP Node MUST NOT use the XML namespace identifier for this
      specification (listed in <a href="#xmlnamespaces">Table 2-1</a>) within
@@ -217,12 +201,12 @@
      request-response message exchange, the responses generated by the service
      server MUST use the same WS-Addressing namespace binding that was used in the
      request.</p></div></div><div class="div1">
-<h2><a name="resourceOperations" id="resourceOperations"></a>3 Resource Operations</h2><p>
+<h2><a name="resourceOperations" id="resourceOperations"/>3 Resource Operations</h2><p>
        All messages defined by this specification MUST be sent
        to a Web service that is addressable by an EPR
-       <a href="#WsAddressing">[WS-Addressing]</a>.
+       <a href="#AddrCore">[WS-Addressing]</a>.
       </p><div class="div2">
-<h3><a name="Get" id="Get"></a>3.1 Get</h3><p>This specification defines one Web service operation (Get) for fetching a
+<h3><a name="Get" id="Get"/>3.1 Get</h3><p>This specification defines one Web service operation (Get) for fetching a
 one-time snapshot of the representation of a resource.</p><p>The Get request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope ...&gt;  
   &lt;s:Header ...&gt;
     &lt;wsa:Action&gt;
@@ -238,16 +222,12 @@
     &lt;/wst:Get&gt;
   &lt;/s:Body&gt;
 &lt;/s:Envelope&gt;</pre></div></div><p>The following describes additional, normative constraints on the outline
-listed above:</p><dl><dt class="label">
-              <code>/s:Envelope/s:Header/wsa:Action</code>
-            </dt><dd><p>
+listed above:</p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
                This required element MUST contain the value
                <code>http://www.w3.org/2009/02/ws-tra/Get</code>. If a
                SOAP Action URI is also present in the underlying transport, 
                its value MUST convey the same value.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/s:Body/wst:Get</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/s:Body/wst:Get</code></dt><dd><p>
                This REQUIRED element MAY contain child elements that 
                can be used for extensibility purposes.
               </p></dd></dl><p>A Get request MUST be targeted at the resource whose representation is
@@ -283,16 +263,12 @@
 &lt;/s:Envelope&gt; </pre></div></div><p>
          The following describes additional, normative constraints on the 
          outline listed above:
-        </p><dl><dt class="label">
-              <code>/s:Envelope/s:Header/wsa:Action</code>
-            </dt><dd><p>
+        </p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
                This required element MUST contain the value
                http://www.w3.org/2009/02/ws-tra/GetResponse. If a SOAP
                Action URI is also present in the underlying transport, its 
                value MUST convey the same value.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/s:Body/wst:GetResponse</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/s:Body/wst:GetResponse</code></dt><dd><p>
                This REQUIRED element MUST contain at least one child
                element - the representation of the resource.  The 
                presence of subsequent child elements is service-specific and 
@@ -362,7 +338,7 @@
     &lt;xxx:state&gt;CA&lt;/xxx:state&gt;
     &lt;xxx:zip&gt;90266&lt;/xxx:zip&gt;
   &lt;/xxx:Customer&gt;</pre></div></div></div><div class="div2">
-<h3><a name="Put" id="Put"></a>3.2 Put</h3><p>This specification defines one Web service operation (Put) for updating a
+<h3><a name="Put" id="Put"/>3.2 Put</h3><p>This specification defines one Web service operation (Put) for updating a
 resource by providing a replacement representation. A resource MAY accept
 updates that provide different XML representations than that returned by the
 resource; in such a case, the semantics of the update operation is defined by
@@ -383,16 +359,12 @@
 &lt;/s:Envelope&gt;  </pre></div></div><p>
          The following describes additional, normative constraints on the 
          outline listed above:
-        </p><dl><dt class="label">
-              <code>/s:Envelope/s:Header/wsa:Action</code>
-            </dt><dd><p>
+        </p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
                This required element MUST contain the value
                http://www.w3.org/2009/02/ws-tra/Put. If a SOAP Action
                URI is also present in the underlying transport, its value 
                MUST convey the same value.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/s:Body/Put</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/s:Body/Put</code></dt><dd><p>
                This REQUIRED element MUST contain at least one child element -
                the representation to be used for the update.
                All other children SHOULD be ignored by the service.
@@ -436,16 +408,12 @@
       <em>xs:any ?</em>
     &lt;/wst:PutResponse&gt;
   &lt;/s:Body&gt;
-&lt;/s:Envelope&gt;  </pre></div></div><dl><dt class="label">
-              <code>/s:Envelope/s:Header/wsa:Action</code>
-            </dt><dd><p>
+&lt;/s:Envelope&gt;  </pre></div></div><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
                This required element MUST contain the value
                http://www.w3.org/2009/02/ws-tra/PutResponse. If a SOAP
                Action URI is also present in the underlying transport, 
                its value MUST convey the same value.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/s:Body/PutResponse</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/s:Body/PutResponse</code></dt><dd><p>
                This REQUIRED element MUST contain at least one child element
                (the current representation of the resource) if the updated
                representation differs from the representation sent in the
@@ -531,7 +499,7 @@
     &lt;wst:PutResponse/&gt;
   &lt;/s:Body/&gt;
 &lt;/s:Envelope&gt; </pre></div></div></div><div class="div2">
-<h3><a name="Delete" id="Delete"></a>3.3 Delete</h3><p>This specification defines one Web service operation (Delete) for deleting
+<h3><a name="Delete" id="Delete"/>3.3 Delete</h3><p>This specification defines one Web service operation (Delete) for deleting
 a resource in its entirety.</p><p>Extension specifications MAY define extensions to the Delete request,
 enabled by OPTIONAL header values, which specifically control preconditions
 for the Delete to succeed and which may control the nature or format of the
@@ -553,16 +521,12 @@
     &lt;/wst:Delete&gt;
   &lt;/s:Body&gt;
 &lt;/s:Envelope&gt;  </pre></div></div><p>The following describes additional, normative constraints on the outline
-listed above:</p><dl><dt class="label">
-              <code>/s:Envelope/s:Header/wsa:Action</code>
-            </dt><dd><p>
+listed above:</p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
                This required element MUST contain the value
                <code>http://www.w3.org/2009/02/ws-tra/Delete</code>. If
                a SOAP Action URI is also present in the underlying transport,
                its value MUST convey the same value.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/s:Body/wst:Delete</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/s:Body/wst:Delete</code></dt><dd><p>
                 This REQUIRED element MAY contain child elements that
                 can be used for extensibility purposes.
               </p></dd></dl><p>A Delete request MUST be targeted at the resource to be deleted as
@@ -586,16 +550,12 @@
       <em>xs:any ?</em>
     &lt;/wst:DeleteResponse&gt;
   &lt;/s:Body&gt;
-&lt;/s:Envelope&gt;  </pre></div></div><dl><dt class="label">
-              <code>/s:Envelope/s:Header/wsa:Action</code>
-            </dt><dd><p>
+&lt;/s:Envelope&gt;  </pre></div></div><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
                This required element MUST contain the value
                <code>http://www.w3.org/2009/02/ws-tra/DeleteResponse</code>.
                If a SOAP Action URI is also present in the underlying 
                transport, its value MUST convey the same value.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/s:Body/wst:DeleteResponse</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/s:Body/wst:DeleteResponse</code></dt><dd><p>
                This REQUIRED element MAY contain a child element that
                can be used for extensibility purposes.
               </p></dd></dl><p>
@@ -650,8 +610,8 @@
     &lt;/wst:DeleteResponse&gt;
   &lt;/s:Body&gt;
 &lt;/s:Envelope&gt; </pre></div></div></div></div><div class="div1">
-<h2><a name="Resource_Factory_Operations" id="Resource_Factory_Operations"></a>4 Resource Factory Operations</h2><div class="div2">
-<h3><a name="Factory_Create" id="Factory_Create"></a>4.1 Create</h3><p>This specification defines one Web service operation (Create) for creating
+<h2><a name="Resource_Factory_Operations" id="Resource_Factory_Operations"/>4 Resource Factory Operations</h2><div class="div2">
+<h3><a name="Factory_Create" id="Factory_Create"/>4.1 Create</h3><p>This specification defines one Web service operation (Create) for creating
     a resource and providing its initial representation. In some cases, the
     initial representation MAY constitute the representation of a logical
     constructor for the resource and may thus differ structurally from the
@@ -681,16 +641,12 @@
 &lt;/s:Envelope&gt; </pre></div></div><p>
          The following describes additional, normative constraints on the 
          outline listed above:
-        </p><dl><dt class="label">
-              <code>/s:Envelope/s:Header/wsa:Action</code>
-            </dt><dd><p>
+        </p><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
                This required element MUST contain the value
                <code>http://www.w3.org/2009/02/ws-tra/Create</code>. If
                a SOAP Action URI is also present in the underlying transport,
                its value MUST convey the same value.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/s:Body/Create</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/s:Body/Create</code></dt><dd><p>
                If this REQUIRED element contains children then the first child
                MUST be the literal resource representation, a representation 
                of the constructor for the resource, or other instructions for
@@ -728,16 +684,12 @@
       <em>xs:any ?</em>
     &lt;/wst:CreateResponse&gt;
   &lt;/s:Body&gt;
-&lt;/s:Envelope&gt;</pre></div></div><dl><dt class="label">
-              <code>/s:Envelope/s:Header/wsa:Action</code>
-            </dt><dd><p>
+&lt;/s:Envelope&gt;</pre></div></div><dl><dt class="label"><code>/s:Envelope/s:Header/wsa:Action</code></dt><dd><p>
                This required element MUST contain the value
                http://www.w3.org/2009/02/ws-tra/CreateResponse. If a
                SOAP Action URI is also present in the underlying transport, 
                its value MUST convey the same value.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/wst:CreateResponse</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/wst:CreateResponse</code></dt><dd><p>
                This REQUIRED element MUST contain, at a minimum,
                a resource reference (wst:ResourceCreated element)
                to the newly created resource.
@@ -783,9 +735,7 @@
                consider adding a corresponding SOAP header value in 
                the response to signal to the receiver that the
                extension is being used.
-              </p></dd><dt class="label">
-              <code>/s:Envelope/wst:CreateResponse/wst:ResourceCreated</code>
-            </dt><dd><p>
+              </p></dd><dt class="label"><code>/s:Envelope/wst:CreateResponse/wst:ResourceCreated</code></dt><dd><p>
                This required element MUST contain a resource reference for the
                newly created resource. This resource reference, represented 
                as an endpoint reference as defined in WS-Addressing, MUST 
@@ -852,14 +802,14 @@
     &lt;/wst:CreateResponse&gt;
   &lt;/s:Body&gt;
 &lt;/s:Envelope&gt;</pre></div></div></div></div><div class="div1">
-<h2><a name="Faults" id="Faults"></a>5 Faults</h2><p>All fault messages defined in this specification MUST be sent according to
+<h2><a name="Faults" id="Faults"/>5 Faults</h2><p>All fault messages defined in this specification MUST be sent according to
     the rules and usage described in  <a href="http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/">WS-Addressing 1.0 SOAP Binding</a>
     Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.
     The <b>[action]</b> property below SHOULD be used for faults 
     defined in this specification:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra/fault">http://www.w3.org/2009/02/ws-tra/fault</a></pre></div></div><div class="div2">
-<h3><a name="InvalidRepresentation" id="InvalidRepresentation"></a>5.1 InvalidRepresentation</h3><p>This fault is returned when an incorrect representation is sent in a
-    wst:Put or wst:Create message. </p><a name="Table2" id="Table2"></a><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidRepresentation</td></tr><tr><th align="left"><b>[Reason]</b></th><td>The supplied representation is invalid</td></tr><tr><th align="left"><b>[Detail]</b></th><td>none</td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="Security_Considerations" id="Security_Considerations"></a>6 Security Considerations</h2><p>It is strongly recommended that the communication between services be
+<h3><a name="InvalidRepresentation" id="InvalidRepresentation"/>5.1 InvalidRepresentation</h3><p>This fault is returned when an incorrect representation is sent in a
+    wst:Put or wst:Create message. </p><a name="Table2" id="Table2"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:InvalidRepresentation</td></tr><tr><th align="left"><b>[Reason]</b></th><td>The supplied representation is invalid</td></tr><tr><th align="left"><b>[Detail]</b></th><td>none</td></tr></tbody></table></div></div><div class="div1">
+<h2><a name="Security_Considerations" id="Security_Considerations"/>6 Security Considerations</h2><p>It is strongly recommended that the communication between services be
     secured using the mechanisms described in <a href="#WsSec">[WS-Security]</a>.</p><p>In order to properly secure messages, the body (even if empty) and all
     relevant headers need to be included in the signature. Specifically, the
     WS-Addressing header blocks, WS-Security timestamp, and any header blocks
@@ -875,50 +825,41 @@
     (e.g. embedded signatures and encryption) are also out-of-scope.</p><p>It is recommended that the security considerations of WS-Security also be
     considered.</p><p>While a comprehensive listing of attacks is not feasible, the following
     list summarizes common classes of attacks that apply to this protocol and
-    identifies the mechanism(s) to prevent/mitigate the attacks.</p><ul><li><p>
-            <em>Replay</em> -  Messages, or portions of messages, can be
+    identifies the mechanism(s) to prevent/mitigate the attacks.</p><ul><li><p><em>Replay</em> -  Messages, or portions of messages, can be
      replayed in an attempt to gain access or disrupt services. Freshness
      checks such as timestamps, digests, and sequences can be used to detect
      duplicate messages.
-    </p></li><li><p>
-            <em>Invalid tokens</em> - There are a number of token attacks
+    </p></li><li><p><em>Invalid tokens</em> - There are a number of token attacks
      including certificate authorities, false signatures, and PKI attacks.
      Care should be taken to ensure each token is valid (usage window, digest,
      signing authority, revocation, ...), and that the appropriate delegation
-      policies are in compliance.</p></li><li><p>
-            <em>Man-in-the-middle</em> - The message exchanges in this
+      policies are in compliance.</p></li><li><p><em>Man-in-the-middle</em> - The message exchanges in this
      specification could be subject to man-in-the-middle attacks so care
      should be taken to reduce possibilities here such as establishing a
      secure channel and verifying that the security tokens user represent
      identities authorized to speak for, or on behalf of, the desired resource
-     reference.</p></li><li><p>
-            <em>Message alteration</em> - Alteration is prevented by
+     reference.</p></li><li><p><em>Message alteration</em> - Alteration is prevented by
      including signatures of the message information using WS-Security. Care
      should be taken to review message part references to ensure they haven't
-     been forged (e.g. ID duplication).</p></li><li><p>
-            <em>Message disclosure</em> - Confidentiality is preserved by
-     encrypting sensitive data using WS-Security.</p></li><li><p>
-            <em>Key integrity</em> - Key integrity is maintained by using
+     been forged (e.g. ID duplication).</p></li><li><p><em>Message disclosure</em> - Confidentiality is preserved by
+     encrypting sensitive data using WS-Security.</p></li><li><p><em>Key integrity</em> - Key integrity is maintained by using
      the strongest algorithms possible (by comparing secured policies - see
       <a href="#WsPolicy">[WS-Policy]</a>
       and <a href="#WsSecPolicy">[WS-SecurityPolicy]</a>
       and by using derived keys (<a href="#WsSecConv">[WS-SecureConversation]</a>).
-    </p></li><li><p>
-            <em>Authentication</em> - Authentication is established using
+    </p></li><li><p><em>Authentication</em> - Authentication is established using
      the mechanisms described in WS-Security and WS-Trust. Each message is
-     authenticated using the mechanisms described in WS-Security.</p></li><li><p>
-            <em>Accountability</em> - Accountability is a function of the
+     authenticated using the mechanisms described in WS-Security.</p></li><li><p><em>Accountability</em> - Accountability is a function of the
      type of and string of the key and algorithms being used. In many cases, a
      strong symmetric key provides sufficient accountability. However, in some
-     environments, strong PKI signatures are required.</p></li><li><p>
-            <em>Availability</em> - All reliable messaging services are
+     environments, strong PKI signatures are required.</p></li><li><p><em>Availability</em> - All reliable messaging services are
      subject to a variety of availability attacks. Replay detection is a
      common attack and it is recommended that this be addressed by the
      mechanisms described in WS-Security. Other attacks, such as network-level
      denial of service attacks are harder to avoid and are outside the scope
      of this specification. That said, care should be taken to ensure that
      minimal state is saved prior to any authenticating sequences.</p></li></ul></div><div class="div1">
-<h2><a name="acks" id="acks"></a>7 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
       Ashok Malhotra (Oracle Corp.),
@@ -940,69 +881,58 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"></a>8 References</h2><dl><dt class="label"><a name="Rfc2119" id="Rfc2119"></a>RFC 2119</dt><dd>
-          <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>8 References</h2><dl><dt class="label"><a name="Rfc2119" id="Rfc2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
       Key words for use in RFCs to Indicate Requirement Levels
      </cite></a>
      , S. Bradner, Harvard University, March 1997.
-      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="Soap11" id="Soap11"></a>SOAP 1.1</dt><dd>
-          <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="Soap11" id="Soap11"/>SOAP 1.1</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
       Simple Object Access Protocol (SOAP) 1.1
      </cite></a>
      , D. Box, et al, May 2000.
-      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="Soap12" id="Soap12"></a>SOAP 1.2</dt><dd>
-          <a href="http://www.w3.org/TR/soap12-part1/"><cite>
+      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="Soap12" id="Soap12"/>SOAP 1.2</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
       SOAP Version 1.2 Part 1: Messaging Framework
      </cite></a>
      , M. Gudgin, et al, June 2003.
-      (See http://www.w3.org/TR/soap12-part1/.)</dd><dt class="label"><a name="WsAddressing" id="WsAddressing"></a>WS-Addressing</dt><dd>
-          <a href="http://www.w3.org/2005/08/addressing/"><cite>
-      W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
-     </cite></a>
-     , May 2006.
-      (See http://www.w3.org/2005/08/addressing/.)</dd><dt class="label"><a name="WsPolicy" id="WsPolicy"></a>WS-Policy</dt><dd>
-          <a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
+      (See http://www.w3.org/TR/soap12-part1/.)</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/2005/08/addressing/"><cite>
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+      </cite></a>
+      , May 2006.
+      (See http://www.w3.org/2005/08/addressing/.)</dd><dt class="label"><a name="WsPolicy" id="WsPolicy"/>WS-Policy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
       S. Bajaj, et al, "Web Services Policy Framework (WS-Policy)," 
      </cite></a>
      , September 2004.
-      (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WsSecConv" id="WsSecConv"></a>WS-SecureConversation</dt><dd>
+      (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WsSecConv" id="WsSecConv"/>WS-SecureConversation</dt><dd>
      href="http://schemas.xmlsoap.org/ws/2005/02/sc/"&gt;
      <cite>
       Web Services Secure Conversation Language (WS-SecureConversation)
      </cite>
      , S. Anderson, et al, February 2005.
-    </dd><dt class="label"><a name="WsSec" id="WsSec"></a>WS-Security</dt><dd>
-          <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
+    </dd><dt class="label"><a name="WsSec" id="WsSec"/>WS-Security</dt><dd><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
       Web Services Security: SOAP Message Security 1.0
      </cite></a>
      , OASIS standard.
-      (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WsSecPolicy" id="WsSecPolicy"></a>WS-SecurityPolicy</dt><dd>
-          <a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
+      (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WsSecPolicy" id="WsSecPolicy"/>WS-SecurityPolicy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
       G. Della-Libera, et al, "Web Services Security Policy Language (WS-SecurityPolicy), Version 1.1" 
      </cite></a>
      , July 2005.
-      (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="Wsdl11" id="Wsdl11"></a>WSDL 1.1</dt><dd>
-          <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+      (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="Wsdl11" id="Wsdl11"/>WSDL 1.1</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
       Web Services Description Language (WSDL) 1.1
      </cite></a>
      , E. Christensen, et al, March 2001.
-      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoSet" id="XMLInfoSet"></a>XML Infoset</dt><dd>
-          <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
+      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoSet" id="XMLInfoSet"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
       J. Cowan, et al, "XML Information Set"
      </cite></a>
      , February 2004.
-      (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XmlSchemaPart1" id="XmlSchemaPart1"></a>XML Schema, Part 1</dt><dd>
-          <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
+      (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XmlSchemaPart1" id="XmlSchemaPart1"/>XML Schema, Part 1</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
       XML Schema Part 1: Structures
      </cite></a>
      , H. Thompson, et al, October 2004.
-      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XmlSchemaPart2" id="XmlSchemaPart2"></a>XML Schema, Part 2</dt><dd>
-          <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
+      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XmlSchemaPart2" id="XmlSchemaPart2"/>XML Schema, Part 2</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
       XML Schema Part 2: Datatypes
      </cite></a>
      , James Clark, et al, November 1999.
       (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd></dl></div></div><div class="back"><div class="div1">
-<h2><a name="Appendix_I__E2_80_93_XSD" id="Appendix_I__E2_80_93_XSD"></a>A XML Schema</h2><p>
+<h2><a name="Appendix_I__E2_80_93_XSD" id="Appendix_I__E2_80_93_XSD"/>A XML Schema</h2><p>
         A normative copy of the XML Schema <a href="#XmlSchemaPart1">[XML Schema, Part 1]</a>,
         <a href="#XmlSchemaPart2">[XML Schema, Part 2]</a> description for this specification may be
         retrieved from the following address:
@@ -1101,7 +1031,7 @@
   &lt;/xs:element&gt;
  
 &lt;/xs:schema&gt;  </pre></div></div></div><div class="div1">
-<h2><a name="Appendix_II__E2_80_93_WSDL" id="Appendix_II__E2_80_93_WSDL"></a>B WSDL</h2><p>A normative copy of the WSDL <a href="#Wsdl11">[WSDL 1.1]</a> description
+<h2><a name="Appendix_II__E2_80_93_WSDL" id="Appendix_II__E2_80_93_WSDL"/>B WSDL</h2><p>A normative copy of the WSDL <a href="#Wsdl11">[WSDL 1.1]</a> description
     for this specification may be retrieved from the following address:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-tra/transfer.wsdl">http://www.w3.org/2009/02/ws-tra/transfer.wsdl</a></pre></div></div><p>A non-normative copy of the WSDL description is listed below for
     convenience.</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wsdl:definitions 
     targetNamespace="http://www.w3.org/2009/02/ws-tra" 
@@ -1195,16 +1125,11 @@
   &lt;/wsdl:portType&gt;
     
 &lt;/wsdl:definitions&gt;</pre></div></div></div><div class="div1">
-<h2><a name="ChangeLog" id="ChangeLog"></a>C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a>
-        </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6388">6388</a>
-        </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a>
-        </td></tr><tr><td> 2009/03/09 </td><td> DD </td><td> Added resolution of issue 
-         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6398">6398</a>
-        </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a>
-        </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a>
-        </td></tr></tbody></table></div></div></body></html>
+<h2><a name="ChangeLog" id="ChangeLog"/>C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6388">6388</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/09 </td><td> DD </td><td> Added resolution of issue 
+         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6398">6398</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue 
+         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- wsmex.xml	19 Mar 2009 14:11:55 -0000	1.20
+++ wsmex.xml	23 Mar 2009 19:38:29 -0000	1.21
@@ -616,93 +616,53 @@
     </ulist>
 
     <p>
-     
-    In addition to Message Information Header properties
-    
+     In addition to Message Information Header properties
      <bibref ref="AddrCore"/>, 
-    
-    this specification uses the following properties to define messages:
-    
+     this specification uses the following properties to define messages:
     </p>
     
-    
-    
     <glist>
-     
      <gitem>
-      
       <label> <kw>[Headers]</kw> </label>
-      
       <def>
-       
-       <p>Unordered message headers. </p>
-       
+       <p> Unordered message headers. </p>
       </def>
-      
      </gitem>
      
-     
-     
      <gitem>
-      
       <label> <kw>[Action]</kw> </label>
-      
       <def>
-       
        <p> The value to be used for the wsa:Action URI. </p>
-       
       </def>
-      
      </gitem>
      
-     
-     
      <gitem>
-      
       <label> <kw>[Body]</kw> </label>
-      
       <def>
-       
        <p> A message body. </p>
-       
       </def>
-      
      </gitem>
-     
     </glist>
     
-    
-    
     <p>
-     
      These properties bind to a SOAP Envelope as follows:
-     
     </p>
     
-    
-    
     <example>    
-   <eg>
-   &lt;s:Envelope&gt;
-     &lt;s:Header&gt;
-       <kw>[Headers]</kw>
-       &lt;wsa:Action&gt;<kw>[Action]</kw>&lt;/wsa:Action&gt;
-       ...
-     &lt;/s:Header&gt;
-     &lt;s:Body&gt;<kw>[Body]</kw>&lt;/s:Body&gt; 
-   &lt;/s:Envelope&gt;</eg>  
-     </example>
-    
-    
+     <eg>&lt;s:Envelope&gt;
+  &lt;s:Header&gt;
+    <kw>[Headers]</kw>
+    &lt;wsa:Action&gt;<kw>[Action]</kw>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<kw>[Body]</kw>&lt;/s:Body&gt; 
+&lt;/s:Envelope&gt;</eg>  
+    </example>
     
     <p>
-     
      This specification defines Fault properties for each defined
-     
      fault and defines SOAP bindings for each Fault property.
-     
     </p>
-    
    </div2>
    
  
@@ -1652,12 +1612,12 @@
      , M. Gudgin, et al, June 2003.
     </bibl>
 
-    <bibl id="AddrCore" key="WS-Addressing 1.0 Core"
-       href="http://www.w3.org/TR/2006/PR-ws-addr-core-20060321/">
-     <titleref>
-      Web Services Addressing 1.0 - Core" (Proposed Recommendation)
-     </titleref>
-     , M. Gudgin, M. Hadley, T. Rogers (editors), March 2006.
+    <bibl key="WS-Addressing" id="AddrCore"
+     href="http://www.w3.org/2005/08/addressing/">
+      <titleref>
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+      </titleref>
+      , May 2006.
     </bibl>
 
     <bibl id="WS-Policy" key="WS-Policy"
@@ -1955,6 +1915,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6404">6404</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/03/23 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -d -r1.26 -r1.27
--- wsenum.html	19 Mar 2009 14:14:22 -0000	1.26
+++ wsenum.html	23 Mar 2009 19:38:29 -0000	1.27
@@ -1,6 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Enumeration (WS-Enumeration)</title><style type="text/css">
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Enumeration (WS-Enumeration)</title><style type="text/css">
 code           { font-family: monospace; }
 
 div.constraint,
@@ -30,46 +28,41 @@
 div.exampleWrapper { margin: 4px }
 div.exampleHeader { font-weight: bold;
                     margin: 4px}
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css" /></head><body><div class="head">
-<h1><a name="title" id="title"></a>Web Services Enumeration (WS-Enumeration)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd>
-    <a href="http://www.w3.org/TR/ws-enumeration">http://www.w3.org/TR/ws-enumeration
-   </a>
-  </dd><dt>Previous version:</dt><dd>
-   <a href="http://www.w3.org/TR/2009/WD-ws-enumeration-20090317">http://www.w3.org/TR/2009/WD-ws-enumeration-20090317
-   </a>
-  </dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr /><div>
-<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
+<h1><a name="title" id="title"/>Web Services Enumeration (WS-Enumeration)</h1>
+<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-enumeration">http://www.w3.org/TR/ws-enumeration
+   </a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-enumeration-20090317">http://www.w3.org/TR/2009/WD-ws-enumeration-20090317</a></dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.or/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
     This specification describes a general
     SOAP-based protocol for enumerating a sequence of XML elements that
     is suitable for traversing logs, message queues, or other linear
     information models.
    </p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
+<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
         no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br />
-&nbsp;&nbsp;&nbsp;1.1 <a href="#reqs">Requirements</a><br />
-2 <a href="#termsNotes">Notations and Terminology</a><br />
-&nbsp;&nbsp;&nbsp;2.1 <a href="#conv">Notational Conventions</a><br />
-&nbsp;&nbsp;&nbsp;2.2 <a href="#namespaces">XML Namespaces</a><br />
-&nbsp;&nbsp;&nbsp;2.3 <a href="#terms">Terminology</a><br />
-&nbsp;&nbsp;&nbsp;2.4 <a href="#compliance">Compliance</a><br />
-3 <a href="#EnumMsgs">Enumeration Messages</a><br />
-&nbsp;&nbsp;&nbsp;3.1 <a href="#Enumerate">Enumerate</a><br />
-&nbsp;&nbsp;&nbsp;3.2 <a href="#Pull">Pull</a><br />
-&nbsp;&nbsp;&nbsp;3.3 <a href="#Renew">Renew</a><br />
-&nbsp;&nbsp;&nbsp;3.4 <a href="#GetStatus">GetStatus</a><br />
-&nbsp;&nbsp;&nbsp;3.5 <a href="#Release">Release</a><br />
-&nbsp;&nbsp;&nbsp;3.6 <a href="#EnumerationEnd">EnumerationEnd</a><br />
-4 <a href="#Security">Security Considerations</a><br />
-5 <a href="#acks">Acknowledgements</a><br />
-6 <a href="#refs">References</a><br />
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br/>
+&nbsp;&nbsp;&nbsp;1.1 <a href="#reqs">Requirements</a><br/>
+2 <a href="#termsNotes">Notations and Terminology</a><br/>
+&nbsp;&nbsp;&nbsp;2.1 <a href="#conv">Notational Conventions</a><br/>
+&nbsp;&nbsp;&nbsp;2.2 <a href="#namespaces">XML Namespaces</a><br/>
+&nbsp;&nbsp;&nbsp;2.3 <a href="#terms">Terminology</a><br/>
+&nbsp;&nbsp;&nbsp;2.4 <a href="#compliance">Compliance</a><br/>
+3 <a href="#EnumMsgs">Enumeration Messages</a><br/>
+&nbsp;&nbsp;&nbsp;3.1 <a href="#Enumerate">Enumerate</a><br/>
+&nbsp;&nbsp;&nbsp;3.2 <a href="#Pull">Pull</a><br/>
+&nbsp;&nbsp;&nbsp;3.3 <a href="#Renew">Renew</a><br/>
+&nbsp;&nbsp;&nbsp;3.4 <a href="#GetStatus">GetStatus</a><br/>
+&nbsp;&nbsp;&nbsp;3.5 <a href="#Release">Release</a><br/>
+&nbsp;&nbsp;&nbsp;3.6 <a href="#EnumerationEnd">EnumerationEnd</a><br/>
+4 <a href="#Security">Security Considerations</a><br/>
+5 <a href="#acks">Acknowledgements</a><br/>
+6 <a href="#refs">References</a><br/>
 </p>
-<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br />
-B <a href="#WSDL">WSDL</a><br />
-C <a href="#changelog">Change Log</a><br />
-</p></div><hr /><div class="body"><div class="div1">
-<h2><a name="intro" id="intro"></a>1 Introduction</h2><p>
+<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
+B <a href="#WSDL">WSDL</a><br/>
+C <a href="#changelog">Change Log</a><br/>
+</p></div><hr/><div class="body"><div class="div1">
+<h2><a name="intro" id="intro"/>1 Introduction</h2><p>
      There are numerous applications for which a
      simple single-request/single-reply metaphor is insufficient for
      transferring large data sets over SOAP. Applications that do not
@@ -128,7 +121,7 @@
      items that are returned in a Pull response are removed from the
      queue.
     </p><div class="div2">
-<h3><a name="reqs" id="reqs"></a>1.1 Requirements</h3><p>
+<h3><a name="reqs" id="reqs"/>1.1 Requirements</h3><p>
        This specification intends to meet the following requirements:
       </p><ul><li><p>
          Support enumeration of data sources
@@ -141,12 +134,12 @@
          Minimize additional mechanism
          beyond the current web service architecture.
         </p></li></ul></div></div><div class="div1">
-<h2><a name="termsNotes" id="termsNotes"></a>2 Notations and Terminology</h2><p>
+<h2><a name="termsNotes" id="termsNotes"/>2 Notations and Terminology</h2><p>
      This section specifies the notations,
      namespaces, and terminology used in this
      specification.
     </p><div class="div2">
-<h3><a name="conv" id="conv"></a>2.1 Notational Conventions</h3><p>
+<h3><a name="conv" id="conv"/>2.1 Notational Conventions</h3><p>
       The keywords "MUST", "MUST NOT", "REQUIRED",
       "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
       and "OPTIONAL" in this document are to be interpreted as described
@@ -187,47 +180,44 @@
         XML namespace prefixes (see <a href="#xmlnamespaces">Table 2-1</a>) are used 
         to indicate the namespace of the element being
         defined.
-       </p></li></ul></div><div class="div2">
-<h3><a name="namespaces" id="namespaces"></a>2.2 XML Namespaces</h3><p>
+       </p></li></ul><p>
+      In addition to Message Information Header properties
+      <a href="#AddrCore">[WS-Addressing]</a>,
+      this specification uses the following properties to define messages:
+     </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
+      These properties bind to a SOAP Envelope as follows:
+     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope&gt;
+  &lt;s:Header&gt;
+    <b>[Headers]</b>
+    &lt;wsa:Action&gt;<b>[Action]</b>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt;
+&lt;/s:Envelope&gt;</pre></div></div></div><div class="div2">
+<h3><a name="namespaces" id="namespaces"/>2.2 XML Namespaces</h3><p>
        The XML namespace URI that MUST be used by
        implementations of this specification is: 
-      </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-enu">http://www.w3.org/2009/02/ws-enu</a></pre></div></div><p>
-       <a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are used in
+      </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-enu">http://www.w3.org/2009/02/ws-enu</a></pre></div></div><p><a href="#xmlnamespaces">Table 2-1</a> lists XML namespaces that are used in
        this specification. The choice of any namespace prefix is arbitrary
        and not semantically significant.
-      </p><a name="xmlnamespaces" id="xmlnamespaces"></a><table border="1"><caption>Table 2-1: 
+      </p><a name="xmlnamespaces" id="xmlnamespaces"/><table border="1"><caption>Table 2-1: 
         Prefixes and XML namespaces used in this specification
-       </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wsen </td><td>
-          <a href="http://www.w3.org/2009/02/ws-enu">
+       </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </th><th align="left"> Specification(s) </th></tr><tr><td> wsen </td><td><a href="http://www.w3.org/2009/02/ws-enu">
            http://www.w3.org/2009/02/ws-enu
-          </a>
-         </td><td> This specification </td></tr><tr><td> s </td><td>
-          <a href="http://www.w3.org/2003/05/soap-envelope">
+          </a></td><td> This specification </td></tr><tr><td> s </td><td><a href="http://www.w3.org/2003/05/soap-envelope">
            http://www.w3.org/2003/05/soap-envelope
-          </a>
-         </td><td> SOAP 1.2 <a href="#SOAP121">[SOAP12]</a> </td></tr><tr><td> s11 </td><td>
-          <a href="http://schemas.xmlsoap.org/soap/envelope/">
+          </a></td><td> SOAP 1.2 <a href="#SOAP121">[SOAP12]</a></td></tr><tr><td> s11 </td><td><a href="http://schemas.xmlsoap.org/soap/envelope/">
            http://schemas.xmlsoap.org/soap/envelope/
-          </a>
-         </td><td> SOAP 1.1 <a href="#SOAP11">[SOAP11]</a> </td></tr><tr><td> wsa </td><td>
-          <a href="http://www.w3.org/2005/08/addressing">
+          </a></td><td> SOAP 1.1 <a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> wsa </td><td><a href="http://www.w3.org/2005/08/addressing">
            http://www.w3.org/2005/08/addressing
-          </a>
-         </td><td> WS-Addressing <a href="#WSAddressing">[WS-Addressing]</a> </td></tr><tr><td> wsam </td><td>
-          <a href="http://www.w3.org/2007/05/addressing/metadata">
+          </a></td><td> WS-Addressing <a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsam </td><td><a href="http://www.w3.org/2007/05/addressing/metadata">
            http://www.w3.org/2007/05/addressing/metadata
-          </a>
-         </td><td> WS-Addressing <a href="#WSAddressing">[WS-Addressing]</a> </td></tr><tr><td> xs </td><td>
-          <a href="http://www.w3.org/2001/XMLSchema">
+          </a></td><td> WS-Addressing <a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> xs </td><td><a href="http://www.w3.org/2001/XMLSchema">
            http://www.w3.org/2001/XMLSchema
-          </a>
-         </td><td> 
-          XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a>
-         </td></tr><tr><td> wsdl </td><td>
-          <a href="http://schemas.xmlsoap.org/wsdl">
+          </a></td><td> 
+          XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr><tr><td> wsdl </td><td><a href="http://schemas.xmlsoap.org/wsdl">
            http://schemas.xmlsoap.org/wsdl
-          </a>
-         </td><td> WSDL/1.1 <a href="#WSDL11">[WSDL11]</a> </td></tr></tbody></table><p>
+          </a></td><td> WSDL/1.1 <a href="#WSDL11">[WSDL11]</a></td></tr></tbody></table><p>
        The working group intends to update the value of the Web Services
        Enumeration namespace URI each time a new version of this document is
        published until such time that the document reaches Candidate
@@ -244,7 +234,7 @@
         http://www.w3.org/2005/07/13-nsuri
        </a>.
       </p></div><div class="div2">
-<h3><a name="terms" id="terms"></a>2.3 Terminology</h3><dl><dt class="label"> Consumer </dt><dd><p>
+<h3><a name="terms" id="terms"/>2.3 Terminology</h3><dl><dt class="label"> Consumer </dt><dd><p>
          The Web service that is requesting the data
          enumeration from the data source
         </p></dd><dt class="label"> Data source </dt><dd><p>
@@ -257,7 +247,7 @@
          items using the Pull operation defined in this
          specification
         </p></dd></dl></div><div class="div2">
-<h3><a name="compliance" id="compliance"></a>2.4 Compliance</h3><p>
+<h3><a name="compliance" id="compliance"/>2.4 Compliance</h3><p>
       An implementation is not compliant with this
       specification if it fails to satisfy one or more of the MUST or
       REQUIRED level requirements defined herein. A SOAP Node MUST NOT
@@ -269,7 +259,7 @@
       precedence over normative outlines, which in turn takes precedence
       over the XML Schema and WSDL descriptions.
      </p></div></div><div class="div1">
-<h2><a name="EnumMsgs" id="EnumMsgs"></a>3 Enumeration Messages</h2><p>
+<h2><a name="EnumMsgs" id="EnumMsgs"/>3 Enumeration Messages</h2><p>
     Enumeration contexts represent a specific
     traversal through a sequence of XML information items. An Enumerate
     operation may be used to establish an enumeration context from a
@@ -314,9 +304,9 @@
    </p><p>
     All messages defined by this specification MUST be sent
     to a Web service that is addressable by an EPR 
-    <a href="#WSAddressing">[WS-Addressing]</a>.
+    <a href="#AddrCore">[WS-Addressing]</a>.
    </p><div class="div2">
-<h3><a name="Enumerate" id="Enumerate"></a>3.1 Enumerate</h3><p>
+<h3><a name="Enumerate" id="Enumerate"/>3.1 Enumerate</h3><p>
      All data sources MUST support some operation
      that allows an enumeration to be started. A data source MAY support
      the Enumerate operation, or it may provide some other mechanism for
@@ -481,7 +471,7 @@
           s12:Code/s12:Subcode/s12:Value = wsen:CannotProcessFilter
          </p></li><li><p>
           s12:Reason/s12:Text = e.g., "cannot filter as requested"
-         </p></li></ul></dd><dt class="label"><a name="Dialect" id="Dialect"></a> /s:Envelope/s:Body/*/wsen:Filter/@Dialect </dt><dd><p>
+         </p></li></ul></dd><dt class="label"><a name="Dialect" id="Dialect"/> /s:Envelope/s:Body/*/wsen:Filter/@Dialect </dt><dd><p>
         Implied value is
         "http://www.w3.org/TR/1999/REC-xpath-19991116". 
        </p><p>
@@ -561,10 +551,9 @@
         consumer is required to pass this XML data in Pull requests for
         this enumeration context, until and unless a PullResponse message
         updates the enumeration context.
-       </p></dd></dl><p>
-     <a href="#enumReq">Example 3-1</a> lists a sample Enumerate request.
+       </p></dd></dl><p><a href="#enumReq">Example 3-1</a> lists a sample Enumerate request.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="enumReq" id="enumReq"></a>Example 3-1: Enumerate request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="enumReq" id="enumReq"/>Example 3-1: Enumerate request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
 (02)    xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (03)    xmlns:wsen="http://www.w3.org/2009/02/ws-enu"&gt;
 (04)   &lt;s:Header&gt;
@@ -596,11 +585,10 @@
      period. No wsen:Filter element is present, so the resultant
      enumeration context is expected to return all available
      elements.
-    </p><p>
-     <a href="#enumRes">Example 3-2</a> lists a response to the request in 
+    </p><p><a href="#enumRes">Example 3-2</a> lists a response to the request in 
      <a href="#enumReq">Example 3-1</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="enumRes" id="enumRes"></a>Example 3-2: Response to Enumerate request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S='http://www.w3.org/2003/05/soap-envelope'
+<div class="exampleHeader"><a name="enumRes" id="enumRes"/>Example 3-2: Response to Enumerate request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S='http://www.w3.org/2003/05/soap-envelope'
 (02)     xmlns:wsen='http://www.w3.org/2009/02/ws-enu'
 (03)     xmlns:wsa='http://www.w3.org/2005/08/addressing'
 (04) &gt;
@@ -631,7 +619,7 @@
      enumeration context that supports the Pull operation defined
      below.
     </p></div><div class="div2">
-<h3><a name="Pull" id="Pull"></a>3.2 Pull</h3><p>
+<h3><a name="Pull" id="Pull"/>3.2 Pull</h3><p>
      The Pull operation is initiated by sending a
      Pull request message to the data source. The Pull request message
      MUST be of the following form:
@@ -678,16 +666,14 @@
          </p></li><li><p>
           faultstring = <em>text explaining why the enumeration context is 
           no longer valid, or</em> "Invalid enumeration context" 
-          <em>if no additional information is available</em>
-         </p></li></ul><p>SOAP 1.2:</p><ul><li><p>
+          <em>if no additional information is available</em></p></li></ul><p>SOAP 1.2:</p><ul><li><p>
           s:Code/s:Value = s:Receiver
          </p></li><li><p>
           s:Code/s:Subcode/s:Value = wsen:InvalidEnumerationContext
          </p></li><li><p>
           s:Reason/s:Text = <em>text explaining why the enumeration context 
           is no longer valid, or</em> "Invalid enumeration context" 
-          <em>if no additional information is available</em>
-         </p></li></ul><p>
+          <em>if no additional information is available</em></p></li></ul><p>
         Note that the data source may not be able to
         determine that an enumeration context is not valid, especially if
         all of the state associated with the enumeration is kept in the
@@ -809,8 +795,7 @@
         enumeration context. The consumer is required to replace the prior
         representation with the contents of this element.
        </p></dd><dt class="label"> 
-       /s:Envelope/s:Body/wsen:PullResponse/wsen:Items/<em>any</em>
-      </dt><dd><p>
+       /s:Envelope/s:Body/wsen:PullResponse/wsen:Items/<em>any</em></dt><dd><p>
         The optional Items element contains one or
         more enumeration-specific elements, one for each element being
         returned. 
@@ -828,10 +813,9 @@
      wsen:EnumerationContext and wsen:EndOfSequence MUST NOT both
      appear; neither may appear, or one without the other, but not both
      in the same PullResponse.
-    </p><p>
-     <a href="#pullReq">Example 3-3</a> lists a Pull request.
+    </p><p><a href="#pullReq">Example 3-3</a> lists a Pull request.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="pullReq" id="pullReq"></a>Example 3-3: Pull request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="pullReq" id="pullReq"/>Example 3-3: Pull request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
 (02)    xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (03)    xmlns:wsen="http://www.w3.org/2009/02/ws-enu"&gt;
 (04)   &lt;s:Header&gt;
@@ -863,11 +847,10 @@
      of the Pull request message. Line (22) indicates that no more than
      10 elements should be returned in the body of the Pull response
      message.
-    </p><p>
-     <a href="#pullRes">Example 3-4</a> lists a response to the request in 
+    </p><p><a href="#pullRes">Example 3-4</a> lists a response to the request in 
      <a href="#pullReq">Example 3-3</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="pullRes" id="pullRes"></a>Example 3-4: Response to Pull request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="pullRes" id="pullRes"/>Example 3-4: Response to Pull request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
 (02)     xmlns:wsen="http://www.w3.org/2009/02/ws-enu"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04) &gt;
@@ -914,7 +897,7 @@
      wsen:InvalidEnumerationContext fault, as described above, or MAY
      take some other action.
     </p></div><div class="div2">
-<h3><a name="Renew" id="Renew"></a>3.3 Renew</h3><p>
+<h3><a name="Renew" id="Renew"/>3.3 Renew</h3><p>
      Data sources MUST support requests to renew
      enumerations.
     </p><p>
@@ -959,16 +942,14 @@
          </p></li><li><p>
           faultstring = <em>text explaining why the enumeration context is 
           no longer valid, or</em> "Invalid enumeration context" 
-          <em>if no additional information is available</em>
-         </p></li></ul><p>SOAP 1.2:</p><ul><li><p>
+          <em>if no additional information is available</em></p></li></ul><p>SOAP 1.2:</p><ul><li><p>
           s:Code/s:Value = s:Receiver
          </p></li><li><p>
           s:Code/s:Subcode/s:Value = wsen:InvalidEnumerationContext
          </p></li><li><p>
           s:Reason/s:Text = <em>text explaining why the enumeration 
           context is no longer valid, or</em> "Invalid enumeration 
-          context" <em>if no additional information is available</em>
-         </p></li></ul><p>
+          context" <em>if no additional information is available</em></p></li></ul><p>
         Note that the data source may not be able to
         determine that an enumeration context is not valid, especially if
         all of the state associated with the enumeration is kept in the
@@ -1021,8 +1002,7 @@
       </p></li><li><p>
        faultstring = <em>text explaining why the enumeration context cannot 
        be renewed, or</em> "data source unable to renew" <em>if no 
-       additional information is available</em>
-      </p></li></ul><p>
+       additional information is available</em></p></li></ul><p>
      The SOAP 1.2 binding of this type of fault is:
     </p><ul><li><p>
        s12:Code/s12:Value = s12:Receiver
@@ -1031,12 +1011,11 @@
       </p></li><li><p>
        s12:Reason/s12:Text = <em>text explaining why the enumeration 
        context cannot be renewed, or</em> "data source unable to 
-       renew" <em>if no additional information is available</em>
-      </p></li></ul><p>
+       renew" <em>if no additional information is available</em></p></li></ul><p>
      Other components of the outline above are not
      further constrained by this specification.
     </p></div><div class="div2">
-<h3><a name="GetStatus" id="GetStatus"></a>3.4 GetStatus</h3><p>
+<h3><a name="GetStatus" id="GetStatus"/>3.4 GetStatus</h3><p>
      To get the status of an enumeration, the
      subscriber sends a request of the following form to the data
      source:
@@ -1087,7 +1066,7 @@
      (see <a href="#Renew"><b>3.3 Renew</b></a>). Other components of the outline above are 
      not further constrained by this specification.
     </p></div><div class="div2">
-<h3><a name="Release" id="Release"></a>3.5 Release</h3><p>
+<h3><a name="Release" id="Release"/>3.5 Release</h3><p>
      The Release operation is initiated by sending a
      Release request message to the data source. The Release request
      message MUST be of the following form:
@@ -1146,10 +1125,9 @@
         http://www.w3.org/2009/02/ws-enu/ReleaseResponse.
         If a SOAP Action URI is also present in the underlying transport,
         its value MUST convey the same value.
-       </p></dd></dl><p>
-     <a href="#releaseReq">Example 3-5</a> lists a Release request.
+       </p></dd></dl><p><a href="#releaseReq">Example 3-5</a> lists a Release request.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="releaseReq" id="releaseReq"></a>Example 3-5: Release request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="releaseReq" id="releaseReq"/>Example 3-5: Release request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
 (02)    xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (03)    xmlns:wsen="http://www.w3.org/2009/02/ws-enu"&gt;
 (04)   &lt;s:Header&gt;
@@ -1176,11 +1154,10 @@
      is a Release request and that the data source is expected to
      respond with a Release response message. Line (20) identifies the
      enumeration context to be released.
-    </p><p>
-     <a href="#releaseRes">Example 3-6</a> lists a response to the request in 
+    </p><p><a href="#releaseRes">Example 3-6</a> lists a response to the request in 
      <a href="#releaseReq">Example 3-5</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="releaseRes" id="releaseRes"></a>Example 3-6: Response to Release request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
+<div class="exampleHeader"><a name="releaseRes" id="releaseRes"/>Example 3-6: Response to Release request</div><div class="exampleInner"><pre>(01) &lt;s:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
 (02)     xmlns:wsen="http://www.w3.org/2009/02/ws-enu"
 (03)     xmlns:wsa="http://www.w3.org/2005/08/addressing"
 (04) &gt;
@@ -1200,7 +1177,7 @@
      Lines (06-08) in <a href="#releaseRes">Example 3-6</a> indicate this message
      is a Release response message.
     </p></div><div class="div2">
-<h3><a name="EnumerationEnd" id="EnumerationEnd"></a>3.6 EnumerationEnd</h3><p>
+<h3><a name="EnumerationEnd" id="EnumerationEnd"/>3.6 EnumerationEnd</h3><p>
      If the data source terminates an enumeration
      unexpectedly, the data source SHOULD send an EnumerationEnd SOAP
      message to the endpoint reference indicated when the enumeration
@@ -1260,7 +1237,7 @@
      Other components of the outline above are not
      further constrained by this specification.
     </p></div></div><div class="div1">
-<h2><a name="Security" id="Security"></a>4 Security Considerations</h2><p>
+<h2><a name="Security" id="Security"/>4 Security Considerations</h2><p>
     It is strongly recommended that the
     communication between services be secured using the mechanisms
     described in <a href="#WSSecurity">[WS-Security]</a>. 
@@ -1297,60 +1274,51 @@
     feasible, the following list summarizes common classes of attacks
     that apply to this protocol and identifies the mechanism(s) to
     prevent/mitigate the attacks. 
-   </p><ul><li><p>
-      <em>Replay</em>
+   </p><ul><li><p><em>Replay</em>
       - Messages, or portions
       of messages, can be replayed in an attempt to gain access or
       disrupt services. Freshness checks such as timestamps,
       digests, and sequences can be used to detect duplicate
       messages.
-     </p></li><li><p>
-      <em>Invalid tokens</em> 
+     </p></li><li><p><em>Invalid tokens</em> 
       - There are a number of token attacks including certificate 
       authorities, false signatures, and PKI attacks. Care should be taken
       to ensure each token is valid (usage window, digest, signing
       authority, revocation, ...), and that the appropriate delegation
       policies are in compliance.
-     </p></li><li><p>
-      <em>Man-in-the-middle</em>
+     </p></li><li><p><em>Man-in-the-middle</em>
       - The message exchanges in this
       specification could be subject to man-in-the-middle attacks so care
       should be taken to reduce possibilities here such as establishing a
       secure channel and verifying that the security tokens user
       represent identities authorized to speak for, or on behalf of, the
       desired resource reference.
-     </p></li><li><p>
-      <em>Message alteration</em> 
+     </p></li><li><p><em>Message alteration</em> 
       - Alteration is prevented by
       including signatures of the message information using WS-Security.
       Care should be taken to review message part references
       to ensure they haven't been forged (e.g. ID duplication).
-     </p></li><li><p>
-      <em>Message disclosure</em> 
+     </p></li><li><p><em>Message disclosure</em> 
       - Confidentiality is preserved
       by encrypting sensitive data using WS-Security.
-     </p></li><li><p>
-      <em>Key integrity</em> 
+     </p></li><li><p><em>Key integrity</em> 
       - Key integrity is maintained
       by using the strongest algorithms possible (by comparing secured
       policies - see <a href="#wspolicy">[WS-Policy]</a> and
       <a href="#WSSecurityPolicy">[WS-SecurityPolicy]</a>) and by using derived
       keys (<a href="#WSSecureConversation">[WS-SecureConversation]</a>).
-     </p></li><li><p>
-      <em>Authentication</em> 
+     </p></li><li><p><em>Authentication</em> 
       - Authentication is
       established using the mechanisms described in WS-Security and
       WS-Trust. Each message is authenticated using the
       mechanisms described in WS-Security.
-     </p></li><li><p>
-      <em>Accountability</em> 
+     </p></li><li><p><em>Accountability</em> 
       - Accountability is
       a function of the type of and string of the key and algorithms
       being used. In many cases, a strong symmetric key
       provides sufficient accountability. However, in some
       environments, strong PKI signatures are required.
-     </p></li><li><p>
-      <em>Availability</em> 
+     </p></li><li><p><em>Availability</em> 
       - All reliable
       messaging services are subject to a variety of availability
       attacks. Replay detection is a common attack and it is
@@ -1361,7 +1329,7 @@
       taken to ensure that minimal state is saved prior to any
       authenticating sequences.
      </p></li></ul></div><div class="div1">
-<h2><a name="acks" id="acks"></a>5 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>5 Acknowledgements</h2><p>
     This specification has been developed as a
     result of joint work with many individuals and teams,
     including: 
@@ -1384,73 +1352,60 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"></a>6 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"></a>RFC2119</dt><dd>
-      <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>6 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
        Key words for use in RFCs to Indicate Requirement Levels
       </cite></a>
       , S. Bradner, March 1997.
-      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>SOAP11</dt><dd>
-      <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
        Simple Object Access Protocol (SOAP) 1.1
       </cite></a>
       , D. Box, et al, May 2000.
-      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP121" id="SOAP121"></a>SOAP12</dt><dd>
-      <a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
+      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP121" id="SOAP121"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
        SOAP Version 1.2 Part 1: Messaging Framework
       </cite></a>
       , M. Gudgin, et al, June 2003.
-      (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="WSAddressing" id="WSAddressing"></a>WS-Addressing</dt><dd>
-      <a href="http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/"><cite>
-       Web Services Addressing (WS-Addressing)
+      (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/2005/08/addressing/"><cite>
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
       </cite></a>
-      ,D. Box, et al, August 2004.
-      (See http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/.)</dd><dt class="label"><a name="wspolicy" id="wspolicy"></a>WS-Policy</dt><dd>
-      <a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
+      , May 2006.
+      (See http://www.w3.org/2005/08/addressing/.)</dd><dt class="label"><a name="wspolicy" id="wspolicy"/>WS-Policy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2004/09/policy"><cite>
        Web Services Policy Framework (WS-Policy)
       </cite></a>
       , S. Bajaj, et al, September 2004.
-      (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"></a>WS-SecureConversation</dt><dd>
-      <a href="http://schemas.xmlsoap.org/ws/2005/02/sc"><cite>
+      (See http://schemas.xmlsoap.org/ws/2004/09/policy.)</dd><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/02/sc"><cite>
        Web Services Secure Conversation Language (WS-SecureConversation)
       </cite></a>
       , S. Anderson, et al, February 2005.
-      (See http://schemas.xmlsoap.org/ws/2005/02/sc.)</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"></a>WS-Security</dt><dd>
-      <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
+      (See http://schemas.xmlsoap.org/ws/2005/02/sc.)</dd><dt class="label"><a name="WSSecurity" id="WSSecurity"/>WS-Security</dt><dd><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
        Web Services Security: SOAP Message Security 1.0
       </cite></a>
       , A. Nadalin, et al, March 2004.
-      (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"></a>WS-SecurityPolicy</dt><dd>
-      <a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
+      (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WSSecurityPolicy" id="WSSecurityPolicy"/>WS-SecurityPolicy</dt><dd><a href="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy"><cite>
        Web Services Security Policy Language (WS-SecurityPolicy), , Version 1.1
       </cite></a>
       , G. Della-Libera, et al, July 2005.
-      (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"></a>WSDL11</dt><dd>
-      <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+      (See http://schemas.xmlsoap.org/ws/2005/07/securitypolicy.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
        Web Services Description Language (WSDL) 1.1
       </cite></a>
       , E. Christensen, et al, March 2001.
-      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"></a>XML Infoset</dt><dd>
-      <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
+      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"/>XML Infoset</dt><dd><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/"><cite>
        XML Information Set
       </cite></a>
       , J. Cowan, et al, February 2004.
-      (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"></a>XMLSchema - Part 1</dt><dd>
-      <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
+      (See http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.)</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XMLSchema - Part 1</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
        XML Schema Part 1: Structures
       </cite></a>
       , H. Thompson, et al, October 2004.
-      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"></a>XMLSchema - Part 2</dt><dd>
-      <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
+      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XMLSchema - Part 2</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
        XML Schema Part 2: Datatypes
       </cite></a>
       , P. Biron, et al, October 2004.
-      (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="XPath1" id="XPath1"></a>XPath1.0</dt><dd>
-      <a href="http://www.w3.org/TR/1999/REC-xpath-19991116"><cite>
+      (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd><dt class="label"><a name="XPath1" id="XPath1"/>XPath1.0</dt><dd><a href="http://www.w3.org/TR/1999/REC-xpath-19991116"><cite>
        XML Path Language (XPath) Version 1.0
       </cite></a>
       , J. Clark, et al, November 1999.
       (See http://www.w3.org/TR/1999/REC-xpath-19991116.)</dd></dl></div></div><div class="back"><div class="div1">
-<h2><a name="schema" id="schema"></a>A XML Schema</h2><p>
+<h2><a name="schema" id="schema"/>A XML Schema</h2><p>
     A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
     <a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification may be
     retrieved from the following address:
@@ -1695,7 +1650,7 @@
     &lt;xs:union memberTypes="tns:EnumerationEndCodeType xs:anyURI" /&gt;
   &lt;/xs:simpleType&gt;
 &lt;/xs:schema&gt;</pre></div></div></div><div class="div1">
-<h2><a name="WSDL" id="WSDL"></a>B WSDL</h2><p>
+<h2><a name="WSDL" id="WSDL"/>B WSDL</h2><p>
     A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</a>
     description for this specification may be retrieved from the
     following address:
@@ -1815,16 +1770,11 @@
   &lt;/wsdl:portType&gt;
 
 &lt;/wsdl:definitions&gt;</pre></div></div></div><div class="div1">
-<h2><a name="changelog" id="changelog"></a>C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a>
-      </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a>
-      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a>
-      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a>
-      </td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a>
-      </td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6399">6399</a>
-      </td></tr></tbody></table></div></div></body></html>
+<h2><a name="changelog" id="changelog"/>C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a></td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6399">6399</a></td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- wsenum.xml	19 Mar 2009 14:11:55 -0000	1.17
+++ wsenum.xml	23 Mar 2009 19:38:29 -0000	1.18
@@ -273,6 +273,51 @@
        </p>
       </item>
      </ulist>
+
+     <p>
+      In addition to Message Information Header properties
+      <bibref ref="AddrCore"/>,
+      this specification uses the following properties to define messages:
+     </p>
+ 
+     <glist>
+      <gitem>
+       <label> <kw>[Headers]</kw> </label>
+       <def>
+        <p> Unordered message headers. </p>
+       </def>
+      </gitem>
+ 
+      <gitem>
+       <label> <kw>[Action]</kw> </label>
+       <def>
+        <p> The value to be used for the wsa:Action URI. </p>
+       </def>
+      </gitem>
+ 
+      <gitem>
+       <label> <kw>[Body]</kw> </label>
+       <def>
+        <p> A message body. </p>
+       </def>
+      </gitem>
+     </glist>
+ 
+     <p>
+      These properties bind to a SOAP Envelope as follows:
+     </p>
+ 
+     <example>
+     <eg>&lt;s:Envelope&gt;
+  &lt;s:Header&gt;
+    <kw>[Headers]</kw>
+    &lt;wsa:Action&gt;<kw>[Action]</kw>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<kw>[Body]</kw>&lt;/s:Body&gt;
+&lt;/s:Envelope&gt;</eg>
+     </example>
+
     </div2>
 
     <div2 id="namespaces">
@@ -338,7 +383,7 @@
            http://www.w3.org/2005/08/addressing
           </loc>
          </td>
-         <td> WS-Addressing <bibref ref="WSAddressing"/> </td>
+         <td> WS-Addressing <bibref ref="AddrCore"/> </td>
         </tr>
         <tr>
          <td> wsam </td>
@@ -347,7 +392,7 @@
            http://www.w3.org/2007/05/addressing/metadata
           </loc>
          </td>
-         <td> WS-Addressing <bibref ref="WSAddressing"/> </td>
+         <td> WS-Addressing <bibref ref="AddrCore"/> </td>
         </tr>
         <tr>
          <td> xs </td>
@@ -506,7 +551,7 @@
    <p>
     All messages defined by this specification MUST be sent
     to a Web service that is addressable by an EPR 
-    <bibref ref="WSAddressing"/>.
+    <bibref ref="AddrCore"/>.
    </p>
 
    <div2 id="Enumerate">
@@ -2338,12 +2383,12 @@
       , M. Gudgin, et al, June 2003.
     </bibl>
 
-    <bibl key="WS-Addressing" id="WSAddressing"
-     href="http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/">
+    <bibl key="WS-Addressing" id="AddrCore"
+     href="http://www.w3.org/2005/08/addressing/">
       <titleref>
-       Web Services Addressing (WS-Addressing)
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
       </titleref>
-      ,D. Box, et al, August 2004.
+      , May 2006.
     </bibl>
 
     <bibl key="WS-Policy" id="wspolicy"
@@ -2875,6 +2920,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6399">6399</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/03/23 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -d -r1.29 -r1.30
--- wsmex.html	19 Mar 2009 14:14:22 -0000	1.29
+++ wsmex.html	23 Mar 2009 19:38:29 -0000	1.30
@@ -1,6 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Metadata Exchange (WS-MetadataExchange)</title><style type="text/css">
+<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>Web Services Metadata Exchange (WS-MetadataExchange)</title><style type="text/css">
 code           { font-family: monospace; }
 
 div.constraint,
@@ -30,56 +28,51 @@
 div.exampleWrapper { margin: 4px }
 div.exampleHeader { font-weight: bold;
                     margin: 4px}
-</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css" /></head><body><div class="head">
-<h1><a name="title" id="title"></a>Web Services Metadata Exchange (WS-MetadataExchange)</h1>
-<h2><a name="w3c-doctype" id="w3c-doctype"></a>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd>
-    <a href="http://www.w3.org/TR/ws-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange
-   </a>
-  </dd><dt>Previous version:</dt><dd>
-   <a href="http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317">http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317
-   </a>
-  </dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr /><div>
-<h2><a name="abstract" id="abstract"></a>Abstract</h2><p>
+</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
+<h1><a name="title" id="title"/>Web Services Metadata Exchange (WS-MetadataExchange)</h1>
+<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange
+   </a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317">http://www.w3.org/TR/2009/WD-ws-metadata-exchange-20090317</a></dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 2009 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http//www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
     This specification defines how metadata
     associated with a Web service endpoint can be represented as
     <a href="#WS-Transfer">[WS-Transfer]</a> resources, how metadata can
-    be embedded in <a href="#AddrCore">[WS-Addressing 1.0 Core]</a>
+    be embedded in <a href="#AddrCore">[WS-Addressing]</a>
     endpoint references, and how metadata could be
     retrieved from a Web service endpoint.
    </p></div><div>
-<h2><a name="status" id="status"></a>Status of this Document</h2><p><strong>This document is an editors' copy that has
+<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
         no official standing.</strong></p></div><div class="toc">
-<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#Composable">Composable Architecture</a><br />
-2 <a href="#Introduction">Introduction</a><br />
-&nbsp;&nbsp;&nbsp;2.1 <a href="#Requirements">Requirements</a><br />
-&nbsp;&nbsp;&nbsp;2.2 <a href="#Example">Example</a><br />
-3 <a href="#Notation">Notation</a><br />
-&nbsp;&nbsp;&nbsp;3.1 <a href="#Namespaces">XML Namespaces</a><br />
-&nbsp;&nbsp;&nbsp;3.2 <a href="#Conventions">Notational Conventions</a><br />
-&nbsp;&nbsp;&nbsp;3.3 <a href="#Compliance">Compliance</a><br />
-4 <a href="#metadata-resources">Metadata Resources</a><br />
-5 <a href="#web-services-metadata">Web Services Metadata</a><br />
-6 <a href="#Retrieving-Metadata">Retrieving Metadata</a><br />
-&nbsp;&nbsp;&nbsp;6.1 <a href="#WS-Transfer-Get">WS-Transfer Get</a><br />
-&nbsp;&nbsp;&nbsp;6.2 <a href="#Get-Metadata">Get Metadata</a><br />
-7 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br />
-8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br />
-9 <a href="#Security">Security</a><br />
-10 <a href="#Acknowledgements">Acknowledgements</a><br />
-11 <a href="#References">References</a><br />
+<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#Composable">Composable Architecture</a><br/>
+2 <a href="#Introduction">Introduction</a><br/>
+&nbsp;&nbsp;&nbsp;2.1 <a href="#Requirements">Requirements</a><br/>
+&nbsp;&nbsp;&nbsp;2.2 <a href="#Example">Example</a><br/>
+3 <a href="#Notation">Notation</a><br/>
+&nbsp;&nbsp;&nbsp;3.1 <a href="#Namespaces">XML Namespaces</a><br/>
+&nbsp;&nbsp;&nbsp;3.2 <a href="#Conventions">Notational Conventions</a><br/>
+&nbsp;&nbsp;&nbsp;3.3 <a href="#Compliance">Compliance</a><br/>
+4 <a href="#metadata-resources">Metadata Resources</a><br/>
+5 <a href="#web-services-metadata">Web Services Metadata</a><br/>
+6 <a href="#Retrieving-Metadata">Retrieving Metadata</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#WS-Transfer-Get">WS-Transfer Get</a><br/>
+&nbsp;&nbsp;&nbsp;6.2 <a href="#Get-Metadata">Get Metadata</a><br/>
+7 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
+8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br/>
+9 <a href="#Security">Security</a><br/>
+10 <a href="#Acknowledgements">Acknowledgements</a><br/>
+11 <a href="#References">References</a><br/>
 </p>
-<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br />
-B <a href="#Appendix-B">WSDL</a><br />
-C <a href="#changelog">Change Log</a><br />
-</p></div><hr /><div class="body"><div class="div1">
-<h2><a name="Composable" id="Composable"></a>1 Composable Architecture</h2><p>
+<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
+B <a href="#Appendix-B">WSDL</a><br/>
+C <a href="#changelog">Change Log</a><br/>
+</p></div><hr/><div class="body"><div class="div1">
+<h2><a name="Composable" id="Composable"/>1 Composable Architecture</h2><p>
     The Web services specifications (WS-*) are designed to be composed with 
     each other to provide a rich set of tools for the Web services 
     environment. This specification specifically relies on other Web 
     services specifications to provide secure, reliable, and/or transacted 
     message delivery and to express Web service metadata.
    </p></div><div class="div1">
-<h2><a name="Introduction" id="Introduction"></a>2 Introduction</h2><p>
+<h2><a name="Introduction" id="Introduction"/>2 Introduction</h2><p>
     Web services use metadata to describe what other endpoints need to know 
     to interact with them. Specifically, <a href="#WS-Policy">[WS-Policy]</a> 
     describes the capabilities, requirements, and general characteristics 
@@ -108,7 +101,7 @@
     mechanism for other types of data associated with a Web service, 
     such as state data, properties and attribute values, etc.
    </p><div class="div2">
-<h3><a name="Requirements" id="Requirements"></a>2.1 Requirements</h3><p>
+<h3><a name="Requirements" id="Requirements"/>2.1 Requirements</h3><p>
      This specification intends to meet the following requirements:
     </p><ul><li><p>
        Define an encapsulation format for metadata.
@@ -133,12 +126,11 @@
        Enable description in <a href="#WSDL11">[WSDL 1.1]</a> of the optional 
        request-response interaction.
       </p></li></ul></div><div class="div2">
-<h3><a name="Example" id="Example"></a>2.2 Example</h3><p>
-     <a href="#GetRequest">Example 2-1</a> illustrates a sample 
+<h3><a name="Example" id="Example"/>2.2 Example</h3><p><a href="#GetRequest">Example 2-1</a> illustrates a sample 
      <a href="#WS-Transfer">[WS-Transfer]</a> Get request for a resource'
      s representation.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetRequest" id="GetRequest"></a>Example 2-1: Sample Get request message</div><div class="exampleInner"><pre>(01)  &lt;s11:Envelope
+<div class="exampleHeader"><a name="GetRequest" id="GetRequest"/>Example 2-1: Sample Get request message</div><div class="exampleInner"><pre>(01)  &lt;s11:Envelope
 (02)     xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
 (03)     xmlns:wsa='http://www.w3.org/2005/08/addressing'&gt;
 (04)    &lt;s11:Header&gt;
@@ -162,11 +154,10 @@
      endpoint. The fact that the resource's representation is a 
      mex:Metadata element may be known to the requestor but is not 
      explicitly encoded in the request message.
-    </p><p>
-     <a href="#GetResponse">Example 2-2</a> illustrates a sample response to the 
+    </p><p><a href="#GetResponse">Example 2-2</a> illustrates a sample response to the 
      request of <a href="#GetRequest">Example 2-1</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetResponse" id="GetResponse"></a>Example 2-2: Sample response message with metadata</div><div class="exampleInner"><pre>(01)  &lt;s11:Envelope
+<div class="exampleHeader"><a name="GetResponse" id="GetResponse"/>Example 2-2: Sample response message with metadata</div><div class="exampleInner"><pre>(01)  &lt;s11:Envelope
 (02)      xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
 (03)      xmlns:wsa='http://www.w3.org/2005/08/addressing'
 (04)      xmlns:mex='http://www.w3.org/2009/02/ws-mex'
@@ -258,7 +249,7 @@
      <a href="#Schema2">[XML Schema: Datatypes]</a> used by the WSDL document. The schemas can 
      be retrieved through an HTTP GET request at the identified URL 
      (lines 65-67). The third Metadata Section (lines 69-77) contains 
-     the <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> endpoint reference (lines 72-75) of 
+     the <a href="#AddrCore">[WS-Addressing]</a> endpoint reference (lines 72-75) of 
      a <a href="#WS-Transfer">[WS-Transfer]</a> resource the representation of 
      which is a <a href="#WS-Policy">[WS-Policy]</a> document as indicated by 
      the Dialect attribute (line 70). The WS-Policy document is the 
@@ -272,7 +263,7 @@
      <a href="#GetMexReq">Example 2-3</a> illustrates a sample Get Metadata request 
      for the <a href="#WS-Policy">[WS-Policy]</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq"></a>Example 2-3: Sample Get Metadata request message</div><div class="exampleInner"><pre>(01)  &lt;s11:Envelope
+<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq"/>Example 2-3: Sample Get Metadata request message</div><div class="exampleInner"><pre>(01)  &lt;s11:Envelope
 (02)      xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
 (03)      xmlns:wsa='http://www.w3.org/2005/08/addressing'
 (04)      xmlns:mex='http://www.w3.org/2009/02/ws-mex' &gt;
@@ -298,11 +289,10 @@
      Lines 7-9 in <a href="#GetMexReq">Example 2-3</a> indicate this is a Get Metadata 
      request. As lines 18-21 indicate, this request is for the policy of 
      the Web service endpoint (line 6).
-    </p><p>
-     <a href="#GetMexRes">Example 2-4</a> lists a sample response to the request in 
+    </p><p><a href="#GetMexRes">Example 2-4</a> lists a sample response to the request in 
      <a href="#GetMexReq">Example 2-3</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetMexRes" id="GetMexRes"></a>Example 2-4: Sample Get Metadata response message</div><div class="exampleInner"><pre>(01)   &lt;s11:Envelope
+<div class="exampleHeader"><a name="GetMexRes" id="GetMexRes"/>Example 2-4: Sample Get Metadata response message</div><div class="exampleInner"><pre>(01)   &lt;s11:Envelope
 (02)      xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
 (03)      xmlns:wsa='http://www.w3.org/2005/08/addressing'
 (04)      xmlns:wsp='http://schemas.xmlsoap.org/ws/2004/09/policy'
@@ -340,15 +330,14 @@
      Web service endpoint to which the Get Metadata request of 
      <a href="#GetMexReq">Example 2-3</a> was directed.
     </p></div></div><div class="div1">
-<h2><a name="Notation" id="Notation"></a>3 Notation</h2><div class="div2">
-<h3><a name="Namespaces" id="Namespaces"></a>3.1 XML Namespaces</h3><p>
+<h2><a name="Notation" id="Notation"/>3 Notation</h2><div class="div2">
+<h3><a name="Namespaces" id="Namespaces"/>3.1 XML Namespaces</h3><p>
      The XML namespace URI that MUST be used by implementations of this 
      specification is:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex">http://www.w3.org/2009/02/ws-mex</a></pre></div></div><p> 
-     <a href="#XMLNS">Table 3-1</a> lists XML namespaces that are used in this 
+    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex">http://www.w3.org/2009/02/ws-mex</a></pre></div></div><p><a href="#XMLNS">Table 3-1</a> lists XML namespaces that are used in this 
      specification. The choice of any namespace prefix is arbitrary and 
      not semantically significant.
-    </p><a name="XMLNS" id="XMLNS"></a><table border="1"><caption>Table 3-1:  Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td> <a href="#SOAP11">[SOAP 1.1]</a> </td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td> <a href="#SOAP12">[SOAP 1.2]</a> </td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td> <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> </td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td> <a href="#WSDL11">[WSDL 1.1]</a> </td></tr><tr><td> wsp </td><td> http://schemas.xmlsoap.org/ws/2004/09/policy </td><td> <a href="#WS-Policy">[WS-Policy]</a> </td></tr><tr><td> mex </td><td> http://www.w3.org/2009/02/ws-mex </td><td>This specification </td></tr><tr><td> xs </td><td> http://www.w3.org/2001/XMLSchema </td><td> <a href="#Schema1">[XML Schema: Structures]</a> </td></tr><tr><td> wst </td><td> http://www.w3.org/2009/02/ws-tra </td><td> <a href="#WS-Transfer">[WS-Transfer]</a> </td></tr></tbody></table><p>
+    </p><a name="XMLNS" id="XMLNS"/><table border="1"><caption>Table 3-1:  Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td><a href="#SOAP11">[SOAP 1.1]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP12">[SOAP 1.2]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL 1.1]</a></td></tr><tr><td> wsp </td><td> http://schemas.xmlsoap.org/ws/2004/09/policy </td><td><a href="#WS-Policy">[WS-Policy]</a></td></tr><tr><td> mex </td><td> http://www.w3.org/2009/02/ws-mex </td><td> This specification </d></tr><tr><td> xs </td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#Schema1">[XML Schema: Structures]</a></td></tr><tr><td> wst </td><td> http://www.w3.org/2009/02/ws-tra </td><td><a href="#WS-Transfer">[WS-Transfer]</a></td></tr></tbody></table><p>
      The working group intends to update the value of the Web Services
      Metadata Exchange namespace URI each time a new version of this document is
      published until such time that the document reaches Candidate
@@ -365,7 +354,7 @@
       http://www.w3.org/2005/07/13-nsuri
      </a>.
     </p></div><div class="div2">
-<h3><a name="Conventions" id="Conventions"></a>3.2 Notational Conventions</h3><p>
+<h3><a name="Conventions" id="Conventions"/>3.2 Notational Conventions</h3><p>
      The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
      document are to be interpreted as described in RFC 2119 
@@ -398,45 +387,35 @@
        XML namespace prefixes (see <a href="#XMLNS">Table 3-1</a>) are used to 
        indicate the namespace of the element being defined.
       </p></li></ul><p>
-     
-    In addition to Message Information Header properties
-    
-     <a href="#AddrCore">[WS-Addressing 1.0 Core]</a>, 
-    
-    this specification uses the following properties to define messages:
-    
-    </p><dl><dt class="label"> <b>[Headers]</b> </dt><dd><p>Unordered message headers. </p></dd><dt class="label"> <b>[Action]</b> </dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"> <b>[Body]</b> </dt><dd><p> A message body. </p></dd></dl><p>
-     
+     In addition to Message Information Header properties
+     <a href="#AddrCore">[WS-Addressing]</a>, 
+     this specification uses the following properties to define messages:
+    </p><dl><dt class="label"><b>[Headers]</b></dt><dd><p> Unordered message headers. </p></dd><dt class="label"><b>[Action]</b></dt><dd><p> The value to be used for the wsa:Action URI. </p></dd><dt class="label"><b>[Body]</b></dt><dd><p> A message body. </p></dd></dl><p>
      These properties bind to a SOAP Envelope as follows:
-     
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>
-   &lt;s:Envelope&gt;
-     &lt;s:Header&gt;
-       <b>[Headers]</b>
-       &lt;wsa:Action&gt;<b>[Action]</b>&lt;/wsa:Action&gt;
-       ...
-     &lt;/s:Header&gt;
-     &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt; 
-   &lt;/s:Envelope&gt;</pre></div></div><p>
-     
+    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope&gt;
+  &lt;s:Header&gt;
+    <b>[Headers]</b>
+    &lt;wsa:Action&gt;<b>[Action]</b>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<b>[Body]</b>&lt;/s:Body&gt; 
+&lt;/s:Envelope&gt;</pre></div></div><p>
      This specification defines Fault properties for each defined
-     
      fault and defines SOAP bindings for each Fault property.
-     
     </p></div><div class="div2">
-<h3><a name="Compliance" id="Compliance"></a>3.3 Compliance</h3><p>
+<h3><a name="Compliance" id="Compliance"/>3.3 Compliance</h3><p>
      An implementation is not compliant with this specification if it 
      fails to satisfy one or more of the MUST or REQUIRED level 
      requirements defined herein. A SOAP Node MUST NOT use the XML 
      namespace identifier for this specification (listed in 
      <a href="#Conventions"><b>3.2 Notational Conventions</b></a>) within XML documents, SOAP Envelopes, 
-     and <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> endpoint 
+     and <a href="#AddrCore">[WS-Addressing]</a> endpoint 
      references unless it is compliant with this specification.
     </p><p>
      Support for the GetMetadata operation by a Web service is 
      optional. If metadata about a Web service endpoint is referenced by 
      a Metadata Reference, which is a 
-     <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> endpoint reference, then the Metadata 
+     <a href="#AddrCore">[WS-Addressing]</a> endpoint reference, then the Metadata 
      Reference MUST refer to a <a href="#WS-Transfer">[WS-Transfer]</a> resource. 
      The referred resource MAY also support other resource management 
      and access specifications (e.g. HTTP, WS-ResourceFramework).
@@ -449,11 +428,11 @@
     </p><p>
      All messages defined by this specification MUST be sent
      to a Web service that is addressable by an EPR
-     <a href="#AddrCore">[WS-Addressing 1.0 Core]</a>.
+     <a href="#AddrCore">[WS-Addressing]</a>.
     </p></div></div><div class="div1">
-<h2><a name="metadata-resources" id="metadata-resources"></a>4 Metadata Resources</h2><p>
+<h2><a name="metadata-resources" id="metadata-resources"/>4 Metadata Resources</h2><p>
     A resource is a Web service that is addressable by an endpoint 
-    reference <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> and can 
+    reference <a href="#AddrCore">[WS-Addressing]</a> and can 
     be represented by an XML Infoset. The resource's representation can be 
     retrieved using the Get operation defined in 
     <a href="#WS-Transfer">[WS-Transfer]</a>.
@@ -479,7 +458,7 @@
     non-static metadata by authorized agents), or other resource management 
     and access specifications (e.g. HTTP, WS-ResourceFramework).
    </p></div><div class="div1">
-<h2><a name="web-services-metadata" id="web-services-metadata"></a>5 Web Services Metadata</h2><p>
+<h2><a name="web-services-metadata" id="web-services-metadata"/>5 Web Services Metadata</h2><p>
     The Web service Metadata element is a collection of metadata units 
     such as <a href="#WSDL11">[WSDL 1.1]</a> definitions, <a href="#Schema1">[XML Schema: Structures]</a> 
     documents, <a href="#WS-Policy">[WS-Policy]</a> expressions, etc. Each unit 
@@ -491,7 +470,7 @@
     @Dialect and (optionally) @Identifier of the metadata unit. To ensure 
     scalability, a unit of metadata may be included in-line within its 
     Metadata Section or may be included by reference, either an endpoint 
-    reference <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> 
+    reference <a href="#AddrCore">[WS-Addressing]</a> 
     (Metadata Reference) or a URL (Location).
    </p><p>
     The outline for the Metadata element is: 
@@ -534,7 +513,7 @@
     This specification defines the following values for Dialect; 
     other specifications should define values for Dialect for their 
     metadata format(s).
-   </p><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#Schema1">[XML Schema: Structures]</a> </td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL 1.1]</a> </td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy</td><td> wsp:Policy <a href="#WS-Policy">[WS-Policy]</a> </td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy/attachment </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a> </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex-all </td><td> None.  [Defined in this specification for use in GetMetadata requests.  See <a href="#Get-Metadata"><b>6.2 Get Metadata</b></a>.] </td></tr></tbody></table><p>
+   </p><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#Schema1">[XML Schema: Structures]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL 1.1]</a></td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy</td><td> wsp:Policy <a href="#WS-Policy">[WS-Policy]</a></td></tr><tr><td> http://schemas.xmlsoap.org/ws/2004/09/policy/attachment </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex-all </td><td> None.  [Defined in this specification for use in GetMetadata requests.  See <a href="#Get-Metadata"><b>6.2 Get Metadata</b></a>.] </td></tr></tbody></table><p>
     If there is more than one metadata unit with the same Dialect, e.g., 
     more than one XML Schema document, including them all, one per 
     Metadata Section, is explicitly encouraged.
@@ -575,7 +554,7 @@
     explicitly encouraged.
    </p><dl><dt class="label">/mex:Metadata/mex:MetadataSection/mex:MetadataReference</dt><dd><p>
        This is an endpoint reference to a metadata resource and is 
-       of type EndpointReferenceType as defined by <a href="#AddrCore">[WS-Addressing 1.0 Core]</a>. 
+       of type EndpointReferenceType as defined by <a href="#AddrCore">[WS-Addressing]</a>. 
        The resource MUST support the GET operation 
        <a href="#WS-Transfer">[WS-Transfer]</a> to allow the retrieval of the 
        metadata unit for the Metadata Section's Dialect and Identifier 
@@ -594,8 +573,8 @@
        the metadata unit associated with the Metadata Section's Dialect 
        and Identifier.
       </p></dd></dl></div><div class="div1">
-<h2><a name="Retrieving-Metadata" id="Retrieving-Metadata"></a>6 Retrieving Metadata</h2><div class="div2">
-<h3><a name="WS-Transfer-Get" id="WS-Transfer-Get"></a>6.1 WS-Transfer Get</h3><p>
+<h2><a name="Retrieving-Metadata" id="Retrieving-Metadata"/>6 Retrieving Metadata</h2><div class="div2">
+<h3><a name="WS-Transfer-Get" id="WS-Transfer-Get"/>6.1 WS-Transfer Get</h3><p>
      To retrieve the representation of a metadata resource, a requester 
      MAY send a <a href="#WS-Transfer">[WS-Transfer]</a> Get request message to the 
      metadata resource's endpoint. The WS-Transfer Get request fetches a 
@@ -611,7 +590,7 @@
      <a href="#WS-Policy">[WS-Policy]</a>) for which a mex:MetadataSection/@Dialect 
      has been defined.
     </p></div><div class="div2">
-<h3><a name="Get-Metadata" id="Get-Metadata"></a>6.2 Get Metadata</h3><p>
+<h3><a name="Get-Metadata" id="Get-Metadata"/>6.2 Get Metadata</h3><p>
      When the metadata for an endpoint is not available or is unknown 
      and there is no information on how to retrieve it (e.g. an endpoint 
      reference to a <a href="#WS-Transfer">[WS-Transfer]</a> resource representing 
@@ -635,20 +614,20 @@
   &lt;/mex:GetMetadata&gt; </pre></div></div><p>
      The following describes additional, normative constraints on the 
      outline listed above:
-    </p><dl><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect </dt><dd><p>
+    </p><dl><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect </dt><dd><p>
         When this repeating OPTIONAL element is present,the response
         MUST include only Metadata Sections corresponding to the
         dialect specified by the URI attribute; if the receiver does 
         not have any Metadata Sections of the indicated dialect, the 
         response MUST include zero Metadata Sections. </p><p>When this element 
         is not present, the endpoint SHOULD return all the types of metadata that it deems necessary to communicate with it.
-       </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI </dt><dd><p>
+       </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI </dt><dd><p>
         This REQUIRED attribute specifies the Metadata dialect. The response MUST only include Metadata Sections corresponding to the dialect specified by this URI. If the receiver does not have any Metadata Sections of this indicated dialect, the response MUST include zero Metadata Sections for this URI. 
-       </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex-all"  </dt><dd><p>
+       </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex-all"  </dt><dd><p>
         This value returns all known metadata.  The endpoint has the option to optimize the format in which it returns the data. 
-       </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex"</dt><dd><p>
+       </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI="http://www.w3.org/2009/02/ws-mex/Dialects/ws-mex"</dt><dd><p>
         This value returns no metadata sections. 
-       </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@Identifier </dt><dd><p>
+       </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@Identifier </dt><dd><p>
         When this OPTIONAL attribute is present, the response MUST include only
         Metadata Sections with the indicated identifier; if the receiver 
         does not have any Metadata Sections of the indicated identifier, 
@@ -658,7 +637,7 @@
         identifier. 
         If multiple Metadata Sections have the indicated Dialect 
         and Identifier then all of them MUST be returned.
-       </p></dd><dt class="label"> <b>[Body]</b>/mex:GetMetadata/mex:Dialect@Content </dt><dd><p>
+       </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@Content </dt><dd><p>
         When this OPTIONAL attribute is present, the response MUST include only
         Metadata Sections of this specified content form. If the specified
         content form is not available then the response MUST include zero
@@ -669,13 +648,13 @@
         "http://www.w3.org/2009/02/ws-mex/Content/Any".
        </p></dd></dl><p>
      Other message information headers defined by WS-Addressing 
-     <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> MAY be included 
+     <a href="#AddrCore">[WS-Addressing]</a> MAY be included 
      in the request and response messages, according to the usage and 
      semantics defined in WS-Addressing.
     </p><p>
      An endpoint MAY respond with a fault message using the standard 
      fault codes defined in WS-Addressing 
-     <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> (e.g., wsa:ActionNotSupported).
+     <a href="#AddrCore">[WS-Addressing]</a> (e.g., wsa:ActionNotSupported).
     </p><p>
      If an endpoint accepts a Get Metadata request, it MUST reply with 
      a Get Metadata response message. The normative outline for a 
@@ -689,12 +668,11 @@
  &lt;/mex:Metadata&gt;</pre></div></div><p>
      The following describes additional, normative constraints on the 
      outline listed above:
-    </p><dl><dt class="label"> <b>[Body]</b>/mex:Metadata </dt><dd><p>
+    </p><dl><dt class="label"><b>[Body]</b>/mex:Metadata </dt><dd><p>
         The body of the response message MUST contain one mex:Metadata 
         element as defined in Section 4 of this specification.
        </p></dd></dl></div></div><div class="div1">
-<h2><a name="Metadata-in-Endpoint-References" id="Metadata-in-Endpoint-References"></a>7 Metadata in Endpoint References</h2><p>
-    <a href="#Retrieving-Metadata"><b>6 Retrieving Metadata</b></a> describes two mechanisms that 
+<h2><a name="Metadata-in-Endpoint-References" id="Metadata-in-Endpoint-References"/>7 Metadata in Endpoint References</h2><p><a href="#Retrieving-Metadata"><b>6 Retrieving Metadata</b></a> describes two mechanisms that 
     allow requesters to retrieve ("pull metadata") Web services metadata 
     from an endpoint (GetMetadata) or a metadata resource 
     (WS-Transfer Get).
@@ -710,7 +688,7 @@
     the issuer of the endpoint reference to include metadata by value 
     or by reference, according to the options described in 
     <a href="#web-services-metadata"><b>5 Web Services Metadata</b></a>. 
-    The outline of a <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> endpoint reference which 
+    The outline of a <a href="#AddrCore">[WS-Addressing]</a> endpoint reference which 
     includes Web services metadata is as follows:
    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wsa:EndpointReference&gt;
     &lt;wsa:Address&gt;xs:anyURI&lt;/wsa:Address&gt;
@@ -724,11 +702,11 @@
        A unique mex:Metadata element appearing as a direct child of the 
        wsa:Metadata endpoint reference element.
       </p></dd></dl><p>
-    In the example of <a href="#EPRMEX">Example 7-1</a>, a <a href="#AddrCore">[WS-Addressing 1.0 Core]</a> 
+    In the example of <a href="#EPRMEX">Example 7-1</a>, a <a href="#AddrCore">[WS-Addressing]</a> 
     endpoint reference contains WSDL metadata by value that identifies 
     the binding used to access the service endpoint:
    </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="EPRMEX" id="EPRMEX"></a>Example 7-1: Endpoint reference with embedded WSDL metadata</div><div class="exampleInner"><pre>(01)  &lt;wsa:EndpointReference
+<div class="exampleHeader"><a name="EPRMEX" id="EPRMEX"/>Example 7-1: Endpoint reference with embedded WSDL metadata</div><div class="exampleInner"><pre>(01)  &lt;wsa:EndpointReference
 (02)      xmlns:wsa='http://www.w3.org/2005/08/addressing'&gt;
 (03)    &lt;wsa:Address&gt;http://services.example.org/stockquote&lt;/wsa:Address&gt;
 (04)    &lt;wsa:Metadata&gt;
@@ -812,7 +790,7 @@
     to the metadata resource's endpoint, as defined in 
     <a href="#Bootstrapping-Metadata-Retrieval"><b>8 Bootstrapping Metadata Retrieval</b></a>.
    </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="EPRMD" id="EPRMD"></a>Example 7-2: Endpoint reference with embedded metadata about the Metadata Reference</div><div class="exampleInner"><pre>(01)  &lt;wsa:EndpointReference
+<div class="exampleHeader"><a name="EPRMD" id="EPRMD"/>Example 7-2: Endpoint reference with embedded metadata about the Metadata Reference</div><div class="exampleInner"><pre>(01)  &lt;wsa:EndpointReference
 (02)      xmlns:wsa='http://www.w3.org/2005/08/addressing'&gt;
 (03)    &lt;wsa:Address&gt;http://services.example.org/stockquote&lt;/wsa:Address&gt;
 (04)    &lt;wsa:Metadata&gt;
@@ -836,8 +814,7 @@
 (22)        &lt;/mex:MetadataSection&gt;
 (23)      &lt;/mex:Metadata&gt;
 (24)    &lt;/wsa:Metadata&gt;
-(25)  &lt;/wsa:EndpointReference&gt;</pre></div></div><p>
-    <a href="#EPRMD">Example 7-2</a> shows an example of a Web service endpoint 
+(25)  &lt;/wsa:EndpointReference&gt;</pre></div></div><p><a href="#EPRMD">Example 7-2</a> shows an example of a Web service endpoint 
     reference in which the Metadata element contains a single 
     Metadata Reference element to a metadata resource (lines 8-21) the 
     representation of which is mex:Metadata as hinted by the value of 
@@ -850,7 +827,7 @@
     WSDL portType and the necessary binding information for communicating 
     with that resource.
    </p></div><div class="div1">
-<h2><a name="Bootstrapping-Metadata-Retrieval" id="Bootstrapping-Metadata-Retrieval"></a>8 Bootstrapping Metadata Retrieval</h2><p>
+<h2><a name="Bootstrapping-Metadata-Retrieval" id="Bootstrapping-Metadata-Retrieval"/>8 Bootstrapping Metadata Retrieval</h2><p>
     This specification provides several mechanisms to aid service 
     endpoints and service requesters in bootstrapping the interaction. 
     In particular, the mechanisms described in 
@@ -867,14 +844,14 @@
     metadata retrieval may be defined by communities within the 
     context of particular application domains. 
    </p></div><div class="div1">
-<h2><a name="Security" id="Security"></a>9 Security</h2><p>
+<h2><a name="Security" id="Security"/>9 Security</h2><p>
     It is strongly RECOMMENDED that the communication between Web services 
     be secured using the mechanisms described in WS-Security 
     <a href="#WS-Security">[WS-Security]</a>. In order to properly secure messages, 
     the body and all relevant headers need to be included in the 
     signature. Specifically, any standard messaging headers, such as 
     those from WS-Addressing 
-    <a href="#AddrCore">[WS-Addressing 1.0 Core]</a>, need to be signed with the body in 
+    <a href="#AddrCore">[WS-Addressing]</a>, need to be signed with the body in 
     order to "bind" the two together.
    </p><p>
     Different security mechanisms may be desired depending on the 
@@ -908,43 +885,36 @@
     The following list summarizes common classes of attacks that apply to 
     this protocol and identifies the mechanism to prevent/mitigate 
     the attacks:
-   </p><ul><li><p>
-      <b>Message alteration</b> - Alteration is prevented by including 
+   </p><ul><li><p><b>Message alteration</b> - Alteration is prevented by including 
       signatures of the message information using WS-Security.
-     </p></li><li><p>
-      <b>Message disclosure</b> - Confidentiality is preserved by 
+     </p></li><li><p><b>Message disclosure</b> - Confidentiality is preserved by 
       encrypting sensitive data using WS-Security.
-     </p></li><li><p>
-      <b>Key integrity</b> - Key integrity is maintained by using 
+     </p></li><li><p><b>Key integrity</b> - Key integrity is maintained by using 
       the strongest algorithms possible (by comparing secured policies 
       - see <a href="#WS-Policy">[WS-Policy]</a> and 
       <a href="#WS-SecurityPolicy">[WS-SecurityPolicy]</a>)
-     </p></li><li><p>
-      <b>Authentication</b> - Authentication is established using the 
+     </p></li><li><p><b>Authentication</b> - Authentication is established using the 
       mechanisms described in WS-Security and WS-Trust. Each message is 
       authenticated using the mechanisms described in WS-Security
-     </p></li><li><p>
-      <b>Accountability</b> - Accountability is a function of the type 
+     </p></li><li><p><b>Accountability</b> - Accountability is a function of the type 
       of and strength of the key and algorithms being used. In many 
       cases, a strong symmetric key provides sufficient accountability. 
       However, in some environments, strong PKI signatures are required.
-     </p></li><li><p>
-      <b>Availability</b> - Metadata services are subject to a variety 
+     </p></li><li><p><b>Availability</b> - Metadata services are subject to a variety 
       of availability attacks such as application-level denial of 
       service. It is recommended that the mechanisms described in 
       WS-Security be considered as mitigations for some forms of 
       attacks. Other attacks, such as network-level denial of service 
       are harder to avoid. Note that both of these classes of attack 
       are outside the scope of this specification.
-     </p></li><li><p>
-      <b>Replay</b> - Messages may be replayed for a variety of 
+     </p></li><li><p><b>Replay</b> - Messages may be replayed for a variety of 
       reasons. To detect and eliminate this attack, mechanisms should 
       be used to identify replayed messages such as the timestamp/nonce 
       outlined in WS-Security. Alternatively, and optionally, other 
       technologies, such as sequencing, can also be used to prevent 
       replay of application messages.
      </p></li></ul></div><div class="div1">
-<h2><a name="Acknowledgements" id="Acknowledgements"></a>10 Acknowledgements</h2><p>
+<h2><a name="Acknowledgements" id="Acknowledgements"/>10 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
       Ashok Malhotra (Oracle Corp.),
@@ -966,78 +936,64 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="References" id="References"></a>11 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"></a>RFC 2119</dt><dd>
-     <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="References" id="References"/>11 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
       Key words for use in RFCs to Indicate Requirement Levels
      </cite></a>
       , S. Bradner, Harvard University, March 1997.
-      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>SOAP 1.1</dt><dd>
-     <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+      (See http://www.ietf.org/rfc/rfc2119.txt.)</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP 1.1</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
       Simple Object Access Protocol (SOAP) 1.1
      </cite></a>
      , D. Box, et al, May 2000.
-      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP12" id="SOAP12"></a>SOAP 1.2</dt><dd>
-     <a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
+      (See http://www.w3.org/TR/2000/NOTE-SOAP-20000508/.)</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP 1.2</dt><dd><a href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/"><cite>
       "SOAP Version 1.2 Part 1: Messaging Framework
      </cite></a>
      , M. Gudgin, et al, June 2003.
-      (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="AddrCore" id="AddrCore"></a>WS-Addressing 1.0 Core</dt><dd>
-     <a href="http://www.w3.org/TR/2006/PR-ws-addr-core-20060321/"><cite>
-      Web Services Addressing 1.0 - Core" (Proposed Recommendation)
-     </cite></a>
-     , M. Gudgin, M. Hadley, T. Rogers (editors), March 2006.
-      (See http://www.w3.org/TR/2006/PR-ws-addr-core-20060321/.)</dd><dt class="label"><a name="WS-Policy" id="WS-Policy"></a>WS-Policy</dt><dd>
-     <a href="http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/"><cite>
+      (See http://www.w3.org/TR/2003/REC-soap12-part1-20030624/.)</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/2005/08/addressing/"><cite>
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
+      </cite></a>
+      , May 2006.
+      (See http://www.w3.org/2005/08/addressing/.)</dd><dt class="label"><a name="WS-Policy" id="WS-Policy"/>WS-Policy</dt><dd><a href="http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/"><cite>
       Web Services Policy Framework (WS-Policy)
      </cite></a>
      , S. Bajaj, et al, March 2006.
-      (See http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/.)</dd><dt class="label"><a name="WS-PolicyAttachment" id="WS-PolicyAttachment"></a>WS-PolicyAttachment</dt><dd>
-     <a href="http://www.w3.org/Submission/2006/SUBM-WS-PolicyAttachment-20060425/"><cite>
+      (See http://www.w3.org/Submission/2006/SUBM-WS-Policy-20060425/.)</dd><dt class="label"><a name="WS-PolicyAttachment" id="WS-PolicyAttachment"/>WS-PolicyAttachment</dt><dd><a href="http://www.w3.org/Submission/2006/SUBM-WS-PolicyAttachment-20060425/"><cite>
       Web Services Policy Attachment (WS-PolicyAttachment)
      </cite></a>
      , S. Bajaj, et al, March 2006.
-      (See http://www.w3.org/Submission/2006/SUBM-WS-PolicyAttachment-20060425/.)</dd><dt class="label"><a name="WS-SecureConversation" id="WS-SecureConversation"></a>WS-SecureConversation</dt><dd>
-     <a href="http://www.oasis-open.org/committees/download.php/17364."><cite>
+      (See http://www.w3.org/Submission/2006/SUBM-WS-PolicyAttachment-20060425/.)</dd><dt class="label"><a name="WS-SecureConversation" id="WS-SecureConversation"/>WS-SecureConversation</dt><dd><a href="http://www.oasis-open.org/committees/download.php/17364."><cite>
       Web Services Secure Conversation Language (WS-SecureConversation)
      </cite></a>
      , S. Anderson, et al, February 2005.
-      (See http://www.oasis-open.org/committees/download.php/17364..)</dd><dt class="label"><a name="WS-Security" id="WS-Security"></a>WS-Security</dt><dd>
-     <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
+      (See http://www.oasis-open.org/committees/download.php/17364..)</dd><dt class="label"><a name="WS-Security" id="WS-Security"/>WS-Security</dt><dd><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf"><cite>
       Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)
      </cite></a>
      , A. Nadalin, et al, March 2004.
-      (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WS-SecurityPolicy" id="WS-SecurityPolicy"></a>WS-SecurityPolicy</dt><dd>
-     <a href="http://www.oasis-open.org/committees/download.php/16569/"><cite>
+      (See http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf.)</dd><dt class="label"><a name="WS-SecurityPolicy" id="WS-SecurityPolicy"/>WS-SecurityPolicy</dt><dd><a href="http://www.oasis-open.org/committees/download.php/16569/"><cite>
       Web Services Security Policy Language (WS-SecurityPolicy)
      </cite></a>
      , G. Della-Libera, et al, July 2005.
-      (See http://www.oasis-open.org/committees/download.php/16569/.)</dd><dt class="label"><a name="WS-Transfer" id="WS-Transfer"></a>WS-Transfer</dt><dd>
-     <a href="http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/"><cite>
+      (See http://www.oasis-open.org/committees/download.php/16569/.)</dd><dt class="label"><a name="WS-Transfer" id="WS-Transfer"/>WS-Transfer</dt><dd><a href="http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/"><cite>
       Web Services Transfer (WS-Transfer)
      </cite></a>
      , J. Alexander, et al, September 2004.
-      (See http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/.)</dd><dt class="label"><a name="WS-Trust" id="WS-Trust"></a>WS-Trust</dt><dd>
-     <a href="http://www.oasis-open.org/committees/download.php/17364"><cite>
+      (See http://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060315/.)</dd><dt class="label"><a name="WS-Trust" id="WS-Trust"/>WS-Trust</dt><dd><a href="http://www.oasis-open.org/committees/download.php/17364"><cite>
       Web Services Trust Language (WS-Trust)
      </cite></a>
      , S. Anderson, et al, February 2005.
-      (See http://www.oasis-open.org/committees/download.php/17364.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"></a>WSDL 1.1</dt><dd>
-     <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+      (See http://www.oasis-open.org/committees/download.php/17364.)</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL 1.1</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
       Web Services Description Language (WSDL) 1.1
      </cite></a>
      , E. Christensen, et al, March 2001
-      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="Schema1" id="Schema1"></a>XML Schema: Structures</dt><dd>
-     <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
+      (See http://www.w3.org/TR/2001/NOTE-wsdl-20010315.)</dd><dt class="label"><a name="Schema1" id="Schema1"/>XML Schema: Structures</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"><cite>
       XML Schema Part 1: Structures
      </cite></a>
      , H. Thompson, et al, October 2004.
-      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="Schema2" id="Schema2"></a>XML Schema: Datatypes</dt><dd>
-     <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
+      (See http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.)</dd><dt class="label"><a name="Schema2" id="Schema2"/>XML Schema: Datatypes</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>
       XML Schema Part 2: Datatypes
      </cite></a>
      , P. Biron, et al, October 2004.
       (See http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.)</dd></dl></div></div><div class="back"><div class="div1">
-<h2><a name="Appendix-A" id="Appendix-A"></a>A XML Schema</h2><p>
+<h2><a name="Appendix-A" id="Appendix-A"/>A XML Schema</h2><p>
     A normative copy of the XML Schema <a href="#Schema1">[XML Schema: Structures]</a>,
     <a href="#Schema2">[XML Schema: Datatypes]</a> description for this specification may be 
     retrieved from the following address:
@@ -1106,7 +1062,7 @@
   &lt;xs:element name='MetadataReference' type='wsa:EndpointReferenceType'/&gt;
   &lt;xs:element name='Location' type='xs:anyURI'/&gt;
 &lt;/xs:schema&gt;</pre></div></div></div><div class="div1">
-<h2><a name="Appendix-B" id="Appendix-B"></a>B WSDL</h2><p>
+<h2><a name="Appendix-B" id="Appendix-B"/>B WSDL</h2><p>
     A normative copy of the WSDL <a href="#WSDL11">[WSDL 1.1]</a> description for 
     this specification may be retrieved from the following address:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl">http://www.w3.org/2009/02/ws-mex/metadataexchange.wsdl</a></pre></div></div><p>
@@ -1147,20 +1103,13 @@
   &lt;/wsdl:portType&gt;
 
 &lt;/wsdl:definitions&gt;</pre></div></div></div><div class="div1">
-<h2><a name="changelog" id="changelog"></a>C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a>
-      </td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a>
-      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6639">6639</a>
-      </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a>
-      </td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a>
-      </td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6405">6405</a>
-      </td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6604">6604</a>
-      </td></tr><tr><td> 2009/03/18 </td><td> AM </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6404">6404</a>
-      </td></tr></tbody></table></div></div></body></html>
+<h2><a name="changelog" id="changelog"/>C Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a></td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6639">6639</a></td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a></td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6405">6405</a></td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6604">6604</a></td></tr><tr><td> 2009/03/18 </td><td> AM </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6404">6404</a></td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- wseventing.xml	19 Mar 2009 14:11:55 -0000	1.22
+++ wseventing.xml	23 Mar 2009 19:38:29 -0000	1.23
@@ -500,6 +500,51 @@
       </p>
      </item>
     </ulist>
+
+    <p>
+     In addition to Message Information Header properties
+     <bibref ref="AddrCore"/>,
+     this specification uses the following properties to define messages:
+    </p>
+
+    <glist>
+     <gitem>
+      <label> <kw>[Headers]</kw> </label>
+      <def>
+       <p> Unordered message headers. </p>
+      </def>
+     </gitem>
+
+     <gitem>
+      <label> <kw>[Action]</kw> </label>
+      <def>
+       <p> The value to be used for the wsa:Action URI. </p>
+      </def>
+     </gitem>
+
+     <gitem>
+      <label> <kw>[Body]</kw> </label>
+      <def>
+       <p> A message body. </p>
+      </def>
+     </gitem>
+    </glist>
+
+    <p>
+     These properties bind to a SOAP Envelope as follows:
+    </p>
+
+    <example>
+     <eg>&lt;s:Envelope&gt;
+  &lt;s:Header&gt;
+    <kw>[Headers]</kw>
+    &lt;wsa:Action&gt;<kw>[Action]</kw>&lt;/wsa:Action&gt;
+    ...
+  &lt;/s:Header&gt;
+  &lt;s:Body&gt;<kw>[Body]</kw>&lt;/s:Body&gt;
+&lt;/s:Envelope&gt;</eg>
+    </example>
+
    </div2>
 
    <div2 id="namespaces">
@@ -568,7 +613,7 @@
          http://www.w3.org/2005/08/addressing
         </loc>
        </td>
-       <td>WS-Addressing <bibref ref="WSAddressing"/></td>
+       <td>WS-Addressing <bibref ref="AddrCore"/></td>
       </tr>
       <tr>
        <td>wse</td>
@@ -750,7 +795,7 @@
    <p>
     All messages defined by this specification MUST be sent
     to a Web service that is addressable by an EPR
-    <bibref ref="WSAddressing"/>.
+    <bibref ref="AddrCore"/>.
    </p>
 
    <div2 id="Subscribe">
@@ -1047,7 +1092,7 @@
 
     <p>
      Other message information headers defined by WS-Addressing
-     <bibref ref="WSAddressing"/> MAY be included in
+     <bibref ref="AddrCore"/> MAY be included in
      the request and response messages, according to the usage and
      semantics defined in WS-Addressing.
     </p>
@@ -1835,7 +1880,7 @@
 
     <p>
      Other message information headers defined by WS-Addressing
-     <bibref ref="WSAddressing"/> MAY be included in
+     <bibref ref="AddrCore"/> MAY be included in
      the message, according to the usage and semantics defined in
      WS-Addressing.
     </p>
@@ -1901,7 +1946,7 @@
     header blocks in the Subscribe request, in the
     /s:Envelope/s:Body/wse:Subscribe/wse:NotifyTo/wsa:ReferenceParameters
     element; per WS-Addressing 
-    <bibref ref="WSAddressing"/>, the event source MUST include
+    <bibref ref="AddrCore"/>, the event source MUST include
     each such literal SOAP header block in every notification sent to
     the endpoint addressed by
     /s:Envelope/s:Body/wse:Subscribe/wse:NotifyTo.
@@ -2401,7 +2446,7 @@
      included in the signature. Specifically, any headers identified
      in the <code>&lt;wse:NotifyTo&gt;</code> element and standard
      messaging headers, such as those from WS-Addressing 
-     <bibref ref="WSAddressing"/>, need to be signed with the
+     <bibref ref="AddrCore"/>, need to be signed with the
      body in order to "bind" the two together. For messages with empty
      bodies, the <code>&lt;s12:Body&gt;</code> element should be
      signed so content cannot be added in transit.
@@ -2624,12 +2669,12 @@
       , M. Gudgin, et al, June 2003.
     </bibl>
 
-    <bibl key="WS-Addressing" id="WSAddressing"
-     href="http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/">
+    <bibl key="WS-Addressing" id="AddrCore"
+     href="http://www.w3.org/2005/08/addressing/">
       <titleref>
-       Web Services Addressing (WS-Addressing)
+       W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
       </titleref>
-      , D. Box et al, August 2004.
+      , May 2006.
     </bibl>
 
     <bibl key="WS-MetadataExchange" id="MEX"
@@ -3339,6 +3384,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6687">6687</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/03/23 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Received on Monday, 23 March 2009 19:38:47 UTC