Remove Namespaces and Down-level clients section per CSSWG decision

Author: fantasai

selectors3/Overview.html

@@ -238,15 +238,14 @@ <h2><a name=contents>Table of contents</a></h2>
       <li class="tocline3"><a href="#grammar">10.1. Grammar</a>
       <li class="tocline3"><a href="#lex">10.2. Lexical scanner</a></li>
      </ul>
-    <li class="tocline2"><a href="#downlevel">11. Namespaces and down-level clients</a>
-    <li class="tocline2"><a href="#profiling">12. Profiles</a>
-    <li><a href="#Conformance">13. Conformance and requirements</a>
-    <li><a href="#Tests">14. Tests</a>
-    <li><a href="#ACKS">15. Acknowledgements</a>
-    <li class="tocline2"><a href="#references">16. References</a>
+    <li class="tocline2"><a href="#profiling">11. Profiles</a>
+    <li><a href="#Conformance">12. Conformance and requirements</a>
+    <li><a href="#Tests">13. Tests</a>
+    <li><a href="#ACKS">14. Acknowledgements</a>
+    <li class="tocline2"><a href="#references">15. References</a>
      <ul class="toc">
-      <li class="tocline3"><a href="#normative-references">16.1. Normative References</a>
-      <li class="tocline3"><a href="#informative-references">16.2. Informative References</a></li>
+      <li class="tocline3"><a href="#normative-references">15.1. Normative References</a>
+      <li class="tocline3"><a href="#informative-references">15.2. Informative References</a></li>
      </ul>
    </ul>
 
@@ -2632,133 +2631,7 @@ <h3><a name=lex>10.2. Lexical scanner</a></h3>
 
 .                return *yytext;</pre>
 
-
-
-<h2><a name=downlevel>11. Namespaces and down-level clients</a></h2>
-
-<p><em>This section is informative (non-normative).</em></p>
-
-<p>An important issue is the interaction of Selectors with XML
-documents in Web clients that were produced prior to this
-document. Unfortunately, due to the fact that namespaces must be
-matched based on the URI which identifies the namespace, not the
-namespace prefix, some mechanism is required to identify namespaces in
-Selectors by their URI as well. Without such a mechanism, it is impossible
-to construct, e.g., a CSS style sheet which will properly match selectors in
-all cases against a random set of XML documents. However, given
-complete knowledge of the XML document to which a style sheet is to be
-applied, and a limited use of namespaces within the XML document, it
-is possible to construct a style sheet in which selectors would match
-elements and attributes correctly.</p>
-
-<p>It should be noted that a down-level CSS client will (if it
-properly conforms to CSS forward compatible parsing rules) ignore all
-<code>@namespace</code> at-rules, as well as all style rules that make
-use of namespace qualified element type or attribute selectors. The
-syntax of delimiting namespace prefixes in CSS was deliberately chosen
-so that down-level CSS clients would ignore the style rules rather
-than possibly match them incorrectly.</p>
-
-<p>The use of default namespaces in CSS makes it possible to write
-element type selectors that will function in both namespace aware CSS
-clients as well as down-level clients. It should be noted that
-down-level clients may incorrectly match selectors against XML
-elements in other namespaces.</p>
-
-<p>The following are scenarios and examples in which it is possible to
-construct style sheets which would function properly in web clients
-that do not implement this proposal.</p>
-
-<ol>
-  <li>
-
-   <p>The XML document does not use namespaces.</p>
-
-   <ul>
-
-    <li>In this case, it is obviously not necessary to declare or use
-    namespaces in the style sheet. Standard CSS element type and
-    attribute selectors will function adequately in a down-level
-    client.</li>
-
-    <li>In a CSS namespace aware client, the default behavior of
-    element selectors matching without regard to namespace will
-    function properly against all elements, since no namespaces are
-    present. However, the use of specific element type selectors that
-    match only elements that have no namespace ("<code>|name</code>")
-    will guarantee that selectors will match only XML elements that do
-    not have a <a href="#nsdecl">declared</a>  namespace. </li>
-
-   </ul>
-
-  </li>
-
-  <li>
-
-   <p>The XML document defines a single, default namespace used
-   throughout the document. No namespace prefixes are used in element
-   names.</p>
-
-   <ul>
-
-    <li>In this case, a down-level client will function as if
-    namespaces were not used in the XML document at all. Standard CSS
-    element type and attribute selectors will match against all
-    elements. </li>
-
-   </ul>
-
-  </li>
-
-  <li>
-
-   <p>The XML document does <b>not</b> use a default namespace, all
-   namespace prefixes used are known to the style sheet author, and
-   there is a direct mapping between namespace prefixes and namespace
-   URIs. (A given prefix may only be mapped to one namespace URI
-   throughout the XML document; there may be multiple prefixes mapped
-   to the same URI).</p>
-
-   <ul>
-
-    <li>In this case, the down-level client will view and match
-    element type and attribute selectors based on their fully
-    qualified name, not the local part as outlined in the <a
-    href="#typenmsp">Type selectors and Namespaces</a> section. 
-    Selectors may be declared using an escaped colon "<code>\:</code>"
-    to describe the fully qualified names, e.g.
-    "<code>html\:h1</code>" will match
-    <code>&lt;html:h1&gt;</code>. Selectors using the qualified name
-    will only match XML elements that use the same prefix. Other
-    namespace prefixes used in the XML that are mapped to the same URI
-    will not match as expected unless additional CSS style rules are
-    declared for them.</li>
-
-    <li>Note that selectors declared in this fashion will
-    <em>only</em> match in down-level clients. A CSS namespace aware
-    client will match element type and attribute selectors based on
-    the name's local part. Selectors declared with the fully
-    qualified name will not match (unless there is no namespace prefix
-    in the fully qualified name).</li>
-
-   </ul>
-
-  </li>
-
- </ol>
-
-<p>In other scenarios: when the namespace prefixes used in the XML are
-not known in advance by the style sheet author; or a combination of
-elements with no namespace are used in conjunction with elements using
-a default namespace; or the same namespace prefix is mapped to
-<em>different</em> namespace URIs within the same document, or in
-different documents; it is impossible to construct a CSS style sheet
-that will function properly against all elements in those documents,
-unless, the style sheet is written using a namespace URI syntax (as
-outlined in this document or similar) and the document is processed by
-a CSS and XML namespace aware client.</p>
-
-<h2><a name=profiling>12. Profiles</a></h2>
+<h2><a name=profiling>11. Profiles</a></h2>
 
 <p>Each specification using Selectors must define the subset of
 Selectors it allows and excludes, and describe the local meaning of
