tr.html
changeset 54 840ff6a43e74
parent 53 2c13766abd84
child 55 6bd6536dd075
--- a/tr.html	Wed Dec 11 19:04:30 2013 +0400
+++ b/tr.html	Wed Dec 11 20:02:47 2013 +0400
@@ -58,11 +58,9 @@
           version.</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>
+          Sections have now been renumbered, the "outline" (heading structure)
+          rebuilt and some headings changed. No content has been deleted since
+          the last commit (except in this introductory material).</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>
@@ -80,9 +78,9 @@
             process for such changes</a>, subject to the resolution of <a href="https://www.w3.org/community/w3process/track/issues/39">ISSUE-39</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, Elika
-          Etimad, Ivan Herman, Ian Hickson, Ian Jacobs, Jeff Jaffe, Chris
-          Lilley, Ralph Swick, Anne van Kesteren, Steve Zilles, and many people
-          I have forgotten to acknowledge for suggestions, comments and
+          Etimad, Fantasai, Ivan Herman, Ian Hickson, Ian Jacobs, Jeff Jaffe,
+          Chris Lilley, Ralph Swick, Anne van Kesteren, Steve Zilles, and many
+          people I have forgotten to acknowledge for suggestions, comments and
           discussions that helped me sort out my thinking, and to Ora Lassila
           for the original version of the image that illustrates the normal
           process of a W3C Recommendation-track document. </p>
@@ -102,6 +100,9 @@
           <li>Last Call and Candidate Recommendation have been collapsed
             together. Some of the requirements are therefore enforced earlier in
             the process.</li>
+          <li>There is a stronger emphasis (without creating new formal
+            requirements) on getting review and testing implementation as early
+            as possible. How to do this is left to Working Groups to determine.</li>
           <li>Proposed Recommendation is no longer a separate step. Advisory
             Committee review now begins at the same time as Candidate
             recommendation, and ends 4 weeks after the Working group has
@@ -136,74 +137,79 @@
     <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><br>
-    <h3><a class="mozTocH3" id="mozTocId308503"></a>Table of Contents</h3>
-    <br>
+      </p>
+    <h3>Table of Contents</h3>
     <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>
+      <li><a href="#mozTocId615339">Table of Contents</a></li>
+      <li><a href="#mozTocId661463">7.1 W3C Technical Reports</a>
         <ul>
-          <li><a href="#mozTocId859663">7.2.1 Substantive Change</a></li>
+          <li><a href="#mozTocId598359">7.1.1 Recommendations and Notes</a></li>
+          <li><a href="#mozTocId643257">7.1.2 Maturity Levels</a></li>
         </ul>
       </li>
-      <li><a href="#mozTocId647919">7.3 Reviews and Review Responsibilities</a>
+      <li><a href="#mozTocId674003">7.2 General requirements and definitions</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>
+          <li><a href="#mozTocId840436">7.2.1 General requirements for Technical
+              Reports</a></li>
+          <li><a href="#mozTocId650463">7.2.2 Advancement on the Recommendation
+              Track</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>
+              <li><a href="#mozTocId787038">7.2.2.1 Substantive Change</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>
+          <li><a href="#mozTocId891540">7.2.3 Reviews and Review
+              Responsibilities</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>
+              <li><a href="#mozTocId712209">7.2.3.1 Wide Review</a></li>
             </ul>
           </li>
+          <li><a href="#mozTocId677214">7.2.4 Implementation Experience</a></li>
         </ul>
       </li>
-      <li><a href="#mozTocId548274">7.6 Modifying a W3C Recommendation</a>
+      <li><a href="#mozTocId124435">7.3 Working Draft</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>
+          <li><a href="#mozTocId531921">7.3.1 First Public Working Draft</a></li>
+          <li><a href="#mozTocId557161">7.3.2 Revised Public Working Drafts</a></li>
         </ul>
       </li>
-      <li><a href="#mozTocId325969">7.5 Publishing a Working Group or Interest
+      <li><a href="#mozTocId603428">7.4 Candidate Recommendation</a>
+        <ul>
+          <li><a href="#mozTocId884719">7.4.1 Revised Candidate Recommendation</a></li>
+        </ul>
+      </li>
+      <li><a href="#mozTocId388392">7.5 W3C Recommendation</a>
+        <ul>
+          <li><a href="#mozTocId753802">7.5.1 For all W3C Recommendations</a></li>
+          <li><a href="#mozTocId368357">7.5.2 Publishing a Candidate
+              Recommendation as a W3C Recommendation</a></li>
+        </ul>
+      </li>
+      <li><a href="#mozTocId66258">7.6 Modifying a W3C Recommendation</a>
+        <ul>
+          <li><a href="#mozTocId861101">7.6.1 Errata Management</a></li>
+          <li><a href="#mozTocId582942">7.6.2 Classes of Changes to a
+              Recommendation</a></li>
+          <li><a href="#mozTocId478895">7.6.3 Revised Recommendation</a></li>
+        </ul>
+      </li>
+      <li><a href="#mozTocId663232">7.7 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>
+      <li><a href="#mozTocId592607">7.8 Rescinding a W3C Recommendation</a></li>
+      <li><a href="#mozTocId806006">Further reading</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>
+    <h3>7.1 <a name="rec-advance" id="rec-advance">W3C Technical Reports</a></h3>
+    <h4>7.1.1 Recommendations and Notes</h4>
     <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>
