link the 30 sept review darft in the changes section
authorcharles
Thu, 29 Jan 2015 16:28:34 +0100
changeset 141 9879d992ac84
parent 140 8826b6bccaec
child 142 a2fae0c1cafd
link the 30 sept review darft in the changes section
cover.html
--- a/cover.html	Thu Jan 29 16:14:28 2015 +0100
+++ b/cover.html	Thu Jan 29 16:28:34 2015 +0100
@@ -3,8 +3,7 @@
   <head>
     <meta content="text/html; charset=utf-8" http-equiv="content-type">
     <meta name="keywords" content="W3C, World Wide Web, WWW, Consortium, process, Team, Recommendation, Advisory Committee,
-Advisory Board, Working Group, Coordination Group, Interest Group, W3C Activity, Workshop, Symposium, charter, Activity Proposal,
-Working Draft, Process Document, Candidate Recommendation, Director, Proposed Recommendation, Last Call, Submission request">
+Advisory Board, Working Group, Coordination Group, Interest Group, W3C Activity, Workshop, Symposium, charter, Activity Proposal,Working Draft, Process Document, Candidate Recommendation, Director, Proposed Recommendation, Last Call, Submission request">
     <link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/base.css">
     <title>World Wide Web Consortium Process Document</title>
     <style type="text/css">
@@ -32,15 +31,13 @@
         <dt>Previous editor:</dt>
         <dd>Ian Jacobs, <a href="http://www.w3.org/">W3C</a></dd>
       </dl>
-      <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1996-2015 
-        <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
+      <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1996-2015 <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
         (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr
             title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>,
         <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
         <a href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a rel="Copyright" href="/Consortium/Legal/copyright-documents">document
           use</a> and <a rel="Copyright" href="/Consortium/Legal/copyright-software">software licensing</a> rules apply. Your interactions
-        with this site are in accordance with our <a href="/Consortium/Legal/privacy-statement#Public">public</a> and 
-        <a href="/Consortium/Legal/privacy-statement#Members">Member</a>
+        with this site are in accordance with our <a href="/Consortium/Legal/privacy-statement#Public">public</a> and <a href="/Consortium/Legal/privacy-statement#Members">Member</a>
         privacy statements.</p>
       <hr></div>
     <h2 class="notoc"><a id="abstract">Abstract</a></h2>
@@ -53,26 +50,23 @@
     <h2 class="notoc" id="status">Status of this Document</h2>
     <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
+    <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 28 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>Note that sections have not been renumbered from the current Operative version. This is intended to facilitate comparison for review,
       but renumbering will occur before adoption of a New Process document.</p>
-    <p>In <em>this draft</em> line feed characters have been used in the source. A <a href="#changes">change history</a>
-      (compared to the 2014 Process Document) forms part of the draft.</p>
+    <p>In <em>this draft</em> line feed characters have been used in the source. A <a href="#changes">change history</a> (compared to the
+      2014 Process Document) forms part of the draft.</p>
     <p>The document will continue to be developed in preparation for adopting a revised process in 2015. A further revision is anticipated,
       to be adopted in 2016.</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
+    <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
         changelogs</a> are available online. </p>
     <h2 class="notoc" id="pp">Relation of Process Document to Patent Policy</h2>
-    <p>W3C Members' attention is called to the fact that provisions of the Process Document are binding on Members per the 
-      <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+    <p>W3C Members' attention is called to the fact that provisions of the Process Document are binding on Members per the <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
         Agreement</a> [<a href="#ref-member-agreement">PUB6</a>]. The Patent Policy <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
         Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>] is incorporated by normative reference as a part of the Process Document,
       and is thus equally binding.</p>
@@ -82,8 +76,7 @@
     <p>In the Process Document, the term "participant" refers to an individual, not an organization.</p>
     <h2 class=".notoc">Conformance and specialized terms</h2>
     <p>The terms <em class="rfc2119">must</em>, <em class="rfc2119">must not</em>, <em class="rfc2119">should</em>, <em class="rfc2119">should
