whitespace and the like.
authorcharles
Mon, 11 Jul 2016 02:18:28 +0200
changeset 176 f070f753bcea
parent 175 9d8c6442086a
child 177 31805674944b
whitespace and the like.
cover.html
--- a/cover.html	Mon Jul 11 01:57:31 2016 +0200
+++ b/cover.html	Mon Jul 11 02:18:28 2016 +0200
@@ -1927,54 +1927,69 @@
           on getting to Recommendation faster</a> [<a href="#ref-rec-tips">PUB27</a>].</p>
 
       <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 initiate an Advisory Committee Appeal of a W3C decision or Director's Decision. 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>.</p>
 
       <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>
-        <li><a href="#cfr">Proposed Recommendations</a>, <a href="#cfr-edited">Proposed Edited Recommendations</a>, <a href="#proposed-rescinded-rec">Proposal
-            to Rescind a Recommendation</a>, and</li>
+        <li><a href="#cfr">Proposed Recommendations</a>, <a href="#cfr-edited">Proposed Edited Recommendations</a>,
+          <a href="#proposed-rescinded-rec">Proposal to Rescind a Recommendation</a>, and</li>
         <li><a href="#GAProcess">Proposed changes to the W3C process</a>.</li>
       </ul>
+
       <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>
-        be returned by its Advisory Committee representative.</p>
+
+      <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> be returned by its Advisory Committee representative.</p>
+
       <p>The Team <em class="rfc2119">must</em> provide two channels for Advisory Committee review comments:</p>
+
       <ol>
         <li>an archived <a href="#Team-only">Team-only</a> channel;</li>
         <li>an archived <a href="#Member-only">Member-only</a> channel.</li>
       </ol>
+
       <p>The Call for Review <em class="rfc2119">must</em> specify which channel is the default for review comments on that Call.</p>
-      <p>Reviewers <em class="rfc2119">may</em> send information to either or both channels. They <em class="rfc2119">may</em> also share
-        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>
+
+      <p>Reviewers <em class="rfc2119">may</em> send information to either or both channels. They <em class="rfc2119">may</em> also
+        share 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">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
-          confidentiality level</a>. This <a href="#def-w3c-decision">W3C decision</a> is generally one of the following:</p>
+
+      <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 confidentiality level</a>. This <a href="#def-w3c-decision">W3C decision</a>
+        is generally one of the following:</p>
+
       <ol>
         <li>The proposal is approved, possibly with minor changes integrated.</li>
-        <li>The proposal is approved, possibly with <a href="#substantive-change">substantive changes</a> integrated. In this case the
-          Director's announcement <em class="rfc2119">must</em> include rationale for the decision to advance the document despite the
-          proposal for a substantive change.</li>
-        <li>The proposal is returned for additional work, with a request to the initiator to <a href="#formal-address">formally address</a>
-          certain issues.</li>
+        <li>The proposal is approved, possibly with <a href="#substantive-change">substantive changes</a> integrated. In this case
+          the Director's announcement <em class="rfc2119">must</em> include rationale for the decision to advance the document
+          despite the proposal for a substantive change.</li>
+        <li>The proposal is returned for additional work, with a request to the initiator to
+          <a href="#formal-address">formally address</a> certain issues.</li>
         <li>The proposal is rejected.</li>
       </ol>
-      <p>This document does not specify time intervals between the end of an Advisory Committee review period and the <a href="#def-w3c-decision">W3C
-          decision</a>. This is to ensure that the Members and Team have sufficient time to consider comments gathered during the review.
-        The Advisory Committee <em class="rfc2119">should not</em> expect an announcement sooner than <span class="time-interval">two
-          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>
+
+      <p>This document does not specify time intervals between the end of an Advisory Committee review period and the
+        <a href="#def-w3c-decision">W3C decision</a>. This is to ensure that the Members and Team have sufficient time to consider
+        comments gathered during the review. The Advisory Committee <em class="rfc2119">should not</em> expect an announcement
+        sooner than <span class="time-interval">two 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">7.2 Appeal by Advisory Committee Representatives</h3>
 
@@ -1994,8 +2009,8 @@
         described in this Process Document <em class="rfc2119">may</em> also be appealed if the type of appeal is identified where
         that Director's decision is described.</p>
 
-      <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>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. Within one week the Team 
         <em class="rfc2119">must</em> announce the appeal process to the Advisory Committee and provide a mechanism for
