W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > August 2009

WWW/2002/ws/ra/edcopies wsenum.html,1.48,1.49 wsenum.xml,1.39,1.40 wseventing.html,1.71,1.72 wseventing.xml,1.62,1.63 wsfrag.html,1.4,1.5 wsfrag.xml,1.4,1.5 wsmex.html,1.47,1.48 wsmex.xml,1.36,1.37 wsrt.html,1.40,1.41 wsrt.xml,1.29,1.30 wst.html,1.49,1.50 wst.xml,1.45,1.46

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 18 Aug 2009 20:54:33 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MdVhR-0007Ab-Fz@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv27469

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
	wsfrag.html wsfrag.xml wsmex.html wsmex.xml wsrt.html wsrt.xml 
	wst.html wst.xml 
Log Message:
7206


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -d -r1.45 -r1.46
--- wst.xml	18 Aug 2009 19:19:48 -0000	1.45
+++ wst.xml	18 Aug 2009 20:54:31 -0000	1.46
@@ -414,6 +414,16 @@
     </p>
 
     <p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p>
+
+    <p>
      Extension elements and attributes MUST NOT use the Web Services
      Transfer namespace URI.
     </p>
@@ -2001,6 +2011,13 @@
             <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</loc>
           </td>
         </tr>
+        <tr>
+          <td> 2009/08/18 </td>
+          <td> DD </td>
+          <td> Added resolution of issue 
+            <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</loc>
+          </td>
+        </tr>
       </tbody>
      </table>
     </div1>

Index: wsrt.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -d -r1.29 -r1.30
--- wsrt.xml	5 Aug 2009 21:51:38 -0000	1.29
+++ wsrt.xml	18 Aug 2009 20:54:31 -0000	1.30
@@ -651,6 +651,16 @@
     </p>
 
     <p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p>
+
+    <p>
      Extension elements and attributes MUST NOT use the Web Services
      Resource Transfer namespace URI.
     </p>
@@ -3760,6 +3770,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/08/18 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -d -r1.71 -r1.72
--- wseventing.html	5 Aug 2009 21:46:53 -0000	1.71
+++ wseventing.html	18 Aug 2009 20:54:30 -0000	1.72
@@ -347,6 +347,14 @@
      of a corresponding SOAP Header with a soap:mustUnderstand attribute
      with the value "1".
     </p><p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p><p>
      Extension elements and attributes MUST NOT use the Web Services
      Eventing namespace URI.
     </p></div><div class="div2">
@@ -2058,4 +2066,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7136">7136</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6432">6432</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7205">7205</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7205">7205</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</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.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- wsrt.html	5 Aug 2009 21:51:38 -0000	1.40
+++ wsrt.html	18 Aug 2009 20:54:31 -0000	1.41
@@ -369,6 +369,14 @@
      of a corresponding SOAP Header with a soap:mustUnderstand attribute
      with the value "1".
     </p><p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p><p>
      Extension elements and attributes MUST NOT use the Web Services
      Resource Transfer namespace URI.
     </p></div><div class="div2">
@@ -2117,4 +2125,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a></td></tr><tr><td> 2009/04/27 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</a></td></tr><tr><td> 2009/07/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6699">6699</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- wsfrag.xml	18 Aug 2009 17:21:55 -0000	1.4
+++ wsfrag.xml	18 Aug 2009 20:54:31 -0000	1.5
@@ -418,6 +418,16 @@
     </p>
 
     <p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p>
[...1528 lines suppressed...]
+   <table border="1">
+    <tbody>
+     <tr>
+      <th> Data </th>
+      <th> Author </th>
+      <th> Description </th>
+     </tr>
+     <tr>
+      <td> 2009/08/01 </td>
+      <td> DD </td>
+      <td> Initial draft </td>
+     </tr>
+     <tr>
+      <td> 2009/08/18 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</loc>
       </td>
      </tr>
     </tbody>

Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- wsfrag.html	18 Aug 2009 17:21:55 -0000	1.4
+++ wsfrag.html	18 Aug 2009 20:54:31 -0000	1.5
@@ -53,8 +53,8 @@
 &nbsp;&nbsp;&nbsp;3.2 <a href="#Put">Put</a><br/>
 &nbsp;&nbsp;&nbsp;3.3 <a href="#Delete">Delete</a><br/>
 &nbsp;&nbsp;&nbsp;3.4 <a href="#Create">Create</a><br/>
-4 <a href="#iddiv1_1_802">Examples</a><br/>
-&nbsp;&nbsp;&nbsp;4.1 <a href="#iddiv2_1_805">Examples</a><br/>
+4 <a href="#iddiv1_1_804">Examples</a><br/>
+&nbsp;&nbsp;&nbsp;4.1 <a href="#iddiv2_1_807">Examples</a><br/>
 5 <a href="#QName">QName Expression Language</a><br/>
 &nbsp;&nbsp;&nbsp;5.1 <a href="#QName_Get">Get</a><br/>
 &nbsp;&nbsp;&nbsp;5.2 <a href="#QName_Put">Put</a><br/>
@@ -195,6 +195,14 @@
      of a corresponding SOAP Header with a soap:mustUnderstand attribute
      with the value "1".
     </p><p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p><p>
      Extension elements and attributes MUST NOT use the Web Services
      Fragment namespace URI.
     </p></div><div class="div2">
@@ -457,12 +465,12 @@
   &lt;/wst:CreateResponse&gt;</pre></div></div><p>
      There are no additional constraints beyond what WS-Transfer defines.
     </p></div></div><div class="div1">
