Remove CR issue

fantasai · fantasai · commit aa49914e473d · 2011-08-29T06:29:54.000Z
diff --git a/css3-text/Overview.html b/css3-text/Overview.html
@@ -386,6 +386,27 @@ <h2 class="no-num no-toc" id=contents>Table of Contents</h2>
       the &lsquo;<code class=property>text-shadow</code>&rsquo; property</a>
     </ul>
 
+   <li><a href="#conformance"><span class=secno>11. </span> Conformance</a>
+    <ul class=toc>
+     <li><a href="#conventions"><span class=secno>11.1. </span> Document
+      Conventions</a>
+
+     <li><a href="#conformance-classes"><span class=secno>11.2. </span>
+      Conformance Classes</a>
+
+     <li><a href="#partial"><span class=secno>11.3. </span> Partial
+      Implementations</a>
+
+     <li><a href="#experimental"><span class=secno>11.4. </span> Experimental
+      Implementations</a>
+
+     <li><a href="#testing"><span class=secno>11.5. </span>Non-Experimental
+      Implementations</a>
+
+     <li><a href="#cr-exit-criteria"><span class=secno>11.6. </span> CR Exit
+      Criteria</a>
+    </ul>
+
    <li class=no-num><a href="#acknowledgements"> Appendix A:
     Acknowledgements</a>
 
@@ -5248,6 +5269,177 @@ <h3 id=text-shadow><span class=secno>10.3. </span> Text Shadows: the
    class=css>text-shadow</code></a>&rsquo; property applies to both the
    <code>::first-line</code> and <code>::first-letter</code> pseudo-elements.
 
+  <h2 id=conformance><span class=secno>11. </span> Conformance</h2>
+
+  <h3 id=conventions><span class=secno>11.1. </span> Document Conventions</h3>
+
+  <p>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.
+
+  <p>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>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.
+
+  <h3 id=conformance-classes><span class=secno>11.2. </span> Conformance
+   Classes</h3>
+
+  <p>Conformance to CSS Text Level 3 is defined for three conformance
+   classes:
+
+  <dl>
+   <dt><dfn id=style-sheet title="style sheet!!as conformance class">style
+    sheet</dfn>
+
+   <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
+    style sheet</a>.
+
+   <dt><dfn id=renderer>renderer</dfn>
+
+   <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+    that interprets the semantics of a style sheet and renders documents that
+    use them.
+
+   <dt><dfn id=authoring-tool>authoring tool</dfn>
+
+   <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+    that writes a style sheet.
+  </dl>
+
+  <p>A style sheet is conformant to CSS Text Level 3 if all of its
+   declarations that use properties defined in this module have values that
+   are valid according to the generic CSS grammar and the individual grammars
+   of each property as given in this module.
+
+  <p>A renderer is conformant to CSS Text Level 3 if, in addition to
+   interpreting the style sheet as defined by the appropriate specifications,
+   it supports all the features defined by CSS Text Level 3 by parsing them
+   correctly and rendering the document accordingly. However, the inability
+   of a UA to correctly render a document due to limitations of the device
+   does not make the UA non-conformant. (For example, a UA is not required to
+   render color on a monochrome monitor.)
+
+  <p>An authoring tool is conformant to CSS Text Level 3 if it writes style
+   sheets that are syntactically correct according to the generic CSS grammar
+   and the individual grammars of each feature in this module, and meet all
+   other conformance requirements of style sheets as described in this
+   module.
+
+  <h3 id=partial><span class=secno>11.3. </span> Partial Implementations</h3>
+
+  <p>So that authors can exploit the forward-compatible parsing rules to
+   assign fallback values, CSS renderers <strong>must</strong> treat as
+   invalid (and <a
+   href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore as
+   appropriate</a>) any at-rules, properties, property values, keywords, and
+   other syntactic constructs for which they have no usable level of support.
+   In particular, user agents <strong>must not</strong> selectively ignore
+   unsupported component values and honor supported values in a single
+   multi-value property declaration: if any value is considered invalid (as
+   unsupported values must be), CSS requires that the entire declaration be
+   ignored.
+
+  <h3 id=experimental><span class=secno>11.4. </span> Experimental
+   Implementations</h3>
+
+  <p>To avoid clashes with future CSS features, the CSS2.1 specification
+   reserves a <a
+   href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
+   syntax</a> for proprietary and experimental extensions to CSS.
+
+  <p>Prior to a specification reaching the Candidate Recommendation stage in
+   the W3C process, all implementations of a CSS feature are considered
+   experimental. The CSS Working Group recommends that implementations use a
+   vendor-prefixed syntax for such features, including those in W3C Working
+   Drafts. This avoids incompatibilities with future changes in the draft.
+
+  <h3 id=testing><span class=secno>11.5. </span>Non-Experimental
+   Implementations</h3>
+
+  <p>Once a specification reaches the Candidate Recommendation stage,
+   non-experimental implementations are possible, and implementors should
+   release an unprefixed implementation of any CR-level feature they can
+   demonstrate to be correctly implemented according to spec.
+
+  <p>To establish and maintain the interoperability of CSS across
+   implementations, the CSS Working Group requests that non-experimental CSS
+   renderers submit an implementation report (and, if necessary, the
+   testcases used for that implementation report) to the W3C before releasing
+   an unprefixed implementation of any CSS features. Testcases submitted to
+   W3C are subject to review and correction by the CSS Working Group.
+
+  <p>Further information on submitting testcases and implementation reports
+   can be found from on the CSS Working Group's website at <a
+   href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
+   Questions should be directed to the <a
+   href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
+   mailing list.
+
+  <h3 id=cr-exit-criteria><span class=secno>11.6. </span> CR Exit Criteria</h3>
+
+  <p> For this specification to be advanced to Proposed Recommendation, there
+   must be at least two independent, interoperable implementations of each
+   feature. Each feature may be implemented by a different set of products,
+   there is no requirement that all features be implemented by a single
+   product. For the purposes of this criterion, we define the following
+   terms:
+
+  <dl>
+   <dt>independent
+
+   <dd>each implementation must be developed by a different party and cannot
+    share, reuse, or derive from code used by another qualifying
+    implementation. Sections of code that have no bearing on the
+    implementation of this specification are exempt from this requirement.
+
+   <dt>interoperable
+
+   <dd>passing the respective test case(s) in the official CSS test suite,
+    or, if the implementation is not a Web browser, an equivalent test. Every
+    relevant test in the test suite should have an equivalent test created if
+    such a user agent (UA) is to be used to claim interoperability. In
+    addition if such a UA is to be used to claim interoperability, then there
+    must one or more additional UAs which can also pass those equivalent
+    tests in the same way for the purpose of interoperability. The equivalent
+    tests must be made publicly available for the purposes of peer review.
+
+   <dt>implementation
+
+   <dd>a user agent which:
+    <ol class=inline>
+     <li>implements the specification.
+
+     <li>is available to the general public. The implementation may be a
+      shipping product or other publicly available version (i.e., beta
+      version, preview release, or “nightly build”). Non-shipping product
+      releases must have implemented the feature(s) for a period of at least
+      one month in order to demonstrate stability.
+
+     <li>is not experimental (i.e., a version specifically designed to pass
+      the test suite and is not intended for normal usage going forward).
+    </ol>
+  </dl>
+
+  <p>The specification will remain Candidate Recommendation for at least six
+   months.
+
   <h2 class=no-num id=acknowledgements> Appendix A: Acknowledgements</h2>
 
   <p>This specification would not have been possible without the help from:
