fixed spec status

Rik Cabanier · svgeesus · commit 47803312eb19 · 2025-12-03T12:04:30.000-05:00
diff --git a/compositing-1/Makefile b/compositing-1/Makefile
@@ -33,7 +33,7 @@ CURLFLAGS=
 PUBMSG=
 PUBDATE=
 USER=
-STATUS="CR"
+STATUS="ED"
 
 W3C_CSS_DIR=~/work/W3C/cvs/dev.w3.org/csswg/compositing
 
diff --git a/compositing-1/index.html b/compositing-1/index.html
@@ -15,7 +15,7 @@
   <meta content="Rik Cabanier" name=dcterms.creator>
   <meta content="Nikos Andronikos" name=dcterms.creator>
   <meta content=W3C name=dcterms.publisher>
-  <meta content="http://www.w3.org/TR/2014/CR-compositing-1-20141022/"
+  <meta content="http://dev.w3.org/csswg/compositing-1/"
    name=dcterms.identifier>
   <meta content="text/html; charset=UTF-8" http-equiv=content-type>
   <style type="text/css">
@@ -220,7 +220,7 @@
        </style>
   <link href="style/alternate-spec-style.css" id=st
    rel="alternate stylesheet" title="alternate spec style" type="text/css">
-  <link href="http://www.w3.org/StyleSheets/TR/W3C-CR.css" rel=stylesheet
+  <link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=stylesheet
    type="text/css">
 
  <body>
@@ -230,8 +230,8 @@
 
    <h1>Compositing and Blending Level 1</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>W3C Candidate Recommendation
-    22 October 2014</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 22 October
+    2014</h2>
 
    <dl>
     <dt>This version:
@@ -2993,55 +2993,7 @@ <h3 class=no-ref id=testing> Non-experimental implementations</h3>
    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 class=no-ref 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. <!--end-conformance-->
+   mailing list. <!--end-conformance-->
 
   <h2 id=references1><span class=secno>13. </span>References</h2>
 