-<h2><a name="iddiv1_1_802" id="iddiv1_1_802"/>4 Examples</h2><div class="div2">
-<h3><a name="iddiv2_1_805" id="iddiv2_1_805"/>4.1 Examples</h3><p>
-      In the following examples, and Expression Language definitions,
-      the following representation of a resource is used for
-      informational purposes:
-     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;ab:AddressBook xmlns:ab="http://example.com/address"&gt;
+<h2><a name="iddiv1_1_804" id="iddiv1_1_804"/>4 Examples</h2><div class="div2">
+<h3><a name="iddiv2_1_807" id="iddiv2_1_807"/>4.1 Examples</h3><p>
+     In the following examples, and Expression Language definitions,
+     the following representation of a resource is used for
+     informational purposes:
+    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;ab:AddressBook xmlns:ab="http://example.com/address"&gt;
   &lt;ab:owner&gt;Me&lt;/owner&gt;
   &lt;ab:size&gt;2&lt;/size&gt;
   &lt;ab:contact&gt;
@@ -505,7 +513,8 @@
     &lt;/wst:Get&gt;
   &lt;/s:Body&gt;
 &lt;/s:Envelope&gt;</pre></div></div><p>
-     The following shows the corresponding response message:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope  
+     The following shows the corresponding response message:
+    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope  
     xmlns:s="http://www.w3.org/2003/05/soap-envelope" 
     xmlns:wsa="http://www.w3.org/2005/08/addressing" 
     xmlns:ex="http://www.example.com/" &gt;
@@ -544,72 +553,72 @@
   &lt;/s:Body&gt;
 &lt;/s:Envelope&gt;</pre></div></div></div></div><div class="div1">
 <h2><a name="QName" id="QName"/>5 QName Expression Language</h2><p>
-     The QName expression language is a syntax for expressions that 
-     uses a single QName to reference the immediate children of the root 
-     element of 
-     the resource representation.  The expression MUST evaluate to zero or 
-     more elements, each including the element name, any attributes 
-     and its entire content.
-     This language can be implemented as a precise subset of the XPath language.
-    </p><p>
-     The QName language MUST be indicated by using the URI:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-fra/QName">http://www.w3.org/2009/02/ws-fra/QName</a></pre></div></div><div class="div2">
+    The QName expression language is a syntax for expressions that 
+    uses a single QName to reference the immediate children of the root 
+    element of 
+    the resource representation.  The expression MUST evaluate to zero or 
+    more elements, each including the element name, any attributes 
+    and its entire content.
+    This language can be implemented as a precise subset of the XPath language.
+   </p><p>
+    The QName language MUST be indicated by using the URI:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-fra/QName">http://www.w3.org/2009/02/ws-fra/QName</a></pre></div></div><div class="div2">
 <h3><a name="QName_Get" id="QName_Get"/>5.1 Get</h3><p>
-      When used in a Get request message, the expression identifies
-      which immediate children of the root element to return. If the
-      QName matches more than one element then all of those elements
-      are returned.  If the QName doesn't match any element then 
-      an empty Fragment element is returned.
-     </p></div><div class="div2">
+     When used in a Get request message, the expression identifies
+     which immediate children of the root element to return. If the
+     QName matches more than one element then all of those elements
+     are returned.  If the QName doesn't match any element then 
+     an empty Fragment element is returned.
+    </p></div><div class="div2">
 <h3><a name="QName_Put" id="QName_Put"/>5.2 Put</h3><p>
-      When used in a Put request message. the expression identifies
-      which immediate children of the root element to replace. If the
-      QName matches more than one element then all of those elements
-      are deleted and the children Fragment elements are inserted in their
-      place.
-     </p></div><div class="div2">
+     When used in a Put request message. the expression identifies
+     which immediate children of the root element to replace. If the
+     QName matches more than one element then all of those elements
+     are deleted and the children Fragment elements are inserted in their
+     place.
+    </p></div><div class="div2">
 <h3><a name="QName_Delete" id="QName_Delete"/>5.3 Delete</h3><p>
-      When used in a Delete request message. the expression identifies
-      which immediate children of the root element to remove. If the
-      QName matches more than one element then all of those elements
-      are deleted.  If the QName doesn't match any element then this
-      operation will have no impact on the resource.
-     </p></div><div class="div2">
+     When used in a Delete request message. the expression identifies
+     which immediate children of the root element to remove. If the
+     QName matches more than one element then all of those elements
+     are deleted.  If the QName doesn't match any element then this
+     operation will have no impact on the resource.
+    </p></div><div class="div2">
 <h3><a name="QName_Create" id="QName_Create"/>5.4 Create</h3><p>
-      When used in a Create request message. the children Fragment elements
-      are inserted as children of the root element. If the expression
-      identifies an existing element then the new elements are inserted
-      after them.
-     </p></div></div><div class="div1">
+     When used in a Create request message. the children Fragment elements
+     are inserted as children of the root element. If the expression
+     identifies an existing element then the new elements are inserted
+     after them.
+    </p></div></div><div class="div1">
 <h2><a name="XPathL1" id="XPathL1"/>6 XPath Level 1 Expression Language</h2><p>