-        not</em>, <em class="rfc2119">required</em>, and <em class="rfc2119">may</em> are used in accordance with 
-      <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC
+        not</em>, <em class="rfc2119">required</em>, and <em class="rfc2119">may</em> are used in accordance with <a href="http://www.ietf.org/rfc/rfc2119.txt">RFC
         2119</a> [<a href="#ref-RFC2119">RFC2119</a>]. The term <dfn><em class="rfc2119">not required</em></dfn> is equivalent to the term
       <em class="rfc2119">may</em> as defined in RFC 2119.&nbsp;</p>
     <p>Some terms have been capitalized in this document (and in other W3C materials) to indicate that they are entities with special
@@ -349,8 +342,7 @@
       </ol>
       <p id="MemberSubscription">W3C membership is open to all entities, as described in "<a href="http://www.w3.org/Consortium/join">How to
           Join W3C</a>" [<a href="#ref-join-w3c">PUB5</a>]; (refer to the public list of <a href="http://www.w3.org/Consortium/Member/List">current
-          W3C Members</a> [<a href="#ref-current-mem">PUB8</a>]). Organizations subscribe according to the 
-        <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+          W3C Members</a> [<a href="#ref-current-mem">PUB8</a>]). Organizations subscribe according to the <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
           Agreement</a> [<a href="#ref-member-agreement">PUB6</a>]. The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure that
         Member participation agreements remain <a href="#Team-only">Team-only</a> and that no Member receives preferential treatment within
         W3C.</p>
@@ -396,13 +388,11 @@
       </ol>
       <p>A <em>subsidiary</em> is an organization of which effective control and/or majority ownership rests with another, single
         organization.</p>
-      <p>Related Members <em class="rfc2119">must</em> disclose these relationships according to the mechanisms described in the
-        <a href="http://www.w3.org/Member/Intro">New
+      <p>Related Members <em class="rfc2119">must</em> disclose these relationships according to the mechanisms described in the <a href="http://www.w3.org/Member/Intro">New
           Member Orientation</a> [<a href="#ref-new-member">MEM4</a>].</p>
       <h4 id="AC">2.1.3 Advisory Committee (AC)</h4>
       <p>When an organization joins W3C (see "<a href="http://www.w3.org/Consortium/join">How to Join W3C</a>" [<a href="#ref-join-w3c">PUB5</a>]),
-        it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement. The
-        <a href="http://www.w3.org/Member/Intro">New
+        it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement. The <a href="http://www.w3.org/Member/Intro">New
           Member Orientation</a> explains how to subscribe or unsubscribe to Advisory Committee mailing lists, provides information about
         Advisory Committee meetings, explains how to name a new Advisory Committee representative, and more. Advisory Committee
         representatives <em class="rfc2119">must</em> follow the <a href="#coi">conflict of interest policy</a> by disclosing information
@@ -474,8 +464,7 @@
       <h4 id="TeamSubmission">2.2.1 Team Submissions</h4>
       <p>Team members <em class="rfc2119">may</em> request that the Director publish information at the W3C Web site. At the Director's
         discretion, these documents are published as "Team Submissions". These documents are analogous to <a href="#Submission">Member
-          Submissions</a> (e.g., in <a href="#SubmissionScope">expected scope</a>). However, there is no additional Team comment. The
-        <a href="#DocumentStatus">document
+          Submissions</a> (e.g., in <a href="#SubmissionScope">expected scope</a>). However, there is no additional Team comment. The <a href="#DocumentStatus">document
           status section</a> of a Team Submission indicates the level of Team consensus about the published material.</p>
       <p>Team Submissions are <strong>not</strong> part of the <a href="#Reports">technical report development process</a>.</p>
       <p>The list of <a href="http://www.w3.org/TeamSubmission/">published Team Submissions</a> [<a href="#ref-team-submission-list">PUB16</a>]
@@ -556,8 +545,7 @@
         seat is <a href="#AB-TAG-vacated">vacated</a>. Although Advisory Board and TAG participants do not advocate for the commercial
         interests of their employers, their participation does carry the responsibilities associated with Member representation, Invited
         Expert status, or Team representation (as described in the section on the <a href="#AB-TAG-elections">AB/TAG nomination and
-          election process</a>). See also the licensing obligations on TAG participants in
-        <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+          election process</a>). See also the licensing obligations on TAG 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 claim exclusion process of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section 4</a>.</p>
       <h4 id="AB-TAG-constraints">2.5.1 Advisory Board and Technical Architecture Group Participation Constraints</h4>
