remove reference to css3page, added CR exit criteria

Author: howcom

css3-multicol/Overview.src.html

@@ -217,7 +217,7 @@ <h2>Introduction</h2>
 }
 </pre>
 
-<p>The properties and values used in this example are formally defined in [[!CSS3PAGE]].
+<!--<p>The properties and values used in this example are formally defined in [[!CSS3PAGE]].-->
 
 </div>
 
@@ -1638,6 +1638,71 @@ <h2>Conformance</h2>
     and notes. [[!RFC2119]]</p>
 
 
+<h3>CR exit criteria</h3>
+
+<p>As described in the W3C process document, a <a
+href="http://www.w3.org/2005/10/Process-20051014/tr.html#cfi">Candidate
+Recommendation</a> (CR) is a specification that W3C recommends for use
+on the Web. The next stage is <em>Recommendation</em>, when the
+specification is sufficiently implemented.
+
+<p>For this specification to be proposed as a W3C Recommendation, the
+following conditions shall be met. 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 <em>nightly build</em>). 
+    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>A minimum of sixth months of the CR period must have elapsed. This
+is to ensure that enough time is given for any remaining major errors
+to be caught.
+
+<p>Features will be dropped if two or more interoperable
+implementations are not found by the end of the CR period.
+
+<p>Features may/will also be dropped if adequate/sufficient (by
+judgment of CSS WG) tests have not been produced for those feature(s)
+by the end of the CR period.
+
+
+
+
 <h2 class=no-num id=acknowledgments>Acknowledgments</h2>
 
 <p>This document is based on several older proposals and comments on