-     The XPath Level 1 expression language uses an XPath to
-     reference specific fragments of the resource representation. The XPath is
-     logically applied to the XML representation of the resource and the 
-     resulting
-     node-set is the resource fragment which is the subject of the message
-     containing the expression. 
-     This language is useful for resources with limited XPath processing
-     capability which do not need to support returning values computed from
-     their resource representation.
-    </p><p>
-     XPath Level 1 is a subset of the abbreviated relative syntax
-     of XPath 1.0, and is used to identify or select a node within a resource
-     representation or fragment. It is identified by the following URI:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/02/ws-fra/XPath-Level-1</pre></div></div><p>
-     An XPath Level 1 expression is an expression whose context is:
-    </p><ul><li><p>
-       Context Node: the root element of the XML representation of the resource
-      </p></li><li><p> Context Position: 1 </p></li><li><p> Context Size: 1 </p></li><li><p> Variable Binding: None </p></li><li><p> Node Tests: NameTest and the text NodeType </p></li><li><p> Function Libraries: None </p></li><li><p>
-       Namespace Declarations: Any namespace declarations in-scope where the
-       XPath expression appears
-      </p></li></ul><p>
-     An implementation that uses the XPath Level 1 language MUST support the
-     expressions whose syntax is described by the following BNF. It MAY
-     support additional expressions defined by XPath 1.0.
-     The following XPath Level 1 grammar is LL(1), and the
-     nonterminal productions are in angle brackets. Terminal symbols are
-     either literals, or in UPPERCASE:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;xpath&gt; ::=  &lt;context&gt; &lt;node_sequence&gt;;
+    The XPath Level 1 expression language uses an XPath to
+    reference specific fragments of the resource representation. The XPath is
+    logically applied to the XML representation of the resource and the 
+    resulting
+    node-set is the resource fragment which is the subject of the message
+    containing the expression. 
+    This language is useful for resources with limited XPath processing
+    capability which do not need to support returning values computed from
+    their resource representation.
+   </p><p>
+    XPath Level 1 is a subset of the abbreviated relative syntax
+    of XPath 1.0, and is used to identify or select a node within a resource
+    representation or fragment. It is identified by the following URI:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/02/ws-fra/XPath-Level-1</pre></div></div><p>
+    An XPath Level 1 expression is an expression whose context is:
+   </p><ul><li><p>
+      Context Node: the root element of the XML representation of the resource
+     </p></li><li><p> Context Position: 1 </p></li><li><p> Context Size: 1 </p></li><li><p> Variable Binding: None </p></li><li><p> Node Tests: NameTest and the text NodeType </p></li><li><p> Function Libraries: None </p></li><li><p>
+      Namespace Declarations: Any namespace declarations in-scope where the
+      XPath expression appears
+     </p></li></ul><p>
+    An implementation that uses the XPath Level 1 language MUST support the
+    expressions whose syntax is described by the following BNF. It MAY
+    support additional expressions defined by XPath 1.0.
+    The following XPath Level 1 grammar is LL(1), and the
+    nonterminal productions are in angle brackets. Terminal symbols are
+    either literals, or in UPPERCASE:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;xpath&gt; ::=  &lt;context&gt; &lt;node_sequence&gt;;
 (02)
 (03) &lt;context&gt; ::= '/' | &lt;&gt;;
 (04)
@@ -632,19 +641,19 @@
 (21) &lt;text_function&gt;  ::= "text()" ;
 (22) &lt;array_location&gt; ::= NONZERO_DECIMAL_UNSIGNED_INTEGER;
 (23) &lt;name&gt;           ::= XML_TOKEN;</pre></div></div><p>
-     The terminal tokens which require further lexical
-     specification are NONZERO_DECIMAL_UNSIGNED_INTEGER, whose values are in the
-     subrange (1...4294967295), and XML_TOKEN whose values are equivalent to 
-     those for the XML Schema type <em>xs:token</em>. This grammar 
-     is small enough
-     that it can be easily implemented in resource-constrained implementations.
-    </p><p>
-     The following comments on the grammar will clarify certain
-     constructs within the BNF.
-    </p><p>
-     Most of the examples assume the following XML sample acting
-     as a "resource" document:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;a&gt;
+    The terminal tokens which require further lexical
+    specification are NONZERO_DECIMAL_UNSIGNED_INTEGER, whose values are in the
+    subrange (1...4294967295), and XML_TOKEN whose values are equivalent to 
+    those for the XML Schema type <em>xs:token</em>. This grammar 
+    is small enough
+    that it can be easily implemented in resource-constrained implementations.
+   </p><p>
+    The following comments on the grammar will clarify certain
+    constructs within the BNF.
+   </p><p>
+    Most of the examples assume the following XML sample acting
+    as a "resource" document:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;a&gt;
 (02)   &lt;b&gt;
 (03)     &lt;c d="30"&gt; 20 &lt;/c&gt;
 (04)   &lt;/b&gt;
@@ -653,190 +662,192 @@
 (07)     &lt;f/&gt;
 (08)   &lt;/e&gt;
 (09) &lt;/a&gt;</pre></div></div><p>
-     The context and document root node need
-     clarification. XPath Level 1 assumes that the root is the root
-     node of the resource document, not the SOAP envelope or any other wrapper
-     element which may contain the resource.
-    </p><p>
-     Further, the default context is the root element and the
-     context position is 1.
-    </p><p>
-     In view of this, the / operator selects the containing root,
-     and the only valid operand which may follow it is the outermost element 
-     of the resource:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a</pre></div></div><p>The following paths are equivalent:</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b
+    The context and document root node need
+    clarification. XPath Level 1 assumes that the root is the root
+    node of the resource document, not the SOAP envelope or any other wrapper
+    element which may contain the resource.
+   </p><p>
+    Further, the default context is the root element and the
+    context position is 1.
+   </p><p>
+    In view of this, the / operator selects the containing root,
+    and the only valid operand which may follow it is the outermost element 
+    of the resource:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a</pre></div></div><p>The following paths are equivalent:</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b
 (02) b</pre></div></div><p>