@@ -583,8 +571,7 @@
       <p>Each Member (or group of <a href="#MemberRelated">related Members</a>) <em class="rfc2119">may</em> nominate one individual. A
         nomination <em class="rfc2119">must</em> be made with the consent of the nominee. In order for an individual to be nominated as a
         Member representative, the individual <em class="rfc2119">must</em> qualify for <a href="#member-rep">Member representation</a>
-        and the Member's Advisory Committee representative <em class="rfc2119">must</em> include in the nomination the (same)
-        <a href="#member-rep-info">information
+        and the Member's Advisory Committee representative <em class="rfc2119">must</em> include in the nomination the (same) <a href="#member-rep-info">information
           required for a Member representative in a Working Group</a>. In order for an individual to be nominated as an Invited Expert, the
         individual <em class="rfc2119">must</em> provide the (same) <a href="#inv-expert-info">information required for an Invited Expert
           in a Working Group</a> and the nominating Advisory Committee representative <em class="rfc2119">must</em> include that
@@ -608,11 +595,9 @@
         receive 10 votes each for two seats), the <a href="#random">verifiable random selection procedure</a> described below will be used
         to fill the available seats.</p>
       <p id="short-term">The shortest term is assigned to the elected individual who received the fewest votes, the next shortest to the
-        elected individual who received the next fewest, and so on. In the case of a tie among those eligible for a short term, the
-        <a href="#random">verifiable
+        elected individual who received the next fewest, and so on. In the case of a tie among those eligible for a short term, the <a href="#random">verifiable
           random selection procedure</a> described below will be used to assign the short term.</p>
-      <p>Refer to <a href="http://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a>
-        [<a href="#ref-election-howto">MEM15</a>]
+      <p>Refer to <a href="http://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a> [<a href="#ref-election-howto">MEM15</a>]
         for more details.</p>
       <h5 id="random">2.5.2.1 Verifiable Random Selection Procedure</h5>
       <p>When it is necessary to use a verifiable random selection process (e.g., in an AB or TAG election, to "draw straws" in case of a
@@ -646,8 +631,7 @@
       </ul>
       <h2 id="Policies">3 General Policies for W3C Groups</h2>
       <p>This section describes general policies for W3C groups regarding participation, meeting requirements, and decision-making. These
-        policies apply to <span id="participant">participants</span> in the following groups: <a href="#AC">Advisory Committee</a>,
-        <a href="#ABParticipation">Advisory
+        policies apply to <span id="participant">participants</span> in the following groups: <a href="#AC">Advisory Committee</a>, <a href="#ABParticipation">Advisory
           Board</a>, <a href="#tag-participation">TAG</a>, <a href="#wgparticipant">Working Groups</a>, and <a href="#igparticipant">Interest
           Groups</a>.</p>
       <h3 id="ParticipationCriteria">3.1 Individual Participation Criteria</h3>
@@ -876,8 +860,7 @@
         <p>The Team makes every effort to ensure the persistence and availability of the following public information:</p>
         <ul>
           <li><a href="#Reports">W3C technical reports</a> whose publication has been approved by the Director. Per the Membership
-            Agreement, W3C technical reports (and software) are available free of charge to the general public; (refer to the
-            <a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C
+            Agreement, W3C technical reports (and software) are available free of charge to the general public; (refer to the <a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C
               Document License</a> [<a href="#ref-doc-license">PUB18</a>]).</li>
           <li>A <a href="http://www.w3.org/Consortium/mission">mission statement</a> [<a href="#ref-mission">PUB15</a>] that explains the
             purpose and mission of W3C, the key benefits for Members, and the organizational structure of W3C.</li>
@@ -939,8 +922,7 @@
         <ol>
           <li><a href="#GroupsWG">Working Groups.</a> Working Groups typically produce deliverables (e.g., <a href="#rec-advance">Recommendation
               Track technical reports</a>, software, test suites, and reviews of the deliverables of other groups). There are additional
-            participation requirements described in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
-            [<a href="#ref-patentpolicy">PUB33</a>].</li>
+            participation requirements described in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</li>
           <li><a href="#GroupsIG">Interest Groups.</a> The primary goal of an Interest Group is to bring together people who wish to
             evaluate potential Web technologies and policies. An Interest Group is a forum for the exchange of ideas.</li>
         </ol>
@@ -1053,8 +1035,7 @@
           <li>identify the organization, if any, the individual represents as a participant in this group,</li>
           <li>agree to the terms of the <a href="http://www.w3.org/Consortium/Legal/collaborators-agreement">invited expert and
               collaborators agreement</a> [<a href="#ref-invited-expert">PUB17</a>],</li>
-          <li>accept the participation terms set forth in the charter (including the participation requirements of
-            <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+          <li>accept the participation terms set forth in the charter (including the participation requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
               3</a> (especially 3.4) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section 6</a> (especially
             6.10) of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]).
             Indicate a specific charter date or version,</li>
@@ -1156,13 +1137,11 @@
             Royalty-Free licensing goals of section 2 of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a
               href="#ref-patentpolicy">PUB33</a>]?</li>
         </ul>
-        <p>See also the charter requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section 2</a> and
-          <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+        <p>See also the charter requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section 2</a> and <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>].</p>
         <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding participation,
           including specifying that the <dfn id="ig-mail-only">only requirement for participation (by anyone) in the Interest Group is
