--- a/tr.html Thu Oct 10 00:51:58 2013 +0200
+++ b/tr.html Thu Oct 10 01:11:16 2013 +0200
@@ -25,7 +25,7 @@
height="48" width="72"></a> </p>
<h1 class="title" id="title">Recommendation Track Process, draft proposal</h1>
<h2 id="w3c-working-draft-20-september-2012"><abbr title="World Wide Web Consortium"></abbr>Editors'
- Draft 3 October 2013</h2>
+ Draft 9 October 2013</h2>
<dl>
<!--dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/HTML-longdesc">http://www.w3.org/TR/HTML-longdesc</a></dd-->
@@ -52,8 +52,12 @@
<p>This is a revised draft proposal to replace the <a href="http://www.w3.org/2005/10/Process-20051014/tr.html">current
chapter 7 of the W3C process document</a> with a more effective W3C
Specification life cycle following the meeting of the W3C Advisory
- Board on 17-18 September 2013. This document is an editor's draft for
- the Advisory Board but does not yet fully reflect consensus.</p>
+ Board Process Task Force on 7 October 2013. This document is an
+ editor's draft for the Advisory Board but does not yet fully reflect
+ consensus. The Task Force proposed to request that the Advisory Board
+ consider, at its 14 October meeting, recommending the content of this
+ draft for adoption by the Advisory Committee as a replacement for the
+ existing Chapter 7.</p>
<p>An earlier version was first proposed to the W3C Advisory Board on 13
May 2013 as a possible replacement for the <a href="http://www.w3.org/2005/10/Process-20051014/tr.html">current
chapter 7 of the W3C process document</a>, and a <a href="http://yadi.sk/d/Zikwkr385JG8f">subsequent
@@ -68,10 +72,10 @@
process for such changes</a>.</p>
<p>I am grateful to the W3C Advisory Board, the W3C Process Community
Group, Art Barstow, Robin Berjon, Wayne Carr, Marcos Cáceres, Ian
- Hickson, Ian Jacobs, Ralph Swick, Anne van Kesteren, and many people I
- have forgotten to acknowledge for suggestions, comments and
- discussions the helped me sort out my thinking, and to Ora Lassila for
- the image that illustrates the normal process of a W3C
+ Hickson, Ian Jacobs, Chris Lilley, Ralph Swick, Anne van Kesteren, and
+ many people I have forgotten to acknowledge for suggestions, comments
+ and discussions the helped me sort out my thinking, and to Ora Lassila
+ for the image that illustrates the normal process of a W3C
Recommendation-track document. </p>
<p>Please send comments on this document to, or participate in, the <a
href="http://www.w3.org/community/w3process/">W3C Process Community
@@ -101,9 +105,6 @@
<p>Editorially, I have tried to rationalize requirements, and clarify
who is responsible for meeting them. I have also actively removed
advice and general statements to keep this version short.</p>
- <p>Note that I have generally not yet renumbered sections that are
- deleted or moved, which explains why some items are not sequentially
- numbered.</p>
</div>
</div>
<h2>7 <a name="Reports" id="Reports">W3C Technical Report Development
@@ -133,11 +134,11 @@
<g transform="scale(1 1) rotate(0) translate(4 58)" class="graph" id="graph0">
<g class="node" id="wd">
<ellipse ry="18" rx="38.1938" cy="-18" cx="147" stroke="black" fill="none"></ellipse>
- <text font-size="14.00" font-family="Times,serif" y="-14.3" x="147"
- text-anchor="middle">WD</text> </g>
+ <a xlink:href="#RecsWD"><text font-size="14.00" font-family="Times,serif"
+ y="-14.3" x="147" text-anchor="middle">WD</text></a> </g>
<g class="edge" id="edge1">
- <text font-size="8.00" font-family="Times,serif" y="-20" x="66" text-anchor="left">First
- WD</text>
+ <a xlink:href="#first-wd"><text font-size="8.00" font-family="Times,serif"
+ y="-20" x="66" text-anchor="left">First WD</text></a>
<path d="M66,-18h32.25" stroke="black" fill="none"></path>
<polygon points="98.5289,-21.5001 108.529,-18 98.5289,-14.5001 98.5289,-21.5001"
stroke="black" fill="black"></polygon> </g>
@@ -148,8 +149,8 @@
stroke="black" fill="black"></polygon> </g>
<g class="node" id="lccr">
<ellipse ry="18" rx="37.8943" cy="-18" cx="260" stroke="black" fill="none"></ellipse>
- <text font-size="14.00" font-family="Times,serif" y="-14.3" x="260"
- text-anchor="middle">LCCR</text> </g>
+ <a xlink:href="#RecsCR"><text font-size="14.00" font-family="Times,serif"
+ y="-14.3" x="260" text-anchor="middle">LCCR</text></a> </g>
<g class="edge" id="lccr-repeat">
<path d="M183.12,-11.67h30.5" stroke="black" fill="none"></path>
<polygon points="214.378,-14.8689 224.487,-11.6987 214.607,-7.87265 214.378,-14.8689"
@@ -165,8 +166,8 @@
stroke="black" fill="black"></polygon> </g>
<g class="node" id="node4">
<ellipse ry="18" rx="28.6953" cy="-18" cx="363" stroke="black" fill="none"></ellipse>
- <text font-size="14.00" font-family="Times,serif" y="-14.3" x="363"
- text-anchor="middle">REC</text> </g>
+ <a xlink:href="#RecsW3C"><text font-size="14.00" font-family="Times,serif"
+ y="-14.3" x="363" text-anchor="middle">REC</text></a> </g>
<g class="edge" id="edge6">
<path d="M297.75,-18h26.5" stroke="black" fill="none"></path>
<polygon points="324.306,-21.5001 334.306,-18 324.306,-14.5001 324.306,-21.5001"
@@ -174,45 +175,53 @@
<h3>Table of Contents</h3>
<ul id="mozToc">
<!--mozToc h3 1 h4 2 h5 3 h6 4-->
- <li><a href="#mozTocId316776">Table of Contents</a></li>
- <li><a href="#mozTocId405414">General requirements for Technical Reports</a></li>
- <li><a href="#mozTocId1729">7.1 Maturity Levels</a></li>
- <li><a href="#mozTocId318562">7.2 General Requirements for Advancement on
+ <li><a href="#mozTocId663575">Table of Contents</a></li>
+ <li><a href="#mozTocId640923">General requirements for Technical Reports</a></li>
+ <li><a href="#mozTocId773099">7.1 Maturity Levels</a></li>
+ <li><a href="#mozTocId48944">7.2 General Requirements for Advancement on
the Recommendation Track</a>
<ul>
- <li><a href="#mozTocId348163">7.2.2 Wide Review</a></li>
- <li><a href="#mozTocId133300">7.2.3 Implementation Experience</a></li>
+ <li><a href="#mozTocId61574">7.2.1 Substantive Change</a></li>
+ <li><a href="#mozTocId776695">7.2.2 Wide Review</a></li>
+ <li><a href="#mozTocId111988">7.2.3 Implementation Experience</a></li>
</ul>
</li>
- <li><a href="#mozTocId29135">7.3 Reviews and Review Responsibilities</a></li>
- <li><a href="#mozTocId412309">7.4 Advancing a Technical Report to
+ <li><a href="#mozTocId838441">7.3 Reviews and Review Responsibilities</a></li>
+ <li><a href="#mozTocId983157">7.4 Advancing a Technical Report to
Recommendation</a>
<ul>
- <li><a href="#mozTocId20175">7.4.1.a Working Draft</a></li>
- <li><a href="#mozTocId87620">7.4.2 Last Call Candidate Recommendation</a></li>
- <li><a href="#mozTocId707682">7.4.5 Publication of a W3C
+ <li><a href="#mozTocId647636">7.4.1 Working Draft</a>
+ <ul>
+ <li><a href="#mozTocId165613">7.4.1.a First Public Working Draft</a></li>
+ <li><a href="#mozTocId671592">7.4.1.b Revised Public Working
+ Drafts</a></li>
+ </ul>
+ </li>
+ <li><a href="#mozTocId275563">7.4.2 Last Call Candidate Recommendation</a></li>
+ <li><a href="#mozTocId809317">7.4.3 Publication of a W3C
Recommendation</a>
<ul>
- <li><a href="#mozTocId848355">Publishing a Last Call Candidate
+ <li><a href="#mozTocId629587">Publishing a Last Call Candidate
Recommendation as a W3C Recommendation</a></li>
- <li><a href="#mozTocId961203">Publishing an Edited Recommendation
+ <li><a href="#mozTocId40322">Publishing an Edited Recommendation
(See also Modifying a Recommendation below)</a></li>
- <li><a href="#mozTocId138350">For all W3C Recommendations</a></li>
+ <li><a href="#mozTocId681338">For all W3C Recommendations, in
+ addition to meeting the general requirements for advancement,</a></li>
</ul>
</li>
</ul>
</li>
- <li><a href="#mozTocId151871">7.5 Publishing a Working Group or Interest
+ <li><a href="#mozTocId360048">7.5 Publishing a Working Group or Interest
Group Note</a></li>
- <li><a href="#mozTocId986536">7.6 Modifying a W3C Recommendation</a>
+ <li><a href="#mozTocId38383">7.6 Modifying a W3C Recommendation</a>
<ul>
- <li><a href="#mozTocId565826">7.6.1 Errata Management</a></li>
- <li><a href="#mozTocId347486">7.6.2 Classes of Changes to a
+ <li><a href="#mozTocId72619">7.6.1 Errata Management</a></li>
+ <li><a href="#mozTocId171734">7.6.2 Classes of Changes to a
Recommendation</a></li>
</ul>
</li>
- <li><a href="#mozTocId990936">7.7 Rescinding a W3C Recommendation</a></li>
- <li><a href="#mozTocId589973">Good practices</a></li>
+ <li><a href="#mozTocId737554">7.7 Rescinding a W3C Recommendation</a></li>
+ <li><a href="#mozTocId185651">Good practices</a></li>
</ul>
<h3>General requirements for Technical Reports</h3>
<p>Every document published as part of the technical report development
@@ -456,7 +465,6 @@
specification is returned to a Working Group for further work.</p>
<h4 id="working-draft">7.4.1 Working Draft</h4>
<h5>7.4.1.a <a name="first-wd" id="first-wd">First Public Working Draft</a></h5>
- <h4> </h4>
<p>To publish the First Public Working Draft of a document, in addition to
meeting the <a href="#transition-reqs">general requirements for
advancement</a> a Working Group</p>
@@ -474,7 +482,7 @@
per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</p>
- <h5 id="revised-wd">7.4.1b Revised Public Working Drafts</h5>
+ <h5 id="revised-wd">7.4.1.b Revised Public Working Drafts</h5>
<p class="new">A Working Group <em class="rfc2119">should</em> publish a
Working Draft to the W3C Technical Reports page every 6 months, or sooner
when there have been significant changes to the document that would
@@ -560,7 +568,7 @@
<p> <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
Committee</a> representatives <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
the decision to advance the technical report.</p>
- <h4>7.4.5 <a name="rec-publication" id="rec-publication">Publication of a
+ <h4>7.4.3 <a name="rec-publication" id="rec-publication">Publication of a
W3C Recommendation</a></h4>
<h5><a name="lcrec-publication" id="lcrec-publication">Publishing a Last
Call Candidate Recommendation as a W3C Recommendation</a></h5>
@@ -601,8 +609,7 @@
<li><span class="new"><em class="rfc2119">may</em> provisionally approve a
Recommendation with minimal implementation experience where there is a
compelling reason to do so. In such a case, the Director <em class="rfc2119">should</em>
- explain the reasons for that decision. <br>
- </span></li>
+ explain the reasons for that decision. </span></li>
</ul>
<h5 id="rec-edited">Publishing an Edited Recommendation (See also <a href="#rec-modify">Modifying
a Recommendation</a> below)</h5>
@@ -618,24 +625,27 @@
<h5>For <strong>all</strong> W3C Recommendations, in addition to meeting
the <a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#transition-reqs">general
requirements for advancement</a>,</h5>
- <p>The Director <em class="rfc2119">must</em> announce the provisional
- approval of a Request for publication of a W3C Recommendation to the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
- Committee</a>.</p>
- <p class="changed">The Advisory Committee review of the technical report <em
- class="rfc2119">must</em> continue at least 28 days after the
- announcement of provisional approval to publish the Edited Recommendation
- as a W3C Recommendation. <span class="from">(was 7.4.4)</span> </p>
- <p>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
- rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
- in Advisory Committee reviews, the Director <span class="new"><em class="rfc2119">must</em>
- publish the substantive content of the dissent to W3C and the general
- public</span> and <em class="rfc2119">must</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
- address</a> the comment <span class="new">at least 14 days before
- publication as a W3C Recommendation</span>. In this case the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
- Committee</a> <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
- the decision.</p>
- <p>The Director <em class="rfc2119">must</em> announce the publication of a
- W3C Recommendation to other W3C groups and to the public.</p>
+ <ul>
+ <li>The Director <em class="rfc2119">must</em> announce the provisional
+ approval of a Request for publication of a W3C Recommendation to the <a
+ href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+ Committee</a>.</li>
+ <li>The Advisory Committee review of the technical report <em class="rfc2119">must</em>
+ continue at least 28 days after the announcement of provisional approval
+ to publish the Edited Recommendation as a W3C Recommendation. <span class="from">(was
+ 7.4.4)</span></li>
+ <li>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
+ rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
+ in Advisory Committee reviews, the Director <span class="new"><em class="rfc2119">must</em>
+ publish the substantive content of the dissent to W3C and the general
+ public</span> and <em class="rfc2119">must</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
+ address</a> the comment <span class="new">at least 14 days before
+ publication as a W3C Recommendation</span>. In this case the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+ Committee</a> <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
+ the decision.</li>
+ <li>The Director <em class="rfc2119">must</em> announce the publication
+ of a W3C Recommendation to other W3C groups and to the public. </li>
+ </ul>
<p>Possible next steps:</p>
<ul>
<li>A W3C Recommendation normally retains its status indefinitely. However
@@ -727,14 +737,14 @@
conformance, but add no new features</dt>
<dd>These changes <span class="rfc2119">MAY</span> affect conformance to
the Recommendation. A change that affects conformance is one that:
- <ol>
+ <ul>
<li>turns conforming data, processors, or other conforming agents into
non-conforming agents, or</li>
<li>turns non-conforming agents into conforming ones, or</li>
<li>clears up an ambiguity or under-specified part of the
specification in such a way that an agent whose conformance was once
unclear becomes clearly conforming or non-conforming.</li>
- </ol>
+ </ul>
</dd>
<dt>4. New features</dt>
</dl>
@@ -793,14 +803,14 @@
rescind a W3C Recommendation to other W3C groups, the public, and the <a
href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
Committee</a>. The announcement <em class="rfc2119">must</em>:</p>
- <ol>
+ <ul>
<li>indicate that this is a Proposal to Rescind a Recommendation</li>
<li>specify the deadline for review comments, which <em class="rfc2119">must</em>
be at least <span class="time-interval">four weeks after publication </span></li>
<li>identify known dependencies and solicit review from all dependent
Working Groups;</li>
<li>solicit public review.</li>
- </ol>
+ </ul>
<p>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
in Advisory Committee reviews, the Director <span class="new"><em class="rfc2119">must</em>