Editorial tweaks (including expanding listof changes) for publication today.
--- a/tr.html Mon Jan 20 10:44:23 2014 +0100
+++ b/tr.html Mon Jan 20 10:56:24 2014 +0100
@@ -23,10 +23,9 @@
<div class="head">
<p> <a href="http://www.w3.org/"><img alt="W3C" src="http://www.w3.org/Icons/w3c_home"
height="48" width="72"></a> </p>
- <h1 class="title" id="title">Recommendation Track Process, post-"Last
- Call" draft proposal</h1>
- <h2 id="w3c-working-draft-20-september-2012"><abbr title="World Wide Web Consortium"></abbr>Editors'
- Draft 19 January 2014</h2>
+ <h1 class="title" id="title">Recommendation Track Process draft proposal</h1>
+ <h2 id="draft-shorthand-status"><abbr title="World Wide Web Consortium"></abbr>Editors'
+ Draft 20 January 2014</h2>
<dl>
<dt>Current active version:</dt>
<dd><a href="http://www.w3.org/2005/10/Process-20051014/tr.html">http://www.w3.org/2005/10/Process-20051014/tr.html</a></dd>
@@ -56,7 +55,8 @@
Board's Chapter 7 Task Force on 14 January 2014. This document is an
editor's draft for resolution of comments received.</p>
<p>In this draft, there are some pointers and placeholders for changes
- expected in response to open issues, most particularly <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a>.</p>
+ expected in response to open issues, most particularly <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a>
+ and <a href="http://www.w3.org/community/w3process/track/issues/77">ISSUE-77</a>.</p>
<p>This introductory session (before the chapter title below) will be
removed when this chapter is re-incorporated into the full process
document, as per issues 60-64.</p>
@@ -89,10 +89,14 @@
<ul>
<li>There is a requirement that Working groups <em class="rfc2119">should</em>
document known implementation for all transitions</li>
- <li>New sections give some guidance on what is considered when
- assessing "<a href="#implementation-experience">adequate
- implementation experience</a>" and "<a href="#wide-review">wide
- review</a>"</li>
+ <li>Implementation requirements are not simply listed as "2
+ interoperable implementations", instead a new sections gives
+ guidance on what is considered when assessing "<a href="#implementation-experience">adequate
+ implementation experience</a>".</li>
+ <li>Instead of relying on a Last Call publication for adequate review
+ there is a requirement for a Working Group to demonstrate "<a href="#wide-review">wide
+ review</a>", leaving them to implement review processes as they
+ see fit.</li>
<li>Last Call and Candidate Recommendation have been collapsed
together. Some of the requirements are therefore enforced earlier in
the process.</li>
@@ -103,7 +107,9 @@
Committee review now begins at the same time as Candidate
recommendation, and ends 4 weeks after the Working group has
provisional approval for a Request to publish as a W3C
- Recommendation.</li>
+ Recommendation. (This may be reversed, per <a href="https://www.w3.org/community/w3process/track/issues/84">ISSUE-84</a>)</li>
+ <li>If W3C closes a Working Group, they <em class="rfc2119">must</em>
+ republish its unfinished work as Notes. </li>
<li>The Director is required to address AC review comments <strong>publicly</strong>,
2 weeks <em>before</em> publication of a Recommendation.</li>
<li>And it is in HTML5</li>
@@ -537,7 +543,7 @@
<li><em class="rfc2119">should</em> report any changes in dependencies
with other groups,</li>
</ul>
- <p>Possible next steps:</p>
+ <p>Possible next steps for any Working Draft:</p>
<ul>
<li><a href="#hb-wd">Revised Public Working Draft</a></li>
<li><a href="#last-call">Candidate recommendation</a>.</li>