@@ -2015,32 +2030,41 @@
         "one vote per available seat".</p>
 
       <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 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
-        technology or policy, or to address the pressing concerns of W3C Members. Organizers of the first type of Workshop <em class="rfc2119">may</em>
-        solicit position papers for the Workshop program and <em class="rfc2119">may</em> use those papers to choose attendees and/or
-        presenters.</p>
+        technology or policy, or to address the pressing concerns of W3C Members. Organizers of the first type of Workshop
+        <em class="rfc2119">may</em> solicit position papers for the Workshop program and <em class="rfc2119">may</em> use those
+        papers to choose attendees and/or presenters.</p>
+
       <p>The goal of a Symposium is usually to educate interested parties about a particular subject.</p>
-      <p>The Call for Participation in a Workshop or Symposium <em class="rfc2119">may</em> indicate participation requirements or limits,
-        and expected deliverables (e.g., reports and minutes). Organization of an event does not guarantee further investment by W3C in a
-        particular topic, but <em class="rfc2119">may</em> lead to proposals for new activities or groups.</p>
-      <p>Workshops and Symposia generally last one to three days. If a Workshop is being organized to address the pressing concerns of
-        Members, the Team <em class="rfc2119">must</em> issue the Call for Participation no later than <span class="time-interval">six
-          weeks</span> prior to the Workshop's scheduled start date. For other Workshops and Symposia, the Team <em class="rfc2119">must</em>
-        issue a Call for Participation no later than <span class="time-interval">eight weeks</span> prior to the meeting's scheduled start
-        date. This helps ensure that speakers and authors have adequate time to prepare position papers and talks.</p>
-      <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>
+
+      <p>The Call for Participation in a Workshop or Symposium <em class="rfc2119">may</em> indicate participation requirements or 
+        limits, and expected deliverables (e.g., reports and minutes). Organization of an event does not guarantee further
+        investment by W3C in a particular topic, but <em class="rfc2119">may</em> lead to proposals for new activities or groups.</p>
+
+      <p>Workshops and Symposia generally last one to three days. If a Workshop is being organized to address the pressing concerns
+        of Members, the Team <em class="rfc2119">must</em> issue the Call for Participation no later than
+        <span class="time-interval">six weeks</span> prior to the Workshop's scheduled start date. For other Workshops and
+        Symposia, the Team <em class="rfc2119">must</em> issue a Call for Participation no later than
+        <span class="time-interval">eight weeks</span> prior to the meeting's scheduled start date. This helps ensure that speakers
+        and authors have adequate time to prepare position papers and talks.</p>
+
+      <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">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>
-      <p>All liaisons <em class="rfc2119">must</em> be coordinated by the Team due to requirements for public communication; patent,
-        copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.</p>
+      <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>
+
+      <p>All liaisons <em class="rfc2119">must</em> be coordinated by the Team due to requirements for public communication;
+        patent, copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.</p>
 
       <p>The W3C Director <em class="rfc2119">may</em> negotiate and sign a <dfn id="mou">Memorandum of Understanding
         (<abbr>MoU</abbr>)</dfn> with another organization. Before signing the MoU, the Team <em class="rfc2119">must</em> inform
@@ -2048,25 +2072,34 @@
         representatives <em class="rfc2119">may</em> initiate an <a href="#ACAppeal">Advisory Committee Appeal</a> of the decision
         to sign the MoU. Once approved, a Memorandum of Understanding <em class="rfc2119">should</em> be made public.</p>
 
-      <p>Information about <a href="https://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>
+      <p>Information about <a href="https://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">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
-        also publishes review comments on the Submitted materials for W3C Members, the public, and the media.</p>
+
+      <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 also publishes review comments on the Submitted materials for W3C Members, the public, and
+        the media.</p>
+
       <p>A <dfn id="MemberSubmission">Member Submission</dfn> consists of:</p>
+
       <ul>
         <li>One or more documents developed outside of the W3C process, and</li>
         <li>Information about the documents, provided by the Submitter.</li>
       </ul>
-      <p>One or more Members (called the "Submitter(s)") <em class="rfc2119">may</em> participate in a Member Submission. Only W3C Members
-        <em class="rfc2119">may</em> be listed as Submitter(s).</p>
+
+      <p>One or more Members (called the "Submitter(s)") <em class="rfc2119">may</em> participate in a Member Submission. Only W3C
+        Members <em class="rfc2119">may</em> be listed as Submitter(s).</p>
+
       <p>The Submission process consists of the following steps:</p>
