--- a/cover.html Mon Jul 11 00:14:02 2016 +0200
+++ b/cover.html Mon Jul 11 01:38:52 2016 +0200
@@ -31,32 +31,46 @@
<dt>Previous editor:</dt>
<dd>Ian Jacobs, <a href="https://www.w3.org/">W3C</a></dd>
</dl>
- <p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1996-2016 <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
- (<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr
- title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>,
- <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
- <a href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a rel="Copyright" href="/Consortium/Legal/copyright-documents">document
- use</a> and <a rel="Copyright" href="/Consortium/Legal/copyright-software">software licensing</a> rules apply. Your interactions
- with this site are in accordance with our <a href="/Consortium/Legal/privacy-statement#Public">public</a> and <a href="/Consortium/Legal/privacy-statement#Members">Member</a>
- privacy statements.</p>
+
+ <p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1996-2016
+ <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
+ (<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
+ <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
+ <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C
+ <a href="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
+ <a href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
+ <a rel="Copyright" href="/Consortium/Legal/copyright-documents">document use</a> and
+ <a rel="Copyright" href="/Consortium/Legal/copyright-software">software licensing</a> rules apply. Your interactions
+ with this site are in accordance with our <a href="/Consortium/Legal/privacy-statement#Public">public</a> and
+ <a href="/Consortium/Legal/privacy-statement#Members">Member</a> privacy statements.</p>
+
<hr></div>
+
<h2 class="notoc"><a id="abstract">Abstract</a></h2>
+
<p>The mission of the World Wide Web Consortium (<abbr>W3C</abbr>) is to lead the World Wide Web to its full potential by developing
common protocols that promote its evolution and ensure its interoperability. The W3C Process Document describes the organizational
structure of the W3C and the processes related to the responsibilities and functions they exercise to enable W3C to accomplish its
mission. This document does not describe the internal workings of the Team or W3C's public communication mechanisms.</p>
<p>For more information about the W3C mission and the history of W3C, please refer to <a href="https://www.w3.org/Consortium/">About W3C</a>
[<a href="#ref-mission">PUB15</a>].</p>
+
<h2 class="notoc" id="status">Status of this Document</h2>
- <p>W3C, including all existing chartered groups, follows the <a href="https://www.w3.org/Consortium/Process/">most recent operative
- Process Document</a> announced to the Membership.</p>
- <p>This document is developed by the Advisory Board's Process Task Force (which anyone may join) working within the <a href="https://www.w3.org/community/w3process/">Revising
- W3C Process Community Group</a>. This is the 10 July 2016 Editor's draft for the proposed next version of the W3C Process Document.
- This document is based on the 1 September 2015 Process.</p>
- <p>This draft is expected to be proposed to the Advisory Committee for a formal AC review on whether to adopt this as the new operative
- Process document. Further revision to the Process is expected as needed.</p>
- <p>A <a href="#changes">change history</a>
- (compared to the current 1 September 2015 Process Document) forms part of this draft.</p>
+
+ <p>W3C, including all existing chartered groups, follows the
+ <a href="https://www.w3.org/Consortium/Process/">most recent operative Process Document</a> announced to the Membership.</p>
+
+ <p>This document is developed by the Advisory Board's Process Task Force (which anyone may join) working within the
+ <a href="https://www.w3.org/community/w3process/">Revising W3C Process Community Group</a>. This is the 10 July 2016
+ Editor's draft for the proposed next version of the W3C Process Document. This document is based on the 1 September 2015
+ Process.</p>
+
+ <p>This draft is offered to the Advisory Committee and the Public for information, prior to any formal AC review on whether to
+ adopt this as the new operative Process document. Further revision to the Process is expected as needed.</p>
+
+ <p>A <a href="#changes">change history</a> (compared to the current 1 September 2015 Process Document) forms part of
+ this draft.</p>
+
<p>Comment is invited on the draft. Please send comments to <a href="mailto:public-w3process@w3.org">public-w3process@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-w3process/">Mailing
list archive</a>, publicly available) or to process-issues@w3.org (<a href="https://lists.w3.org/Archives/Member/process-issues">Member-only
archive</a>). A <a href="https://www.w3.org/community/w3process/track/">Public Issue Tracker</a> and <a href="https://dvcs.w3.org/hg/AB/">detailed
@@ -183,7 +197,7 @@
<li class="tocline4"><a href="#cfp">5.2.4 Call for Participation in a Working Group or Interest Group</a></li>
<li class="tocline4"><a href="#charter-extension">5.2.5 Working Group and Interest Group Charter Extension</a></li>
<li class="tocline4"><a href="#WGCharter">5.2.6 Working Group and Interest Group Charters</a></li>
- <li class="tocline4"><a href="#GeneralTermination">5.2.8 Working Group and Interest Group Closure</a></li>
+ <li class="tocline4"><a href="#GeneralTermination">5.2.7 Working Group and Interest Group Closure</a></li>
</ul>
</li>
</ul>
@@ -277,36 +291,46 @@
<li class="tocline2"><a href="#changes">14 Changes</a></li>
</ul>
</div>
+
<main>
+
<h2 id="Intro">1 Introduction</h2>
- <p>Most W3C work revolves around the standardization of Web technologies. To accomplish this work, W3C follows processes that promote
- the development of high-quality standards based on the <a href="#Consensus">consensus</a> of the Membership, Team, and public. W3C
+
+ <p>Most W3C work revolves around the standardization of Web technologies. To accomplish this work, W3C follows processes that
+ promote the development of high-quality standards based on the <a href="#Consensus">consensus</a> of the Membership, Team,
+ and public. W3C
processes promote fairness, responsiveness, and progress: all facets of the W3C mission. This document describes the processes W3C
follows in pursuit of its mission.</p>
<p>Here is a general overview of how W3C standardizes a Web technology. In many cases, the goal of this work is a <a href="#RecsW3C">W3C
Recommendation</a>, the W3C equivalent of a Web standard.</p>
+
<ol>
- <li>People generate interest in a particular topic (e.g., Web services). For instance, Members express interest in the form of <a href="#Submission">Member
- Submissions</a>, and the <a href="#Team">Team</a> monitors work inside and outside of W3C for signs of interest. Also, W3C is
- likely to organize a <a href="#GAEvents">Workshop</a> to bring people together to discuss topics that interest the W3C community.</li>
- <li>When there is enough interest in a topic (e.g., after a successful Workshop and/or discussion on an <a href="#ACCommunication">Advisory
- Committee mailing list</a>), the Director announces the development of a proposal for one or more new <a href="#WGCharterDevelopment">Interest
- Group or Working Group charters</a>, depending on the breadth of the topic of interest. W3C Members <a href="#ActivityCreation">review</a>
- the proposed charters. When there is support within W3C for investing resources in the topic of interest, the Director approves
- the group(s) and they begin their work.</li>
- <li>There are three types of Working Group participants: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited
- Experts</a>, and <a href="#Team">Team representatives</a>. Team representatives both contribute to the technical work and help
- ensure the group's proper integration with the rest of W3C. The <a href="#WGCharter">Working Group charter</a> sets expectations
- about each group's deliverables (e.g., <a href="#Reports">technical reports</a>, test suites, and tutorials).</li>
- <li>Working Groups generally create specifications and guidelines that undergo cycles of revision and review as they <a href="#rec-advance">advance
- to W3C Recommendation</a> status. The W3C process for producing these technical reports includes significant review by the
- Members and public, and requirements that the Working Group be able to show implementation and interoperability experience. At the
- end of the process, the Advisory Committee reviews the mature technical report, and if there is support, W3C publishes it as a <a
- href="#RecsW3C">Recommendation</a>.</li>
+ <li>People generate interest in a particular topic (e.g., Web services). For instance, Members express interest in the form
+ of <a href="#Submission">Member Submissions</a>, and the <a href="#Team">Team</a> monitors work inside and outside of W3C
+ for signs of interest. Also, W3C is likely to organize a <a href="#GAEvents">Workshop</a> to bring people together to
+ discuss topics that interest the W3C community.</li>
+ <li>When there is enough interest in a topic (e.g., after a successful Workshop and/or discussion on an
+ <a href="#ACCommunication">Advisory Committee mailing list</a>), the Director announces the development of a proposal for
+ one or more new <a href="#WGCharterDevelopment">Interest Group or Working Group charters</a>, depending on the breadth of
+ the topic of interest. W3C Members <a href="#ActivityCreation">review</a> the proposed charters. When there is support
+ within W3C for investing resources in the topic of interest, the Director approves the group(s) and they begin their
+ work.</li>
+ <li>There are three types of Working Group participants: <a href="#member-rep">Member representatives</a>,
+ <a href="#invited-expert-wg">Invited Experts</a>, and <a href="#Team">Team representatives</a>. Team representatives both
+ contribute to the technical work and help ensure the group's proper integration with the rest of W3C. The
+ <a href="#WGCharter">Working Group charter</a> sets expectations about each group's deliverables (e.g.,
+ <a href="#Reports">technical reports</a>, test suites, and tutorials).</li>
+ <li>Working Groups generally create specifications and guidelines that undergo cycles of revision and review as they
+ <a href="#rec-advance">advance to W3C Recommendation</a> status. The W3C process for producing these technical reports
+ includes significant review by the Members and public, and requirements that the Working Group be able to show
+ implementation and interoperability experience. At the end of the process, the Advisory Committee reviews the mature
+ technical report, and if there is support, W3C publishes it as a <a href="#RecsW3C">Recommendation</a>.</li>
</ol>
- <p>The Process Document promotes the goals of quality and fairness in technical decisions by encouraging <a href="#Consensus">consensus</a>,
- requiring reviews (by both Members and public) as part of the <a href="#Reports">technical report development process</a>, and
- through an <a href="#ACAppeal">appeal process</a> for the Advisory Committee.</p>
+
+ <p>The Process Document promotes the goals of quality and fairness in technical decisions by encouraging
+ <a href="#Consensus">consensus</a>, requiring reviews (by both Members and public) as part of the
+ <a href="#Reports">technical report development process</a>, and through an <a href="#ACAppeal">Advisory Committee Appeal process</a>.</p>
+
<p>The other sections of the Process Document:</p>
<ol>
<li>set forth <a href="#Policies">policies</a> for participation in W3C groups,</li>
@@ -319,23 +343,32 @@
<h2 id="Organization">2 Members, Advisory Committee, Team, Advisory Board, Technical Architecture Group</h2>
<p>W3C's mission is to lead the Web to its full potential. W3C <a href="#Members">Member</a> organizations provide resources to this
end, and the W3C <a href="#Team">Team</a> provides the technical leadership and organization to coordinate the effort.</p>
+
<h3 id="Members">2.1 Members</h3>
+
<p>W3C Members are primarily represented in W3C processes as follows:</p>
+
<ol>
- <li>The <a href="#AC">Advisory Committee</a> is composed of one representative from each Member organization (refer to the <a href="#Member-only">Member-only</a>
- list of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a> [<a href="#ref-current-ac">MEM1</a>]).
+ <li>The <a href="#AC">Advisory Committee</a> is composed of one representative from each Member organization (refer to the
+ <a href="#Member-only">Member-only</a> list of
+ <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>
+ [<a href="#ref-current-ac">MEM1</a>]).
The Advisory Committee:
<ul>
<li>reviews plans for W3C at each <a href="#ACMeetings">Advisory Committee meeting</a>;</li>
- <li>reviews formal proposals from the W3C Director: <a href="#CharterReview">Charter Proposals</a>, <a href="#RecsPR">Proposed
- Recommendations</a>, and <a href="#GAProcess">Proposed Process Documents</a>.</li>
+ <li>reviews formal proposals from the W3C Director: <a href="#CharterReview">Charter Proposals</a>,
+ <a href="#RecsPR">Proposed Recommendations</a>, and <a href="#GAProcess">Proposed Process Documents</a>.</li>
<li>elects the <a href="#AB">Advisory Board</a> participants other than the Advisory Board Chair.</li>
<li>elects 5 of the 9 participants on the <a href="#TAG">Technical Architecture Group</a>.</li>
</ul>
- Advisory Committee representatives have <a href="#ACAppeal">appeal</a> powers for some processes described in this document.</li>
- <li>Representatives of Member organizations participate in <a href="#GAGeneral">Working Groups and Interest Groups</a> and author
- and review <a href="#Reports">technical reports</a>.</li>
+
+ Advisory Committee representatives <em class="rfc2119">may</em> initiate an
+ <a href="#ACAppeal">Advisory Committee Appeal</a> in some cases described in this document.</li>
+
+ <li>Representatives of Member organizations participate in <a href="#GAGeneral">Working Groups and Interest Groups</a> and
+ author and review <a href="#Reports">technical reports</a>.</li>
</ol>
+
<p id="MemberSubscription">W3C membership is open to all entities, as described in "<a href="https://www.w3.org/Consortium/join">How to
Join W3C</a>" [<a href="#ref-join-w3c">PUB5</a>]; (refer to the public list of <a href="https://www.w3.org/Consortium/Member/List">current
W3C Members</a> [<a href="#ref-current-mem">PUB8</a>]). Organizations subscribe according to the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
@@ -345,35 +378,60 @@
<p id="IndividualParticipation">W3C does not have a class of membership tailored to, or priced for individuals. However, an individual
<em class="rfc2119">may</em> join W3C as an Affiliate Member. In this case the same restrictions pertaining to <a href="#MemberRelated">related
Members</a> apply when the individual also <a href="#member-rep">represents</a> another W3C Member.</p>
+
<h4 id="MemberBenefits">2.1.1 Rights of Members</h4>
+
<p>Each Member organization enjoys the following rights and benefits:</p>
+
<ul>
<li>A seat on the <a href="#AC">Advisory Committee</a>;</li>
<li>Access to <a href="#Member-only">Member-only</a> information;</li>
<li>The <a href="#Submission">Member Submission</a> process;</li>
- <li>Use of the W3C Member logo on promotional material and to publicize the Member's participation in W3C. For more information,
- please refer to the Member logo usage policy described in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a>
- [<a href="#ref-new-member">MEM4</a>].</li>
+ <li>Use of the W3C Member logo on promotional material and to publicize the Member's participation in W3C. For more
+ information, please refer to the Member logo usage policy described in the
+ <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [<a href="#ref-new-member">MEM4</a>].</li>
</ul>
- <p>Furthermore, representatives of Member organizations participate in W3C as follows:</p>
+
+ <p>Furthermore, subject to further restrictions included in the Member Agreement, representatives of Member organizations
+ participate in W3C as follows:</p>
+
<ul>
<li>In <a href="#GAGeneral">Working Groups and Interest Groups</a>.</li>
<li>In <a href="#GAEvents">Workshops and Symposia</a>;</li>
<li>On the Team, as <a href="#fellows">W3C Fellows</a>.</li>
</ul>
- <p>In the case (described in paragraph 5g of the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
- Agreement</a>), where a Member organization is itself a consortium, user society, or otherwise has members or sponsors, the
- organization's paid staff and Advisory Committee representative exercise all the rights and privileges of W3C membership. In
- addition, the Advisory Committee representative <em class="rfc2119">may</em> designate up to four (or more at the Team's
- discretion) individuals who, though not employed by the organization, <em class="rfc2119">may</em> exercise the rights of <a href="#member-rep">Member
- representatives</a>. These individuals <em class="rfc2119">must</em> disclose their employment affiliation when participating in
- W3C work. Provisions for <a href="#MemberRelated">related Members</a> apply. Furthermore, these individuals are expected to
- represent the broad interests of the W3C Member organization and not the parochial interests of their employers.</p>
- <p>The rights and benefits of W3C membership are contingent upon conformance to the processes described in this document. The vast
- majority of W3C Members faithfully follow the spirit as well as the letter of these processes. When serious and/or repeated
- violations do occur, and repeated attempts to address these violations have not resolved the situation, the Director <em class="rfc2119">may</em>
- take disciplinary action. Arbitration in the case of further disagreement is governed by paragraph 19 of the Membership Agreement.
- Refer to the <a href="https://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a> [<a href="#ref-discipline-gl">MEM14</a>].</p>
+
+ <p>In the Member is itself a consortium, user society, or otherwise has members or sponsors, as described in paragraph 5g of
+ the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a>), the rights and privileges
+ of W3C Membership granted by W3C Process extend to the the organization's paid staff and Advisory Committee.</p>
+
+ <p>Such an organization <em class="rfc2119">may</em> also designate up to four (or more at the Team's discretion) individuals
+ who, though not employed by the organization, <em class="rfc2119">may</em> exercise the rights of
+ <a href="#member-rep">Member representatives</a>.
+
+ <p>For Consortia who have individual persons as members these individuals <em class="rfc2119">must</em> disclose their
+ employment affiliation when participating in W3C work. Provisions for <a href="#MemberRelated">related Members</a> apply.
+ Furthermore, these individuals <em class="rfc2119">must</em> represent the broad interests of the W3C Member organization
+ and not the particular interests of their employers.</p>
+
+ <p>For Consortia who have organizations as Members, all such designated representatives must be an official representative
+ of the Member organization (i.e. a Committee or Task Force Chairperson) and <em class="rfc2119">must</em> disclose their
+ employment affiliation when participating in W3C work. Provisions for <a href="#MemberRelated">related Members</a> apply.
+ Furthermore, these individuals <em class="rfc2119">must</em> represent the broad interests of the W3C Member organization
+ and not the particular interests of their employers.</p>
+
+ <p>For all representatives of a Member that is a Consortium, as described in the preceeding two paragraphs, any IPR
+ contributions are only those of the individual person or Consortium they are representing as no IPR commitments have been
+ granted by the individuals' employers.</p>
+
+ <p>The rights and benefits of W3C membership are contingent upon conformance to the processes described in this document.
+ The vast majority of W3C Members faithfully follow the spirit as well as the letter of these processes. When serious and/or
+ repeated violations do occur, and repeated attempts to address these violations have not resolved the situation, the
+ Director <em class="rfc2119">may</em> take disciplinary action. Arbitration in the case of further disagreement is governed
+ by paragraph 19 of the Membership Agreement. Refer to the
+ <a href="https://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a>
+ [<a href="#ref-discipline-gl">MEM14</a>].</p>
+
<h4 id="MemberRelated">2.1.2 Related Members</h4>
<p>In the interest of ensuring the integrity of the consensus process, Member involvement in some of the processes in this document is
affected by related Member status. As used herein, two Members are related if:</p>
@@ -446,11 +504,14 @@
and the public about the Web and W3C technologies.</p>
<p>The Director and CEO <em class="rfc2119">may</em> delegate responsibility (generally to other individuals in the Team) for any of
their roles described in this document.</p>
- <p>The <dfn id="def-Director">Director</dfn> is the lead technical architect at W3C. His responsibilities are identified throughout
- this document in relevant places Some key ones include: assessing <a href="#def-Consensus" id="DirectorDecision">consensus</a>
- within W3C for architectural choices, publication of <a href="#Reports">technical reports</a>, and chartering new Groups;
- appointing group <a href="#GeneralChairs">Chairs</a>; "tie-breaker" for <a href="#WGAppeals">appeal of a Working Group decision</a>
- and deciding on the outcome of formal objections; the Director is generally Chair of the <a href="#TAG">TAG</a>.</p>
+
+ <p>The <dfn id="def-Director">Director</dfn> is the lead technical architect at W3C. His responsibilities are identified
+ throughout this document in relevant places Some key ones include: assessing
+ <a href="#def-Consensus" id="DirectorDecision">consensus</a> within W3C for architectural choices, publication of
+ <a href="#Reports">technical reports</a>, and chartering new Groups; appointing group <a href="#GeneralChairs">Chairs</a>;
+ adjudicating as "tie-breaker" for <a href="#WGAppeals">Group decision appeals</a> and deciding on the outcome of formal
+ objections; the Director is generally Chair of the <a href="#TAG">TAG</a>.</p>
+
<p>Team administrative information such as Team salaries, detailed budgeting, and other business decisions are <a href="#Team-only">Team-only</a>,
subject to oversight by the Host institutions.</p>
<p><strong>Note:</strong> W3C is not currently incorporated. For legal contracts, W3C is represented by four <dfn id="hosts">"Host"
@@ -465,12 +526,16 @@
<p>Team Submissions are <strong>not</strong> part of the <a href="#Reports">technical report development process</a>.</p>
<p>The list of <a href="https://www.w3.org/TeamSubmission/">published Team Submissions</a> [<a href="#ref-team-submission-list">PUB16</a>]
is available at the W3C Web site.</p>
+
<h3 id="AB">2.3 Advisory Board (AB)</h3>
- <p>Created in March 1998, the Advisory Board provides ongoing guidance to the Team on issues of strategy, management, legal matters,
- process, and conflict resolution. The Advisory Board also serves the Members by tracking issues raised between Advisory Committee
- meetings, soliciting Member comments on such issues, and proposing actions to resolve these issues. The Advisory Board manages the <a
- href="#GAProcess">evolution of the Process Document</a>. The Advisory Board hears appeals of <a href="#SubmissionNo">Member
- Submission requests</a> that are rejected for reasons unrelated to Web architecture; see also the <a href="#TAG">TAG</a>.</p>
+
+ <p>Created in March 1998, the Advisory Board provides ongoing guidance to the Team on issues of strategy, management,
+ legal matters, process, and conflict resolution. The Advisory Board also serves the Members by tracking issues raised
+ between Advisory Committee meetings, soliciting Member comments on such issues, and proposing actions to resolve these
+ issues. The Advisory Board manages the <a href="#GAProcess">evolution of the Process Document</a>. The Advisory Board hears
+ a <a href="#SubmissionNo">Submission Appeal</a> when a Member Submission is rejected for reasons unrelated to Web
+ architecture; see also the <a href="#TAG">TAG</a>.</p>
+
<p>The Advisory Board is <strong>not</strong> a board of directors and has no decision-making authority within W3C; its role is
strictly advisory.</p>
<p>The Team <em class="rfc2119">must</em> make available a mailing list for the Advisory Board to use for its communication,
@@ -497,8 +562,10 @@
<li>to resolve issues involving general Web architecture brought to the TAG;</li>
<li>to help coordinate cross-technology architecture developments inside and outside W3C.</li>
</ol>
- <p>The TAG hears appeals of <a href="#SubmissionNo">Member Submission requests</a> that are rejected for reasons related to Web
- architecture; see also the <a href="#AB">Advisory Board</a>.</p>
+
+ <p>The TAG hears a <a href="#SubmissionNo">Submission Appeal</a> when a Member Submission is rejected for reasons related
+ to Web architecture; see also the <a href="#AB">Advisory Board</a>.</p>
+
<p>The TAG's scope is limited to technical issues about Web architecture. The TAG <em class="rfc2119">should not</em> consider
administrative, process, or organizational policy issues of W3C, which are generally addressed by the W3C Advisory Committee,
Advisory Board, and Team. Please refer to the <a href="https://www.w3.org/2001/07/19-tag">TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
@@ -509,9 +576,11 @@
<li>a <a href="#Member-only">Member-only</a> list for discussions within the TAG and for requests to the TAG that, for whatever
reason, cannot be made on the public list.</li>
</ul>
- <p>The TAG <em class="rfc2119">may</em> also request the creation of additional topic-specific, public mailing lists. For some TAG
- discussions (e.g., an appeal of a <a href="#SubmissionNo">rejected Member Submission request</a>), the TAG <em class="rfc2119">may</em>
+
+ <p>The TAG <em class="rfc2119">may</em> also request the creation of additional topic-specific, public mailing lists.
+ For some TAG discussions (e.g., a <a href="#SubmissionNo">Submission Appeal</a>), the TAG <em class="rfc2119">may</em>
use a list that will be <a href="#Member-only">Member-only</a>.</p>
+
<p>The TAG <em class="rfc2119">should</em> send a summary of each of its <a href="#GeneralMeetings">meetings</a> to the Advisory
Committee and other group Chairs. The TAG <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory
Committee meeting</a>.</p>
@@ -846,14 +915,19 @@
<p>A group charter <em class="rfc2119">should</em> include formal voting procedures (e.g., quorum or threshold requirements) for
making decisions about substantive issues.</p>
<p>Procedures for <a href="#ACVotes">Advisory Committee votes</a> are described separately.</p>
+
<h3 id="WGAppeals">3.5 Appeal of a Chair's Decision</h3>
- <p>Groups resolve issues through dialog. Individuals who disagree strongly with a decision <em class="rfc2119">should</em> register
- with the Chair any <a href="#FormalObjection">Formal Objections</a> (e.g., to a decision made as the result of a <a href="#Votes">vote</a>).</p>
- <p>When group participants believe that their concerns are not being duly considered by the group, they <em class="rfc2119">may</em>
- ask the <a href="#def-Director">Director</a> (for representatives of a Member organization, via their Advisory Committee
- representative) to confirm or deny the decision. The participants <em class="rfc2119">should</em> also make their requests known to
- the <a href="#TeamContact">Team Contact</a>. The Team Contact <em class="rfc2119">must</em> inform the Director when a group
+
+ <p>Groups resolve issues through dialog. Individuals who disagree strongly with a decision <em class="rfc2119">should</em>
+ register with the Chair any <a href="#FormalObjection">Formal Objections</a> (e.g., to a decision made as the result of a <a href="#Votes">vote</a>).</p>
+
+ <p>When group participants believe that their concerns are not being duly considered by the group, they
+ <em class="rfc2119">may</em> ask the <a href="#def-Director">Director</a> (for representatives of a Member organization,
+ via their Advisory Committee representative) to confirm or deny the decision. This is a <dfn>Group Decision Appeal</dfn>.
+ The participants <em class="rfc2119">should</em> also make their requests known to the
+ <a href="#TeamContact">Team Contact</a>. The Team Contact <em class="rfc2119">must</em> inform the Director when a group
participant has raised concerns about due process.</p>
+
<p>Any requests to the Director to confirm a decision <em class="rfc2119">must</em> include a summary of the issue (whether technical
or procedural), decision, and rationale for the objection. All counter-arguments, rationales, and decisions <em class="rfc2119">must</em>
be recorded.</p>
@@ -1135,8 +1209,9 @@
<p>After a Call for Participation, any <a href="#member-rep">Member representatives</a> and
<a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">must</em> be designated (or re-designated).</p>
- <p>Advisory Committee representatives <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> creation or substantive
- modification of a Working Group or Interest Group charter.</p>
+ <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate an
+ <a href="#ACAppeal">Advisory Committee Appeal</a> against a Director's decision to create or substantially modify a
+ Working Group or Interest Group charter.</p>
<h4>5.2.5 <dfn id="charter-extension">Working Group and Interest Group Charter Extension</dfn></h4>
@@ -1148,7 +1223,8 @@
<p>After a charter extension, Advisory Committee representatives and the Chair are <em class="rfc2119">not required</em>
to re-designate <a href="#member-rep">Member representatives</a> and <a href="#invited-expert-wg">Invited Experts</a>.</p>
- <p>Advisory Committee representatives <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> the extension of a
+ <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate an
+ <a href="#ACAppeal">Advisory Committee Appeal</a> against a Director's decision regarding the extension of a
Working Group or Interest Group charter.</p>
<h4>5.2.6 <dfn id="WGCharter">Working Group and Interest Group Charters</dfn></h4>
@@ -1219,9 +1295,11 @@
Process Document (e.g., limits on the number of individuals in a Working Group who represent the same Member organization
or group of <a href="#MemberRelated">related Members</a>).</p>
- <h4>5.2.8 <dfn id="GeneralTermination">Working Group and Interest Group Closure</dfn></h4>
- <p>A Working Group or Interest Group charter specifies a duration for the group. The Director, subject to <a href="#ACAppeal">appeal</a>
- by Advisory Committee representatives, <em class="rfc2119">may</em> close a group prior to the date specified in the charter in
+ <h4>5.2.7 <dfn id="GeneralTermination">Working Group and Interest Group Closure</dfn></h4>
+
+ <p>A Working Group or Interest Group charter specifies a duration for the group. The Director, subject to
+ an <a href="#ACAppeal">Advisory Committee Appeal</a>initiated by Advisory Committee representatives,
+ <em class="rfc2119">may</em> decide to close a group prior to the date specified in the charter in
any of the following circumstances:</p>
<ul>
<li>There are insufficient resources to produce chartered deliverables or to maintain the group, according to priorities
@@ -1567,9 +1645,8 @@
<li><a href="#rec-pr">Proposed Recommendation</a> (The expected next step)</li>
<li><a href="#Note">Working Group Note</a></li>
</ul>
- <p>If there was any <a href="#def-Dissent" rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
- to the Working Group decision to request advancement <a href="#AC">Advisory Committee</a> representatives <em class="rfc2119">may</em>
- <a href="#ACAppeal">appeal</a> the decision to advance the technical report.</p>
+ <p><a href="#AC">Advisory Committee</a> representatives <em class="rfc2119">may</em> initiate an
+ <a href="#ACAppeal">Advisory COmmittee Appeal</a> of the decision to advance the technical report.</p>
<h4 id="revised-cr">6.4.1 Revising a Candidate Recommendation</h4>
@@ -1639,11 +1716,13 @@
<li>A Recommendation <em class="rfc2119">must</em> identify where errata are tracked, and</li>
<li>A Recommendation <em class="rfc2119">must not</em> include any substantive changes from the Proposed Recommendation on which it
is based.</li>
- <li>If there was any <a href="#def-Dissent" rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
- in Advisory Committee reviews, the Director <em class="rfc2119">must</em> publish the substantive content of the dissent to W3C
- and the general public, and <em class="rfc2119">must</em> <a href="#formal-address">formally address</a> the comment at least 14
- days before publication as a W3C Recommendation. In this case the <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em>
- <a href="#ACAppeal">appeal</a> the decision,</li>
+ <li>If there was any
+ <a href="#def-Dissent" rel="glossary" title="Definition of Dissent"><span class="dfn-instance">dissent</span></a>
+ in Advisory Committee reviews, the Director <em class="rfc2119">must</em> publish the substantive content of the dissent
+ to W3C and the general public, and <em class="rfc2119">must</em> <a href="#formal-address">formally address</a>
+ the comment at least 14 days before publication as a W3C Recommendation.</li>
+ <li><a href="#AC">Advisory Committee</a> representatives <em class="rfc2119">may</em> initiate an
+ <a href="#ACAppeal">Advisory Committee Appeal</a> of the W3C decision</li>
<li>The Director <em class="rfc2119">must</em> announce the publication of a W3C Recommendation to <a href="#AC">Advisory
Committee</a>, other W3C groups and to the public.</li>
</ul>
@@ -1825,8 +1904,8 @@
<a href="#formal-address">formally address</a> the dissent at least 14 days before publication as an
Obsolete or Rescinded Recommendation.</p>
- <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> the
- Director's decision.</p>
+ <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an
+ <a href="#ACAppeal">Advisory Committee Appeal</a> of the Director's decision.</p>
<p>An Obsolete or Rescinded Recommendation <em class="rfc2119">must</em> be published with up to date status.
The updated version <em class="rfc2119">may</em> remove the main body of the document. The Status of this Document section
@@ -1842,13 +1921,13 @@
<p>Refer to <a href="https://www.w3.org/2003/05/Transitions">"How to Organize a Recommendation Track Transition"</a> in the <a href="https://www.w3.org/Guide/">Member
guide</a> for practical information about preparing for the reviews and announcements of the various steps, and <a href="https://www.w3.org/2002/05/rec-tips">tips
on getting to Recommendation faster</a> [<a href="#ref-rec-tips">PUB27</a>].</p>
+
<h2 id="ReviewAppeal">7 Advisory Committee Reviews, Appeals, and Votes</h2>
- <p>This section describes how the Advisory Committee reviews proposals from the Director and how Advisory Committee representatives
- appeal W3C decisions and decisions by the Director. A <dfn id="def-w3c-decision">W3C decision</dfn> is one where the Director (or
- the Director's delegate) has exercised the role of assessing consensus after an <a href="#ACReview">Advisory Committee review</a>
- of an <a href="#CharterReview">Charter Proposal</a>, after a <a href="#cfr">Call for Review of a Proposed Recommendation</a>,
- after a <a href="#cfr-edited">Call for Review of a Proposed Recommendation</a>, after a <a href="#proposed-rescinded-rec">Proposal
- to Rescind a W3C Recommendation</a>, and after a <a href="#GAProcess">Proposed Process Document</a> review.</p>
+ <p>This section describes how the Advisory Committee reviews proposals from the Director and how Advisory Committee
+ representatives initiate an Advisory Committee Appeal of a W3C decision or Director's Decision. A
+ <dfn id="def-w3c-decision">W3C decision</dfn> is one where the Director (or the Director's delegate) has exercised the role
+ of assessing consensus after an <a href="#ACReview">Advisory Committee review</a>.</p>
+
<h3 id="ACReview">7.1 Advisory Committee Reviews</h3>
<p>The Advisory Committee reviews:</p>
<ul>
@@ -1892,38 +1971,45 @@
weeks</span> after the end of a Proposed Recommendation review period. If, after <span class="time-interval">three weeks</span>,
the Director has not announced the outcome, the Director <em class="rfc2119">should</em> provide the Advisory Committee with an
update.</p>
+
<h3 id="ACAppeal">7.2 Appeal by Advisory Committee Representatives</h3>
- <p>Advisory Committee representatives <em class="rfc2119">may</em> appeal certain decisions, though appeals are only expected to
- occur in extraordinary circumstances.</p>
- <p>When Advisory Committee review immediately precedes a decision, Advisory Committee representatives <em class="rfc2119">may</em>
- only appeal when there is <a href="#def-Dissent">dissent</a>. These decisions are:</p>
- <ul>
- <li><a href="#rec-publication">Publication of a Recommendation</a> or <a href="#proposed-rescinded-rec">Publication of a Rescinded
- Recommendation</a>,</li>
- <li><a href="#cfp">Working or Interest Group creation</a>, substantive <a href="#CharterReview">modification</a> or <a href="#charter-extension">extension</a>,</li>
- <li>Changes to the <a href="#GAProcess">W3C process</a>.</li>
- </ul>
- <p>Advisory Committee representatives <em class="rfc2119">may</em> always appeal the following decisions:</p>
- <ul>
- <li><a href="#charter-extension">Working or Interest Group extension</a> or <a href="#GeneralTermination">closure</a>,</li>
- <li><a href="#candidate-rec">Call for Implementations</a>, <a href="#cfr">Call for Review of a Proposed Recommendation</a>, <a href="#cfr-edited">Call
- for Review of an Edited Recommendation</a>, or <a href="#proposed-rescinded-rec">Proposal to Rescind a Recommendation</a></li>
- <li>the Director's intention to sign a <a href="#mou">Memorandum of Understanding</a> with another organization.</li>
- </ul>
+
+ <p>Advisory Committee representatives <em class="rfc2119">may</em> appeal certain decisions, though appeals are only expected
+ to occur in extraordinary circumstances.</p>
+
+ <p>When a W3C decision is made following an <a href="#ACReview">Advisory Committee review</a>, Advisory Committee
+ representatives <em class="rfc2119">may</em> initiate an <a href="#def-w3c-decision">Advisory Committee Appeal</a>.
+ only appeal when there is <a href="#def-Dissent">dissent</a>. These W3C decisions are identified in the sections that
+ explain the requirements for the decisions and include decisions related to group creation and modification, certain
+ maturity levels for Recommendation Track documents and the Process document.</p>
+
+ <p>Advisory Committee representatives <em class="rfc2119">may</em> also initiate an appeal for certain Director's decisions
+ that do not involve an Advisory Committee review. These, too, are identified in the sections which describe the
+ requirements for the Director's decision and include additional (non-reviewed) maturity levels of Recommendation Track
+ documents, group charter extensions and closures, and Memorandums of Understanding. Director's decisions on issues not
+ described in this Process Document <em class="rfc2119">may</em> also be appealed if the type of appeal is identified where
+ that Director's decision is described.</p>
+
<p>In all cases, an appeal <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the
decision.</p>
- <p>An Advisory Committee representative initiates an appeal by sending a request to the Team (explained in detail in the <a href="https://www.w3.org/Member/Intro">New
- Member Orientation</a>). The Team <em class="rfc2119">must</em> announce the appeal process to the Advisory Committee and provide
- an address for comments from Advisory Committee representatives. The archive of these comments <em class="rfc2119">must</em> be
- Member-visible. If, within <span class="time-interval">one week</span> of the Team's announcement, 5% or more of the Advisory
- Committee support the appeal request, the Team <em class="rfc2119">must</em> organize an appeal vote asking the Advisory Committee
- to approve or reject the decision.
+
+ <p>An Advisory Committee representative initiates an appeal by sending a request to the Team. Within one week the Team
+ <em class="rfc2119">must</em> announce the appeal process to the Advisory Committee and provide a mechanism for
+ Advisory Committee representatives to respond with a statement of support (yes, no or abstain) and comments, as desired.
+ The archive of these comments <em class="rfc2119">must</em> be Member-visible. If, within
+ <span class="time-interval">one week</span> of the Team's announcement, 5% or more of the Advisory Committee support the
+ appeal request, the Team <em class="rfc2119">must</em> organize an appeal vote asking the Advisory Committee to approve or
+ reject the decision.
<!-- Voting procedure to be determined --></p>
+
<h3 id="ACVotes">7.3 Advisory Committee Votes</h3>
- <p>The Advisory Committee votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>, and in the event
- of a formal appeal of a <a href="#def-w3c-decision">W3C decision</a>. Whenever the Advisory Committee votes, each Member or group
- of <a href="#MemberRelated">related Members</a> has one vote. In the case of <a href="#AB-TAG-elections">Advisory Board and TAG
- elections</a>, "one vote" means "one vote per available seat".</p>
+
+ <p>The Advisory Committee votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>, and in
+ the event of an <a href="#def-w3c-decision">Advisory Committee Appeal</a> achieving the required support to trigger an
+ appeal vote.. Whenever the Advisory Committee votes, each Member or group of <a href="#MemberRelated">related Members</a>
+ has one vote. In the case of <a href="#AB-TAG-elections">Advisory Board and TAG elections</a>, "one vote" means
+ "one vote per available seat".</p>
+
<h2 id="GAEvents">8 Workshops and Symposia</h2>
<p>The Team organizes <dfn id="EventsW">Workshops</dfn> and <dfn id="EventsS">Symposia</dfn> to promote early involvement in the
development of W3C activities from Members and the public.</p>
@@ -1943,16 +2029,21 @@
<p><strong>Note:</strong> In general, W3C does not organize <dfn id="EventsC">conferences</dfn>. Currently, W3C presents its work to
the public at the annual World Wide Web Conference, which is coordinated by the <a href="http://www.iw3c2.org/">International World
Wide Web Conference Committee</a> (<abbr>IW3C2</abbr>).</p>
+
<h2 id="Liaisons">9 Liaisons</h2>
+
<p>W3C uses the term "liaison" to refer to coordination of activities with a variety of organizations, through a number of mechanisms
ranging from very informal (e.g., an individual from another organization participates in a W3C Working Group, or just follows its
work) to mutual membership, to even more formal agreements. Liaisons are not meant to substitute for W3C membership.</p>
<p>All liaisons <em class="rfc2119">must</em> be coordinated by the Team due to requirements for public communication; patent,
copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.</p>
- <p>The W3C Director <em class="rfc2119">may</em> negotiate and sign a <dfn id="mou">Memorandum of Understanding (<abbr>MoU</abbr>)</dfn>
- with another organization. Before signing the MoU, the Team <em class="rfc2119">must</em> inform the Advisory Committee of the
- intent to sign and make the MoU available for Advisory Committee review; the Advisory Committee <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a>.
- Once approved, a Memorandum of Understanding <em class="rfc2119">should</em> be made public.</p>
+
+ <p>The W3C Director <em class="rfc2119">may</em> negotiate and sign a <dfn id="mou">Memorandum of Understanding
+ (<abbr>MoU</abbr>)</dfn> with another organization. Before signing the MoU, the Team <em class="rfc2119">must</em> inform
+ the Advisory Committee of the intent to sign and make the MoU available for Advisory Committee review; Advisory Committee
+ representatives <em class="rfc2119">may</em> initiate an <a href="#ACAppeal">Advisory Committee Appeal</a> of the decision
+ to sign the MoU. Once approved, a Memorandum of Understanding <em class="rfc2119">should</em> be made public.</p>
+
<p>Information about <a href="https://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a> and the guidelines W3C
follows when creating a liaison [<a href="#ref-liaison-list">PUB28</a>] is available on the Web.</p>
<h2 id="Submission">10 Member Submission Process</h2>
@@ -1973,10 +2064,10 @@
to ensure that the Member Submission is complete.</li>
<li>After Team review, the Director <em class="rfc2119">must</em> either acknowledge or reject the Submission request.
<ul>
- <li>If <a href="#SubmissionYes">acknowledged</a>, the Team <em class="rfc2119">must</em> publish the Member Submission at the
- public W3C Web site, in addition to Team comments about the Member Submission.</li>
- <li>If <a href="#SubmissionNo">rejected</a>, the Submitter(s) <em class="rfc2119">may</em> appeal to either the <a href="#TAG">TAG</a>
- or the <a href="#AB">Advisory Board</a>.</li>
+ <li>If <a href="#SubmissionYes">acknowledged</a>, the Team <em class="rfc2119">must</em> publish the Member Submission
+ at the public W3C Web site, in addition to Team comments about the Member Submission.</li>
+ <li>If <a href="#SubmissionNo">rejected</a>, the Submitter(s) <em class="rfc2119">may</em> initiate a
+ <dfn>Submission Appeal</dfn> to either the <a href="#TAG">TAG</a> or the <a href="#AB">Advisory Board</a>.</li>
</ul>
</li>
</ol>
@@ -2074,7 +2165,9 @@
</ul>
<p>If the Submitter(s) wishes to modify a document published as the result of acknowledgment, the Submitter(s) <em class="rfc2119">must</em>
start the Submission process from the beginning, even just to correct editorial changes.</p>
- <h3 id="SubmissionNo">10.4 Rejection of a Submission Request</h3>
+
+ <h3 id="SubmissionNo">10.4 Rejection of a Submission Request, and Submission Appeals</h3>
+
<p>The Director <em class="rfc2119">may</em> reject a Submission request for a variety of reasons, including any of the following:</p>
<ul>
<li>The ideas expressed in the request overlap in scope with the work of a chartered Working Group, and acknowledgment might
@@ -2090,11 +2183,14 @@
Submitter(s). If requested by the Submitter(s), the Team <em class="rfc2119">must</em> provide rationale to the Submitter(s) about
the rejection. Other than to the Submitter(s), the Team <em class="rfc2119">must not</em> make statements about why a Submission
request was rejected.</p>
- <p>The Advisory Committee representative(s) of the Submitters(s) <em class="rfc2119">may</em> appeal the rejection to the <a href="#TAG">TAG</a>
- if the reasons are related to Web architecture, or to the <a href="#AB">Advisory Board</a> if the request is rejected for other
- reasons. In this case the Team <em class="rfc2119">should</em> make available its rationale for the rejection to the appropriate
- body. The Team will establish a process for such appeals that ensures the appropriate <a href="#confidentiality-levels">level of
- confidentiality</a>.</p>
+
+ <p>The Advisory Committee representative(s) of the Submitters(s) <em class="rfc2119">may</em> initiate a
+ <a href="#SubmissionNo">Submission Appeal</a> of the Team's Decision to the <a href="#TAG">TAG</a> if the reasons are
+ related to Web architecture, or to the <a href="#AB">Advisory Board</a> if the request is rejected for other
+ reasons. In this case the Team <em class="rfc2119">should</em> make available its rationale for the rejection to the
+ appropriate body. The Team will establish a process for such appeals that ensures the appropriate
+ <a href="#confidentiality-levels">level of confidentiality</a>.</p>
+
<h2 id="GAProcess">11 Process Evolution</h2>
<p>The <span id="ProcessDoc">W3C Process Document</span> undergoes similar consensus-building processes as technical reports, with
the <a href="#AB">Advisory Board</a> acting as the sponsoring Working Group.</p>
@@ -2104,9 +2200,10 @@
<li>After comments have been <a href="#formal-address">formally addressed</a> and the document possibly modified, the Team seeks
endorsement from the Members by initiating an <a href="#ACReview">Advisory Committee review</a> of a Proposed Process Document.
The review period <em class="rfc2119">must</em> last at least <span class="time-interval">four weeks</span>.</li>
- <li><a href="#ACReviewAfter">After the Advisory Committee review</a>, if there is consensus, the Team enacts the new process
- officially by announcing the <a href="#def-w3c-decision">W3C decision</a> to the Advisory Committee. If there was <a href="#def-Dissent">dissent</a>,
- Advisory Committee representatives <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a> the decision.</li>
+ <li><a href="#ACReviewAfter">After the Advisory Committee review</a>, if there is consensus, the Team enacts the new
+ process officially by announcing the <a href="#def-w3c-decision">W3C decision</a> to the Advisory Committee.
+ Advisory Committee representatives <em class="rfc2119">may</em> initiate an
+ <a href="#ACAppeal">Advisory Committee Appeal</a> to the W3C.</li>
</ol>
<p>W3C <em class="rfc2119">may</em> also modify a Process Document by following the processes for <a href="#rec-modify">modifying a
Recommendation</a>.</p>
@@ -2247,6 +2344,13 @@
<a href="#CharterReview">5.2.3</a>, <a href="#cfp">5.2.4</a>, <a href="#WGCharter">5.2.6</a>,
<a href="#transition-reqs">6.2.2</a>.</li>
<li>Changed the voting for AB and TAG elections to Single Transferable Vote - <a href="AB-TAG-Elections">2.5.2</a></li>
+ <li>Clarified the rights and obligations of Member Consortia and their representatives -
+ <a href="#MemberBenefits">2.1.1</a></li>
+ <li>Renumber - 5.2.8 becomes 5.2.7 (there was no section 5.2.7)</li>
+ <li>Simplify Appeals, so they can occur whether there was dissent or not, and in a broader range of cases -
+ especially <a href="#candidate-rec">6.4</a>, <a href="#rec-publication">6.6</a>, <a href="#rec-rescind">6.9</a>,
+ <a href="#ReviewAppeal">7</a>, <a href="#ACAppeal">7.2</a>, <a href="ACVotes">7.3</a>,
+ <a href="#Submission">10</a>, <a href="#SubmissionNo">10.4</a>, <a href="#GAProcess">11</a></li>
</ul>
</main>
</body>