Renumber 6-15, tweak revision diagram, prepare status for publishing this version, fix change list
authorcharles
Thu, 23 Apr 2015 17:18:22 -0700
changeset 155 5789e30470d4
parent 154 c7f0dddfc5eb
child 156 79b04ebab5d3
child 158 90bbfd0e954a
child 169 f743b62f959d
Renumber 6-15, tweak revision diagram, prepare status for publishing this version, fix change list
cover.html
--- a/cover.html	Thu Apr 23 16:55:57 2015 -0700
+++ b/cover.html	Thu Apr 23 17:18:22 2015 -0700
@@ -19,7 +19,7 @@
   <body>
     <div class="head"><a href="http://www.w3.org/"><img alt="W3C" src="https://www.w3.org/Icons/w3c_home" height="48" width="72"></a>
       <h1>W3C Draft Process Document</h1>
-      <h2 class="notoc">3 March 2015 Editor's Draft</h2>
+      <h2 class="notoc">23 April 2015 Editor's Draft</h2>
       <dl>
         <dt>Latest Editor's version:</dt>
         <dd> <a href="https://dvcs.w3.org/hg/AB/raw-file/default/cover.html">https://dvcs.w3.org/hg/AB/raw-file/default/cover.html</a></dd>
@@ -51,20 +51,16 @@
     <p>W3C, including all existing chartered groups, follows the <a href="http://www.w3.org/Consortium/Process/">most recent operative
         Process Document</a> announced to the Membership.</p>
     <p>This document is developed by the Advisory Board's Process Task Force (which anyone may join) working within the <a href="http://www.w3.org/community/w3process/">Revising
