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

WWW/2002/ws/ra/edcopies wsfrag.html,1.68,1.69 wsfrag.xml,1.66,1.67

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 12 May 2010 04:51:49 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1OC3vB-0006m0-AW@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv25944

Modified Files:
	wsfrag.html wsfrag.xml 
Log Message:
9558


Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -d -r1.68 -r1.69
--- wsfrag.html	11 May 2010 23:27:53 -0000	1.68
+++ wsfrag.html	12 May 2010 04:51:47 -0000	1.69
@@ -59,17 +59,16 @@
 5 <a href="#iddiv1_1_1421">Examples</a><br/>
 &nbsp;&nbsp;&nbsp;5.1 <a href="#iddiv2_1_1424">Examples</a><br/>
 6 <a href="#QName">QName Expression Language</a><br/>
-7 <a href="#XPathL1">XPath Level 1 Expression Language</a><br/>
-8 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
-9 <a href="#Faults">Faults</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#UnsupportedLanguage">UnsupportedLanguage</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#InvalidExpression">InvalidExpression</a><br/>
-&nbsp;&nbsp;&nbsp;9.3 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
-10 <a href="#metadata">WS-Fragment Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2_1_1956">Fragment Assertion</a><br/>
-11 <a href="#acks">Acknowledgements</a><br/>
-12 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_2019">Normative References</a><br/>
+7 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
+8 <a href="#Faults">Faults</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#UnsupportedLanguage">UnsupportedLanguage</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#InvalidExpression">InvalidExpression</a><br/>
+&nbsp;&nbsp;&nbsp;8.3 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
+9 <a href="#metadata">WS-Fragment Metadata</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_1867">Fragment Assertion</a><br/>
+10 <a href="#acks">Acknowledgements</a><br/>
+11 <a href="#refs">References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_1930">Normative References</a><br/>
 </p>
 <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="#changelog">Change Log</a><br/>
@@ -582,7 +581,7 @@
      There are no additional constraints beyond what WS-Transfer defines.
     </p><p>
      The following table elaborates on the expected behavior of a 
-     WS-Fragment Put request using the XPath Level 1 language.
+     WS-Fragment Put request using the XPath language.
     </p><p>
      Given a resource whose schema is defined as:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;a foo="xs:integer"? bar="xs:integer"? &gt;