+      <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>
       <svg xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg"
@@ -211,13 +217,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>
-            <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>
+            <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">
-            <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>
+            <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>
@@ -228,9 +232,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>
-            <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>
+            <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"
@@ -246,27 +249,25 @@
               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="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>
+            <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"
               stroke="black" fill="black"></polygon> </g> </g> </svg> </p>
-    <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>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="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
+      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>
     <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>
+      can go from Rec-track to Note and back, to this section. <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a></p>
+    <h4>7.1.2 <a name="maturity-levels" id="maturity-levels">Maturity Levels</a></h4>
     <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
@@ -330,8 +331,9 @@
       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 id="general-requirements"><a class="mozTocH3" id="mozTocId135327"></a>General
-      requirements for Technical Reports</h3>
+    <h3>7.2 General requirements and definitions</h3>
+    <h4 id="general-requirements">7.2.1 General requirements for Technical
+      Reports</h4>
     <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>]
@@ -339,7 +341,7 @@
       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
+      process <em class="rfc2119 old">must</em> 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>
@@ -376,9 +378,8 @@
       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>
+    <h4>7.2.2 <a name="transition-reqs" id="transition-reqs">Advancement on the
+        Recommendation Track</a></h4>
     <p>For <em>all</em> requests to advance a specification to a new maturity
       level other than Note the Working Group:</p>
     <ul>
@@ -406,31 +407,28 @@
       mechanical approval is normally fairly automatic, whereas for later stages
       there is generally a formal review meeting to ensure the requirements have
       been met before Director's approval is given.</p>
-    <ul>
-    </ul>
-    <h4 id="substantive-change"><a class="mozTocH4" id="mozTocId859663"></a>7.2.1
-      Substantive Change</h4>
+    <h5 id="substantive-change">7.2.2.1 Substantive Change</h5>
+    <p class="issue">This subsection will probably get merged into the later
+      section on changes, as per <a href="http://www.w3.org/community/w3process/track/issues/72">ISSUE-72</a></p>
     <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>
-    <h3><a class="mozTocH3" id="mozTocId647919"></a>7.3 <a name="doc-reviews" id="doc-reviews">Reviews
-        and Review Responsibilities</a></h3>
+    <h4>7.2.3 <a name="doc-reviews" id="doc-reviews">Reviews and Review
+        Responsibilities</a></h4>
     <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>
+      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.
+    <h5>7.2.3.1 <a id="wide-review">Wide Review</a></h5>
     <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
@@ -455,8 +453,7 @@
       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"><a class="mozTocH4" id="mozTocId547761"></a>7.2.3
-      Implementation Experience</h4>
+    <h4 id="implementation-experience">7.2.4 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
@@ -479,14 +476,8 @@
       more effectively if they plan how they will demonstrate interoperable
       implementations early in the development process; for example, they may
       wish to develop tests in concert with implementation efforts.</p>
-    <ul>
-    </ul>
-    <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>
+    <h3 id="working-draft">7.3 Working Draft</h3>
+    <h4>7.3.1 <a name="first-wd" id="first-wd">First Public Working Draft</a></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>
@@ -505,8 +496,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"><a class="mozTocH5" id="mozTocId972800"></a>7.4.1.b
-      Revised Public Working Drafts</h5>
+    <h4 id="revised-wd">7.3.2 Revised Public Working Drafts</h4>
     <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
@@ -515,7 +505,6 @@
       Working Group <em class="rfc2119">should</em> publish a revised Working
       Draft, whose status section <em class="rfc2119">should</em> indicate
       reasons for the lack of change. </p>
-    <p> </p>
     <p>To publish a revised Working draft, a Working Group </p>
     <ul>
       <li><em class="rfc2119">must</em> record the group's decision to request
@@ -542,8 +531,7 @@
       <li><a href="#last-call">Candidate recommendation</a>.</li>
       <li><a href="#tr-end">Working Group Note</a></li>
     </ul>
-    <h4><a class="mozTocH4" id="mozTocId115371"></a>7.4.2 <a name="last-call" id="last-call">Candidate
-        Recommendation </a></h4>
+    <h3>7.4 <a name="last-call" id="last-call">Candidate Recommendation </a></h3>
     <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>
