Various editorial cleanups - typos, and some markup mistakes.
authorcharles
Wed, 28 Jan 2015 00:27:27 +0100
changeset 137 5408f1b3e4da
parent 136 d8fdfbc0ee40
child 138 71fbcdbb9364
Various editorial cleanups - typos, and some markup mistakes.
cover.html
--- a/cover.html	Wed Jan 21 16:43:05 2015 +0100
+++ b/cover.html	Wed Jan 28 00:27:27 2015 +0100
@@ -156,7 +156,7 @@
           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">
          <g id="basicProcess" opacity=".6">
            <g id="Modif-nodeWD">
              <ellipse ry="18" rx="38" cy="40" cx="147" stroke="black" fill="none"></ellipse>
              <a xlink:href="#RecsWD"><text font-size="14" font-family="Times,serif"
                  y="44"
                  x="147"
                  text-anchor="middle">WD</text></a>
            </g>
            <g id="Modif-repeatWD" stroke="black">
              <path d="M128,24C123,14 129,4 147,4 158,4 165,8 167,14" fill="none"
                stroke-dasharray="6 1"></path>
              <polygon points="170,14 166,24 164,13"></polygon> </g>
            <g class="edge" id="Modif-toCR" stroke="black" fill="black">
              <path d="M185,40h31"></path>
              <polygon points="211,36 221,40 211,44"></polygon> </g>
            <g id="Modif-nodeCR">
              <ellipse ry="18" rx="38" cy="40" cx="260" stroke="black" fill="none"></ellipse>
              <a xlink:href="#RecsCR"><text font-size="14" font-family="Times,serif"
                  y="44"
                  x="260"
                  text-anchor="middle">CR</text></a>
            </g>
            <g class="edge" id="Modif-repeatCR" stroke="black" fill="black">
              <path d="M242,24C238,14 244,4 260,4 271,4 277,8 279,14" stroke-dasharray="5 3"
                fill="none"></path>
              <polygon points="282,14 277,24 275,13"></polygon> </g>
            <g id="Modif-backToWD" stroke="#666" fill="#666">
              <path d="M190,47h34" stroke-dasharray="4 4"></path>
              <polygon points="190,45 183,47 190,49"></polygon> </g>
            <g class="edge" id="Modif-ToPR" stroke="black" fill="black">
              <path d="M298,40h27"></path>
              <polygon points="324,36 334,40 324,44"></polygon> </g>
            <g id="Modif-nodePR">
              <ellipse ry="18" rx="28" cy="40" cx="363" stroke="black" fill="none"></ellipse>
              <a xlink:href="#RecsPR"><text font-size="14" font-family="Times,serif"
                  y="44"
                  x="363"
                  text-anchor="middle">PR</text></a>
            </g>
            <g id="Modif-BackToCR" stroke="#aaa" fill="#aaa">
              <path d="M301,47h38" stroke-dasharray="2 5"></path>
              <polygon points="301,45 296,47 301,49"></polygon> </g>
            <g id="Modif-ToRec" stroke="black" fill="black">
              <path d="M391,40h20"></path>
              <polygon points="404,36 414,40 404,44"></polygon> </g> </g>
          <g id="Modif-nodeRec" stroke="black">
            <ellipse ry="18" rx="28" cy="40" cx="443" fill="none" stroke-width="2"></ellipse>
            <a xlink:href="#RecsW3C"><text font-size="16" font-family="Times,serif"
                y="44"
                x="443"
                text-anchor="middle"
                stroke-width=".3">REC</text></a></g>
          <g id="changeARec" stroke="black">
            <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>
          <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>
          <g id="Modif-RecSubstantiveChanges" stroke="black">
            <text x="488" y="100" font-size="10" stroke-width="0.2">Yes</text>
            <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>
          <g id="Modif-NoNewFeatures">
            <path d="M260,78v-20" stroke="black"></path>
            <text x="262" y="75" font-size="10">No</text>
            <polygon points="260,58 262,63 258,63" stroke="black"></polygon> </g>
          <g id="Modif-BackToFPWD" stroke="black">
            <a xlink:href="#first-wd"><text font-size="8" font-family="Times,serif"
                y="38"
                x="66"
                stroke="none">First
                 WD</text></a>
            <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>
      <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
        <meta charset="utf-8">
        any error that can be resolved by one or more changes in classes 1-3 of
        section <a href="#correction-classes">7.2.5 Classes of Changes</a>.</p>
      <p>Working Groups <em class="rfc2119">must</em> keep a
        <meta charset="utf-8">
        record as errors are reported by readers and implementers. Such error
        reports <em class="rfc2119">should</em> be processed no less frequently
        than quarterly. Readers of the Recommendation <em class="rfc2119">should</em>
        be able easily to find and see the errata that apply to that specific
        Recommendation.</p>
      <p>
        <meta charset="utf-8">
        Working groups may decide how to document errata. The best practice is a
        document that identifies itself as based on the Recommendation text and
        clearly identifies the errata and any proposed corrections; other
        approaches include various forms of an 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>
      <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 Working Group <span
          class="rfc2119">may</span>
        request publication of a <a href="#rec-pr">Proposed Recommendation</a>&nbsp;
         or W3C <span class="rfc2119">may</span> publish a <a href="#rec-pr">Proposed