+
       <ol>
-        <li>One of the Submitter(s) sends a request to the Team to acknowledge the Submission request. The Team and Submitter(s) communicate
-          to ensure that the Member Submission is complete.</li>
+        <li>One of the Submitter(s) sends a request to the Team to acknowledge the Submission request. The Team and Submitter(s)
+          communicate to ensure that the Member Submission is complete.</li>
         <li>After Team review, the Director <em class="rfc2119">must</em> either acknowledge or reject the Submission request.
+
           <ul>
             <li>If <a href="#SubmissionYes">acknowledged</a>, the Team <em class="rfc2119">must</em> publish the Member Submission
               at the public W3C Web site, in addition to Team comments about the Member Submission.</li>
@@ -2075,118 +2108,163 @@
           </ul>
         </li>
       </ol>
+
       <p><strong>Note:</strong> To avoid confusion about the Member Submission process, please note that:</p>
+
       <ul>
-        <li>Documents in a Member Submission are developed outside of W3C. These documents are <strong>not</strong> part of the <a href="#Reports">technical
-            report development process</a> (and therefore are not included in the <a href="https://www.w3.org/TR/">index of W3C technical
-            reports</a>). Members wishing to have documents developed outside of W3C published by W3C <em class="rfc2119">must</em> follow
-          the Member Submission process.</li>
-        <li>The Submission process is <strong>not</strong> a means by which Members ask for "ratification" of these documents as <a href="#RecsW3C">W3C
-            Recommendations</a>.</li>
-        <li>There is no requirement or guarantee that technology which is part of an acknowledged Submission request will receive further
-          consideration by W3C (e.g., by a W3C Working Group).</li>
+        <li>Documents in a Member Submission are developed outside of W3C. These documents are <strong>not</strong> part of the
+          <a href="#Reports">technical report development process</a> (and therefore are not included in the
+          <a href="https://www.w3.org/TR/">index of W3C technical reports</a>). Members wishing to have documents developed outside
+          of W3C published by W3C <em class="rfc2119">must</em> follow the Member Submission process.</li>
+        <li>The Submission process is <strong>not</strong> a means by which Members ask for "ratification" of these documents as
+          <a href="#RecsW3C">W3C Recommendations</a>.</li>
+        <li>There is no requirement or guarantee that technology which is part of an acknowledged Submission request will receive
+          further consideration by W3C (e.g., by a W3C Working Group).</li>
       </ul>
-      <p>Publication of a Member Submission by W3C does not imply endorsement by W3C, including the W3C Team or Members. The acknowledgment
-        of a Submission request does not imply that any action will be taken by W3C. It merely records publicly that the Submission request
-        has been made by the Submitter. A Member Submission published by W3C <em class="rfc2119">must not</em> be referred to as "work in
-        progress" of the W3C.</p>
-      <p>The list of <a href="https://www.w3.org/Submission/">acknowledged Member Submissions</a> [<a href="#ref-submission-list">PUB10</a>]
-        is available at the W3C Web site.</p>
+
+      <p>Publication of a Member Submission by W3C does not imply endorsement by W3C, including the W3C Team or Members. The
+        acknowledgment of a Submission request does not imply that any action will be taken by W3C. It merely records publicly that
+        the Submission request has been made by the Submitter. A Member Submission published by W3C
+        <em class="rfc2119">must not</em> be referred to as "work in progress" of the W3C.</p>
+
+      <p>The list of <a href="https://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">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
-        Submission request.</p>
+
+      <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 Submission request.</p>
+
       <p>At any time prior to acknowledgment, any Submitter <em class="rfc2119">may</em> withdraw support for a Submission request