-     Note that because the context node is the root element, a
-     relative path selects a matching child element.
-    </p><p>
-     The &lt;node_sequence&gt; production provides the recursive
-     behavior for the XPath:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b/c
+    Note that because the context node is the root element, a
+    relative path selects a matching child element.
+   </p><p>
+    The &lt;node_sequence&gt; production provides the recursive
+    behavior for the XPath:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b/c
 (02) b/c</pre></div></div><p>
-     It also provides for selecting specific repeated elements
-     through the &lt;optional_collection_operator&gt; production:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/e/f[2]</pre></div></div><p>
-     The collection operator only takes unsigned nonzero values,
-     as defined above for NONZERO_DECIMAL_UNSIGNED_INTEGER. Thus, [1] is the
-     first of a repeating series of elements.
-    </p><p>
-     The &lt;qualified_name&gt; production allows the XML naming
-     tokens to be either namespace-qualified or unqualified:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /ns1:a/ns2:b/c</pre></div></div><p>
-     The namespace bindings are evaluated against any namespace
-     declarations that are in scope where the XPath appears within the SOAP
-     message.
-    </p><p>
-     NOTE: If the element name is unqualified, i.e. appears
-     without a namespace prefix, then the element name MUST be matched against a
-     matching element name in the resource document, regardless of namespace
-     bindings that are in effect, including default bindings. This allows
-     implementations to simply match element names in the majority of cases.
-     If namespace bindings are significant for all elements, then qualified 
-     names must be used.
-    </p><p>
-     The &lt;follower&gt; production allows for special-casing of
-     the final tokens of the XPath allowing it to end in either an attribute
-     or text.
-    </p><p>
-     The text() NodeTest may be applied as a final token to the
-     selected element. This NodeTest selects any text nodes that are
-     children of the selected element. If the element only contains text
-     content, the
-     return value will be a node-set containing a single text node.
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) b/c/text()</pre></div></div><p>
-     The above expression would return a node-set containing a
-     single text node with the value <em>20 </em>as its result. This text 
-     node would then be serialized into the following XML representation:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:TextNode&gt;20&lt;/wsf:TextNode&gt;</pre></div></div><p>
-     If accessed, attributes must be the final token in the path
-     and they may be namespace-qualified or unqualified names, as required:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b/c/@d</pre></div></div><p>
-     The above expression would return a node-set containing a
-     single attribute node with the value <em>d="30"</em> as its result. 
-     This attribute node would then be serialized into the following XML
-     representation:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:AttributeNode name="d"&gt;30&lt;/wsf:AttributeNode&gt;</pre></div></div><p>
-     Selection of an element returns the element and its entire
-     content. The path <em>/a/b </em>executed against the sample XML 
-     returns a
-     node-set containing a single element node which serializes directly:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;b&gt; &lt;c d="30"&gt; 20 &lt;/c&gt; &lt;/b&gt;</pre></div></div><p>
-     In the event that there is more than one node which would
-     match the XPath, the implementation SHOULD select or return the first node
-     only. This allows simple implementations to avoid the overhead of
-     checking the remainder of the resource document for a possible match.
-    </p><p>
-     Conformant implementations MAY supply additional functions
-     and capabilities, but MUST adhere to the minimum behavior described above.
-    </p><p>
-     Expressions in this language MUST NOT evaluate to more than a
-     single node. The XPath Level 1 language does not support computed values. 
-     Text and attribute nodes MUST be serialized using the same serialization 
-     as for the XPath 1.0 language.
-    </p></div><div class="div1">
+    It also provides for selecting specific repeated elements
+    through the &lt;optional_collection_operator&gt; production:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/e/f[2]</pre></div></div><p>
+    The collection operator only takes unsigned nonzero values,
+    as defined above for NONZERO_DECIMAL_UNSIGNED_INTEGER. Thus, [1] is the
+    first of a repeating series of elements.
+   </p><p>
+    The &lt;qualified_name&gt; production allows the XML naming
+    tokens to be either namespace-qualified or unqualified:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /ns1:a/ns2:b/c</pre></div></div><p>
+    The namespace bindings are evaluated against any namespace
+    declarations that are in scope where the XPath appears within the SOAP
+    message.
+   </p><p>
+    NOTE: If the element name is unqualified, i.e. appears
+    without a namespace prefix, then the element name MUST be matched against a
+    matching element name in the resource document, regardless of namespace
+    bindings that are in effect, including default bindings. This allows
+    implementations to simply match element names in the majority of cases.
+    If namespace bindings are significant for all elements, then qualified 
+    names must be used.
+   </p><p>
+    The &lt;follower&gt; production allows for special-casing of
+    the final tokens of the XPath allowing it to end in either an attribute
+    or text.
+   </p><p>
+    The text() NodeTest may be applied as a final token to the
+    selected element. This NodeTest selects any text nodes that are
+    children of the selected element. If the element only contains text
+    content, the
+    return value will be a node-set containing a single text node.
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) b/c/text()</pre></div></div><p>
+    The above expression would return a node-set containing a
+    single text node with the value <em>20 </em>as its result. This text 
+    node would then be serialized into the following XML representation:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:TextNode&gt;20&lt;/wsf:TextNode&gt;</pre></div></div><p>
+    If accessed, attributes must be the final token in the path
+    and they may be namespace-qualified or unqualified names, as required:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) /a/b/c/@d</pre></div></div><p>
+    The above expression would return a node-set containing a
+    single attribute node with the value <em>d="30"</em> as its result. 
+    This attribute node would then be serialized into the following XML
+    representation:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:AttributeNode name="d"&gt;30&lt;/wsf:AttributeNode&gt;</pre></div></div><p>
+    Selection of an element returns the element and its entire
+    content. The path <em>/a/b </em>executed against the sample XML 
+    returns a
+    node-set containing a single element node which serializes directly:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;b&gt; &lt;c d="30"&gt; 20 &lt;/c&gt; &lt;/b&gt;</pre></div></div><p>
+    In the event that there is more than one node which would
+    match the XPath, the implementation SHOULD select or return the first node
+    only. This allows simple implementations to avoid the overhead of
+    checking the remainder of the resource document for a possible match.
+   </p><p>
+    Conformant implementations MAY supply additional functions
+    and capabilities, but MUST adhere to the minimum behavior described above.
+   </p><p>
+    Expressions in this language MUST NOT evaluate to more than a
+    single node. The XPath Level 1 language does not support computed values. 
+    Text and attribute nodes MUST be serialized using the same serialization 
+    as for the XPath 1.0 language.
+   </p></div><div class="div1">
 <h2><a name="XPath10" id="XPath10"/>7 XPath 1.0 Expression Language</h2><p>