-            subscription to the Interest Group mailing list</dfn>. This type of Interest Group <em class="rfc2119">may</em> have
-          <a href="#public-participant-ig">public
+            subscription to the Interest Group mailing list</dfn>. This type of Interest Group <em class="rfc2119">may</em> have <a href="#public-participant-ig">public
             participants</a>.</p>
         <p>A charter <em class="rfc2119">may</em> include additional voting procedures, but those procedures <em class="rfc2119">must not</em>
           conflict with the <a href="#Votes">voting requirements</a> of the Process Document.</p>
@@ -1339,13 +1318,11 @@
         a Group Chair. It is the responsibility of these editors to ensure that the decisions of the Group are correctly reflected in
         subsequent drafts of the technical report. An editor <em class="rfc2119">must</em> be a participant, as a Member representative,
         Team representative, or Invited Expert in the Group responsible for the document(s) they are editing. </p>
-      <p>The Team is <em class="rfc2119">not required</em> to publish a Technical Report that does not conform to the Team's
-        <a href="http://www.w3.org/Guide/pubrules">Publication
+      <p>The Team is <em class="rfc2119">not required</em> to publish a Technical Report that does not conform to the Team's <a href="http://www.w3.org/Guide/pubrules">Publication
           Rules</a> [<a href="#rdf-pubrules">PUB31</a>](e.g., for <span id="DocumentName">naming</span>, status information, style, and <span
           id="document-copyright">copyright requirements</span>). These rules are subject to change by the Team from time to time. The Team
         <em class="rfc2119">must</em> inform group Chairs and the Advisory Committee of any changes to these rules.</p>
-      <p>The primary language for W3C Technical Reports is English. W3C encourages the translation of its Technical Reports.
-        <a href="http://www.w3.org/Consortium/Translation/">Information
+      <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>
       <p>For <em>all</em> requests to advance a specification to a new maturity level other than Note the Working Group:</p>
@@ -1367,8 +1344,7 @@
         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>
-      <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
+      <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
@@ -1445,8 +1421,7 @@
           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
+      <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>
       <p>A Working Group <em class="rfc2119">should</em> publish a Working Draft to the W3C Technical Reports page when there have been
@@ -1514,8 +1489,7 @@
       <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
-        Opportunity 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
+        Opportunity 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>]. Note that approval is <em>expected</em> to be fairly simple compared
         to getting approval for a transition from Working Draft to Candidate Recommendation.</p>
       <p>In addition the Working Group:</p>
@@ -1591,8 +1565,7 @@
         <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>
-      <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
+      <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>
         <svg xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 500 160" height="12em" width="50em">