@@ -2869,7 +2742,7 @@ <h2><a name=profiling>12. Profiles</a></h2>
   <li>fragment descriptions that appear on the right side of declarations.
 </li></ol></div>
 
-<h2><a name=Conformance></a>13. Conformance and requirements</h2>
+<h2><a name=Conformance></a>12. Conformance and requirements</h2>
 
 <p>This section defines conformance with the present specification only.
 
@@ -2908,15 +2781,15 @@ <h2><a name=Conformance></a>13. Conformance and requirements</h2>
 href="#refsUNICODE">[UNICODE]</a> and apply to implementations of this
 specification.</p>-->
 
-<h2><a name=Tests></a>14. Tests</h2>
+<h2><a name=Tests></a>13. Tests</h2>
 
 <p>This specification has <a
 href="http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/">a test
 suite</a> allowing user agents to verify their basic conformance to
 the specification. This test suite does not pretend to be exhaustive
 and does not cover all possible combined cases of Selectors.</p>
 
-<h2><a name=ACKS></a>15. Acknowledgements</h2>
+<h2><a name=ACKS></a>14. Acknowledgements</h2>
 
 <p>The CSS working group would like to thank everyone who has sent
 comments on this specification over the years.</p>
@@ -2926,13 +2799,13 @@ <h2><a name=ACKS></a>15. Acknowledgements</h2>
 Brower who performed the final editorial review of the last call
 draft. The working group would also like to thank Adam Kuehn, Boris
 Zbarsky, David Perrell, Elliotte Harold, Matthew Raymond, Ruud
-Steltenpool, Patrick Garies,
+Steltenpool, Patrick Garies, Anton Prowse,
 and the W3C Internationalization Working Group for their
 last call comments and kind words.</p>
 
-<h2><a name=references>16. References</a></h2>
+<h2><a name=references>15. References</a></h2>
 
-<h3><a name=normative-references>16.1 Normative References</a></h3>
+<h3><a name=normative-references>15.1 Normative References</a></h3>
 
 <dl class="refs">
 
@@ -2957,7 +2830,7 @@ <h3><a name=normative-references>16.1 Normative References</a></h3>
 
 </dl>
 
-<h3><a name=informative-references>16.2 Informative References</a></h3>
+<h3><a name=informative-references>15.2 Informative References</a></h3>
 
 <dl class="refs">