@@ -698,69 +697,28 @@
    </p><p>
     The QName language MUST be indicated by using the IRI:
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-fra/QName">http://www.w3.org/2002/ws/ra/edcopies/ws-fra/QName</a></pre></div></div></div><div class="div1">
-<h2><a name="XPathL1" id="XPathL1"/>7 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.
+<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. 
+    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>
-    XPath Level 1 is a subset of the abbreviated relative syntax
-    of XPath 1.0 <a href="#XPath1">[XPath1.0]</a>, and is used to identify or select 
-    a node (element, attribute
-    or value) within a resource
-    representation or fragment. It is identified by the following IRI:
-   </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-fra/XPath-Level-1">http://www.w3.org/2002/ws/ra/edcopies/ws-fra/XPath-Level-1</a></pre></div></div><p>
-    An XPath Level 1 expression is an expression whose context is:
+    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> 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><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>
-    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
-    non-terminal 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)
-(05) &lt;node_sequence&gt; ::=
-(06)    &lt;element&gt; &lt;optional_collection_operator&gt; &lt;more&gt;;
-(07)
-(08) &lt;optional_collection_operator&gt; ::= '[' &lt;array_location&gt; ']';
-(09) &lt;optional_collection_operator&gt; ::= &lt;&gt;;
-(10)
-(11) &lt;more&gt; ::= '/' &lt;follower&gt; | &lt;&gt;;
-(12)
-(13) &lt;follower&gt; ::=
-(14)     &lt;attribute&gt; | &lt;text_function&gt; | &lt;node_sequence&gt;;
-(15)
-(16) &lt;element&gt;        ::= &lt;qualified_name&gt;;
-(17) &lt;attribute&gt;      ::= '@' &lt;qualified_name&gt;;
-(18)
-(19) &lt;qualified_name&gt; ::= &lt;name&gt; &lt;qname_follower&gt;;
-(20) &lt;qname_follower&gt; ::= ':' &lt;name&gt; | &lt;&gt;;
-(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
-    sub-range (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>
+    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 IRI:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-fra/XPath">http://www.w3.org/2002/ws/ra/edcopies/ws-fra/XPath</a></pre></div></div><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;
@@ -773,7 +731,7 @@
 (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
+    clarification. The XPath 1.0 language assumes that the root is the root
     node of the resource document, not the SOAP envelope or any other wrapper
     element which might contain the resource.
    </p><p>
@@ -788,29 +746,10 @@
     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 &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.
+    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 
@@ -828,43 +767,8 @@
     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>
-    Conformant implementations MAY supply additional functions
-    and capabilities, but MUST adhere to the minimum behavior described above.
-   </p><p>
-    The XPath Level 1 language does not support computed values. 
-   </p></div><div class="div1">
-<h2><a name="XPath10" id="XPath10"/>8 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 IRI:</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-fra/XPath">http://www.w3.org/2002/ws/ra/edcopies/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>
-    The serialization and context rules defined by the XPath Level 1 
-    language apply to the XPath 1.0 language as well.
-   </p></div><div class="div1">
-<h2><a name="Faults" id="Faults"/>9 Faults</h2><p>
+   </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></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>
@@ -912,14 +816,14 @@
     &lt;/s11:Fault&gt;
   &lt;/s11:Body&gt;
 &lt;/s11:Envelope&gt;</pre></div></div><div class="div2">
-<h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"/>9.1 UnsupportedLanguage</h3><p>
+<h3><a name="UnsupportedLanguage" id="UnsupportedLanguage"/>8.1 UnsupportedLanguage</h3><p>
      This fault MUST be generated when a service detects an unknown or
      unsupported Language 
      IRI 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:UnsupportedLanguage</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
         The specified Language IRI is not supported.
        </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Language IRI.</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="InvalidExpression" id="InvalidExpression"/>9.2 InvalidExpression</h3><p>
+<h3><a name="InvalidExpression" id="InvalidExpression"/>8.2 InvalidExpression</h3><p>
      This fault MUST be generated when a service determines that the Language
      expression specified in a request does not conform to the syntax
      of the language specified in the Language attribute or is semantically
@@ -927,20 +831,20 @@
     </p><a name="Table5" id="Table5"/><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:InvalidExpression</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
         The specified Language expression is invalid.
        </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The invalid language expression.</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="UnsupportedMode" id="UnsupportedMode"/>9.3 UnsupportedMode</h3><p>
+<h3><a name="UnsupportedMode" id="UnsupportedMode"/>8.3 UnsupportedMode</h3><p>
      This fault MUST be generated when a service detects a Mode in a Put
      request that is not supported.
     </p><a name="Table6" id="Table6"/><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:UnsupportedMode</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
         The specified mode is not supported.
        </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Mode.</em></td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="metadata" id="metadata"/>10 WS-Fragment Metadata</h2><p>
+<h2><a name="metadata" id="metadata"/>9 WS-Fragment Metadata</h2><p>
     An endpoint MAY indicate its support of WS-Fragment, or its features,
     by including the WS-Fragment FragmentAssertion Policy assertion within its 
     WSDL. By
     doing so the endpoint is indicating that the corresponding WS-Fragment
     features are supported by that endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_1956" id="iddiv2_1_1956"/>10.1 Fragment Assertion</h3><p>
+<h3><a name="iddiv2_1_1867" id="iddiv2_1_1867"/>9.1 Fragment Assertion</h3><p>
      Services indicate their support for the WS-Fragment specification through 
      the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -973,7 +877,7 @@
          Any metadata that appears is scoped to the operations and features 
          of the WS-Fragment specification.
         </p></dd></dl></div></div><div class="div1">
-<h2><a name="acks" id="acks"/>11 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>10 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
      Alessio Soldano (Red Hat),
@@ -1003,8 +907,8 @@
      Wu Chou (Avaya Communications),
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2019" id="iddiv2_1_2019"/>12.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
+<h3><a name="iddiv2_1_1930" id="iddiv2_1_1930"/>11.1 Normative References</h3><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, Author.
@@ -1190,4 +1094,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</a></td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9699">9699</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=9699">9699</a></td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9558">9558</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.66
retrieving revision 1.67
diff -u -d -r1.66 -r1.67
--- wsfrag.xml	11 May 2010 23:27:53 -0000	1.66
+++ wsfrag.xml	12 May 2010 04:51:47 -0000	1.67
@@ -1100,7 +1100,7 @@
 
     <p>
      The following table elaborates on the expected behavior of a 
-     WS-Fragment Put request using the XPath Level 1 language.
+     WS-Fragment Put request using the XPath language.
     </p>
 
     <p>
@@ -1461,105 +1461,55 @@
 
   </div1>
 
-  <div1 id="XPathL1">
-   <head>XPath Level 1 Expression Language</head>
-
-   <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>
+  <div1 id="XPath10">
+   <head>XPath 1.0 Expression Language</head>
 
    <p>
-    XPath Level 1 is a subset of the abbreviated relative syntax
-    of XPath 1.0 <bibref ref="XPath1"/>, and is used to identify or select 
-    a node (element, attribute
-    or value) within a resource
-    representation or fragment. It is identified by the following IRI:
+    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. 
+    This language is
+    useful for resources with full XPath processing capability or which 
+    need to support returning values computed from their resource 
+    representation.
    </p>
-
-   <example>
-    <eg><loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra/XPath-Level-1">http://www.w3.org/&wsfra.nsprefix;/ws-fra/XPath-Level-1</loc></eg>
-   </example>
-
+   
    <p>
-    An XPath Level 1 expression is an expression whose context is:
+    An XPath 1.0 expression is an expression whose context is:
    </p>
-    
+   
    <ulist>
     <item>
      <p>
       Context Node: the root element of the XML representation of the resource
      </p>
     </item>
-    <item> <p> Context Position: 1 </p> </item>
-    <item> <p> Context Size: 1 </p> </item>
-    <item> <p> Variable Binding: None </p> </item>
-    <item> <p> Node Tests: NameTest and the text NodeType </p> </item>
-    <item> <p> Function Libraries: None </p> </item>
+    <item> <p>Context Position: 1</p> </item>
+    <item> <p>Context Size: 1</p> </item>
+    <item> <p>Variable Binding: None</p> </item>
+    <item> <p>Function Libraries: Core function library</p> </item>
     <item>
      <p>
-      Namespace Declarations: Any namespace declarations in-scope where the
-      XPath expression appears
+      Namespace Declarations: Any namespace declarations in-scope where 
+      the XPath expression appears
      </p>
     </item>
    </ulist>
+   
    <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
-    non-terminal productions are in angle brackets. Terminal symbols are
-    either literals, or in UPPERCASE:
+    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 IRI:</p>
    <example>
-    <eg>(01) &lt;xpath> ::=  &lt;context> &lt;node_sequence&gt;;
-(02)
-(03) &lt;context> ::= '/' | &lt;&gt;;
-(04)
-(05) &lt;node_sequence&gt; ::=
-(06)    &lt;element> &lt;optional_collection_operator> &lt;more&gt;;
-(07)
-(08) &lt;optional_collection_operator> ::= '[' &lt;array_location&gt; ']';
-(09) &lt;optional_collection_operator> ::= &lt;&gt;;
-(10)
-(11) &lt;more> ::= '/' &lt;follower> | &lt;&gt;;
-(12)
-(13) &lt;follower&gt; ::=
-(14)     &lt;attribute> | &lt;text_function> | &lt;node_sequence&gt;;
-(15)
-(16) &lt;element>        ::= &lt;qualified_name&gt;;
-(17) &lt;attribute>      ::= '@' &lt;qualified_name&gt;;
-(18)
-(19) &lt;qualified_name> ::= &lt;name> &lt;qname_follower&gt;;
-(20) &lt;qname_follower> ::= ':' &lt;name&gt; | &lt;&gt;;
-(21) &lt;text_function&gt;  ::= "text()" ;
-(22) &lt;array_location&gt; ::= NONZERO_DECIMAL_UNSIGNED_INTEGER;
-(23) &lt;name&gt;           ::= XML_TOKEN;</eg>
+     <eg><loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra/XPath">http://www.w3.org/&wsfra.nsprefix;/ws-fra/XPath</loc></eg>
    </example>
-   
-   <p>
-    The terminal tokens which require further lexical
-    specification are NONZERO_DECIMAL_UNSIGNED_INTEGER, whose values are in the
-    sub-range (1...4294967295), and XML_TOKEN whose values are equivalent to 
-    those for the XML Schema type <emph>xs:token</emph>. 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>
@@ -1578,7 +1528,7 @@
    
    <p>
     The context and document root node need
-    clarification. XPath Level 1 assumes that the root is the root
+    clarification. The XPath 1.0 language assumes that the root is the root
     node of the resource document, not the SOAP envelope or any other wrapper
     element which might contain the resource.
    </p>
@@ -1611,51 +1561,10 @@
    </p>
     
    <p>
-    The &lt;node_sequence&gt; production provides the recursive
-    behavior for the XPath:
-   </p>
-    
-   <example>
-    <eg>(01) /a/b/c
-(02) b/c</eg>
-   </example>
-   
-   <p>
-    It also provides for selecting specific repeated elements
-    through the &lt;optional_collection_operator&gt; production:
-   </p>
-    
-   <example>
-    <eg>(01) /a/e/f[2]</eg>
-   </example>
-    
-   <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>
-   
-   <example>
-    <eg>(01) /ns1:a/ns2:b/c</eg>
-   </example>
-    
-   <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.
+    content, the return value will be a node-set containing a single text node.
    </p>
    
    <example>
@@ -1702,76 +1611,6 @@
    <example>
     <eg>(01) &lt;b&gt; &lt;c d="30"&gt; 20 &lt;/c&gt; &lt;/b&gt;</eg>
    </example>
-   
-   <p>
-    Conformant implementations MAY supply additional functions
-    and capabilities, but MUST adhere to the minimum behavior described above.
-   </p>
-     
-   <p>
-    The XPath Level 1 language does not support computed values. 
-   </p>
-  </div1>
-
-  <div1 id="XPath10">
-   <head>XPath 1.0 Expression Language</head>
-
-   <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>
-   
-   <ulist>
-    <item>
-     <p>
-      Context Node: the root element of the XML representation of the resource
-     </p>
-    </item>
-    <item> <p>Context Position: 1</p> </item>
-    <item> <p>Context Size: 1</p> </item>
-    <item> <p>Variable Binding: None</p> </item>
-    <item> <p>Function Libraries: Core function library</p> </item>
-    <item>
-     <p>
-      Namespace Declarations: Any namespace declarations in-scope where 
-      the XPath expression appears
-     </p>
-    </item>
-   </ulist>
-   
-   <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 IRI:</p>
-   <example>
-     <eg><loc href="http://www.w3.org/&wsfra.nsprefix;/ws-fra/XPath">http://www.w3.org/&wsfra.nsprefix;/ws-fra/XPath</loc></eg>
-   </example>
-    
-   <p>
-    Implementations that support the full XPath 1.0 language MUST
-    support the XPath Level 1 language.
-   </p>
-
-   <p>
-    The serialization and context rules defined by the XPath Level 1 
-    language apply to the XPath 1.0 language as well.
-   </p>
 
   </div1>
 
@@ -2567,6 +2406,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9699">9699</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/05/11 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9558">9558</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Wednesday, 12 May 2010 04:51:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 May 2010 04:51:52 GMT