-        W3C Process Community Group</a>. This is the 25 January 2015 Editor's draft for the proposed next version of the W3C Process
-      Document. This document is based on the 30 September review draft, itself based on the 1 August 2014 Process, developed between the <a
-        href="/2002/ab/">W3C Advisory Board</a> and the <a href="http://www.w3.org/community/w3process/">Revising W3C Process Community
-        Group</a> and adopted as the currently operative Process.</p>
-    <p>This draft is expected to be proposed to the Advisory Committee as a working draft with an explicit request for comment, as a "last
-      call" before a formal AC review on whether to adopt this as the new operative Process document. Further revision is expected, to be
-      adopted in 2016.</p>
-    <p>Note that sections have not been renumbered from the current Operative version. This is intended to facilitate comparison for review.
-      Renumbering will occur before adoption of a New Process document.</p>
-    <p>In <em>this draft</em> the default channel for <a href="#ACReview">AC review</a> has been removed in favor of a requirement for
-      each review to specify a default (<a href="http://www.w3.org/community/w3process/track/issues/154">ISSUE-154</a>), a procedure for <a
-        href="#resignation">resignation</a> from Working (and Interest Groups has been provided (<a href="http://www.w3.org/community/w3process/track/issues/151">ISSUE-151</a>),
-      and <a href="http://www.w3.org/community/w3process/track/issues/152">ISSUE-152</a> is described. A <a href="#changes">change history</a>
-      (compared to the 2014 Process Document) forms part of the draft.</p>
+        W3C Process Community Group</a>. This is the 23 April 2015 Editor's draft for the proposed next version of the W3C Process Document.
+      This document is based on the 3 March review draft which was proposed to the Advisory Committee as a "last call" for an update to the
+      1 August 2014 Process.</p>
+    <p>This draft is expected to be proposed to the Advisory Committee for a formal AC review on whether to adopt this as the new operative
+      Process document. Further revision to the Process is expected as needed.</p>
+    <p>Sections have been renumbered, with the most notable change from the current Operative version being that section numbers 5 and above
+      in this draft correspond to section numbers higher by 1 in the August 2014 Process.</p>
+    <p>In <em>this draft</em> <a href="http://www.w3.org/community/w3process/track/issues/152">ISSUE-152</a> has been resolved, by
+      allowing a Working Group to propose editorial corrections directly as a Proposed Recommendation. A <a href="#changes">change history</a>
+      (compared to the 2014 Process Document) forms part of this draft.</p>
     <p>Comment is invited on the draft. Please send comments to <a href="mailto:[email protected]">[email protected]</a> (<a href="http://lists.w3.org/Archives/Public/public-w3process/">Mailing
         list archive</a>, publicly available) or to [email protected] (<a href="http://lists.w3.org/Archives/Member/process-issues">Member-only
         archive</a>). A <a href="https://www.w3.org/community/w3process/track/">Public Issue Tracker</a> and <a href="https://dvcs.w3.org/hg/AB/">detailed
@@ -95,17 +91,16 @@
               Architecture Group</a></li>
           <li class="tocline2"><a href="#Policies" class="tocxref">3 General Policies for W3C Groups</a></li>
           <li class="tocline2"><a href="#dissemination" class="tocxref">4 Dissemination Policies</a></li>
-          <li class="tocline2"><s>5 Activities</s></li>
-          <li class="tocline2"><a href="#GAGeneral" class="tocxref">6 Working Groups and Interest Groups</a></li>
-          <li class="tocline2"><a href="#Reports" class="tocxref">7 W3C Technical Report Development Process</a></li>
-          <li class="tocline2"><a href="#ReviewAppeal" class="tocxref">8 Advisory Committee Reviews, Appeals, and Votes</a></li>
-          <li class="tocline2"><a href="#GAEvents" class="tocxref">9 Workshops and Symposia</a></li>
-          <li class="tocline2"><a href="#Liaisons" class="tocxref">10 Liaisons</a></li>
-          <li class="tocline2"><a href="#Submission" class="tocxref">11 Member Submission Process</a></li>
-          <li class="tocline2"><a href="#GAProcess" class="tocxref">12 Process Evolution</a></li>
-          <li class="tocline2"><a href="#references" class="tocxref">13 References</a></li>
-          <li class="tocline2"><a href="#acks" class="tocxref">14 Acknowledgments</a></li>
-          <li class="tocline2"><a href="#changes" class="tocxref">15 Changes</a></li>
+          <li class="tocline2"><a href="#GAGeneral" class="tocxref">5 Working Groups and Interest Groups</a></li>
+          <li class="tocline2"><a href="#Reports" class="tocxref">6 W3C Technical Report Development Process</a></li>
+          <li class="tocline2"><a href="#ReviewAppeal" class="tocxref">7 Advisory Committee Reviews, Appeals, and Votes</a></li>
+          <li class="tocline2"><a href="#GAEvents" class="tocxref">8 Workshops and Symposia</a></li>
+          <li class="tocline2"><a href="#Liaisons" class="tocxref">9 Liaisons</a></li>
+          <li class="tocline2"><a href="#Submission" class="tocxref">10 Member Submission Process</a></li>
+          <li class="tocline2"><a href="#GAProcess" class="tocxref">11 Process Evolution</a></li>
+          <li class="tocline2"><a href="#references" class="tocxref">12 References</a></li>
+          <li class="tocline2"><a href="#acks" class="tocxref">13 Acknowledgments</a></li>
+          <li class="tocline2"><a href="#changes" class="tocxref">14 Changes</a></li>
         </ul>
       </div>
     </div>
@@ -180,109 +175,109 @@
             </li>
           </ul>
         </li>
-        <li class="tocline2"><a href="#GAGeneral">6 Working Groups and Interest Groups</a>
+        <li class="tocline2"><a href="#GAGeneral">5 Working Groups and Interest Groups</a>
           <ul class="toc">
-            <li class="tocline3"><a href="#ReqsAllGroups">6.1 Requirements for All Working and Interest Groups</a></li>
-            <li class="tocline3"><a href="#GroupsWG">6.2 Working Groups and Interest Groups</a>
+            <li class="tocline3"><a href="#ReqsAllGroups">5.1 Requirements for All Working and Interest Groups</a></li>
+            <li class="tocline3"><a href="#GroupsWG">5.2 Working Groups and Interest Groups</a>
               <ul class="toc">
-                <li class="tocline4"><a href="#group-participation">6.2.1 Working Group and Interest Group Participation Requirements</a></li>
-                <li class="tocline4"><a href="#WGCharterDevelopment">6.2.2 Working Group and Interest Group Charter Development</a></li>
-                <li class="tocline4"><a href="#CharterReview">6.2.3 Advisory Committee Review of a Working Group or Interest Group Charter</a></li>
-                <li class="tocline4"><a href="#cfp">6.2.4 Call for Participation in a Working Group or Interest Group</a></li>
-                <li class="tocline4"><a href="#charter-extension">6.2.5 Working Group and Interest Group Charter Extension</a></li>
-                <li class="tocline4"><a href="#WGCharter">6.2.6 Working Group and Interest Group Charters</a></li>
-                <li class="tocline4"><a href="#GeneralTermination">6.2.8 Working Group and Interest Group Closure</a></li>
+                <li class="tocline4"><a href="#group-participation">5.2.1 Working Group and Interest Group Participation Requirements</a></li>
+                <li class="tocline4"><a href="#WGCharterDevelopment">5.2.2 Working Group and Interest Group Charter Development</a></li>
+                <li class="tocline4"><a href="#CharterReview">5.2.3 Advisory Committee Review of a Working Group or Interest Group Charter</a></li>
+                <li class="tocline4"><a href="#cfp">5.2.4 Call for Participation in a Working Group or Interest Group</a></li>
+                <li class="tocline4"><a href="#charter-extension">5.2.5 Working Group and Interest Group Charter Extension</a></li>
+                <li class="tocline4"><a href="#WGCharter">5.2.6 Working Group and Interest Group Charters</a></li>
+                <li class="tocline4"><a href="#GeneralTermination">5.2.8 Working Group and Interest Group Closure</a></li>
               </ul>
             </li>
           </ul>
         </li>
-        <li class="tocline2"><a href="#Reports">7 W3C Technical Report Development Process</a>
+        <li class="tocline2"><a href="#Reports">6 W3C Technical Report Development Process</a>
           <ul class="toc">
-            <li><a href="#rec-advance">7.1 W3C Technical Reports</a>
+            <li><a href="#rec-advance">6.1 W3C Technical Reports</a>
               <ul class="toc">
-                <li><a href="#recs-and-notes" id="return-to-wg">7.1.1 Recommendations and Notes</a></li>
-                <li><a href="#maturity-levels">7.1.2 Maturity Levels</a></li>
+                <li><a href="#recs-and-notes" id="return-to-wg">6.1.1 Recommendations and Notes</a></li>
+                <li><a href="#maturity-levels">6.1.2 Maturity Levels</a></li>
               </ul>
             </li>
-            <li><a href="#requirements-and-definitions">7.2 General requirements and definitions</a>
+            <li><a href="#requirements-and-definitions">6.2 General requirements and definitions</a>
               <ul class="toc">
-                <li><a href="#general-requirements">7.2.1 General requirements for Technical Reports</a></li>
-                <li><a href="#transition-reqs">7.2.2 Advancement on the Recommendation Track</a>
+                <li><a href="#general-requirements">6.2.1 General requirements for Technical Reports</a></li>
+                <li><a href="#transition-reqs">6.2.2 Advancement on the Recommendation Track</a>
                   <ul class="toc">
-                    <li><a href="#substantive-change">7.2.2.1 Substantive Change</a></li>
-                  </ul>
-                </li>
-                <li><a href="#doc-reviews">7.2.3 Reviews and Review Responsibilities</a>
-                  <ul class="toc">
-                    <li><a href="#wide-review">7.2.3.1 Wide Review</a></li>
+                    <li><a href="#substantive-change">6.2.2.1 Substantive Change</a></li>
                   </ul>
                 </li>
-                <li><a href="#implementation-experience">7.2.4 Implementation Experience</a> </li>
-                <li><a href="#correction-classes">7.2.5 Classes of Changes to a Recommendation</a></li>
-              </ul>
-            </li>
-            <li><a href="#working-draft">7.3 Working Draft</a>
-              <ul class="toc">
-                <li><a href="#first-wd">7.3.1 First Public Working Draft</a></li>
-                <li><a href="#revised-wd">7.3.2 Revising Public Working Drafts</a></li>
-                <li><a href="#tr-end">7.3.3 Stopping work on a specification</a></li>
+                <li><a href="#doc-reviews">6.2.3 Reviews and Review Responsibilities</a>
+                  <ul class="toc">
+                    <li><a href="#wide-review">6.2.3.1 Wide Review</a></li>
+                  </ul>
+                </li>
+                <li><a href="#implementation-experience">6.2.4 Implementation Experience</a> </li>
+                <li><a href="#correction-classes">6.2.5 Classes of Changes to a Recommendation</a></li>
               </ul>
             </li>
-            <li><a href="#candidate-rec" id="cfi">7.4 Candidate Recommendation</a>
+            <li><a href="#working-draft">6.3 Working Draft</a>
               <ul class="toc">
-                <li><a href="#revised-cr">7.4.1 Revising a Candidate Recommendation</a></li>
+                <li><a href="#first-wd">6.3.1 First Public Working Draft</a></li>
+                <li><a href="#revised-wd">6.3.2 Revising Public Working Drafts</a></li>
+                <li><a href="#tr-end">6.3.3 Stopping work on a specification</a></li>
               </ul>
             </li>
-            <li> <a href="#rec-pr" id="cfr">7.5 Proposed Recommendation</a></li>
-            <li> <a href="#rec-publication">7.6 W3C Recommendation</a></li>
-            <li><a href="#rec-modify">7.7 Modifying a W3C Recommendation</a>
+            <li><a href="#candidate-rec" id="cfi">6.4 Candidate Recommendation</a>
               <ul class="toc">
-                <li><a href="#errata">7.7.1 Errata Management</a></li>
-                <li><a href="#revised-rec" id="cfr-edited">7.7.2 Revising a Recommendation</a></li>
+                <li><a href="#revised-cr">6.4.1 Revising a Candidate Recommendation</a></li>
               </ul>
             </li>
-            <li><a href="#Note">7.8 Publishing a Working Group or Interest Group Note</a></li>
-            <li><a href="#rec-rescind">7.9 Rescinding a W3C Recommendation</a></li>
+            <li> <a href="#rec-pr" id="cfr">6.5 Proposed Recommendation</a></li>
+            <li> <a href="#rec-publication">6.6 W3C Recommendation</a></li>
+            <li><a href="#rec-modify">6.7 Modifying a W3C Recommendation</a>
+              <ul class="toc">
+                <li><a href="#errata">6.7.1 Errata Management</a></li>
+                <li><a href="#revised-rec" id="cfr-edited">6.7.2 Revising a Recommendation</a></li>
+              </ul>
+            </li>
+            <li><a href="#Note">6.8 Publishing a Working Group or Interest Group Note</a></li>
+            <li><a href="#rec-rescind">6.9 Rescinding a W3C Recommendation</a></li>
             <li><a href="#further-reading">Further reading</a></li>
           </ul>
         </li>
-        <li class="tocline2"><a href="#ReviewAppeal">8 Advisory Committee Reviews, Appeals, and Votes</a>
+        <li class="tocline2"><a href="#ReviewAppeal">7 Advisory Committee Reviews, Appeals, and Votes</a>
           <ul class="toc">
-            <li class="tocline3"><a href="#ACReview">8.1 Advisory Committee Reviews</a>
+            <li class="tocline3"><a href="#ACReview">7.1 Advisory Committee Reviews</a>
               <ul class="toc">
-                <li class="tocline4"><a href="#ACReviewStart">8.1.1 Start of a Review Period</a></li>
-                <li class="tocline4"><a href="#ACReviewAfter">8.1.2 After the Review Period</a></li>
+                <li class="tocline4"><a href="#ACReviewStart">7.1.1 Start of a Review Period</a></li>
+                <li class="tocline4"><a href="#ACReviewAfter">7.1.2 After the Review Period</a></li>
               </ul>
             </li>
-            <li class="tocline3"><a href="#ACAppeal">8.2 Appeal by Advisory Committee Representatives</a></li>
-            <li class="tocline3"><a href="#ACVotes">8.3 Advisory Committee Votes</a></li>
+            <li class="tocline3"><a href="#ACAppeal">7.2 Appeal by Advisory Committee Representatives</a></li>
+            <li class="tocline3"><a href="#ACVotes">7.3 Advisory Committee Votes</a></li>
           </ul>
         </li>
-        <li class="tocline2"><a href="#GAEvents">9 Workshops and Symposia</a></li>
-        <li class="tocline2"><a href="#Liaisons">10 Liaisons</a></li>
-        <li class="tocline2"><a href="#Submission">11 Member Submission Process</a>
+        <li class="tocline2"><a href="#GAEvents">8 Workshops and Symposia</a></li>
+        <li class="tocline2"><a href="#Liaisons">9 Liaisons</a></li>
+        <li class="tocline2"><a href="#Submission">10 Member Submission Process</a>
           <ul class="toc">
-            <li class="tocline3"><a href="#SubmissionRights">11.1 Submitter Rights and Obligations</a>
+            <li class="tocline3"><a href="#SubmissionRights">10.1 Submitter Rights and Obligations</a>
               <ul class="toc">
-                <li class="tocline4"><a href="#SubmissionScope">11.1.1 Scope of Member Submissions</a></li>
-                <li class="tocline4"><a href="#SubmissionReqs">11.1.2 Information Required in a Submission Request</a></li>
+                <li class="tocline4"><a href="#SubmissionScope">10.1.1 Scope of Member Submissions</a></li>
+                <li class="tocline4"><a href="#SubmissionReqs">10.1.2 Information Required in a Submission Request</a></li>
               </ul>
             </li>
-            <li class="tocline3"><a href="#TeamSubmissionRights">11.2 Team Rights and Obligations</a></li>
-            <li class="tocline3"><a href="#SubmissionYes">11.3 Acknowledgment of a Submission Request</a></li>
-            <li class="tocline3"><a href="#SubmissionNo">11.4 Rejection of a Submission Request</a></li>
+            <li class="tocline3"><a href="#TeamSubmissionRights">10.2 Team Rights and Obligations</a></li>
+            <li class="tocline3"><a href="#SubmissionYes">10.3 Acknowledgment of a Submission Request</a></li>
+            <li class="tocline3"><a href="#SubmissionNo">10.4 Rejection of a Submission Request</a></li>
           </ul>
         </li>
-        <li class="tocline2"><a href="#GAProcess">12 Process Evolution</a></li>
-        <li class="tocline2"><a href="#references">13 References</a>
+        <li class="tocline2"><a href="#GAProcess">11 Process Evolution</a></li>
+        <li class="tocline2"><a href="#references">12 References</a>
           <ul class="toc">
-            <li class="tocline3"><a href="#public-refs">13.1 Public Resources</a></li>
-            <li class="tocline3"><a href="#member-refs">13.2 Member-only Resources</a></li>
-            <li class="tocline3"><a href="#other-refs">13.3 Other References</a></li>
+            <li class="tocline3"><a href="#public-refs">12.1 Public Resources</a></li>
+            <li class="tocline3"><a href="#member-refs">12.2 Member-only Resources</a></li>
+            <li class="tocline3"><a href="#other-refs">12.3 Other References</a></li>
           </ul>
         </li>
-        <li class="tocline2"><a href="#acks">14 Acknowledgments</a></li>
-        <li class="tocline2"><a href="#changes">15 Changes</a></li>
+        <li class="tocline2"><a href="#acks">13 Acknowledgments</a></li>
+        <li class="tocline2"><a href="#changes">14 Changes</a></li>
       </ul>
     </div>
     <main>
@@ -922,7 +917,7 @@
         </ol>
       </section>
       <section id="ChapterGroups">
-        <h2 id="GAGeneral">6 Working Groups and Interest Groups</h2>
+        <h2 id="GAGeneral">5 Working Groups and Interest Groups</h2>
         <p id="GAGroups">This document defines two types of groups:</p>
         <ol>
           <li><a href="#GroupsWG">Working Groups.</a> Working Groups typically produce deliverables (e.g., <a href="#rec-advance">Recommendation
@@ -933,7 +928,7 @@
         </ol>
         <p>Interest Groups do not publish <a href="#RecsW3C">Recommendation Track technical reports</a>; see information about <a href="#WGNote">maturity
             levels for Interest Groups</a>.</p>
-        <h3 id="ReqsAllGroups">6.1 Requirements for All Working and Interest Groups</h3>
+        <h3 id="ReqsAllGroups">5.1 Requirements for All Working and Interest Groups</h3>
         <p>Each group <em class="rfc2119">must</em> have a charter. Requirements for the charter depend on the group type. All group
           charters <em class="rfc2119">must</em> be public (even if other proceedings of the group are <a href="#Member-only">Member-only</a>).
           Existing charters that are not yet public <em class="rfc2119">must</em> be made public when next revised or extended (with
@@ -955,10 +950,10 @@
           document the process it uses to create task forces (e.g., each task force might have an informal "charter"). Task forces do not
           publish <a href="#Reports">technical reports</a>; the Working Group <em class="rfc2119">may</em> choose to publish their results
           as part of a technical report.</p>
-        <h3>6.2 <dfn id="GroupsWG">Working Groups</dfn> and <dfn id="GroupsIG">Interest Groups</dfn></h3>
+        <h3>5.2 <dfn id="GroupsWG">Working Groups</dfn> and <dfn id="GroupsIG">Interest Groups</dfn></h3>
         <p>Although Working Groups and Interest Groups have different purposes, they share some characteristics, and so are defined together
           in the following sections.</p>
-        <h4>6.2.1 <dfn id="group-participation">Working Group and Interest Group Participation Requirements</dfn></h4>
+        <h4>5.2.1 <dfn id="group-participation">Working Group and Interest Group Participation Requirements</dfn></h4>
         <p>There are three types of individual <dfn id="wgparticipant">participants in a Working Group</dfn>: <a href="#member-rep">Member
             representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>, and <a href="#Team">Team representatives</a> (including
           the <a href="#TeamContact">Team Contact</a>).</p>
@@ -984,7 +979,7 @@
         <p>See also the licensing obligations on Working Group participants in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
             3</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
           and the patent claim exclusion process of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section 4</a>.</p>
-        <h5>6.2.1.1 <dfn id="member-rep-wg">Member Representative</dfn> in a Working Group</h5>
+        <h5>5.2.1.1 <dfn id="member-rep-wg">Member Representative</dfn> in a Working Group</h5>
         <p>An individual is a Member representative in a Working Group if all of the following conditions are satisfied:</p>
         <ul>
           <li>the Advisory Committee representative of the Member in question has designated the individual as a Working Group participant,
@@ -1009,7 +1004,7 @@
           <li>the Member <a href="#resignation">resigns</a> from the Working Group; this is done through the Member's Advisory Committee
             representative.</li>
         </ul>
-        <h5>6.2.1.2 <dfn id="member-rep-ig">Member Representative</dfn> in an Interest Group</h5>
+        <h5>5.2.1.2 <dfn id="member-rep-ig">Member Representative</dfn> in an Interest Group</h5>
         <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>, an individual
           is a Member representative in an Interest Group if all of the following conditions are satisfied:</p>
         <ul>
@@ -1020,7 +1015,7 @@
         <p>To designate an individual as a Member representative in an Interest Group, the Advisory Committee representative <em class="rfc2119">must</em>
           follow the instructions in the <a href="#cfp">Call for Participation</a> and charter.</p>
         <p>Member participation in an Interest Group ceases under the same conditions as for a Working Group.</p>
-        <h5>6.2.1.3 <dfn id="invited-expert-wg">Invited Expert in a Working Group</dfn></h5>
+        <h5>5.2.1.3 <dfn id="invited-expert-wg">Invited Expert in a Working Group</dfn></h5>
         <p>The Chair <em class="rfc2119">may</em> invite an individual with a particular expertise to participate in a Working Group. This
           individual <em class="rfc2119">may</em> represent an organization in the group (e.g., if acting as a liaison with another
           organization).</p>
@@ -1061,11 +1056,11 @@
           <li>the Chair or Director withdraws the invitation to participate, or</li>
           <li>the individual <a href="#resignation">resigns</a>.</li>
         </ul>
-        <h5>6.2.1.4 <dfn id="invited-expert-ig">Invited Expert in an Interest Group</dfn></h5>
+        <h5>5.2.1.4 <dfn id="invited-expert-ig">Invited Expert in an Interest Group</dfn></h5>
         <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>, the
           participation requirements for an Invited Expert in an Interest Group are the same as those for an <a href="#invited-expert-wg">Invited
             Expert in a Working Group</a>.</p>
-        <h5>6.2.1.5 <dfn id="team-rep-wg">Team Representative in a Working Group</dfn></h5>
+        <h5>5.2.1.5 <dfn id="team-rep-wg">Team Representative in a Working Group</dfn></h5>
         <p>An individual is a Team representative in a Working Group when so designated by W3C management.</p>
         <p>A Team representative participates in a Working Group from the moment the individual joins the group until any of the following
           occurs:</p>
@@ -1074,23 +1069,23 @@
           <li>W3C management changes Team representation by sending email to the Chair, cc'ing the group mailing list.</li>
         </ul>
         <p>The Team participates in a Working Group from the moment the Director announces the creation of the group until the group closes.</p>
-        <h5>6.2.1.6 <dfn id="team-rep-ig">Team Representative in an Interest Group</dfn></h5>
+        <h5>5.2.1.6 <dfn id="team-rep-ig">Team Representative in an Interest Group</dfn></h5>
         <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>, an individual
           is a Team representative in an Interest Group when so designated by W3C management.</p>
-        <h4>6.2.2 <dfn id="WGCharterDevelopment">Working Group and Interest Group Charter Development</dfn></h4>
+        <h4>5.2.2 <dfn id="WGCharterDevelopment">Working Group and Interest Group Charter Development</dfn></h4>
         <p>W3C creates a charter based on interest from the Members and Team. The Team <em class="rfc2119">must</em> notify the Advisory
           Committee when a charter for a new Working Group or Interest Group is in development. This is intended to raise awareness, even if
           no formal proposal is yet available. Advisory Committee representatives <em class="rfc2119">may</em> provide feedback on the <a
             href="#ACCommunication">Advisory Committee discussion list</a>.</p>
         <p>W3C <em class="rfc2119">may</em> begin work on a Working Group or Interest Group charter at any time.</p>
-        <h4>6.2.3 <dfn id="CharterReview">Advisory Committee Review of a Working Group or Interest Group Charter</dfn></h4>
+        <h4>5.2.3 <dfn id="CharterReview">Advisory Committee Review of a Working Group or Interest Group Charter</dfn></h4>
         <p>The Director <em class="rfc2119">must</em> solicit <a href="#ReviewAppeal">Advisory Committee review</a> of every new or
           substantively modified Working Group or Interest Group charter. The Director is <em class="rfc2119">not required</em> to solicit
           Advisory Committee review prior to a charter extension or for minor changes. The review period <em class="rfc2119">must</em> be
           at least four weeks.</p>
         <p>The Director's Call for Review of a substantively modified charter <em class="rfc2119">must</em> highlight important changes
           (e.g., regarding deliverables or resource allocation) and include rationale for the changes.</p>
-        <h4>6.2.4 <dfn id="cfp">Call for Participation in a Working Group or Interest Group</dfn></h4>
+        <h4>5.2.4 <dfn id="cfp">Call for Participation in a Working Group or Interest Group</dfn></h4>
         <p>After Advisory Committee review of a Working Group or Interest Group charter, the Director <em class="rfc2119">may</em> issue a
           Call for Participation to the Advisory Committee. Charters <em class="rfc2119">may</em> be amended based on review comments
           before the Director issues a Call for Participation. </p>
@@ -1101,7 +1096,7 @@
             Experts</a> <em class="rfc2119">must</em> be designated (or re-designated).</p>
         <p>Advisory Committee representatives <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> creation or substantive
           modification of a Working Group or Interest Group charter.</p>
-        <h4>6.2.5 <dfn id="charter-extension">Working Group and Interest Group Charter Extension</dfn></h4>
+        <h4>5.2.5 <dfn id="charter-extension">Working Group and Interest Group Charter Extension</dfn></h4>
         <p>To extend a Working Group or Interest Group charter with no other substantive modifications, the Director announces the extension
           to the Advisory Committee. The announcement <em class="rfc2119">must</em> indicate the new duration. The announcement <em class="rfc2119">must</em>
           also include rationale for the extension, a reference to the <a href="#WGCharter">charter</a>, the name(s) of the group's <a href="#GeneralChairs">Chair(s)</a>,
@@ -1110,7 +1105,7 @@
           re-designate <a href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited Experts</a>.</p>
         <p>Advisory Committee representatives <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> the extension of a Working Group
           or Interest Group charter.</p>
-        <h4>6.2.6 <dfn id="WGCharter">Working Group and Interest Group Charters</dfn></h4>
+        <h4>5.2.6 <dfn id="WGCharter">Working Group and Interest Group Charters</dfn></h4>
         <p>A Working Group or Interest Group charter <em class="rfc2119">must</em> include all of the following information.</p>
         <ul>
           <li>The group's mission (e.g., develop a technology or process, review the work of other groups);</li>
@@ -1149,7 +1144,7 @@
         <p>A charter <em class="rfc2119">may</em> include provisions other than those required by this document. The charter <em class="rfc2119">should</em>
           highlight whether additional provisions impose constraints beyond those of the W3C Process Document (e.g., limits on the number of
           individuals in a Working Group who represent the same Member organization or group of <a href="#MemberRelated">related Members</a>).</p>
-        <h4>6.2.8 <dfn id="GeneralTermination">Working Group and Interest Group Closure</dfn></h4>
+        <h4>5.2.8 <dfn id="GeneralTermination">Working Group and Interest Group Closure</dfn></h4>
         <p>A Working Group or Interest Group charter specifies a duration for the group. The Director, subject to <a href="#ACAppeal">appeal</a>
           by Advisory Committee representatives, <em class="rfc2119">may</em> close a group prior to the date specified in the charter in
           any of the following circumstances:</p>
@@ -1162,7 +1157,7 @@
         <p>Closing a Working Group has implications with respect to the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
             Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
       </section>
-      <h2 id="Reports">7 W3C Technical Report Development Process</h2>
+      <h2 id="Reports">6 W3C Technical Report Development Process</h2>
       <p>The W3C technical report development process is the set of steps and requirements followed by W3C <a href="#GroupsWG">Working
           Groups</a> to standardize Web technology. The W3C technical report development process is designed to </p>
       <ul>
@@ -1177,7 +1172,7 @@
       <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="#ref-patentpolicy">PUB33</a>].
       </p>
-      <h3 id="rec-advance">7.1 W3C Technical Reports</h3>
+      <h3 id="rec-advance">6.1 W3C Technical Reports</h3>
       <p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a W3C Technical
         Report on its <a href="http://www.w3.org/TR/">Technical Reports page http://www.w3.org/TR</a>.</p>
       <p>This chapter describes the formal requirements for publishing and maintaining a W3C Recommendation or Note.</p>
@@ -1195,7 +1190,7 @@
         recommendation of W3C but are simply documents preserved for historical reference.</p>
       <p>Individual Working Groups and Interest Groups may adopt additional processes for developing publications, so long as they do not
         conflict with the requirements in this chapter.</p>
-      <h4 id="recs-and-notes">7.1.1 Recommendations and Notes</h4>
+      <h4 id="recs-and-notes">6.1.1 Recommendations and Notes</h4>
       <p>W3C follows these steps when advancing a technical report to Recommendation.</p>
       <ol>
         <li>Publication of the <a href="#first-wd">First Public Working Draft</a>,</li>
@@ -1251,7 +1246,7 @@
           level</a>. The Director <em class="rfc2119">must</em> inform the <a href="#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 the specification is returned to a
         Working Group for further work.</p>
-      <h4 id="maturity-levels">7.1.2 Maturity Levels</h4>
+      <h4 id="maturity-levels">6.1.2 Maturity Levels</h4>
       <dl>
         <dt id="RecsWD">Working Draft (WD)</dt>
         <dd>A Working Draft is a document that W3C has published for review by the community, including W3C Members, the public, and other
@@ -1296,10 +1291,10 @@
       <p>Working Groups and Interest Groups <em class="rfc2119">may</em> make available "Editor's drafts". Editor's drafts have no official
         standing whatsoever, and do not necessarily imply consensus of a Working Group or Interest Group, nor are their contents endorsed in
         any way by W3C.</p>
-      <h3 id="requirements-and-definitions">7.2 General requirements and definitions</h3>
+      <h3 id="requirements-and-definitions">6.2 General requirements and definitions</h3>
       <p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a W3C Technical
         Report on its <a href="http://www.w3.org/TR/">Technical Reports page http://www.w3.org/TR</a> [<a href="#rdf-doc-list">PUB11</a>].</p>
-      <h4 id="general-requirements">7.2.1 General requirements for Technical Reports</h4>
+      <h4 id="general-requirements">6.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="#ref-doc-list">PUB11</a>] is available
         at the W3C Web site. W3C strives to make archival documents indefinitely available at their original address in their original form.</p>
@@ -1325,7 +1320,7 @@
         <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="#ref-translations">PUB18</a>] is available at the W3C Web site.</p>
