Re-ordered content and added a couple of markers for missing text as per ISSUE-59.
authorcharles
Wed, 11 Dec 2013 19:04:30 +0400
changeset 53 2c13766abd84
parent 52 59ee28366bf8
child 54 840ff6a43e74
Re-ordered content and added a couple of markers for missing text as per ISSUE-59.
The Table of Contents has been regenerated (but the links may not work properly yet), but sections have not yet been renumbered, to assist following the changes.
There has been no text deleted, and only issue markers added, since the last version.
In subsequent commits the sections will be renumbered, and content edited if required to simplify reading.
tr.html
--- a/tr.html	Fri Dec 06 09:47:59 2013 +0100
+++ b/tr.html	Wed Dec 11 19:04:30 2013 +0400
@@ -26,7 +26,7 @@
       <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 6 December 2013</h2>
+        Draft 11 December 2013</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>
@@ -50,15 +50,19 @@
       <hr> </div>
     <div class="noprint">
       <div class="navbar">
-        <p>This is a revised draft proposal to replace the <a href="http://www.w3.org/2005/10/Process-20051014/tr.html">current
+        <p>This is an intermediate 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's Chapter 7 Task Force on 2 December 2013. This document is the
           editor's draft for resolution of comments received on the "Last Call"
           version.</p>
-        <p>As per <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a>,
-          the editor expect to do a significant re-organisation of the content
-          probably between 9 and 18 December 2013. </p>
+        <p>In this draft, there has been a reordering of the content along the
+          lines foreshadowed by <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a>.
+          Although the table of contents has been regenerated, sections have not
+          yet been renumbered, to assist following the changes. There has been
+          no text deleted, and only issue markers added, since the last version.
+          In subsequent commits the sections will be renumbered, and content
+          edited if required to simplify reading.</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>
@@ -132,18 +136,88 @@
     <p>See also the licensing goals for W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section
         2</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>
+      </p><br>
+    <h3><a class="mozTocH3" id="mozTocId308503"></a>Table of Contents</h3>
+    <br>
+    <ul id="mozToc">
+      <!--mozToc h3 1 h4 2 h5 3-->
+      <li><a href="#mozTocId438832">7.4 Advancing a Technical Report to
+          Recommendation</a></li>
+      <li><a href="#mozTocId936662">7.1 Maturity Levels</a></li>
+      <li><a href="#mozTocId135327">General requirements for Technical Reports</a></li>
+      <li><a href="#mozTocId151445">7.2 General Requirements for Advancement on
+          the Recommendation Track</a>
+        <ul>
+          <li><a href="#mozTocId859663">7.2.1 Substantive Change</a></li>
+        </ul>
+      </li>
+      <li><a href="#mozTocId647919">7.3 Reviews and Review Responsibilities</a>
+        <ul>
+          <li><a href="#mozTocId921995">7.2.2 Wide Review</a></li>
+          <li><a href="#mozTocId547761">7.2.3 Implementation Experience</a></li>
+          <li><a href="#mozTocId899983">7.4.1 Working Draft</a>
+            <ul>
+              <li><a href="#mozTocId653661">7.4.1.a First Public Working Draft</a></li>
+              <li><a href="#mozTocId972800">7.4.1.b Revised Public Working
+                  Drafts</a></li>
+            </ul>
+          </li>
+          <li><a href="#mozTocId115371">7.4.2 Candidate Recommendation</a></li>
+          <li><a href="#mozTocId525956">7.4.3 Publication of a W3C
+              Recommendation</a>
+            <ul>
+              <li><a href="#mozTocId774333">Publishing a Candidate
+                  Recommendation as a W3C Recommendation</a></li>
+              <li><a href="#mozTocId872144">Publishing an Edited Recommendation
+                  (See also Modifying a Recommendation below)</a></li>
+              <li><a href="#mozTocId187610">For all W3C Recommendations, in
+                  addition to meeting the general requirements for advancement,</a></li>
+            </ul>
+          </li>
+        </ul>
+      </li>
+      <li><a href="#mozTocId548274">7.6 Modifying a W3C Recommendation</a>
+        <ul>
+          <li><a href="#mozTocId169012">7.6.1 Errata Management</a></li>
+          <li><a href="#mozTocId644984">7.6.2 Classes of Changes to a
+              Recommendation</a></li>
+        </ul>
+      </li>
+      <li><a href="#mozTocId325969">7.5 Publishing a Working Group or Interest
+          Group Note</a></li>
+      <li><a href="#mozTocId22672">7.7 Rescinding a W3C Recommendation</a></li>
+      <li><a href="#mozTocId168231">Good practices</a></li>
+    </ul>
+    <p class="issue">Add a short overview of what this chapter is about. <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a></p>
+    <h3><a class="mozTocH3" id="mozTocId438832"></a>7.4 <a name="rec-advance" id="rec-advance">Advancing
+        a Technical Report to Recommendation</a></h3>
+    <p>W3C follows these steps when advancing a technical report to
+      Recommendation.</p>
+    <ol>
+      <li><a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#first-wd">Publication
+          of the First Public Working Draft</a>,</li>
+      <li><a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#hb-wd">Publication
+          of zero or more revised Public Working Drafts</a>.</li>
+      <li><a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#last-call">Publication
+          of a Candidate Recommendation</a>.</li>
+      <li><a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#rec-publication">Publication
+          as a Recommendation</a>.</li>
+      <li>Possibly, <a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#rec-edited">Publication
+          as an Edited Recommendation</a></li>
+    </ol>
     <p>
       <svg xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"
         viewBox="0.00 0.00 400.00 62.00" height="5em" width="36em">
         <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>