-          Recommendation</a> to make this class of change without passing
        through earlier maturity levels. Such publications are <em class="rfc2119">may</em>
        be called a <dfn>Proposed Edited Recommendation</dfn>.</p>
      <p>To make corrections to a Recommendation that produce <a href="#substantive-change">substantive
+          Recommendation</a> to make this class of change without passing
        through earlier maturity levels. Such publications <em class="rfc2119">may</em>
        be called a <dfn>Proposed Edited Recommendation</dfn>.</p>
      <p>To make corrections to a Recommendation that produce <a href="#substantive-change">substantive
           changes</a> but do not add new features, a Working Group <span class="rfc2119">may</span>
        request publication of a <a href="#last-call">Candidate Recommendation</a>,
        without passing through earlier maturity levels.</p>
      <p>In the latter two cases, the resulting Recommendation <em class="rfc2119">may</em>
        be called an <dfn id="rec-edited">Edited Recommendation</dfn>.</p>
      <p>When requesting the publication of an edited Recommendation as
        described in this section, in addition to meeting the requirements for
        the relevant maturity level, a Working Group</p>
      <ul>
        <li><em class="rfc2119">must</em> show that the changes to the document
          have received <a href="#wide-review">wide review</a>, and </li>
        <li><em class="rfc2119">should</em> address all recorded errata.</li>
      </ul>
      <p>For changes which introduces a new feature or features, W3C <span class="rfc2119">must</span>
        follow the full process of <a href="#rec-advance">advancing a technical
          report to Recommendation</a> beginning with a new First Public Working
        Draft.</p>
      <h3 id="Note">7.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 standard.</p>
      <p>In order to publish a Note, a Working Group or Interest Group: </p>
      <ul>
        <li> <em class="rfc2119">may</em> publish a Note with or without its
          prior publication as a Working Draft.</li>
        <li><em class="rfc2119">must</em> record the group's decision to request
          publication as a Note, and</li>
        <li><em class="rfc2119">should</em> publish documentation of significant
          changes to the technical report since any previous publication.</li>
      </ul>
      <p>Possible next steps:</p>
      <ul>
        <li>End state: A technical report <em class="rfc2119">may</em> remain a
          Working Group Note indefinitely</li>
        <li>A Working Group <em class="rfc2119">may</em> resume work on
          technical report within the scope of its charter at any time, at the
          maturity level the specification had before publication as a Note</li>
      </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>
      <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
           5</a> (bullet 10) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section