-        (described in "<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>"). A Submission request is
-        "withdrawn" when no Submitter(s) support it. The Team <em class="rfc2119">must not</em> make statements about withdrawn Submission
-        requests.</p>
-      <p>Prior to acknowledgment, the Submitter(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>, refer to a
-        document as "submitted to the World Wide Web Consortium" or "under consideration by W3C" or any similar phrase either in public or
-        Member communication. The Submitter(s) <em class="rfc2119">must not</em> imply in public or Member communication that W3C is
-        working (with the Submitter(s)) on the material in the Member Submission. The Submitter(s) <em class="rfc2119">may</em> publish the
-        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>
+        (described in "<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>"). A Submission request
+        is "withdrawn" when no Submitter(s) support it. The Team <em class="rfc2119">must not</em> make statements about withdrawn
+        Submission requests.</p>
+
+      <p>Prior to acknowledgment, the Submitter(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>,
+       refer to a document as "submitted to the World Wide Web Consortium" or "under consideration by W3C" or any similar phrase
+       either in public or Member communication. The Submitter(s) <em class="rfc2119">must not</em> imply in public or Member
+       communication that W3C is working (with the Submitter(s)) on the material in the Member Submission. The Submitter(s)
+       <em class="rfc2119">may</em> publish the 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">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
-        the Working Group does not incorporate the technology, it <em class="rfc2119">should not</em> publish the contributed documents as
-        Working Group Notes since Working Group Notes represent group output, not input to the group.</p>
-      <p>On the other hand, while W3C is in the early stages of developing a charter, Members <em class="rfc2119">should</em> use the
-        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="https://www.w3.org/Consortium/mission">W3C's
-          mission</a> [<a href="#ref-mission">PUB15</a>].</p>
+
+      <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 the Working Group does not incorporate the technology, it
+        <em class="rfc2119">should not</em> publish the contributed documents as Working Group Notes since Working Group Notes
+        represent group output, not input to the group.</p>
+
+      <p>On the other hand, while W3C is in the early stages of developing a charter, Members <em class="rfc2119">should</em> use
+        the 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="https://www.w3.org/Consortium/mission">W3C's mission</a> [<a href="#ref-mission">PUB15</a>].</p>
+
       <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="https://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>
+
+      <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="https://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>
         hold the copyright for the documents in a Member Submission.</p>
-      <p>The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments of <a href="https://www.w3.org/Consortium/Patent-Policy#sec-submissions">section
-          3.3</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+
+      <p>The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments of
+        <a href="https://www.w3.org/Consortium/Patent-Policy#sec-submissions">section 3.3</a> of the
+        <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+
       <p>The Submitter(s) <em class="rfc2119">must</em> include the following information:</p>
+
       <ul>
         <li>The list of all submitting Members.</li>
-        <li>Position statements from all submitting Members (gathered by the Submitter). All position statements <em class="rfc2119">must</em>
-          appear in a separate document.</li>
-        <li>Complete electronic copies of any documents submitted for consideration (e.g., a technical specification, a position paper,
-          etc.) If the Submission request is acknowledged, these documents will be published by W3C and therefore <em class="rfc2119">must</em>
-          satisfy the Communication Team's <a href="https://www.w3.org/Guide/pubrules">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>].
-          Submitters may hold the copyright for the material contained in these documents, but when published by W3C, these documents <em class="rfc2119">must</em>
-          be subject to the provisions of the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> [<a
-            href="#ref-doc-license">PUB18</a>].</li>
+        <li>Position statements from all submitting Members (gathered by the Submitter). All position statements
+          <em class="rfc2119">must</em> appear in a separate document.</li>
+        <li>Complete electronic copies of any documents submitted for consideration (e.g., a technical specification, a position
+          paper, etc.) If the Submission request is acknowledged, these documents will be published by W3C and therefore
+          <em class="rfc2119">must</em> satisfy the Communication Team's
+          <a href="https://www.w3.org/Guide/pubrules">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>].
+          Submitters may hold the copyright for the material contained in these documents, but when published by W3C, these
+          documents <em class="rfc2119">must</em> be subject to the provisions of the
+          <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a>
+          [<a href="#ref-doc-license">PUB18</a>].</li>
       </ul>
+
       <p>The request <em class="rfc2119">must</em> also answer the following questions.</p>
+
       <ul>
-        <li>What proprietary technology is required to implement the areas addressed by the request, and what terms are associated with its
-          use? Again, many answers are possible, but the specific answer will affect the Team's decision.</li>
-        <li>What resources, if any, does the Submitter intend to make available if the W3C acknowledges the Submission request and takes
-          action on it?</li>
+        <li>What proprietary technology is required to implement the areas addressed by the request, and what terms are associated
+          with its use? Again, many answers are possible, but the specific answer will affect the Team's decision.</li>
+        <li>What resources, if any, does the Submitter intend to make available if the W3C acknowledges the Submission request and
+          takes action on it?</li>
         <li>What action would the Submitter like W3C to take if the Submission request is acknowledged?</li>
-        <li>What mechanisms are there to make changes to the specification being submitted? This includes, but is not limited to, stating
-          where change control will reside if the request is acknowledged.</li>
+        <li>What mechanisms are there to make changes to the specification being submitted? This includes, but is not limited to,
+          stating where change control will reside if the request is acknowledged.</li>
       </ul>
-      <p>For other administrative requirements related to Submission requests, see "<a href="https://www.w3.org/2000/09/submission">How to
-          send a Submission request</a>" [<a href="#ref-member-sub">MEM8</a>].</p>
+
+      <p>For other administrative requirements related to Submission requests, see
+        "<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>"
+        [<a href="#ref-member-sub">MEM8</a>].</p>
+
       <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="https://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
-        request and judged it complete and correct.</p>
-      <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>
+        requirements established by the Team, including the Team's
+        <a href="https://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 request and judged it complete and correct.</p>
+
+      <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">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>
+
+      <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>
         keep the Submitter(s) informed of when an announcement is likely to be made.</p>
+
       <p>Once a Submission request has been acknowledged, the Team <em class="rfc2119">must</em>:</p>
+
       <ul>
         <li>Publish the Member Submission.</li>
         <li>Publish Team comments about the Submission request.</li>
       </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>
+
+      <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">10.4 Rejection of a Submission Request, and Submission Appeals</h3>
 
-      <p>The Director <em class="rfc2119">may</em> reject a Submission request for a variety of reasons, including any of the following:</p>
+      <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
-          jeopardize the progress of the group.</li>
-        <li>The IPR statement made by the Submitter(s) is inconsistent with the W3C's <a href="https://www.w3.org/Consortium/Patent-Policy">Patent
-            Policy</a> [<a href="#ref-patentpolicy">PUB33</a>], <a href="https://www.w3.org/Consortium/Legal/copyright-documents">Document
-            License</a> [<a href="#ref-doc-license">PUB18</a>], or other IPR policies.</li>
-        <li>The ideas expressed in the request are poor, might harm the Web, or run counter to <a href="https://www.w3.org/Consortium/mission">W3C's
-            mission</a>.</li>
+        <li>The ideas expressed in the request overlap in scope with the work of a chartered Working Group, and acknowledgment
+          might jeopardize the progress of the group.</li>
+        <li>The IPR statement made by the Submitter(s) is inconsistent with the W3C's
+          <a href="https://www.w3.org/Consortium/Patent-Policy">Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
+          <a href="https://www.w3.org/Consortium/Legal/copyright-documents">Document License</a>
+          [<a href="#ref-doc-license">PUB18</a>], or other IPR policies.</li>
+        <li>The ideas expressed in the request are poor, might harm the Web, or run counter to
+          <a href="https://www.w3.org/Consortium/mission">W3C's mission</a>.</li>
         <li>The ideas expressed in the request lie well outside the scope of W3C's mission.</li>
       </ul>
+
       <p>In case of a rejection, the Team <em class="rfc2119">must</em> inform the Advisory Committee representative(s) of the
-        Submitter(s). If requested by the Submitter(s), the Team <em class="rfc2119">must</em> provide rationale to the Submitter(s) about
-        the rejection. Other than to the Submitter(s), the Team <em class="rfc2119">must not</em> make statements about why a Submission
-        request was rejected.</p>
+        Submitter(s). If requested by the Submitter(s), the Team <em class="rfc2119">must</em> provide rationale to the
+        Submitter(s) about the rejection. Other than to the Submitter(s), the Team <em class="rfc2119">must not</em> make
+        statements about why a Submission request was rejected.</p>
 
       <p>The Advisory Committee representative(s) of the Submitters(s) <em class="rfc2119">may</em> initiate a
         <a href="#SubmissionNo">Submission Appeal</a> of the Team's Decision to the <a href="#TAG">TAG</a> if the reasons are
@@ -2196,123 +2274,136 @@
         <a href="#confidentiality-levels">level of confidentiality</a>.</p>
 
       <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 <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>
+
       <ol>
         <li>The Team sends a Call for Review to the Advisory Committee and other W3C groups.</li>
-        <li>After comments have been <a href="#formal-address">formally addressed</a> and the document possibly modified, the Team seeks
-          endorsement from the Members by initiating an <a href="#ACReview">Advisory Committee review</a> of a Proposed Process Document.
+        <li>After comments have been <a href="#formal-address">formally addressed</a> and the document possibly modified, the Team
+          seeks endorsement from the Members by initiating an <a href="#ACReview">Advisory Committee review</a> of a
+          Proposed Process Document.
           The review period <em class="rfc2119">must</em> last at least <span class="time-interval">four weeks</span>.</li>
         <li><a href="#ACReviewAfter">After the Advisory Committee review</a>, if there is consensus, the Team enacts the new
           process officially by announcing the <a href="#def-w3c-decision">W3C decision</a> to the Advisory Committee. 
           Advisory Committee representatives <em class="rfc2119">may</em> initiate an
           <a href="#ACAppeal">Advisory Committee Appeal</a> to the W3C.</li>
       </ol>
-      <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>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">12 References</h2>
+
       <h3 id="public-refs">12.1 Public Resources</h3>
+
       <p>The following public information is available at the <a href="https://www.w3.org/">W3C Web site</a>.</p>
+
       <dl>
         <dt id="ref-join-w3c">[PUB5]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/join">How to Join W3C</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/join">How to Join W3C</a></cite></dd>
         <dt id="ref-member-agreement">[PUB6]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a></cite></dd>
         <dt id="ref-current-mem">[PUB8]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/Member/List">The list of current W3C Members</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/Member/List">The list of current W3C Members</a></cite></dd>
         <dt id="ref-activity-list">[PUB9]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/activities">The list of W3C Activities</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/activities">The list of W3C Activities</a></cite></dd>
         <dt id="ref-submission-list">[PUB10]</dt>
-        <dd><cite><a href="https://www.w3.org/Submission/">The list of acknowledged Member Submissions</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Submission/">The list of acknowledged Member Submissions</a></cite></dd>
         <dt id="ref-doc-list">[PUB11]</dt>
-        <dd><cite><a href="https://www.w3.org/TR/">The W3C technical reports index</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/TR/">The W3C technical reports index</a></cite></dd>
         <dt id="ref-submission-overview">[PUB13]</dt>
-        <dd><cite><a href="https://www.w3.org/Submission/1996/Template/">Submission request overview</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Submission/1996/Template/">Submission request overview</a></cite></dd>
         <dt id="ref-people">[PUB14]</dt>
-        <dd><cite><a href="https://www.w3.org/People/">The W3C Team</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/People/">The W3C Team</a></cite></dd>
         <dt id="ref-mission">[PUB15]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/">About the World Wide Web Consortium</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/">About the World Wide Web Consortium</a></cite></dd>
         <dt id="ref-team-submission-list">[PUB16]</dt>
-        <dd><cite><a href="https://www.w3.org/TeamSubmission/">The list of published Team Submissions</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/TeamSubmission/">The list of published Team Submissions</a></cite></dd>
         <dt id="ref-invited-expert">[PUB17]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">Invited expert and collaborators agreement</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">Invited expert and collaborators agreement</a></cite></dd>
         <dt id="ref-doc-license">[PUB18]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a></cite></dd>
         <dt id="ref-software-license">[PUB19]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software Notice and License</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software Notice and License</a></cite></dd>
         <dt id="ref-translations">[PUB20]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/Translation/">Translations of W3C technical reports</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/Translation/">Translations of W3C technical reports</a></cite></dd>
         <dt id="ref-pub-mailing-lists">[PUB21]</dt>
-        <dd><cite><a href="https://www.w3.org/Mail/">Public W3C mailing lists</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Mail/">Public W3C mailing lists</a></cite></dd>
         <dt id="ref-coi">[PUB23]</dt>
-        <dd><cite><a href="https://www.w3.org/2000/09/06-conflictpolicy">Conflict of Interest Policy for W3C Team Members Engaged in Outside
-              Professional Activities</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2000/09/06-conflictpolicy">Conflict of Interest Policy for W3C Team Members Engaged in Outside Professional Activities</a></cite></dd>
         <dt id="ref-tag-charter">[PUB25]</dt>
-        <dd><cite><a href="https://www.w3.org/2004/10/27-tag">Technical Architecture Group (TAG) Charter</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2004/10/27-tag">Technical Architecture Group (TAG) Charter</a></cite></dd>
         <dt id="ref-tag-home">[PUB26]</dt>
-        <dd><cite><a href="https://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
         <dt id="ref-rec-tips">[PUB27]</dt>
-        <dd><cite><a href="https://www.w3.org/2002/05/rec-tips">Tips for Getting to Recommendation Faster</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2002/05/rec-tips">Tips for Getting to Recommendation Faster</a></cite></dd>
         <dt id="ref-liaison-list">[PUB28]</dt>
-        <dd><cite><a href="https://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a></cite></dd>
         <dt id="ref-ab-home">[PUB30]</dt>
-        <dd><cite><a href="https://www.w3.org/2002/ab/">The Advisory Board home page</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2002/ab/">The Advisory Board home page</a></cite></dd>
         <dt id="ref-pubrules">[PUB31]</dt>
-        <dd><cite><a href="https://www.w3.org/Guide/pubrules">Publication Rules</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Guide/pubrules">Publication Rules</a></cite></dd>
         <dt id="ref-fellows">[PUB32]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a></cite></dd>
         <dt id="ref-patentpolicy">[PUB33]</dt>
-        <dd><cite><a href="https://www.w3.org/Consortium/Patent-Policy-20040205/">5 Feb 2004 version of the W3C Patent Policy</a></cite>. The
+         <dd><cite><a href="https://www.w3.org/Consortium/Patent-Policy-20040205/">5 Feb 2004 version of the W3C Patent Policy</a></cite>. The
           <a href="https://www.w3.org/Consortium/Patent-Policy/">latest version of the W3C Patent Policy</a> is available at
           https://www.w3.org/Consortium/Patent-Policy/.</dd>
         <dt id="in-place-tr-mod">[PUB35]</dt>
-        <dd><cite><a href="https://www.w3.org/2003/01/republishing/">In-place modification of W3C Technical Reports</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2003/01/republishing/">In-place modification of W3C Technical Reports</a></cite></dd>
       </dl>
+
       <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="https://www.w3.org/">W3C Web site</a>.</p>
+
+      <p>The following <a href="#Member-only">Member-only</a> information is available at the
+        <a href="https://www.w3.org/">W3C Web site</a>.</p>
+
       <dl>
         <dt id="ref-current-ac">[MEM1]</dt>
-        <dd><cite><a href="https://www.w3.org/Member/ACList">Current Advisory Committee representatives</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Member/ACList">Current Advisory Committee representatives</a></cite></dd>
         <dt id="ref-mailing-lists">[MEM2]</dt>
-        <dd><cite><a href="https://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
         <dt id="ref-calendar">[MEM3]</dt>
-        <dd>The <cite><a href="https://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite></dd>
+         <dd>The <cite><a href="https://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite></dd>
         <dt id="ref-new-member">[MEM4]</dt>
-        <dd>The <cite><a href="https://www.w3.org/Member/Intro">New Member Orientation</a></cite>, which includes an introduction to W3C
-          processes from a practical standpoint, including relevant email addresses.</dd>
+         <dd>The <cite><a href="https://www.w3.org/Member/Intro">New Member Orientation</a></cite>, which includes an introduction to W3C processes from a practical standpoint, including relevant email addresses.</dd>
         <dt id="ref-ac-meetings">[MEM5]</dt>
-        <dd><cite><a href="https://www.w3.org/Member/Meeting/">Advisory Committee meetings</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Member/Meeting/">Advisory Committee meetings</a></cite></dd>
         <dt id="ref-member-web">[MEM6]</dt>
-        <dd><cite><a href="https://www.w3.org/Member/">Member Web site</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/Member/">Member Web site</a></cite></dd>
         <dt id="ref-member-sub">[MEM8]</dt>
-        <dd><cite><a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a></cite></dd>
         <dt id="ref-guide">[MEM9]</dt>
-        <dd><cite><a href="https://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other
-          collaborators</dd>
+         <dd><cite><a href="https://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other collaborators</dd>
         <dt id="ref-discipline-gl">[MEM14]</dt>
-        <dd><cite><a href="https://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a></cite></dd>
         <dt id="ref-election-howto">[MEM15]</dt>
-        <dd><cite><a href="https://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a></cite></dd>
+         <dd><cite><a href="https://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a></cite></dd>
       </dl>
+
       <h3 id="other-refs">12.3 Other References</h3>
+
       <dl>
         <dt id="ref-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.
-          Bradner, March 1997.</dd>
+         <dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">"Key words for use in RFCs to Indicate Requirement Levels"</a></cite>, S. Bradner, March 1997.</dd>
         <dt id="ref-RFC2777">[RFC2777]</dt>
-        <dd><cite><a href="http://www.ietf.org/rfc/rfc2777.txt">"Publicly Verifiable Nomcom Random Selection"</a></cite>, D. Eastlake 3rd,
-          February 2000.</dd>
+         <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">13 Acknowledgments</h2>
+
       <p>The following individuals have contributed to this proposal for a revised Process: Daniel Appelquist,
         David Baron (Mozilla), J Alan Bird (W3C), Carine Bournez (W3C), Wayne Carr (Intel),
         Tantek Çelik (Mozilla), Michael Champion (W3C), Maria Courtemanche (IBM), Donald Deutsch (Oracle),
         Geoffrey Creighton (Microsoft),
         Kevin Fleming (Bloomberg), Virginia Fournier (Apple), Virginie Galindo (Gemalto),
         Daniel Glazman (Disruptive Innovations), Michael Geldblum (), Jeff Jaffe (W3C), Jay Junichi Kishigami (NTT),
-        Peter Patel-Schneider, Scott Peterson (Google), Delfí Ramírez, Florian Rivoal, Wendy Seltzer (W3C),
+        Mark Nottingham, Peter Patel-Schneider, Scott Peterson (Google), Delfí Ramírez, Florian Rivoal, Wendy Seltzer (W3C),
         David Singer (Apple), Geoffrey Snedden, Josh Soref,
         Léonie Watson (The Paciello Group), Ben Wilson, Chris Wilson (Google), Rigo Wenning (W3C), Helene Workman (Apple),
         Judy Zhu 茱滴 (Alibaba), Steve Zilles (Adobe).</p>
@@ -2329,7 +2420,8 @@
         Ian Jacobs (W3C), Jeff Jaffe (W3C), Cullen Jennings (Cisco), Brain Kardell (JQuery), Sally Khudairi (W3C),
         John Klensin (MCI), Tim Krauskopf (Spyglass), Kari Laihonen (Ericsson), Ken Laskey (MITRE), Ora Lassila (Nokia),
         Håkon Wium Lie (Opera Software), Chris Lilley (W3C), Peter Linss (HP), Bede McCall (MITRE), Giri Mandyam (Qualcomm),
-        Larry Masinter (Adobe Systems), Nigel Megitt (BBC), Olle Olsson (SICS), Qiuling Pan (Huawei), TV Raman (Google),
+        Larry Masinter (Adobe Systems), Nigel Megitt (BBC), Olle Olsson (SICS), Mark Nottingham, Qiuling Pan (Huawei),
+        TV Raman (Google),
         Thomas Reardon (Microsoft), Claus von Riegen (SAP AG), Natasha Rooney (GSMA), Sam Ruby (IBM), David Singer (Apple),
         David Singer (IBM), Henri Sivonen (Mozilla), Josh Soref (BlackBerry), Ralph Swick (W3C), Anne van Kesteren,
         Jean-Charles Verdié (MStar), Mike West (Google),  Chris Wilson (Google), Lauren Wood (unaffiliated),
@@ -2340,7 +2432,9 @@
       <p>This document is based on the <a href="https://www.w3.org/2015/Process-20150901/">1 September 2015 Process. <a href="https://dvcs.w3.org/hg/AB/">Detailed change logs</a> are available.</p>
 
       <p>The notable changes include:</p>
+
       <h3>Current draft</h3>
+
       <ul>
         <li>Added a process to make a Recommendation Obsolete - 6.9</a></li>
         <li>Clarified the process to rescind a Recommendation, aligning with with obsoleting a Recommendation - 6.9</a></li>
@@ -2356,6 +2450,7 @@
           <a href="#ReviewAppeal">7</a>, <a href="#ACAppeal">7.2</a>, <a href="ACVotes">7.3</a>,
           <a href="#Submission">10</a>, <a href="#SubmissionNo">10.4</a>, <a href="#GAProcess">11</a></li>
       </ul>
+
     </main>
   </body>
 </html>