html5/spec Overview.html,1.2463,1.2464

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv26237

Modified Files:
	Overview.html 
Log Message:
Add rules for improving compat with XPath 1.0. (bug 6778) (whatwg r3324)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2463
retrieving revision 1.2464
diff -u -d -r1.2463 -r1.2464
--- Overview.html	26 Jun 2009 06:34:45 -0000	1.2463
+++ Overview.html	26 Jun 2009 08:32:30 -0000	1.2464
@@ -405,7 +405,7 @@
      <li><a href="#transparent-content-models"><span class="secno">3.4.2 </span>Transparent content models</a></ol></li>
    <li><a href="#paragraphs"><span class="secno">3.5 </span>Paragraphs</a></li>
    <li><a href="#apis-in-html-documents"><span class="secno">3.6 </span>APIs in HTML documents</a></li>
-   <li><a href="#dom-based-xslt-1.0-processors"><span class="secno">3.7 </span>DOM-based XSLT 1.0 processors</a></li>
+   <li><a href="#interactions-with-xpath-and-xslt"><span class="secno">3.7 </span>Interactions with XPath and XSLT</a></li>
    <li><a href="#dynamic-markup-insertion"><span class="secno">3.8 </span>Dynamic markup insertion</a>
     <ol>
      <li><a href="#controlling-the-input-stream"><span class="secno">3.8.1 </span>Controlling the input stream</a></li>
@@ -7526,9 +7526,25 @@
    </dd>
 
 
-  </dl><h3 id="dom-based-xslt-1.0-processors"><span class="secno">3.7 </span>DOM-based XSLT 1.0 processors</h3><p>XSLT 1.0 processors outputting to a DOM when the output method is
-  "html" (either explicitly or via the defaulting rule in XSLT 1.0)
-  are affected as follows:<p>If the transformation program outputs an element in no namespace,
+  </dl><h3 id="interactions-with-xpath-and-xslt"><span class="secno">3.7 </span>Interactions with XPath and XSLT</h3><p>Implementations of XPath 1.0 that operate on HTML documents
+  parsed or created in the manners described in this specification
+  (e.g. as part of the <code title="">document.evaluate()</code> API)
+  are affected as follows:<p>In addition to the cases where a name expression would match a
+  node per XPath 1.0, a name expression must evaluate to matching a
+  node when all the following conditions are also met:<ul class="brief"><li>The name expression has no namespace.</li>
+   <li>The name expression has local name that is a match for <var title="">local</var>.</li>
+   <li>The expression is being tested against an element node.</li>
+   <li>The element has local name <var title="">local</var>.</li>
+   <li>The element is in the <a href="#html-namespace-0">HTML namespace</a>.</li>
+   <li>The element's document is an <a href="#html-documents" title="HTML documents">HTML document</a>.</li>
+  </ul><p class="note">These requirements are a <a href="#willful-violation">willful
+  violation</a> of the XPath 1.0 specification, motivated by desire
+  to have implementations be compatible with legacy content while
+  still supporting the changes that this specification introduces to
+  HTML regarding which namespace is used for HTML elements. <a href="#references">[XPATH10]</a></p><!-- note: version matters for
+  this ref --><hr><p id="dom-based-xslt-1.0-processors">XSLT 1.0 processors outputting
+  to a DOM when the output method is "html" (either explicitly or via
+  the defaulting rule in XSLT 1.0) are affected as follows:<p>If the transformation program outputs an element in no namespace,
   the processor must, prior to constructing the corresponding DOM
   element node, change the namespace of the element to the <a href="#html-namespace-0">HTML
   namespace</a>, <a href="#converted-to-ascii-lowercase" title="converted to ASCII

Received on Friday, 26 June 2009 08:32:48 UTC