changeset 223 da9a9cd4bdb6
parent 220 8d0fe573ea13
child 224 5fb97d1539fe
equal deleted inserted replaced
221:f6eb5b0520ce 223:da9a9cd4bdb6
     1 <!DOCTYPE html>
     1 <!DOCTYPE html>
     2 <html lang="en">
     2 <html lang="en">
     3   <head>
     3   <head>
     4     <meta charset="utf-8">
     4     <meta charset="utf-8">
     5     <meta name="keywords" content="W3C Process, Consortium, Team, Recommendation, Advisory Committee,
     5         <title>W3C Process Document Editor's Draft has moved</title>
     6 Advisory Board, Working Group, Coordination Group, Interest Group, W3C Activity, Workshop, charter, Working Draft, Process Document, Candidate Recommendation, Director, Proposed Recommendation, Submission request">
     7     <link rel="stylesheet" type="text/css" href="">
     8     <title>World Wide Web Consortium Process Document</title>
     9     <style type="text/css">
    10      .about { margin-left: 3em; margin-right: 3em; font-size: .83em}
    11      table { margin-left: auto; margin-right: auto }
    12      .diagram { text-align: center; margin: 2.5em 0 }
    13       .issue:before {content: "Issue: "}
    14       .issue {border: 2px dashed red; background-color: #ffa;}
    15       .issue .issue {background-color: #fcc;}
    16       .rfc2119 {font-variant:small-caps}
    18 /*for the SVG - navigation highlighting */
    20      :focus path, :focus polygon, :focus ellipse { stroke-width: 4}
    21      g g:hover path, g g:hover polygon, g g:hover ellipse { stroke-width: 4}
    22      :focus text, g g:hover text { stroke: black; stroke-width: .5}
    24 </style> <!--[if lt IE 9]><script src='undefined://'></script><![endif]-->
    25   </head>
     6   </head>
    26   <body>
     7   <body>
    27     <div class="head"><a href=""><img alt="W3C" src="" height="48" width="72"></a>
     8     <p><a href=""><img alt="W3C" src="" height="48" width="72"></a></p>
    28       <h1>W3C Editor's Draft Process Document</h1>
     9       <h1>The Editor's Draft of the W3C Process Document has moved</h1>
    29       <h2 class="notoc">24 December 2016 Editor's Draft</h2>
    10     <p>As of April 2017, following the adoption of the March 2017 version of the W3C Process</a>,
    30       <dl>
    11     the Editor's Drafts for updates to the W3C Process Document are now managed through a 
    31         <dt>Latest Editor's version:</dt>
    12   <a href="">W3C Process github repository</a>.</p>
    32          <dd><a href=""></a></dd>
    13   <p>Chaals McCathie Nevile, Editor, 12 July 2017</p>
    33         <dt>Latest operative version:</dt>
    34          <dd><a href=""></a></dd>
    35         <dt>Editor:</dt>
    36          <dd>Charles McCathie Nevile, <a style="color:black" href=""><span style="color: red;">Y</span>andex</a> —
    37            <a style="color:black" href=""><span style="color: red;">Я</span>ндекс</a></dd>
    38         <dt>Previous editor:</dt>
    39         <dd>Ian Jacobs, <a href="">W3C</a></dd>
    40       </dl>
    42       <p class="copyright"><a href="">Copyright</a> © 1996-2016
    43         <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
    44         (<a href=""><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
    45         <a href=""><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
    46         <a href="">Keio</a>, <a href="">Beihang</a>), All Rights Reserved. W3C
    47         <a href="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
    48         <a href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
    49         <a rel="Copyright" href="/Consortium/Legal/copyright-documents">document use</a> and
    50         <a rel="Copyright" href="/Consortium/Legal/copyright-software">software licensing</a> rules apply. Your interactions
    51         with this site are in accordance with our <a href="/Consortium/Legal/privacy-statement#Public">public</a> and
    52         <a href="/Consortium/Legal/privacy-statement#Members">Member</a> privacy statements.</p>
    54       <hr></div>
    56     <h2 class="notoc"><a id="abstract">Abstract</a></h2>
    58     <p>The mission of the World Wide Web Consortium (<abbr>W3C</abbr>) is to lead the World Wide Web to its full potential by
    59       developing common protocols that promote its evolution and ensure its interoperability. The W3C Process Document describes 
    60       the organizational structure of the W3C and the processes related to the responsibilities and functions they exercise to
    61       enable W3C to accomplish its mission. This document does not describe the internal workings of the Team or W3C's public 
    62       communication mechanisms.</p>
    64     <p>For more information about the W3C mission and the history of W3C, please refer to
    65       <a href="">About W3C</a> [<a href="#ref-mission">PUB15</a>].</p>
    67     <h2 class="notoc" id="status">Status of this Document</h2>
    69     <p>W3C, including all existing chartered groups, follows the
    70       <a href="">most recent operative Process Document</a> announced to the Membership.</p>
    72     <p>This document is developed by the Advisory Board's Process Task Force working within the
    73       <a href="">Revising W3C Process Community Group</a> (which anyone can join).
    74       This is the 15 October 2016 Editor's draft for the proposed next version of the W3C Process Document. This document is
    75       based on the <a href="">1 September 2015 Process Document</a>, which is the
    76       currently operative W3C Process.</p>
    78     <p>This draft has been approved by the Advisory Board to propose to the W3C director as the new operative Process document.
    79       This follows a formal review by W3C Advisory Committee Representatives. This revision incorporates minor editorial
    80       changes to the draft that was reviewed by the Advisory Committee.</p>
    82     <p>Further revision is expected to take place in a new version of the Process as required.</p>
    84     <p>A <a href="#changes">history of substantial changes</a> since the 1 September 2015 Process Document is provided. A log of
    85       <a href="">all changes in diff format</a> is available, as is an
    86       <a href="">"HTML diff-marked" comparison</a>
    87       to the 1 September document</a>.</p>
    89     <p>Comment is invited on the draft. Please send comments to
    90       <a href=""></a>
    91      (<a href="">Mailing list archive</a>, publicly available) or to
    92 (<a href="">Member-only archive</a>). A
    93      <a href="">Public Issue Tracker</a> is available online. </p>
    95     <h2 class="notoc" id="pp">Relation of Process Document to Patent Policy</h2>
    97     <p>W3C Members' attention is called to the fact that provisions of the Process Document are binding on Members per the
    98       <a href="">Membership Agreement</a>
    99       [<a href="#ref-member-agreement">PUB6</a>]. The Patent Policy
   100       <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]
   101       is incorporated by normative reference as a part of the Process Document, and is thus equally binding.</p>
   103     <p>The Patent Policy places additional obligations on Members, Team, and other participants in W3C.
   104       The Process Document does not restate those requirements but includes references to them.
   105       The Process Document and Patent Policy have been designed to allow them to evolve independently.</p>
   107     <p>In the Process Document, the term "participant" refers to an individual, not an organization.</p>
   109     <h2 class=".notoc">Conformance and specialized terms</h2>
   111     <p>The terms <em class="rfc2119">must</em>, <em class="rfc2119">must not</em>, <em class="rfc2119">should</em>,
   112       <em class="rfc2119">should not</em>, <em class="rfc2119">required</em>, and <em class="rfc2119">may</em> are used
   113       in accordance with <a href="">RFC 2119</a> [<a href="#ref-RFC2119">RFC2119</a>].
   114       The term <dfn><em class="rfc2119">not required</em></dfn> is equivalent to the term
   115       <em class="rfc2119">may</em> as defined in [<a href="#ref-RFC2119">RFC2119</a>].</p>
   117     <p>Some terms have been capitalized in this document (and in other W3C materials) to indicate that they are entities
   118       with special relevance to the W3C Process. These terms are defined within this document, and readers are reminded that the
   119       ordinary English definitions are insufficient for the purpose of understanding this document.</p>
   121     <div class="toc" role="navigation">
   122       <h2 class="notoc" id="toc">Table of Contents</h2>
   123       <div class="noprint">
   124         <ul class="toc">
   125           <li class="tocline2"><a href="#Intro" class="tocxref">1 Introduction</a></li>
   126           <li class="tocline2"><a href="#Organization" class="tocxref">2 Members, Advisory Committee, Team, Advisory Board, Technical
   127               Architecture Group</a></li>
   128           <li class="tocline2"><a href="#Policies" class="tocxref">3 General Policies for W3C Groups</a></li>
   129           <li class="tocline2"><a href="#dissemination" class="tocxref">4 Dissemination Policies</a></li>
   130           <li class="tocline2"><a href="#GAGeneral" class="tocxref">5 Working Groups and Interest Groups</a></li>
   131           <li class="tocline2"><a href="#Reports" class="tocxref">6 W3C Technical Report Development Process</a></li>
   132           <li class="tocline2"><a href="#ReviewAppeal" class="tocxref">7 Advisory Committee Reviews, Appeals, and Votes</a></li>
   133           <li class="tocline2"><a href="#GAEvents" class="tocxref">8 Workshops and Symposia</a></li>
   134           <li class="tocline2"><a href="#Liaisons" class="tocxref">9 Liaisons</a></li>
   135           <li class="tocline2"><a href="#Submission" class="tocxref">10 Member Submission Process</a></li>
   136           <li class="tocline2"><a href="#GAProcess" class="tocxref">11 Process Evolution</a></li>
   137           <li class="tocline2"><a href="#references" class="tocxref">12 References</a></li>
   138           <li class="tocline2"><a href="#acks" class="tocxref">13 Acknowledgments</a></li>
   139           <li class="tocline2"><a href="#changes" class="tocxref">14 Changes</a></li>
   140         </ul>
   141       </div>
   142     </div>
   143     <div class="longtoc">
   144       <div class="noprint">
   145         <h3 class="notoc" id="fulltoc">Expanded table of contents</h3>
   146       </div>
   147       <ul class="toc">
   148         <li class="tocline2"><a href="#Intro">1 Introduction</a></li>
   149         <li class="tocline2"><a href="#Organization">2 Members, Advisory Committee, Team, Advisory Board, Technical Architecture Group</a>
   150           <ul class="toc">
   151             <li class="tocline3"><a href="#Members">2.1 Members</a>
   152               <ul class="toc">
   153                 <li class="tocline4"><a href="#MemberBenefits">2.1.1 Rights of Members</a></li>
   154                 <li class="tocline4"><a href="#RelatedAndConsortiumMembers">2.1.2 Member Consortia, and Related Members</a></li>
   155                 <li class="tocline4"><a href="#AC">2.1.3 Advisory Committee (AC)</a></li>
   156               </ul>
   157             </li>
   158             <li class="tocline3"><a href="#Team">2.2 The W3C Team</a>
   159               <ul class="toc">
   160                 <li class="tocline4"><a href="#TeamSubmission">2.2.1 Team Submissions</a></li>
   161               </ul>
   162             </li>
   163             <li class="tocline3"><a href="#AB">2.3 Advisory Board (AB)</a>
   164               <ul class="toc">
   165                 <li class="tocline4"><a href="#ABParticipation">2.3.1 Advisory Board Participation</a></li>
   166               </ul>
   167             </li>
   168             <li class="tocline3"><a href="#TAG">2.4 Technical Architecture Group (TAG)</a>
   169               <ul class="toc">
   170                 <li class="tocline4"><a href="#tag-participation">2.4.1 Technical Architecture Group Participation</a></li>
   171               </ul>
   172             </li>
   173             <li class="tocline3"><a href="#AB-TAG-participation">2.5 Advisory Board and Technical Architecture Group Participation</a>
   174               <ul class="toc">
   175                 <li class="tocline4"><a href="#AB-TAG-constraints">2.5.1 Advisory Board and Technical Architecture Group Participation
   176                     Constraints</a></li>
   177                 <li class="tocline4"><a href="#AB-TAG-elections">2.5.2 Advisory Board and Technical Architecture Group Elections</a></li>
   178                 <li class="tocline4"><a href="#AB-TAG-vacated">2.5.3 Advisory Board and Technical Architecture Group Vacated Seats</a></li>
   179               </ul>
   180             </li>
   181           </ul>
   182         </li>
   183         <li class="tocline2"><a href="#Policies">3 General Policies for W3C Groups</a>
   184           <ul class="toc">
   185             <li class="tocline3"><a href="#ParticipationCriteria">3.1 Individual Participation Criteria</a>
   186               <ul class="toc">
   187                 <li class="tocline4"><a href="#coi">3.1.1 Conflict of Interest Policy</a></li>
   188                 <li class="tocline4"><a href="#member-rep">3.1.2 Individuals Representing a Member Organization</a></li>
   189               </ul>
   190             </li>
   191             <li class="tocline3"><a href="#GeneralMeetings">3.2 Meetings</a></li>
   192             <li class="tocline3"><a href="#Consensus">3.3 Consensus</a>
   193               <ul class="toc">
   194                 <li class="tocline4"><a href="#managing-dissent">3.3.1 Managing Dissent</a></li>
   195                 <li class="tocline4"><a href="#WGArchiveMinorityViews">3.3.2 Recording and Reporting Formal Objections</a></li>
   196                 <li class="tocline4"><a href="#formal-address">3.3.3 Formally Addressing an Issue</a></li>
   197                 <li class="tocline4"><a href="#WGChairReopen">3.3.4 Reopening a Decision When Presented With New Information</a></li>
   198               </ul>
   199             </li>
   200             <li class="tocline3"><a href="#Votes">3.4 Votes</a></li>
   201             <li class="tocline3"><a href="#WGAppeals">3.5 Appeal of a Chair's Decision</a></li>
   202             <li class="tocline3"><a href="#resignation">3.6 Resignation from a Group</a></li>
   203           </ul>
   204         </li>
   205         <li class="tocline2"><a href="#dissemination">4 Dissemination Policies</a>
   206           <ul class="toc">
   207             <li class="tocline3"><a href="#confidentiality-levels">4.1 Confidentiality Levels</a>
   208               <ul class="toc">
   209                 <li class="tocline4"><a href="#confidentiality-change">4.1.1 Changing Confidentiality Level</a></li>
   210               </ul>
   211             </li>
   212           </ul>
   213         </li>
   214         <li class="tocline2"><a href="#GAGeneral">5 Working Groups and Interest Groups</a>
   215           <ul class="toc">
   216             <li class="tocline3"><a href="#ReqsAllGroups">5.1 Requirements for All Working and Interest Groups</a></li>
   217             <li class="tocline3"><a href="#GroupsWG">5.2 Working Groups and Interest Groups</a>
   218               <ul class="toc">
   219                 <li class="tocline4"><a href="#group-participation">5.2.1 Working Group and Interest Group Participation Requirements</a></li>
   220                 <li class="tocline4"><a href="#WGCharterDevelopment">5.2.2 Working Group and Interest Group Charter Development</a></li>
   221                 <li class="tocline4"><a href="#CharterReview">5.2.3 Advisory Committee Review of a Working Group or Interest Group Charter</a></li>
   222                 <li class="tocline4"><a href="#cfp">5.2.4 Call for Participation in a Working Group or Interest Group</a></li>
   223                 <li class="tocline4"><a href="#charter-extension">5.2.5 Working Group and Interest Group Charter Extension</a></li>
   224                 <li class="tocline4"><a href="#WGCharter">5.2.6 Working Group and Interest Group Charters</a></li>
   225                 <li class="tocline4"><a href="#GeneralTermination">5.2.7 Working Group and Interest Group Closure</a></li>
   226               </ul>
   227             </li>
   228           </ul>
   229         </li>
   230         <li class="tocline2"><a href="#Reports">6 W3C Technical Report Development Process</a>
   231           <ul class="toc">
   232             <li><a href="#rec-advance">6.1 W3C Technical Reports</a>
   233               <ul class="toc">
   234                 <li><a href="#recs-and-notes" id="return-to-wg">6.1.1 Recommendations and Notes</a></li>
   235                 <li><a href="#maturity-levels">6.1.2 Maturity Levels</a></li>
   236               </ul>
   237             </li>
   238             <li><a href="#requirements-and-definitions">6.2 General requirements and definitions</a>
   239               <ul class="toc">
   240                 <li><a href="#general-requirements">6.2.1 General requirements for Technical Reports</a></li>
   241                 <li><a href="#transition-reqs">6.2.2 Advancement on the Recommendation Track</a>
   242                   <ul class="toc">
   243                     <li><a href="#substantive-change"> Substantive Change</a></li>
   244                   </ul>
   245                 </li>
   246                 <li><a href="#doc-reviews">6.2.3 Reviews and Review Responsibilities</a>
   247                   <ul class="toc">
   248                     <li><a href="#wide-review"> Wide Review</a></li>
   249                   </ul>
   250                 </li>
   251                 <li><a href="#implementation-experience">6.2.4 Implementation Experience</a> </li>
   252                 <li><a href="#correction-classes">6.2.5 Classes of Changes to a Recommendation</a></li>
   253               </ul>
   254             </li>
   255             <li><a href="#working-draft">6.3 Working Draft</a>
   256               <ul class="toc">
   257                 <li><a href="#first-wd">6.3.1 First Public Working Draft</a></li>
   258                 <li><a href="#revised-wd">6.3.2 Revising Public Working Drafts</a></li>
   259                 <li><a href="#tr-end">6.3.3 Stopping work on a specification</a></li>
   260               </ul>
   261             </li>
   262             <li><a href="#candidate-rec" id="cfi">6.4 Candidate Recommendation</a>
   263               <ul class="toc">
   264                 <li><a href="#revised-cr">6.4.1 Revising a Candidate Recommendation</a></li>
   265               </ul>
   266             </li>
   267             <li> <a href="#rec-pr" id="cfr">6.5 Proposed Recommendation</a></li>
   268             <li> <a href="#rec-publication">6.6 W3C Recommendation</a></li>
   269             <li><a href="#rec-modify">6.7 Modifying a W3C Recommendation</a>
   270               <ul class="toc">
   271                 <li><a href="#errata">6.7.1 Errata Management</a></li>
   272                 <li><a href="#revised-rec" id="cfr-edited">6.7.2 Revising a Recommendation</a></li>
   273               </ul>
   274             </li>
   275             <li><a href="#Note">6.8 Publishing a Working Group or Interest Group Note</a></li>
   276             <li><a href="#rec-rescind">6.9 Obsoleting or Rescinding a W3C Recommendation</a></li>
   277             <li><a href="#further-reading">6.10 Further reading</a></li>
   278           </ul>
   279         </li>
   280         <li class="tocline2"><a href="#ReviewAppeal">7 Advisory Committee Reviews, Appeals, and Votes</a>
   281           <ul class="toc">
   282             <li class="tocline3"><a href="#ACReview">7.1 Advisory Committee Reviews</a>
   283               <ul class="toc">
   284                 <li class="tocline4"><a href="#ACReviewStart">7.1.1 Start of a Review Period</a></li>
   285                 <li class="tocline4"><a href="#ACReviewAfter">7.1.2 After the Review Period</a></li>
   286               </ul>
   287             </li>
   288             <li class="tocline3"><a href="#ACAppeal">7.2 Appeal by Advisory Committee Representatives</a></li>
   289             <li class="tocline3"><a href="#ACVotes">7.3 Advisory Committee Votes</a></li>
   290           </ul>
   291         </li>
   292         <li class="tocline2"><a href="#GAEvents">8 Workshops and Symposia</a></li>
   293         <li class="tocline2"><a href="#Liaisons">9 Liaisons</a></li>
   294         <li class="tocline2"><a href="#Submission">10 Member Submission Process</a>
   295           <ul class="toc">
   296             <li class="tocline3"><a href="#SubmissionRights">10.1 Submitter Rights and Obligations</a>
   297               <ul class="toc">
   298                 <li class="tocline4"><a href="#SubmissionScope">10.1.1 Scope of Member Submissions</a></li>
   299                 <li class="tocline4"><a href="#SubmissionReqs">10.1.2 Information Required in a Submission Request</a></li>
   300               </ul>
   301             </li>
   302             <li class="tocline3"><a href="#TeamSubmissionRights">10.2 Team Rights and Obligations</a></li>
   303             <li class="tocline3"><a href="#SubmissionYes">10.3 Acknowledgment of a Submission Request</a></li>
   304             <li class="tocline3"><a href="#SubmissionNo">10.4 Rejection of a Submission Request</a></li>
   305           </ul>
   306         </li>
   307         <li class="tocline2"><a href="#GAProcess">11 Process Evolution</a></li>
   308         <li class="tocline2"><a href="#references">12 References</a>
   309           <ul class="toc">
   310             <li class="tocline3"><a href="#public-refs">12.1 Public Resources</a></li>
   311             <li class="tocline3"><a href="#member-refs">12.2 Member-only Resources</a></li>
   312             <li class="tocline3"><a href="#other-refs">12.3 Other References</a></li>
   313           </ul>
   314         </li>
   315         <li class="tocline2"><a href="#acks">13 Acknowledgments</a></li>
   316         <li class="tocline2"><a href="#changes">14 Changes</a></li>
   317       </ul>
   318     </div>
   320     <main>
   322       <h2 id="Intro">1 Introduction</h2>
   324       <p>Most W3C work revolves around the standardization of Web technologies. To accomplish this work, W3C follows processes that
   325         promote the development of high-quality standards based on the <a href="#Consensus">consensus</a> of the Membership, Team, 
   326         and public. W3C processes promote fairness, responsiveness, and progress: all facets of the W3C mission.
   327         This document describes the processes W3C follows in pursuit of its mission.</p>
   329       <p>Here is a general overview of how W3C standardizes a Web technology. In many cases, the goal of this work is a
   330         <a href="#RecsW3C">W3C Recommendation</a> - a Web standard.</p>
   332       <ol>
   333         <li>People generate interest in a particular topic. For instance, Members express interest in the form 
   334           of <a href="#Submission">Member Submissions</a>, and the <a href="#Team">Team</a> monitors work inside and outside of W3C
   335           for signs of interest. Also, W3C is likely to organize a <a href="#GAEvents">Workshop</a> to bring people together to 
   336           discuss topics that interest the W3C community.</li>
   337         <li>When there is enough interest in a topic (e.g., after a successful Workshop and/or discussion on an
   338           <a href="#ACCommunication">Advisory Committee mailing list</a>), the Director announces the development of a proposal for
   339           one or more new <a href="#WGCharterDevelopment">Interest Group or Working Group charters</a>, depending on the breadth of
   340           the topic of interest. W3C Members <a href="#CharterReview">review</a> the proposed charters. When there is support
   341           within W3C for investing resources in the topic of interest, the Director approves the group(s) and they begin their
   342           work.</li>
   343         <li>There are three types of Working Group participants: <a href="#member-rep">Member representatives</a>,
   344           <a href="#invited-expert-wg">Invited Experts</a>, and <a href="#Team">Team representatives</a>. Team representatives both
   345           contribute to the technical work and help ensure the group's proper integration with the rest of W3C. The
   346           <a href="#WGCharter">Working Group charter</a> sets expectations about each group's deliverables (e.g.,
   347           <a href="#Reports">technical reports</a>, test suites, and tutorials).</li>
   348         <li>Working Groups generally create specifications and guidelines that undergo cycles of revision and review as they
   349           <a href="#rec-advance">advance to W3C Recommendation</a> status. The W3C process for producing these technical reports
   350           includes significant review by the Members and public, and requirements that the Working Group be able to show 
   351           implementation and interoperability experience. At the end of the process, the Advisory Committee reviews the mature
   352           technical report, and if there is support, W3C publishes it as a <a href="#RecsW3C">Recommendation</a>.</li>
   353       </ol>
   355       <p>The Process Document promotes the goals of quality and fairness in technical decisions by encouraging
   356         <a href="#Consensus">consensus</a>, requiring reviews (by both Members and public) as part of the
   357         <a href="#Reports">technical report development process</a>, and through an
   358         <a href="#ACAppeal">Advisory Committee Appeal process</a>.</p>
   360       <p>The other sections of the Process Document:</p>
   361       <ol>
   362         <li>set forth <a href="#Policies">policies</a> for participation in W3C groups,</li>
   363         <li>establish two permanent groups within W3C: the <a href="#TAG">Technical Architecture Group (TAG)</a>, to help resolve
   364           Consortium-wide technical issues; and the <a href="#AB">Advisory Board (AB)</a>, to help resolve
   365           Consortium-wide non-technical issues, and to manage the <a href="#GAProcess">evolution of the W3C process</a>, and</li>
   366         <li>describe other interactions between the <a href="#Members">Members</a> (as represented by the
   367           <a href="#AC">W3C Advisory Committee</a>), the Team, and the general public.</li>
   368       </ol>
   370       <h2 id="Organization">2 Members, Advisory Committee, Team, Advisory Board, Technical Architecture Group</h2>
   372       <p>W3C's mission is to lead the Web to its full potential. W3C <a href="#Members">Member</a> organizations
   373         provide resources to this end, and the W3C <a href="#Team">Team</a> provides the technical leadership
   374         and organization to coordinate the effort.</p>
   376       <h3 id="Members">2.1 Members</h3>
   378       <p>W3C Members are primarily represented in W3C processes as follows:</p>
   380       <ol>
   381         <li>The <a href="#AC">Advisory Committee</a> is composed of one representative from each Member organization (refer to the
   382           <a href="#Member-only">Member-only</a> list of
   383           <a href="">current Advisory Committee representatives</a>
   384           [<a href="#ref-current-ac">MEM1</a>]).
   385           The Advisory Committee:
   386           <ul>
   387             <li>reviews plans for W3C at each <a href="#ACMeetings">Advisory Committee meeting</a>;</li>
   388             <li>reviews formal proposals from the W3C Director: <a href="#CharterReview">Charter Proposals</a>,
   389             <a href="#RecsPR">Proposed Recommendations</a>, and <a href="#GAProcess">Proposed Process Documents</a>.</li>
   390             <li>elects the <a href="#AB">Advisory Board</a> participants other than the Advisory Board Chair.</li>
   391             <li>elects 5 of the 9 participants on the <a href="#TAG">Technical Architecture Group</a>.</li>
   392           </ul>
   394           Advisory Committee representatives <em class="rfc2119">may</em> initiate an 
   395           <a href="#ACAppeal">Advisory Committee Appeal</a> in some cases described in this document.</li>
   397         <li>Representatives of Member organizations participate in <a href="#GAGeneral">Working Groups and Interest Groups</a> and
   398           author and review <a href="#Reports">technical reports</a>.</li>
   399       </ol>
   401       <p id="MemberSubscription">W3C membership is open to all entities, as described in
   402         "<a href="">How to Join W3C</a>" [<a href="#ref-join-w3c">PUB5</a>];
   403         (refer to the public list of <a href="">current W3C Members</a>
   404         [<a href="#ref-current-mem">PUB8</a>]). Organizations subscribe according to the
   405         <a href="">Membership Agreement</a>
   406         [<a href="#ref-member-agreement">PUB6</a>]. The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure that
   407         Member participation agreements remain <a href="#Team-only">Team-only</a> and that no Member receives
   408         preferential treatment within W3C.</p>
   410       <p id="IndividualParticipation">W3C does not have a class of membership tailored to, or priced for individuals.
   411         However, an individual <em class="rfc2119">may</em> join W3C as an Affiliate Member. In this case the same
   412         restrictions pertaining to <a href="#MemberRelated">related Members</a> apply when the individual also
   413         <a href="#member-rep">represents</a> another W3C Member.</p>
   415       <h4 id="MemberBenefits">2.1.1 Rights of Members</h4>
   417       <p>Each Member organization enjoys the following rights and benefits:</p>
   419       <ul>
   420         <li>A seat on the <a href="#AC">Advisory Committee</a>;</li>
   421         <li>Access to <a href="#Member-only">Member-only</a> information;</li>
   422         <li>The <a href="#Submission">Member Submission</a> process;</li>
   423         <li>Use of the W3C Member logo on promotional material and to publicize the Member's participation in W3C. For more
   424           information, please refer to the Member logo usage policy described in the
   425           <a href="">New Member Orientation</a> [<a href="#ref-new-member">MEM4</a>].</li>
   426       </ul>
   428       <p>Furthermore,  subject to further restrictions included in the Member Agreement, representatives of Member organizations
   429         participate in W3C as follows:</p>
   431       <ul>
   432         <li>In <a href="#GAGeneral">Working Groups and Interest Groups</a>.</li>
   433         <li>In <a href="#GAEvents">Workshops and Symposia</a>;</li>
   434         <li>On the Team, as <a href="#fellows">W3C Fellows</a>.</li>
   435       </ul>
   437       <p>The rights and benefits of W3C membership are contingent upon conformance to the processes described in this document.
   438         The vast majority of W3C Members faithfully follow the spirit as well as the letter of these processes. When
   439         serious and/or repeated violations do occur, and repeated attempts to address these violations have not
   440         resolved the situation, the  Director <em class="rfc2119">may</em> take disciplinary action.
   441         Arbitration in the case of further disagreement is governed by paragraph 19 of the Membership Agreement. Refer to the
   442         <a href="">Guidelines for Disciplinary Action</a>
   443         [<a href="#ref-discipline-gl">MEM14</a>].</p>
   445       <h4 id="RelatedAndConsortiumMembers">2.1.2 Membership Consortia and related Members</h4>
   447       <h5 id="MemberConsortia"> Membership Consortia</h5>
   449       <p>A "Member Consortium" means a consortium, user society, or association of two or more individuals, companies,
   450         organizations or governments, or any combination of these entities which has the purpose of participating in a
   451         common activity or pooling resources to achieve a common goal other than participation in, or achieving certain goals in,
   452         W3C. A joint-stock corporation or similar entity is not a "Member Consortium" merely because it has shareholders or
   453         stockholders.  If it is not clear whether a prospective Member qualifies as a Member Consortium, the Director may
   454         reasonably make the determination. For a Member Consortium, the rights and privileges of W3C Membership described in the
   455         W3C Process Document extend to the Member Consortium's paid staff and Advisory Committee representative.</p>
   457       <p>Member Consortia <em class="rfc2119">may</em> also designate up to four (or more at the Team's discretion) individuals
   458         who, though not employed by the organization, <em class="rfc2119">may</em> exercise the rights of
   459         <a href="#member-rep">Member representatives</a>.
   461       <p>For Member Consortia that have individual people as members these individuals <em class="rfc2119">must</em> disclose
   462         their employment affiliation when participating in W3C work. Provisions for <a href="#MemberRelated">related Members</a>
   463         apply. Furthermore, these individuals <em class="rfc2119">must</em> represent the broad interests of the
   464         W3C Member organization and not the particular interests of their employers.</p>
   466       <p>For Member Consortia that have organizations as Members, all such designated representatives
   467         <em class="rfc2119">must</em> be an official representative of the Member organization
   468         (e.g. a Committee or Task Force Chairperson) and <em class="rfc2119">must</em> disclose their employment affiliation
   469         when participating in W3C work. Provisions for <a href="#MemberRelated">related Members</a> apply. 
   470         Furthermore, these individuals <em class="rfc2119">must</em> represent the broad interests of the W3C Member organization
   471         and not the particular interests of their employers.</p>
   473       <p>For all representatives of a Member Consortium, IPR commitments are made on behalf of the Member Consortium, unless a
   474         further IPR commitment is made by the individuals' employers.</p>
   476       <h5 id="MemberRelated"> Related Members</h5>
   478       <p>In the interest of ensuring the integrity of the consensus process, Member involvement in some of the processes in this
   479         document is affected by related Member status. As used herein, two Members are related if:</p>
   480       <ol>
   481         <li>Either Member is a subsidiary of the other, or</li>
   482         <li>Both Members are subsidiaries of a common entity, or</li>
   483         <li>The Members have an employment contract or consulting contract that affects W3C participation.</li>
   484       </ol>
   485       <p>A <em>subsidiary</em> is an organization of which effective control and/or majority ownership rests with another, single
   486         organization.</p>
   487       <p>Related Members <em class="rfc2119">must</em> disclose these relationships according to the mechanisms described in the
   488         <a href="">New Member Orientation</a> [<a href="#ref-new-member">MEM4</a>].</p>
   490       <h4 id="AC">2.1.3 Advisory Committee (AC)</h4>
   492       <p>When an organization joins W3C (see "<a href="">How to Join W3C</a>"
   493         [<a href="#ref-join-w3c">PUB5</a>]), it <em class="rfc2119">must</em> name its Advisory Committee representative as part
   494         of the Membership Agreement. The <a href="">New Member Orientation</a> explains how to
   495         subscribe or unsubscribe to Advisory Committee mailing lists, provides information about Advisory Committee Meetings,
   496         explains how to name a new Advisory Committee representative, and more. Advisory Committee representatives
   497         <em class="rfc2119">must</em> follow the <a href="#coi">conflict of interest policy</a> by disclosing information
   498         according to the mechanisms described in the New Member Orientation. See also the additional roles of
   499         Advisory Committee representatives described in the
   500         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
   501       <p>Additional information for Members is available at the <a href="">Member Web site</a>
   502        [<a href="#ref-member-web">MEM6</a>].</p>
   504       <h5 id="ACCommunication"> Advisory Committee Mailing Lists</h5>
   505       <p>The Team <em class="rfc2119">must</em> provide two mailing lists for use by the Advisory Committee:</p>
   506       <ol>
   507         <li>One for official announcements (e.g., those required by this document) from the Team to the Advisory Committee.
   508           This list is read-only for Advisory Committee representatives.</li>
   509         <li>One for discussion among Advisory Committee representatives. Though this list is primarily for Advisory Committee
   510           representatives, the Team <em class="rfc2119">must</em> monitor discussion and <em class="rfc2119">should</em>
   511           participate in discussion when appropriate. Ongoing detailed discussions <em class="rfc2119">should</em> be moved
   512           to other appropriate lists (new or existing, such as a mailing list created for a <a href="#GAEvents">Workshop</a>).</li>
   513       </ol>
   514       <p>An Advisory Committee representative <em class="rfc2119">may</em> request that additional individuals from their
   515         organization be subscribed to these lists. Failure to contain distribution internally <em class="rfc2119">may</em>
   516         result in suspension of additional email addresses, at the discretion of the Team.</p>
   518       <h5 id="ACMeetings"> Advisory Committee Meetings</h5>
   519       <p>The Team organizes a <a href="#ftf-meeting">face-to-face meeting</a> for the Advisory Committee 
   520         <span class="time-interval">twice a year</span>. The Team appoints the Chair of these meetings (generally the CEO).
   521         At each Advisory Committee meeting, the Team <em class="rfc2119">should</em> provide an update to the
   522         Advisory Committee about:</p>
   523       <dl>
   524         <dt><em>Resources</em></dt>
   525         <dd>
   526           <ul>
   527             <li>The number of W3C Members at each level.</li>
   528             <li>An overview of the financial status of W3C.</li>
   529           </ul>
   530         </dd>
   531         <dt><em>Allocations</em></dt>
   532         <dd>
   533           <ul>
   534             <li>The allocation of the annual budget, including size of the Team and their approximate deployment.</li>
   535             <li>A list of all activities (including but not limited to Working and Interest Groups) and brief status statement
   536               about each, in particular those started or terminated since the previous Advisory Committee meeting.</li>
   537             <li>The allocation of resources to pursuing <a href="#Liaisons">liaisons</a> with other organizations.</li>
   538           </ul>
   539         </dd>
   540       </dl>
   541       <p>Each Member organization <em class="rfc2119">should</em> send one <a href="#member-rep">representative</a> to each
   542         Advisory Committee Meeting. In exceptional circumstances (e.g., during a period of transition between representatives
   543         from an organization),
   544         the meeting Chair <em class="rfc2119">may</em> allow a Member organization to send two representatives to a meeting.</p>
   545       <p>The Team <em class="rfc2119">must</em> announce the date and location of each Advisory Committee meeting no later than
   546         at the end of the previous meeting; <span class="time-interval">one year's</span> notice is preferred. The Team
   547         <em class="rfc2119">must</em>
   548         announce the region of each Advisory Committee meeting at least <span class="time-interval">one year</span> in advance.</p>
   549       <p>More information about <a href="">Advisory Committee meetings</a>
   550         [<a href="#ref-ac-meetings">MEM5</a>] is available at the Member Web site.</p>
   552       <h3 id="Team">2.2 The W3C Team</h3>
   554       <p>The Team consists of the Director, CEO, W3C paid staff, unpaid interns, and W3C Fellows.
   555         <dfn id="fellows">W3C Fellows</dfn> are Member employees working as part of the Team; see the
   556         <a href="">W3C Fellows Program</a> [<a href="#ref-fellows">PUB32</a>].
   557         The Team provides technical leadership about Web technologies, organizes and manages W3C activities to reach goals within
   558         practical constraints (such as resources available), and communicates with the Members and the public about 
   559         the Web and W3C technologies.</p>
   560       <p>The Director and CEO <em class="rfc2119">may</em> delegate responsibility (generally to other individuals in the Team)
   561         for any of their roles described in this document.</p>
   563       <p>The <dfn id="def-Director">Director</dfn> is the lead technical architect at W3C. His responsibilities are identified
   564         throughout this document in relevant places. Some key ones include: assessing
   565         <a href="#def-Consensus" id="DirectorDecision">consensus</a> within W3C for architectural choices, publication of
   566         <a href="#Reports">technical reports</a>, and chartering new Groups; appointing group <a href="#GeneralChairs">Chairs</a>;
   567         adjudicating as "tie-breaker" for <a href="#WGAppeals">Group decision appeals</a> and deciding on the outcome of formal
   568         objections; the Director is generally Chair of the <a href="#TAG">TAG</a>.</p>
   570       <p>Team administrative information such as Team salaries, detailed budgeting, and other business decisions are
   571         <a href="#Team-only">Team-only</a>, subject to oversight by the Host institutions.</p>
   572       <p><strong>Note:</strong> W3C is not currently incorporated. For legal contracts, W3C is represented by four
   573         <dfn id="hosts">"Host" institutions</dfn>: Beihang University,
   574         the European Research Consortium for Informatics and Mathematics (<abbr>ERCIM</abbr>),
   575         Keio University, and the Massachusetts Institute of Technology (<abbr>MIT</abbr>). Within W3C, the Host institutions are
   576         governed by hosting agreements; the Hosts themselves are not W3C Members.</p>
   578       <h4 id="TeamSubmission">2.2.1 Team Submissions</h4>
   580       <p>Team members <em class="rfc2119">may</em> request that the Director publish information at the W3C Web site.
   581         At the Director's discretion, these documents are published as "Team Submissions". These documents are analogous to
   582         <a href="#Submission">Member Submissions</a> (e.g., in <a href="#SubmissionScope">expected scope</a>). However, there is
   583         no additional Team comment. The <a href="#DocumentStatus">document status section</a> of a Team Submission indicates
   584         the level of Team consensus about the published material.</p>
   585       <p>Team Submissions are <strong>not</strong> part of the <a href="#Reports">technical report development process</a>.</p>
   586       <p>The list of <a href="">published Team Submissions</a>
   587         [<a href="#ref-team-submission-list">PUB16</a>] is available at the W3C Web site.</p>
   589       <h3 id="AB">2.3 Advisory Board (AB)</h3>
   591       <p>Created in March 1998, the Advisory Board provides ongoing guidance to the Team on issues of strategy, management,
   592         legal matters, process, and conflict resolution. The Advisory Board also serves the Members by tracking issues raised
   593         between Advisory Committee meetings, soliciting Member comments on such issues, and proposing actions to resolve these 
   594         issues. The Advisory Board manages the <a href="#GAProcess">evolution of the Process Document</a>. The Advisory Board hears
   595         a <a href="#SubmissionNo">Submission Appeal</a> when a Member Submission is rejected for reasons unrelated to Web
   596         architecture; see also the <a href="#TAG">TAG</a>.</p>
   598       <p>The Advisory Board is <strong>not</strong> a board of directors and has no decision-making authority within W3C;
   599         its role is strictly advisory.</p>
   601       <p>The Team <em class="rfc2119">must</em> make available a mailing list for the Advisory Board to use for its 
   602         communication,confidential to the Advisory Board and Team.</p>
   604       <p>The Advisory Board <em class="rfc2119">should</em> send a summary of each of its meetings to the Advisory Committee
   605         and other group Chairs. The Advisory Board <em class="rfc2119">should</em> also report on its activities at each
   606         <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
   608       <p>Details about the Advisory Board (e.g., the list of Advisory Board participants, mailing list information, and
   609         summaries of Advisory Board meetings) are available at the 
   610         <a href="">Advisory Board home page</a> [<a href="#ref-ab-home">PUB30</a>].</p>
   612       <h4 id="ABParticipation">2.3.1 Advisory Board Participation</h4>
   614       <p>The Advisory Board consists of nine elected participants and a Chair. The Team appoints the Chair of the
   615         <a href="#AB">Advisory Board</a>, who is generally the CEO.</p>
   617       <p>The remaining nine Advisory Board participants are elected by the W3C Advisory Committee following the
   618         <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.</p>
   620       <p>With the exception of the Chair, the terms of all Advisory Board participants are for
   621         <span class="time-interval">two years</span>. Terms are staggered so that each year, either four or five terms expire.
   622         If an individual is elected to fill an incomplete term, that individual's term ends at the normal expiration date of
   623         that term. Regular Advisory Board terms begin on 1 July and end on 30 June.</p>
   625       <h3 id="TAG">2.4 Technical Architecture Group (TAG)</h3>
   627       <p>Created in February 2001, the mission of the TAG is stewardship of the Web architecture. There are three aspects to
   628         this mission:</p>
   629       <ol>
   630         <li>to document and build consensus around principles of Web architecture and to interpret and clarify these
   631           principles when necessary;</li>
   632         <li>to resolve issues involving general Web architecture brought to the TAG;</li>
   633         <li>to help coordinate cross-technology architecture developments inside and outside W3C.</li>
   634       </ol>
   636       <p>The TAG hears a <a href="#SubmissionNo">Submission Appeal</a> when a Member Submission is rejected for reasons related
   637         to Web architecture; see also the <a href="#AB">Advisory Board</a>.</p>
   639       <p>The TAG's scope is limited to technical issues about Web architecture. The TAG <em class="rfc2119">should not</em>
   640         consider administrative, process, or organizational policy issues of W3C, which are generally addressed by the
   641         W3C Advisory Committee, Advisory Board, and Team. Please refer to the
   642         <a href="">TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
   643         for more information about the background and scope of the TAG, and the expected qualifications of TAG participants.</p>
   645       <p>The Team <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
   647       <ul>
   648         <li>a public discussion (not just input) list for issues of Web architecture. The TAG will conduct its public business
   649           on this list.</li>
   650         <li>a <a href="#Member-only">Member-only</a> list for discussions within the TAG and for requests to the TAG that,
   651           for whatever reason, cannot be made on the public list.</li>
   652       </ul>
   654       <p>The TAG <em class="rfc2119">may</em> also request the creation of additional topic-specific, public mailing lists.
   655         For some TAG discussions (e.g.,  a <a href="#SubmissionNo">Submission Appeal</a>), the TAG <em class="rfc2119">may</em>
   656         use a list that will be <a href="#Member-only">Member-only</a>.</p>
   658       <p>The TAG <em class="rfc2119">should</em> send a summary of each of its <a href="#GeneralMeetings">meetings</a> to the
   659         Advisory Committee and other group Chairs. The TAG <em class="rfc2119">should</em> also report on its activities at each
   660         <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
   662       <p>When the TAG votes to resolve an issue, each TAG participant (whether appointed, elected, or the Chair) has one vote;
   663         see also the section on <a href="">voting in the TAG charter</a>
   664        [<a href="#ref-tag-charter">PUB25</a>] and the general section on <a href="#Votes">votes</a> in this Process Document.</p>
   666       <p>Details about the TAG (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings)
   667         are available at the <a href="">TAG home page</a> [<a href="#ref-tag-home">PUB26</a>].</p>
   669       <h4 id="tag-participation">2.4.1 Technical Architecture Group Participation</h4>
   671       <p>The TAG consists of eight elected or appointed participants and a Chair. The Team appoints the Chair of the TAG,
   672         who is generally the <a href="#def-Director">Director</a>.</p>
   674       <p>Three TAG participants are appointed by the Director. Appointees are <em class="rfc2119">not required</em> to be
   675         on the W3C Team. The Director <em class="rfc2119">may</em> appoint <a href="#fellows">W3C Fellows</a> to the TAG.</p>
   677       <p>The remaining five TAG participants are elected by the W3C Advisory Committee following the
   678         <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.</p>
   680       <p>With the exception of the Chair, the terms of all TAG participants are for <span class="time-interval">two years</span>.
   681         Terms are staggered so that each year, either two or three elected terms, and either one or two appointed terms expire.
   682         If an individual is appointed or elected to fill an incomplete term, that individual's term ends at the normal
   683         expiration date of that term. Regular TAG terms begin on 1 February and end on 31 January.</p>
   685       <h3 id="AB-TAG-participation">2.5 Advisory Board and Technical Architecture Group Participation</h3>
   687       <p>Advisory Board and TAG participants have a special role within W3C: they are elected by the Membership and
   688         appointed by the Director with the expectation that they will use their best judgment to find the best solutions
   689         for the Web, not just for any particular network, technology, vendor, or user. Advisory Board and TAG participants
   690         are expected to participate regularly and fully. Advisory Board and TAG participants <em class="rfc2119">should</em>
   691         attend <a href="#ACMeetings">Advisory Committee meetings</a>.</p>
   693       <p>An individual participates on the Advisory Board or TAG from the moment the individual's term begins until the term ends
   694         or the seat is <a href="#AB-TAG-vacated">vacated</a>. Although Advisory Board and TAG participants do not advocate for
   695         the commercial interests of their employers, their participation does carry the responsibilities associated with
   696         Member representation, Invited Expert status, or Team representation (as described in the section on the
   697         <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>). See also the licensing obligations on
   698         TAG participants in <a href="">section 3</a> of the
   699         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
   700         and the claim exclusion process of <a href="">section 4</a>.</p>
   702       <h4 id="AB-TAG-constraints">2.5.1 Advisory Board and Technical Architecture Group Participation Constraints</h4>
   704       <p>Given the few seats available on the Advisory Board and the TAG, and in order to ensure that the diversity of
   705         W3C Members is represented:</p>
   707       <ul>
   708         <li>A Member organization is permitted at most one participant on the TAG except when having more than one participant
   709           is caused by a change of affiliation of an existing participant. At the completion of the next regularly scheduled
   710           election for the TAG, the Member organization <em class="rfc2119">must</em> have returned to having at most
   711           one participant.</li>
   712         <li>A Member organization is permitted at most one participant on the AB.</li>
   713         <li>An individual <em class="rfc2119">must not</em> participate on both the TAG and the AB.</li>
   714       </ul>
   716       <p>If, for whatever reason, these constraints are not satisfied (e.g., because an AB participant changes jobs),
   717         one participant <em class="rfc2119">must</em> cease AB participation until the situation has been resolved. If after
   718         <span class="time-interval">30 days</span> the situation has not been resolved, the Chair will declare one participant's
   719         seat to be vacant. When more than one individual is involved, the
   720         <a href="#random">verifiable random selection procedure</a> described below will be used to choose one person for
   721         continued participation.</p>
   723       <h4 id="AB-TAG-elections">2.5.2 Advisory Board and Technical Architecture Group Elections</h4>
   725       <p>The Advisory Board and a portion of the Technical Architecture Group are elected by the Advisory Committee, using a
   726         Single Transferable Vote system. An election begins when the Team sends a Call for Nominations to the Advisory Committee.
   727         Any Call for Nominations specifies the number of available seats, the deadline for nominations, details about the
   728         specific vote tabulation system selected by the Team for the election, and operational information such as how to
   729         nominate a candidate. The Team 
   730         <em class="rfc2119">may</em> modify the  tabulation system after the Call for Nominations but
   731         <em class="rfc2119">must</em> stabilize it no later than the Call for Votes. The Director <em class="rfc2119">should</em>
   732         announce appointments no later than the start of a nomination period as part of the Call for Nominations.</p>
   734       <p>Each Member (or group of <a href="#MemberRelated">related Members</a>) <em class="rfc2119">may</em> nominate one 
   735         individual. A nomination <em class="rfc2119">must</em> be made with the consent of the nominee. In order for
   736         an individual to be nominated as a Member representative, the individual <em class="rfc2119">must</em> qualify for 
   737         <a href="#member-rep">Member representation</a> and the Member's Advisory Committee representative
   738         <em class="rfc2119">must</em> include in the nomination the (same)
   739         <a href="#member-rep-info">information required for a Member representative in a Working Group</a>. In order for an
   740         individual to be nominated as an Invited Expert, the individual <em class="rfc2119">must</em> provide the (same)
   741         <a href="#inv-expert-info">information required for an Invited Expert in a Working Group</a> and the nominating
   742         Advisory Committee representative <em class="rfc2119">must</em> include that information in the nomination. 
   743         In order for an individual to be nominated as a Team representative, the nominating Advisory Committee representative
   744         <em class="rfc2119">must</em> first secure approval from Team management. A nominee is
   745         <em class="rfc2119">not required</em> to be an employee of a Member organization, and <em class="rfc2119">may</em> be a
   746         <a href="#fellows">W3C Fellow</a>. Each nomination <em class="rfc2119">should</em> include a few informative paragraphs
   747         about the nominee.</p>
   749       <p>If, after the deadline for nominations, the number of nominees is:</p>
   751       <ul>
   752         <li>Equal to the number of available seats, those nominees are thereby elected. This situation constitutes a tie for the
   753           purposes of assigning <a href="#short-term">short terms</a>.</li>
   754         <li>Less than the number of available seats, Calls for Nominations are issued until a sufficient number of people
   755           have been nominated. Those already nominated do not need to be renominated after a renewed call.</li>
   756         <li>Greater than the number of available seats, the Team issues a Call for Votes that includes the names of
   757           all candidates, the number of available seats, the deadline for votes, details about the vote tabulation system
   758           selected by the Team for the election, and operational information.</li>
   759       </ul>
   761       <p>When there is a vote, each Member (or group of <a href="#MemberRelated">related Members</a>)
   762         <em class="rfc2119">may</em> submit one ballot that ranks candidates in the Member's preferred order. Once the deadline
   763         for votes has passed, the Team announces the results to the Advisory Committee. In case of a tie the
   764         <a href="#random">verifiable random selection procedure</a> described below will be used to fill the available seats.</p>
   766       <p id="short-term">The shortest term is assigned to the elected candidate ranked lowest by the tabulation of votes, the
   767         next shortest term to the next-lowest ranked elected candidate, and so on. In the case of a tie among those eligible for
   768         a short term, the <a href="#random">verifiable random selection procedure</a> described below will be used to assign the
   769         short term.</p>
   771       <p>Refer to <a href="">How to Organize an Advisory Board or TAG election</a>
   772        [<a href="#ref-election-howto">MEM15</a>] for more details.</p>
   774       <h5 id="random"> Verifiable Random Selection Procedure</h5>
   776       <p>When it is necessary to use a verifiable random selection process (e.g., in an AB or TAG election, to "draw straws"
   777         in case of a tie or to fill a short term), W3C uses the random and verifiable procedure defined in
   778         <a href="">RFC 2777</a> [<a href="#ref-RFC2777">RFC2777</a>]. The procedure orders
   779         an input list of names (listed in alphabetical order by family name unless otherwise specified) into a
   780         "result order."</p>
   782       <p>W3C applies this procedure as follows:</p>
   784       <ol>
   785         <li>When N people have tied for M (less than N) seats. In this case, only the names of the N individuals who tied
   786           are provided as input to the procedure. The M seats are assigned in result order.</li>
   787         <li>After all elected individuals have been identified, when N people are eligible for M (less than N) short terms.
   788           In this case, only the names of those N individuals are provided as input to the procedure. The short terms are
   789           assigned in result order.</li>
   790       </ol>
   792       <h4 id="AB-TAG-vacated">2.5.3 Advisory Board and Technical Architecture Group Vacated Seats</h4>
   794       <p>An Advisory Board or TAG participant's seat is vacated when either of the following occurs:</p>
   795       <ul>
   796         <li>the participant <a href="#resignation">resigns</a>, or</li>
   797         <li>the Chair asks the participant to <a href="#resignation">resign</a>.</li>
   798       </ul>
   800       <p>When an Advisory Board or TAG participant changes affiliations, as long as
   801         <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are respected, the individual
   802         <em class="rfc2119">may</em> continue to participate until the next regularly scheduled election for that group.
   803         Otherwise, the seat is vacated.</p>
   805       <p>Vacated seats are filled according to this schedule:</p>
   807       <ul>
   808         <li>When an appointed TAG seat is vacated, the Director <em class="rfc2119">may</em> re-appoint someone immediately,
   809           but no later than the next regularly scheduled election.</li>
   810         <li>When an elected seat on either the AB or TAG is vacated, the seat is filled at the next regularly scheduled election
   811           for the group unless the group Chair requests that W3C hold an election before then (for instance,
   812           due to the group's workload). The group Chair <em class="rfc2119">should not</em> request an exceptional election
   813           if the next regularly scheduled election is fewer than three months away.</li>
   814       </ul>
   816       <h2 id="Policies">3 General Policies for W3C Groups</h2>
   818       <p>This section describes general policies for W3C groups regarding participation, meeting requirements, and
   819         decision-making. These policies apply to <span id="participant">participants</span> in the following groups:
   820         <a href="#AC">Advisory Committee</a>, <a href="#ABParticipation">Advisory Board</a>,
   821         <a href="#tag-participation">TAG</a>,
   822         <a href="#wgparticipant">Working Groups</a>, and <a href="#igparticipant">Interest Groups</a>.</p>
   824       <h3 id="ParticipationCriteria">3.1 Individual Participation Criteria</h3>
   826       <p>There are three qualities an individual is expected to demonstrate in order to participate in W3C:</p>
   827       <ol>
   828         <li>Technical competence in one's role</li>
   829         <li>The ability to act fairly</li>
   830         <li>Social competence in one's role</li>
   831       </ol>
   832       <p>Advisory Committee representatives who nominate individuals from their organization for participation in W3C activities
   833         are responsible for assessing and attesting to the qualities of those nominees.</p>
   834       <p>See also the <a href="">W3C Code of Ethics and Professional Conduct</a> 
   835        [<a href="#ref-cepc">PUB38</a>] and the participation requirements described in
   836         <a href="">section 6</a> of the
   837         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
   839       <h4 id="coi">3.1.1 Conflict of Interest Policy</h4>
   841       <p>Individuals participating materially in W3C work <em class="rfc2119">must</em> disclose significant relationships when
   842        those relationships might reasonably be perceived as creating a conflict of interest with the individual's role at W3C.
   843        These disclosures <em class="rfc2119">must</em> be kept up-to-date as the individual's affiliations change and
   844        W3C membership evolves (since, for example, the individual might have a relationship with an organization that joins or
   845        leaves W3C). Each section in this document that describes a W3C group provides more detail about the disclosure mechanisms
   846        for that group.</p>
   847       <p>The ability of an individual to fulfill a role within a group without risking a conflict of interest depends on
   848         the individual's affiliations. When these affiliations change, the individual's assignment to the role
   849         <em class="rfc2119">must</em> be evaluated. The role <em class="rfc2119">may</em> be reassigned according to the
   850         appropriate process. For instance, the Director <em class="rfc2119">may</em> appoint a new group Chair when the
   851         current Chair changes affiliations (e.g., if there is a risk of conflict of interest, or if there is risk that the
   852         Chair's new employer will be over-represented within a W3C activity).</p>
   853       <p>The following are some scenarios where disclosure is appropriate:</p>
   854       <ul>
   855         <li>Paid consulting for an organization whose activity is relevant to W3C, or any consulting compensated with
   856           equity (shares of stock, stock options, or other forms of corporate equity).</li>
   857         <li>A decision-making role/responsibility (such as participating on the Board) in other organizations relevant to W3C.</li>
   858         <li>A position on a publicly visible advisory body, even if no decision making authority is involved.</li>
   859       </ul>
   860       <p>Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the Team.</p>
   861       <p>Team members are subject to the
   862         <a href="">W3C Team conflict of interest policy</a>
   863         [<a href="#ref-coi">PUB23</a>].</p>
   865       <h4 id="member-rep">3.1.2 Individuals Representing a Member Organization</h4>
   867       <p>Generally, individuals representing a Member in an official capacity within W3C are employees of the
   868         Member organization.
   869         However, an Advisory Committee representative <em class="rfc2119">may</em> designate a non-employee to represent the
   870         Member. Non-employee Member representatives <em class="rfc2119">must</em> disclose relevant affiliations to the Team and
   871         to any group in which the individual participates.</p>
   873       <p>In exceptional circumstances (e.g., situations that might jeopardize the progress of a group or create a
   874         <a href="#coi">conflict of interest</a>), the <a href="#def-Director">Director</a> <em class="rfc2119">may</em>
   875         decline to allow an individual designated by an Advisory Committee representative to participate in a group.</p>
   877       <p>A group charter <em class="rfc2119">may</em> limit the number of individuals representing a W3C Member (or group of
   878         <a href="#MemberRelated">related Members</a>).</p>
   880       <h3 id="GeneralMeetings">3.2 Meetings</h3>
   882       <p>W3C groups (including the <a href="#ACMeetings">Advisory Committee</a>, <a href="#AB">Advisory Board</a>,
   883         <a href="#TAG">TAG</a>, and <a href="#GroupsWG">Working Groups</a>) <em class="rfc2119">should</em> observe the
   884         meeting requirements in this section.</p>
   886       <p>W3C distinguishes two types of meetings:</p>
   888       <ol>
   889         <li>A <dfn id="ftf-meeting">face-to-face meeting</dfn> is one where most of the attendees are expected to
   890           participate in the same physical location.</li>
   891         <li>A <dfn id="distributed-meeting">distributed meeting</dfn> is one where most of the attendees are expected
   892           to participate from remote locations (e.g., by telephone, video conferencing, or
   893           <abbr title="Internet Relay Chat">IRC</abbr>).</li>
   894       </ol>
   896       <p>A Chair <em class="rfc2119">may</em> invite an individual with a particular expertise to attend a meeting on
   897         an exceptional basis. This person is a meeting guest, not a group <a href="#participant">participant</a>. Meeting guests
   898         do not have <a href="#Votes">voting rights</a>. It is the responsibility of the Chair to ensure that all meeting guests
   899         respect the chartered <a href="#confidentiality-levels">level of confidentiality</a> and other group requirements.</p>
   901       <p>Meeting announcements <em class="rfc2119">should</em> be sent to all appropriate group mailing lists, i.e., those most
   902         relevant to the anticipated meeting participants.</p>
   904       <p>The following table lists requirements for organizing a meeting:</p>
   906       <table border="1">
   907         <tbody>
   908           <tr>
   909             <th><br>
   910             </th>
   911             <th>Face-to-face meetings</th>
   912             <th>Distributed meetings</th>
   913           </tr>
   914           <tr>
   915             <th>Meeting announcement (before)</th>
   916             <td><span class="time-interval">eight weeks<sup>*</sup></span></td>
   917             <td><span class="time-interval">one week<sup>*</sup></span></td>
   918           </tr>
   919           <tr>
   920             <th>Agenda available (before)</th>
   921             <td><span class="time-interval">two weeks</span></td>
   922             <td><span class="time-interval">24 hours</span> (or longer if a meeting is scheduled after a weekend or holiday)</td>
   923           </tr>
   924           <tr>
   925             <th>Participation confirmed (before)</th>
   926             <td><span class="time-interval">three days</span></td>
   927             <td><span class="time-interval">24 hours</span></td>
   928           </tr>
   929           <tr>
   930             <th>Action items available (after)</th>
   931             <td><span class="time-interval">three days</span></td>
   932             <td><span class="time-interval">24 hours</span></td>
   933           </tr>
   934           <tr>
   935             <th>Minutes available (after)</th>
   936             <td><span class="time-interval">two weeks</span></td>
   937             <td><span class="time-interval">48 hours</span></td>
   938           </tr>
   939         </tbody>
   940       </table>
   942       <p><sup>*</sup> To allow proper planning (e.g., travel arrangements), the Chair is responsible for giving sufficient
   943         advance notice about the date and location of a meeting. Shorter notice for a meeting is allowed provided that there
   944         are no objections from group participants.</p>
   946       <h3 id="Consensus">3.3 Consensus</h3>
   948       <p>Consensus is a core value of W3C. To promote consensus, the W3C process requires Chairs to ensure that groups consider
   949         all legitimate views and objections, and endeavor to resolve them, whether these views and objections are expressed by
   950         the active participants of the group or by others (e.g., another W3C group, a group in another organization, or the
   951         general public). Decisions <em class="rfc2119">may</em> be made during meetings (<a href="#ftf-meeting">face-to-face</a>
   952         or <a href="#distributed-meeting">distributed</a>) as well as through email. <strong>Note:</strong> The Director, CEO,
   953         and COO have the role of assessing consensus within the Advisory Committee.</p>
   955       <p>The following terms are used in this document to describe the level of support for a decision among a set of eligible
   956         individuals:</p>
   957       <ol>
   958         <li><dfn id="def-Consensus">Consensus</dfn>: A substantial number of individuals in the set support the decision and
   959           nobody in the set registers a <a href="#FormalObjection">Formal Objection</a>. Individuals in the set
   960           <em class="rfc2119">may</em> abstain.
   961           Abstention is either an explicit expression of no opinion or silence by an individual in the set.
   962           <dfn id="def-Unanimity">Unanimity</dfn> is the particular case of consensus where all individuals in the set support
   963           the decision (i.e., no individual in the set abstains).</li>
   964         <li><dfn id="def-Dissent">Dissent</dfn>: At least one individual in the set registers a
   965           <a href="#FormalObjection">Formal Objection</a>.</li>
   966       </ol>
   968       <p>By default, the set of individuals eligible to participate in a decision is the set of group participants. The
   969         Process Document does not require a quorum for decisions (i.e., the minimal number of eligible participants required
   970         to be present before the Chair can call a question). A charter <em class="rfc2119">may</em> include a
   971         quorum requirement for consensus decisions.</p>
   973       <p>Where unanimity is not possible, a group <em class="rfc2119">should</em> strive to make consensus decisions where
   974         there is significant support and few abstentions. The Process Document does not require a particular percentage of
   975         eligible participants to agree to a motion in order for a decision to be made. To avoid decisions where there is 
   976         widespread apathy, (i.e., little support and many abstentions), groups <em class="rfc2119">should</em> set
   977         minimum thresholds of active support before a decision can be recorded. The appropriate percentage
   978         <em class="rfc2119">may</em> vary depending on the size of the group and the nature of the decision. A charter
   979         <em class="rfc2119">may</em> include threshold requirements for consensus decisions. For instance, a charter
   980         might require a supermajority of eligible participants (i.e., some established percentage above 50%) to support
   981         certain types of consensus decisions.</p>
   983       <h4 id="managing-dissent">3.3.1 Managing Dissent</h4>
   985       <p>In some cases, even after careful consideration of all points of view, a group might find itself unable to reach
   986         consensus. The Chair <em class="rfc2119">may</em> record a decision where there is dissent (i.e., there is at least one
   987         <a href="#FormalObjection">Formal Objection</a>) so that the group can make progress (for example, to produce a
   988         deliverable in a timely manner). Dissenters cannot stop a group's work simply by saying that they cannot live with a
   989         decision. When the Chair believes that the Group has duly considered the legitimate concerns of dissenters as far as is
   990         possible and reasonable, the group <em class="rfc2119">should</em> move on.</p>
   991       <p>Groups <em class="rfc2119">should</em> favor proposals that create the weakest objections. This is preferred over
   992         proposals that are supported by a large majority but that cause strong objections from a few people. As part of making
   993         a decision where there is dissent, the Chair is expected to be aware of which participants work for the same (or
   994         <a href="#MemberRelated">related</a>) Member organizations and weigh their input accordingly.</p>
   996       <h4 id="WGArchiveMinorityViews">3.3.2 Recording and Reporting Formal Objections</h4>
   998       <p>In the W3C process, an individual <em class="rfc2119">may</em> register a Formal Objection to a decision. A
   999         <dfn id="FormalObjection">Formal Objection</dfn> to a group decision is one that the reviewer requests that the
  1000         Director consider as part of evaluating the related decision (e.g., in response to a
  1001         <a href="#rec-advance">request to advance</a> a technical report). <strong>Note:</strong> In this document, the
  1002         term "Formal Objection" is used to emphasize this process implication: Formal Objections receive Director consideration.
  1003         The word "objection" used alone has ordinary English connotations.</p>
  1004       <p>An individual who registers a Formal Objection <em class="rfc2119">should</em> cite technical arguments and propose
  1005         changes that would remove the Formal Objection; these proposals <em class="rfc2119">may</em> be vague or incomplete.
  1006         Formal Objections that do not provide substantive arguments or rationale are unlikely to receive serious consideration
  1007         by the Director.</p>
  1008       <p>A record of each Formal Objection <em class="rfc2119">must</em> be
  1009         <a href="#confidentiality-change">publicly available</a>. A Call for Review (of a document) to the Advisory Committee
  1010         <em class="rfc2119">must</em> identify any Formal Objections.</p>
  1012       <h4 id="formal-address">3.3.3 Formally Addressing an Issue</h4>
  1014       <p>In the context of this document, a group has formally addressed an issue when it has sent a public, substantive response
  1015         to the reviewer who raised the issue. A substantive response is expected to include rationale for decisions (e.g., a
  1016         technical explanation, a pointer to charter scope, or a pointer to a requirements document). The adequacy of a response
  1017         is measured against what a W3C reviewer would generally consider to be technically sound. If a group believes that a
  1018         reviewer's comments result from a misunderstanding, the group <em class="rfc2119">should</em> seek clarification
  1019         before reaching a decision.</p>
  1020       <p>As a courtesy, both Chairs and reviewers <em class="rfc2119">should</em> set expectations for the schedule of
  1021         responses and acknowledgments. The group <em class="rfc2119">should</em> reply to a reviewer's initial comments in a
  1022         timely manner. The group <em class="rfc2119">should</em> set a time limit for acknowledgment by a reviewer of the
  1023         group's substantive response; a reviewer cannot block a group's progress. It is common for a reviewer to require a week
  1024         or more to acknowledge and comment on a substantive response. The group's responsibility to respond to reviewers does
  1025         not end once a reasonable amount of time has elapsed. However, reviewers <em class="rfc2119">should</em> realize that
  1026         their comments will carry less weight if not sent to the group in a timely manner.</p>
  1027       <p>Substantive responses <em class="rfc2119">should</em> be recorded. The group <em class="rfc2119">should</em> maintain
  1028         an accurate summary of all substantive issues and responses to them (e.g., in the form of an issues list with links to
  1029         mailing list archives).</p>
  1031       <h4 id="WGChairReopen">3.3.4 Reopening a Decision When Presented With New Information</h4>
  1033       <p>The Chair <em class="rfc2119">may</em> reopen a decision when presented with new information, including:</p>
  1034       <ul>
  1035         <li>additional technical information,</li>
  1036         <li>comments by email from participants who were unable to attend a scheduled meeting,</li>
  1037         <li>comments by email from meeting attendees who chose not to speak out during a meeting (e.g., so they could confer
  1038           later with colleagues or for cultural reasons).</li>
  1039       </ul>
  1040       <p>The Chair <em class="rfc2119">should</em> record that a decision has been reopened, and <em class="rfc2119">must</em>
  1041         do so upon request from a group participant.</p>
  1043       <h3 id="Votes">3.4 Votes</h3>
  1045       <p>A group <em class="rfc2119">should</em> only conduct a vote to resolve a <em>substantive issue</em> after the Chair has
  1046         determined that all available means of <a href="#Consensus">reaching consensus</a> through technical discussion and
  1047         compromise have failed, and that a vote is necessary to break a deadlock. In this case the Chair
  1048         <em class="rfc2119">must</em> record (e.g., in the minutes of the meeting or in an archived email message):</p>
  1049       <ul>
  1050         <li>an explanation of the issue being voted on;</li>
  1051         <li>the decision to conduct a vote (e.g., a simple majority vote) to resolve the issue;</li>
  1052         <li>the outcome of the vote;</li>
  1053         <li>any Formal Objections.</li>
  1054       </ul>
  1055       <p>In order to vote to resolve a substantive issue, an individual <em class="rfc2119">must</em> be a group
  1056         <a href="#participant">participant</a>. Each organization represented in the group <em class="rfc2119">must</em> have
  1057         at most one vote, even when the organization is represented by several participants in the group (including
  1058         Invited Experts). For the purposes of voting:</p>
  1059       <ul>
  1060         <li>A Member or group of <a href="#MemberRelated">related Members</a> is considered a single organization.</li>
  1061         <li>The <a href="#Team">Team</a> is considered an organization.</li>
  1062       </ul>
  1063       <p>Unless the charter states otherwise, <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">may</em> vote.</p>
  1064       <p>If a participant is unable to attend a vote, that individual <em class="rfc2119">may</em> authorize anyone at the meeting
  1065         to act as a <dfn id="proxy">proxy</dfn>. The absent participant <em class="rfc2119">must</em> inform the Chair in writing
  1066         who is acting as proxy, with written instructions on the use of the proxy. For a Working Group or Interest Group, see the
  1067         related requirements regarding an individual who attends a meeting as a <a href="#mtg-substitute">substitute</a>
  1068         for a participant.</p>
  1070       <p>A group <em class="rfc2119">may</em> vote for other purposes than to resolve a substantive issue. For instance, the
  1071        Chair often conducts a "straw poll" vote as a means of determining whether there is consensus about a potential decision.</p>
  1072       <p>A group <em class="rfc2119">may</em> also vote to make a process decision. For example, it is appropriate to decide by
  1073         simple majority whether to hold a meeting in San Francisco or San Jose (there's not much difference geographically).
  1074         When simple majority votes are used to decide minor issues, the minority are <em class="rfc2119">not required</em> to
  1075         state the reasons for their dissent, and the group is <em class="rfc2119">not required</em> to record individual votes.</p>
  1076       <p>A group charter <em class="rfc2119">should</em> include formal voting procedures (e.g., quorum or threshold requirements)
  1077         for making decisions about substantive issues.</p>
  1079       <p>Procedures for <a href="#ACVotes">Advisory Committee votes</a> are described separately.</p>
  1081       <h3 id="WGAppeals">3.5 Appeal of a Chair's Decision</h3>
  1083       <p>Groups resolve issues through dialog. Individuals who disagree strongly with a decision <em class="rfc2119">should</em>
  1084         register with the Chair any <a href="#FormalObjection">Formal Objections</a> (e.g., to a decision made as the result of a
  1085         <a href="#Votes">vote</a>).</p>
  1087       <p>When group participants believe that their concerns are not being duly considered by the group, they
  1088         <em class="rfc2119">may</em> ask the <a href="#def-Director">Director</a> (for representatives of a Member organization,
  1089         via their Advisory Committee representative) to confirm or deny the decision. This is a <dfn>Group Decision Appeal</dfn>.
  1090         The participants <em class="rfc2119">should</em> also make their requests known to the
  1091         <a href="#TeamContact">Team Contact</a>. The Team Contact <em class="rfc2119">must</em> inform the Director when a group
  1092         participant has raised concerns about due process.</p>
  1094       <p>Any requests to the Director to confirm a decision <em class="rfc2119">must</em> include a summary of the issue
  1095        (whether technical or procedural), decision, and rationale for the objection. All counter-arguments, rationales,
  1096        and decisions <em class="rfc2119">must</em> be recorded.</p>
  1097       <p>Procedures for <a href="#ACAppeal">Advisory Committee appeals</a> are described separately.</p>
  1099       <h3 id="resignation">3.6 Resignation from a Group</h3>
  1100       <p>A W3C Member or Invited Expert <em class="rfc2119">may</em> resign from a group. On written notification from an Advisory
  1101         Committee representative or Invited Expert to the team, the Member and their representatives or the Invited Expert will
  1102         be deemed to have resigned from the relevant group. See section 4.2. of the
  1103         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]
  1104         for information about obligations remaining after resignation from certain groups.</p>
  1106       <section id="chapterDissemination">
  1107         <h2 id="dissemination">4 Dissemination Policies</h2>
  1108         <p>The Team is responsible for managing communication within W3C and with the general public (e.g., news services,
  1109           press releases, managing the Web site and access privileges, and managing calendars). Members
  1110           <em class="rfc2119">should</em> solicit review by the Team prior to issuing press releases about their work within W3C.</p>
  1111         <p>The Team makes every effort to ensure the persistence and availability of the following public information:</p>
  1112         <ul>
  1113           <li><a href="#Reports">W3C technical reports</a> whose publication has been approved by the Director. Per the Membership
  1114             Agreement, W3C technical reports (and software) are available free of charge to the general public;
  1115             (refer to the <a href="">W3C Document License</a>
  1116             [<a href="#ref-doc-license">PUB18</a>]).</li>
  1117           <li>A <a href="">mission statement</a> [<a href="#ref-mission">PUB15</a>]
  1118             that explains the
  1119             purpose and mission of W3C, the key benefits for Members, and the organizational structure of W3C.</li>
  1120           <li>Legal documents, including the
  1121             <a href="">Membership Agreement</a>
  1122             [<a href="#ref-member-agreement">PUB6</a>]) and documentation of any legal commitments W3C has with other entities.</li>
  1123           <li>The Process Document.</li>
  1124           <li>Public results of W3C activities and <a href="#GAEvents">Workshops</a>.</li>
  1125         </ul>
  1126         <p>To keep the Members abreast of W3C meetings, Workshops, and review deadlines, the Team provides them with a regular
  1127           (e.g., weekly) news service and maintains a <a href="">calendar</a>
  1128           [<a href="#ref-calendar">PUB36</a>] of official W3C events. Members are encouraged to send schedule and event information
  1129           to the Team for inclusion on this calendar.</p>
  1131         <h3 id"confidentiality-levels"="">4.1 Confidentiality Levels</h3>
  1133         <p>There are three principal levels of access to W3C information (on the W3C Web site, in W3C meetings, etc.): public,
  1134           Member-only, and Team-only.</p>
  1135         <p>While much information made available by W3C is public, <dfn id="Member-only">"Member-only" information</dfn>
  1136           is available to authorized parties only, including representatives of Member organizations,
  1137           <a href="#invited-expert-wg">Invited Experts</a>, the Advisory Board, the TAG, and the Team. For example, the
  1138           <a href="#WGCharter">charter</a> of some Working Groups <em class="rfc2119">may</em> specify a
  1139           Member-only confidentiality level for group proceedings.</p>
  1140         <p id="Team-only">"Team-only" information is available to the Team and other authorized parties.</p>
  1141         <p>Those authorized to access Member-only and Team-only information:</p>
  1142         <ul>
  1143           <li><em class="rfc2119">must</em> treat the information as confidential within W3C,</li>
  1144           <li><em class="rfc2119">must</em> use reasonable efforts to maintain the proper level confidentiality, and</li>
  1145           <li><em class="rfc2119">must not</em> release this information to the general public or press.</li>
  1146         </ul>
  1147         <p>The Team <em class="rfc2119">must</em> provide mechanisms to protect the confidentiality of Member-only information
  1148           and ensure that authorized parties have proper access to this information. Documents <em class="rfc2119">should</em>
  1149           clearly indicate whether they require Member-only confidentiality. Individuals uncertain of the confidentiality level
  1150           of a piece of information <em class="rfc2119">should</em> contact the Team.</p>
  1151         <p>Advisory Committee representatives <em class="rfc2119">may</em> authorize Member-only access to
  1152           <a href="#member-rep">Member representatives</a> and other individuals employed by the Member who are considered
  1153           appropriate recipients. For instance, it is the responsibility of the Advisory Committee representative and other
  1154           employees and official representatives of the organization to ensure that Member-only news announcements are
  1155           distributed for internal use only within their organization. Information about
  1156           Member mailing lists is available in the <a href="">New Member Orientation</a>.</p>
  1158         <h4 id="confidentiality-change">4.1.1 Changing Confidentiality Level</h4>
  1160         <p>As a benefit of membership, W3C provides some Team-only and Member-only channels for certain types of communication.
  1161           For example, Advisory Committee representatives can send <a href="#ACReview">reviews</a> to a Team-only channel.
  1162           However, for W3C processes with a significant public component, such as the technical report development process, it
  1163           is also important for information that affects decision-making to be publicly available. The Team
  1164           <em class="rfc2119">may</em> need to communicate Team-only information to a Working Group or the public. Similarly,
  1165           a Working Group whose proceedings are Member-only <em class="rfc2119">must</em> make
  1166           public information pertinent to the technical report development process.</p>
  1167         <p>This document clearly indicates which information <em class="rfc2119">must</em> be available to Members or the public,
  1168           even though that information was initially communicated on Team-only or Member-only channels. Only the Team and
  1169           parties authorized by the Team change the level of confidentiality of this information. When doing so:</p>
  1170         <ol>
  1171           <li>The Team <em class="rfc2119">must</em> use a version of the information that was expressly provided by the author
  1172             for the new confidentiality level. In Calls for Review and other similar messages, the Team
  1173             <em class="rfc2119">should</em> remind recipients to provide such alternatives.</li>
  1174           <li>The Team <em class="rfc2119">must not</em> attribute the version for the new confidentiality level to the
  1175             author without the author's consent.</li>
  1176           <li>If the author has not conveyed to the Team a version that is suitable for another confidentiality level, the Team
  1177             <em class="rfc2119">may</em> make available a version that reasonably communicates what is required, while
  1178             respecting the original level of confidentiality, and without attribution to the original author.</li>
  1179         </ol>
  1180       </section>
  1182       <section id="ChapterGroups">
  1184         <h2 id="GAGeneral">5 Working Groups and Interest Groups</h2>
  1186         <p id="GAGroups">This document defines two types of groups:</p>
  1187         <ol>
  1188           <li><a href="#GroupsWG">Working Groups.</a> Working Groups typically produce deliverables (e.g.,
  1189             <a href="#rec-advance">Recommendation Track technical reports</a>, software, test suites, and reviews of the
  1190             deliverables of other groups). There are additional participation requirements described in the
  1191             <a href="">W3C Patent Policy</a>
  1192             [<a href="#ref-patentpolicy">PUB33</a>].</li>
  1193           <li><a href="#GroupsIG">Interest Groups.</a> The primary goal of an Interest Group is to bring together people who
  1194             wish to evaluate potential Web technologies and policies. An Interest Group is a forum for the exchange of ideas.</li>
  1195         </ol>
  1196         <p>Interest Groups do not publish <a href="#RecsW3C">Recommendation Track technical reports</a>; see information about
  1197           <a href="#WGNote">maturity levels for Interest Groups</a>.</p>
  1199         <h3 id="ReqsAllGroups">5.1 Requirements for All Working and Interest Groups</h3>
  1201         <p>Each group <em class="rfc2119">must</em> have a charter. Requirements for the charter depend on the group type.
  1202           All group charters <em class="rfc2119">must</em> be public (even if other proceedings of the group are
  1203           <a href="#Member-only">Member-only</a>).</p>
  1204         <p>Each group <em class="rfc2119">must</em> have a <dfn id="GeneralChairs">Chair</dfn> (or co-Chairs) to coordinate
  1205           the group's tasks. The Director appoints (and re-appoints) Chairs for all groups. The Chair is a
  1206           <a href="#member-rep">Member representative</a>, a <a href="#Team">Team representative</a>, or an
  1207           <a href="#invited-expert-wg">Invited Expert</a> (invited by the Director). The requirements of this document that
  1208           apply to those types of participants apply to Chairs as well. The
  1209           <a href="/Guide/chair-roles">role of the Chair</a> is described in the
  1210           <a href="">Art of Consensus</a> [<a href="#ref-guide">PUB37</a>].</p>
  1211         <p>Each group <em class="rfc2119">must</em> have a <dfn id="TeamContact">Team Contact</dfn>, who acts as the interface
  1212           between the Chair, group participants, and the rest of the Team. The 
  1213           <a href="/Guide/staff-contact">role of the Team Contact</a> is described in the Member guide. The Chair and the
  1214           Team Contact of a group <em class="rfc2119">should not</em> be the same individual.</p>
  1215         <p>Each group <em class="rfc2119">must</em> have an archived mailing list for formal group communication (e.g., for
  1216           meeting announcements and minutes, documentation of decisions, and <a href="#FormalObjection">Formal Objections</a>
  1217           to decisions). It is the responsibility of the Chair and Team Contact to ensure that new participants are subscribed
  1218           to all relevant mailing lists. Refer to the list of
  1219           <a href="">group mailing lists</a> [<a href="#ref-mailing-lists">MEM2</a>].</p>
  1220         <p>A Chair <em class="rfc2119">may</em> form task forces (composed of group participants) to carry out assignments for
  1221           the group. The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group's charter.
  1222           A group <em class="rfc2119">should</em> document the process it uses to create task forces (e.g., each task force
  1223           might have an informal "charter"). Task forces do not publish <a href="#Reports">technical reports</a>; the 
  1224           Working Group <em class="rfc2119">may</em> choose to publish their results as part of a technical report.</p>
  1226         <h3>5.2 <dfn id="GroupsWG">Working Groups</dfn> and <dfn id="GroupsIG">Interest Groups</dfn></h3>
  1228         <p>Although Working Groups and Interest Groups have different purposes, they share some characteristics, and so are
  1229           defined together in the following sections.</p>
  1231         <h4>5.2.1 <dfn id="group-participation">Working Group and Interest Group Participation Requirements</dfn></h4>
  1233         <p>There are three types of individual <dfn id="wgparticipant">participants in a Working Group</dfn>:
  1234           <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
  1235           and <a href="#Team">Team representatives</a> (including the <a href="#TeamContact">Team Contact</a>).</p>
  1236         <p>There are four types of individual <dfn id="igparticipant">participants in an Interest Group</dfn>: the same three
  1237           types as for Working Groups plus, for an Interest Group where the only
  1238           <a href="#ig-mail-only">participation requirement is mailing list subscription</a>,
  1239           <dfn id="public-participant-ig">public participants</dfn>.</p>
  1240         <p>Except where noted in this document or in a group charter, all participants share the same rights and responsibilities
  1241           in a group; see also the <a href="#ParticipationCriteria">individual participation criteria</a>.</p>
  1242         <p>A participant <em class="rfc2119">must</em> represent at most one organization in a Working Group or Interest Group.</p>
  1243         <p>An individual <em class="rfc2119">may</em> become a Working or Interest Group participant at any time during the group's
  1244           existence. See also relevant requirements in
  1245           <a href="">section 4.3</a> of the
  1246           <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
  1247         <p>On an exceptional basis, a Working or Interest Group participant <em class="rfc2119">may</em> designate a
  1248           <dfn id="mtg-substitute">substitute</dfn> to attend a <a href="#GeneralMeetings">meeting</a> and
  1249           <em class="rfc2119">should</em> inform the Chair. The substitute <em class="rfc2119">may</em> act on behalf of the
  1250           participant, including for <a href="#Votes">votes</a>. For the substitute to vote, the participant
  1251           <em class="rfc2119">must</em> inform the Chair in writing in advance. As a courtesy to the group, if the substitute
  1252           is not well-versed in the group's discussions, the regular participant <em class="rfc2119">should</em> authorize
  1253           another participant to act as <a href="#proxy">proxy</a> for votes.</p>
  1254         <p>To allow rapid progress, Working Groups are intended to be small (typically fewer than 15 people) and composed of
  1255           experts in the area defined by the charter. In principle, Interest Groups have no limit on the number of participants.
  1256           When a Working Group grows too large to be effective, W3C <em class="rfc2119">may</em> split it into an Interest Group
  1257           (a discussion forum) and a much smaller Working Group (a core group of highly dedicated participants).</p>
  1258         <p>See also the licensing obligations on Working Group participants in
  1259           <a href="">section 3</a> of the
  1260           <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
  1261           and the patent claim exclusion process of
  1262           <a href="">section 4</a>.</p>
  1264         <h5> <dfn id="member-rep-wg">Member Representative</dfn> in a Working Group</h5>
  1266         <p>An individual is a Member representative in a Working Group if all of the following conditions are satisfied:</p>
  1267         <ul>
  1268           <li>the Advisory Committee representative of the Member in question has designated the individual as a
  1269             Working Group participant, and</li>
  1270           <li>the individual qualifies for <a href="#member-rep">Member representation</a>.</li>
  1271         </ul>
  1272         <p><dfn id="member-rep-info">To designate an individual as a Member representative in a Working Group</dfn>, an
  1273           Advisory Committee representative <em class="rfc2119">must</em> provide the Chair and Team Contact with all of
  1274           the following information, in addition to any other information required by the <a href="#cfp">Call for Participation</a>
  1275           and charter (including the participation requirements of the
  1276           <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]):</p>
  1277         <ol>
  1278           <li>The name of the W3C Member the individual represents and whether the individual is an employee of that
  1279             Member organization;</li>
  1280           <li>A statement that the individual accepts the participation terms set forth in the charter (with an indication
  1281             of charter date or version);</li>
  1282           <li>A statement that the Member will provide the necessary financial support for participation (e.g., for travel,
  1283             telephone calls, and conferences).</li>
  1284         </ol>
  1285         <p>A Member participates in a Working Group from the moment the first Member representative joins the group until
  1286           either of the following occurs:</p>
  1287         <ul>
  1288           <li>the group closes, or</li>
  1289           <li>the Member <a href="#resignation">resigns</a> from the Working Group; this is done through the
  1290             Member's Advisory Committee representative.</li>
  1291         </ul>
  1293         <h5> <dfn id="member-rep-ig">Member Representative</dfn> in an Interest Group</h5>
  1295         <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
  1296           an individual is a Member representative in an Interest Group if all of the following conditions are satisfied:</p>
  1298         <ul>
  1299           <li>the Advisory Committee representative of the Member in question has designated the individual as an
  1300             Interest Group participant, and</li>
  1301           <li>the individual qualifies for <a href="#member-rep">Member representation</a>.</li>
  1302         </ul>
  1304         <p>To designate an individual as a Member representative in an Interest Group, the Advisory Committee representative
  1305           <em class="rfc2119">must</em> follow the instructions in the <a href="#cfp">Call for Participation</a> and charter.</p>
  1307         <p>Member participation in an Interest Group ceases under the same conditions as for a Working Group.</p>
  1309         <h5> <dfn id="invited-expert-wg">Invited Expert in a Working Group</dfn></h5>
  1311         <p>The Chair <em class="rfc2119">may</em> invite an individual with a particular expertise to participate in a
  1312           Working Group. This individual <em class="rfc2119">may</em> represent an organization in the group 
  1313           (e.g., if acting as a liaison with another organization).</p>
  1315         <p>An individual is an Invited Expert in a Working Group if all of the following conditions are satisfied:</p>
  1317         <ul>
  1318           <li>the Chair has designated the individual as a group participant,</li>
  1319           <li>the Team Contact has agreed with the Chair's choice, and</li>
  1320           <li>the individual has provided the <a href="#inv-expert-info">information required of an Invited Expert</a> to
  1321             the Chair and Team Contact.</li>
  1322         </ul>
  1324         <p>To designate an individual as an Invited Expert in a Working Group, the Chair <em class="rfc2119">must</em>
  1325           inform the Team Contact and provide rationale for the choice. When the Chair and the Team Contact disagree about
  1326           a designation, the <a href="#def-Director">Director</a> determines whether the individual will be invited to
  1327           participate in the Working Group.</p>
  1329         <p>To <dfn id="inv-expert-info">participate in a Working Group as an Invited Expert</dfn>, an individual
  1330           <em class="rfc2119">must</em>:</p>
  1332         <ul>
  1333           <li>identify the organization, if any, the individual represents as a participant in this group,</li>
  1334           <li>agree to the terms of the
  1335             <a href="">invited expert and collaborators agreement</a>
  1336             [<a href="#ref-invited-expert">PUB17</a>],</li>
  1337           <li>accept the participation terms set forth in the charter (including the participation requirements of
  1338             <a href="">section 3</a> (especially 3.4) and
  1339             <a href="">section 6</a> (especially 6.10) of the
  1340             <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]),
  1341             indicating a specific charter date or version,</li>
  1342           <li>disclose whether the individual is an employee of a W3C Member; see the
  1343             <a href="#coi">conflict of interest policy</a>,</li>
  1344           <li>provide a statement of who will provide the necessary financial support for the individual's participation
  1345             (e.g., for travel, telephone calls, and conferences), and</li>
  1346           <li>if the individual's employer (including a self-employed individual) or the organization the individual represents
  1347             is not a W3C Member, indicate whether that organization intends to join W3C. If the organization does not intend to
  1348             join W3C, indicate reasons the individual is aware of for this choice.</li>
  1349         </ul>
  1351         <p>The Chair <em class="rfc2119">should not</em> designate as an Invited Expert in a Working Group an individual
  1352           who is an employee of a W3C Member. The Chair <em class="rfc2119">must not</em> use Invited Expert status to circumvent
  1353           participation limits imposed by the <a href="#WGCharter">charter</a>.</p>
  1354         <p>An Invited Expert participates in a Working Group from the moment the individual joins the group until any of
  1355           the following occurs:</p>
  1356         <ul>
  1357           <li>the group closes, or</li>
  1358           <li>the Chair or Director withdraws the invitation to participate, or</li>
  1359           <li>the individual <a href="#resignation">resigns</a>.</li>
  1360         </ul>
  1362         <h5> <dfn id="invited-expert-ig">Invited Expert in an Interest Group</dfn></h5>
  1364         <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>, the
  1365           participation requirements for an Invited Expert in an Interest Group are the same as those for an
  1366           <a href="#invited-expert-wg">Invited Expert in a Working Group</a>.</p>
  1368         <h5> <dfn id="team-rep-wg">Team Representative in a Working Group</dfn></h5>
  1370         <p>An individual is a Team representative in a Working Group when so designated by W3C management.</p>
  1372         <p>A Team representative participates in a Working Group from the moment the individual joins the group until any of
  1373           the following occurs:</p>
  1375         <ul>
  1376           <li>the group closes, or</li>
  1377           <li>W3C management changes Team representation by sending email to the Chair, cc'ing the group mailing list.</li>
  1378         </ul>
  1380         <p>The Team participates in a Working Group from the moment the Director announces the creation of the group until
  1381           the group closes.</p>
  1383         <h5> <dfn id="team-rep-ig">Team Representative in an Interest Group</dfn></h5>
  1385         <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
  1386           an individual is a Team representative in an Interest Group when so designated by W3C management.</p>
  1388         <h4>5.2.2 <dfn id="WGCharterDevelopment">Working Group and Interest Group Charter Development</dfn></h4>
  1390         <p>W3C creates a charter based on interest from the Members and Team. The Team <em class="rfc2119">must</em> notify
  1391           the Advisory Committee when a charter for a new Working Group or Interest Group is in development. This is intended
  1392           to raise awareness, even if no formal proposal is yet available. Advisory Committee representatives
  1393           <em class="rfc2119">may</em> provide feedback on the
  1394           <a href="#ACCommunication">Advisory Committee discussion list</a>.</p>
  1396         <p>W3C <em class="rfc2119">may</em> begin work on a Working Group or Interest Group charter at any time.</p>
  1398         <h4>5.2.3 <dfn id="CharterReview">Advisory Committee Review of a Working Group or Interest Group Charter</dfn></h4>
  1400         <p>The Director <em class="rfc2119">must</em> solicit <a href="#ACReview">Advisory Committee review</a> of every new or
  1401           substantively modified Working Group or Interest Group charter. The Director is <em class="rfc2119">not required</em>
  1402           to solicit Advisory Committee review prior to a charter extension or for minor changes. The review period
  1403           <em class="rfc2119">must</em> be at least four weeks.</p>
  1405         <p>The Director's Call for Review of a substantively modified charter <em class="rfc2119">must</em> highlight
  1406           important changes (e.g., regarding deliverables or resource allocation) and include rationale for the changes.</p>
  1408         <h4>5.2.4 <dfn id="cfp">Call for Participation in a Working Group or Interest Group</dfn></h4>
  1410         <p>After Advisory Committee review of a Working Group or Interest Group charter, the Director
  1411           <em class="rfc2119">may</em> issue a Call for Participation to the Advisory Committee. Charters
  1412           <em class="rfc2119">may</em> be amended based on review comments before the Director issues a
  1413           Call for Participation. </p>
  1415         <p>For a new group, this announcement officially creates the group. The announcement <em class="rfc2119">must</em>
  1416           include a reference to the <a href="#WGCharter">charter</a>, the name(s) of the group's
  1417           <a href="#GeneralChairs">Chair(s)</a>, and the name(s) of the <a href="#TeamContact">Team Contact(s)</a>.</p>
  1419         <p>After a Call for Participation, any <a href="#member-rep">Member representatives</a> and
  1420           <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">must</em> be designated (or re-designated).</p>
  1422         <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate an
  1423           <a href="#ACAppeal">Advisory Committee Appeal</a> against a Director's decision to create or substantially modify a
  1424           Working Group or Interest Group charter.</p>
  1426         <h4>5.2.5 <dfn id="charter-extension">Working Group and Interest Group Charter Extension</dfn></h4>
  1428         <p>To extend a Working Group or Interest Group charter with no other substantive modifications, the Director announces
  1429           the extension to the Advisory Committee. The announcement <em class="rfc2119">must</em> indicate the new duration.
  1430           The announcement <em class="rfc2119">must</em> also include rationale for the extension, a reference to the
  1431           <a href="#WGCharter">charter</a>, the name(s) of the group's <a href="#GeneralChairs">Chair(s)</a>,
  1432           the name of the <a href="#TeamContact">Team Contact</a>, and instructions for joining the group.</p>
  1434         <p>After a charter extension, Advisory Committee representatives and the Chair are <em class="rfc2119">not required</em>
  1435           to re-designate <a href="#member-rep">Member representatives</a> and
  1436           <a href="#invited-expert-wg">Invited Experts</a>.</p>
  1438         <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate an
  1439           <a href="#ACAppeal">Advisory Committee Appeal</a> against a Director's decision regarding the extension of a
  1440           Working Group or Interest Group charter.</p>
  1442         <h4>5.2.6 <dfn id="WGCharter">Working Group and Interest Group Charters</dfn></h4>
  1444         <p>A Working Group or Interest Group charter <em class="rfc2119">must</em> include all of the following information.</p>
  1446         <ul>
  1447           <li>The group's mission (e.g., develop a technology or process, review the work of other groups);</li>
  1448           <li>The scope of the group's work and criteria for success;</li>
  1449           <li>The duration of the group (typically from six months to two years);</li>
  1450           <li>The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software);</li>
  1451           <li>Expected milestone dates where available. <strong>Note</strong>: A charter is <em class="rfc2119">not required</em>
  1452             to include schedules for review of other group's deliverables;</li>
  1453           <li>The process for the group to approve the release of deliverables (including intermediate results);</li>
  1454           <li>Any dependencies by groups within or outside of W3C on the deliverables of this group. For any dependencies,
  1455             the charter <em class="rfc2119">must</em> specify the mechanisms for communication about the deliverables;</li>
  1456           <li>Any dependencies of this group on other groups within or outside of W3C. Such dependencies include interactions
  1457             with <a href="">W3C Horizontal Groups</a>;</li>
  1458           <li>The <a href="#confidentiality-levels">level of confidentiality</a> of the group's proceedings and deliverables;</li>
  1459           <li>Meeting mechanisms and expected frequency;</li>
  1460           <li>If known, the date of the first <a href="#ftf-meeting">face-to-face meeting</a>. The date of the first
  1461             face-to-face meeting of a proposed group <em class="rfc2119">must not</em> be sooner than
  1462             <span class="time-interval">eight weeks</span> after the date of the proposal.</li>
  1463           <li>Communication mechanisms to be employed within the group, between the group and the rest of W3C, and with the
  1464             general public;</li>
  1465           <li>An estimate of the expected time commitment from participants;</li>
  1466           <li>The expected time commitment and level of involvement by the Team (e.g., to track developments, write and edit
  1467             technical reports, develop code, or organize pilot experiments).</li>
  1468           <li>Intellectual property information. What are the intellectual property (including patents and copyright)
  1469             considerations affecting the success of the Group? In particular, is there any reason to believe that it will be
  1470             difficult to meet the Royalty-Free licensing goals of section 2 of the
  1471             <a href="">W3C Patent Policy</a>
  1472             [<a href="#ref-patentpolicy">PUB33</a>]?</li>
  1473         </ul>
  1475         <p>See also the charter requirements of <a href="">section 2</a>
  1476          and <a href="">section 3</a> of the
  1477          <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
  1479         <p>For every Recommendation Track deliverable that continues work on a Working Draft (WD) published under any other
  1480           Charter (including a predecessor group of the same name), for which there is an existing Reference Draft or
  1481           Candidate Recommendation, the description of that deliverable in the proposed charter of the adopting Working Group
  1482           <em class="rfc2119">must</em> provide the following information:</p>
  1484         <ul>
  1485           <li>The title, stable URL, and publication date of the <dfn>Adopted Working Draft</dfn> which will serve as the basis
  1486             for work on the deliverable</li>
  1487           <li>The title, stable URL, and publication date of the most recent Reference Draft or
  1488             <a href="#last-call">Candidate Recommendation</a> which triggered an Exclusion Opportunity per the Patent Process</li>
  1489           <li>The stable URL of the Working Group charter under which the most recent Reference Draft or Candidate Recommendation
  1490             was published.</li>
  1491         </ul>
  1493         <p>These data <em class=rfc2119>must</em> be identified in the charter with the labels "Adopted Working Draft",
  1494           "most recent Reference Draft", "most recent Candidate Recommendation", and "Other Charter", respectively.</p>
  1496         <p>The <dfn>Reference Draft</dfn> is the latest Working Draft published within 90 days of the 
  1497           <a href="#first-wd">First Public Working Draft</a> or if no Public Working Draft has been published within
  1498           90 days of the First Public Working Draft it is that First Public Working Draft. It is the specific draft against which
  1499           exclusions are made, as per <a href="">section 4.1</a>
  1500           of the <a href="">W3C Patent Policy</a>
  1501           [<a href="#ref-patentpolicy">PUB33</a>].</p>
  1503         <p>The Adopted Working Draft and the most recent Reference Draft or <a href="#last-call">Candidate Recommendation</a>
  1504           <em class="rfc2119">must</em> each be adopted in their entirety and without any modification. The proposed charter
  1505           <em class="rfc2119">must</em> state that the most recent Reference Draft or Candidate Recommendation
  1506           is deemed to be the Reference Draft or Candidate Recommendation of the Adopted Working Draft, and the date when the
  1507           Exclusion Opportunity that arose on publishing the First Public Working Draft or Candidate Recommendation
  1508           began and ended. As per <a href="">section 4.3</a> of
  1509           the <a href="">W3C Patent Policy</a>
  1510           [<a href="#ref-patentpolicy">PUB33</a>], this potentially means that exclusions can only be made
  1511           immediately on joining a Working Group.</p>
  1513         <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding
  1514           participation, including specifying that the <dfn id="ig-mail-only">only requirement for participation (by anyone) in
  1515           the Interest Group is subscription to the Interest Group mailing list</dfn>. This type of Interest Group 
  1516           <em class="rfc2119">may</em> have <a href="#public-participant-ig">public participants</a>.</p>
  1518         <p>A charter <em class="rfc2119">may</em> include additional voting procedures, but those procedures
  1519           <em class="rfc2119">must not</em> conflict with the <a href="#Votes">voting requirements</a> of the Process Document.</p>
  1521         <p>A charter <em class="rfc2119">may</em> include provisions other than those required by this document. The charter
  1522           <em class="rfc2119">should</em> highlight whether additional provisions impose constraints beyond those of the W3C
  1523           Process Document (e.g., limits on the number of individuals in a Working Group who represent the same
  1524           Member organization or group of <a href="#MemberRelated">related Members</a>).</p>
  1526         <h4>5.2.7 <dfn id="GeneralTermination">Working Group and Interest Group Closure</dfn></h4>
  1528         <p>A Working Group or Interest Group charter specifies a duration for the group. The Director
  1529           <em class="rfc2119">may</em> decide to close a group prior to the date specified in the charter in
  1530           any of the following circumstances:</p>
  1532         <ul>
  1533           <li>There are insufficient resources to produce chartered deliverables or to maintain the group, according to
  1534             priorities established within W3C.</li>
  1535           <li>The group produces chartered deliverables ahead of schedule.</li>
  1536         </ul>
  1538         <p>The Director closes a Working Group or Interest Group by announcement to the Advisory Committee.
  1539           Advisory Committee representatives <em class="">may</em> initiate an
  1540           <a href="#ACAppeal">Advisory Committee Appeal</a>.</p>
  1542         <p>Closing a Working Group has implications with respect to the
  1543           <a href="">W3C Patent Policy</a>
  1544           [<a href="#ref-patentpolicy">PUB33</a>].</p>
  1545       </section>
  1547       <h2 id="Reports">6 W3C Technical Report Development Process</h2>
  1549       <p>The W3C technical report development process is the set of steps and requirements followed by W3C
  1550         <a href="#GroupsWG">Working Groups</a> to standardize Web technology. The W3C technical report development process
  1551         is designed to:</p>
  1553       <ul>
  1554         <li>support multiple specification development methodologies</li>
  1555         <li>maximize
  1556           <a href="#def-Consensus" rel="glossary" title="Definition of Consensus"><span class="dfn-instance">consensus</span></a>
  1557           about the content of stable technical reports</li>
  1558         <li>ensure high technical and editorial quality</li>
  1559         <li>promote consistency among specifications</li>
  1560         <li>facilitate royalty-free, interoperable implementations of Web Standards, and</li>
  1561         <li>earn endorsement by W3C and the broader community.</li>
  1562       </ul>
  1564       <p>See also the licensing goals for W3C Recommendations in
  1565         <a href="">section 2</a> of the
  1566         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].
  1567       </p>
  1569       <h3 id="rec-advance">6.1 W3C Technical Reports</h3>
  1571       <p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a
  1572         W3C Technical Report on its <a href="">Technical Reports page</a>.</p>
  1574       <p>This chapter describes the formal requirements for publishing and maintaining a W3C Recommendation or Note.</p>
  1576       <p>Typically a series of Working Drafts are published, each of which refines a document under development to complete
  1577         the scope of work envisioned by a Working Group's charter. For a technical specification, once review suggests the
  1578         Working Group has met their requirements satisfactorily for a new standard, there is a
  1579         <a href="#last-call">Candidate Recommendation</a> phase. This allows the entire W3C membership to provide feedback
  1580         on whether the specification is appropriate as a W3C Recommendation, while the Working Group formally collects
  1581         implementation experience to demonstrate that the specification works in practice. The next phase is a
  1582         Proposed Recommendation, to finalize the review of W3C Members. If the Director determines that W3C Member review
  1583         supports a specification becoming a standard, W3C publishes it as a Recommendation.</p>
  1585       <p>Groups can also publish documents as W3C Notes, typically either to document information other than technical
  1586         specifications, such as use cases motivating a specification and best practices for its use, or to clarify the
  1587         status of work that is abandoned. </p>
  1589       <p>Some W3C Notes are developed through successive Working Drafts, with an expectation that they will become Notes,
  1590         while others are simply published. There are few formal requirements to publish a document as a W3C Note, and they
  1591         have no standing as a recommendation of W3C but are simply documents preserved for historical reference.</p>
  1593       <p>Individual Working Groups and Interest Groups <em class="rfc2119">should</em> adopt additional processes for
  1594         developing publications, so long as they do not conflict with the requirements in this chapter.</p>
  1596       <h4 id="recs-and-notes">6.1.1 Recommendations and Notes</h4>
  1598       <p>W3C follows these steps when advancing a technical report to Recommendation.</p>
  1600       <ol>
  1601         <li>Publication of the <a href="#first-wd">First Public Working Draft</a>,</li>
  1602         <li>Publication of zero or more revised <a href="#revised-wd">Public Working Drafts</a>.</li>
  1603         <li>Publication of a <a href="#last-call">Candidate Recommendation</a>.</li>
  1604         <li>Publication of a <a href="#rec-pr">Proposed Recommendation</a>.</li>
  1605         <li>Publication as a <a href="#rec-publication">W3C Recommendation</a>.</li>
  1606         <li>Possibly, Publication as an <a href="#rec-edited">Edited Recommendation</a></li>
  1607       </ol>
  1609       <p>
  1611 <svg xmlns:xlink="" xmlns="" viewBox="-5 60 630 160" width="100%">
  1612   <title>Flowchart: The basic W3C Recommendation Track</title>
  1613   <g id="basicProcess" role="list">
  1615     <g id="Rectrac-FPWD" role="listitem" aria-labelledby="Rectrac-fpwd-label Rectrac-fpwd-text">
  1616       <title id="Rectrac-fpwd-label">First Public Working Draft - Exclusion Opportunity</title>
  1617       <a xlink:href="#Rectrac-nodeWD">
  1618         <rect fill="white" y="122" width="57" height="45"/>
  1619         <text font-size="8"><tspan y="132" x="0">First WD</tspan>
  1620           <tspan x="0" y="152">WG Decision</tspan>
  1621           <tspan x="0" y="162">Director's approval</tspan></text>
  1622         <path d="M0,140h53" fill="none" stroke="#000"></path>
  1623         <polygon points="47,136 57,140 47,144"></polygon></a>
  1624     </g>
  1626     <g id="Rectrac-nodeWD" role="list" aria-labelledby="Rectrac-nodewd-label">
  1627       <title id="Rectrac-nodewd-label">Working Draft</title>
  1628       <a xlink:href="#RecsWD" aria-labelledby="Rectrac-nodewd-label">
  1629         <ellipse ry="18" rx="38" cy="140" cx="97" stroke="black" fill="#fff"></ellipse>
  1630         <text font-size="14" y="144" x="97" text-anchor="middle">WD</text></a>
  1632 <!-- g[role=listitem] with a link inside it -->
  1634       <g id="Rectrac-repeatWD" role="listitem">
  1635         <a xlink:href="#Rectrac-nodeWD" aria-labelledby="Rectrac-repeatwd-label Rectrac-repeatwd-text">
  1636         <title id="Rectrac-repeatwd-label">Publish a New Working Draft</title>
  1637         <text id="Rectrac-repeatwd-text" font-size="8">
  1638           <tspan x="30" y="92">WG Decision: review needed, or</tspan>
  1639           <tspan x="40" y="100">No change for 6 months</tspan></text>
  1640         <path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114"
  1641           fill="none" stroke="black" stroke-dasharray="6 1"></path>
  1642         <polygon points="120,114 116,124 114,113"></polygon> </a> </g>
  1644       <g id="Rectrac-toCR" role="listitem" fill="#060">
  1645         <a xlink:href="#Rectrac-nodeCR" aria-labelledby="Rectrac-tocr-label Rectrac-tocr-text">
  1646         <title id="Rectrac-tocr-label">Advance to Candidate Recommendation</title> 
  1647         <text role="none" id="Rectrac-tocr-text" x="138" y="134" font-size="8">Director's approval</text>
  1648           <path stroke="#060" d="M135,140h81"></path>
  1649           <polygon points="211,136 221,140 211,144"></polygon></a> </g>
  1650     </g>
  1652     <g id="Rectrac-nodeCR" role="list" aria-labelledby="Rectrac-nodecr-label">
  1653       <title id="Rectrac-nodecr-label">Candidate recommendation - Patent Policy Exclusion Opportunity</title>
  1654       <a xlink:href="#RecsCR">
  1655         <ellipse ry="18" rx="38" cy="140" cx="260" stroke="black" fill="#fff"></ellipse>
  1656         <text font-size="14" y="144" x="260" text-anchor="middle">CR</text></a>
  1658 <!-- a instead of g -->
  1660       <a xlink:href="#Rectrac-nodeCR" id="Rectrac-repeatCR"
  1661         aria-labelledby="Rectrac-repeatcr-label Rectrac-repeatcr-text" fill="#060">
  1662         <title id="Rectrac-repeatcr-label">Publish a revised CR</title>
  1663         <text role="none" font-size="8" id="Rectrac-repeatcr-text">
  1664           <tspan x="225" y="84">Working Group Decision,</tspan>
  1665           <tspan x="240" y="96">Directors approval</tspan></text>
  1666         <path stroke="#000" d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114"
  1667           stroke-dasharray="5 11" fill="none"></path>
  1668         <path stroke="#060" d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114"
  1669           stroke-dasharray="5 11" stroke-dashoffset="8" fill="none"></path>
  1670         <polygon points="282,114 277,124 275,113"></polygon> </a>
  1672       <a xlink:href="#Rectrac-nodePR" id="Rectrac-ToPR"
  1673         aria-labelledby="Rectrac-topr-label Rectrac-topr-text" fill="#060">
  1674         <title id="Rectrac-topr-label">Advance to Proposed Recommendation</title> 
  1675         <text role="none" id="Rectrac-topr-text" x="300" y="134" font-size="8">Director's approval</text>
  1676         <path d="M298,140h77" stroke="#060"></path>
  1677         <polygon points="374,136 384,140 374,144"></polygon> </a>
  1679       <a xlink:href="#Rectrac-nodeWD" id="Rectrac-backToWD"
  1680         aria-labelledby="Rectrac-backtowd-label Rectrac-backtowd-text" fill="#600">
  1681         <title id="Rectrac-backtowd-label">Return to Working Draft</title> 
  1682         <text role="none" id="Rectrac-backtowd-text" font-size="8">
  1683           <tspan x="142" y="160">WG or Director decision</tspan>
  1684           <tspan x="144" y="170">e.g. for further review</tspan></text>
  1685         <path d="M140,147h84" stroke-dasharray="4 4" stroke="#600"></path>
  1686         <polygon points="140,145 133,147 140,149"></polygon> </a>
  1687     </g>
  1689     <g id="Rectrac-nodePR" role="list" aria-labelledby="Rectrac-nodepr-label">
  1690       <title id="Rectrac-nodepr-label">Proposed Recommendation - Advisory Committee Review</title>
  1691       <a xlink:href="#RecsPR">
  1692         <ellipse ry="18" rx="28" cy="140" cx="413" stroke="black" fill="#fff"></ellipse>
  1693         <text font-size="14" font-family="Times,serif" y="144" x="413" text-anchor="middle">PR</text></a>
  1695 <!-- use a[role=listitem] instead of g -->
  1697       <a xlink:href="#Rectrac-nodeRec" id="Rectrac-ToRec" role="listitem"
  1698         aria-labelledby="Rectrac-torec-label Rectrac-torec-text" fill="#060">
  1699         <title id="Rectrac-torec-label">Advance to Recommendation</title> 
  1700         <text role="none" id="Rectrac-torec-text" x="300" y="138" font-size="8">  
  1701           <tspan x="445" y="124">Advisory Committee Review</tspan>
  1702           <tspan x="445" y="134">Director's Decision</tspan></text>
  1704         <path d="M441,140h100" stroke="#060"></path>
  1705         <polygon points="534,136 544,140 534,144"></polygon> </a>
  1707       <a xlink:href="#Rectrac-nodeCR" id="Rectrac-BackToCR" role="listitem"
  1708         aria-labelledby="Rectrac-backtocr-label Rectrac-backtocr-text" fill="#600">
  1709         <title id="Rectrac-backtocr-label">Return to Working Draft</title> 
  1710         <text id="Rectrac-backtocr-text" font-size="8">
  1711           <tspan x="306" y="160">AC Review, </tspan>
  1712           <tspan x="302" y="170">Director Decision</tspan>
  1713           <tspan x="304" y="180">e.g. for minor changes</tspan></text>
  1714         <path d="M301,147h88" stroke-dasharray="3 5" stroke="#600"></path>
  1715         <polygon points="301,145 296,147 301,149"></polygon> </a>
  1717       <a xlink:href="#Rectrac-nodeWD" id="Rectrac-PRBackToWD" role="listitem"
  1718         aria-labelledby="Rectrac-prbacktowd-label Rectrac-prbacktowd-text" fill="#c00">
  1719         <title id="Rectrac-prbacktowd-label">Return to Working Draft</title> 
  1720         <text role="none" id="Rectrac-prbacktowd-text" font-size="9">
  1721           <tspan x="90" y="202">Advisory Committee review and Director's Decision, e.g. for further work and review</tspan></text>
  1722         <path d="M413,158v32h-316v-26" stroke-dasharray="2 2" stroke="#c00" fill="none"></path>
  1723         <polygon points="95,164 97,159 99,164"></polygon> </a>
  1724     </g>
  1726     <g id="Rectrac-nodeRec" stroke="black" aria-labelledby="Rectrac-noderec-label" role="list">
  1727       <title id="Rectrac-noderec-label">W3C Recommendation</title>
  1728       <a xlink:href="#RecsW3C" aria-labelledby="Rectrac-noderec-label">
  1729         <ellipse ry="18" rx="28" cy="140" cx="573" fill="#fff" stroke-width="2"></ellipse>
  1730         <text font-size="16" y="144" x="573"
  1731           text-anchor="middle" stroke-width=".3">REC</text></a>
  1734   </g>
  1735  </g>
  1737 </svg>
  1738       </p>
  1740       <p>W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.</p>
  1742       <p>The Director <em class="rfc2119">may</em> decline a request to advance in maturity level, requiring a Working Group
  1743         to conduct further work, and <em class="rfc2119">may</em> require the specification to return to a lower
  1744         <a href="#maturity-levels">maturity level</a>. The Director <em class="rfc2119">must</em> inform the
  1745         <a href="#AC">Advisory Committee</a> and Working Group Chairs when a Working Group's request for a specification
  1746         to advance in maturity level is declined and the specification is returned to a Working Group for further work.</p>
  1748       <h4 id="maturity-levels">6.1.2 Maturity Levels</h4>
  1750       <dl>
  1751         <dt id="RecsWD">Working Draft (WD)</dt>
  1752         <dd>A Working Draft is a document that W3C has published for review by the community, including W3C Members, the public,
  1753           and other technical organizations. Some, but not all, Working Drafts are meant to advance to Recommendation; see the
  1754           <a href="#DocumentStatus">document status section</a> of a Working Draft for the group's expectations. Any
  1755           Working Draft not, or no longer, intended to advance to Recommendation <em class="rfc2119">should</em> be
  1756           published as a Working Group Note. Working Drafts do not necessarily represent a consensus of the Working Group,
  1757           and do not imply any endorsement by W3C or its members beyond agreement to work on a general area of technology.</dd>
  1758         <dt id="RecsCR">Candidate Recommendation (CR)</dt>
  1759         <dd class="changed">A Candidate Recommendation is a document that satisfies the Working Group's technical requirements,
  1760           and has already received wide review. W3C publishes a Candidate Recommendation to
  1761           <ul>
  1762             <li>signal to the wider community that it is time to do a final review</li>
  1763             <li>gather <a href="#implementation-experience">implementation experience</a></li>
  1764             <li>begin formal review by the Advisory Committee, who <em class="rfc2119">may</em> recommend that the document
  1765               be published as a W3C Recommendation, returned to the Working Group for further work, or abandoned.</li>
  1766             <li>Provide an exclusion opportunity per the
  1767               <a href="">W3C Patent Policy</a>
  1768               [<a href="#ref-patentpolicy">PUB33</a>]. <strong>Note</strong>: A Candidate Recommendation under this process
  1769               corresponds to the "Last Call Working Draft" discussed in the Patent Policy.</li>
  1770           </ul>
  1771         </dd>
  1772         <dd><strong>Note</strong>: Candidate Recommendations are expected to be acceptable as Recommendations. Announcement of a
  1773           different next step <em class="rfc2119">should</em> include the reasons why the change in expectations comes at so late
  1774           a stage.</dd>
  1775         <dt id="RecsPR">Proposed Recommendation</dt>
  1776         <dd>A Proposed Recommendation is a document that has been accepted by the W3C Director as of sufficient quality to become
  1777           a W3C Recommendation. This phase establishes a deadline for the Advisory Committee review that begins with
  1778           Candidate Recommendation. Substantive changes <em class="rfc2119">must</em> not be made to a Proposed Recommendation
  1779           except by publishing a new Working Draft or Candidate Recommendation.</dd>
  1780         <dt id="RecsW3C">W3C Recommendation (REC)</dt>
  1781         <dd>A W3C Recommendation is a specification or set of guidelines or requirements that, after extensive
  1782           consensus-building, has received the endorsement of W3C Members and the Director. W3C recommends the wide deployment
  1783           of its Recommendations as standards for the Web. The W3C Royalty-Free IPR licenses granted under the 
  1784           <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]
  1785           apply to W3C Recommendations.</dd>
  1786         <dt id="RecsObs">Obsolete Recommendation</dt>
  1787          <dd>An Obsolete Recommendation is a specification that W3C does not believe has sufficient market relevance to continue
  1788          recommending that the community implement it, but does not consider that there are fundamental problems that require the 
  1789          Recommendation be Rescinded. It is possible for an Obsolete Recommendation to receive sufficient market uptake that W3C
  1790          decides to restore it to Recommendation status. An Obsolete Recommendation has the same status as a W3C Recommendation 
  1791          with regards to W3C Royalty-Free IPR licenses granted under the Patent Policy.</dd>
  1792         <dt id="RescindedRec">Rescinded Recommendation</dt>
  1793         <dd>A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses, and believes is unlikely to ever
  1794            be restored to Recommendation Status. See also clause 10 of the licensing
  1795           requirements for W3C Recommendations in
  1796           <a href="">section 5</a> of the
  1797           <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</dd>
  1798         <dt id="WGNote">Working Group Note, Interest Group Note (NOTE) </dt>
  1799         <dd>A Working Group Note or Interest Group Note is published by a chartered Working Group or Interest Group to provide
  1800           a stable reference for a useful document that is not intended to be a formal standard, or to document work that was
  1801           abandoned without producing a Recommendation.</dd>
  1802       </dl>
  1804       <p>Working Groups and Interest Groups <em class="rfc2119">may</em> make available "Editor's drafts". Editor's drafts have
  1805         no official standing whatsoever, and do not necessarily imply consensus of a Working Group or Interest Group, nor are
  1806         their contents endorsed in any way by W3C.</p>
  1808       <h3 id="requirements-and-definitions">6.2 General requirements and definitions</h3>
  1810       <p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a
  1811         W3C Technical Report on its <a href="">Technical Reports page</a>
  1812         [<a href="#ref-doc-list">PUB11</a>].</p>
  1814       <h4 id="general-requirements">6.2.1 General requirements for Technical Reports</h4>
  1816       <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be
  1817         a public document. The <a href="">index of W3C technical reports</a>
  1818         [<a href="#ref-doc-list">PUB11</a>] is available at the W3C Web site. W3C strives to make archival documents
  1819         indefinitely available at their original address in their original form.</p>
  1821       <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly
  1822         indicate its <a href="#maturity-levels">maturity level</a>, and <em id="DocumentStatus" class="rfc2119">must</em>
  1823         include information about the status of the document. This status information</p>
  1825       <ul>
  1826         <li><em class="rfc2119">must</em> be unique each time a specification is published,</li>
  1827         <li><em class="rfc2119">must</em> state which Working Group developed the specification, </li>
  1828         <li><em class="rfc2119">must</em> state how to send comments or file bugs, and where these are recorded, </li>
  1829         <li><em class="rfc2119">must</em> include expectations about next steps,</li>
  1830         <li><em class="rfc2119">should</em> explain how the technology relates to existing international standards and
  1831           related work inside or outside W3C, and</li>
  1832         <li><em class="rfc2119">should</em> explain or link to an explanation of significant changes from the previous version.</li>
  1833       </ul>
  1835       <p>Every Technical Report published as part of the Technical Report development process is edited by one or more editors
  1836         appointed by a Group Chair. It is the responsibility of these editors to ensure that the decisions of the Group are
  1837         correctly reflected in subsequent drafts of the technical report. An editor <em class="rfc2119">must</em> be a
  1838         participant, per <a href="#group-participation">section 5.2.1</a> in the Group responsible for the document(s) they are
  1839         editing. </p>
  1840       <p>The Team is <em class="rfc2119">not required</em> to publish a Technical Report that does not conform to the Team's
  1841         <a href="">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>](e.g., for
  1842         <span id="DocumentName">naming</span>, status information, style, and
  1843         <span id="document-copyright">copyright requirements</span>). These rules are subject to change by the Team from
  1844         time to time. The Team <em class="rfc2119">must</em> inform group Chairs and the Advisory Committee of any changes to
  1845         these rules.</p>
  1846       <p>The primary language for W3C Technical Reports is English. W3C encourages the translation of its Technical Reports.
  1847         <a href="">Information about translations of W3C technical reports</a>
  1848         [<a href="#ref-translations">PUB18</a>] is available at the W3C Web site.</p>
  1850       <h4 id="transition-reqs">6.2.2 Advancement on the Recommendation Track</h4>
  1852       <p>For <em>all</em> <dfn>Transition Requests</dfn>, to advance a specification to a new maturity level other than Note,
  1853         the Working Group:</p>
  1855       <ul>
  1856         <li><em class="rfc2119">must</em> record the group's decision to request advancement.</li>
  1857         <li><em class="rfc2119">must </em> obtain Director approval.</li>
  1858         <li><em class="rfc2119 ">must</em> provide public documentation of all
  1859           <a href="#substantive-change">substantive changes</a> to the
  1860           technical report since the previous publication.</li>
  1861         <li><em class="rfc2119">must</em> <a href="#formal-address">formally address</a> all issues raised about the document
  1862           since the previous maturity level.</li>
  1863         <li><em class="rfc2119">must</em> provide public documentation of any <a href="#FormalObjection">Formal Objections</a>.</li>
  1864         <li><em class="rfc2119">should</em> provide public documentation of changes that are not substantive.</li>
  1865         <li><em class="rfc2119">should</em> report which, if any, of the Working Group's requirements for this document have 
  1866           changed since the previous step.</li>
  1867         <li><em class="rfc2119">should</em> report any changes in dependencies with other groups.</li>
  1868         <li><em class="rfc2119">should</em> provide information about implementations known to the Working Group.</li>
  1869       </ul>
  1871       <p>For a First Public Working Draft there is no "previous maturity level", so many requirements do not apply, and
  1872         approval is normally fairly automatic. For later stages, especially transition to Candidate or Proposed Recommendation,
  1873         there is usually a formal review meeting to ensure the requirements have been met before Director's approval is given.</p>
  1875       <p>Transition Requests to First Public Working Draft or <a href="#last-call">Candidate Recommendation</a> will not normally 
  1876         be approved while a Working Group's charter is undergoing or awaiting a Director's decision on an
  1877         Advisory Committee Review.</p>
  1879       <h4 id="doc-reviews">6.2.3 Reviews and Review Responsibilities</h4>
  1881       <p>A document is available for review from the moment it is first published. Working Groups <em class="rfc2119">should</em>
  1882         <a href="#formal-address">formally address</a> <em>any</em> substantive review comment about a technical report in a
  1883         timely manner. </p>
  1884       <p>Reviewers <em class="rfc2119">should</em> send substantive technical reviews as early as possible. Working Groups are
  1885         often reluctant to make <a href="#substantive-change">substantive changes</a> to a mature document, particularly if this
  1886         would cause significant compatibility problems due to existing implementation. Working Groups
  1887         <em class="rfc2119">should</em> record substantive or interesting proposals raised by reviews but not incorporated into
  1888         a current specification.
  1890       <h5 id="wide-review"> Wide Review</h5>
  1892       <p>The requirements for wide review are not precisely defined by the W3C Process. The objective is to ensure that the
  1893         entire set of stakeholders of the Web community, including the general public, have had adequate notice of the progress
  1894         of the Working Group (for example through notices posted to
  1895         <a href=""></a>) and were able to actually perform
  1896         reviews of and provide comments on the specification. A second objective is to encourage groups to request reviews
  1897         early enough that comments and suggested changes can still be reasonably incorporated in response to the review. Before
  1898         approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the
  1899         document, who has provided comments, the record of requests to and responses from reviewers, especially
  1900         <a href="">W3C Horizontal Groups</a> and groups identified as
  1901         dependencies in the charter or identified as <a href="">liaisons</a>
  1902         [<a href="#ref-liaison-list">PUB29</a>], and seek evidence of clear communication to the general public about appropriate
  1903         times and which content to review and whether such reviews actually occurred. </p>
  1905       <p>For example, inviting review of new or significantly revised sections published in Working Drafts, and tracking those
  1906         comments and the Working Group's responses, is generally a good practice which would often be considered
  1907         positive evidence of wide review. Working Groups <em class="rfc2119">should</em> announce to other W3C Working Groups
  1908         as well as the general public, especially those affected by this specification, a proposal to enter
  1909         <a href="#last-call">Candidate Recommendation</a> (for example in approximately four weeks). By contrast a
  1910         generic statement in a document requesting review at any time is likely not to be considered as sufficient evidence
  1911         that the group has solicited wide review. </p>
  1913       <p>A Working Group could present evidence that wide review has been received, irrespective of solicitation. But it is
  1914         important to note that receiving many detailed reviews is not necessarily the same as wide review, since they might only
  1915         represent comment from a small segment of the relevant stakeholder community.</p>
  1917       <h4 id="implementation-experience">6.2.4 Implementation Experience</h4>
  1919       <p>Implementation experience is required to show that a specification is sufficiently clear, complete, and relevant to market
  1920         needs, to ensure that independent interoperable implementations of each feature of the specification will be realized.
  1921         While no exhaustive list of requirements is provided here, when assessing that there is
  1922         <dfn>adequate implementation experience</dfn> the Director will consider (though not be limited to):</p>
  1923       <ul>
  1924         <li>is each feature of the current specification implemented, and how is this demonstrated?</li>
  1925         <li>are there independent interoperable implementations of the current specification?</li>
  1926         <li>are there implementations created by people other than the authors of the specification?</li>
  1927         <li>are implementations publicly deployed?</li>
  1928         <li>is there implementation experience at all levels of the specification's ecosystem (authoring, consuming, publishing…)?</li>
  1929         <li>are there reports of difficulties or problems with implementation?</li>
  1930       </ul>
  1931       <p>Planning and accomplishing a demonstration of (interoperable) implementations can be very time consuming. Groups are
  1932         often able to work more effectively if they plan how they will demonstrate interoperable implementations early in the
  1933         development process; for example, developing tests in concert with implementation efforts.</p>
  1935       <h4 id="correction-classes">6.2.5 Classes of Changes</h4>
  1937       <p>This document distinguishes the following 4 classes of changes to a specification. The first two classes of change are
  1938         considered <dfn id="editorial-change">editorial changes</dfn>, the latter two
  1939         <dfn id="substantive-change">substantive changes</dfn>.</p>
  1940       <dl>
  1941         <dt>1. No changes to text content</dt>
  1942         <dd>These changes include fixing broken links, style sheets or invalid markup.</dd>
  1943         <dt>2. Corrections that do not affect conformance</dt>
  1944         <dd>Changes that reasonable implementers would not interpret as changing architectural or interoperability requirements
  1945           or their implementation. Changes which resolve ambiguities in the specification are considered to change 
  1946           (by clarification) the implementation requirements and do not fall into this class.</dd>
  1947         <dd>Examples of changes in this class include correcting non-normative code examples where the code clearly conflicts with
  1948           normative requirements, clarifying informative use cases or other non-normative text, fixing typos or grammatical errors
  1949           where the change does not change implementation requirements. If there is any doubt or dissent as to whether requirements
  1950           are changed, such changes do not fall into this class.</dd>
  1951         <dt>3. Corrections that do not add new features</dt>
  1952         <dd>These changes <em class="rfc2119">may</em> affect conformance to the specification. A change that affects conformance
  1953           is one that:
  1954           <ul>
  1955             <li>makes conforming data, processors, or other conforming agents become non-conforming according to the new version,
  1956               or</li>
  1957             <li>makes non-conforming data, processors, or other agents become conforming, or</li>
  1958             <li>clears up an ambiguity or under-specified part of the specification in such a way that data, a processor, or an
  1959               agent whose conformance was once unclear becomes clearly either conforming or non-conforming.</li>
  1960           </ul>
  1961         </dd>
  1962         <dt>4. New features</dt>
  1963         <dd>Changes that add a new functionality, element, etc.</dd>
  1964       </dl>
  1966       <h3 id="working-draft">6.3 Working Draft</h3>
  1968       <p>A Public Working Draft is published on the <a href="">W3C's Technical Reports page</a>
  1969        [<a href="#ref-doc-list">PUB11</a>] for review, and for simple historical reference. For all Public Working Drafts a
  1970        Working Group:</p>
  1971       <ul>
  1972         <li> <em class="rfc2119">should</em> document outstanding issues, and parts of the document on which the Working Group
  1973           does not have consensus, and</li>
  1974         <li> <em class="rfc2119">may</em> request publication of a Working Draft even if its content is considered unstable
  1975           and does not meet all Working Group requirements.</li>
  1976       </ul>
  1978       <h4 id="first-wd">6.3.1 First Public Working Draft</h4>
  1980       <p>To publish the First Public Working Draft of a document, a Working Group <em class="rfc2119">must</em> meet the
  1981         applicable <a href="#transition-reqs">general requirements for advancement</a>.</p>
  1982       <p>The Director <em class="rfc2119">must</em> announce the publication of a First Public Working Draft publication to
  1983         other W3C groups and to the public. </p>
  1984       <p>Publishing the First Public Working Draft triggers a Call for Exclusions, per
  1985         <a href="">section 4</a> of the
  1986         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
  1988       <h4 id="revised-wd">6.3.2 Revising Public Working Drafts</h4>
  1990       <p>A Working Group <em class="rfc2119">should</em> publish a Working Draft to the W3C Technical Reports page when there have
  1991         been significant changes to the previous published document that would benefit from review beyond the Working Group. </p>
  1992       <p>If 6 months elapse without significant changes to a specification a Working Group <em class="rfc2119">should</em> publish
  1993         a revised Working Draft, whose status section <em class="rfc2119">should</em> indicate reasons for the lack of change.</p>
  1994       <p>To publish a revision of a Working draft, a Working Group:</p>
  1995       <ul>
  1996         <li><em class="rfc2119">must</em> record the group's decision to request publication. Consensus is not required, as this
  1997           is a procedural step,</li>
  1998         <li><em class="rfc2119">must</em> provide public documentation of <a href="#substantive-change">substantive changes</a>
  1999           to the technical report since the previous Working Draft,</li>
  2000         <li><em class="rfc2119">should</em> provide public documentation of significant
  2001           <a href="#editorial-change">editorial changes</a> to the technical report since the previous step,</li>
  2002         <li><em class="rfc2119">should</em> report which, if any, of the Working Group's requirements for this document
  2003           have changed since the previous step,</li>
  2004         <li><em class="rfc2119">should</em> report any changes in dependencies with other groups,</li>
  2005       </ul>
  2006       <p>Possible next steps for any Working Draft:</p>
  2007       <ul>
  2008         <li>Revised <a href="#revised-wd">Public Working Draft</a></li>
  2009         <li><a href="#last-call">Candidate recommendation</a>.</li>
  2010         <li><a href="#Note">Working Group Note</a></li>
  2011       </ul>
  2012       <h4 id="tr-end">6.3.3 Stopping Work on a specification</h4>
  2013       <p>Work on a technical report <em class="rfc2119">may</em> cease at any time. Work <em class="rfc2119 new">should</em>
  2014         cease if W3C or a Working Group determines that it cannot productively carry the work any further. If the Director
  2015         <a href="#GeneralTermination">closes a Working Group</a> W3C <em class="rfc2119">must </em> publish any unfinished
  2016         specifications on the Recommendation track as <a href="#Note">Working Group Notes</a>. If a Working group decides, or
  2017         the Director requires, the Working Group to discontinue work on a technical report before completion, the Working Group
  2018         <em class="rfc2119">should</em> publish the document as a <a href="#Note">Working Group Note</a>. </p>
  2020       <h3 id="candidate-rec"><a id="last-call">6.4 Candidate Recommendation </a></h3>
  2022       <p>To publish a Candidate recommendation, in addition to meeting the
  2023         <a href="#transition-reqs">general requirements for advancement</a> a Working Group:</p>
  2024       <ul>
  2025         <li><em class="rfc2119">must</em> show that the specification has met all Working Group requirements, or explain why the
  2026           requirements have changed or been deferred,</li>
  2027         <li><em class="rfc2119">must</em> document changes to dependencies during the development of the specification,</li>
  2028         <li><em class="rfc2119">must</em> document how adequate <a href="#implementation-experience"> implementation experience</a>
  2029           will be demonstrated,</li>
  2030         <li><em class="rfc2119">must</em> specify the deadline for comments, which <em class="rfc2119">must</em> be 
  2031           <strong>at least</strong> four weeks after publication, and <em class="rfc2119">should</em> be longer for
  2032           complex documents,</li>
  2033         <li><em class="rfc2119">must</em> show that the specification has received <a href="#wide-review">wide review</a>, and</li>
  2034         <li><em class="rfc2119">may</em> identify features in the document as "at risk". These features
  2035           <em class="rfc2119">may</em> be removed before advancement to Proposed Recommendation without a requirement to publish a
  2036           new Candidate Recommendation.</li>
  2037       </ul>
  2038       <p>The Director <em class="rfc2119">must</em> announce the publication of a Candidate Recommendation to other W3C groups
  2039         and to the public, and <em class="rfc2119">must</em> begin an Advisory Committee Review on the question of whether the
  2040         specification is appropriate to publish as a W3C Recommendation.</p>
  2041       <p> A Candidate Recommendation corresponds to a "Last Call Working Draft" as used in the
  2042         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].
  2043         Publishing a Candidate Recommendation triggers a Call for Exclusions, per
  2044         <a href="">section 4</a> of the
  2045         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
  2046       <p>Possible next steps:</p>
  2047       <ul>
  2048         <li>Return to <a href="#revised-wd">Working Draft</a></li>
  2049         <li>A revised <a href="#last-call">Candidate Recommendation</a></li>
  2050         <li><a href="#rec-pr">Proposed Recommendation</a> (The expected next step)</li>
  2051         <li><a href="#Note">Working Group Note</a></li>
  2052       </ul>
  2053       <p><a href="#AC">Advisory Committee</a> representatives <em class="rfc2119">may</em> initiate an
  2054         <a href="#ACAppeal">Advisory Committee Appeal</a> of the decision to advance the technical report.</p>
  2056       <h4 id="revised-cr">6.4.1 Revising a Candidate Recommendation</h4>
  2058       <p>If there are any <a href="#substantive-change">substantive changes</a> made to a Candidate Recommendation other than to
  2059         remove features explicitly identified as "at risk", the Working Group <em class="rfc2119">must</em> obtain the Director's
  2060         approval to publish a revision of a Candidate Recommendation. This is because substantive changes will generally require a
  2061         new Exclusion Opportunity per <a href="">section 4</a> of the
  2062         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].
  2063         Note that approval is <em>expected</em> to be fairly simple compared to getting approval for a transition from
  2064         Working Draft to Candidate Recommendation.</p>
  2066       <p>In addition the Working Group:</p>
  2067       <ul>
  2068         <li><em class="rfc2119">must</em> show that the revised specification meets all Working Group requirements, or explain
  2069           why the requirements have changed or been deferred,</li>
  2070         <li><em class="rfc2119">must</em> specify the deadline for further comments, which <em class="rfc2119">must</em> be
  2071           <strong>at least</strong> four weeks after publication, and <em class="rfc2119">should</em> be longer for
  2072           complex documents,</li>
  2073         <li><em class="rfc2119">must</em> document the changes since the previous Candidate Recommendation, </li>
  2074         <li><em class="rfc2119">must</em> show that the proposed changes have received <a href="#wide-review">wide review</a>,
  2075           and</li>
  2076         <li><em class="rfc2119">may</em> identify features in the document as "at risk". These features
  2077           <em class="rfc2119">may</em> be removed before advancement to Proposed Recommendation without a requirement to publish a
  2078           new Candidate Recommendation.</li>
  2079       </ul>
  2080       <p>The Director <em class="rfc2119">must</em> announce the publication of a revised Candidate Recommendation to 
  2081         other W3C groups and the Public.</p>
  2083       <h3 id="rec-pr">6.5 Proposed Recommendation</h3>
  2084       <p>In addition to meeting the <a href="#transition-reqs">general requirements for advancement</a>,</p>
  2085       <ul>
  2086         <li>The status information <em class="rfc2119">must</em> specify the deadline for Advisory Committee review, which
  2087           <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after the publication of the
  2088           Proposed Recommendation and <em class="rfc2119">should</em> be at least 10 days after the end of the
  2089           last Exclusion Opportunity per
  2090           <a href="">section 4</a> of the
  2091           <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</li>
  2092       </ul>
  2093       <p>A Working Group:</p>
  2094       <ul>
  2095         <li><em class="rfc2119">must</em> show adequate <a href="#implementation-experience">implementation experience</a>
  2096           except where an exception is approved by the Director,</li>
  2097         <li><em class="rfc2119">must</em> show that the document has received <a href="#wide-review">wide review,</a></li>
  2098         <li><em class="rfc2119">must</em> show that all issues raised during the Candidate Recommendation review period other
  2099           than by Advisory Committee representatives acting in their formal AC representative role have been
  2100           <a href="#formal-address">formally addressed</a>,</li>
  2101         <li><em class="rfc2119">must </em>identify any substantive issues raised since the close of the Candidate Recommendation
  2102           review period by parties other than Advisory Committee representatives acting in their formal AC representative role,</li>
  2103         <li><em class="rfc2119">may</em> have removed features identified in the Candidate Recommendation document as "at risk"
  2104           without republishing the specification as a Candidate Recommendation.</li>
  2105       </ul>
  2106       <p>The Director:</p>
  2107       <ul>
  2108         <li><em class="rfc2119">must</em> announce the publication of a Proposed Recommendation to the
  2109           <a href="#AC">Advisory Committee</a>, and</li>
  2110         <li><span><em class="rfc2119">may</em> approve a Proposed Recommendation with minimal implementation experience where
  2111           there is a compelling reason to do so. In such a case, the Director <em class="rfc2119">should</em> explain the
  2112           reasons for that decision.</span></li>
  2113       </ul>
  2114       <p>Since a W3C Recommendation <em class="rfc2119">must not</em> include any substantive changes from the
  2115         Proposed Recommendation it is based on, to make any substantive change to a Proposed Recommendation the Working Group
  2116         <em class="rfc2119">must</em> return the specification to <a href="#last-call">Candidate Recommendation</a> or
  2117         Working Draft.</p>
  2118       <p>Possible Next Steps:</p>
  2119       <ul>
  2120         <li>Return to <a href="#revised-wd">Working Draft</a></li>
  2121         <li>Return to <a href="#last-call">Candidate Recommendation</a></li>
  2122         <li><a href="#rec-publication">Recommendation status</a> (The expected next step)</li>
  2123         <li><a href="#Note">Working Group Note</a></li>
  2124       </ul>
  2125       <p><a href="#AC">Advisory Committee</a> representatives <em class="rfc2119">may</em> initiate an
  2126         <a href="#ACAppeal">Advisory Committee Appeal</a> of the decision to advance the technical report.</p>
  2128       <h3 id="rec-publication">6.6 W3C Recommendation</h3>
  2129       <p>The decision to advance a document to Recommendation is a <a href="#def-w3c-decision">W3C Decision</a>.</p>
  2130       <p>In addition to meeting the <a href="#transition-reqs">general requirements for advancement</a>,</p>
  2131       <ul>
  2132         <li>A Recommendation <em class="rfc2119">must</em> identify where errata are tracked, and</li>
  2133         <li>A Recommendation <em class="rfc2119">must not</em> include any substantive changes from the Proposed Recommendation
  2134           on which it is based.</li>
  2135         <li>If there was any
  2136           <a href="#def-Dissent" rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
  2137           in Advisory Committee reviews, the Director <em class="rfc2119">must</em> publish the substantive content of the dissent
  2138           to W3C and the general public, and <em class="rfc2119">must</em> <a href="#formal-address">formally address</a>
  2139           the comment at least 14 days before publication as a W3C Recommendation.</li>
  2140         <li><a href="#AC">Advisory Committee</a> representatives <em class="rfc2119">may</em> initiate an
  2141           <a href="#ACAppeal">Advisory Committee Appeal</a> of the W3C decision</li>
  2142         <li>The Director <em class="rfc2119">must</em> announce the publication of a W3C Recommendation to <a href="#AC">Advisory
  2143             Committee</a>, other W3C groups and to the public.</li>
  2144       </ul>
  2145       <p>Possible next steps:</p>
  2146       <p>A W3C Recommendation normally retains its status indefinitely. However it</p>
  2147       <ul>
  2148         <li><em class="rfc2119">may</em> be republished as an <a href="#rec-modify">(Edited) Recommendation</a>, or</li>
  2149         <li><em class="rfc2119">may</em> be <a href="#rec-rescind">rescinded</a>.</li>
  2150       </ul>
  2152       <h3 id="rec-modify">6.7 Modifying a W3C Recommendation</h3>
  2154       <p>This section details the management of errors in, and the process for making changes to a Recommendation. Please see also
  2155         the <a href="">Requirements for modification of W3C Technical Reports</a>
  2156         [<a href="#in-place-tr-mod">PUB35</a>].</p>
  2157       <p>
  2159 <svg xmlns:xlink="" xmlns="" viewBox="-10 60 635 240" width="100%">
  2160   <title>Flowchart: Revising a W3C Recommendation</title>
  2161   <g id="Rectrac-basicProcess" role="list">
  2163     <g id="Modif-FPWD" role="listitem" aria-labelledby="modif-fpwd-label modif-fpwd-text">
  2164       <title id="modif-fpwd-label">First Public Working Draft - Exclusion Opportunity</title>
  2165       <a xlink:href="#Modif-nodeWD">
  2166         <rect fill="white" y="122" width="57" height="45"/>
  2167         <text font-size="8"><tspan y="136" x="0">First WD</tspan>
  2168           <tspan x="0" y="154">WG Decision</tspan>
  2169           <tspan x="0" y="166">Director's approval</tspan></text>
  2170         <path d="M0,140h53" fill="none" stroke="#000"></path>
  2171         <polygon points="47,136 57,140 47,144"></polygon></a>
  2172     </g>
  2174     <g id="Modif-nodeWD" role="list" aria-labelledby="modif-nodewd-label">
  2175       <title id="modif-nodewd-label">Working Draft</title>
  2176       <a xlink:href="#RecsWD" aria-labelledby="modif-nodewd-label">
  2177         <ellipse ry="18" rx="38" cy="140" cx="97" stroke="black" fill="#fff"></ellipse>
  2178         <text font-size="14" y="144" x="97" text-anchor="middle">WD</text></a>
  2181       <g id="Modif-repeatWD" role="listitem">
  2182         <a xlink:href="#Modif-nodeWD" aria-labelledby="modif-repeatwd-label modif-repeatwd-text">
  2183         <title id="modif-repeatwd-label">Publish a New Working Draft</title>
  2184         <text id="modif-repeatwd-text" font-size="8">
  2185           <tspan x="30" y="84">WG Decision: review needed, or</tspan>
  2186           <tspan x="40" y="96">No change for 6 months</tspan></text>
  2187         <path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114"
  2188           fill="none" stroke="black" stroke-dasharray="6 1"></path>
  2189         <polygon points="120,114 116,124 114,113"></polygon> </a> </g>
  2191       <g id="Modif-toCR" role="listitem" fill="#060">
  2192         <a xlink:href="#Modif-nodeCR" aria-labelledby="modif-tocr-label modif-tocr-text">
  2193         <title id="modif-tocr-label">Advance to Candidate Recommendation</title> 
  2194         <text role="none" id="modif-tocr-text" x="138" y="136" font-size="8">Director's approval</text>
  2195           <path stroke="#060" d="M135,140h81"></path>
  2196           <polygon points="211,136 221,140 211,144"></polygon></a> </g>
  2197     </g>
  2199     <g id="Modif-nodeCR" role="list" aria-labelledby="modif-nodecr-label">
  2200       <title id="modif-nodecr-label">Candidate recommendation - Patent Policy Exclusion Opportunity</title>
  2201       <a xlink:href="#RecsCR">
  2202         <ellipse ry="18" rx="38" cy="140" cx="260" stroke="black" fill="#fff"></ellipse>
  2203         <text font-size="14" y="144" x="260" text-anchor="middle">CR</text></a>
  2205 <!-- use a instead of g -->
  2207       <a xlink:href="#Modif-nodeCR" id="Modif-repeatCR"
  2208         aria-labelledby="modif-repeatcr-label modif-repeatcr-text" fill="#060">
  2209         <title id="modif-repeatcr-label">Publish a revised CR</title>
  2210         <text role="none" font-size="8" id="modif-repeatcr-text">
  2211           <tspan x="225" y="84">Working Group Decision,</tspan>
  2212           <tspan x="240" y="96">Directors approval</tspan></text>
  2213         <path stroke="#000" d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114"
  2214           stroke-dasharray="5 11" fill="none"></path>
  2215         <path stroke="#060" d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114"
  2216           stroke-dasharray="5 11" stroke-dashoffset="8" fill="none"></path>
  2217         <polygon points="275,114 277,124 282,113"></polygon> </a>
  2219       <a xlink:href="#Modif-nodePR" id="Modif-ToPR"
  2220         aria-labelledby="modif-topr-label modif-topr-text" fill="#060">
  2221         <title id="modif-topr-label">Advance to Proposed Recommendation</title> 
  2222         <text role="none" id="modif-topr-text" x="300" y="136" font-size="8">Director's approval</text>
  2223         <path d="M298,140h77" stroke="#060"></path>
  2224         <polygon points="374,136 384,140 374,144"></polygon> </a>
  2226       <a xlink:href="#Modif-nodeWD" id="Modif-backToWD"
  2227         aria-labelledby="modif-backtowd-label modif-backtowd-text" fill="#600">
  2228         <title id="modif-backtowd-label">Return to Working Draft</title> 
  2229         <text role="none" id="modif-backtowd-text" font-size="8">
  2230           <tspan x="140" y="160">WG or Director decision</tspan>
  2231           <tspan x="142" y="172">e.g. for further review</tspan></text>
  2232         <path d="M140,147h84" stroke-dasharray="4 4" stroke="#600"></path>
  2233         <polygon points="140,145 133,147 140,149"></polygon> </a>
  2234     </g>
  2236     <g id="Modif-nodePR" role="list" aria-labelledby="modif-nodepr-label">
  2237       <title id="modif-nodepr-label">Proposed Recommendation - Advisory Committee Review</title>
  2238       <a xlink:href="#RecsPR">
  2239         <ellipse ry="18" rx="28" cy="140" cx="413" stroke="black" fill="#fff"></ellipse>
  2240         <text font-size="14" font-family="Times,serif" y="144" x="413" text-anchor="middle">PR</text></a>
  2242 <!--  use a[role=listitem] instead of g -->
  2244       <a xlink:href="#Modif-nodeRec" id="Modif-ToRec" role="listitem"
  2245         aria-labelledby="modif-torec-label modif-torec-text" fill="#060">
  2246         <title id="modif-torec-label">Advance to Recommendation</title> 
  2247         <text role="none" id="modif-torec-text" x="300" y="138" font-size="8">  
  2248           <tspan x="445" y="128">Advisory Committee Review</tspan>
  2249           <tspan x="445" y="136">Director's Decision</tspan></text>
  2251         <path d="M441,140h100" stroke="#060"></path>
  2252         <polygon points="534,136 544,140 534,144"></polygon> </a>
  2254       <a xlink:href="#Modif-nodeCR" id="Modif-BackToCR" role="listitem"
  2255         aria-labelledby="modif-backtocr-label modif-backtocr-text" fill="#600">
  2256         <title id="modif-backtocr-label">Return to Working Draft</title> 
  2257         <text id="modif-backtocr-text" font-size="8">
  2258           <tspan x="306" y="158">AC Review, </tspan>
  2259           <tspan x="302" y="168">Director Decision</tspan>
  2260           <tspan x="304" y="178">e.g. for minor changes</tspan></text>
  2261         <path d="M301,147h88" stroke-dasharray="3 5" stroke="#600"></path>
  2262         <polygon points="301,145 296,147 301,149"></polygon> </a>
  2264       <a xlink:href="#Modif-nodeWD" id="Modif-PRBackToWD" role="listitem"
  2265         aria-labelledby="modif-prbacktowd-label modif-prbacktowd-text" fill="#c00">
  2266         <title id="modif-prbacktowd-label">Return to Working Draft</title> 
  2267         <text role="none" id="modif-prbacktowd-text" font-size="9">
  2268           <tspan x="92" y="202">Advisory Committee review and Director's Decision, e.g. for further work and review</tspan></text>
  2269         <path d="M413,158v32h-316v-26" stroke-dasharray="2 2" stroke="#c00" fill="none"></path>
  2270         <polygon points="95,164 97,159 99,164"></polygon> </a>
  2271     </g>
  2273     <g id="Modif-nodeRec" stroke="black" aria-labelledby="modif-noderec-label" role="list">
  2274       <title id="modif-noderec-label">W3C Recommendation</title>
  2275       <a xlink:href="#RecsW3C" aria-labelledby="modif-noderec-label">
  2276         <ellipse ry="18" rx="28" cy="140" cx="573" fill="#fff" stroke-width="2"></ellipse>
  2277         <text font-size="16" y="144" x="573"
  2278           text-anchor="middle" stroke-width=".3">REC</text></a>
  2281       <a xlink:href="#Modif-TextChanges" id="Modif-ChangeProposal" aria-labelledby="Modif-changeproposal-title">
  2282         <title id="Modif-changeproposal-tit">Proposed change to a Recommendation</title>
  2283         <path d="M573,158 v30"></path>
  2284         <polygon points="573,188 571,181 575,181"></polygon>
  2285     </g>
  2286   </g>
  2287  </g>
  2289 <g aria-labelledby="modif-overall-title">
  2290  <title id="modif-overall-title">Initial maturity levels for a modification</title>
  2291     <g id="Modif-TextChanges" stroke="black" stroke-width="2" role="list">
  2292       <g role="listitem" tabindex="0">
  2293         <polygon points="573,188 623,213 573,238 520,213" fill="white"></polygon>
  2294         <text id="modif-textchanges-text" text-anchor="middle" font-size="10" stroke="none">
  2295           <tspan x="573" y="212">Substantive</tspan>
  2296           <tspan x="573" y="222">Changes?</tspan></text></g>
  2298         <a xlink:href="#Modif-nodeRec" aria-labelledby="modif-editedrec-title">
  2299           <title id="modif-editedrec-title">Only editorial changes: Edited Recommendation</title>
  2300           <text role="none" x="510" y="207" font-size="10" stroke="none">No</text>
  2301           <text text-anchor="end" font-size="10" stroke="none">
  2302             <tspan x="507" y="170">Director's</tspan><tspan x="504" y="180">approval</tspan></text>
  2303           <path fill="none" d="M520,213h-16c0,-35 11,-54 44,-60"></path>
  2304           <polygon points="548,152 543,152 545,156"></polygon></a>
  2306         <a xlink:href="#Modif-SubstantiveChanges">
  2307           <text x="578" y="255" font-size="10" stroke="none">Yes</text>
  2308           <path fill="none" d="M573,238v22h-108c-25,0 -30,-44 -55,-49h-80v15"></path>
  2309           <polygon points="330,226 328,219 332,219"></polygon></a>
  2310         </g>
  2312     <g id="Modif-NewFeatures" stroke="black" stroke-width="2" role="list">
  2313       <g role="listitem" tabindex="0">
  2314         <polygon points="330,278 370,253 330,228 290,253" fill="white"></polygon>
  2315         <text font-size="10" text-anchor="middle" stroke="none">
  2316           <tspan x="330" y="250">New</tspan>
  2317           <tspan x="330" y="260" text-anchor="middle">Features?</tspan></text></g>
  2319         <a xlink:href="#Modif-nodeCR" aria-labelledby="modif-nonewfeatures-label director-approval-text"
  2320           stroke="black" stroke-width="2">
  2321           <title id="modif-nonewfeatures-label">No new features - return to Candidate Recommendation</title>
  2322           <path d="M290,253h-30v-44" fill="none"></path>
  2323           <path d="M260,185v-20"></path>
  2324           <text role="none" x="280" y="245" stroke="none" font-size="10">No</text>
  2325           <text text-anchor="end" font-size="10" stroke="none">
  2326             <tspan x="254" y="225">Director's</tspan><tspan x="254" y="235">approval</tspan></text>
  2327           <polygon points="260,160 262,165 258,165" stroke="black"></polygon></a>
  2329         <a xlink:href="#Modif-FPWD" aria-labelledby="modif-fpwd-label modif-fpwd-text"
  2330           stroke="black" stroke-width="2">
  2331              <text x="335" y="286" font-size="10" stroke="none">Yes</text>
  2332             <path d="M330,278v12h-335v-150h10" fill="none"></path></a>
  2333     </g>
  2334   </g>
  2335 </svg>
  2337       </p>
  2339       <h4 id="errata">6.7.1 Errata Management</h4>
  2341       <p>Tracking errors is an important part of a Working Group's ongoing care of a Recommendation; for this reason,
  2342         the scope of a Working Group charter generally allows time for work after publication of a Recommendation.
  2343         In this Process Document, the term "erratum" (plural "errata") refers to any error that can be resolved by one or more
  2344         changes in classes 1-3 of section <a href="#correction-classes">7.2.5 Classes of Changes</a>.</p>
  2346       <p>Working Groups <em class="rfc2119">must</em> keep a record as errors are reported by readers and implementers.
  2347         Such error reports <em class="rfc2119">should</em> be processed no less frequently than quarterly. Readers of the
  2348         Recommendation <em class="rfc2119">should</em>
  2349         be able easily to find and see the errata that apply to that specific Recommendation.</p>
  2351       <p> Working Groups decide how to document errata. The best practice is a document that identifies itself as based on the
  2352         Recommendation text and clearly identifies the errata and any proposed corrections; other approaches include various
  2353         forms of an errata page, possibly auto-generated from a database.</p>
  2355       <p>An erratum is resolved by an informative, "proposed" correction generated by the Working Group. A correction
  2356         becomes part of the Recommendation by the process for Revising a Recommendation described in the next section.</p>
  2358       <h4 id="revised-rec">6.7.2 Revising a Recommendation</h4>
  2360       <p>A Working group <em class="rfc2119">may</em> request republication of a Recommendation, or W3C
  2361         <em class="rfc2119">may</em> republish a Recommendation, to make corrections that do not result in any changes to the
  2362         text of the specification.</p>
  2364       <p><a href="#editorial-change">Editorial changes</a> to a Recommendation require no technical review of the proposed changes.
  2365         A Working Group, provided there are no votes against the resolution to publish <em class="rfc2119">may</em> request
  2366         publication of a <a href="#rec-publication">Recommendation</a> or W3C <em class="rfc2119">may</em> publish a
  2367         <a href="#rec-publication">Recommendation</a> to make this class of change without passing through earlier maturity levels.
  2368         Such publications are called <dfn>Edited Recommendation</dfn>s.</p>
  2370       <p>To make corrections to a Recommendation that produce <a href="#substantive-change">substantive changes</a> but do not
  2371         add new features, or where there were votes against publishing the corrections directly as a
  2372         <a href="#rec-pr">Recommendation</a>, a Working Group <em class="rfc2119">may</em> request publication of a
  2373         <a href="#last-call">Candidate Recommendation</a>, without passing through earlier maturity levels.</p>
  2375       <p>In the latter two cases, the resulting Recommendation is called an
  2376         <dfn id="rec-edited">Edited Recommendation</dfn>.</p>
  2377       <p>When requesting the publication of an Edited Recommendation as described in this section, in addition to meeting the
  2378         requirements for the relevant maturity level, a Working Group</p>
  2379       <ul>
  2380         <li><em class="rfc2119">must</em> show that the changes to the document have received
  2381           <a href="#wide-review">wide review</a>, and </li>
  2382         <li><em class="rfc2119">should</em> address all recorded errata.</li>
  2383       </ul>
  2384       <p>For changes which introduces a new feature or features, W3C <em class="rfc2119">must</em> follow the full process of
  2385         <a href="#rec-advance">advancing a technical report to Recommendation</a> beginning with a new
  2386         First Public Working Draft.</p>
  2388       <h3 id="Note">6.8 Publishing a Working Group or Interest Group Note</h3>
  2390       <p>Working Groups and Interest Groups <em class="rfc2119">may</em> publish work as W3C Notes. Examples include:</p> 
  2391       <ul>
  2392         <li>supporting documentation for a specification, such as explanations of design principles or 
  2393           use cases and requirements,</li>
  2394         <li>non-normative guides to good practices,
  2395         <li>specifications where work has been stopped and there is no longer consensus for making them a new standard.</li>
  2396       </ul>
  2397       <p>In order to publish a Note, a Working Group or Interest Group: </p>
  2398       <ul>
  2399         <li><em class="rfc2119">may</em> publish a Note with or without its prior publication as a Working Draft.</li>
  2400         <li><em class="rfc2119">must</em> record the group's decision to request publication as a Note, and</li>
  2401         <li><em class="rfc2119">should</em> publish documentation of significant changes to the technical report since any previous
  2402           publication.</li>
  2403       </ul>
  2404       <p>Possible next steps:</p>
  2405       <ul>
  2406         <li>End state: A technical report <em class="rfc2119">may</em> remain a Working or Interest Group Note indefinitely</li>
  2407         <li>A Working Group <em class="rfc2119">may</em> resume work on technical report within the scope of its charter at any
  2408           time, at the maturity level the specification had before publication as a Note</li>
  2409       </ul>
  2410       <p>The <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]
  2411         does not specify any licensing requirements or commitments for Working Group Notes.</p>
  2413       <h3 id="rec-rescind">6.9 Obsoleting or Rescinding a W3C Recommendation</h3>
  2415       <p>It is possible that W3C decides that implementing a particular Recommendation is no longer recommended.
  2416         There are two designations for such specifications, chosen depending on how strongly W3C wishes to advise against
  2417         using the specification.</p> 
  2419       <p>W3C <em class="rfc2119">may</em> obsolete a Recommendation, for example if the W3C Community decides that
  2420         the Recommendation no longer represents best practices, or is not adopted and is not apparently likely to be adopted.
  2421         An Obsolete Recommendation <em class="rfc2119">may</em> be restored to normal Recommendation,
  2422         for example because despite marking it Obsolete the specification is later more broadly adopted.</p>
  2424       <p>W3C <em class="rfc2119">may</em> rescind a Recommendation if W3C believes there is no reasonable prospect
  2425         of it being restored for example due to burdensome patent claims that affect implementers and cannot be resolved; see the
  2426         <a href="">W3C Patent Policy</a>
  2427         [<a href="#ref-patentpolicy">PUB33</a>] and in particular
  2428         <a href="">section 5</a> (bullet 10) and
  2429         <a href="">section 7.5</a>.</p>
  2431       <p>W3C only rescinds or obsoletes entire Recommendations. To rescind or obsolete some part of a Recommendation,
  2432         W3C follows the process for <a href="#rec-modify">modifying a Recommendation</a>.</p>
  2434       <p class="note">For the purposes of the <a href="">W3C Patent Policy</a>
  2435        [<a href="#ref-patentpolicy">PUB33</a>] an Obsolete Recommendation has the status of an active Recommendation,
  2436        although it is not recommended for future implementation; a Rescinded Recommendation ceases to be in effect
  2437        and no new licenses are granted under the Patent Policy.</p>
  2439       <p>The Director <em class="rfc2119">may</em> recommend obsoleting, rescinding, or restoring a Recommendation. The Director
  2440         <em class="rfc2119">must</em> begin an <a href="#ACReview">Advisory Committee review</a> of a
  2441         proposal to obsolete, rescind, or restore a Recommendation when requested to do so by any of the following:</p>
  2443       <ul>
  2444         <li>The Working Group who produced, or is chartered to maintain, the Recommendation.</li>
  2445         <li>The TAG, if there is no such Working Group</li>
  2446         <li>Any individual who made a request to the relevant Working Group as described above, or the TAG if such a group
  2447           does not exist, to obsolete, rescind, or restore a Recommendation, where the request was not answered
  2448           within 90 days</li>
  2449         <li>5% of the members of the Advisory Committee</li>
  2450       </ul>
  2452       <p id="proposed-rescinded-rec">For any <a href="#ACReview">Advisory Committee review</a> of a
  2453         proposal to obsolete, rescind, or restore a Recommendation the Director <em class="rfc2119">must</em>:</p>
  2455       <ul>
  2456         <li>announce the proposal to all Working Group Chairs, and to the Public, as well as to the Advisory Committee</li>
  2457         <li>indicate that this is a proposal to Rescind, Obsolete, or restore, a Recommendation as appropriate</li>
  2458         <li>identify the Recommendation by URL</li>
  2459         <li>publish a rationale for the proposal</li>
  2460         <li>identify known dependencies and solicit review from all dependent Working Groups</li>
  2461         <li>solicit public review</li>
  2462         <li>specify the deadline for review comments, which <em class="rfc2119">must</em> be at least four weeks after
  2463           the Director's announcement</li>
  2464       </ul>
  2466       <p>and <em class="rfc2119">should</em></p>
  2468       <ul>
  2469         <li>identify known implementations.</li>
  2470       </ul>
  2472       <p>If there was any <a href="#def-Dissent" rel="glossary"><span class="dfn-instance">dissent</span></a>
  2473         in the Advisory Committee review, the Director <em class="rfc2119">must</em> publish the substantive content of
  2474         the dissent to W3C <strong>and the public</strong>, and <em class="rfc2119">must</em>
  2475         <a href="#formal-address">formally address</a> the dissent at least 14 days before publication as an
  2476         Obsolete or Rescinded Recommendation.</p> 
  2478       <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an 
  2479         <a href="#ACAppeal">Advisory Committee Appeal</a> of the Director's decision.</p>
  2481       <p>W3C <em class="rfc2119">must</em> publish an Obsolete or Rescinded Recommendation with up to date status.
  2482         The updated version <em class="rfc2119">may</em> remove the main body of the document. The Status of this Document section
  2483         <em class="rfc2119">should</em> link to the explanation of <a href="">Obsoleting and Rescinding W3C Specifications</a> [<a href="#ref-obs-resc">PUB39</a>] as appropriate.</p>
  2485       <p>Once W3C has published a Rescinded Recommendation, future W3C technical reports
  2486         <em class="rfc2119">must not</em> include normative references to that technical report.</p>
  2488       <p><span style="font-weight: bold;">Note:</span> W3C strives to ensure that all Technical Reports will continue to be
  2489         available at their version-specific URL.</p>
  2491       <h3 id="further-reading">6.10 Further reading</h3>
  2493       <p>Refer to <a href="">"How to Organize a Recommendation Track Transition"</a> in
  2494         the <a href="">Member guide</a> for practical information about preparing for the reviews
  2495         and announcements of the various steps, and
  2496         <a href="">tips on getting to Recommendation faster</a>
  2497        [<a href="#ref-rec-tips">PUB27</a>].</p>
  2499       <h2 id="ReviewAppeal">7 Advisory Committee Reviews, Appeals, and Votes</h2>
  2501       <p>This section describes how the Advisory Committee reviews proposals from the Director and how Advisory Committee
  2502         representatives initiate an Advisory Committee Appeal of a W3C decision or Director's decision. A 
  2503         <dfn id="def-w3c-decision">W3C decision</dfn> is one where the Director (or the Director's delegate) has exercised the role
  2504         of assessing consensus after an <a href="#ACReview">Advisory Committee review</a>.</p>
  2506       <h3 id="ACReview">7.1 Advisory Committee Reviews</h3>
  2508       <p>The Advisory Committee reviews:</p>
  2510       <ul>
  2511         <li><a href="#CharterReview">new and modified Working and Interest Groups</a>,</li>
  2512         <li><a href="#cfr">Proposed Recommendations</a>, <a href="#cfr-edited">Proposed Edited Recommendations</a>,
  2513           <a href="#proposed-rescinded-rec">Proposal to Rescind a Recommendation</a>, and</li>
  2514         <li><a href="#GAProcess">Proposed changes to the W3C process</a>.</li>
  2515       </ul>
  2517       <h4 id="ACReviewStart">7.1.1 Start of a Review Period</h4>
  2519       <p>Each Advisory Committee review period begins with a Call for Review from the Team to the Advisory Committee. The
  2520         <dfn id="reviewform">Call for Review</dfn> describes the proposal, raises attention to deadlines, estimates when the decision
  2521         will be available, and includes other practical information. Each Member organization <em class="rfc2119">may</em> send one
  2522         review, which <em class="rfc2119">must</em> be returned by its Advisory Committee representative.</p>
  2524       <p>The Team <em class="rfc2119">must</em> provide two channels for Advisory Committee review comments:</p>
  2526       <ol>
  2527         <li>an archived <a href="#Team-only">Team-only</a> channel;</li>
  2528         <li>an archived <a href="#Member-only">Member-only</a> channel.</li>
  2529       </ol>
  2531       <p>The Call for Review <em class="rfc2119">must</em> specify which channel is the default for review comments on that Call.</p>
  2533       <p>Reviewers <em class="rfc2119">may</em> send information to either or both channels. They <em class="rfc2119">may</em> also
  2534         share their reviews with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>.</p>
  2536       <p>A Member organization <em class="rfc2119">may</em> modify its review during a review period (e.g., in light of comments
  2537        from other Members).</p>
  2539       <h4 id="ACReviewAfter">7.1.2 After the Review Period</h4>
  2541       <p>After the review period, the Director <em class="rfc2119">must</em> announce to the Advisory Committee the level of
  2542         support for the proposal (<a href="#def-Consensus">consensus</a> or <a href="#def-Dissent">dissent</a>). The Director
  2543         <em class="rfc2119">must</em> also indicate whether there were any Formal Objections, with attention to
  2544         <a href="#confidentiality-change">changing confidentiality level</a>. This <a href="#def-w3c-decision">W3C decision</a>
  2545         is generally one of the following:</p>
  2547       <ol>
  2548         <li>The proposal is approved, possibly with minor changes integrated.</li>
  2549         <li>The proposal is approved, possibly with <a href="#substantive-change">substantive changes</a> integrated. In this case
  2550           the Director's announcement <em class="rfc2119">must</em> include rationale for the decision to advance the document
  2551           despite the proposal for a substantive change.</li>
  2552         <li>The proposal is returned for additional work, with a request to the initiator to
  2553           <a href="#formal-address">formally address</a> certain issues.</li>
  2554         <li>The proposal is rejected.</li>
  2555       </ol>
  2557       <p>This document does not specify time intervals between the end of an Advisory Committee review period and the
  2558         <a href="#def-w3c-decision">W3C decision</a>. This is to ensure that the Members and Team have sufficient time to consider
  2559         comments gathered during the review. The Advisory Committee <em class="rfc2119">should not</em> expect an announcement
  2560         sooner than <span class="time-interval">two weeks</span> after the end of a Proposed Recommendation review period. If,
  2561         after <span class="time-interval">three weeks</span>, the Director has not announced the outcome, the Director
  2562         <em class="rfc2119">should</em> provide the Advisory Committee with an update.</p>
  2564       <h3 id="ACAppeal">7.2 Appeal by Advisory Committee Representatives</h3>
  2566       <p>Advisory Committee representatives <em class="rfc2119">may</em> appeal certain decisions, though appeals are only expected
  2567         to occur in extraordinary circumstances.</p>
  2569       <p>When a W3C decision is made following an <a href="#ACReview">Advisory Committee review</a>, Advisory Committee
  2570         representatives <em class="rfc2119">may</em> initiate an <a href="#def-w3c-decision">Advisory Committee Appeal</a>.
  2571         These W3C decisions include those related to group creation and modification, and transitions to new maturity levels
  2572         for Recommendation Track documents and the Process document.</p>
  2574       <p>Advisory Committee representatives <em class="rfc2119">may</em> also initiate an appeal for certain Director's decisions
  2575         that do not involve an Advisory Committee review. These cases are identified in the sections which describe the
  2576         requirements for the Director's decision and include additional (non-reviewed) maturity levels of Recommendation Track
  2577         documents, group charter extensions and closures, and Memoranda of Understanding.</p>
  2579       <p>In all cases, an appeal <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span>
  2580         of the decision.</p>
  2582       <p>An Advisory Committee representative initiates an appeal by sending a request to the Team. Within one week the Team 
  2583         <em class="rfc2119">must</em> announce the appeal process to the Advisory Committee and provide a mechanism for
  2584         Advisory Committee representatives to respond with a statement of support (yes, no, or abstain) and comments, as desired.
  2585         The archive of these comments <em class="rfc2119">must</em> be Member-visible. If, within
  2586         <span class="time-interval">one week</span> of the Team's announcement, 5% or more of the Advisory Committee support the
  2587         appeal request, the Team <em class="rfc2119">must</em> organize an appeal vote asking the Advisory Committee to
  2588         approve or reject the decision.
  2589         <!-- Voting procedure to be determined --></p>
  2591       <h3 id="ACVotes">7.3 Advisory Committee Votes</h3>
  2593       <p>The Advisory Committee votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>, and in
  2594         the event of an <a href="#def-w3c-decision">Advisory Committee Appeal</a> achieving the required support to trigger an
  2595         appeal vote.. Whenever the Advisory Committee votes, each Member or group of <a href="#MemberRelated">related Members</a>
  2596         has one vote. In the case of <a href="#AB-TAG-elections">Advisory Board and TAG elections</a>, "one vote" means
  2597         "one vote per available seat".</p>
  2599       <h2 id="GAEvents">8 Workshops and Symposia</h2>
  2601       <p>The Team organizes <dfn id="EventsW">Workshops</dfn> and <dfn id="EventsS">Symposia</dfn> to promote early involvement in
  2602         the development of W3C activities from Members and the public.</p>
  2604       <p>The goal of a Workshop is usually either to convene experts and other interested parties for an exchange of ideas about a
  2605         technology or policy, or to address the pressing concerns of W3C Members. Organizers of the first type of Workshop
  2606         <em class="rfc2119">may</em> solicit position papers for the Workshop program and <em class="rfc2119">may</em> use those
  2607         papers to choose attendees and/or presenters.</p>
  2609       <p>The goal of a Symposium is usually to educate interested parties about a particular subject.</p>
  2611       <p>The Call for Participation in a Workshop or Symposium <em class="rfc2119">may</em> indicate participation requirements or 
  2612         limits, and expected deliverables (e.g., reports and minutes). Organization of an event does not guarantee further
  2613         investment by W3C in a particular topic, but <em class="rfc2119">may</em> lead to proposals for
  2614         new activities or groups.</p>
  2616       <p>Workshops and Symposia generally last one to three days. If a Workshop is being organized to address the pressing concerns
  2617         of Members, the Team <em class="rfc2119">must</em> issue the Call for Participation no later than
  2618         <span class="time-interval">six weeks</span> prior to the Workshop's scheduled start date. For other Workshops and
  2619         Symposia, the Team <em class="rfc2119">must</em> issue a Call for Participation no later than
  2620         <span class="time-interval">eight weeks</span> prior to the meeting's scheduled start date. This helps ensure that speakers
  2621         and authors have adequate time to prepare position papers and talks.</p>
  2623       <h2 id="Liaisons">9 Liaisons</h2>
  2625       <p>W3C uses the term "liaison" to refer to coordination of activities with a variety of organizations, through a number of
  2626         mechanisms ranging from very informal (e.g., an individual from another organization participates in a W3C Working Group,
  2627         or just follows its work) to mutual membership, to even more formal agreements. Liaisons are not meant to substitute for
  2628         W3C membership.</p>
  2630       <p>All liaisons <em class="rfc2119">must</em> be coordinated by the Team due to requirements for public communication;
  2631         patent, copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.</p>
  2633       <p>The W3C Director <em class="rfc2119">may</em> negotiate and sign a <dfn id="mou">Memorandum of Understanding
  2634         (<abbr>MoU</abbr>)</dfn> with another organization. Before signing the MoU, the Team <em class="rfc2119">must</em> inform
  2635         the Advisory Committee of the intent to sign and make the MoU available for Advisory Committee review; Advisory Committee
  2636         representatives <em class="rfc2119">may</em> initiate an <a href="#ACAppeal">Advisory Committee Appeal</a> of the decision
  2637         to sign the MoU. Once approved, a Memorandum of Understanding <em class="rfc2119">should</em> be made public.</p>
  2639       <p>Information about <a href="">W3C liaisons with other organizations</a> and the
  2640         guidelines W3C follows when creating a liaison [<a href="#ref-liaison-list">PUB28</a>] is available on the Web.</p>
  2642       <h2 id="Submission">10 Member Submission Process</h2>
  2644       <p>The Member Submission process allows Members to propose technology or other ideas for consideration by the Team. After
  2645         review, the Team <em class="rfc2119">may</em> publish the material at the W3C Web site. The formal process affords Members
  2646         a record of their contribution and gives them a mechanism for disclosing the details of the transaction with the Team
  2647         (including IPR claims). The Team also publishes review comments on the Submitted materials for W3C Members, the public, and
  2648         the media.</p>
  2650       <p>A <dfn id="MemberSubmission">Member Submission</dfn> consists of:</p>
  2652       <ul>
  2653         <li>One or more documents developed outside of the W3C process, and</li>
  2654         <li>Information about the documents, provided by the Submitter.</li>
  2655       </ul>
  2657       <p>One or more Members (called the "Submitter(s)") <em class="rfc2119">may</em> participate in a Member Submission. Only W3C
  2658         Members <em class="rfc2119">may</em> be listed as Submitter(s).</p>
  2660       <p>The Submission process consists of the following steps:</p>
  2662       <ol>
  2663         <li>One of the Submitter(s) sends a request to the Team to acknowledge the Submission request. The Team and Submitter(s)
  2664           communicate to ensure that the Member Submission is complete.</li>
  2665         <li>After Team review, the Director <em class="rfc2119">must</em> either acknowledge or reject the Submission request.
  2667           <ul>
  2668             <li>If <a href="#SubmissionYes">acknowledged</a>, the Team <em class="rfc2119">must</em> publish the Member Submission
  2669               at the public W3C Web site, in addition to Team comments about the Member Submission.</li>
  2670             <li>If <a href="#SubmissionNo">rejected</a>, the Submitter(s) <em class="rfc2119">may</em> initiate a 
  2671               <dfn>Submission Appeal</dfn> to either the <a href="#TAG">TAG</a> or the <a href="#AB">Advisory Board</a>.</li>
  2672           </ul>
  2673         </li>
  2674       </ol>
  2676       <p><strong>Note:</strong> To avoid confusion about the Member Submission process, please note that:</p>
  2678       <ul>
  2679         <li>Documents in a Member Submission are developed outside of W3C. These documents are <strong>not</strong> part of the
  2680           <a href="#Reports">technical report development process</a> (and therefore are not included in the
  2681           <a href="">index of W3C technical reports</a>). Members wishing to have documents developed outside
  2682           of W3C published by W3C <em class="rfc2119">must</em> follow the Member Submission process.</li>
  2683         <li>The Submission process is <strong>not</strong> a means by which Members ask for "ratification" of these documents as
  2684           <a href="#RecsW3C">W3C Recommendations</a>.</li>
  2685         <li>There is no requirement or guarantee that technology which is part of an acknowledged Submission request will receive
  2686           further consideration by W3C (e.g., by a W3C Working Group).</li>
  2687       </ul>
  2689       <p>Publication of a Member Submission by W3C does not imply endorsement by W3C, including the W3C Team or Members. The
  2690         acknowledgment of a Submission request does not imply that any action will be taken by W3C. It merely records publicly that
  2691         the Submission request has been made by the Submitter. A Member Submission published by W3C
  2692         <em class="rfc2119">must not</em> be referred to as "work in progress" of the W3C.</p>
  2694       <p>The list of <a href="">acknowledged Member Submissions</a>
  2695        [<a href="#ref-submission-list">PUB10</a>] is available at the W3C Web site.</p>
  2697       <h3 id="SubmissionRights">10.1 Submitter Rights and Obligations</h3>
  2699       <p>When more than one Member jointly participates in a Submission request, only one Member formally sends in the request.
  2700         That Member <em class="rfc2119">must</em> copy each of the Advisory Committee representatives of the other participating
  2701         Members, and each of those Advisory Committee representatives <em class="rfc2119">must</em> confirm (by email to the Team)
  2702         their participation in the Submission request.</p>
  2704       <p>At any time prior to acknowledgment, any Submitter <em class="rfc2119">may</em> withdraw support for a Submission request
  2705         (described in "<a href="">How to send a Submission request</a>"). A Submission request
  2706         is "withdrawn" when no Submitter(s) support it. The Team <em class="rfc2119">must not</em> make statements about withdrawn
  2707         Submission requests.</p>
  2709       <p>Prior to acknowledgment, the Submitter(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>,
  2710        refer to a document as "submitted to the World Wide Web Consortium" or "under consideration by W3C" or any similar phrase
  2711        either in public or Member communication. The Submitter(s) <em class="rfc2119">must not</em> imply in public or Member
  2712        communication that W3C is working (with the Submitter(s)) on the material in the Member Submission. The Submitter(s)
  2713        <em class="rfc2119">may</em> publish the documents in the Member Submission prior to acknowledgment (without reference
  2714        to the Submission request).</p>
  2716       <p>After acknowledgment, the Submitter(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>, imply
  2717         W3C investment in the Member Submission until, and unless, the material has been adopted as a deliverable of a W3C Working
  2718         Group</p>
  2720       <h4 id="SubmissionScope">10.1.1 Scope of Member Submissions</h4>
  2722       <p>When a technology overlaps in scope with the work of a chartered Working Group, Members <em class="rfc2119">should</em>
  2723         <a href="#group-participation">participate in the Working Group</a> and contribute the technology to the group's process
  2724         rather than seek publication through the Member Submission process. The Working Group <em class="rfc2119">may</em>
  2725         incorporate the contributed technology into its deliverables. If the Working Group does not incorporate the technology, it
  2726         <em class="rfc2119">should not</em> publish the contributed documents as Working Group Notes since Working Group Notes
  2727         represent group output, not input to the group.</p>
  2729       <p>On the other hand, while W3C is in the early stages of developing a charter, Members <em class="rfc2119">should</em> use
  2730         the Submission process to build consensus around concrete proposals for new work.</p>
  2732       <p>Members <em class="rfc2119">should not</em> submit materials covering topics well outside the scope of
  2733         <a href="">W3C's mission</a> [<a href="#ref-mission">PUB15</a>].</p>
  2735       <h4 id="SubmissionReqs">10.1.2 Information Required in a Submission Request</h4>
  2737       <p>The Submitter(s) and any other authors of the submitted material <em class="rfc2119">must</em> agree that, if the request 
  2738         is acknowledged, the documents in the Member Submission will be subject to the
  2739         <a href="">W3C Document License</a>
  2740         [<a href="#ref-doc-license">PUB18</a>] and will include a reference to it. The Submitter(s) <em class="rfc2119">may</em>
  2741         hold the copyright for the documents in a Member Submission.</p>
  2743       <p>The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments of
  2744         <a href="">section 3.3</a> of the
  2745         <a href="">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
  2747       <p>The Submitter(s) <em class="rfc2119">must</em> include the following information:</p>
  2749       <ul>
  2750         <li>The list of all submitting Members.</li>
  2751         <li>Position statements from all submitting Members (gathered by the Submitter). All position statements
  2752           <em class="rfc2119">must</em> appear in a separate document.</li>
  2753         <li>Complete electronic copies of any documents submitted for consideration (e.g., a technical specification, a position
  2754           paper, etc.) If the Submission request is acknowledged, these documents will be published by W3C and therefore
  2755           <em class="rfc2119">must</em> satisfy the Communication Team's
  2756           <a href="">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>].
  2757           Submitters <em class="rfc2119">may</em> hold the copyright for the material contained in these documents, but when
  2758           published by W3C, these documents <em class="rfc2119">must</em> be subject to the provisions of the
  2759           <a href="">W3C Document License</a>
  2760           [<a href="#ref-doc-license">PUB18</a>].</li>
  2761       </ul>
  2763       <p>The request <em class="rfc2119">must</em> also answer the following questions.</p>
  2765       <ul>
  2766         <li>What proprietary technology is required to implement the areas addressed by the request, and what terms are associated
  2767           with its use? Again, many answers are possible, but the specific answer will affect the Team's decision.</li>
  2768         <li>What resources, if any, does the Submitter intend to make available if the W3C acknowledges the Submission request and
  2769           takes action on it?</li>
  2770         <li>What action would the Submitter like W3C to take if the Submission request is acknowledged?</li>
  2771         <li>What mechanisms are there to make changes to the specification being submitted? This includes, but is not limited to,
  2772           stating where change control will reside if the request is acknowledged.</li>
  2773       </ul>
  2775       <p>For other administrative requirements related to Submission requests, see
  2776         "<a href="">How to send a Submission request</a>"
  2777         [<a href="#ref-member-sub">MEM8</a>].</p>
  2779       <h3 id="TeamSubmissionRights">10.2 Team Rights and Obligations</h3>
  2781       <p>Although they are not technical reports, the documents in a Member Submission <em class="rfc2119">must</em> fulfil the
  2782         requirements established by the Team, including the Team's
  2783         <a href="">Publication Rules</a>.</p>
  2785       <p>The Team sends a <a id="validation-notice">validation notice</a> to the Submitter(s) once the Team has reviewed a
  2786         Submission request and judged it complete and correct.</p>
  2788       <p>Prior to a decision to <a href="#SubmissionYes">acknowledge</a> or <a href="#SubmissionNo">reject</a> the request, the
  2789         request is <a href="#Team-only">Team-only</a>, and the Team <em class="rfc2119">must</em> hold it in the strictest 
  2790         confidentiality. In particular, the Team <em class="rfc2119">must not</em> comment to the media about the Submission
  2791         request.</p>
  2793       <h3 id="SubmissionYes">10.3 Acknowledgment of a Submission Request</h3>
  2795       <p>The Director <a href="#SubmissionYes">acknowledges</a> a Submission request by sending an announcement to the Advisory
  2796         Committee. Though the announcement <em class="rfc2119">may</em> be made at any time, the Submitter(s) can expect an
  2797         announcement between <span class="time-interval">four to six weeks</span> after the
  2798         <a href="#validation-notice">validation notice</a>. The Team <em class="rfc2119">must</em>
  2799         keep the Submitter(s) informed of when an announcement is likely to be made.</p>
  2801       <p>Once a Submission request has been acknowledged, the Team <em class="rfc2119">must</em>:</p>
  2803       <ul>
  2804         <li>Publish the Member Submission.</li>
  2805         <li>Publish Team comments about the Submission request.</li>
  2806       </ul>
  2808       <p>If the Submitter(s) wishes to modify a document published as the result of acknowledgment, the Submitter(s)
  2809         <em class="rfc2119">must</em> start the Submission process from the beginning, even just to correct editorial changes.</p>
  2811       <h3 id="SubmissionNo">10.4 Rejection of a Submission Request, and Submission Appeals</h3>
  2813       <p>The Director <em class="rfc2119">may</em> reject a Submission request for a variety of reasons, including any of the
  2814         following:</p>
  2816       <ul>
  2817         <li>The ideas expressed in the request overlap in scope with the work of a chartered Working Group, and acknowledgment
  2818           might jeopardize the progress of the group.</li>
  2819         <li>The IPR statement made by the Submitter(s) is inconsistent with the W3C's
  2820           <a href="">Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
  2821           <a href="">Document License</a>
  2822           [<a href="#ref-doc-license">PUB18</a>], or other IPR policies.</li>
  2823         <li>The ideas expressed in the request are poor, might harm the Web, or run counter to
  2824           <a href="">W3C's mission</a>.</li>
  2825         <li>The ideas expressed in the request lie well outside the scope of W3C's mission.</li>
  2826       </ul>
  2828       <p>In case of a rejection, the Team <em class="rfc2119">must</em> inform the Advisory Committee representative(s) of the
  2829         Submitter(s). If requested by the Submitter(s), the Team <em class="rfc2119">must</em> provide rationale to the
  2830         Submitter(s) about the rejection. Other than to the Submitter(s), the Team <em class="rfc2119">must not</em> make
  2831         statements about why a Submission request was rejected.</p>
  2833       <p>The Advisory Committee representative(s) of the Submitters(s) <em class="rfc2119">may</em> initiate a
  2834         <a href="#SubmissionNo">Submission Appeal</a> of the Team's Decision to the <a href="#TAG">TAG</a> if the reasons are
  2835         related to Web architecture, or to the <a href="#AB">Advisory Board</a> if the request is rejected for other
  2836         reasons. In this case the Team <em class="rfc2119">should</em> make available its rationale for the rejection to the
  2837         appropriate body. The Team will establish a process for such appeals that ensures the appropriate
  2838         <a href="#confidentiality-levels">level of confidentiality</a>.</p>
  2840       <h2 id="GAProcess">11 Process Evolution</h2>
  2842       <p>The <span id="ProcessDoc">W3C Process Document</span> undergoes similar consensus-building processes as technical reports,
  2843         with the <a href="#AB">Advisory Board</a> acting as the sponsoring Working Group.</p>
  2845       <p>The Advisory Board initiates review of a Process Document as follows:</p>
  2847       <ol>
  2848         <li>The Team sends a Call for Review to the Advisory Committee and other W3C groups.</li>
  2849         <li>After comments have been <a href="#formal-address">formally addressed</a> and the document possibly modified, the Team
  2850           seeks endorsement from the Members by initiating an <a href="#ACReview">Advisory Committee review</a> of a
  2851           Proposed Process Document.
  2852           The review period <em class="rfc2119">must</em> last at least <span class="time-interval">four weeks</span>.</li>
  2853         <li><a href="#ACReviewAfter">After the Advisory Committee review</a>, if there is consensus, the Team enacts the new
  2854           process officially by announcing the <a href="#def-w3c-decision">W3C decision</a> to the Advisory Committee. 
  2855           Advisory Committee representatives <em class="rfc2119">may</em> initiate an
  2856           <a href="#ACAppeal">Advisory Committee Appeal</a> to the W3C.</li>
  2857       </ol>
  2859       <p>W3C <em class="rfc2119">may</em> also modify a Process Document by following the processes for
  2860         <a href="#rec-modify">modifying a Recommendation</a>.</p>
  2862       <p>Reviews of the Process Document are not public reviews.</p>
  2864       <h2 id="references">12 References</h2>
  2866       <h3 id="public-refs">12.1 Public Resources</h3>
  2868       <p>The following public information is available at the <a href="">W3C Web site</a>.</p>
  2870       <dl>
  2871         <dt id="ref-join-w3c">[PUB5]</dt>
  2872          <dd><cite><a href="">How to Join W3C</a></cite></dd>
  2873         <dt id="ref-member-agreement">[PUB6]</dt>
  2874          <dd><cite><a href="">Membership Agreement</a></cite></dd>
  2875         <dt id="ref-current-mem">[PUB8]</dt>
  2876          <dd><cite><a href="">The list of current W3C Members</a></cite></dd>
  2877         <dt id="ref-activity-list">[PUB9]</dt>
  2878          <dd><cite><a href="">The list of W3C Activities</a></cite></dd>
  2879         <dt id="ref-submission-list">[PUB10]</dt>
  2880          <dd><cite><a href="">The list of acknowledged Member Submissions</a></cite></dd>
  2881         <dt id="ref-doc-list">[PUB11]</dt>
  2882          <dd><cite><a href="">The W3C technical reports index</a></cite></dd>
  2883         <dt id="ref-submission-overview">[PUB13]</dt>
  2884          <dd><cite><a href="">Submission request overview</a></cite></dd>
  2885         <dt id="ref-people">[PUB14]</dt>
  2886          <dd><cite><a href="">The W3C Team</a></cite></dd>
  2887         <dt id="ref-mission">[PUB15]</dt>
  2888          <dd><cite><a href="">About the World Wide Web Consortium</a></cite></dd>
  2889         <dt id="ref-team-submission-list">[PUB16]</dt>
  2890          <dd><cite><a href="">The list of published Team Submissions</a></cite></dd>
  2891         <dt id="ref-invited-expert">[PUB17]</dt>
  2892          <dd><cite><a href="">Invited expert and collaborators agreement</a></cite></dd>
  2893         <dt id="ref-doc-license">[PUB18]</dt>
  2894          <dd><cite><a href="">W3C Document License</a></cite></dd>
  2895         <dt id="ref-software-license">[PUB19]</dt>
  2896          <dd><cite><a href="">W3C Software Notice and License</a></cite></dd>
  2897         <dt id="ref-translations">[PUB20]</dt>
  2898          <dd><cite><a href="">Translations of W3C technical reports</a></cite></dd>
  2899         <dt id="ref-pub-mailing-lists">[PUB21]</dt>
  2900          <dd><cite><a href="">Public W3C mailing lists</a></cite></dd>
  2901         <dt id="ref-coi">[PUB23]</dt>
  2902          <dd><cite><a href="">Conflict of Interest Policy for W3C Team Members Engaged in Outside Professional Activities</a></cite></dd>
  2903         <dt id="ref-tag-charter">[PUB25]</dt>
  2904          <dd><cite><a href="">Technical Architecture Group (TAG) Charter</a></cite></dd>
  2905         <dt id="ref-tag-home">[PUB26]</dt>
  2906          <dd><cite><a href="">The TAG home page</a></cite></dd>
  2907         <dt id="ref-rec-tips">[PUB27]</dt>
  2908          <dd><cite><a href="">Tips for Getting to Recommendation Faster</a></cite></dd>
  2909         <dt id="ref-liaison-list">[PUB28]</dt>
  2910          <dd><cite><a href="">W3C liaisons with other organizations</a></cite></dd>
  2911         <dt id="ref-ab-home">[PUB30]</dt>
  2912          <dd><cite><a href="">The Advisory Board home page</a></cite></dd>
  2913         <dt id="ref-pubrules">[PUB31]</dt>
  2914          <dd><cite><a href="">Publication Rules</a></cite></dd>
  2915         <dt id="ref-fellows">[PUB32]</dt>
  2916          <dd><cite><a href="">W3C Fellows Program</a></cite></dd>
  2917         <dt id="ref-patentpolicy">[PUB33]</dt>
  2918          <dd><cite><a href="">5 Feb 2004 version of the W3C Patent Policy</a></cite>. The
  2919           <a href="">latest version of the W3C Patent Policy</a> is available at
  2920 </dd>
  2921         <dt id="in-place-tr-mod">[PUB35]</dt>
  2922          <dd><cite><a href="">In-place modification of W3C Technical Reports</a></cite></dd>
  2923         <dt id="ref-calendar">[PUB36]</dt>
  2924          <dd>The <cite><a href="">calendar of all scheduled official W3C events</a></cite> replaced the <a href="">former member-confidential version</a> [<a href="#oldref-mem-calendar">MEM3</a>].</dd>
  2925         <dt id="ref-guide">[PUB37]</dt>
  2926          <dd><cite><a href="">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other collaborators</dd>
  2927         <dt id="ref-cepc">[PUB38]</dt>
  2928          <dd><cite><a href="">W3C Code of Ethics and Professional Conduct</a></cite></dd>
  2929         <dt id="ref-obs-resc">[PUB39]</dt>
  2930          <dd><cite><a href="">Obsoleting and Rescinding W3C Specifications</a></cite></dd>
  2932       </dl>
  2934       <h3>12.2 <a id="member-refs">Member-only Resources</a></h3>
  2936       <p>The following <a href="#Member-only">Member-only</a> information is available at the
  2937         <a href="">W3C Web site</a>.</p>
  2939       <dl>
  2940         <dt id="ref-current-ac">[MEM1]</dt>
  2941          <dd><cite><a href="">Current Advisory Committee representatives</a></cite></dd>
  2942         <dt id="ref-mailing-lists">[MEM2]</dt>
  2943          <dd><cite><a href="">Group mailing lists</a></cite></dd>
  2944         <dt id="oldref-mem-calendar">[MEM3]</dt>
  2945          <dd>The Member-only <cite><a href="">calendar of all scheduled official W3C events</a></cite> is no longer maintained. The information is now maintained in the public calendar [<a href="#ref-calendar">PUB36</a>]</dd>
  2946         <dt id="ref-new-member">[MEM4]</dt>
  2947          <dd>There is a <cite><a href="">Member intro and FAQ</a></cite> as well as the <cite><a href="">Process, Patent Policy, Finances Guide</a></cite> previously known as the "New Member Orientation", which includes an introduction to W3C processes from a practical standpoint, including relevant email addresses.</dd>
  2948         <dt id="ref-ac-meetings">[MEM5]</dt>
  2949          <dd><cite><a href="">Advisory Committee meetings</a></cite></dd>
  2950         <dt id="ref-member-web">[MEM6]</dt>
  2951          <dd><cite><a href="">Member Web site</a></cite></dd>
  2952         <dt id="ref-member-sub">[MEM8]</dt>
  2953          <dd><cite><a href="">How to send a Submission request</a></cite></dd>
  2954         <dt>[MEM9]</dt>
  2955          <dd><cite><a href="">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other collaborators, is now a Public resource [<a href="ref-guide">PUB37</a>]</dd>
  2956         <dt id="ref-discipline-gl">[MEM14]</dt>
  2957          <dd><cite><a href="">Guidelines for Disciplinary Action</a></cite></dd>
  2958         <dt id="ref-election-howto">[MEM15]</dt>
  2959          <dd><cite><a href="">How to Organize an Advisory Board or TAG election</a></cite></dd>
  2960       </dl>
  2962       <h3 id="other-refs">12.3 Other References</h3>
  2964       <dl>
  2965         <dt id="ref-RFC2119">[RFC2119]</dt>
  2966          <dd><cite><a href="">"Key words for use in RFCs to Indicate Requirement Levels"</a></cite>, S. Bradner, March 1997.</dd>
  2967         <dt id="ref-RFC2777">[RFC2777]</dt>
  2968          <dd><cite><a href="">"Publicly Verifiable Nomcom Random Selection"</a></cite>, D. Eastlake 3rd, February 2000.</dd>
  2969       </dl>
  2971       <h2 id="acks">13 Acknowledgments</h2>
  2973       <p>The following individuals (some as individuals, others with the affiliation listed) have contributed to this
  2974         proposal for a revised Process: Daniel Appelquist,
  2975         David Baron (Mozilla), J Alan Bird (W3C), Carine Bournez (W3C), Wayne Carr (Intel),
  2976         Tantek Çelik (Mozilla), Michael Champion (Microsoft), Maria Courtemanche (IBM), Donald Deutsch (Oracle),
  2977         Geoffrey Creighton (Microsoft), Kevin Fleming (Bloomberg), Virginia Fournier (Apple), Virginie Galindo (Gemalto),
  2978         Daniel Glazman (Disruptive Innovations), Michael Geldblum (Oracle), Ian Jacobs (W3C), Jeff Jaffe (W3C),
  2979         Jay Kishigami 岸上順一 (NTT), Philippe LeHégaret (W3C), Coralie Mercier (W3C),
  2980         Mark Nottingham, Peter Patel-Schneider, Scott Peterson (Google), Delfí Ramírez, Florian Rivoal, Wendy Seltzer (W3C),
  2981         David Singer (Apple), Geoffrey Snedden, Josh Soref, Ralph Swick (W3C), 
  2982         Léonie Watson (The Paciello Group), Ben Wilson, Chris Wilson (Google), Rigo Wenning (W3C), Helene Workman (Apple),
  2983         Judy Zhu 朱红儒 (Alibaba), Steve Zilles (Adobe).
  2984       <br>The editor is sorry for forgetting any names, and grateful to those who have listened patiently to conversations
  2985         about this document, without feeling a need to add more.</p>
  2987       <p>The following individuals contributed to the development of earlier versions of the Process:
  2988         Jean-François Abramatic (IBM, and previously ILOG and W3C), Dan Appelquist (Telefonica), Art Barstow (Nokia, unaffiliated),
  2989         Ann Bassetti (The Boeing Company), Jim Bell (HP), Robin Berjon (W3C), Tim Berners-Lee (W3C),
  2990         Klaus Birkenbihl (Fraunhofer Gesellschaft), Judy Brewer (W3C), Don Brutzman (Web3D),
  2991         Carl Cargill (Netscape, Sun Microsystems), Wayne Carr (Intel), Marcos Cáceres (Mozilla), Michael Champion (Microsoft),
  2992         Paul Cotton (Microsoft), Mark Crawford (SAP), Tantek Çelik (Mozilla), Don Deutsch (Oracle), Karl Dubost (Mozilla),
  2993         David Fallside (IBM), Fantasai (Mozilla), Wendy Fong (Hewlett-Packard), Virginie Galindo (Gemalto),
  2994         Daniel Glazman (Disruptive Innovations), Paul Grosso (Arbortext), Eduardo Gutentag (Sun Microsystems), Joe Hall (CDT),
  2995         Ivan Herman (W3C), Ian Hickson (Google), Brad Hill (Facebook), Steve Holbrook (IBM), Renato Iannella (IPR Systems),
  2996         Ian Jacobs (W3C), Jeff Jaffe (W3C), Cullen Jennings (Cisco), Brain Kardell (JQuery), Sally Khudairi (W3C),
  2997         John Klensin (MCI), Tim Krauskopf (Spyglass), Kari Laihonen (Ericsson), Ken Laskey (MITRE), Ora Lassila (Nokia),
  2998         Håkon Wium Lie (Opera Software), Chris Lilley (W3C), Peter Linss (HP), Bede McCall (MITRE), Giri Mandyam (Qualcomm),
  2999         Larry Masinter (Adobe Systems), Nigel Megitt (BBC), Olle Olsson (SICS), Mark Nottingham, Qiuling Pan (Huawei),
  3000         TV Raman (Google),
  3001         Thomas Reardon (Microsoft), Claus von Riegen (SAP AG), Natasha Rooney (GSMA), Sam Ruby (IBM), David Singer (Apple),
  3002         David Singer (IBM), Henri Sivonen (Mozilla), Josh Soref (BlackBerry), Ralph Swick (W3C), Anne van Kesteren,
  3003         Jean-Charles Verdié (MStar), Mike West (Google),  Chris Wilson (Google), Lauren Wood (unaffiliated),
  3004         and Steve Zilles (Adobe Systems).</p>
  3006       <h2 id="changes">14 Changes</h2>
  3008       <p>This document is based on the <a href="">1 September 2015 Process</a>.
  3009         <a href="">Detailed logs of all changes</a> are available.</p>
  3011       <p>Substantive changes compared to the <a href="">1 September 2015 Process</a>
  3012         include:</p>
  3014       <ul>
  3015         <li>Added link to document explaining Obsolete and Rescinded Recommendations - section <a href="#rec-rescind">6.9</a></li>
  3016         <li>Allow Edited Recommendations to incorporate editorial changes without Advisory Committee review 
  3017           - <a href="#revised-rec">Section 6.7.2</a></li>
  3018         <li>Replace diagrams of Recommendation track with new versions to improve accessibility and accuracy
  3019           - section <a href="#recs-and-notes">6.1.1</a> and section <a href="#rec-modify">6.7</a></li>
  3020         <li>Remove statement that W3C does not organise conferences
  3021           - section <a href="#GAEvents">8</a></li>
  3022         <li>Added a process to make a Recommendation Obsolete - section <a href="#rec-rescind">6.9</a></li>
  3023         <li>Clarified the process to rescind a Recommendation, aligning with with obsoleting a Recommendation
  3024           - section <a href="#rec-rescind">6.9</a></li>
  3025         <li>Clarified the process for continuing work on a specification initially developed under another charter
  3026           - sections <a href="#CharterReview">5.2.3</a>, <a href="#cfp">5.2.4</a>, <a href="#WGCharter">5.2.6</a>,
  3027           <a href="#transition-reqs">6.2.2</a>.</li>
  3028         <li>Changed the voting for AB and TAG elections to Single Transferable Vote
  3029           - section <a href="AB-TAG-Elections">2.5.2</a></li>
  3030         <li>Clarified the rights and obligations of Member Consortia and their representatives
  3031           - section <a href="#MemberBenefits">2.1.1</a></li>
  3032         <li>Renumber: 5.2.8 becomes 5.2.7 because there was no section 5.2.7</li>
  3033         <li>Simplify Appeals, so they can occur whether there was dissent or not, and in a broader range of cases 
  3034           - sections <a href="#candidate-rec">6.4</a>, <a href="#rec-publication">6.6</a>, <a href="#rec-rescind">6.9</a>,
  3035           <a href="#ReviewAppeal">7</a>, <a href="#ACAppeal">7.2</a>, <a href="ACVotes">7.3</a>,
  3036           <a href="#Submission">10</a>, <a href="#SubmissionNo">10.4</a>, <a href="#GAProcess">11</a></li>
  3037       </ul>
  3039     </main>
  3040   </body>
    14   </body>
  3041 </html>
    15 </html>