- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 29 Aug 2011 06:26:13 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-writing-modes
In directory hutz:/tmp/cvs-serv8696
Modified Files:
Overview.html Overview.src.html
Log Message:
Add conformance section, fix validation errors, prep for WD
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.html,v
retrieving revision 1.204
retrieving revision 1.205
diff -u -d -r1.204 -r1.205
--- Overview.html 29 Aug 2011 05:43:28 -0000 1.204
+++ Overview.html 29 Aug 2011 06:26:11 -0000 1.205
@@ -22,7 +22,7 @@
margin:auto;
}
</style>
- <link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=stylesheet
+ <link href="http://www.w3.org/StyleSheets/TR/W3C-WD.css" rel=stylesheet
type="text/css">
<body>
@@ -32,16 +32,17 @@
<h1>CSS Writing Modes Module Level 3</h1>
- <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 29 August 2011</h2>
+ <h2 class="no-num no-toc" id=longstatus-date>W3C Working Draft 31 August
+ 2011</h2>
<dl>
- <dt>This version:
+ <dt>This version:</dt>
+ <!--
+ <dd><a href="http://dev.w3.org/csswg/css3-writing-modes/">http://dev.w3.org/csswg/css3-writing-modes/</a>
+-->
<dd><a
- href="http://dev.w3.org/csswg/css3-writing-modes/">http://dev.w3.org/csswg/css3-writing-modes/</a>
- <!--
- <dd><a href="http://www.w3.org/TR/2011/WD-css3-writing-modes-20110829">http://www.w3.org/TR/2011/ED-css3-writing-modes-20110829/</a>
--->
+ href="http://www.w3.org/TR/2011/WD-css3-writing-modes-20110831">http://www.w3.org/TR/2011/WD-css3-writing-modes-20110831/</a>
<dt>Latest version:
@@ -113,36 +114,42 @@
<h2 class="no-num no-toc" id=status> Status of this document</h2>
<!--begin-status-->
- <p>This is a public copy of the editors' draft. It is provided for
- discussion only and may change at any moment. Its publication here does
- not imply endorsement of its contents by W3C. Don't cite this document
- other than as work in progress.
+ <p><em>This section describes the status of this document at the time of
+ its publication. Other documents may supersede this document. A list of
+ current W3C publications and the latest revision of this technical report
+ can be found in the <a href="http://www.w3.org/TR/">W3C technical reports
+ index at http://www.w3.org/TR/.</a></em>
+
+ <p>Publication as a Working Draft does not imply endorsement by the W3C
+ Membership. This is a draft document and may be updated, replaced or
+ obsoleted by other documents at any time. It is inappropriate to cite this
+ document as other than work in progress.
<p>The (<a
href="http://lists.w3.org/Archives/Public/www-style/">archived</a>) public
- mailing list <a
- href="mailto:www-style@w3.org?Subject=%5Bcss3-writing-modes%5D%20PUT%20SUBJECT%20HERE">
- www-style@w3.org</a> (see <a
- href="http://www.w3.org/Mail/Request">instructions</a>) is preferred for
- discussion of this specification. When sending e-mail, please put the text
- “css3-writing-modes” in the subject, preferably like this:
- “[<!---->css3-writing-modes<!---->] <em>…summary of
+ mailing list <a href="mailto:www-style@w3.org">www-style@w3.org</a> (see
+ <a href="http://www.w3.org/Mail/Request">instructions</a>) is preferred
+ for discussion of this specification. When sending e-mail, please put the
+ text “css3-writing-modes” in the subject, preferably like
+ this: “[<!---->css3-writing-modes<!---->] <em>…summary of
comment…</em>”
- <p>This document was produced by the <a href="/Style/CSS/members">CSS
- Working Group</a> (part of the <a href="/Style/">Style Activity</a>).
+ <p>This document was produced by the <a
+ href="http://www.w3.org/Style/CSS/members">CSS Working Group</a> (part of
+ the <a href="http://www.w3.org/Style/">Style Activity</a>).
<p>This document was produced by a group operating under the <a
- href="/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent
- Policy</a>. W3C maintains a <a href="/2004/01/pp-impl/32061/status"
+ href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
+ 2004 W3C Patent Policy</a>. W3C maintains a <a
+ href="http://www.w3.org/2004/01/pp-impl/32061/status"
rel=disclosure>public list of any patent disclosures</a> made in
connection with the deliverables of the group; that page also includes
instructions for disclosing a patent. An individual who has actual
knowledge of a patent which the individual believes contains <a
- href="/Consortium/Patent-Policy-20040205/#def-essential">Essential
+ href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a
- href="/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the
- W3C Patent Policy</a>.</p>
+ href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+ 6 of the W3C Patent Policy</a>.</p>
<!--end-status-->
<p>The following features are at-risk and may be dropped during CR:
@@ -161,7 +168,7 @@
href="#text-combine-horizontal0"><code
class=property>text-combine-horizontal</code></a>’.
- <li>The ‘<a href="#text-combine-mode"><code
+ <li>The ‘<a href="#text-combine-mode0"><code
class=property>text-combine-mode</code></a>’ property
</ul>
@@ -175,10 +182,7 @@
<li><a href="#placement"><span class=secno>1.1. </span> Module
Interactions</a>
- <li><a href="#conventions"><span class=secno>1.2. </span> Document
- Conventions</a>
-
- <li><a href="#values"><span class=secno>1.3. </span> Values</a>
+ <li><a href="#values"><span class=secno>1.2. </span> Values</a>
</ul>
<li><a href="#text-direction"><span class=secno>2. </span> Inline
@@ -301,7 +305,7 @@
Horizonal-in-Vertical Composition: the ‘<code
class=property>text-combine-horizontal</code>’ property</a>
- <li><a href="#text-combine-horizontal"><span class=secno>9.2. </span>
+ <li><a href="#text-combine-mode"><span class=secno>9.2. </span>
Horizonal-in-Vertical Glyph Scaling: the ‘<code
class=property>text-combine-mode</code>’ property</a>
</ul>
@@ -313,6 +317,27 @@
Draft">WD</abbr></a>
</ul>
+ <li><a href="#conformance"><span class=secno>10. </span> Conformance</a>
+ <ul class=toc>
+ <li><a href="#conventions"><span class=secno>10.1. </span> Document
+ Conventions</a>
+
+ <li><a href="#conformance-classes"><span class=secno>10.2. </span>
+ Conformance Classes</a>
+
+ <li><a href="#partial"><span class=secno>10.3. </span> Partial
+ Implementations</a>
+
+ <li><a href="#experimental"><span class=secno>10.4. </span> Experimental
+ Implementations</a>
+
+ <li><a href="#testing"><span class=secno>10.5. </span>Non-Experimental
+ Implementations</a>
+
+ <li><a href="#cr-exit-criteria"><span class=secno>10.6. </span> CR Exit
+ Criteria</a>
+ </ul>
+
<li class=no-num><a href="#acknowledgements"> Acknowledgements</a>
<li class=no-num><a href="#character-properties">Appendix A. Characters
@@ -455,34 +480,7 @@
href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> sections 8.6
and 9.10.
- <h3 id=conventions><span class=secno>1.2. </span> Document Conventions</h3>
-
- <p>Conformance requirements are expressed with a combination of descriptive
- assertions and RFC 2119 terminology. The key words “MUST”, “MUST
- NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
- “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the
- normative parts of this document are to be interpreted as described in RFC
- 2119. However, for readability, these words do not appear in all uppercase
- letters in this specification.
-
- <p>All of the text of this specification is normative except sections
- explicitly marked as non-normative, examples, and notes. <a
- href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a>
-
- <p>Examples in this specification are introduced with the words “for
- example” or are set apart from the normative text with
- <code>class="example"</code>, like this:
-
- <div class=example>
- <p>This is an example of an informative example.</p>
- </div>
-
- <p>Informative notes begin with the word “Note” and are set apart from
- the normative text with <code>class="note"</code>, like this:
-
- <p class=note>Note, this is an informative note.
-
- <h3 id=values><span class=secno>1.3. </span> Values</h3>
+ <h3 id=values><span class=secno>1.2. </span> Values</h3>
<p>This specification follows the <a
href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
@@ -2035,12 +2033,12 @@
<p>The following table summarizes the abstract-to-physical mappings:
<table class="complex data">
+ <caption>Abstract-Physical Mapping</caption>
+
<colgroup class=header></colgroup>
<colgroup span=10></colgroup>
- <caption>Abstract-Physical Mapping</caption>
-
<thead>
<tr>
<th scope=row>‘<a href="#writing-mode1"><code
@@ -3038,9 +3036,9 @@
</div>
</div>
- <h3 id=text-combine-horizontal><span class=secno>9.2. </span>
+ <h3 id=text-combine-mode><span class=secno>9.2. </span>
Horizonal-in-Vertical Glyph Scaling: the ‘<a
- href="#text-combine-mode"><code
+ href="#text-combine-mode0"><code
class=property>text-combine-mode</code></a>’ property</h3>
<table class=propdef>
@@ -3048,7 +3046,7 @@
<tr>
<th>Name:
- <td><dfn id=text-combine-mode>text-combine-mode</dfn>
+ <td><dfn id=text-combine-mode0>text-combine-mode</dfn>
<tr>
<th>Value:
@@ -3180,7 +3178,7 @@
class=property>text-combine-horizontal</code></a>’ and added
ability to auto-combine by character classes.
- <li>Added ‘<a href="#text-combine-mode"><code
+ <li>Added ‘<a href="#text-combine-mode0"><code
class=property>text-combine-mode</code></a>’ property to control
scaling method used to compose horizontal-in-vertical text.
@@ -3188,6 +3186,182 @@
Properties</a>.
</ul>
+ <h2 id=conformance><span class=secno>10. </span> Conformance</h2>
+
+ <h3 id=conventions><span class=secno>10.1. </span> Document Conventions</h3>
+
+ <p>Conformance requirements are expressed with a combination of descriptive
+ assertions and RFC 2119 terminology. The key words “MUST”, “MUST
+ NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”,
+ “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the
+ normative parts of this document are to be interpreted as described in RFC
+ 2119. However, for readability, these words do not appear in all uppercase
+ letters in this specification.
+
+ <p>All of the text of this specification is normative except sections
+ explicitly marked as non-normative, examples, and notes. <a
+ href="#RFC2119" rel=biblioentry>[RFC2119]<!--{{!RFC2119}}--></a>
+
+ <p>Examples in this specification are introduced with the words “for
+ example” or are set apart from the normative text with
+ <code>class="example"</code>, like this:
+
+ <div class=example>
+ <p>This is an example of an informative example.</p>
+ </div>
+
+ <p>Informative notes begin with the word “Note” and are set apart from
+ the normative text with <code>class="note"</code>, like this:
+
+ <p class=note>Note, this is an informative note.
+
+ <h3 id=conformance-classes><span class=secno>10.2. </span> Conformance
+ Classes</h3>
+
+ <p>Conformance to CSS Writing Modes is defined for three conformance
+ classes:
+
+ <dl>
+ <dt><dfn id=style-sheet title="style sheet!!as conformance class">style
+ sheet</dfn>
+
+ <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
+ style sheet</a>.
+
+ <dt><dfn id=renderer>renderer</dfn>
+
+ <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+ that interprets the semantics of a style sheet and renders documents that
+ use them.
+
+ <dt><dfn id=authoring-tool>authoring tool</dfn>
+
+ <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+ that writes a style sheet.
+ </dl>
+
+ <p>A style sheet is conformant to CSS Writing Modes if all of its
+ declarations that use properties defined in this module have values that
+ are valid according to the generic CSS grammar and the individual grammars
+ of each property as given in this module.
+
+ <p>A renderer is conformant to CSS Writing Modes if, in addition to
+ interpreting the style sheet as defined by the appropriate specifications,
+ it supports all the features defined by CSS Writing Modes by parsing them
+ correctly and rendering the document accordingly. However, the inability
+ of a UA to correctly render a document due to limitations of the device
+ does not make the UA non-conformant. (For example, a UA is not required to
+ render color on a monochrome monitor.)
+
+ <p>An authoring tool is conformant to CSS Writing Modes if it writes style
+ sheets that are syntactically correct according to the generic CSS grammar
+ and the individual grammars of each feature in this module, and meet all
+ other conformance requirements of style sheets as described in this
+ module.
+
+ <h3 id=partial><span class=secno>10.3. </span> Partial Implementations</h3>
+
+ <p>So that authors can exploit the forward-compatible parsing rules to
+ assign fallback values, CSS renderers <strong>must</strong> treat as
+ invalid (and <a
+ href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore as
+ appropriate</a>) any at-rules, properties, property values, keywords, and
+ other syntactic constructs for which they have no usable level of support.
+ In particular, user agents <strong>must not</strong> selectively ignore
+ unsupported component values and honor supported values in a single
+ multi-value property declaration: if any value is considered invalid (as
+ unsupported values must be), CSS requires that the entire declaration be
+ ignored.
+
+ <h3 id=experimental><span class=secno>10.4. </span> Experimental
+ Implementations</h3>
+
+ <p>To avoid clashes with future CSS features, the CSS2.1 specification
+ reserves a <a
+ href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
+ syntax</a> for proprietary and experimental extensions to CSS.
+
+ <p>Prior to a specification reaching the Candidate Recommendation stage in
+ the W3C process, all implementations of a CSS feature are considered
+ experimental. The CSS Working Group recommends that implementations use a
+ vendor-prefixed syntax for such features, including those in W3C Working
+ Drafts. This avoids incompatibilities with future changes in the draft.
+
+ <h3 id=testing><span class=secno>10.5. </span>Non-Experimental
+ Implementations</h3>
+
+ <p>Once a specification reaches the Candidate Recommendation stage,
+ non-experimental implementations are possible, and implementors should
+ release an unprefixed implementation of any CR-level feature they can
+ demonstrate to be correctly implemented according to spec.
+
+ <p>To establish and maintain the interoperability of CSS across
+ implementations, the CSS Working Group requests that non-experimental CSS
+ renderers submit an implementation report (and, if necessary, the
+ testcases used for that implementation report) to the W3C before releasing
+ an unprefixed implementation of any CSS features. Testcases submitted to
+ W3C are subject to review and correction by the CSS Working Group.
+
+ <p>Further information on submitting testcases and implementation reports
+ can be found from on the CSS Working Group's website at <a
+ 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 id=cr-exit-criteria><span class=secno>10.6. </span> CR Exit Criteria</h3>
+
+ <p class=issue>[Change or remove the following CR exit criteria if the spec
+ is not a module, but, e.g., a Note or a profile. 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=acknowledgements> Acknowledgements</h2>
<p>John Daggett, Martin Heijdra, Yasuo Kida, Tatsuo Kobayashi, Toshi
@@ -3372,7 +3546,7 @@
<p class=issue>This section needs careful review. Please send feedback and
suggestions for improvement, particularly for the <a
- href="http://unicode.org/cldr/utility/list-unicodeset.jsp?a=\p{Block%3DGeneral+Punctuation}%26[%3AGeneral_category%3DPo%3A]%0D%0A&g=">U+2016–U+205F</a>
+ href="http://unicode.org/cldr/utility/list-unicodeset.jsp?a=\p{Block%3DGeneral+Punctuation}%26[%3AGeneral_category%3DPo%3A]%0D%0A&g=">U+2016–U+205F</a>
range.
<p>When ‘<a href="#text-orientation0"><code
@@ -4103,7 +4277,7 @@
<td>visual
<tr>
- <th><a class=property href="#text-combine-mode">text-combine-mode</a>
+ <th><a class=property href="#text-combine-mode0">text-combine-mode</a>
<td>auto | compress | [ no-compress || use-glyphs ]
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.src.html,v
retrieving revision 1.215
retrieving revision 1.216
diff -u -d -r1.215 -r1.216
--- Overview.src.html 29 Aug 2011 05:43:28 -0000 1.215
+++ Overview.src.html 29 Aug 2011 06:26:11 -0000 1.216
@@ -34,11 +34,11 @@
<h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
<dl>
<dt>This version:</dt>
-
- <dd><a href="http://dev.w3.org/csswg/css3-writing-modes/">http://dev.w3.org/csswg/css3-writing-modes/</a>
<!--
- <dd><a href="http://www.w3.org/TR/[YEAR]/WD-[SHORTNAME]-[CDATE]">[VERSION]</a>
+ <dd><a href="http://dev.w3.org/csswg/css3-writing-modes/">http://dev.w3.org/csswg/css3-writing-modes/</a>
-->
+ <dd><a href="http://www.w3.org/TR/[YEAR]/WD-[SHORTNAME]-[CDATE]">[VERSION]</a>
+
<dt>Latest version:</dt>
<dd><a
href="http://www.w3.org/TR/css3-writing-modes/">http://www.w3.org/TR/css3-writing-modes/</a></dd>
@@ -179,33 +179,6 @@
<p>This module replaces and extends the 'unicode-bidi' and 'direction'
features defined in [[!CSS21]] sections 8.6 and 9.10.
-<h3 id="conventions">
-Document Conventions</h3>
-
- <p>Conformance requirements are expressed with a combination of
- descriptive assertions and RFC 2119 terminology. The key words “MUST”,
- “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
- “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
- document are to be interpreted as described in RFC 2119.
- However, for readability, these words do not appear in all uppercase
- letters in this specification.
-
- <p>All of the text of this specification is normative except sections
- explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
-
- <p>Examples in this specification are introduced with the words “for example”
- or are set apart from the normative text with <code>class="example"</code>,
- like this:
-
- <div class="example">
- <p>This is an example of an informative example.</p>
- </div>
-
- <p>Informative notes begin with the word “Note” and are set apart from the
- normative text with <code>class="note"</code>, like this:
-
- <p class="note">Note, this is an informative note.</p>
-
<h3 id="values">
Values</h3>
@@ -1481,9 +1454,9 @@
<p>The following table summarizes the abstract-to-physical mappings:</p>
<table class="complex data">
+ <caption>Abstract-Physical Mapping</caption>
<colgroup class="header"></colgroup>
<colgroup span=10></colgroup>
- <caption>Abstract-Physical Mapping</caption>
<thead>
<tr>
<th scope="row">'writing-mode'</th>
@@ -2269,7 +2242,7 @@
</div>
</div>
-<h3 id="text-combine-horizontal">
+<h3 id="text-combine-mode">
Horizonal-in-Vertical Glyph Scaling: the 'text-combine-mode' property</h3>
<table class="propdef">
@@ -2368,6 +2341,179 @@
<li>Added appendix on <a href="#character-properties">Characters and Properties</a>.
</ul>
+<h2 id="conformance">
+Conformance</h2>
+
+<h3 id="conventions">
+Document Conventions</h3>
+
+ <p>Conformance requirements are expressed with a combination of
+ descriptive assertions and RFC 2119 terminology. The key words “MUST”,
+ “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
+ “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
+ document are to be interpreted as described in RFC 2119.
+ However, for readability, these words do not appear in all uppercase
+ letters in this specification.
+
+ <p>All of the text of this specification is normative except sections
+ explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p>
+
+ <p>Examples in this specification are introduced with the words “for example”
+ or are set apart from the normative text with <code>class="example"</code>,
+ like this:
+
+ <div class="example">
+ <p>This is an example of an informative example.</p>
+ </div>
+
+ <p>Informative notes begin with the word “Note” and are set apart from the
+ normative text with <code>class="note"</code>, like this:
+
+ <p class="note">Note, this is an informative note.</p>
+
+<h3 id="conformance-classes">
+Conformance Classes</h3>
+
+ <p>Conformance to CSS Writing Modes
+ is defined for three conformance classes:
+ <dl>
+ <dt><dfn title="style sheet!!as conformance class">style sheet</dfn>
+ <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#style-sheet">CSS
+ style sheet</a>.
+ <dt><dfn>renderer</dfn></dt>
+ <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+ that interprets the semantics of a style sheet and renders
+ documents that use them.
+ <dt><dfn id="authoring-tool">authoring tool</dfn></dt>
+ <dd>A <a href="http://www.w3.org/TR/CSS21/conform.html#user-agent">UA</a>
+ that writes a style sheet.
+ </dl>
+
+ <p>A style sheet is conformant to CSS Writing Modes
+ if all of its declarations that use properties defined in this module
+ have values that are valid according to the generic CSS grammar and the
+ individual grammars of each property as given in this module.
+
+ <p>A renderer is conformant to CSS Writing Modes
+ if, in addition to interpreting the style sheet as defined by the
+ appropriate specifications, it supports all the features defined
+ by CSS Writing Modes by parsing them correctly
+ and rendering the document accordingly. However, the inability of a
+ UA to correctly render a document due to limitations of the device
+ does not make the UA non-conformant. (For example, a UA is not
+ required to render color on a monochrome monitor.)
+
+ <p>An authoring tool is conformant to CSS Writing Modes
+ if it writes style sheets that are syntactically correct according to the
+ generic CSS grammar and the individual grammars of each feature in
+ this module, and meet all other conformance requirements of style sheets
+ as described in this module.
+
+<h3 id="partial">
+Partial Implementations</h3>
+
+ <p>So that authors can exploit the forward-compatible parsing rules to
+ assign fallback values, CSS renderers <strong>must</strong>
+ treat as invalid (and <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignore
+ as appropriate</a>) any at-rules, properties, property values, keywords,
+ and other syntactic constructs for which they have no usable level of
+ support. In particular, user agents <strong>must not</strong> selectively
+ ignore unsupported component values and honor supported values in a single
+ multi-value property declaration: if any value is considered invalid
+ (as unsupported values must be), CSS requires that the entire declaration
+ be ignored.</p>
+
+<h3 id="experimental">
+Experimental Implementations</h3>
+
+ <p>To avoid clashes with future CSS features, the CSS2.1 specification
+ reserves a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
+ syntax</a> for proprietary and experimental extensions to CSS.
+
+ <p>Prior to a specification reaching the Candidate Recommendation stage
+ in the W3C process, all implementations of a CSS feature are considered
+ experimental. The CSS Working Group recommends that implementations
+ use a vendor-prefixed syntax for such features, including those in
+ W3C Working Drafts. This avoids incompatibilities with future changes
+ in the draft.
+ </p>
+
+<h3 id="testing">Non-Experimental Implementations</h3>
+
+ <p>Once a specification reaches the Candidate Recommendation stage,
+ non-experimental implementations are possible, and implementors should
+ release an unprefixed implementation of any CR-level feature they
+ can demonstrate to be correctly implemented according to spec.
+
+ <p>To establish and maintain the interoperability of CSS across
+ implementations, the CSS Working Group requests that non-experimental
+ CSS renderers submit an implementation report (and, if necessary, the
+ testcases used for that implementation report) to the W3C before
+ releasing an unprefixed implementation of any CSS features. Testcases
+ submitted to W3C are subject to review and correction by the CSS
+ Working Group.
+
+ <p>Further information on submitting testcases and implementation reports
+ can be found from on the CSS Working Group's website at
+ <a 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 id="cr-exit-criteria">
+CR Exit Criteria</h3>
+
+ <p class=issue>[Change or remove the following CR exit criteria if
+ the spec is not a module, but, e.g., a Note or a profile. This text was <a
+ href="http://www.w3.org/Style/CSS/Tracker/actions/44"> decided on 2008-06-04.</a>]</p>
+
+ <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="acknowledgements">
Acknowledgements</h2>
@@ -2474,7 +2620,7 @@
<p class="issue">This section needs careful review. Please send feedback
and suggestions for improvement, particularly for the
- <a href="http://unicode.org/cldr/utility/list-unicodeset.jsp?a=\p{Block%3DGeneral+Punctuation}%26[%3AGeneral_category%3DPo%3A]%0D%0A&g=">U+2016–U+205F</a>
+ <a href="http://unicode.org/cldr/utility/list-unicodeset.jsp?a=\p{Block%3DGeneral+Punctuation}%26[%3AGeneral_category%3DPo%3A]%0D%0A&g=">U+2016–U+205F</a>
range.
<p>When 'text-orientation' is either ''upright-right'' or ''upright'',
Received on Monday, 29 August 2011 06:26:19 UTC