-            <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>
+            <a xlink:href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#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">
-            <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>
+            <a xlink:href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#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>
@@ -154,8 +228,9 @@
               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>
-            <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>
+            <a xlink:href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#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"
@@ -171,109 +246,27 @@
               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>
-            <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>
+            <a xlink:href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#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"
               stroke="black" fill="black"></polygon> </g> </g> </svg> </p>
-    <h3>Table of Contents</h3>
-    <ul id="Toc">
-      <!--mozToc h3 1 h4 2 h5 3 h6 4-->
-      <li><a href="#general-requirements">General requirements for Technical
-          Reports</a></li>
-      <li><a href="#maturity-levels">7.1 Maturity Levels</a></li>
-      <li><a href="#transition-reqs">7.2 General Requirements for Advancement on
-          the Recommendation Track</a>
-        <ul>
-          <li><a href="#substantive-change">7.2.1 Substantive Change</a></li>
-          <li><a href="#wide-review">7.2.2 Wide Review</a></li>
-          <li><a href="#implementation-experience">7.2.3 Implementation
-              Experience</a></li>
-        </ul>
-      </li>
-      <li><a href="#doc-reviews">7.3 Reviews and Review Responsibilities</a></li>
-      <li><a href="#rec-advance">7.4 Advancing a Technical Report to
-          Recommendation</a>
-        <ul>
-          <li><a href="#wd">7.4.1 Working Draft</a>
-            <ul>
-              <li><a href="#first-wd">7.4.1.a First Public Working Draft</a></li>
-              <li><a href="#revised-wd">7.4.1.b Revised Public Working Drafts</a></li>
-            </ul>
-          </li>
-          <li><a href="#last-call">7.4.2 Candidate Recommendation</a></li>
-          <li><a href="#rec-publication">7.4.3 Publication of a W3C
-              Recommendation</a>
-            <ul>
-              <li><a href="#lcrec-publication">7.4.3.a Publishing a Candidate
-                  Recommendation as a W3C Recommendation</a></li>
-              <li><a href="#rec-edited">7.4.3.b Publishing an Edited
-                  Recommendation</a></li>
-              <li><a href="#for-all-recs">7.4.3.c For all W3C Recommendations</a></li>
-            </ul>
-          </li>
-        </ul>
-      </li>
-      <li><a href="#tr-end">7.5 Publishing a Working Group or Interest Group
-          Note</a></li>
-      <li><a href="#rec-modify">7.6 Modifying a W3C Recommendation</a>
-        <ul>
-          <li><a href="#errata">7.6.1 Errata Management</a></li>
-          <li><a href="#correction-classes">7.6.2 Classes of Changes to a
-              Recommendation</a></li>
-        </ul>
-      </li>
-      <li><a href="#rec-rescind">7.7 Rescinding a W3C Recommendation</a></li>
-      <li><a href="#good-practice">Good practices</a></li>
-    </ul>
-    <h3 id="general-requirements">General requirements for Technical Reports</h3>
-    <p>Every document published as part of the technical report development
-      process <em class="rfc2119 old">must</em> be a public document. The <a href="http://www.w3.org/TR/">index
-        of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-doc-list">PUB11</a>]
-      is available at the W3C Web site. W3C will make every effort to make
-      archival documents indefinitely available at their original address in
-      their original form.</p>
-    <p>Every document published as part of the technical report development
-      process <em class="rfc2119 old">must</em> <span class="from">(was in
-        7.8)</span> clearly indicate its <a href="#maturity-levels">maturity
-        level</a>, and <em id="DocumentStatus" class="rfc2119">must</em>
-      include information about the status of the document. This status
-      information</p>
-    <ul>
-      <li><em class="rfc2119">must</em> be unique each time a specification is
-        published,<br>
-        <em class="rfc2119"></em></li>
-      <li><em class="rfc2119">must</em> state who developed the specification, </li>
-      <li><em class="rfc2119">must</em> state how to send comments or file bugs,
-        and where these are recorded, </li>
-      <li> <em class="rfc2119">should</em> explain how the technology relates
-        to existing international standards and related work inside or outside
-        W3C,</li>
-      <li><em class="rfc2119">should</em> include expectations about next steps,
-        and</li>
-      <li><em class="rfc2119">should</em> explain or link to an explanation of
-        significant changes from the previous version.</li>
-    </ul>
-    <p>Every Technical Report published as part of the Technical Report
-      development process is edited by one or more editors appointed by a Group
-      Chair. It is the responsibility of these editors to ensure that the
-      decisions of the Group are correctly reflected in subsequent drafts of the
-      technical report. An editor <em class="rfc2119">must</em> be a
-      participant, as a Member representative, Team representative, or Invited
-      Expert in the Group responsible for the document(s) they are editing. </p>
-    <p>The Team is <em class="rfc2119">not required</em> to publish a Technical
-      Report that does not conform to the Team's <a href="http://www.w3.org/Guide/pubrules">Publication
-        Rules</a> (e.g., for <a name="DocumentName" id="DocumentName">naming</a>,
-      status information, style, and <a name="document-copyright" id="document-copyright">copyright
-        requirements</a>). These rules are subject to change by the Team from
-      time to time. The Team <em class="rfc2119">must</em> inform group Chairs
-      and the Advisory Committee of any changes to these rules.</p>
-    <p>The primary language for W3C Technical Reports is English. W3C encourages
-      the translation of its Technical Reports. <a href="http://www.w3.org/Consortium/Translation/">Information
-        about translations of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-translations">PUB18</a>]
-      is available at the W3C Web site.</p>
-    <h3>7.1 <a name="maturity-levels" id="maturity-levels">Maturity Levels</a></h3>
+    <p>W3C <em class="rfc2119">may</em> <a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#tr-end">end
+        work on a technical report</a> at any time.</p>
+    <p>The Director <em class="rfc2119">may</em> decline a request to advance
+      in maturity level, requiring a Working Group to conduct further work, and
+      <em class="rfc2119">may</em> require the specification to return to a
+      lower <a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#maturity-level">maturity
+        level</a>. The Director <em class="rfc2119">must</em> inform the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
+        Committee</a> and Working Group Chairs when a Working Group's request
+      for a specification to advance in maturity level is declined and and the
+      specification is returned to a Working Group for further work.</p>
+    <p class="issue">Add a short explanation of Note track, and how documents
+      can go from Rec-track to Note and back. <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a></p>
+    <h3><a class="mozTocH3" id="mozTocId936662"></a>7.1 <a name="maturity-levels"
+        id="maturity-levels">Maturity Levels</a></h3>
     <dl>
       <dt><a name="RecsWD" id="RecsWD">Working Draft (WD)</a></dt>
       <dd>A Working Draft is a document that W3C has published for review by the