-     The XPath 1.0 expression language uses an XPath to reference specific
-     fragments of the resource representation. The XPath is logically 
-     applied to the XML representation of the resource and the result of 
-     the XPath is returned as the value for that expression. The XPath 1.0 
-     language supports a
-     wider set of XPath function libraries than the XPath Level 1 language.
-     This language is
-     useful for resources with full XPath processing capability or which 
-     need to support returning values computed from their resource 
-     representation.
-    </p><p>
-     An XPath 1.0 expression is an expression whose context is:
-    </p><ul><li><p>
-       Context Node: the root element of the XML representation of the resource
-      </p></li><li><p>Context Position: 1</p></li><li><p>Context Size: 1</p></li><li><p>Variable Binding: None</p></li><li><p>Function Libraries: Core function library</p></li><li><p>
-       Namespace Declarations: Any namespace declarations in-scope where 
-       the XPath expression appears
-      </p></li></ul><p>
-     The XPath 1.0 language can
-     define references to any element, attribute or value in the resource
-     representation and can also be used to compute values from the resource
-     representation.
-    </p><p>The XPath 1.0 language MUST be indicated by using the URI:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-fra/XPath">http://www.w3.org/2009/02/ws-fra/XPath</a></pre></div></div><p>
-     Implementations that support the full XPath 1.0 language MUST
-     support the XPath Level 1 language.
-    </p><p>
-     Note that the expression may evaluate to one of four
-     possible types: a node-set, a Boolean, a number or a string. The 
-     latter three types are the results of evaluating a computed expression. 
-     They are serialized
-     by performing the following conversion and then wrapping the result in 
-     the wsf:Value element:
-    </p><ul><li><p>Boolean - converted to an xs:boolean</p></li><li><p>string - convert to an xs:string</p></li><li><p>number - convert to an xs:double</p></li></ul><p>
-     A node-set is zero or more elements, attributes or text
-     values of elements. A node-set is serialized into XML by 
-     concatenating each
-     node and enclosing it in the wsf:Value wrapper XML element for which 
-     schema
-     validation is suppressed. Element nodes in a node-set are serialized 
-     directly
-     into their XML representation. For attributes and text nodes in the 
-     node-set,
-     a wrapper element is used to enclose these values to distinguish them from
-     other such nodes in the serialized result.
-    </p><p>
-     Attribute nodes in XPath are represented in the following form:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>name="value"</pre></div></div><p>
-     Serialization of an attribute node separates the name from
-     the value using the following element:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:AttributeNode name="<em>attribute name</em>"&gt;
+    The XPath 1.0 expression language uses an XPath to reference specific
+    fragments of the resource representation. The XPath is logically 
+    applied to the XML representation of the resource and the result of 
+    the XPath is returned as the value for that expression. The XPath 1.0 
+    language supports a
+    wider set of XPath function libraries than the XPath Level 1 language.
+    This language is
+    useful for resources with full XPath processing capability or which 
+    need to support returning values computed from their resource 
+    representation.
+   </p><p>
+    An XPath 1.0 expression is an expression whose context is:
+   </p><ul><li><p>
+      Context Node: the root element of the XML representation of the resource
+     </p></li><li><p>Context Position: 1</p></li><li><p>Context Size: 1</p></li><li><p>Variable Binding: None</p></li><li><p>Function Libraries: Core function library</p></li><li><p>
+      Namespace Declarations: Any namespace declarations in-scope where 
+      the XPath expression appears
+     </p></li></ul><p>
+    The XPath 1.0 language can
+    define references to any element, attribute or value in the resource
+    representation and can also be used to compute values from the resource
+    representation.
+   </p><p>The XPath 1.0 language MUST be indicated by using the URI:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-fra/XPath">http://www.w3.org/2009/02/ws-fra/XPath</a></pre></div></div><p>
+    Implementations that support the full XPath 1.0 language MUST
+    support the XPath Level 1 language.
+   </p><p>
+    Note that the expression may evaluate to one of four
+    possible types: a node-set, a Boolean, a number or a string. The 
+    latter three types are the results of evaluating a computed expression. 
+    They are serialized
+    by performing the following conversion and then wrapping the result in 
+    the wsf:Value element:
+   </p><ul><li><p>Boolean - converted to an xs:boolean</p></li><li><p>string - convert to an xs:string</p></li><li><p>number - convert to an xs:double</p></li></ul><p>
+    A node-set is zero or more elements, attributes or text
+    values of elements. A node-set is serialized into XML by 
+    concatenating each
+    node and enclosing it in the wsf:Value wrapper XML element for which 
+    schema
+    validation is suppressed. Element nodes in a node-set are serialized 
+    directly
+    into their XML representation. For attributes and text nodes in the 
+    node-set,
+    a wrapper element is used to enclose these values to distinguish them from
+    other such nodes in the serialized result.
+   </p><p>
+    Attribute nodes in XPath are represented in the following form:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>name="value"</pre></div></div><p>
+    Serialization of an attribute node separates the name from
+    the value using the following element:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:AttributeNode name="<em>attribute name</em>"&gt;
 (02)   <em>attribute value</em>
 (03) &lt;/wsf:AttributeNode&gt;</pre></div></div><p>