@@ -5300,6 +5492,15 @@ <h3 class=no-num id=normative-ref>Normative references</h3>
     </dd>
    <!---->
 
+   <dt id=RFC2119>[RFC2119]
+
+   <dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key
+    words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet
+    RFC 2119. URL: <a
+    href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+    </dd>
+   <!---->
+
    <dt id=UAX11>[UAX11]
 
    <dd>Asmus Freytag. <a
diff --git a/css3-text/Overview.src.html b/css3-text/Overview.src.html
@@ -3943,6 +3943,175 @@ <h3 id="text-shadow">
       <code>::first-line</code> and <code>::first-letter</code>
       pseudo-elements.</p>
 
+<h2 id="conformance">
+Conformance</h2>
+
+<h3 id="conventions">
+Document Conventions</h3>
+
+  <p>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.
+  
+  <p>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="conformance-classes">
+Conformance Classes</h3>
+
+  <p>Conformance to CSS Text Level 3
+  is defined for three conformance classes:
+  <dl>
+    <dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
+      <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
+      style sheet</a>.
+    <dt><dfn>renderer</dfn></dt>
+      <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+      that interprets the semantics of a style sheet and renders
+      documents that use them.
+    <dt><dfn id="authoring-tool">authoring tool</dfn></dt>
+      <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+      that writes a style sheet.
+  </dl>
+  
+  <p>A style sheet is conformant to CSS Text Level 3
+  if all of its declarations that use properties defined in this module
+  have values that are valid according to the generic CSS grammar and the
+  individual grammars of each property as given in this module.
+  
+  <p>A renderer is conformant to CSS Text Level 3
+  if, in addition to interpreting the style sheet as defined by the
+  appropriate specifications, it supports all the features defined
+  by CSS Text Level 3 by parsing them correctly
+  and rendering the document accordingly. However, the inability of a
+  UA to correctly render a document due to limitations of the device
+  does not make the UA non-conformant. (For example, a UA is not
+  required to render color on a monochrome monitor.)
+  
+  <p>An authoring tool is conformant to CSS Text Level 3
+  if it writes style sheets that are syntactically correct according to the
+  generic CSS grammar and the individual grammars of each feature in
+  this module, and meet all other conformance requirements of style sheets
+  as described in this module.
+
+<h3 id="partial">
+Partial Implementations</h3>
+
+  <p>So that authors can exploit the forward-compatible parsing rules to
+  assign fallback values, CSS renderers <strong>must</strong>
+  treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
+  as appropriate</a>) any at-rules, properties, property values, keywords,
+  and other syntactic constructs for which they have no usable level of
+  support. In particular, user agents <strong>must not</strong> selectively
+  ignore unsupported component values and honor supported values in a single
+  multi-value property declaration: if any value is considered invalid
+  (as unsupported values must be), CSS requires that the entire declaration
+  be ignored.</p>
+  
+<h3 id="experimental">
+Experimental Implementations</h3>
+
+  <p>To avoid clashes with future CSS features, the CSS2.1 specification
+  reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
+  syntax</a> for proprietary and experimental extensions to CSS.
+  
+  <p>Prior to a specification reaching the Candidate Recommendation stage
+  in the W3C process, all implementations of a CSS feature are considered
+  experimental. The CSS Working Group recommends that implementations
+  use a vendor-prefixed syntax for such features, including those in
+  W3C Working Drafts. This avoids incompatibilities with future changes
+  in the draft.
+  </p>
+ 
+<h3 id="testing">Non-Experimental Implementations</h3>
+
+  <p>Once a specification reaches the Candidate Recommendation stage,
+  non-experimental implementations are possible, and implementors should
+  release an unprefixed implementation of any CR-level feature they
+  can demonstrate to be correctly implemented according to spec.
+  
+  <p>To establish and maintain the interoperability of CSS across
+  implementations, the CSS Working Group requests that non-experimental
+  CSS renderers submit an implementation report (and, if necessary, the
+  testcases used for that implementation report) to the W3C before
+  releasing an unprefixed implementation of any CSS features. Testcases
+  submitted to W3C are subject to review and correction by the CSS
+  Working Group.
+  
+  <p>Further information on submitting testcases and implementation reports
+  can be found from on the CSS Working Group's website at
+  <a href="http://www.w3.org/Style/CSS/Test/">http://www.w3.org/Style/CSS/Test/</a>.
+  Questions should be directed to the
+  <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">public-css-testsuite@w3.org</a>
+  mailing list.
+
+<h3 id="cr-exit-criteria">
+CR Exit Criteria</h3>
+
+  <p>
+  For this specification to be advanced to Proposed Recommendation,
+  there must be at least two independent, interoperable implementations
+  of each feature. Each feature may be implemented by a different set of
+  products, there is no requirement that all features be implemented by
+  a single product. For the purposes of this criterion, we define the
+  following terms:
+  
+  <dl>
+    <dt>independent <dd>each implementation must be developed by a
+    different party and cannot share, reuse, or derive from code
+    used by another qualifying implementation. Sections of code that
+    have no bearing on the implementation of this specification are
+    exempt from this requirement.
+  
+    <dt>interoperable <dd>passing the respective test case(s) in the
+    official CSS test suite, or, if the implementation is not a Web
+    browser, an equivalent test. Every relevant test in the test
+    suite should have an equivalent test created if such a user
+    agent (UA) is to be used to claim interoperability. In addition
+    if such a UA is to be used to claim interoperability, then there
+    must one or more additional UAs which can also pass those
+    equivalent tests in the same way for the purpose of
+    interoperability. The equivalent tests must be made publicly
+    available for the purposes of peer review.
+  
+    <dt>implementation <dd>a user agent which:
+  
+    <ol class=inline>
+      <li>implements the specification.
+  
+      <li>is available to the general public. The implementation may
+      be a shipping product or other publicly available version
+      (i.e., beta version, preview release, or “nightly build”). 
+      Non-shipping product releases must have implemented the
+      feature(s) for a period of at least one month in order to
+      demonstrate stability.
+  
+      <li>is not experimental (i.e., a version specifically designed
+      to pass the test suite and is not intended for normal usage
+      going forward).
+    </ol>
+  </dl>
+  
+  <p>The specification will remain Candidate Recommendation for at least
+  six months.
+
 <h2 class="no-num" id="acknowledgements">
   Appendix A: Acknowledgements</h2>
 