@@ -337,8 +330,55 @@
       their contents endorsed in any way by W3C or its members, except to the
       extent that such contents happen to be consistent with some other document
       which carries a higher level of endorsement.</p>
-    <h3>7.2 <a name="transition-reqs" id="transition-reqs">General Requirements
-        for Advancement on the Recommendation Track</a></h3>
+    <h3 id="general-requirements"><a class="mozTocH3" id="mozTocId135327"></a>General
+      requirements for Technical Reports</h3>
+    <p>Every document published as part of the technical report development
+      process <em class="rfc2119 old">must</em> be a public document. The <a href="http://www.w3.org/TR/">index
+        of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-doc-list">PUB11</a>]
+      is available at the W3C Web site. W3C will make every effort to make
+      archival documents indefinitely available at their original address in
+      their original form.</p>
+    <p>Every document published as part of the technical report development
+      process <em class="rfc2119 old">must</em> clearly indicate its <a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#maturity-levels">maturity
+        level</a>, and <em id="DocumentStatus" class="rfc2119">must</em>
+      include information about the status of the document. This status
+      information</p>
+    <ul>
+      <li><em class="rfc2119">must</em> be unique each time a specification is
+        published,<br>
+        <em class="rfc2119"></em></li>
+      <li><em class="rfc2119">must</em> state who developed the specification, </li>
+      <li><em class="rfc2119">must</em> state how to send comments or file bugs,
+        and where these are recorded, </li>
+      <li> <em class="rfc2119">should</em> explain how the technology relates
+        to existing international standards and related work inside or outside
+        W3C,</li>
+      <li><em class="rfc2119">should</em> include expectations about next steps,
+        and</li>
+      <li><em class="rfc2119">should</em> explain or link to an explanation of
+        significant changes from the previous version.</li>
+    </ul>
+    <p>Every Technical Report published as part of the Technical Report
+      development process is edited by one or more editors appointed by a Group
+      Chair. It is the responsibility of these editors to ensure that the
+      decisions of the Group are correctly reflected in subsequent drafts of the
+      technical report. An editor <em class="rfc2119">must</em> be a
+      participant, as a Member representative, Team representative, or Invited
+      Expert in the Group responsible for the document(s) they are editing. </p>
+    <p>The Team is <em class="rfc2119">not required</em> to publish a Technical
+      Report that does not conform to the Team's <a href="http://www.w3.org/Guide/pubrules">Publication
+        Rules</a> (e.g., for <a name="DocumentName" id="DocumentName">naming</a>,
+      status information, style, and <a name="document-copyright" id="document-copyright">copyright
+        requirements</a>). These rules are subject to change by the Team from
+      time to time. The Team <em class="rfc2119">must</em> inform group Chairs
+      and the Advisory Committee of any changes to these rules.</p>
+    <p>The primary language for W3C Technical Reports is English. W3C encourages
+      the translation of its Technical Reports. <a href="http://www.w3.org/Consortium/Translation/">Information
+        about translations of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-translations">PUB18</a>]
+      is available at the W3C Web site.</p>
+    <h3><a class="mozTocH3" id="mozTocId151445"></a>7.2 <a name="transition-reqs"
+        id="transition-reqs">General Requirements for Advancement on the
+        Recommendation Track</a></h3>
     <p>For <em>all</em> requests to advance a specification to a new maturity
       level other than Note the Working Group:</p>
     <ul>
