Add CR exit criteria

Fri, 03 Sep 2010 00:33:34 +0000

author
Elika Etemad <fantasai.cvs@inkedblade.net>
date
Fri, 03 Sep 2010 00:33:34 +0000
changeset 1953
41226843561b
parent 1952
3faf018b5fdc
child 1954
6168d0497c4a

Add CR exit criteria

css-style-attr/Overview.html file | annotate | diff | comparison | revisions
css-style-attr/Overview.src.html file | annotate | diff | comparison | revisions
     1.1 --- a/css-style-attr/Overview.html	Thu Sep 02 22:42:46 2010 +0000
     1.2 +++ b/css-style-attr/Overview.html	Fri Sep 03 00:33:34 2010 +0000
     1.3 @@ -15,11 +15,12 @@
     1.4  
     1.5     <h1>CSS Styling Attributes Level 1</h1>
     1.6  
     1.7 -   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 25 August 2010</h2>
     1.8 +   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 3 September
     1.9 +    2010</h2>
    1.10  
    1.11     <dl>
    1.12      <dt>This version:</dt>
    1.13 -    <!-- <dd><dd><a href="http://www.w3.org/TR/2010/WD-css-style-attr-20100825/">http://www.w3.org/TR/2010/WD-css-style-attr-20100825/</a></dd> -->
    1.14 +    <!-- <dd><dd><a href="http://www.w3.org/TR/2010/WD-css-style-attr-20100903/">http://www.w3.org/TR/2010/WD-css-style-attr-20100903/</a></dd> -->
    1.15  
    1.16      <dd><a
    1.17       href="http://dev.w3.org/csswg/css-style-attr/">http://dev.w3.org/csswg/css-style-attr/</a>
    1.18 @@ -129,12 +130,54 @@
    1.19     W3C Patent Policy</a>.</p>
    1.20    <!--end-status-->
    1.21  
    1.22 -  <p>This specification is a <strong>Last Call Working Draft</strong>. All
    1.23 -   persons are encouraged to review this document and <strong>send comments
    1.24 -   to the <a
    1.25 -   href="http://lists.w3.org/Archives/Public/www-style/">www-style</a>
    1.26 -   mailing list</strong> as described above. The <strong>deadline for
    1.27 -   comments</strong> is <strong>9 February 2010</strong>.
    1.28 +  <p>For this specification to exit the CR stage, the following conditions
    1.29 +   shall be met:
    1.30 +
    1.31 +  <ol>
    1.32 +   <li>
    1.33 +    <p>There must be at least two interoperable implementations. For the
    1.34 +     purposes of this criterion, we define the following terms:</p>
    1.35 +
    1.36 +    <dl>
    1.37 +     <dt>interoperable
    1.38 +
    1.39 +     <dd>
    1.40 +      <p>passing the respective test case(s) in the <a
    1.41 +       href="http://www.w3.org/Style/CSS/Test/">CSS test suite</a>, or, if
    1.42 +       the implementation is not a Web browser, an equivalent test. Every
    1.43 +       relevant test in the test suite should have an equivalent test created
    1.44 +       if such a user agent (UA) is to be used to claim interoperability. In
    1.45 +       addition if such a UA is to be used to claim interoperability, then
    1.46 +       there must one or more additional UAs which can also pass those
    1.47 +       equivalent tests in the same way for the purpose of interoperability.
    1.48 +       The equivalent tests must be made publicly available for the purposes
    1.49 +       of peer review.</p>
    1.50 +
    1.51 +     <dt>implementation
    1.52 +
    1.53 +     <dd>
    1.54 +      <p>a user agent which:</p>
    1.55 +
    1.56 +      <ol>
    1.57 +       <li>implements the specification.
    1.58 +
    1.59 +       <li>is available (i.e. publicly downloadable or available through some
    1.60 +        other public point of sale mechanism). This is the "show me"
    1.61 +        requirement.
    1.62 +
    1.63 +       <li>is shipped, or is a "nightly build" (i.e., a development version
    1.64 +        for the next release), but is not experimental (i.e., a version
    1.65 +        specifically designed to pass the test suite and not intended for
    1.66 +        daily usage going forward).
    1.67 +      </ol>
    1.68 +    </dl>
    1.69 +
    1.70 +   <li>
    1.71 +    <p>A minimum of three months of the CR period must elapse. That is, this
    1.72 +     specification will not exit CR before XXX INSERT DATE HERE. When the
    1.73 +     specification exits CR, an implementation report will be published. At
    1.74 +     this point, no such report exists.</p>
    1.75 +  </ol>
    1.76  
    1.77    <p>A CSS Styling Attribute <a href="http://www.w3.org/Style/CSS/Test/">Test
    1.78     Suite</a> will be developed during the Candidate Recommendation phase of
     2.1 --- a/css-style-attr/Overview.src.html	Thu Sep 02 22:42:46 2010 +0000
     2.2 +++ b/css-style-attr/Overview.src.html	Fri Sep 03 00:33:34 2010 +0000
     2.3 @@ -55,12 +55,54 @@
     2.4  
     2.5  <h2 class="no-num no-toc" id="status">Status of this document</h2>
     2.6  <!--status-->
     2.7 -  <p>This specification is a <strong>Last Call Working Draft</strong>. All
     2.8 -   persons are encouraged to review this document and <strong>send comments
     2.9 -   to the <a
    2.10 -   href="http://lists.w3.org/Archives/Public/www-style/">www-style</a>
    2.11 -   mailing list</strong> as described above. The <strong>deadline for
    2.12 -   comments</strong> is <strong>9 February 2010</strong>.
    2.13 +  <p>For this specification to exit the CR stage, the following conditions
    2.14 +   shall be met:
    2.15 +
    2.16 +  <ol>
    2.17 +   <li>
    2.18 +    <p>There must be at least two interoperable implementations. For the
    2.19 +     purposes of this criterion, we define the following terms:</p>
    2.20 +
    2.21 +    <dl>
    2.22 +     <dt>interoperable
    2.23 +
    2.24 +     <dd>
    2.25 +      <p>passing the respective test case(s) in the <a
    2.26 +       href="http://www.w3.org/Style/CSS/Test/">CSS test suite</a>, or, if
    2.27 +       the implementation is not a Web browser, an equivalent test. Every
    2.28 +       relevant test in the test suite should have an equivalent test created
    2.29 +       if such a user agent (UA) is to be used to claim interoperability. In
    2.30 +       addition if such a UA is to be used to claim interoperability, then
    2.31 +       there must one or more additional UAs which can also pass those
    2.32 +       equivalent tests in the same way for the purpose of interoperability.
    2.33 +       The equivalent tests must be made publicly available for the purposes
    2.34 +       of peer review.</p>
    2.35 +
    2.36 +     <dt>implementation
    2.37 +
    2.38 +     <dd>
    2.39 +      <p>a user agent which:</p>
    2.40 +
    2.41 +      <ol>
    2.42 +       <li>implements the specification.
    2.43 +
    2.44 +       <li>is available (i.e. publicly downloadable or available through some
    2.45 +        other public point of sale mechanism). This is the "show me"
    2.46 +        requirement.
    2.47 +
    2.48 +       <li>is shipped, or is a "nightly build" (i.e., a development version
    2.49 +        for the next release), but is not experimental (i.e., a version
    2.50 +        specifically designed to pass the test suite and not intended for
    2.51 +        daily usage going forward).
    2.52 +      </ol>
    2.53 +    </dl>
    2.54 +
    2.55 +   <li>
    2.56 +    <p>A minimum of three months of the CR period must elapse. That
    2.57 +     is, this specification will not exit CR before XXX INSERT DATE HERE. When the
    2.58 +     specification exits CR, an implementation report will be published. At
    2.59 +     this point, no such report exists.</p>
    2.60 +  </ol>
    2.61  
    2.62    <p>A CSS Styling Attribute <a href="http://www.w3.org/Style/CSS/Test/">Test
    2.63     Suite</a> will be developed during the Candidate Recommendation phase of

mercurial