-      <h4 id="transition-reqs">7.2.2 Advancement on the Recommendation Track</h4>
+      <h4 id="transition-reqs">6.2.2 Advancement on the Recommendation Track</h4>
       <p>For <em>all</em> requests to advance a specification to a new maturity level other than Note the Working Group:</p>
       <ul>
         <li><em class="rfc2119">must</em> record the group's decision to request advancement.</li>
@@ -1344,14 +1339,14 @@
       <p>For a First Public Working Draft there is no "previous maturity level", so many requirements do not apply, and approval is normally
         fairly automatic. For later stages, especially transition to Candidate or Proposed Recommendation, there is generally a formal
         review meeting to ensure the requirements have been met before Director's approval is given.</p>
-      <h4 id="doc-reviews">7.2.3 Reviews and Review Responsibilities</h4>
+      <h4 id="doc-reviews">6.2.3 Reviews and Review Responsibilities</h4>
       <p>A document is available for review from the moment it is first published. Working Groups <em class="rfc2119">should</em> <a href="#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.
-      <h5 id="wide-review">7.2.3.1 Wide Review</h5>
+      <h5 id="wide-review">6.2.3.1 Wide Review</h5>
       <p>The requirements for wide review are not precisely defined by the W3C Process. The objective is to ensure that the entire set of
         stakeholders of the Web community, including the general public, have had adequate notice of the progress of the Working Group (for
         example through notices posted to <a href="mailto:[email protected].org">[email protected]</a>) and were able
