tr.html
changeset 55 6bd6536dd075
parent 54 840ff6a43e74
child 56 18c78ed75463
equal deleted inserted replaced
54:840ff6a43e74 55:6bd6536dd075
    54             chapter 7 of the W3C process document</a> with a more effective W3C
    54             chapter 7 of the W3C process document</a> with a more effective W3C
    55           Specification life cycle following the meeting of the W3C Advisory
    55           Specification life cycle following the meeting of the W3C Advisory
    56           Board's Chapter 7 Task Force on 2 December 2013. This document is the
    56           Board's Chapter 7 Task Force on 2 December 2013. This document is the
    57           editor's draft for resolution of comments received on the "Last Call"
    57           editor's draft for resolution of comments received on the "Last Call"
    58           version.</p>
    58           version.</p>
    59         <p>In this draft, there has been a reordering of the content along the
    59         <p>In this draft, there are some pointers and placeholders for changes
    60           lines foreshadowed by <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a>.
    60           expected in response to open issues, most particularly <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a>.</p>
    61           Sections have now been renumbered, the "outline" (heading structure)
       
    62           rebuilt and some headings changed. No content has been deleted since
       
    63           the last commit (except in this introductory material).</p>
       
    64         <p>This introductory session (before the chapter title below) will be
    61         <p>This introductory session (before the chapter title below) will be
    65           removed when this chapter is re-incorporated into the full process
    62           removed when this chapter is re-incorporated into the full process
    66           document, as per issues 60-64.</p>
    63           document, as per issues 60-64.</p>
    67         <p>An initial version was first proposed to the W3C Advisory Board on 13
    64         <p>An initial version was first proposed to the W3C Advisory Board on 13
    68           May 2013 as a possible replacement for the <a href="http://www.w3.org/2005/10/Process-20051014/tr.html">current
    65           May 2013 as a possible replacement for the <a href="http://www.w3.org/2005/10/Process-20051014/tr.html">current
   110             Recommendation.</li>
   107             Recommendation.</li>
   111           <li>The Director is required to address AC review comments <strong>publicly</strong>,
   108           <li>The Director is required to address AC review comments <strong>publicly</strong>,
   112             2 weeks <em>before</em> publication of a Recommendation.</li>
   109             2 weeks <em>before</em> publication of a Recommendation.</li>
   113           <li>And it is in HTML5</li>
   110           <li>And it is in HTML5</li>
   114         </ul>
   111         </ul>
   115         <p>Editorially, I have tried to rationalize requirements, and clarify
   112         <p>Editorially, I have tried to rationalize requirements and clarify who
   116           who is responsible for meeting them. I have also actively removed
   113           is responsible for meeting them. I have also removed advice and
   117           advice and general statements to keep this version short.</p>
   114           general statements to keep this version short.</p>
   118       </div>
   115       </div>
   119     </div>
   116     </div>
   120     <h2>7 <a name="Reports" id="Reports">W3C Technical Report Development
   117     <h2 id="Reports">7 W3C Technical Report Development Process</h2>
   121         Process</a></h2>
       
   122     <p>The W3C technical report development process is the set of steps and
   118     <p>The W3C technical report development process is the set of steps and
   123       requirements followed by W3C <a href="http://www.w3.org/2005/10/Process-20051014/groups#GroupsWG">Working
   119       requirements followed by W3C <a href="http://www.w3.org/2005/10/Process-20051014/groups#GroupsWG">Working
   124         Groups</a> to standardize Web technology. The W3C technical report
   120         Groups</a> to standardize Web technology. The W3C technical report
   125       development process is designed to </p>
   121       development process is designed to </p>
   126     <ul>
   122     <ul>
   130         about the content of stable technical reports</li>
   126         about the content of stable technical reports</li>
   131       <li>ensure high technical and editorial quality</li>
   127       <li>ensure high technical and editorial quality</li>
   132       <li>promote consistency among specifications</li>
   128       <li>promote consistency among specifications</li>
   133       <li>facilitate royalty-free, interoperable implementations of Web
   129       <li>facilitate royalty-free, interoperable implementations of Web
   134         Standards, and</li>
   130         Standards, and</li>
   135       <li>earn endorsement by W3C and the broader community. </li>
   131       <li>earn endorsement by W3C and the broader community.</li>
   136     </ul>
   132     </ul>
   137     <p>See also the licensing goals for W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section
   133     <p>See also the licensing goals for W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section
   138         2</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
   134         2</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
   139         Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].
   135         Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].
   140       </p>
   136       </p>
   141     <h3>Table of Contents</h3>
   137     <h3>Table of Contents</h3>
   142     <ul id="mozToc">
   138     <ul id="mozToc">
   143       <!--mozToc h3 1 h4 2 h5 3-->
   139       <!--mozToc h3 1 h4 2 h5 3-->
   144       <li><a href="#mozTocId615339">Table of Contents</a></li>
   140       <li><a href="#rec-advance">7.1 W3C Technical Reports</a>
   145       <li><a href="#mozTocId661463">7.1 W3C Technical Reports</a>
       
   146         <ul>
   141         <ul>
   147           <li><a href="#mozTocId598359">7.1.1 Recommendations and Notes</a></li>
   142           <li><a href="#recs-and-notes">7.1.1 Recommendations and Notes</a></li>
   148           <li><a href="#mozTocId643257">7.1.2 Maturity Levels</a></li>
   143           <li><a href="#maturity-levels">7.1.2 Maturity Levels</a></li>
   149         </ul>
   144         </ul>
   150       </li>
   145       </li>
   151       <li><a href="#mozTocId674003">7.2 General requirements and definitions</a>
   146       <li><a href="#requirements-and-definitions">7.2 General requirements and
       
   147           definitions</a>
   152         <ul>
   148         <ul>
   153           <li><a href="#mozTocId840436">7.2.1 General requirements for Technical
   149           <li><a href="#general-requirements">7.2.1 General requirements for
   154               Reports</a></li>
   150               Technical Reports</a></li>
   155           <li><a href="#mozTocId650463">7.2.2 Advancement on the Recommendation
   151           <li><a href="#transition-reqs">7.2.2 Advancement on the Recommendation
   156               Track</a>
   152               Track</a>
   157             <ul>
   153             <ul>
   158               <li><a href="#mozTocId787038">7.2.2.1 Substantive Change</a></li>
   154               <li><a href="#substantive-change">7.2.2.1 Substantive Change</a></li>
   159             </ul>
   155             </ul>
   160           </li>
   156           </li>
   161           <li><a href="#mozTocId891540">7.2.3 Reviews and Review
   157           <li><a href="#doc-reviews">7.2.3 Reviews and Review Responsibilities</a>
   162               Responsibilities</a>
       
   163             <ul>
   158             <ul>
   164               <li><a href="#mozTocId712209">7.2.3.1 Wide Review</a></li>
   159               <li><a href="#wide-review">7.2.3.1 Wide Review</a></li>
   165             </ul>
   160             </ul>
   166           </li>
   161           </li>
   167           <li><a href="#mozTocId677214">7.2.4 Implementation Experience</a></li>
   162           <li><a href="#implementation-experience">7.2.4 Implementation
       
   163               Experience</a></li>
   168         </ul>
   164         </ul>
   169       </li>
   165       </li>
   170       <li><a href="#mozTocId124435">7.3 Working Draft</a>
   166       <li><a href="#working-draft">7.3 Working Draft</a>
   171         <ul>
   167         <ul>
   172           <li><a href="#mozTocId531921">7.3.1 First Public Working Draft</a></li>
   168           <li><a href="#first-wd">7.3.1 First Public Working Draft</a></li>
   173           <li><a href="#mozTocId557161">7.3.2 Revised Public Working Drafts</a></li>
   169           <li><a href="#revised-wd">7.3.2 Revised Public Working Drafts</a></li>
   174         </ul>
   170         </ul>
   175       </li>
   171       </li>
   176       <li><a href="#mozTocId603428">7.4 Candidate Recommendation</a>
   172       <li><a href="#candidate-rec">7.4 Candidate Recommendation</a>
   177         <ul>
   173         <ul>
   178           <li><a href="#mozTocId884719">7.4.1 Revised Candidate Recommendation</a></li>
   174           <li><a href="#revised-cr">7.4.1 Revised Candidate Recommendation</a></li>
   179         </ul>
   175         </ul>
   180       </li>
   176       </li>
   181       <li><a href="#mozTocId388392">7.5 W3C Recommendation</a>
   177       <li><a href="#rec-publication">7.5 W3C Recommendation</a>
   182         <ul>
   178         <ul>
   183           <li><a href="#mozTocId753802">7.5.1 For all W3C Recommendations</a></li>
   179           <li><a href="#for-all-recs">7.5.1 For all W3C Recommendations</a></li>
   184           <li><a href="#mozTocId368357">7.5.2 Publishing a Candidate
   180           <li><a href="#lcrec-publication">7.5.2 Publishing a Candidate
   185               Recommendation as a W3C Recommendation</a></li>
   181               Recommendation as a W3C Recommendation</a></li>
   186         </ul>
   182         </ul>
   187       </li>
   183       </li>
   188       <li><a href="#mozTocId66258">7.6 Modifying a W3C Recommendation</a>
   184       <li><a href="#rec-modify">7.6 Modifying a W3C Recommendation</a>
   189         <ul>
   185         <ul>
   190           <li><a href="#mozTocId861101">7.6.1 Errata Management</a></li>
   186           <li><a href="#errata">7.6.1 Errata Management</a></li>
   191           <li><a href="#mozTocId582942">7.6.2 Classes of Changes to a
   187           <li><a href="#correction-classes">7.6.2 Classes of Changes to a
   192               Recommendation</a></li>
   188               Recommendation</a></li>
   193           <li><a href="#mozTocId478895">7.6.3 Revised Recommendation</a></li>
   189           <li><a href="#revised-rec">7.6.3 Revising a Recommendation</a></li>
   194         </ul>
   190         </ul>
   195       </li>
   191       </li>
   196       <li><a href="#mozTocId663232">7.7 Publishing a Working Group or Interest
   192       <li><a href="#tr-end">7.7 Publishing a Working Group or Interest Group
   197           Group Note</a></li>
   193           Note</a></li>
   198       <li><a href="#mozTocId592607">7.8 Rescinding a W3C Recommendation</a></li>
   194       <li><a href="#good-practice">7.8 Rescinding a W3C Recommendation</a></li>
   199       <li><a href="#mozTocId806006">Further reading</a></li>
   195       <li><a href="#mozTocId806006">Further reading</a></li>
   200     </ul>
   196     </ul>
   201     <h3>7.1 <a name="rec-advance" id="rec-advance">W3C Technical Reports</a></h3>
   197     <h3 id="rec-advance">7.1 W3C Technical Reports</h3>
   202     <h4>7.1.1 Recommendations and Notes</h4>
   198     <h4 id="recs-and-notes">7.1.1 Recommendations and Notes</h4>
   203     <p>W3C follows these steps when advancing a technical report to
   199     <p>W3C follows these steps when advancing a technical report to
   204       Recommendation.</p>
   200       Recommendation.</p>
   205     <ol>
   201     <ol>
   206       <li><a href="#first-wd">Publication of the First Public Working Draft</a>,</li>
   202       <li><a href="#first-wd">Publication of the First Public Working Draft</a>,</li>
   207       <li><a href="#hb-wd">Publication of zero or more revised Public Working
   203       <li><a href="#hb-wd">Publication of zero or more revised Public Working
   265         Committee</a> and Working Group Chairs when a Working Group's request
   261         Committee</a> and Working Group Chairs when a Working Group's request
   266       for a specification to advance in maturity level is declined and and the
   262       for a specification to advance in maturity level is declined and and the
   267       specification is returned to a Working Group for further work.</p>
   263       specification is returned to a Working Group for further work.</p>
   268     <p class="issue">Add a short explanation of Note track, and how documents
   264     <p class="issue">Add a short explanation of Note track, and how documents
   269       can go from Rec-track to Note and back, to this section. <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a></p>
   265       can go from Rec-track to Note and back, to this section. <a href="http://www.w3.org/community/w3process/track/issues/59">ISSUE-59</a></p>
   270     <h4>7.1.2 <a name="maturity-levels" id="maturity-levels">Maturity Levels</a></h4>
   266     <h4 id="maturity-levels">7.1.2 Maturity Levels</h4>
   271     <dl>
   267     <dl>
   272       <dt><a name="RecsWD" id="RecsWD">Working Draft (WD)</a></dt>
   268       <dt id="RecsWD">Working Draft (WD)</dt>
   273       <dd>A Working Draft is a document that W3C has published for review by the
   269       <dd>A Working Draft is a document that W3C has published for review by the
   274         community, including W3C Members, the public, and other technical
   270         community, including W3C Members, the public, and other technical
   275         organizations. Some, but not all, Working Drafts are meant to advance to
   271         organizations. Some, but not all, Working Drafts are meant to advance to
   276         Recommendation; see the <a href="#DocumentStatus">document status
   272         Recommendation; see the <a href="#DocumentStatus">document status
   277           section</a> of a Working Draft for the group's expectations. Any
   273           section</a> of a Working Draft for the group's expectations. Any
   278         Working Draft not, or no longer, intended to advance to Recommendation <em
   274         Working Draft not, or no longer, intended to advance to Recommendation <em
   279           class="rfc2119">should</em> be published as a Working Group Note.
   275           class="rfc2119">should</em> be published as a Working Group Note.
   280         Working Drafts do not necessarily represent a consensus of the Working
   276         Working Drafts do not necessarily represent a consensus of the Working
   281         Group, and do not imply any endorsement by W3C or its members beyond
   277         Group, and do not imply any endorsement by W3C or its members beyond
   282         agreement to work on a general area of technology.</dd>
   278         agreement to work on a general area of technology.</dd>
   283       <dt><a name="RecsCR" id="RecsCR">Candidate Recommendation (CR)</a></dt>
   279       <dt id="RecsCR">Candidate Recommendation (CR)</dt>
   284       <dd class="changed">A Candidate Recommendation is a document that
   280       <dd class="changed">A Candidate Recommendation is a document that
   285         Satisfies the Working Group's technical requirements, and has already
   281         Satisfies the Working Group's technical requirements, and has already
   286         received wide review. W3C publishes a Candidate Recommendation to
   282         received wide review. W3C publishes a Candidate Recommendation to
   287         <ul>
   283         <ul>
   288           <li>signal to the wider community that a final review should be done</li>
   284           <li>signal to the wider community that a final review should be done</li>
   299         as "Last Call Working Draft"</dd>
   295         as "Last Call Working Draft"</dd>
   300       <dd><strong>Note:</strong> Candidate Recommendations will normally be
   296       <dd><strong>Note:</strong> Candidate Recommendations will normally be
   301         accepted as Recommendations. Announcement of a different next step <em
   297         accepted as Recommendations. Announcement of a different next step <em
   302           class="rfc2119">should</em> include the reasons why the change in
   298           class="rfc2119">should</em> include the reasons why the change in
   303         expectations comes at so late a stage.</dd>
   299         expectations comes at so late a stage.</dd>
   304       <dt><a name="RecsW3C" id="RecsW3C">W3C Recommendation (REC)</a></dt>
   300       <dt id="RecsW3C">W3C Recommendation (REC)</dt>
   305       <dd>A W3C Recommendation is a specification or set of guidelines or
   301       <dd>A W3C Recommendation is a specification or set of guidelines or
   306         requirements that, after extensive consensus-building, has received the
   302         requirements that, after extensive consensus-building, has received the
   307         endorsement of W3C Members and the Director. W3C recommends the wide
   303         endorsement of W3C Members and the Director. W3C recommends the wide
   308         deployment of its Recommendations as standards for the Web.</dd>
   304         deployment of its Recommendations as standards for the Web.</dd>
   309       <dt><a name="WGNote" id="WGNote">Working Group Note, Interest Group Note
   305       <dt id="WGNote">Working Group Note, Interest Group Note (NOTE) </dt>
   310           (NOTE) </a></dt>
       
   311       <dd>A Working Group Note or Interest Group Note is published by a
   306       <dd>A Working Group Note or Interest Group Note is published by a
   312         chartered Working Group or Interest Group to provide a stable reference
   307         chartered Working Group or Interest Group to provide a stable reference
   313         for a document that is not intended to be a specification requiring
   308         for a document that is not intended to be a specification requiring
   314         conformance, but is nevertheless useful. Examples include supporting
   309         conformance, but is nevertheless useful. Examples include supporting
   315         documents such as Use case and Requirements documents, Design Principles
   310         documents such as Use case and Requirements documents, Design Principles
   316         that explain what the Working Group was trying to achieve with a
   311         that explain what the Working Group was trying to achieve with a
   317         specification, or 'Good Practices" documents. A Working Group <em class="rfc2119">may</em>
   312         specification, or 'Good Practices" documents. A Working Group <em class="rfc2119">may</em>
   318         also publish a specification as a Note if they stop work without
   313         also publish a specification as a Note if they stop work without
   319         producing a Recommendation. A Working Group or Interest Group <em class="rfc2119">may</em>
   314         producing a Recommendation. A Working Group or Interest Group <em class="rfc2119">may</em>
   320         publish a Note with or without its prior publication as a Working Draft.</dd>
   315         publish a Note with or without its prior publication as a Working Draft.</dd>
   321       <dt><a name="RescindedRec" id="RescindedRec">Rescinded Recommendation</a></dt>
   316       <dt id="RescindedRec">Rescinded Recommendation</dt>
   322       <dd>A Rescinded Recommendation is an entire Recommendation that W3C no
   317       <dd>A Rescinded Recommendation is an entire Recommendation that W3C no
   323         longer endorses. See also clause 10 of the licensing requirements for
   318         longer endorses. See also clause 10 of the licensing requirements for
   324         W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section
   319         W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section
   325           5</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
   320           5</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
   326           Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</dd>
   321           Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</dd>
   329       "Editor's drafts". Editor's drafts have no official standing whatsoever,
   324       "Editor's drafts". Editor's drafts have no official standing whatsoever,
   330       and do not imply consensus of a Working Group or Interest Group, nor are
   325       and do not imply consensus of a Working Group or Interest Group, nor are
   331       their contents endorsed in any way by W3C or its members, except to the
   326       their contents endorsed in any way by W3C or its members, except to the
   332       extent that such contents happen to be consistent with some other document
   327       extent that such contents happen to be consistent with some other document
   333       which carries a higher level of endorsement.</p>
   328       which carries a higher level of endorsement.</p>
   334     <h3>7.2 General requirements and definitions</h3>
   329     <h3 id="requirements-and-definitions">7.2 General requirements and
       
   330       definitions</h3>
   335     <h4 id="general-requirements">7.2.1 General requirements for Technical
   331     <h4 id="general-requirements">7.2.1 General requirements for Technical
   336       Reports</h4>
   332       Reports</h4>
   337     <p>Every document published as part of the technical report development
   333     <p>Every document published as part of the technical report development
   338       process <em class="rfc2119 old">must</em> be a public document. The <a href="http://www.w3.org/TR/">index
   334       process <em class="rfc2119 old">must</em> be a public document. The <a href="http://www.w3.org/TR/">index
   339         of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-doc-list">PUB11</a>]
   335         of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-doc-list">PUB11</a>]
   376       and the Advisory Committee of any changes to these rules.</p>
   372       and the Advisory Committee of any changes to these rules.</p>
   377     <p>The primary language for W3C Technical Reports is English. W3C encourages
   373     <p>The primary language for W3C Technical Reports is English. W3C encourages
   378       the translation of its Technical Reports. <a href="http://www.w3.org/Consortium/Translation/">Information
   374       the translation of its Technical Reports. <a href="http://www.w3.org/Consortium/Translation/">Information
   379         about translations of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-translations">PUB18</a>]
   375         about translations of W3C technical reports</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-translations">PUB18</a>]
   380       is available at the W3C Web site.</p>
   376       is available at the W3C Web site.</p>
   381     <h4>7.2.2 <a name="transition-reqs" id="transition-reqs">Advancement on the
   377     <h4 id="transition-reqs">7.2.2 Advancement on the Recommendation Track</h4>
   382         Recommendation Track</a></h4>
       
   383     <p>For <em>all</em> requests to advance a specification to a new maturity
   378     <p>For <em>all</em> requests to advance a specification to a new maturity
   384       level other than Note the Working Group:</p>
   379       level other than Note the Working Group:</p>
   385     <ul>
   380     <ul>
   386       <li><em class="rfc2119">must</em> record the group's decision to request
   381       <li><em class="rfc2119">must</em> record the group's decision to request
   387         advancement.</li>
   382         advancement.</li>
   413     <p> A <dfn>substantive change</dfn> (whether deletion, inclusion, or other
   408     <p> A <dfn>substantive change</dfn> (whether deletion, inclusion, or other
   414       modification) is one where someone could reasonably expect that making the
   409       modification) is one where someone could reasonably expect that making the
   415       change would invalidate an individual's review or implementation
   410       change would invalidate an individual's review or implementation
   416       experience. Other changes (e.g., clarifications, bug fixes, editorial
   411       experience. Other changes (e.g., clarifications, bug fixes, editorial
   417       repairs, and minor error corrections) are minor changes.</p>
   412       repairs, and minor error corrections) are minor changes.</p>
   418     <h4>7.2.3 <a name="doc-reviews" id="doc-reviews">Reviews and Review
   413     <h4 id="doc-reviews">7.2.3 Reviews and Review Responsibilities</h4>
   419         Responsibilities</a></h4>
       
   420     <p>A document is available for review from the moment it is first published.
   414     <p>A document is available for review from the moment it is first published.
   421       Working Groups <em class="rfc2119">should</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
   415       Working Groups <em class="rfc2119">should</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
   422         address</a> <em>any</em> substantive review comment about a technical
   416         address</a> <em>any</em> substantive review comment about a technical
   423       report in a timely manner. </p>
   417       report in a timely manner. </p>
   424     Reviewers <em class="rfc2119">should</em> send substantive technical
   418     Reviewers <em class="rfc2119">should</em> send substantive technical
   475       implementations can be very time consuming. Groups are often able to work
   469       implementations can be very time consuming. Groups are often able to work
   476       more effectively if they plan how they will demonstrate interoperable
   470       more effectively if they plan how they will demonstrate interoperable
   477       implementations early in the development process; for example, they may
   471       implementations early in the development process; for example, they may
   478       wish to develop tests in concert with implementation efforts.</p>
   472       wish to develop tests in concert with implementation efforts.</p>
   479     <h3 id="working-draft">7.3 Working Draft</h3>
   473     <h3 id="working-draft">7.3 Working Draft</h3>
   480     <h4>7.3.1 <a name="first-wd" id="first-wd">First Public Working Draft</a></h4>
   474     <p>A Public Working Draft is published on the W3C's Technical Reports page
   481     <p>To publish the First Public Working Draft of a document, in addition to
   475       [TR] for review, and for simple historical reference. For all Public
   482       meeting the <a href="#transition-reqs">general requirements for
   476       Working Drafts a Working Group</p>
   483         advancement</a> a Working Group</p>
       
   484     <ul>
   477     <ul>
   485       <li> <em class="rfc2119">should</em> document outstanding issues, and
   478       <li> <em class="rfc2119">should</em> document outstanding issues, and
   486         parts of the document on which the Working Group does not have
   479         parts of the document on which the Working Group does not have
   487         consensus, and</li>
   480         consensus, and</li>
   488       <li> <em class="rfc2119">may</em> request publication of a Working Draft
   481       <li> <em class="rfc2119">may</em> request publication of a Working Draft
   489         even if its content is considered unstable and does not meet all Working
   482         even if its content is considered unstable and does not meet all Working
   490         Group requirements.</li>
   483         Group requirements.</li>
   491     </ul>
   484     </ul>
       
   485     <h4 id="first-wd">7.3.1 First Public Working Draft</h4>
       
   486     <p>To publish the First Public Working Draft of a document, a Working Group
       
   487       must meet the <a href="#transition-reqs">general requirements for
       
   488         advancement</a>.</p>
   492     <p>The Director <em class="rfc2119">must</em> announce the publication of a
   489     <p>The Director <em class="rfc2119">must</em> announce the publication of a
   493       First Public Working Draft publication to other W3C groups and to the
   490       First Public Working Draft publication to other W3C groups and to the
   494       public. </p>
   491       public. </p>
   495     <p>Publishing the First Public Working Draft triggers a Call for Exclusions,
   492     <p>Publishing the First Public Working Draft triggers a Call for Exclusions,
   496       per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
   493       per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
   517       <li><em class="rfc2119">should</em> report which, if any, of the Working
   514       <li><em class="rfc2119">should</em> report which, if any, of the Working
   518         Group's requirements for this document have changed since the previous
   515         Group's requirements for this document have changed since the previous
   519         step,</li>
   516         step,</li>
   520       <li><em class="rfc2119">should</em> report any changes in dependencies
   517       <li><em class="rfc2119">should</em> report any changes in dependencies
   521         with other groups,</li>
   518         with other groups,</li>
   522       <li><em class="rfc2119">should</em> document outstanding issues and parts
       
   523         of the document on which the Working Group does not have consensus, and</li>
       
   524       <li><em class="rfc2119">may</em> request publication of a Working Draft
       
   525         even if its content is considered unstable and does not meet all Working
       
   526         Group requirements.</li>
       
   527     </ul>
   519     </ul>
   528     <p>Possible next steps:</p>
   520     <p>Possible next steps:</p>
   529     <ul>
   521     <ul>
   530       <li><a href="#hb-wd">Revised Public Working Draft</a></li>
   522       <li><a href="#hb-wd">Revised Public Working Draft</a></li>
   531       <li><a href="#last-call">Candidate recommendation</a>.</li>
   523       <li><a href="#last-call">Candidate recommendation</a>.</li>
   532       <li><a href="#tr-end">Working Group Note</a></li>
   524       <li><a href="#tr-end">Working Group Note</a></li>
   533     </ul>
   525     </ul>
   534     <h3>7.4 <a name="last-call" id="last-call">Candidate Recommendation </a></h3>
   526     <h3 id="candidate-rec"><a name="last-call" id="last-call">7.4 Candidate
       
   527         Recommendation </a></h3>
   535     <p>To publish a Candidate recommendation, in addition to meeting the <a href="#transition-reqs">general
   528     <p>To publish a Candidate recommendation, in addition to meeting the <a href="#transition-reqs">general
   536         requirements for advancement</a> a Working Group</p>
   529         requirements for advancement</a> a Working Group</p>
   537     <ul>
   530     <ul>
   538       <li><em class="rfc2119">must</em> show that the specification has met all
   531       <li><em class="rfc2119">must</em> show that the specification has met all
   539         Working Group requirements, or explain why the requirements have changed
   532         Working Group requirements, or explain why the requirements have changed
   541       <li><em class="rfc2119">must</em> document changes to dependencies during
   534       <li><em class="rfc2119">must</em> document changes to dependencies during
   542         the development of the specification,</li>
   535         the development of the specification,</li>
   543       <li><em class="rfc2119">must</em> document how adequate <a href="#implementation-experience">
   536       <li><em class="rfc2119">must</em> document how adequate <a href="#implementation-experience">
   544           implementation experience</a> will be demonstrated,</li>
   537           implementation experience</a> will be demonstrated,</li>
   545       <li><em class="rfc2119">must</em> specify the deadline for comments, which
   538       <li><em class="rfc2119">must</em> specify the deadline for comments, which
   546         <em class="rfc2119">must</em> be at least four weeks after publication,
   539         <em class="rfc2119">must</em> be <strong>at least</strong> four weeks
   547         and <em class="rfc2119">should</em> be longer for complex documents,</li>
   540         after publication, and <em class="rfc2119">should</em> be longer for
       
   541         complex documents,</li>
   548       <li>If the document has previously been published as a Candidate
   542       <li>If the document has previously been published as a Candidate
   549         Recommendation, <em class="rfc2119">must</em> document the changes
   543         Recommendation, <em class="rfc2119">must</em> document the changes
   550         since the previous Candidate Recommendation, </li>
   544         since the previous Candidate Recommendation, </li>
   551       <li><em class="rfc2119">must</em> show that the specification has received
   545       <li><em class="rfc2119">must</em> show that the specification has received
   552         <a href="#wide-review">wide review</a>, and</li>
   546         <a href="#wide-review">wide review</a>, and</li>
   580       repeat the full process of publication as a Candidate Recommendation
   574       repeat the full process of publication as a Candidate Recommendation
   581       before the Working Group can request Recommendation status.</p>
   575       before the Working Group can request Recommendation status.</p>
   582     <p> <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
   576     <p> <a href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
   583         Committee</a> representatives <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
   577         Committee</a> representatives <em class="rfc2119">may</em> <a href="http://www.w3.org/2005/10/Process-20051014/acreview.html#ACAppeal">appeal</a>
   584       the decision to advance the technical report.</p>
   578       the decision to advance the technical report.</p>
   585     <h4>7.4.1 Revised Candidate Recommendation</h4>
   579     <h4 id="revised-cr">7.4.1 Revised Candidate Recommendation</h4>
   586     <h3>7.5 <a name="rec-publication" id="rec-publication">W3C Recommendation</a></h3>
   580     <h3 id="rec-publication">7.5 W3C Recommendation</h3>
       
   581     <p class="issue">A better explanation of how a document becomes a
       
   582       Recommendation is needed here.</p>
   587     <h4 id="for-all-recs"><a id="rec-requirements">7.5.1 For <strong>all</strong>
   583     <h4 id="for-all-recs"><a id="rec-requirements">7.5.1 For <strong>all</strong>
   588         W3C Recommendations</a></h4>
   584         W3C Recommendations</a></h4>
   589     <p id="for-all-recs">In addition to meeting the <a href="#transition-reqs">general
   585     <p>In addition to meeting the <a href="#transition-reqs">general
   590         requirements for advancement</a>,</p>
   586         requirements for advancement</a>,</p>
   591     <ul>
   587     <ul>
   592       <li>The Director <em class="rfc2119">must</em> announce the provisional
   588       <li>The Director <em class="rfc2119">must</em> announce the provisional
   593         approval of a Request for publication of a W3C Recommendation to the <a
   589         approval of a Request for publication of a W3C Recommendation to the <a
   594           href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
   590           href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
   595           Committee</a>,</li>
   591           Committee</a>,</li>
   596       <li>The Advisory Committee review of the technical report <em class="rfc2119">must</em>
   592       <li>The deadline for Advisory Committee review of the technical report <em
   597         continue at least 28 days after the announcement of provisional approval
   593           class="rfc2119">must</em> be <strong>at least</strong> 28 days after
   598         to publish the Edited Recommendation as a W3C Recommendation,</li>
   594         the announcement of provisional approval to publish the Edited
       
   595         Recommendation as a W3C Recommendation,</li>
   599       <li>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
   596       <li>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
   600           rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
   597           rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
   601         in Advisory Committee reviews, the Director <em class="rfc2119">must</em>
   598         in Advisory Committee reviews, the Director <em class="rfc2119">must</em>
   602         publish the substantive content of the dissent to W3C and the general
   599         publish the substantive content of the dissent to W3C and the general
   603         public, and <em class="rfc2119">must</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
   600         public, and <em class="rfc2119">must</em> <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#formal-address">formally
   609         of a W3C Recommendation to other W3C groups and to the public, and</li>
   606         of a W3C Recommendation to other W3C groups and to the public, and</li>
   610       <li>The "Status of the Document" <em class="rfc2119">must</em> reflect
   607       <li>The "Status of the Document" <em class="rfc2119">must</em> reflect
   611         whether it is provisionally approved, or published as a W3C
   608         whether it is provisionally approved, or published as a W3C
   612         Recommendation.</li>
   609         Recommendation.</li>
   613     </ul>
   610     </ul>
   614     <h4><a name="lcrec-publication" id="lcrec-publication">7.5.2 Publishing a
   611     <h4 id="lcrec-publication">7.5.2 Publishing a Candidate Recommendation as a
   615         Candidate Recommendation as a W3C Recommendation</a></h4>
   612       W3C Recommendation</h4>
   616     <p>To publish a Candidate Recommendation as a W3C Recommendation, a Working
   613     <p>To publish a Candidate Recommendation as a W3C Recommendation, a Working
   617       Group</p>
   614       Group</p>
   618     <ul>
   615     <ul>
   619       <li><em class="rfc2119">must</em> republish the document, identifying it
   616       <li><em class="rfc2119">must</em> republish the document, identifying it
   620         as the basis of a Request for Recommendation,</li>
   617         as the basis of a Request for Recommendation,</li>
   654         it</li>
   651         it</li>
   655       <li><em class="rfc2119">may</em> be <a href="#rec-modify">republished as
   652       <li><em class="rfc2119">may</em> be <a href="#rec-modify">republished as
   656           an Edited Recommendation</a>, or</li>
   653           an Edited Recommendation</a>, or</li>
   657       <li><em class="rfc2119">may</em> be <a href="#rec-rescind">rescinded</a>.</li>
   654       <li><em class="rfc2119">may</em> be <a href="#rec-rescind">rescinded</a>.</li>
   658     </ul>
   655     </ul>
   659     <h3>7.6 <a name="rec-modify" id="rec-modify">Modifying a W3C Recommendation</a></h3>
   656     <h3 id="rec-modify">7.6 Modifying a W3C Recommendation</h3>
   660     <p>The following sections discuss the management of errors and the process
   657     <p>The following sections discuss the management of errors and the process
   661       for making changes to a Recommendation.</p>
   658       for making changes to a Recommendation.</p>
   662     <h4>7.6.1 <a name="errata" id="errata">Errata Management</a></h4>
   659     <h4 id="errata">7.6.1 Errata Management</h4>
   663     <p>Tracking errors is an important part of a Working Group's ongoing care of
   660     <p>Tracking errors is an important part of a Working Group's ongoing care of
   664       a Recommendation; for this reason, the scope of a Working Group charter
   661       a Recommendation; for this reason, the scope of a Working Group charter
   665       generally allows time for work after publication of a Recommendation. In
   662       generally allows time for work after publication of a Recommendation. In
   666       this Process Document, the term "erratum" (plural "errata") refers to any
   663       this Process Document, the term "erratum" (plural "errata") refers to any
   667       class of mistake, from mere editorial to a serious error that may affect
   664       class of mistake, from mere editorial to a serious error that may affect
   683       pages up-to-date, as errors are reported by readers and implementers. A
   680       pages up-to-date, as errors are reported by readers and implementers. A
   684       Working Group <span class="rfc2119">must</span> report errata page
   681       Working Group <span class="rfc2119">must</span> report errata page
   685       changes to interested parties, notably when corrections are proposed or
   682       changes to interested parties, notably when corrections are proposed or
   686       incorporated into an Edited Recommendation, according to the Team's
   683       incorporated into an Edited Recommendation, according to the Team's
   687       requirements.</p>
   684       requirements.</p>
   688     <h4>7.6.2 <a name="correction-classes" id="correction-classes">Classes of
   685     <h4 id="correction-classes">7.6.2 Classes of Changes to a Recommendation</h4>
   689         Changes to a Recommendation</a></h4>
       
   690     <p>This document distinguishes the following classes of changes to a
   686     <p>This document distinguishes the following classes of changes to a
   691       Recommendation.</p>
   687       Recommendation.</p>
   692     <dl>
   688     <dl>
   693       <dt>1. No changes to text content</dt>
   689       <dt>1. No changes to text content</dt>
   694       <dd>These changes include fixing broken links, style sheets or invalid
   690       <dd>These changes include fixing broken links, style sheets or invalid
   721     <p>For the third class of change, a Working Group <span class="rfc2119">must</span>
   717     <p>For the third class of change, a Working Group <span class="rfc2119">must</span>
   722       request publication of an <a href="#rec-edited">Edited Recommendation</a>.</p>
   718       request publication of an <a href="#rec-edited">Edited Recommendation</a>.</p>
   723     <p>For the fourth class of change, which introduces a new feature or
   719     <p>For the fourth class of change, which introduces a new feature or
   724       features, W3C <span class="rfc2119">must</span> follow the full process
   720       features, W3C <span class="rfc2119">must</span> follow the full process
   725       of <a href="#rec-advance">advancing a technical report to Recommendation</a>.</p>
   721       of <a href="#rec-advance">advancing a technical report to Recommendation</a>.</p>
   726     <h4>7.6.3 Revised Recommendation</h4>
   722     <h4 id="revised-rec">7.6.3 Revising a Recommendation</h4>
   727     <p>To publish an Edited Recommendation as a W3C Recommendation, in addition
   723     <p>To publish an Edited Recommendation as a W3C Recommendation, in addition
   728       to meeting the <a href="#rec-requirements">requirements for all W3C
   724       to meeting the <a href="#rec-requirements">requirements for all W3C
   729         Recommendations</a>, a Working Group</p>
   725         Recommendations</a>, a Working Group</p>
   730     <ul>
   726     <ul>
   731       <li><em class="rfc2119">must</em> republish the document, identifying it
   727       <li><em class="rfc2119">must</em> republish the document, identifying it
   732         as the basis of a Request for Recommendation,</li>
   728         as the basis of a Request for Recommendation,</li>
   733       <li><em class="rfc2119">must</em> show that the document has received <a
   729       <li><em class="rfc2119">must</em> show that the document has received <a
   734           href="#wide-review">wide review</a>, and </li>
   730           href="#wide-review">wide review</a>, and </li>
   735       <li><em class="rfc2119">should</em> address all errata.</li>
   731       <li><em class="rfc2119">should</em> address all errata.</li>
   736     </ul>
   732     </ul>
   737     <h3>7.7 <a name="tr-end" id="tr-end">Publishing a Working Group or Interest
   733     <h3 id="tr-end">7.7 Publishing a Working Group or Interest Group Note</h3>
   738         Group Note</a></h3>
       
   739     <p>Working Groups and Interest Groups publish material that is not a formal
   734     <p>Working Groups and Interest Groups publish material that is not a formal
   740       specification as Notes. This may include supporting documentation for a
   735       specification as Notes. This may include supporting documentation for a
   741       specification, such as requirements, use cases, good practices and the
   736       specification, such as requirements, use cases, good practices and the
   742       like.</p>
   737       like.</p>
   743     <p>Work on a technical report <em class="rfc2119">may</em> cease at any
   738     <p>Work on a technical report <em class="rfc2119">may</em> cease at any
   751       Working Group <em class="rfc2119">should</em> publish the document as a
   746       Working Group <em class="rfc2119">should</em> publish the document as a
   752       Working Group Note. </p>
   747       Working Group Note. </p>
   753     <p>In order to publish a Note a Working Group or Interest Group: </p>
   748     <p>In order to publish a Note a Working Group or Interest Group: </p>
   754     <ul>
   749     <ul>
   755       <li><em class="rfc2119">must</em> record the group's decision to request
   750       <li><em class="rfc2119">must</em> record the group's decision to request
   756         advancement, and</li>
   751         publication as a Note, and</li>
   757       <li><em class="rfc2119">should</em> public documentation of significant
   752       <li><em class="rfc2119">should</em> public documentation of significant
   758         changes to the technical report since the previous publication.</li>
   753         changes to the technical report since the previous publication.</li>
   759     </ul>
   754     </ul>
   760     <p>Possible next steps:</p>
   755     <p>Possible next steps:</p>
   761     <ul>
   756     <ul>
   763         Working Group Note indefinitely</li>
   758         Working Group Note indefinitely</li>
   764       <li>A Working Group <em class="rfc2119">may</em> resume work on the
   759       <li>A Working Group <em class="rfc2119">may</em> resume work on the
   765         technical report at any time, at the maturity level the specification
   760         technical report at any time, at the maturity level the specification
   766         had before publication as a Note</li>
   761         had before publication as a Note</li>
   767     </ul>
   762     </ul>
   768     <p>The W3C Patent Policy does not specify any licensing requirements or
   763     <p>The <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
   769       commitments for Working Group Notes, only for W3C Recommendations. See
   764         Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>]
   770       also the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
   765       does not specify any licensing requirements or commitments for Working
   771         Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>].</p>
   766       Group Notes, only for W3C Recommendations.</p>
   772     <h3>7.8 <a name="rec-rescind" id="rec-rescind">Rescinding a W3C
   767     <h3 id="rec-rescind">7.8 &gt;Rescinding a W3C Recommendation</h3>
   773         Recommendation</a></h3>
       
   774     <p>W3C <em class="rfc2119">may</em> rescind a Recommendation, for example
   768     <p>W3C <em class="rfc2119">may</em> rescind a Recommendation, for example
   775       if the Recommendation contains many errors that conflict with a later
   769       if the Recommendation contains many errors that conflict with a later
   776       version or if W3C discovers burdensome patent claims that affect
   770       version or if W3C discovers burdensome patent claims that affect
   777       implementers and cannot be resolved; see the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
   771       implementers and cannot be resolved; see the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
   778         Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>]
   772         Patent Policy</a> [<a href="http://www.w3.org/2005/10/Process-20051014/refs.html#ref-patentpolicy">PUB33</a>]
   780         5</a> (bullet 10) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section
   774         5</a> (bullet 10) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section
   781         7.5</a>. A Working Group <em class="rfc2119">may</em> request the
   775         7.5</a>. A Working Group <em class="rfc2119">may</em> request the
   782       Director to rescind a Recommendation which was a deliverable, or the
   776       Director to rescind a Recommendation which was a deliverable, or the
   783       Director <em class="rfc2119">may</em> directly propose to rescind a
   777       Director <em class="rfc2119">may</em> directly propose to rescind a
   784       Recommendation. </p>
   778       Recommendation. </p>
   785     <p>To deprecate <em>part</em> of a Recommendation, W3C follows the process
   779     <p>W3C only rescinds entire specifications. To rescind some <em>part</em>
   786       for <a href="#rec-modify">modifying a Recommendation</a>.</p>
   780       of a Recommendation, W3C follows the process for <a href="#rec-modify">modifying
       
   781         a Recommendation</a>.</p>
   787     <p>Once W3C has published a Rescinded Recommendation, future W3C technical
   782     <p>Once W3C has published a Rescinded Recommendation, future W3C technical
   788       reports <em class="rfc2119">must not</em> include normative references to
   783       reports <em class="rfc2119">must not</em> include normative references to
   789       that technical report.</p>
   784       that technical report.</p>
   790     <p>To propose rescinding a W3C Recommendation, a Working Group or the
   785     <p>To propose rescinding a W3C Recommendation, a Working Group or the
   791       Director</p>
   786       Director</p>
   792     <ul>
   787     <ul>
   793       <li><em class="rfc2119">must</em> publish rationale for rescinding the
   788       <li><em class="rfc2119">must</em> publish rationale for rescinding the
   794         Recommendation.</li>
   789         Recommendation.</li>
   795       <li><em class="rfc2119">should</em> document known implementation.</li>
   790       <li><em class="rfc2119">should</em> document known implementation.</li>
   796     </ul>
   791     </ul>
   797     <p>In addition a Working Group proposing to rescind</p>
   792     <p>In addition a Working Group requesting to rescind</p>
   798     <ul>
   793     <ul>
   799       <li><em class="rfc2119">must</em> show that the request to rescind has
   794       <li><em class="rfc2119">must</em> show that the request to rescind has
   800         received <a href="#wide-review">wide review</a></li>
   795         received <a href="#wide-review">wide review</a></li>
   801       <li><em class="rfc2119">should</em> show that the request to rescind is
   796       <li><em class="rfc2119">should</em> show that the request to rescind is
   802         based on public comment</li>
   797         based on public comment</li>
   811         href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
   806         href="http://www.w3.org/2005/10/Process-20051014/organization.html#AC">Advisory
   812         Committee</a>. The announcement <em class="rfc2119">must</em>:</p>
   807         Committee</a>. The announcement <em class="rfc2119">must</em>:</p>
   813     <ul>
   808     <ul>
   814       <li>indicate that this is a Proposal to Rescind a Recommendation</li>
   809       <li>indicate that this is a Proposal to Rescind a Recommendation</li>
   815       <li>specify the deadline for review comments, which <em class="rfc2119">must</em>
   810       <li>specify the deadline for review comments, which <em class="rfc2119">must</em>
   816         be at least <span class="time-interval">four weeks after publication </span></li>
   811         be at least <span class="time-interval">four weeks after announcing</span>
       
   812         the proposal to rescind.</li>
   817       <li>identify known dependencies and solicit review from all dependent
   813       <li>identify known dependencies and solicit review from all dependent
   818         Working Groups;</li>
   814         Working Groups;</li>
   819       <li>solicit public review.</li>
   815       <li>solicit public review.</li>
   820     </ul>
   816     </ul>
   821     <p>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"
   817     <p>If there was any <a href="http://www.w3.org/2005/10/Process-20051014/policies.html#def-Dissent"