@@ -368,13 +408,29 @@
       been met before Director's approval is given.</p>
     <ul>
     </ul>
-    <h4 id="substantive-change">7.2.1 Substantive Change</h4>
+    <h4 id="substantive-change"><a class="mozTocH4" id="mozTocId859663"></a>7.2.1
+      Substantive Change</h4>
     <p> A <dfn>substantive change</dfn> (whether deletion, inclusion, or other
       modification) is one where someone could reasonably expect that making the
       change would invalidate an individual's review or implementation
       experience. Other changes (e.g., clarifications, bug fixes, editorial
       repairs, and minor error corrections) are minor changes.</p>
-    <h4>7.2.2 <a id="wide-review">Wide Review</a></h4>
+    <h3><a class="mozTocH3" id="mozTocId647919"></a>7.3 <a name="doc-reviews" id="doc-reviews">Reviews
+        and Review Responsibilities</a></h3>
+    <p>A document is available for review from the moment it is first published.
+      Working Groups <em class="rfc2119">should</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
+        address</a> <em>any</em> substantive review comment about a technical
+      report in a timely manner. </p>
+    Reviewers <em class="rfc2119">should</em> send substantive technical
+    reviews as early as possible. Working Groups are often reluctant to make <a
+      href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#substantive-change">substantive
+      changes</a> to a mature document, particularly if this would cause
+    significant compatibility problems due to existing implementation. Working
+    Groups <em class="rfc2119">should</em> record substantive or interesting
+    proposals raised by reviews but not incorporated into a current
+    specification.
+    <h4><a class="mozTocH4" id="mozTocId921995"></a>7.2.2 <a id="wide-review">Wide
+        Review</a></h4>
     <p>The requirements for <dfn>wide review</dfn> are not precisely defined by
       the process. The objective is to ensure that the entire set of
       stakeholders of the Web community, including the general public, have had