@@ -1371,7 +1366,7 @@
       <p>A Working Group could present evidence that wide review has been received, irrespective of solicitation. But it is important to
         note that 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.4 Implementation Experience</h4>
+      <h4 id="implementation-experience">6.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 specification will be realized. While no exhaustive
         list of requirements is provided here, when assessing that there is <dfn>adequate implementation experience</dfn> the Director will
@@ -1387,7 +1382,7 @@
       <p>Planning and accomplishing a demonstration of (interoperable) implementations can be very time consuming. Groups are often able to
         work 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>
-      <h4 id="correction-classes">7.2.5 Classes of Changes</h4>
+      <h4 id="correction-classes">6.2.5 Classes of Changes</h4>
       <p>This document distinguishes the following 4 classes of changes to a specification. The first two classes of change are considered <dfn
           id="editorial-change">editorial changes</dfn>, the latter two <dfn id="substantive-change">substantive changes</dfn>.</p>
       <dl>
@@ -1414,7 +1409,7 @@
         <dt>4. New features</dt>
         <dd>Changes that add a new functionality, element, etc.</dd>
       </dl>
-      <h3 id="working-draft">7.3 Working Draft</h3>
+      <h3 id="working-draft">6.3 Working Draft</h3>
       <p>A Public Working Draft is published on the <a href="http://www.w3.org/TR/">W3C's Technical Reports page</a> [<a href="#rdf-doc-list">PUB11</a>]
         for review, and for simple historical reference. For all Public Working Drafts a Working Group</p>
       <ul>
