@@ -18,7 +18,7 @@ <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
1818< dl >
1919 < dt > This version:</ dt >
2020 <!--
21- <dd><a href="http://www.w3.org/TR/[YEAR]/CR-css3-namespace-[CDATE]/ ">http://www.w3.org/TR/[YEAR]/CR -css3-namespace-[CDATE]/</a></dd>
21+ <dd><a href="[VERSION] ">http://www.w3.org/TR/[YEAR]/PR -css3-namespace-[CDATE]/</a></dd>
2222 -->
2323 < dd > < a href ="http://dev.w3.org/csswg/css3-namespace/ "> http://dev.w3.org/csswg/css3-namespace/</ a >
2424 < dt > Latest version:</ dt >
@@ -50,58 +50,13 @@ <h2 class="no-num no-toc" id="abstract">Abstract</h2>
5050< h2 class ="no-num no-toc " id ="status "> Status of this document</ h2 >
5151<!--status-->
5252
53- < p > For this specification to exit the CR stage, the following
54- conditions shall be met:</ p >
55-
56- < ol >
57- < li > < p > There must be at least two interoperable implementations. For
58- the purposes of this criterion, we define the following terms:</ p >
59-
60- < dl >
61- < dt > interoperable</ dt >
62-
63- < dd > < p > passing the respective test case(s) in the < a href ="http://www.w3.org/Style/CSS/Test/ "> CSS test suite</ a > ,
64- or, if the implementation is not a Web browser, an equivalent
65- test. Every relevant test in the test suite should have an
66- equivalent test created if such a user agent (UA) is to be used to claim
67- interoperability. In addition if such a UA is to be used to claim
68- interoperability, then there must one or more additional UAs which
69- can also pass those equivalent tests in the same way for the
70- purpose of interoperability. The equivalent tests must be made
71- publicly available for the purposes of peer review. </ p > </ dd >
72-
73- < dt > implementation</ dt >
74-
75- < dd > < p > a user agent which:</ p >
76-
77- < ol >
78- < li > implements the specification.</ li >
79-
80- < li > is available (i.e. publicly downloadable or available
81- through some other public point of sale mechanism). This is the
82- "show me" requirement.</ li >
83-
84- < li > is shipped, or is a "nightly build" (i.e., a development version
85- for the next release), but is not experimental (i.e., a version
86- specifically designed to pass the test suite and not intended for
87- daily usage going forward).</ li > </ ol > </ dd > </ dl > </ li >
88-
89- < li > < p > A minimum of another three months of the CR period must elapse.
90- That is, this specification will not exit CR before 23 August 2008.
91- When the specification exits CR, an implementation report will be
92- published. At this point, no such report exists.</ p > </ li >
93-
94- < li > < p > The specified technology must not be harmful for
95- accessibility.</ p > </ li > </ ol >
9653
9754< p > A CSS Namespace < a href ="http://www.w3.org/Style/CSS/Test/ "> Test Suite</ a >
98- will be developed during the Candidate Recommendation phase of this CSS
55+ has been developed during the Candidate Recommendation phase of this CSS
9956 Namespaces specification.</ p >
10057
101- < p > Comments on and subsequent changes since the last Working Draft are
102- listed in the separate < a
103- href ="http://dev.w3.org/csswg/css3-namespace/issues-2 "> Disposition
104- of Comments.</ a > </ p >
58+ < p > This document is the same as the previous, Candidate Recommendation
59+ version, except for editorial changes.</ p >
10560
10661< h2 class ="no-num no-toc " id ="contents "> Table of contents</ h2 >
10762<!--toc-->
0 commit comments