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

WWW/2002/ws/ra/edcopies wsfrag.html,1.5,1.6 wsfrag.xml,1.6,1.7

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 18 Aug 2009 21:45:57 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MdWVB-0008Ii-TT@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv31814

Modified Files:
	wsfrag.html wsfrag.xml 
Log Message:
7197
Note that since some of the text from wsrt was recently moved
into this spec I grabbed the RFC2119 changes that we approved for
RT and applied them to this spec as well.


Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- wsfrag.html	18 Aug 2009 20:54:31 -0000	1.5
+++ wsfrag.html	18 Aug 2009 21:45:55 -0000	1.6
@@ -198,8 +198,8 @@
      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
+     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>
@@ -665,13 +665,13 @@
     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.
+    element which might 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 
+    and the only valid operand which can 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>
@@ -702,13 +702,13 @@
     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.
+    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
+    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
@@ -718,8 +718,8 @@
     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:
+    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. 
@@ -771,7 +771,7 @@
     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
+    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
@@ -829,7 +829,7 @@
     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;
+    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">
@@ -956,7 +956,7 @@
       (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
+    <a href="#XmlSchemaPart2">[XML Schema, Part 2]</a> description for this specification can 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.
@@ -971,7 +971,7 @@
 &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:
+    for this specification can 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.
@@ -985,7 +985,8 @@
  
 &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/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">
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</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=7197">7197</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: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- wsfrag.xml	18 Aug 2009 21:10:01 -0000	1.6
+++ wsfrag.xml	18 Aug 2009 21:45:55 -0000	1.7
@@ -62,7 +62,7 @@
    <p>This is the First Public Working Draft.</p>
    <p>
     Publication as a Working Draft does not imply endorsement by the
-    W3C Membership. This is a draft document and may be updated, replaced
+    W3C Membership. This is a draft document and can be updated, replaced
     or obsoleted by other documents at any time. It is inappropriate to
     cite this document as other than work in progress.
    </p>
@@ -1189,7 +1189,7 @@
     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.
+    element which might contain the resource.
    </p>
    
    <p>
@@ -1199,7 +1199,7 @@
    
    <p>
     In view of this, the / operator selects the containing root,
-    and the only valid operand which may follow it is the outermost element 
+    and the only valid operand which can follow it is the outermost element 
     of the resource:
    </p>
     
@@ -1266,7 +1266,7 @@
     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.
+    names MUST be used.
    </p>
     
    <p>
@@ -1276,7 +1276,7 @@
    </p>
     
    <p>
-    The text() NodeTest may be applied as a final token to the
+    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
@@ -1298,8 +1298,8 @@
    </example>
    
    <p>
-    If accessed, attributes must be the final token in the path
-    and they may be namespace-qualified or unqualified names, as required:
+    If accessed, attributes MUST be the final token in the path
+    and they MAY be namespace-qualified or unqualified names, as required:
    </p>
    
    <example>
@@ -1404,7 +1404,7 @@
    </p>
     
    <p>
-    Note that the expression may evaluate to one of four
+    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
@@ -1529,7 +1529,7 @@
    </p>
     
    <p>
-    An XPath 1.0 expression may evaluate to multiple nodes;
+    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>
@@ -1783,7 +1783,7 @@
 
    <p>
     A normative copy of the XML Schema <bibref ref='XmlSchemaPart1'/>,
-    <bibref ref='XmlSchemaPart2'/> description for this specification may be
+    <bibref ref='XmlSchemaPart2'/> description for this specification can be
     retrieved from the following address:
    </p>
     
@@ -1812,7 +1812,7 @@
    <head>WSDL</head>
    <p>
     A normative copy of the WSDL <bibref ref="Wsdl11"/> description
-    for this specification may be retrieved from the following address:
+    for this specification can be retrieved from the following address:
    </p>
    <example>
     <eg><loc href="http://www.w3.org/2009/02/ws-fra/fragment.wsdl">http://www.w3.org/2009/02/ws-fra/fragment.wsdl</loc></eg>
@@ -1857,6 +1857,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</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=7197">7197</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Tuesday, 18 August 2009 21:46:07 GMT

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