-     The following describes additional constraints on the outline 
-     listed above:
-    </p><dl><dt class="label"> wsf:AttributeNode </dt><dd><p>
-        This element is used to serialize an attribute node in a
-        node-set and MUST contain the value portion of the attribute node.
-       </p></dd><dt class="label"> wsf:AttributeNode/@name </dt><dd><p>
-        This attribute MUST be the name portion of the attribute node.
-       </p></dd></dl><p>
-     Text nodes are serialized in the following form:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:TextNode&gt;
+    The following describes additional constraints on the outline 
+    listed above:
+   </p><dl><dt class="label"> wsf:AttributeNode </dt><dd><p>
+       This element is used to serialize an attribute node in a
+       node-set and MUST contain the value portion of the attribute node.
+      </p></dd><dt class="label"> wsf:AttributeNode/@name </dt><dd><p>
+       This attribute MUST be the name portion of the attribute node.
+      </p></dd></dl><p>
+    Text nodes are serialized in the following form:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:TextNode&gt;
 (02)   <em>text value</em>
-(03) &lt;/wsf:TextNode&gt;</pre></div></div><p>The following describes additional constraints on the
-    outline listed above:</p><p>wsf:TextNode</p><p>
-     This element is used to serialize a text node in a node-set
-     and MUST contain the text value.
-    </p><p>Given the following XML as an example document.</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;a xmlns="example"&gt;
+(03) &lt;/wsf:TextNode&gt;</pre></div></div><p>
+    The following describes additional constraints on the
+    outline listed above:
+   </p><p>wsf:TextNode</p><p>
+    This element is used to serialize a text node in a node-set
+    and MUST contain the text value.
+   </p><p>Given the following XML as an example document.</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;a xmlns="example"&gt;
 (02)   &lt;b&gt;1&lt;/b&gt;
 (03)   &lt;c x="y"&gt;2&lt;/c&gt;
 (04) &lt;/a&gt;</pre></div></div><p>
-     The result of the XPath "/a/b | /a/b/text() | /a/c/@x" would
-     be serialized as the following:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:Value&gt;
+    The result of the XPath "/a/b | /a/b/text() | /a/c/@x" would
+    be serialized as the following:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wsf:Value&gt;
 (02)   &lt;b&gt;1&lt;/b&gt;
 (03)   &lt;wsf:TextNode&gt;1&lt;/wsf:TextNode&gt;
 (04)   &lt;wsf:AttributeNode name="x"&gt;y&lt;/wsf:AttributeNode&gt;
 (05) &lt;/wsf:Value&gt;</pre></div></div><p>The nodes in the node-set MAY be serialized in any order.</p><p>
-     The WS-Fragment global element definition wsf:NodeSet can also be
-     used as the wrapper element when serializing these node-sets outside of
-     a WS-RT result.
-    </p><p>
-     An XPath 1.0 expression may evaluate to multiple nodes;
-     because of this the XPath 1.0 language MUST NOT be used with a "Put" or
-     "Create" operation.
-    </p></div><div class="div1">
+    The WS-Fragment global element definition wsf:NodeSet can also be
+    used as the wrapper element when serializing these node-sets outside of
+    a WS-RT result.
+   </p><p>
+    An XPath 1.0 expression may evaluate to multiple nodes;
+    because of this the XPath 1.0 language MUST NOT be used with a "Put" or
+    "Create" operation.
+   </p></div><div class="div1">
 <h2><a name="Faults" id="Faults"/>8 Faults</h2><p>