@@ -399,7 +455,8 @@
       receiving many detailed reviews is not necessarily the same as wide
       review, since they may only represent comment from a small segment of the
       relevant stakeholder community.</p>
-    <h4 id="implementation-experience">7.2.3 Implementation Experience</h4>
+    <h4 id="implementation-experience"><a class="mozTocH4" id="mozTocId547761"></a>7.2.3
+      Implementation Experience</h4>
     <p>Implementation experience is required to show that a specification is
       sufficiently clear, complete, and relevant to market needs, to ensure that
       independent interoperable implementations of each feature of the
@@ -424,44 +481,12 @@
       wish to develop tests in concert with implementation efforts.</p>
     <ul>
     </ul>
-    <h3>7.3 <a name="doc-reviews" id="doc-reviews">Reviews and Review
-        Responsibilities</a></h3>
-    <p>A document is available for review from the moment it is first published.
-      Working Groups <em class="rfc2119">should</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
-        address</a> <em>any</em> substantive review comment about a technical
-      report in a timely manner. </p>
-    Reviewers <em class="rfc2119">should</em> send substantive technical
-    reviews as early as possible. Working Groups are often reluctant to make <a
-      href="#substantive-change">substantive changes</a> to a mature document,
-    particularly if this would cause significant compatibility problems due to
-    existing implementation. Working Groups <em class="rfc2119">should</em>
-    record substantive or interesting proposals raised by reviews but not
-    incorporated into a current specification.
-    <h3>7.4 <a name="rec-advance" id="rec-advance">Advancing a Technical Report
-        to Recommendation</a></h3>
-    <p>W3C follows these steps when advancing a technical report to
-      Recommendation.</p>
-    <ol>
-      <li><a href="#first-wd">Publication of the First Public Working Draft</a>,</li>
-      <li><a href="#hb-wd">Publication of zero or more revised Public Working
-          Drafts</a>.</li>
-      <li><a href="#last-call">Publication of a Candidate Recommendation</a>.</li>
-      <li><a href="#rec-publication">Publication as a Recommendation</a>.</li>
-      <li>Possibly, <a href="#rec-edited">Publication as an Edited
-          Recommendation</a></li>
-    </ol>
-    <p>W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a
-        technical report</a> at any time.</p>
-    <p>The Director <em class="rfc2119">may</em> decline a request to advance
-      in maturity level, requiring a Working Group to conduct further work, and
-      <em class="rfc2119">may</em> require the specification to return to a
-      lower <a href="#maturity-level">maturity level</a>. The Director <em class="rfc2119">must</em>
-      inform the <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
-        Committee</a> and Working Group Chairs when a Working Group's request
-      for a specification to advance in maturity level is declined and and the
-      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>
+    <br>
+    <br>
+    <h4 id="working-draft"><a class="mozTocH4" id="mozTocId899983"></a>7.4.1
+      Working Draft</h4>
+    <h5><a class="mozTocH5" id="mozTocId653661"></a>7.4.1.a <a name="first-wd"
+        id="first-wd">First Public Working Draft</a></h5>
     <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>
@@ -480,7 +505,8 @@
       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.1.b Revised Public Working Drafts</h5>