@@ -1423,14 +1418,14 @@
         <li> <em class="rfc2119">may</em> request publication of a Working Draft even if its content is considered unstable and does not
           meet all Working Group requirements.</li>
       </ul>
-      <h4 id="first-wd">7.3.1 First Public Working Draft</h4>
+      <h4 id="first-wd">6.3.1 First Public Working Draft</h4>
       <p>To publish the First Public Working Draft of a document, a Working Group <em class="rfc2119">must</em> meet the applicable <a href="#transition-reqs">general
           requirements for advancement</a>.</p>
       <p>The Director <em class="rfc2119">must</em> announce the publication of a First Public Working Draft publication to other W3C
         groups and to the public. </p>
       <p>Publishing the First Public Working Draft triggers a Call for Exclusions, 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="#ref-patentpolicy">PUB33</a>].</p>
-      <h4 id="revised-wd">7.3.2 Revising Public Working Drafts</h4>
+      <h4 id="revised-wd">6.3.2 Revising 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 previous published document that would benefit from review beyond the Working Group. </p>
       <p>If 6 months elapse without significant changes to a specification a Working Group <em class="rfc2119">should</em> publish a
@@ -1453,14 +1448,14 @@
         <li><a href="#last-call">Candidate recommendation</a>.</li>
         <li><a href="#Note">Working Group Note</a></li>
       </ul>
-      <h4 id="tr-end">7.3.3 Stopping Work on a specification</h4>
+      <h4 id="tr-end">6.3.3 Stopping Work on a specification</h4>
       <p>Work on a technical report <em class="rfc2119">may</em> cease at any time. Work <em class="rfc2119 new">should</em> cease if W3C
         or a Working Group determines that it cannot productively carry the work any further. If the Director <a href="#GeneralTermination">closes
           a Working Group</a> W3C <em class="rfc2119">must </em> publish any unfinished specifications on the Recommendation track as <a
           href="#Note">Working Group Notes</a>. If a Working group decides, or the Director requires, the Working Group to discontinue work
         on a technical report before completion, the Working Group <em class="rfc2119">should</em> publish the document as a <a href="#Note">Working
           Group Note</a>. </p>
-      <h3 id="candidate-rec"><a id="last-call">7.4 Candidate Recommendation </a></h3>
+      <h3 id="candidate-rec"><a id="last-call">6.4 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>
@@ -1492,7 +1487,7 @@
       <p>If there was any <a href="#def-Dissent" rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
         to the Working Group decision to request advancement <a href="#AC">Advisory Committee</a> representatives <em class="rfc2119">may</em>
         <a href="#ACAppeal">appeal</a> the decision to advance the technical report.</p>
-      <h4 id="revised-cr">7.4.1 Revising a Candidate Recommendation</h4>
+      <h4 id="revised-cr">6.4.1 Revising a Candidate Recommendation</h4>
       <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> obtain the Director's approval to
         publish a revision of a Candidate Recommendation. This is because substantive changes will generally require a new Exclusion
@@ -1512,7 +1507,7 @@
       </ul>
       <p>The Director <em class="rfc2119">must</em> announce the publication of a revised Candidate Recommendation to other W3C groups and
         the Public.</p>
-      <h3 id="rec-pr">7.5 Proposed Recommendation</h3>
+      <h3 id="rec-pr">6.5 Proposed Recommendation</h3>
       <p>In addition to meeting the <a href="#transition-reqs">general requirements for advancement</a>,</p>
       <ul>
         <li>The status information <em class="rfc2119">must</em> specify the deadline for Advisory Committee review, which <em class="rfc2119">must</em>
@@ -1550,7 +1545,7 @@
         <li><a href="#rec-publication">Recommendation status</a> (The expected next step)</li>
         <li><a href="#Note">Working Group Note</a></li>
       </ul>