@@ -586,8 +574,6 @@
     </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>
@@ -596,11 +582,37 @@
     <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><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>
+    <h4>7.4.1 Revised Candidate Recommendation</h4>
+    <h3>7.5 <a name="rec-publication" id="rec-publication">W3C Recommendation</a></h3>
+    <h4 id="for-all-recs"><a id="rec-requirements">7.5.1 For <strong>all</strong>
+        W3C Recommendations</a></h4>
+    <p id="for-all-recs">In addition to meeting the <a href="#transition-reqs">general
+        requirements for advancement</a>,</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,</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 <em class="rfc2119">must</em>
+        publish the substantive content of the dissent to W3C and the general
+        public, 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 at least 14 days before publication as a W3C
+        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="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, and</li>
+      <li>The "Status of the Document" <em class="rfc2119">must</em> reflect
+        whether it is provisionally approved, or published as a W3C
+        Recommendation.</li>
+    </ul>
+    <h4><a name="lcrec-publication" id="lcrec-publication">7.5.2 Publishing a
+        Candidate Recommendation as a W3C Recommendation</a></h4>
     <p>To publish a Candidate Recommendation as a W3C Recommendation, a Working
       Group</p>
     <ul>
@@ -630,52 +642,12 @@
           Request for publication of a W3C Recommendation less than 35 days
           after the publication of the Candidate Recommendation on which is it
           based [editor's note - this is to allow for the patent policy
-          exclusion period to expire], and<br>
-        </span></li>
+          exclusion period to expire], and </span></li>
       <li><span><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. </span></li>
     </ul>
-    <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>
-      <li><em class="rfc2119">must</em> republish the document, identifying it
-        as the basis of a Request for Recommendation,</li>
-      <li><em class="rfc2119">must</em> show that the document has received <a
-          href="#wide-review">wide review, and<br>
-        </a></li>
-      <li><em class="rfc2119">should</em> address all errata.</li>
-    </ul>
-    <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
-        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,</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 <em class="rfc2119">must</em>
-        publish the substantive content of the dissent to W3C and the general
-        public, 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 &gt;at least 14 days before publication as a
-        W3C 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="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, and</li>
-      <li>The "Status of the Document" <em class="rfc2119">must</em> reflect
-        whether it is provisionally approved, or published as a W3C
-        Recommendation.</li>
-    </ul>
     <p>Possible next steps:</p>
     <ul>
       <li>A W3C Recommendation normally retains its status indefinitely. However
@@ -684,12 +656,10 @@
           an Edited Recommendation</a>, or</li>
       <li><em class="rfc2119">may</em> be <a href="#rec-rescind">rescinded</a>.</li>
     </ul>
-    <h3><a class="mozTocH3" id="mozTocId548274"></a>7.6 <a name="rec-modify" id="rec-modify">Modifying
-        a W3C Recommendation</a></h3>
+    <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><a class="mozTocH4" id="mozTocId169012"></a>7.6.1 <a name="errata" id="errata">Errata
-        Management</a></h4>
+    <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
@@ -697,7 +667,7 @@
       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
+      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
@@ -715,8 +685,8 @@
       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>
+    <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>
@@ -746,20 +716,26 @@
       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
+        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> [PUB@@].</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>
+      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="file:///Users/chaals/Documents/w3c/ab/AB/tr.html#rec-advance">advancing
-        a technical report to Recommendation</a>.</p>
+      of <a href="#rec-advance">advancing a technical report to Recommendation</a>.</p>
+    <h4>7.6.3 Revised Recommendation</h4>
+    <p>To publish an Edited Recommendation as a W3C Recommendation, in addition
+      to meeting the <a href="#rec-requirements">requirements for all W3C
+        Recommendations</a>, a Working Group</p>
     <ul>
+      <li><em class="rfc2119">must</em> republish the document, identifying it
+        as the basis of a Request for Recommendation,</li>
+      <li><em class="rfc2119">must</em> show that the document has received <a
+          href="#wide-review">wide review</a>, and </li>
+      <li><em class="rfc2119">should</em> address all errata.</li>
     </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>
+    <h3>7.7 <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
@@ -793,9 +769,8 @@
       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>
-    <br>
-    <h3><a class="mozTocH3" id="mozTocId22672"></a>7.7 <a name="rec-rescind" id="rec-rescind">Rescinding
-        a W3C Recommendation</a></h3>
+    <h3>7.8 <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
@@ -848,12 +823,11 @@
       in Advisory Committee reviews, the Director <em class="rfc2119">must</em>
       publish the substantive content of the dissent to W3C <strong>and the
         public</strong>, 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 &gt;at least 14 days before publication as a
+        address</a> the comment at least 14 days before publication as a
       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"><a class="mozTocH3" id="mozTocId168231"></a>Good
-      practices</h3>
+    <h3 id="good-practice">Further reading</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