+    <h5 id="revised-wd"><a class="mozTocH5" id="mozTocId972800"></a>7.4.1.b
+      Revised Public Working Drafts</h5>
     <p>A Working Group <em class="rfc2119">should</em> publish a Working Draft
       to the W3C Technical Reports page when there have been significant changes
       to the document that would benefit from review from beyond the Working
@@ -516,7 +542,8 @@
       <li><a href="#last-call">Candidate recommendation</a>.</li>
       <li><a href="#tr-end">Working Group Note</a></li>
     </ul>
-    <h4>7.4.2 <a name="last-call" id="last-call">Candidate Recommendation </a></h4>
+    <h4><a class="mozTocH4" id="mozTocId115371"></a>7.4.2 <a name="last-call" id="last-call">Candidate
+        Recommendation </a></h4>
     <p>To publish a Candidate recommendation, in addition to meeting the <a href="#transition-reqs">general
         requirements for advancement</a> a Working Group</p>
     <ul>
@@ -557,6 +584,10 @@
         expected next step)</li>
       <li><a href="#tr-end">Working Group Note</a></li>
     </ul>
+    <p class="issue">Add an explanation of publishing a revised Candidate
+      Recommendation. <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a></p>
+    <ul>
+    </ul>
     <p>If there are any <a href="#substantive-change">substantive changes</a>
       made to a Candidate Recommendation other than to remove features
       explicitly identified as "at risk", the Working Group <em class="rfc2119">must</em>
@@ -565,10 +596,11 @@
     <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.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
-        Candidate Recommendation as a W3C Recommendation</a></h5>
+    <h4><a class="mozTocH4" id="mozTocId525956"></a>7.4.3 <a name="rec-publication"
+        id="rec-publication">Publication of a W3C Recommendation</a></h4>
+    <h5><a class="mozTocH5" id="mozTocId774333"></a><a name="lcrec-publication"
+        id="lcrec-publication">Publishing a Candidate Recommendation as a W3C
+        Recommendation</a></h5>
     <p>To publish a Candidate Recommendation as a W3C Recommendation, a Working
       Group</p>
     <ul>
@@ -605,8 +637,9 @@
           compelling reason to do so. In such a case, the Director <em class="rfc2119">should</em>
           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>
+    <h5 id="rec-edited"><a class="mozTocH5" id="mozTocId872144"></a>Publishing
+      an Edited Recommendation (See also <a href="#rec-modify">Modifying a
+        Recommendation</a> below)</h5>
     <p>To publish an Edited Recommendation as a W3C Recommendation, a Working
       Group</p>
     <ul>
@@ -617,8 +650,8 @@
         </a></li>
       <li><em class="rfc2119">should</em> address all errata.</li>
     </ul>
-    <h5 id="for-all-recs">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
+    <h5 id="for-all-recs"><a class="mozTocH5" id="mozTocId187610"></a>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>
     <ul>
       <li>The Director <em class="rfc2119">must</em> announce the provisional
@@ -651,8 +684,82 @@
           an Edited Recommendation</a>, or</li>
       <li><em class="rfc2119">may</em> be <a href="#rec-rescind">rescinded</a>.</li>
     </ul>
