Minor editorial tweaks - typos, intro section, ...
--- a/tr.html Mon Sep 23 22:41:08 2013 +0200
+++ b/tr.html Tue Sep 24 01:35:03 2013 +0200
@@ -5,13 +5,9 @@
<title>A Rec-track Process Draft Proposal</title>
<link href="https://www.w3.org/StyleSheets/TR/base.css" type="text/css" rel="stylesheet">
<style type="text/css">
-
-
.from {display:none }
-
-
-
+
.about { margin-left: 3em; margin-right: 3em; font-size: .83em}
table { margin-left: auto; margin-right: auto }
.diagram { text-align: center; margin: 2.5em 0 }
@@ -63,7 +59,7 @@
chapter 7 of the W3C process document</a>, and a <a href="http://yadi.sk/d/Zikwkr385JG8f">subsequent
version</a> was <a href="http://lists.w3.org/Archives/Public/public-w3process/2013May/0023.html">proposed</a>
to the <a href="http://www.w3.org/community/w3process/">W3C Process
- Community Group</a> on 29 May 2013 by Charles Nevile <<a href="mailto:chaals@yandex-team.ru">chaals@yandex-team.ru</a>
+ Community Group</a> on 29 May 2013 by Charles Nevile <<a href="mailto:chaals@yandex-team.ru">chaals@yandex-team.ru</a>>
for discussion. The Advisory Board has agreed to make all editor's
drafts public, to enable broad input. However, following the existing
process, the Advisory Board retains formal responsibility for
@@ -84,6 +80,12 @@
Lifecycle (chapter 7)</a>"</p>
Major changes:
<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>Last Call and Candidate Recommendation have been collapsed
together. Some of the requirements are therefore enforced earlier in
the process.</li>
@@ -99,8 +101,9 @@
<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 renumbered sections that are deleted
- or moved, which explains why some items are not sequentially numbered.</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