make some editorial edits to address comments from Karl; make REC-XML-NAMES a normative references

Author: annevk

css3-namespace/Overview.html

@@ -15,15 +15,15 @@
 
    <h1 id=css-namespaces>CSS Namespaces Module</h1>
 
-   <h2 class="no-num no-toc" id=longstatus>Editor's Draft 24 December 2007</h2>
+   <h2 class="no-num no-toc" id=longstatus>Editor's Draft 25 December 2007</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a
      href="http://dev.w3.org/csswg/css3-namespace/">http://dev.w3.org/csswg/css3-namespace/</a></dd>
     <!--
-    <dd><a href="http://www.w3.org/TR/2007/WD-css3-namespace-20071224/">http://www.w3.org/TR/2007/WD-css3-namespace-20071224/</a></dd>
+    <dd><a href="http://www.w3.org/TR/2007/WD-css3-namespace-20071225/">http://www.w3.org/TR/2007/WD-css3-namespace-20071225/</a></dd>
 -->
 
     <dt>Latest version:
@@ -71,8 +71,8 @@ <h2 class="no-num no-toc" id=longstatus>Editor's Draft 24 December 2007</h2>
 
   <h2 class="no-num no-toc" id=abstract>Abstract</h2>
 
-  <p>This CSS module defines the syntax for using namespaces in CSS. It
-   introduces the <code>@namespace</code> rule for declaring the default
+  <p>The CSS Namespaces module defines the syntax for using namespaces in
+   CSS. It defines the <code>@namespace</code> rule for declaring the default
    namespace and binding namespaces to namespace prefixes, and it also
    defines a syntax that other specifications can adopt for using those
    prefixes in namespace-qualified names.
@@ -112,6 +112,10 @@ <h2 class="no-num no-toc" id=contents>Table of contents</h2>
    <li><a href="#intro"><span class=secno>1. </span>Introduction</a>
 
    <li><a href="#conformance"><span class=secno>2. </span>Conformance</a>
+    <ul class=toc>
+     <li><a href="#terminology"><span class=secno>2.1. </span>Terminology</a>
+      
+    </ul>
 
    <li><a href="#declaration"><span class=secno>3. </span>Declaring
     namespaces: the <code>@namespace</code> rule</a>
@@ -145,20 +149,14 @@ <h2 id=intro><span class=secno>1. </span>Introduction</h2>
 
    <p><em>This section is non-normative.</em></p>
 
