- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 20 Jun 2011 17:30:28 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css-module
In directory hutz:/tmp/cvs-serv27476
Modified Files:
Overview.html Overview.src.html
Log Message:
Update module template text to snapshot
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css-module/Overview.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- Overview.html 29 May 2011 21:22:04 -0000 1.5
+++ Overview.html 20 Jun 2011 17:30:26 -0000 1.6
@@ -18,13 +18,13 @@
<h1>CSS <var class=issue>TEMPLATE</var> Module Level <var
class=issue>N</var></h1>
- <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 29 May 2011</h2>
+ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 20 June 2011</h2>
<dl>
<dt>This version:
- <dd><a href="http://www.w3.org/TR/2011/ED-css3-TEMPLATE-20110529/">
- http://www.w3.org/TR/2011/ED-css3-TEMPLATE-20110529</a>
+ <dd><a href="http://www.w3.org/TR/2011/ED-css3-TEMPLATE-20110620/">
+ http://www.w3.org/TR/2011/ED-css3-TEMPLATE-20110620</a>
<dt>Latest version:
@@ -121,23 +121,21 @@
<!--begin-toc-->
<ul class=toc>
- <li><a href="#introduction"><span class=secno>1. </span>Introduction</a>
+ <li><a href="#intro"><span class=secno>1. </span> Introduction</a>
<ul class=toc>
- <li><a href="#context"><span class=secno>1.1. </span>Background</a>
-
- <li><a href="#placement"><span class=secno>1.2. </span>Module
+ <li><a href="#placement"><span class=secno>1.1. </span> Module
Interactions</a>
- <li><a href="#conventions"><span class=secno>1.3. </span>Document
+ <li><a href="#conventions"><span class=secno>1.2. </span> Document
Conventions</a>
- <li><a href="#values"><span class=secno>1.4. </span>Values</a>
+ <li><a href="#values"><span class=secno>1.3. </span> Values</a>
</ul>
- <li><a href="#sample-section"><span class=secno>2. </span>Sample
+ <li><a href="#sample-topic"><span class=secno>2. </span> Sample
section</a>
<ul class=toc>
- <li><a href="#the-display-model"><span class=secno>2.1. </span>Inner
+ <li><a href="#the-display-model"><span class=secno>2.1. </span> Inner
Display Model: the ‘<code
class=property>display-model</code>’ property</a>
</ul>
@@ -153,7 +151,10 @@
<li><a href="#experimental"><span class=secno>3.3. </span> Experimental
Implementations</a>
- <li><a href="#cr-exit-criteria"><span class=secno>3.4. </span> CR Exit
+ <li><a href="#testing"><span class=secno>3.4. </span>Non-Experimental
+ Implementations</a>
+
+ <li><a href="#cr-exit-criteria"><span class=secno>3.5. </span> CR Exit
Criteria</a>
</ul>
@@ -173,15 +174,13 @@
</ul>
<!--end-toc-->
- <h2 id=introduction><span class=secno>1. </span>Introduction</h2>
-
- <h3 id=context><span class=secno>1.1. </span>Background</h3>
+ <h2 id=intro><span class=secno>1. </span> Introduction</h2>
<p><em>This section is not normative.</em>
<p><var class=issue>Provide background, motivation, etc.</var>
- <h3 id=placement><span class=secno>1.2. </span>Module Interactions</h3>
+ <h3 id=placement><span class=secno>1.1. </span> Module Interactions</h3>
<p class=issue>Explain, normatively, how this module affects the definition
of CSS.
@@ -191,7 +190,7 @@
rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> sections <var class=issue>W.X
and Y.Z</var>.
- <h3 id=conventions><span class=secno>1.3. </span>Document Conventions</h3>
+ <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
@@ -218,7 +217,7 @@
<p class=note>Note, this is an informative note.
- <h3 id=values><span class=secno>1.4. </span>Values</h3>
+ <h3 id=values><span class=secno>1.3. </span> Values</h3>
<p>This specification follows the <a
href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
@@ -237,7 +236,7 @@
keyword as their property value. For readability it has not been repeated
explicitly.
- <h2 id=sample-section><span class=secno>2. </span>Sample section</h2>
+ <h2 id=sample-topic><span class=secno>2. </span> Sample section</h2>
<p>Look at the mark-up in this section for examples. See the <a
href="https://www.w3.org/Style/Group/css3-src/bin/README">documentation</a>
@@ -302,8 +301,8 @@
<p>A formal definition of a property looks like this:
- <h3 id=the-display-model><span class=secno>2.1. </span>Inner Display Model:
- the ‘<a href="#display-model"><code
+ <h3 id=the-display-model><span class=secno>2.1. </span> Inner Display
+ Model: the ‘<a href="#display-model"><code
class=property>display-model</code></a>’ property</h3>
<table class=propdef>
@@ -444,18 +443,40 @@
<h3 id=experimental><span class=secno>3.3. </span> Experimental
Implementations</h3>
- <p>To avoid clashes with future CSS features, the CSS specifications
- reserve a <a
+ <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 property and value extensions to CSS. The CSS
- Working Group recommends that experimental implementations of features in
- CSS Working Drafts also use vendor-prefixed property or value names. This
- avoids any incompatibilities with future changes in the draft. Once a
- specification reaches the Candidate Recommendation stage, implementors
- should implement the non-prefixed syntax for any feature they consider to
- be correctly implemented according to spec.
+ syntax</a> for proprietary and experimental extensions to CSS.
- <h3 id=cr-exit-criteria><span class=secno>3.4. </span> CR Exit Criteria</h3>
+ <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>3.4. </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>3.5. </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
@@ -525,10 +546,10 @@
<dt id=CSS21>[CSS21]
<dd>Bert Bos; et al. <a
- href="http://www.w3.org/TR/2009/CR-CSS2-20090423"><cite>Cascading Style
- Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 23
- April 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a
- href="http://www.w3.org/TR/2009/CR-CSS2-20090423">http://www.w3.org/TR/2009/CR-CSS2-20090423</a>
+ href="http://www.w3.org/TR/2011/REC-CSS2-20110607"><cite>Cascading Style
+ Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 7 June
+ 2011. W3C Recommendation. URL: <a
+ href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a>
</dd>
<!---->
@@ -574,20 +595,19 @@
<dt id=CSS21>[CSS21]
<dd>Bert Bos; et al. <a
- href="http://www.w3.org/TR/2009/CR-CSS2-20090423"><cite>Cascading Style
- Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 23
- April 2009. W3C Candidate Recommendation. (Work in progress.) URL: <a
- href="http://www.w3.org/TR/2009/CR-CSS2-20090423">http://www.w3.org/TR/2009/CR-CSS2-20090423</a>
+ href="http://www.w3.org/TR/2011/REC-CSS2-20110607"><cite>Cascading Style
+ Sheets Level 2 Revision 1 (CSS 2.1) Specification.</cite></a> 7 June
+ 2011. W3C Recommendation. URL: <a
+ href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a>
</dd>
<!---->
<dt id=CSS3COLOR>[CSS3COLOR]
<dd>Tantek Çelik; Chris Lilley; L. David Baron. <a
- href="http://www.w3.org/TR/2010/PR-css3-color-20101028"><cite>CSS Color
- Module Level 3.</cite></a> 28 October 2010. W3C Proposed Recommendation.
- (Work in progress.) URL: <a
- href="http://www.w3.org/TR/2010/PR-css3-color-20101028">http://www.w3.org/TR/2010/PR-css3-color-20101028</a>
+ href="http://www.w3.org/TR/2011/REC-css3-color-20110607"><cite>CSS Color
+ Module Level 3.</cite></a> 7 June 2011. W3C Recommendation. URL: <a
+ href="http://www.w3.org/TR/2011/REC-css3-color-20110607">http://www.w3.org/TR/2011/REC-css3-color-20110607</a>
</dd>
<!---->
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css-module/Overview.src.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- Overview.src.html 3 Jun 2011 01:32:50 -0000 1.7
+++ Overview.src.html 20 Jun 2011 17:30:26 -0000 1.8
@@ -61,22 +61,23 @@
<!--toc-->
-<h2>Introduction</h2>
-
-<h3 id="context">Background</h3>
+<h2 id="intro">
+Introduction</h2>
<p><em>This section is not normative.</em>
<p><var class="issue">Provide background, motivation, etc.</var></p>
-<h3 id="placement">Module Interactions</h3>
+<h3 id="placement">
+Module Interactions</h3>
<p class="issue">Explain, normatively, how this module affects the definition of CSS.</p>
<p>This module replaces and extends the <var class="issue">SUMMARIZE HERE</var>
features defined in [[!CSS21]] sections <var class="issue">W.X and Y.Z</var>.
-<h3 id="conventions">Document Conventions</h3>
+<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”,
@@ -102,7 +103,8 @@
<p class="note">Note, this is an informative note.</p>
-<h3 id="values">Values</h3>
+<h3 id="values">
+Values</h3>
<p>This specification follows the
<a href="http://www.w3.org/TR/CSS21/about.html#property-defs">CSS property
@@ -118,7 +120,8 @@
keyword as their property value. For readability it has not been repeated
explicitly.
-<h2>Sample section</h2>
+<h2 id="sample-topic">
+Sample section</h2>
<p>Look at the mark-up in this section for examples. See the <a
href="https://www.w3.org/Style/Group/css3-src/bin/README">documentation</a> for more precise instructions. The
@@ -177,7 +180,8 @@
<p>A formal definition of a property looks like this:</p>
-<h3 id="the-display-model">Inner Display Model: the 'display-model' property</h3>
+<h3 id="the-display-model">
+Inner Display Model: the 'display-model' property</h3>
<table class=propdef>
<tr>
@@ -287,19 +291,43 @@
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 CSS specifications
- reserve a <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords">prefixed
- syntax</a> for proprietary property and value extensions to CSS. The CSS
- Working Group recommends that experimental implementations of features in
- CSS Working Drafts also use vendor-prefixed property or value names. This
- avoids any incompatibilities with future changes in the draft. Once a
- specification reaches the Candidate Recommendation stage, implementors
- should implement the non-prefixed syntax for any feature they consider to
- be correctly implemented according to spec.</p>
+ <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>
Received on Monday, 20 June 2011 17:30:30 UTC