@@ -1634,8 +1607,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">changes?</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>
@@ -1644,8 +1616,7 @@
             <path d="M486,103h20v40h-246v-15" fill="none"></path>
             <polygon points="260,128 262,133 258,133"></polygon>
             <polygon points="260,128 300,103 260,78 220,103" fill="none"></polygon>
-            <text font-size="10" stroke-width="0.2" x="260" y="98" text-anchor="middle">New<tspan x="260" y="108"
-              text-anchor="middle">Features?</tspan></text></g>
+            <text font-size="10" stroke-width="0.2" x="260" y="98" text-anchor="middle">New<tspan x="260" y="108" text-anchor="middle">Features?</tspan></text></g>
           <g id="Modif-NoNewFeatures">
             <path d="M260,78v-20" stroke="black"></path>
             <text x="262" y="75" font-size="10">No</text>
@@ -1710,8 +1681,7 @@
         specify any licensing requirements or commitments for Working Group Notes.</p>
       <h3 id="rec-rescind">7.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
+        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
           5</a> (bullet 10) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section 7.5</a>. A Working Group <em
           class="rfc2119">may</em> request the Director to rescind a Recommendation which was a deliverable, or the Director <em class="rfc2119">may</em>
@@ -1812,8 +1782,7 @@
       <ul>
         <li><a href="#rec-publication">Publication of a Recommendation</a> or <a href="#proposed-rescinded-rec">Publication of a Rescinded
             Recommendation</a>,</li>
-        <li><a href="#cfp">Working or Interest Group creation</a>, substantive <a href="#CharterReview">modification</a> or 
-          <a href="#charter-extension">extension</a>,</li>
+        <li><a href="#cfp">Working or Interest Group creation</a>, substantive <a href="#CharterReview">modification</a> or <a href="#charter-extension">extension</a>,</li>
         <li>Changes to the <a href="#GAProcess">W3C process</a>.</li>
       </ul>
       <p>Advisory Committee representatives <em class="rfc2119">may</em> always appeal the following decisions:</p>
@@ -1825,8 +1794,7 @@
       </ul>
       <p>In all cases, an appeal <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the
         decision.</p>
-      <p>An Advisory Committee representative initiates an appeal by sending a request to the Team (explained in detail in the 
-        <a href="http://www.w3.org/Member/Intro">New
+      <p>An Advisory Committee representative initiates an appeal by sending a request to the Team (explained in detail in the <a href="http://www.w3.org/Member/Intro">New
           Member Orientation</a>). The Team <em class="rfc2119">must</em> announce the appeal process to the Advisory Committee and provide
         an address for comments from Advisory Committee representatives. The archive of these comments <em class="rfc2119">must</em> be
         Member-visible. If, within <span class="time-interval">one week</span> of the Team's announcement, 5% or more of the Advisory
@@ -2150,8 +2118,7 @@
         <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
-            id="cgparticipant" name="cgparticipant"></a> <a id="CGCharter" name="CGCharter"></a>Coordination groups - 
-          <a href="https://www.w3.org/community/w3process/track/issues/129">ISSUE-129</a></li>
+            id="cgparticipant" name="cgparticipant"></a> <a id="CGCharter" name="CGCharter"></a>Coordination groups - <a href="https://www.w3.org/community/w3process/track/issues/129">ISSUE-129</a></li>
         <li>Remove vestigial traces of Good Standing throughout</li>
         <li>Loosen constraints on multiple employees of a single member being on TAG - <a href="#AB-TAG-constraints">section 2.5.1</a></li>
         <li>Replace "W3C Chair" with "CEO" throughout</li>
@@ -2161,7 +2128,7 @@
               href="#revised-wd">section 7.3.2</a><br>
           </span></li>
       </ul>
-      <h3>30 September "AC intermediate review" draft</h3>
+      <h3><a href="https://dvcs.w3.org/hg/AB/raw-file/622235dd5cba/cover.html">30 September "AC intermediate review" draft</a></h3>
       <p>Provided to the Advisory Committee to review the following changes made compared to the 1 August 2014 Operative Process document</p>
       <ul>
         <li>Remove <a id="ActivityProposal">Activities</a> from the Process (as resolved multiple times since 2007)</li>