[css3-fonts] tweaks to CR draft

Author: John Daggett

css-fonts/Overview.html

@@ -250,6 +250,13 @@ <h2 class="no-num no-toc" id=status>Status of this document</h2>
    section 6 of the W3C Patent Policy</a>.</p>
   <!--end-status-->
 
+  <p>See the section <a href="#cr-exit-criteria">CR Exit Criteria</a> for
+   details on advancing this specification to W3C Recommendation. The
+   specification will remain Candidate Recommendation at least until 1 April
+   2014. A <a
+   href="http://test.csswg.org/suites/css3-fonts/nightly-unstable/report/">test
+   suite and implementation report</a> are under development.
+
   <h3 class="no-num no-toc" id=atrisk>Features at risk</h3>
 
   <p>The following features are at risk and may be removed when exiting CR:
@@ -466,6 +473,9 @@ <h2 class="no-num no-toc" id=contents>Table of contents</h2>
 
      <li class=no-num><a href="#testing"> Non-Experimental
       Implementations</a>
+
+     <li><a href="#cr-exit-criteria"><span class=secno>8.3 </span>CR Exit
+      Criteria</a>
     </ul>
 
    <li class=no-num><a href="#references">References</a>
@@ -6142,6 +6152,57 @@ <h3 class=no-num id=testing> Non-Experimental Implementations</h3>
    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>8.3 </span>CR Exit Criteria</h3>
+
+  <p class=replaceme>Remove this section unless/until the module is in CR.</p>
+  <!-- This text was <a href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on 2008-06-04.</a> -->
+
+  <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=references>References</h2>
 
   <h3 class=no-num id=normative-references>Normative References</h3>
@@ -7347,12 +7408,3 @@ <h2 class=no-num id=property-index>Property index</h2>
 sgml-local-ecat-files:nil
 End:
 -->
-<!--
-
-to do:
-
-- wording of OpenType family name handling
-- handling combining sequences in the font matching algorithm
-- fix-up fi ligature example
-
--->