-     All fault messages defined in this specification MUST be sent
-     according to the rules and usage described in
-     <a href="#WSABinding">[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 MUST be used for faults
-     defined in this specification:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/02/ws-fra/fault</pre></div></div><p>
-     The definitions of faults in this section use the following properties:
-    </p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element 
-     is defined for the fault.<br/></p><p>
-     For SOAP 1.2, the <b>[Code]</b> property MUST be either
-     "Sender" or "Receiver". These properties are serialized
-     into text XML as follows:
-    </p><a name="soapver" id="soapver"/><table border="1"><tbody><tr><th> SOAP Version </th><th> Sender </th><th> Receiver </th></tr><tr><td> SOAP 1.2 </td><td> s12:Sender </td><td> s12:Receiver </td></tr></tbody></table><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
+    All fault messages defined in this specification MUST be sent
+    according to the rules and usage described in
+    <a href="#WSABinding">[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 MUST be used for faults
+    defined in this specification:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/02/ws-fra/fault</pre></div></div><p>
+    The definitions of faults in this section use the following properties:
+   </p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element 
+    is defined for the fault.<br/></p><p>
+    For SOAP 1.2, the <b>[Code]</b> property MUST be either
+    "Sender" or "Receiver". These properties are serialized
+    into text XML as follows:
+   </p><a name="soapver" id="soapver"/><table border="1"><tbody><tr><th> SOAP Version </th><th> Sender </th><th> Receiver </th></tr><tr><td> SOAP 1.2 </td><td> s12:Sender </td><td> s12:Receiver </td></tr></tbody></table><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
    &lt;s12:Header&gt;
      &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
      &lt;!-- Headers elided for brevity. --&gt;
@@ -871,85 +882,85 @@
    &lt;/s11:Body&gt;
  &lt;/s11:Envelope&gt;</pre></div></div><div class="div2">
 <h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"/>8.1 UnsupportedLanguage</h3><p>
-      This fault is generated when a service detects an unknown Language 
-      URI in a request message. 
-     </p><a name="Table3" id="Table3"/><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:UnknownLanguage</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
-         The specified Language URI is not known.
-        </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown URI if specified</em></td></tr></tbody></table></div></div><div class="div1">
+     This fault is generated when a service detects an unknown Language 
+     URI in a request message. 
+    </p><a name="Table3" id="Table3"/><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:UnknownLanguage</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
+        The specified Language URI is not known.
+       </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown URI if specified</em></td></tr></tbody></table></div></div><div class="div1">
 <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.),
-      Asir Vedamuthu (Microsoft Corp.),
-      Bob Freund (Hitachi, Ltd.),
-      Doug Davis (IBM),
-      Fred Maciel (Hitachi, Ltd.),
-      Geoff Bullen (Microsoft Corp.),
-      Gilbert Pilz (Oracle Corp.),
-      Greg Carpenter (Microsoft Corp.),
-      Jeff Mischkinsky (Oracle Corp.),
-      Katy Warr (IBM),
-      Li Li (Avaya Communications),
-      Mark Little (Red Hat),
-      Prasad Yendluri (Software AG),
-      Sreedhara Narayanaswamy (CA),
-      Sumeet Vij (Software AG),
-      Vikas Varma (Software AG),
-      Wu Chou (Avaya Communications),
-      Yves Lafon (W3C)
-    </p></div><div class="div1">
+    This specification has been developed as a result of joint
+    work with many individuals and teams, including: 
+     Ashok Malhotra (Oracle Corp.),
+     Asir Vedamuthu (Microsoft Corp.),
+     Bob Freund (Hitachi, Ltd.),
+     Doug Davis (IBM),
+     Fred Maciel (Hitachi, Ltd.),
+     Geoff Bullen (Microsoft Corp.),
+     Gilbert Pilz (Oracle Corp.),
+     Greg Carpenter (Microsoft Corp.),
+     Jeff Mischkinsky (Oracle Corp.),
+     Katy Warr (IBM),
+     Li Li (Avaya Communications),
+     Mark Little (Red Hat),
+     Prasad Yendluri (Software AG),
+     Sreedhara Narayanaswamy (CA),
+     Sumeet Vij (Software AG),
+     Vikas Varma (Software AG),
+     Wu Chou (Avaya Communications),
+     Yves Lafon (W3C)
+   </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>10 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"/>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"/>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="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="WSABinding" id="WSABinding"/>WS-Addressing 1.0 SOAP Binding</dt><dd><a href="http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509"><cite>
-       W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
-      </cite></a>
-      , May 2006.
-       (See http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509.)</dd><dt class="label"><a name="WsPolicy" id="WsPolicy"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
-       W3C Recommendation, "Web Services Policy 1.5 - Framework"
-      </cite></a>
-      , September 2007.
-       (See http://www.w3.org/TR/ws-policy/.)</dd><dt class="label"><a name="WsTransfer" id="WsTransfer"/>WS-Transfer</dt><dd><a href="http://www.w3.org/2009/02/ws-tra"><cite>
-       W3C Working Group Draft, "Web Services Transfer"
-      </cite></a>
-      , July 2009.
-       (See http://www.w3.org/2009/02/ws-tra.)</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"/>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"/>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"/>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">
+      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"/>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"/>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="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="WSABinding" id="WSABinding"/>WS-Addressing 1.0 SOAP Binding</dt><dd><a href="http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509"><cite>
+      W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
+     </cite></a>
+     , May 2006.
+      (See http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509.)</dd><dt class="label"><a name="WsPolicy" id="WsPolicy"/>WS-Policy</dt><dd><a href="http://www.w3.org/TR/ws-policy/"><cite>
+      W3C Recommendation, "Web Services Policy 1.5 - Framework"
+     </cite></a>
+     , September 2007.
+      (See http://www.w3.org/TR/ws-policy/.)</dd><dt class="label"><a name="WsTransfer" id="WsTransfer"/>WS-Transfer</dt><dd><a href="http://www.w3.org/2009/02/ws-tra"><cite>
+      W3C Working Group Draft, "Web Services Transfer"
+     </cite></a>
+     , July 2009.
+      (See http://www.w3.org/2009/02/ws-tra.)</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"/>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"/>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"/>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 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:
-    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-fra/fragment.xsd">http://www.w3.org/2009/02/ws-fra/fragment.xsd</a></pre></div></div><p>
-     A non-normative copy of the XML schema is listed below for convenience.
-    </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;xs:schema 
+    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:
+   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-fra/fragment.xsd">http://www.w3.org/2009/02/ws-fra/fragment.xsd</a></pre></div></div><p>
+    A non-normative copy of the XML schema is listed below for convenience.
+   </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;xs:schema 
   targetNamespace="http://www.w3.org/2009/02/ws-fra"
   xmlns:tns="http://www.w3.org/2009/02/ws-fra"
   xmlns:xs="http://www.w3.org/2001/XMLSchema"
@@ -959,22 +970,22 @@
  
 &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"/>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-fra/fragment.wsdl">http://www.w3.org/2009/02/ws-fra/fragment.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-fra" 
-    xmlns:tns="http://www.w3.org/2009/02/ws-fra" 
-    xmlns:wsa="http://www.w3.org/2005/08/addressing"
-    xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"
-    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
-    xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt;
+    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-fra/fragment.wsdl">http://www.w3.org/2009/02/ws-fra/fragment.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-fra" 
+ xmlns:tns="http://www.w3.org/2009/02/ws-fra" 
+ xmlns:wsa="http://www.w3.org/2005/08/addressing"
+ xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"
+ xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" 
+ xmlns:xs="http://www.w3.org/2001/XMLSchema"&gt;
  
 &lt;/wsdl:definitions&gt;</pre></div></div></div><div class="div1">
-<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=xxxx">xxxx</a></td></tr></tbody></table></div><div class="div1">
+<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/08/01 </td><td> DD </td><td> Initial draft </td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</a></td></tr></tbody></table></div><div class="div1">
 <h2><a name="Questions" id="Questions"/>D Open Questions and Actions</h2><p>
     Ram - If the expression resolves to a non-existent node should it fault
       or do nothing?

Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- wst.html	18 Aug 2009 19:19:48 -0000	1.49
+++ wst.html	18 Aug 2009 20:54:31 -0000	1.50
@@ -200,6 +200,14 @@
      of a corresponding SOAP Header with a soap:mustUnderstand attribute
      with the value "1".
     </p><p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p><p>
      Extension elements and attributes MUST NOT use the Web Services
      Transfer namespace URI.
     </p></div><div class="div2">
@@ -1135,4 +1143,5 @@
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7014">7014</a>,
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6975">6975</a>,
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6413">6413</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue 
-            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
+            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</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.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- wsmex.xml	6 Aug 2009 17:51:44 -0000	1.36
+++ wsmex.xml	18 Aug 2009 20:54:31 -0000	1.37
@@ -672,6 +672,16 @@
     </p>
 
     <p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p>
+
+    <p>
      Extension elements and attributes MUST NOT use the Web Services
      Metadata Exchange namespace URI.
     </p>
@@ -2043,6 +2053,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6679">6679</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/08/18 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -d -r1.48 -r1.49
--- wsenum.html	18 Aug 2009 19:11:59 -0000	1.48
+++ wsenum.html	18 Aug 2009 20:54:30 -0000	1.49
@@ -211,6 +211,14 @@
       of a corresponding SOAP Header with a soap:mustUnderstand attribute 
       with the value "1".
      </p><p>
+      In cases where it is either desirable or necessary for the receiver 
+      of a request that has been extended to indicate that it has 
+      recognized and accepted the semantics associated with that extension, 
+      it is recommended that the receiver add a corresponding extension 
+      to the response message.  The definition of an extension should clearly 
+      specify how the extension that appears in the response correlates 
+      with that in the corresponding request.
+     </p><p>
       Extension elements and attributes MUST NOT use the Web Services 
       Enumeration namespace URI.
      </p></div><div class="div2">
@@ -1673,4 +1681,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6916">6916</a></td></tr><tr><td> 2009/06/11 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6956">6956</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a></td></tr><tr><td> 2009/08/06 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7192">7192</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7192">7192</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</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.39
retrieving revision 1.40
diff -u -d -r1.39 -r1.40
--- wsenum.xml	18 Aug 2009 19:11:59 -0000	1.39
+++ wsenum.xml	18 Aug 2009 20:54:30 -0000	1.40
@@ -331,6 +331,16 @@
      </p>
 
      <p>
+      In cases where it is either desirable or necessary for the receiver 
+      of a request that has been extended to indicate that it has 
+      recognized and accepted the semantics associated with that extension, 
+      it is recommended that the receiver add a corresponding extension 
+      to the response message.  The definition of an extension should clearly 
+      specify how the extension that appears in the response correlates 
+      with that in the corresponding request.
+     </p>
+
+     <p>
       Extension elements and attributes MUST NOT use the Web Services 
       Enumeration namespace URI.
      </p>
@@ -2936,6 +2946,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7192">7192</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/08/18 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -d -r1.47 -r1.48
--- wsmex.html	6 Aug 2009 17:51:44 -0000	1.47
+++ wsmex.html	18 Aug 2009 20:54:31 -0000	1.48
@@ -407,6 +407,14 @@
      of a corresponding SOAP Header with a soap:mustUnderstand attribute
      with the value "1".
     </p><p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p><p>
      Extension elements and attributes MUST NOT use the Web Services
      Metadata Exchange namespace URI.
     </p></div><div class="div2">
@@ -1151,4 +1159,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6719">6719</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6720">6720</a></td></tr><tr><td> 2009/08/06 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7194">7194</a></td></tr><tr><td> 2009/08/06 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6679">6679</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6679">6679</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</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.62
retrieving revision 1.63
diff -u -d -r1.62 -r1.63
--- wseventing.xml	5 Aug 2009 21:46:53 -0000	1.62
+++ wseventing.xml	18 Aug 2009 20:54:30 -0000	1.63
@@ -544,6 +544,16 @@
     </p>
 
     <p>
+     In cases where it is either desirable or necessary for the receiver
+     of a request that has been extended to indicate that it has
+     recognized and accepted the semantics associated with that extension,
+     it is recommended that the receiver add a corresponding extension
+     to the response message.  The definition of an extension should clearly
+     specify how the extension that appears in the response correlates
+     with that in the corresponding request.
+    </p>
+
+    <p>
      Extension elements and attributes MUST NOT use the Web Services
      Eventing namespace URI.
     </p>
@@ -3668,6 +3678,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7205">7205</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/08/18 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Tuesday, 18 August 2009 21:00:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 18 August 2009 21:00:53 GMT