-    <h3>7.5 <a name="tr-end" id="tr-end">Publishing a Working Group or Interest
-        Group Note</a></h3>
+    <h3><a class="mozTocH3" id="mozTocId548274"></a>7.6 <a name="rec-modify" id="rec-modify">Modifying
+        a W3C Recommendation</a></h3>
+    <p>The following sections discuss the management of errors and the process
+      for making changes to a Recommendation.</p>
+    <h4><a class="mozTocH4" id="mozTocId169012"></a>7.6.1 <a name="errata" id="errata">Errata
+        Management</a></h4>
+    <p>Tracking errors is an important part of a Working Group's ongoing care of
+      a Recommendation; for this reason, the scope of a Working Group charter
+      generally allows time for work after publication of a Recommendation. In
+      this Process Document, the term "erratum" (plural "errata") refers to any
+      class of mistake, from mere editorial to a serious error that may affect
+      the conformance with the Recommendation by software or content (e.g.,
+      content validity). <strong>Note:</strong> Before a document becomes a
+      Recommendation, the W3C Process focuses on <a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#substantive-change">substantive
+        changes</a> (those related to prior reviews). After a document has been
+      published as Recommendation, the W3C Process focuses on those changes to a
+      technical report that might affect the conformance of content or deployed
+      software.</p>
+    <p>Working Groups <span class="rfc2119">must</span> track errata on an
+      "errata page." An errata page is a list of enumerated errors, possibly
+      accompanied by corrections. Each Recommendation links to an errata page;
+      see the Team's <a href="http://www.w3.org/Guide/pubrules">Publication
+        Rules</a>.</p>
+    <p>A correction is first "proposed" by the Working Group. A correction
+      becomes part of the Recommendation by the process described below.</p>
+    <p>A Working Group <span class="rfc2119">should</span> keep their errata
+      pages up-to-date, as errors are reported by readers and implementers. A
+      Working Group <span class="rfc2119">must</span> report errata page
+      changes to interested parties, notably when corrections are proposed or
+      incorporated into an Edited Recommendation, according to the Team's
+      requirements.</p>
+    <h4><a class="mozTocH4" id="mozTocId644984"></a>7.6.2 <a name="correction-classes"
+        id="correction-classes">Classes of Changes to a Recommendation</a></h4>
+    <p>This document distinguishes the following classes of changes to a
+      Recommendation.</p>
+    <dl>
+      <dt>1. No changes to text content</dt>
+      <dd>These changes include fixing broken links, style sheets or invalid
+        markup.</dd>
+      <dt>2. Corrections that do not affect conformance</dt>
+      <dd>Editorial changes or clarifications that do not change the technical
+        content of the specification.</dd>
+      <dt>3. Corrections that do not add new features</dt>
+      <dd>These changes <span class="rfc2119">may</span> affect conformance to
+        the Recommendation. A change that affects conformance is one that:
+        <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>
+        </ul>
+      </dd>
+      <dt>4. New features</dt>
+    </dl>
+    <p>The first two classes of change require no technical review of the
+      proposed changes. A Working Group <span class="rfc2119">may</span>
+      request republication of a Recommendation for these classes of change, or
+      W3C <span class="rfc2119">may</span> republish a Recommendation with this
+      class of change. The modified Recommendation is published according to the
+      Team's requirements, including <a href="http://www.w3.org/Guide/pubrules">Publication
+        Rules</a> [<a href="file:///Users/chaals/Documents/w3c/ab/AB/refs.html#ref-pubrules">PUB31</a>]
+      and the <a href="http://www.w3.org/2003/01/republishing/">Requirements
+        for modification of W3C Technical Reports</a> [[email protected]@].</p>
+    <p>For the third class of change, a Working Group <span class="rfc2119">must</span>
+      request publication of an <a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#rec-edited">Edited
+        Recommendation</a>.</p>
+    <p>For the fourth class of change, which introduces a new feature or
+      features, W3C <span class="rfc2119">must</span> follow the full process
+      of <a href="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#rec-advance">advancing
+        a technical report to Recommendation</a>.</p>
+    <ul>
+    </ul>
+    <h3><a class="mozTocH3" id="mozTocId325969"></a>7.5 <a name="tr-end" id="tr-end">Publishing
+        a Working Group or Interest Group Note</a></h3>
     <p>Working Groups and Interest Groups publish material that is not a formal
       specification as Notes. This may include supporting documentation for a
       specification, such as requirements, use cases, good practices and the
@@ -686,74 +793,9 @@
       commitments for Working Group Notes, only for W3C Recommendations. See
       also 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>