-   <p>The CSS Namespaces module defines syntax for using namespaces in CSS.
-    It introduces the <code>@namespace</code> rule for declaring a default
-    namespace and for binding namespaces to namespace prefixes. It also
-    defines a syntax for using those prefixes to represent
-    namespace-qualified names. It does not define where such names are valid
-    or what they mean: that depends on their context and is defined by a host
-    language (such as [[Selectors]]) that references the syntax defined in
-    CSS Namespaces.
-
-   <p>The terminology used in this specification is that of <a
-    href="#REC-XML-NAMES"
-    rel=biblioentry>[REC-XML-NAMES]<!--{{REC-XML-NAMES}}--></a>. However, the
-    syntax defined here is not restricted to representing XML element and
-    attribute names.</p>
+   <p>This CSS module defines syntax for using namespaces in CSS. It defines
+    the <code>@namespace</code> rule for declaring a default namespace and
+    for binding namespaces to namespace prefixes. It also defines a syntax
+    for using those prefixes to represent namespace-qualified names. It does
+    not define where such names are valid or what they mean: that depends on
+    their context and is defined by a host language, such as Selectors
+    ([[Select]]), that references the syntax defined in the CSS Namespaces
+    Module.
 
    <p>Note that a CSS client that does not support this module will (if it
     properly conforms to <a
@@ -202,12 +200,11 @@ <h2 id=conformance><span class=secno>2. </span>Conformance</h2>
     descriptive assertions and RFC 2119 terminology. The key words "MUST",
     "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
     "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
-    document are to be interpreted as described in RFC 2119 (see <a
-    href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a>).
-    However, for readability, these words do not appear in all uppercase
-    letters in this specification. All of the text of this specification is
-    normative except sections explicitly marked as non-normative, examples,
-    and notes.</p>
+    document are to be interpreted as described in RFC 2119. However, for
+    readability, these words do not appear in all uppercase letters in this
+    specification. All of the text of this specification is normative except
+    sections explicitly marked as non-normative, examples, and notes. <a
+    href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a></p>
 
    <p>Examples in this specification are introduced with the words "for
     example" or are set apart from the normative text with
@@ -221,6 +218,14 @@ <h2 id=conformance><span class=secno>2. </span>Conformance</h2>
     normative text with <code>class="note"</code>, like this:
 
    <p class=note>Note, this is an informative note.</p>
+
+   <h3 id=terminology><span class=secno>2.1. </span>Terminology</h3>
+
+   <p>Besides terms introduced by this specification, the terminology used is
+    that of Namespaces in XML 1.0. However, the syntax defined here is not
+    restricted to representing XML element and attribute names. <a
+    href="#REC-XML-NAMES"
+    rel=biblioentry>[REC-XML-NAMES]<!--{{!REC-XML-NAMES}}--></a></p>
   </div>
 
   <div>
@@ -249,10 +254,8 @@ <h2 id=declaration><span class=secno>3. </span>Declaring namespaces: the
      where the <code>svg</code> namespace prefix is used.</p>
    </div>
 
-   <p id=expanded-name-match>In CSS Namespaces, as in XML Namespaces <a
-    href="#REC-XML-NAMES"
-    rel=biblioentry>[REC-XML-NAMES]<!--{{REC-XML-NAMES}}--></a>, the prefix
-    is merely a syntactic construct; it is the <em><dfn
+   <p id=expanded-name-match>In CSS Namespaces, as in Namespaces in XML 1.0,
+    the prefix is merely a syntactic construct; it is the <em><dfn
     id=expanded-name>expanded name</dfn></em> (the tuple of local name and
     namespace name) that is significant. Thus the actual prefixes used in a
     CSS style sheet, and whether they are defaulted or not, are independent
@@ -394,9 +397,9 @@ <h2 class=no-num id=acknowledgments>Acknowledgments</h2>
    Bert Bos and Steven Pemberton. Many current and former members of the CSS
    Working Group have contributed to this document. Discussions on
    www-style@w3.org and in other places have also contributed ideas to this
-   specification. Special thanks goes to L. David Baron, Ian Hickson,
-   Bj&ouml;ern H&ouml;hrmann, Lachlan Hunt, and Anne van Kesteren for their
-   comments.
+   specification. Special thanks goes to L. David Baron, Karl Dubost, Ian
+   Hickson, Bj&ouml;ern H&ouml;hrmann, Lachlan Hunt, and Anne van Kesteren
+   for their comments.
 
   <h2 class=no-num id=references>References</h2>
 
@@ -416,6 +419,14 @@ <h3 class=no-num id=normative-references>Normative references</h3>
     </dd>
    <!---->
 
+   <dt id=REC-XML-NAMES>[REC-XML-NAMES]
+
+   <dd>Tim Bray; et al. <cite>Namespaces in XML.</cite> 16 August 2006. W3C
+    Recommendation. URL: <a
+    href="http://www.w3.org/TR/2006/REC-xml-names-20060816">http://www.w3.org/TR/2006/REC-xml-names-20060816</a>
+    </dd>
+   <!---->
+
    <dt id=RFC2119>[RFC2119]
 
    <dd>S. Bradner. <cite>Key words for use in RFCs to Indicate Requirement

css3-namespace/Overview.src.html

@@ -41,8 +41,8 @@ <h2 class="no-num no-toc">[LONGSTATUS] [DATE: 31 October 2007]</h2>
 
 <h2 class="no-num no-toc" id="abstract">Abstract</h2>
 
-  <p>This CSS module defines the syntax for using namespaces in CSS.
-    It introduces the <code>@namespace</code> rule for declaring the
+  <p>The CSS Namespaces module defines the syntax for using namespaces in CSS.
+    It defines the <code>@namespace</code> rule for declaring the
     default namespace and binding namespaces to namespace prefixes, and
     it also defines a syntax that other specifications can adopt for using
     those prefixes in namespace-qualified names.</p>
@@ -72,18 +72,14 @@ <h2 id="intro">Introduction</h2>
 
   <p><em>This section is non-normative.</em></p>
 
-  <p>The CSS Namespaces module defines syntax for using namespaces in CSS.
-    It introduces the <code>@namespace</code> rule for declaring a
+  <p>This CSS module defines syntax for using namespaces in CSS.
+    It defines the <code>@namespace</code> rule for declaring a
     default namespace and for binding namespaces to namespace prefixes.
     It also defines a syntax for using those prefixes to represent
     namespace-qualified names. It does not define where such names are
     valid or what they mean: that depends on their context and is defined
-    by a host language (such as [[Selectors]]) that references the syntax
-    defined in CSS Namespaces.
-
-  <p>The terminology used in this specification is that of [[REC-XML-NAMES]].
-    However, the syntax defined here is not restricted to representing XML
-    element and attribute names.</p>
+    by a host language, such as Selectors ([[Select]]), that references the syntax
+    defined in the CSS Namespaces Module.
 
   <p>Note that a CSS client that does not support this module will (if it
     properly conforms to
@@ -121,11 +117,11 @@ <h2 id="conformance">Conformance</h2>
     descriptive assertions and RFC 2119 terminology. The key words "MUST",
     "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
     "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
-    document are to be interpreted as described in RFC 2119 (see [[!RFC2119]]).
+    document are to be interpreted as described in RFC 2119.
     However, for readability, these words do not appear in all uppercase
     letters in this specification. All of the text of this specification is
     normative except sections explicitly marked as non-normative, examples,
-    and notes.</p>
+    and notes. [[!RFC2119]]</p>
 
   <p>Examples in this specification are introduced with the words "for example"
     or are set apart from the normative text with <code>class="example"</code>,
@@ -140,6 +136,13 @@ <h2 id="conformance">Conformance</h2>
 
   <p class="note">Note, this is an informative note.</p>
 
+  
+  <h3 id="terminology">Terminology</h3>
+  
+  <p>Besides terms introduced by this specification, the terminology used is
+    that of Namespaces in XML 1.0. However, the syntax defined here is not
+    restricted to representing XML element and attribute names.
+    [[!REC-XML-NAMES]]</p>
 </div>
 
 <div>
@@ -164,16 +167,15 @@ <h2 id="declaration">Declaring namespaces: the <code>@namespace</code> rule</h2>
       where the <code>svg</code> namespace prefix is used.</p>
   </div>
 
-  <p id="expanded-name-match">In CSS Namespaces, as in XML Namespaces
-    [[REC-XML-NAMES]], the prefix is merely a syntactic construct; it is
+  <p id="expanded-name-match">In CSS Namespaces, as in Namespaces in XML 1.0,
+    the prefix is merely a syntactic construct; it is
     the <em><dfn id="expanded-name">expanded name</dfn></em> (the tuple of
     local name and namespace name) that is significant.
     Thus the actual prefixes used in a CSS style sheet, and whether they are
     defaulted or not, are independent of the namespace prefixes used in the
     markup and whether these are defaulted or not.</p>
 
 <h3 id="syntax">Syntax</h3>
-
   <p>The syntax for the @namespace rule is as follows (using the notation from
     the <a href="http://www.w3.org/TR/CSS21/grammar.html">Grammar appendix of
     CSS 2.1</a> [[!CSS21]]):</p>
@@ -294,7 +296,7 @@ <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
   and CSS by Bert Bos and Steven Pemberton. Many current and former members of
   the CSS Working Group have contributed to this document. Discussions on
   www-style@w3.org and in other places have also contributed ideas to this
-  specification. Special thanks goes to L. David Baron, Ian Hickson, Bj&ouml;ern
+  specification. Special thanks goes to L. David Baron, Karl Dubost, Ian Hickson, Bj&ouml;ern
   H&ouml;hrmann, Lachlan Hunt, and Anne van Kesteren for their comments.</p>
 
 <h2 class="no-num" id="references">References</h2>