W3C home > Mailing lists > Public > public-html-commits@w3.org > September 2012

html5/decision-policy decision-policy-v3.html,1.6,1.7

From: Sam Ruby via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 25 Sep 2012 18:36:49 +0000
To: public-html-commits@w3.org
Message-Id: <E1TGa01-00021m-Ov@lionel-hutz.w3.org>
Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv7772

Modified Files:
	decision-policy-v3.html 
Log Message:
Wordsmith based on chair review


Index: decision-policy-v3.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy-v3.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- decision-policy-v3.html	25 Sep 2012 16:59:00 -0000	1.6
+++ decision-policy-v3.html	25 Sep 2012 18:36:47 -0000	1.7
@@ -71,7 +71,9 @@
 <li><a href="#enhanced-cc">10. Enhanced Change Control</a> - The policy for enhanced change control and revert requests after specific pre-LC cutoff dates and during LC review.</li>
 <li><a href="#note-vs-rec">11. Note Track and Recommendation Track</a> - The process by which the Working Group decides whether a Working Draft will ultimately proceed down the Recommendation track or will end up as a Working Group Note.</li>
 
-<li><a href="#cr-integration">12. Integration of Extensions during CR</a> - The Process by which the Working Group decides whether a specification that extends HTML be integrated into the core HTML spec.</li>
+<li><a href="#cr-integration">12. Integration of Extensions during CR</a> -
+The Process by which the Working Group decides whether a specification that
+extends any HTML WG specification can be integrated into the original specification.</li>
 
 <li><a href="#cr-remove-early">13. Removing some at-risk features early in CR</a> - The Process by which the Working Group may drop certain at-risk features early in CR..</li>
 
@@ -1094,7 +1096,7 @@
 specifications may advance more rapidly than the spec they extend (for
 example, extensions to the HTML spec itself may advance more
 rapidly). In some such cases, it may be desirable to integrate the
-extension back into the core specification.</p>
+extension back into the specification.</p>
 
 <dl>
 <dt>1. Publish a First Public Working Draft of the extension spec</dt>
@@ -1110,7 +1112,7 @@
 for a feature in the base spec.</dd>
 
 <dt>3. Nominate by the deadline</dt>
-<dd>On entry to CR of any Working Groupspecification, the Chairs
+<dd>On entry to CR of any Working Group specification, the Chairs
 will identify a deadline prior to the end of CR for integration of
 extensions. A Working Group member may enter a nomination for
 integration at any time prior to the deadline. A nomination for
@@ -1137,7 +1139,7 @@
 objection may be addressed. If there are objections which cite
 rationale and are not resolved in a satisfactory manner, the Call for
 Consensus fails, and the extension will not be integrated. It may
-still be proposed for a future version using the usual issue
+still be proposed for integration into a future version using the usual 
 process.</dd>
 
 <dt>5. Integration</dt>
@@ -1166,12 +1168,15 @@
 <dd>If an at-risk feature does not have a thorough test
 suite, and also does not have even a single reasonably complete
 implementation, it may be nominated for early removal. Nominations
-for early removal may be entered before entering CR, or up to 3 months
-after entering CR.</dd>
+for early removal may be entered before entering CR, 
+or up to minimum 3 months after entering CR.  The CfC for entering CR will
+identify the actual period on a specification by specification basis.
+.</dd>
 
 <dt>3. Chair review</dt>
 <dd>Chairs will review nominations to ensure that requests for early removal are
-reasonable.</dd>
+reasonable.  Chairs will approve or disapprove requests within one week of the
+nomination.</dd>
 
 <dt>4. Opportunity to present an implementation or tests</dt>
 <dd>If a nomination is reviewed and approved, advocates of the feature
@@ -1180,10 +1185,10 @@
 
 <dt>5. Early removal</dt>
 <dd>If no one presents a thorough test suite or
-a reasonably complete implementation by the date 3 months after the
-request is made, then such features will be removed early. Such
+a reasonably complete implementation by the date identified by for the spec in
+question, then such features will be removed early. Such
 features may still be pursued in standalone specifications, and may be
-reintegrated into the core specification if they meet the CR exit
+reintegrated into the specification if they meet the CR exit
 criteria and have WG consensus.</dd>
 
 </section>
Received on Tuesday, 25 September 2012 18:36:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 25 September 2012 18:36:51 GMT