[css-namespaces] Revert to the old Conformance section.

Author: tabatkins

css-namespaces/Overview.bs

@@ -13,6 +13,7 @@ Former Editor: Chris Lilley
 Previous Version: http://www.w3.org/TR/2008/CR-css3-namespace-20080523/
 Abstract: This CSS Namespaces module defines the syntax for using namespaces in CSS. It defines the ''@namespace'' 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.
 Link Defaults: selectors-4 (dfn) type selectors, css-syntax-3 (dfn) at-rule
+Boilerplate: omit footer
 </pre>
 
 <!--
@@ -54,6 +55,48 @@ Introduction</h2>
 	so that these CSS clients would ignore the style rules
 	rather than possibly match them incorrectly.
 
+<h2 id="conformance">Conformance</h2>
+
+  <p>A document or implementation cannot conform to CSS Namespaces alone,
+    but can claim conformance to CSS Namespaces if it satisfies the
+    conformance requirements in this specification when implementing CSS or
+    another host language that normatively references this specification.</p>
+
+  <p>Conformance to CSS Namespaces is defined for two classes:
+  <dl>
+    <dt><dfn>style sheet</dfn></dt>
+      <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS style
+        sheet</a> (or a complete unit of another host language that normatively
+        references CSS Namespaces).
+    <dt><dfn>interpreter</dfn></dt>
+      <dd>Someone or something that interprets the semantics of a style sheet.
+        (CSS <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">user
+        agents</a> fall under this category.)</dd>
+  </dl>
+
+  <p>The conformance requirements are expressed with a combination of
+    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.
+    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. [[!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>,
+    like this:
+
+  <div class="example">
+    <p>This is an example of an informative example.</p>
+  </div>
+
+  <p>Informative notes begin with the word "Note" and are set apart from the
+    normative text with <code>class="note"</code>, like this:
+
+  <p class="note">Note, this is an informative note.</p>
+
 
 <h3 id="terminology">
 Terminology</h3>
@@ -323,3 +366,22 @@ Acknowledgments</h2>
 	Björn Höhrmann,
 	and Lachlan Hunt
 	for their comments.
+
+<h2 class="no-num no-ref" id="references">
+References</h2>
+
+<h3 class="no-num no-ref" id="normative">
+Normative References</h3>
+<div data-fill-with="normative-references"></div>
+
+<h3 class="no-num no-ref" id="informative">
+Informative References</h3>
+<div data-fill-with="informative-references"></div>
+
+<h2 class="no-num no-ref" id="index">
+Index</h2>
+<div data-fill-with="index"></div>
+
+<h2 class="no-num no-ref" id="property-index">
+Property index</h2>
+<div data-fill-with="property-index"></div>