-      <h3 id="rec-publication">7.6 W3C Recommendation</h3>
+      <h3 id="rec-publication">6.6 W3C Recommendation</h3>
       <p>The decision to advance a document to Recommendation is a <a href="#def-w3c-decision">W3C Decision</a>.</p>
       <p>In addition to meeting the <a href="#transition-reqs">general requirements for advancement</a>,</p>
       <ul>
@@ -1571,7 +1566,7 @@
         <li><em class="rfc2119">may</em> be republished as an <a href="#rec-modify">(Edited) Recommendation</a>, or</li>
         <li><em class="rfc2119">may</em> be <a href="#rec-rescind">rescinded</a>.</li>
       </ul>
-      <h3 id="rec-modify">7.7 Modifying a W3C Recommendation</h3>
+      <h3 id="rec-modify">6.7 Modifying a W3C Recommendation</h3>
       <p>This section details the management of errors in, and the process for making changes to a Recommendation. Please see also the <a href="http://www.w3.org/2003/01/republishing/">Requirements
           for modification of W3C Technical Reports</a> [<a href="#in-place-tr-mod">PUB35</a>].</p>
       <p>
@@ -1614,7 +1609,7 @@
             <path d="M443,58 v20"></path><polygon points="443,78 441,71 445,71"></polygon>
             <polygon points="443,78 486,103 443,128 400,103" fill="none"></polygon>
             <text x="445" y="68" font-size="10" stroke="none">Changes to text</text>
-            <text x="443" y="103" text-anchor="middle" font-size="10" stroke-width="0.2"><tspan>Substantive</tspan><tspan x="443" y="113" text-anchor="middle">changes?</tspan></text></g>
+            <text x="443" y="103" text-anchor="middle" font-size="10" stroke-width="0.2"><tspan>Substantive?</tspan><tspan x="443" y="113" text-anchor="middle">Dissent?</tspan></text></g>
           <g id="RecToPR">
             <text x="370" y="100" font-size="10" stroke="none">No</text>
             <path d="M400,103h-37v-45" stroke="black" fill="none"></path><polygon stroke="black" points="363,58 361,65 365,65"></polygon></g>
@@ -1633,7 +1628,7 @@
             <path d="M220,103h-160v-63h43" fill="none"></path>
             <text x="200" y="100" stroke-width="0.2" fill="black" font-size="10">Yes</text>
             <polygon points="103,38 108,40 103,42"></polygon> </g> </svg></p>
-      <h4 id="errata">7.7.1 Errata Management</h4>
+      <h4 id="errata">6.7.1 Errata Management</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 error that can be resolved by one or more changes in classes 1-3 of section <a href="#correction-classes">7.2.5
@@ -1646,7 +1641,7 @@
         errata page, possibly auto-generated from a database.</p>
       <p>An erratum is resolved by an informative, "proposed" correction generated by the Working Group. A correction becomes part of the
         Recommendation by the process for Revising a Recommendation described in the next section.</p>
-      <h4 id="revised-rec">7.7.2 Revising a Recommendation</h4>
+      <h4 id="revised-rec">6.7.2 Revising a Recommendation</h4>
       <p>A Working group <em class="rfc2119">may</em> request republication of a Recommendation, or W3C <em class="rfc2119">may</em>
         republish a Recommendation, to make corrections that do not result in any changes to the text of the specification.</p>
       <p><a href="#editorial-change">Editorial changes</a> to a Recommendation require no technical review of the proposed changes. A
@@ -1668,7 +1663,7 @@
       </ul>
       <p>For changes which introduces a new feature or features, W3C <em class="rfc2119">must</em> follow the full process of <a href="#rec-advance">advancing
           a technical report to Recommendation</a> beginning with a new First Public Working Draft.</p>
-      <h3 id="Note">7.8 Publishing a Working Group or Interest Group Note</h3>
+      <h3 id="Note">6.8 Publishing a Working Group or Interest Group Note</h3>
       <p>Working Groups and Interest Groups publish material that is not a formal specification as Notes. This includes supporting
         documentation for a specification such as explanations of design principles or use cases and requirements, non-normative guides to
         good practices, as well as specifications where work has been stopped and there is no longer consensus for making them a new
@@ -1688,7 +1683,7 @@
       </ul>
       <p>The <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>] does not
         specify any licensing requirements or commitments for Working Group Notes.</p>
-      <h3 id="rec-rescind">7.9 Rescinding a W3C Recommendation</h3>
+      <h3 id="rec-rescind">6.9 Rescinding a W3C Recommendation</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 implementers and cannot be resolved; see the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
           Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>] and in particular <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section
@@ -1734,14 +1729,14 @@
       <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 announcements of the various steps, and <a href="http://www.w3.org/2002/05/rec-tips">tips
           on getting to Recommendation faster</a> [<a href="#ref-rec-tips">PUB27</a>].</p>