@@ -217,4 +217,4 @@
               Notice and License</a></cite></dd>
        <dt id="rdf-translations">[PUB20]</dt>
        <dd><cite><a href="http://www.w3.org/Consortium/Translation/">Translations
               of W3C technical reports</a></cite></dd>
        <dt id="rdf-pub-mailing-lists">[PUB21]</dt>
        <dd><cite><a href="http://www.w3.org/Mail/">Public W3C mailing lists</a></cite></dd>
        <dt id="rdf-coi">[PUB23]</dt>
        <dd><cite><a href="http://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="rdf-tag-charter">[PUB25]</dt>
        <dd><cite><a href="http://www.w3.org/2001/07/19-tag">Technical
              Architecture Group (TAG) Charter</a></cite></dd>
        <dt id="rdf-tag-home">[PUB26]</dt>
        <dd><cite><a href="http://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
        <dt id="rdf-rec-tips">[PUB27]</dt>
        <dd><cite><a href="http://www.w3.org/2002/05/rec-tips">Tips for Getting
              to Recommendation Faster</a></cite></dd>
        <dt id="rdf-liaison-list">[PUB28]</dt>
        <dd><cite><a href="http://www.w3.org/2001/11/StdLiaison">W3C liaisons
              with other organizations</a></cite></dd>
        <dt id="rdf-ab-home">[PUB30]</dt>
        <dd><cite><a href="http://www.w3.org/2002/ab/">The Advisory Board home
              page</a></cite></dd>
        <dt id="rdf-pubrules">[PUB31]</dt>
        <dd><cite><a href="http://www.w3.org/Guide/pubrules">Publication Rules</a></cite></dd>
        <dt id="rdf-fellows">[PUB32]</dt>
        <dd><cite><a href="http://www.w3.org/Consortium/Recruitment/Fellows">W3C
              Fellows Program</a></cite></dd>
        <dt id="rdf-patentpolicy">[PUB33]</dt>
        <dd><cite><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
              Feb 2004 version of the W3C Patent Policy</a></cite>. The <a href="http://www.w3.org/Consortium/Patent-Policy/">latest
             version of the W3C Patent Policy</a> is available at
          http://www.w3.org/Consortium/Patent-Policy/.</dd>
        <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>
      <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>
        <dd><cite><a href="http://www.w3.org/Member/ACList">Current Advisory
              Committee representatives</a></cite></dd>
        <dt id="rdf-mailing-lists">[MEM2]</dt>
        <dd><cite><a href="http://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
        <dt id="rdf-calendar">[MEM3]</dt>
        <dd>The <cite><a href="http://www.w3.org/Member/Eventscal">calendar of
              all scheduled official W3C events</a></cite></dd>
        <dt id="rdf-new-member">[MEM4]</dt>
        <dd>The <cite><a href="http://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="rdf-ac-meetings">[MEM5]</dt>
        <dd><cite><a href="http://www.w3.org/Member/Meeting/">Advisory Committee
              meetings</a></cite></dd>
        <dt id="rdf-member-web">[MEM6]</dt>
        <dd><cite><a href="http://www.w3.org/Member/">Member Web site</a></cite></dd>
        <dt id="rdf-member-sub">[MEM8]</dt>
        <dd><cite><a href="http://www.w3.org/2000/09/submission">How to send a
              Submission request</a></cite></dd>
        <dt id="rdf-guide">[MEM9]</dt>
        <dd><cite><a href="http://www.w3.org/Guide/">The Art of Consensus</a></cite>,
          a guidebook for W3C Working Group Chairs and other collaborators</dd>
        <dt id="rdf-discipline-gl">[MEM14]</dt>
        <dd><cite><a href="http://www.w3.org/2002/09/discipline">Guidelines for
              Disciplinary Action</a></cite></dd>
        <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>
      <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.
          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>
      </dl>
      <h2 id="acks">14 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), Cullen Jennings (Cisco), Jeff Jaffe (W3C), 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 Microsystems), Wayne Carr
        (Intel), Marcos Cáceres (Mozilla), Michael Champion (Microsoft), Paul
        Cotton (Microsoft), Mark Crawford (SAP), Tantek Çelik (Mozilla), Don
        Deutsch (Oracle), David Fallside (IBM), Fantasai (Mozilla), Wendy Fong
        (Hewlett-Packard), Virginie Galindo (Gemalto), Daniel Glazman
        (Disruptive Innovations), Paul Grosso (Arbortext), Eduardo Gutentag (Sun
        Microsystems), Joe Hall (CDT), Ivan Herman (W3C), Ian Hickson (Google),
        Steve Holbrook (IBM), Renato Iannella (IPR Systems), Ian Jacobs (W3C),
        Jeff Jaffe (W3C), Cullen Jennings (Cisco), 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), Bede McCall (MITRE), Giri Mandyam (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>
      <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>
      <ul>
        <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>
      </ul>
      <h3>Previous Editor's drafts</h3>
      <ul>
        <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>
        <li>Remove vestigial traces of Good Standing</li>
        <li>Loosen requirement on multiple employees of one member on TAG -
          section 2.5.1</li>
        <li>Replace "W3C Chair" with "CEO"</li>
        <li>Editorial tweaks to what is requested for review</li>
        <li>Remove section <span id="three-month-rule">6.2.7 "Heartbeat"
            publishing requirement</span></li>
      </ul>
      <h3>30 September "AC intermediate review" draft</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>
        <li>Remove <a id="good-standing">6.2.1.7</a> Good Standing in a Working
          Group</li>
      </ul>
    </main>
  </body>
</html>
\ No newline at end of file
+          change logs</a> are available.</p>
      <p>The notable changes include:</p>
      <h3>Current Editor's draft</h3>
      <ul>
        <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>
      </ul>
      <h3>Previous Editor's drafts</h3>
      <ul>
        <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>
        <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>
        <li>Editorial tweaks to what is requested in <a href="file:///Users/chaals/Documents/w3c/AB/cover.html#wide-review">7.2.3.1
            Wide Review</a></li>
        <li>Remove section <span id="three-month-rule">6.2.7 "Heartbeat"
            publishing requirement, redundant with the first requirement of <a
              href="#revised-wd">section
              7.3.2</a><br>
          </span></li>
      </ul>
      <h3>30 September "AC intermediate review" draft</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>
        <li>Remove <a id="good-standing">6.2.1.7</a> Good Standing in a Working
          Group</li>
      </ul>
    </main>
  </body>
</html>
\ No newline at end of file