-    <h3>7.6 <a name="rec-modify" id="rec-modify">Modifying a W3C Recommendation</a></h3>
-    <p>The following sections discuss the management of errors and the process
-      for making changes to a Recommendation.</p>
-    <h4>7.6.1 <a name="errata" id="errata">Errata Management</a></h4>
-    <p>Tracking errors is an important part of a Working Group's ongoing care of
-      a Recommendation; for this reason, the scope of a Working Group charter
-      generally allows time for work after publication of a Recommendation. In
-      this Process Document, the term "erratum" (plural "errata") refers to any
-      class of mistake, from mere editorial to a serious error that may affect
-      the conformance with the Recommendation by software or content (e.g.,
-      content validity). <strong>Note:</strong> Before a document becomes a
-      Recommendation, the W3C Process focuses on <a href="#substantive-change">substantive
-        changes</a> (those related to prior reviews). After a document has been
-      published as Recommendation, the W3C Process focuses on those changes to a
-      technical report that might affect the conformance of content or deployed
-      software.</p>
-    <p>Working Groups <span class="rfc2119">must</span> track errata on an
-      "errata page." An errata page is a list of enumerated errors, possibly
-      accompanied by corrections. Each Recommendation links to an errata page;
-      see the Team's <a href="http://www.w3.org/Guide/pubrules">Publication
-        Rules</a>.</p>
-    <p>A correction is first "proposed" by the Working Group. A correction
-      becomes part of the Recommendation by the process described below.</p>
-    <p>A Working Group <span class="rfc2119">should</span> keep their errata
-      pages up-to-date, as errors are reported by readers and implementers. A
-      Working Group <span class="rfc2119">must</span> report errata page
-      changes to interested parties, notably when corrections are proposed or incorporated
-      into an Edited Recommendation, according to the Team's requirements.</p>
-    <h4>7.6.2 <a name="correction-classes" id="correction-classes">Classes of
-        Changes to a Recommendation</a></h4>
-    <p>This document distinguishes the following classes of changes to a
-      Recommendation.</p>
-    <dl>
-      <dt>1. No changes to text content</dt>
-      <dd>These changes include fixing broken links, style sheets or invalid
-        markup.</dd>
-      <dt>2. Corrections that do not affect conformance</dt>
-      <dd>Editorial changes or clarifications that do not change the technical
-        content of the specification.</dd>
-      <dt>3. Corrections that do not add new features</dt>
-      <dd>These changes <span class="rfc2119">may</span> affect conformance to
-        the Recommendation. A change that affects conformance is one that:
-        <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>
-        </ul>
-      </dd>
-      <dt>4. New features</dt>
-    </dl>
-    <p>The first two classes of change require no technical review of the
-      proposed changes. A Working Group <span class="rfc2119">may</span>
-      request republication of a Recommendation for these classes of change, or
-      W3C <span class="rfc2119">may</span> republish a Recommendation with this
-      class of change. The modified Recommendation is published according to the
-      Team's requirements, including <a href="http://www.w3.org/Guide/pubrules">Publication
-        Rules</a> [<a href="refs.html#ref-pubrules">PUB31</a>] and the <a href="http://www.w3.org/2003/01/republishing/">Requirements
-        for modification of W3C Technical Reports</a> [[email protected]@].</p>
-    <p>For the third class of change, a Working Group <span class="rfc2119">must</span>
-      request publication of an <a href="#rec-edited">Edited Recommendation</a>.</p>
-    <p>For the fourth class of change, which introduces a new feature or
-      features, W3C <span class="rfc2119">must</span> follow the full process
-      of <a href="#rec-advance">advancing a technical report to Recommendation</a>.</p>
-    <h3>7.7 <a name="rec-rescind" id="rec-rescind">Rescinding a W3C
-        Recommendation</a></h3>
+    <br>
+    <h3><a class="mozTocH3" id="mozTocId22672"></a>7.7 <a name="rec-rescind" id="rec-rescind">Rescinding
+        a W3C Recommendation</a></h3>
     <p>W3C <em class="rfc2119">may</em> rescind a Recommendation, for example
       if the Recommendation contains many errors that conflict with a later
       version or if W3C discovers burdensome patent claims that affect
@@ -810,7 +852,8 @@
       Rescinded Recommendation. 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="#ACAppeal">appeal</a>
       the decision.</p>
-    <h3 id="good-practice">Good practices</h3>
+    <h3 id="good-practice"><a class="mozTocH3" id="mozTocId168231"></a>Good
+      practices</h3>
     <p>Refer to <a href="http://www.w3.org/2003/05/Transitions">"How to
         Organize a Recommendation Track Transition"</a> in the <a href="http://www.w3.org/Guide/">Member
         guide</a> for practical information about preparing for the reviews and