-      <h2 id="ReviewAppeal">8 Advisory Committee Reviews, Appeals, and Votes</h2>
+      <h2 id="ReviewAppeal">7 Advisory Committee Reviews, Appeals, and Votes</h2>
       <p>This section describes how the Advisory Committee reviews proposals from the Director and how Advisory Committee representatives
         appeal W3C decisions and decisions by the Director. A <dfn id="def-w3c-decision">W3C decision</dfn> is one where the Director (or
         the Director's delegate) has exercised the role of assessing consensus after an <a href="#ACReview">Advisory Committee review</a>
         of an <a href="#CharterReview">Charter Proposal</a>, after a <a href="#cfr">Call for Review of a Proposed Recommendation</a>,
         after a <a href="#cfr-edited">Call for Review of a Proposed Recommendation</a>, after a <a href="#proposed-rescinded-rec">Proposal
           to Rescind a W3C Recommendation</a>, and after a <a href="#GAProcess">Proposed Process Document</a> review.</p>
-      <h3 id="ACReview">8.1 Advisory Committee Reviews</h3>
+      <h3 id="ACReview">7.1 Advisory Committee Reviews</h3>
       <p>The Advisory Committee reviews:</p>
       <ul>
         <li><a href="#CharterReview">new and modified Working and Interest Groups</a>,</li>
@@ -1749,7 +1744,7 @@
             to Rescind a Recommendation</a>, and</li>
         <li><a href="#GAProcess">Proposed changes to the W3C process</a>.</li>
       </ul>
-      <h4 id="ACReviewStart">8.1.1 Start of a Review Period</h4>
+      <h4 id="ACReviewStart">7.1.1 Start of a Review Period</h4>
       <p>Each Advisory Committee review period begins with a Call for Review from the Team to the Advisory Committee. The <dfn id="reviewform">review
           form</dfn> describes the proposal, raises attention to deadlines, estimates when the decision will be available, and includes
         other practical information. Each Member organization <em class="rfc2119">may</em> send one review, which <em class="rfc2119">must</em>
@@ -1764,7 +1759,7 @@
         their reviews with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>.</p>
       <p>A Member organization <em class="rfc2119">may</em> modify its review during a review period (e.g., in light of comments from other
         Members).</p>
-      <h4 id="ACReviewAfter">8.1.2 After the Review Period</h4>
+      <h4 id="ACReviewAfter">7.1.2 After the Review Period</h4>
       <p>After the review period, the Director <em class="rfc2119">must</em> announce to the Advisory Committee the level of support for
         the proposal (<a href="#def-Consensus">consensus</a> or <a href="#def-Dissent">dissent</a>). The Director <em class="rfc2119">must</em>
         also indicate whether there were any Formal Objections, with attention to <a href="#confidentiality-change">changing
@@ -1784,7 +1779,7 @@
           weeks</span> after the end of a Proposed Recommendation review period. If, after <span class="time-interval">three weeks</span>,
         the Director has not announced the outcome, the Director <em class="rfc2119">should</em> provide the Advisory Committee with an
         update.</p>
-      <h3 id="ACAppeal">8.2 Appeal by Advisory Committee Representatives</h3>
+      <h3 id="ACAppeal">7.2 Appeal by Advisory Committee Representatives</h3>
       <p>Advisory Committee representatives <em class="rfc2119">may</em> appeal certain decisions, though appeals are only expected to
         occur in extraordinary circumstances.</p>
       <p>When Advisory Committee review immediately precedes a decision, Advisory Committee representatives <em class="rfc2119">may</em>
@@ -1811,12 +1806,12 @@
         Committee support the appeal request, the Team <em class="rfc2119">must</em> organize an appeal vote asking the Advisory Committee
         to approve or reject the decision.
         <!-- Voting procedure to be determined --></p>
-      <h3 id="ACVotes">8.3 Advisory Committee Votes</h3>
+      <h3 id="ACVotes">7.3 Advisory Committee Votes</h3>
       <p>The Advisory Committee votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>, and in the event
         of a formal appeal of a <a href="#def-w3c-decision">W3C decision</a>. Whenever the Advisory Committee votes, each Member or group
         of <a href="#MemberRelated">related Members</a> has one vote. In the case of <a href="#AB-TAG-elections">Advisory Board and TAG
           elections</a>, "one vote" means "one vote per available seat".</p>
-      <h2 id="GAEvents">9 Workshops and Symposia</h2>
+      <h2 id="GAEvents">8 Workshops and Symposia</h2>
       <p>The Team organizes <dfn id="EventsW">Workshops</dfn> and <dfn id="EventsS">Symposia</dfn> to promote early involvement in the
         development of W3C activities from Members and the public.</p>
       <p>The goal of a Workshop is usually either to convene experts and other interested parties for an exchange of ideas about a
@@ -1835,7 +1830,7 @@
       <p><strong>Note:</strong> In general, W3C does not organize <dfn id="EventsC">conferences</dfn>. Currently, W3C presents its work to
         the public at the annual World Wide Web Conference, which is coordinated by the <a href="http://www.iw3c2.org/">International World
           Wide Web Conference Committee</a> (<abbr>IW3C2</abbr>).</p>
-      <h2 id="Liaisons">10 Liaisons</h2>
+      <h2 id="Liaisons">9 Liaisons</h2>
       <p>W3C uses the term "liaison" to refer to coordination of activities with a variety of organizations, through a number of mechanisms
         ranging from very informal (e.g., an individual from another organization participates in a W3C Working Group, or just follows its
         work) to mutual membership, to even more formal agreements. Liaisons are not meant to substitute for W3C membership.</p>
@@ -1847,7 +1842,7 @@
         Once approved, a Memorandum of Understanding <em class="rfc2119">should</em> be made public.</p>
       <p>Information about <a href="http://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a> and the guidelines W3C
         follows when creating a liaison [<a href="#ref-liaison-list">PUB28</a>] is available on the Web.</p>
-      <h2 id="Submission">11 Member Submission Process</h2>
+      <h2 id="Submission">10 Member Submission Process</h2>
       <p>The Member Submission process allows Members to propose technology or other ideas for consideration by the Team. After review, the
         Team <em class="rfc2119">may</em> publish the material at the W3C Web site. The formal process affords Members a record of their
         contribution and gives them a mechanism for disclosing the details of the transaction with the Team (including IPR claims). The Team
@@ -1889,7 +1884,7 @@
         progress" of the W3C.</p>
       <p>The list of <a href="http://www.w3.org/Submission/">acknowledged Member Submissions</a> [<a href="#ref-submission-list">PUB10</a>]
         is available at the W3C Web site.</p>
-      <h3 id="SubmissionRights">11.1 Submitter Rights and Obligations</h3>
+      <h3 id="SubmissionRights">10.1 Submitter Rights and Obligations</h3>
       <p>When more than one Member jointly participates in a Submission request, only one Member formally sends in the request. That Member
         <em class="rfc2119">must</em> copy each of the Advisory Committee representatives of the other participating Members, and each of
         those Advisory Committee representatives <em class="rfc2119">must</em> confirm (by email to the Team) their participation in the
@@ -1905,7 +1900,7 @@
         documents in the Member Submission prior to acknowledgment (without reference to the Submission request).</p>
       <p>After acknowledgment, the Submitter(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>, imply W3C
         investment in the Member Submission until, and unless, the material has been adopted as a deliverable of a W3C Working Group</p>
-      <h4 id="SubmissionScope">11.1.1 Scope of Member Submissions</h4>
+      <h4 id="SubmissionScope">10.1.1 Scope of Member Submissions</h4>
       <p>When a technology overlaps in scope with the work of a chartered Working Group, Members <em class="rfc2119">should</em> <a href="#group-participation">participate
           in the Working Group</a> and contribute the technology to the group's process rather than seek publication through the Member
         Submission process. The Working Group <em class="rfc2119">may</em> incorporate the contributed technology into its deliverables. If
@@ -1915,7 +1910,7 @@
         Submission process to build consensus around concrete proposals for new work.</p>
       <p>Members <em class="rfc2119">should not</em> submit materials covering topics well outside the scope of <a href="http://www.w3.org/Consortium/mission">W3C's
           mission</a> [<a href="#ref-mission">PUB15</a>].</p>
-      <h4 id="SubmissionReqs">11.1.2 Information Required in a Submission Request</h4>
+      <h4 id="SubmissionReqs">10.1.2 Information Required in a Submission Request</h4>
       <p>The Submitter(s) and any other authors of the submitted material <em class="rfc2119">must</em> agree that, if the request is
         acknowledged, the documents in the Member Submission will be subject to the <a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C
           Document License</a> [<a href="#ref-doc-license">PUB18</a>] and will include a reference to it. The Submitter(s) <em class="rfc2119">may</em>
@@ -1946,7 +1941,7 @@
       </ul>
       <p>For other administrative requirements related to Submission requests, see "<a href="http://www.w3.org/2000/09/submission">How to
           send a Submission request</a>" [<a href="#ref-member-sub">MEM8</a>].</p>
-      <h3 id="TeamSubmissionRights">11.2 Team Rights and Obligations</h3>
+      <h3 id="TeamSubmissionRights">10.2 Team Rights and Obligations</h3>
       <p>Although they are not technical reports, the documents in a Member Submission <em class="rfc2119">must</em> fulfill the
         requirements established by the Team, including the Team's <a href="http://www.w3.org/Guide/pubrules">Publication Rules</a>.</p>
       <p>The Team sends a <a id="validation-notice">validation notice</a> to the Submitter(s) once the Team has reviewed a Submission
@@ -1954,7 +1949,7 @@
       <p>Prior to a decision to <a href="#SubmissionYes">acknowledge</a> or <a href="#SubmissionNo">reject</a> the request, the request is
         <a href="#Team-only">Team-only</a>, and the Team <em class="rfc2119">must</em> hold it in the strictest confidentiality. In
         particular, the Team <em class="rfc2119">must not</em> comment to the media about the Submission request.</p>
-      <h3 id="SubmissionYes">11.3 Acknowledgment of a Submission Request</h3>
+      <h3 id="SubmissionYes">10.3 Acknowledgment of a Submission Request</h3>
       <p>The Director <a href="#SubmissionYes">acknowledges</a> a Submission request by sending an announcement to the Advisory Committee.
         Though the announcement <em class="rfc2119">may</em> be made at any time, the Submitter(s) can expect an announcement between <span
           class="time-interval">four to six weeks</span> after the <a href="#validation-notice">validation notice</a>. The Team <em class="rfc2119">must</em>
@@ -1966,7 +1961,7 @@
       </ul>
       <p>If the Submitter(s) wishes to modify a document published as the result of acknowledgment, the Submitter(s) <em class="rfc2119">must</em>
         start the Submission process from the beginning, even just to correct editorial changes.</p>
-      <h3 id="SubmissionNo">11.4 Rejection of a Submission Request</h3>
+      <h3 id="SubmissionNo">10.4 Rejection of a Submission Request</h3>
       <p>The Director <em class="rfc2119">may</em> reject a Submission request for a variety of reasons, including any of the following:</p>
       <ul>
         <li>The ideas expressed in the request overlap in scope with the work of a chartered Working Group, and acknowledgment might
@@ -1987,7 +1982,7 @@
         reasons. In this case the Team <em class="rfc2119">should</em> make available its rationale for the rejection to the appropriate
         body. The Team will establish a process for such appeals that ensures the appropriate <a href="#confidentiality-levels">level of
           confidentiality</a>.</p>
-      <h2 id="GAProcess">12 Process Evolution</h2>
+      <h2 id="GAProcess">11 Process Evolution</h2>
       <p>The <span id="ProcessDoc">W3C Process Document</span> undergoes similar consensus-building processes as technical reports, with
         the <a href="#AB">Advisory Board</a> acting as the sponsoring Working Group.</p>
       <p>The Advisory Board initiates review of a Process Document as follows:</p>
@@ -2003,8 +1998,8 @@
       <p>W3C <em class="rfc2119">may</em> also modify a Process Document by following the processes for <a href="#rec-modify">modifying a
           Recommendation</a>.</p>
       <p>Reviews of the Process Document are not public reviews.</p>
-      <h2 id="references">13 References</h2>
-      <h3 id="public-refs">13.1 Public Resources</h3>
+      <h2 id="references">12 References</h2>
+      <h3 id="public-refs">12.1 Public Resources</h3>
       <p>The following public information is available at the <a href="http://www.w3.org/">W3C Web site</a>.</p>
       <dl>
         <dt id="ref-join-w3c">[PUB5]</dt>
@@ -2061,7 +2056,7 @@
         <dt id="in-place-tr-mod">[PUB35]</dt>
         <dd><cite><a href="http://www.w3.org/2003/01/republishing/">In-place modification of W3C Technical Reports</a></cite></dd>
       </dl>
-      <h3>13.2 <a id="member-refs">Member-only Resources</a></h3>
+      <h3>12.2 <a id="member-refs">Member-only Resources</a></h3>
       <p>The following <a href="#Member-only">Member-only</a> information is available at the <a href="http://www.w3.org/">W3C Web site</a>.</p>
       <dl>
         <dt id="rdf-current-ac">[MEM1]</dt>
@@ -2087,7 +2082,7 @@
         <dt id="rdf-election-howto">[MEM15]</dt>
         <dd><cite><a href="http://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a></cite></dd>
       </dl>
-      <h3 id="other-refs">13.3 Other References</h3>
+      <h3 id="other-refs">12.3 Other References</h3>
       <dl>
         <dt id="rdf-RFC2119">[RFC2119]</dt>
         <dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">"Key words for use in RFCs to Indicate Requirement Levels"</a></cite>, S.
@@ -2096,14 +2091,14 @@
         <dd><cite><a href="http://www.ietf.org/rfc/rfc2777.txt">"Publicly Verifiable Nomcom Random Selection"</a></cite>, D. Eastlake 3rd,
           February 2000.</dd>
       </dl>
-      <h2 id="acks">14 Acknowledgments</h2>
+      <h2 id="acks">13 Acknowledgments</h2>
       <p>The following individuals have contributed to this proposal for a revised Process: Daniel Appelquist (Telefonica), Art Barstow
-        (Nokia), Robin Berjon (W3C), Judy Brewer (W3C), Marcos Cáceres (Mozilla), Wayne Carr (Intel), Michael Champion (W3C), Mark Crawford
-        (SAP), Karl Dubost (Mozilla), Fantasai (unaffiliated), Virginie Galindo (Gemalto), Daniel Glazman (Disruptive Innovations), Eduardo
-        Gutentag (unaffiiliated), Brad Hill (Facebook), Jeff Jaffe (W3C), Cullen Jennings (Cisco), Brain Kardell (JQuery), Peter Linss (HP),
-        Nigel Megitt (BBC), Olle Olsson (SICS), Natasha Rooney (GSMA), Sam Ruby (IBM), David Singer (Apple), Henri Sivonen (Mozilla), Josh
-        Soref (BlackBerry), Anne van Kesteren (Mozilla), Léonie Watson (The Paciello Group), Mike West (Google), Chris Wilson (Google),
-        Steve Zilles (Adobe).</p>
+        (Nokia, unaffiliated), Robin Berjon (W3C), Judy Brewer (W3C), Marcos Cáceres (Mozilla), Wayne Carr (Intel), Michael Champion (W3C),
+        Mark Crawford (SAP), Karl Dubost (Mozilla), Fantasai (unaffiliated), Virginie Galindo (Gemalto), Daniel Glazman (Disruptive
+        Innovations), Eduardo Gutentag (unaffiiliated), Brad Hill (Facebook), Jeff Jaffe (W3C), Cullen Jennings (Cisco), Brain Kardell
+        (JQuery), Peter Linss (HP), Nigel Megitt (BBC), Olle Olsson (SICS), Natasha Rooney (GSMA), Sam Ruby (IBM), David Singer (Apple),
+        Henri Sivonen (Mozilla), Josh Soref (BlackBerry), Anne van Kesteren (Mozilla), Léonie Watson (The Paciello Group), Mike West
+        (Google), Chris Wilson (Google), Steve Zilles (Adobe).</p>
       <p>The following individuals contributed to the development of earlier versions of the Process: Jean-François Abramatic (IBM, and
         previously ILOG and W3C), Dan Appelquist (Telefonica), Art Barstow (Nokia), Ann Bassetti (The Boeing Company), Jim Bell (HP), Robin
         Berjon (W3C), Tim Berners-Lee (W3C), Klaus Birkenbihl (Fraunhofer Gesellschaft), Don Brutzman (Web3D), Carl Cargill (Netscape, Sun
@@ -2116,17 +2111,21 @@
         (Qualcomm), Larry Masinter (Adobe Systems), Qiuling Pan (Huawei), TV Raman (Google), Thomas Reardon (Microsoft), Claus von Riegen
         (SAP AG), David Singer (Apple), David Singer (IBM), Ralph Swick (W3C), Anne van Kesteren, Jean-Charles Verdié (MStar), Chris Wilson
         (Google), Lauren Wood (unaffiliated), and Steve Zilles (Adobe Systems).</p>
-      <h2 id="changes">15 Changes</h2>
+      <h2 id="changes">14 Changes</h2>
       <p>This document is based on 1 August 2014 Process. <a href="https://dvcs.w3.org/hg/AB/">Detailed change logs</a> are available.</p>
       <p>The notable changes include:</p>
-      <h3>Current Editor's draft</h3>
+      <h3>Current draft</h3>
+      <ul>
+        <li>A working group can propose non-substantive editorial corrections directly as a Proposed Recommendation (<a href="http://www.w3.org/community/w3process/track/issues/152">ISSUE-152</a>)</li>
+        <li>Sections above 5 have been renumbered (reduced by one since chapter 5 was removed)</li>
+        <li>More explicit mention of W3C Horizontal Groups has been made in regards to wide review and dependencies</li>
+        <li>Various minimal editorial cleanups</li>
+      </ul>
+      <h3>3 March "AC last call" draft</h3>
       <ul>
         <li>The default channel for <a href="#ACReview">AC review</a> has been removed in favor of a requirement for each review to specify
           a default (<a href="http://www.w3.org/community/w3process/track/issues/154">ISSUE-154</a>)</li>
-        <li>A procedure for <a href="#resignation">resignation</a> from Working (and Interest Groups has been provided (<a href="http://www.w3.org/community/w3process/track/issues/151">ISSUE-151</a>)</li>
-      </ul>
-      <h3>Previous Editor's drafts</h3>
-      <ul>
+        <li>A procedure for <a href="#resignation">resignation</a> from Working and Interest Groups has been provided (<a href="http://www.w3.org/community/w3process/track/issues/151">ISSUE-151</a>)</li>
         <li>Editorial cleanups to <a href="#wide-review">7.2.3.1 Wide Review</a></li>
         <li>Editorial Changes to <a href="#errata">7.7.1 Errata Management</a> - <a href="https://www.w3.org/community/w3process/track/issues/141">ISSUE-141</a></li>
         <li>Remove <a id="GCGCreation" name="CGCreation"></a><a id="GroupsCG" name="GroupsCG"></a> <a id="CGParticipation" name="CGParticipation"></a><a