index.bs

<!--
	This document is formatted using Bikeshed.
	Roughly speaking, it is a Markdown preprocessor,
	with additional functionality for cross-spec autolinking,
	automatic generation of indexes/ToC/etc,
	and many other features.
	See https://tabatkins.github.io/bikeshed/ for detailed documentation.

	When making edits, please respect the following coding style:
	- Tabs for indentation, spaces for alignment.
	- Semantic line breaks: at phrases boundaries, each line < ~80ch
	- Indent the entire spec one level except for headings.
	- Line break after opening heading tag, so heading text
	  is easy to pick out when scanning the source.
	- Empty lines between blocks.
	- Indent contents of block-level HTML elements
	  (except <p>, which we usually imply via Markdown formatting
	  and otherwise leave inlined at the start of the paragraph).
	  Definitely leave a break and indent
	  after any block start tag with attributes, though.
	- No optional end tags.
	- Use manual IDs so that IDs remain stable as you adjust the heading text;
	  add old IDs (via empty elements with IDs, or e.g. Bikeshed's oldids attribute)
	  when removing or changing IDs so that links to your spec don't break.
-->
<pre class='metadata'>
Title: W3C Process Document
Group: processcg
Status: CG-DRAFT
ED: https://www.w3.org/policies/process/drafts/
TR: https://www.w3.org/policies/process/
Previous Version: https://www.w3.org/policies/process/20250818/
Editor: Elika J. Etemad / fantasai, Apple, https://fantasai.inkedblade.net/contact
Editor: Florian Rivoal, Invited Expert, https://florian.rivoal.net/
Former Editor: Natasha Rooney, Invited Expert
Former Editor: Charles McCathie Nevile, Yandex, https://yandex.com
Former Editor: Ian Jacobs, W3C, https://www.w3.org/
Level: none
Repository: w3c/process
Shortname: process
Abstract:
	The <a href="https://www.w3.org/mission/">mission of the World Wide Web Consortium (W3C)</a>
	is making the web work, for everyone.
	W3C brings together global stakeholders to develop open standards that enable a World Wide Web that connects and empowers humanity.
	The W3C Process Document describes the organizational structure of W3C and processes,
	responsibilities and functions that enable W3C to accomplish its mission.
	This document does not describe the internal workings of the Team.

	For more information about the W3C mission and the history of W3C,
	please refer to <a href="https://www.w3.org/about/">About W3C</a>.
Status Text:
	This document,
	which is based on the <a href="https://www.w3.org/policies/process/20250818/">18 August 2025 Process</a>,
	is a work in progress
	and further changes may occur before completion of this revision cycle.
	As detailed in <a href="https://www.w3.org/policies/process/#GAProcess">Section 11 Process Changes</a>,
	once the W3C Advisory Board considers it ready for adoption,
	it will be offered for W3C Advisory Committee Review.
Issue Tracking: Github (preferred) https://github.com/w3c/process/issues/
Issue Tracking: Public mailing list https://lists.w3.org/Archives/Public/public-w3process/
Issue Tracking: Member-only mailing list https://lists.w3.org/Archives/Member/process-issues
Boilerplate: repository-issue-tracking off
Boilerplate: omit conformance
Complain About: accidental-2119 yes
</pre>

<style>
.about { margin-left: 3em; margin-right: 3em; font-size: .83em}
table { margin-left: auto; margin-right: auto }
.diagram { text-align: center; margin: 2.5em 0 }
.issue::before {content: "Issue: "}
.issue {border: 2px dashed red; background-color: #ffa;}
.issue .issue {background-color: #fcc;}
.rfc2119 {font-variant:small-caps}

/*for the SVG - navigation highlighting */

:focus path,
:focus polygon,
:focus rect,
:focus ellipse {
	stroke-width: 3px;
}
g g:hover path,
g g:hover polygon,
g g:hover rect,
g g:hover ellipse {
	stroke-width: 3px;
}
:focus text,
g g:hover text {
	stroke: black;
	stroke-width: .5px;
}

@media print {
	a[data-ref]::after { content: " [" attr(data-ref) "]"; }
}

.table-borders {
	border-collapse: collapse;
}
.table-borders td,
.table-borders th {
	border: 1px solid black;
	padding: 0.5ex;
}

</style>
<!--[if lt IE 9]><script src='undefined://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->

<h2 class="no-num no-toc no-ref" id="pp">
Relation of Process Document to Patent Policy and Other Policies</h2>

	<!-- DO NOT REMOVE THIS SECTION OR ITS REFERENCE TO THE PATENT POLICY WITHOUT DISCUSSING WITH PSIG / COUNSEL. -->

	W3C Members' attention is called to the fact
	that provisions of the Process Document are binding on Members
	per their <a href="https://www.w3.org/membership/agreement/">Membership Agreement</a> [[MEMBER-AGREEMENT]].
	The <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> [[!PATENT-POLICY]]
	and other policies
	incorporated by normative reference as a part of the Process Document
	are equally binding.

	The Patent Policy and Code of Conduct place additional obligations on Members, Team, and other participants in W3C.
	The Process Document does not restate those requirements but includes references to them.
	The Process Document, Patent Policy, and Code of Conduct have been designed to allow each to evolve independently.

	In the Process Document, the term “participant” refers to an individual, not an organization.

<h2 class="no-num no-toc no-ref" id=terms>
Conformance and specialized terms</h2>

	The terms
	<em class="rfc2119">must</em>,
	<em class="rfc2119">must not</em>,
	<em class="rfc2119">should</em>,
	<em class="rfc2119">should not</em>,
	<em class="rfc2119">required</em>,
	and <em class="rfc2119">may</em>
	are used in accordance with <a href="https://www.ietf.org/rfc/rfc2119.txt">RFC 2119</a>.
	The term <dfn id="not-required" noexport><em class="rfc2119">not required</em></dfn>
	is equivalent to the term <em class="rfc2119">may</em>
	as defined in RFC2119
	[[!RFC2119]].

	Some terms have been capitalized in this document (and in other W3C materials)
	to indicate that they are entities with special relevance to the W3C Process.
	These terms are defined within this document,
	and readers are reminded that the ordinary English definitions are insufficient
	for the purpose of understanding this document.

<nav data-fill-with="table-of-contents"></nav>
<main>

<h2 id="Intro">
Introduction</h2>

	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.

	The W3C Process promotes the goals of quality and fairness in technical decisions
	by encouraging <a href="#Consensus">consensus</a>,
	soliciting reviews (by both Members and public),
	incorporating implementation and interoperability experience,
	and requiring Membership-wide approval as part of the <a href="#Reports">technical report development process</a>.
	[[#group-participation|Participants]] in W3C include
	<a href="#member-rep">representatives of its Members</a> and the [=Team=],
	as well as <a href="#invited-expert-wg">Invited Experts</a>
	who can bring additional expertise or represent additional stakeholders.
	[=Team=] representatives both contribute to the technical work
	and help ensure each group's proper integration with the rest of W3C.

	W3C’s technical standards, called [=W3C Recommendations=],
	are developed by its [=Working Groups=];
	W3C also has other types of publications,
	all described in [[#Reports]].
	W3C has various types of groups;
	this document describes the formation and policies
	of its chartered [=Working Groups=] and [=Interest Groups=],
	see [[#Policies]] and [[#GAGeneral]].
	W3C also operates Community and Business Groups,
	which are separately described in <a href="https://www.w3.org/community/about/process/">their own process document</a> [[BG-CG]].

	In addition, several groups are formally established by the Consortium:
	the <a href="#AC">W3C Advisory Committee</a>, which has a representative from each Member,
	and two oversight groups elected by its membership:
	the <a href="#AB">Advisory Board (AB)</a>,
	which helps resolve Consortium-wide non-technical issues and manages the <a href="#GAProcess">evolution of the W3C process</a>;
	and the <a href="#TAG">Technical Architecture Group (TAG)</a>,
	which helps resolve Consortium-wide technical issues.

	Here is a general overview of how W3C initiates standardization of a Web technology:

	<ol>
		<li>
			People generate interest in a particular topic.
			For instance, Members express interest by developing proposals in Community Groups
			or proposing ideas in <a href="#Submission">Member Submissions</a>.
			Also, the <a href="#Team">Team</a> monitors work inside and outside of W3C for signs of interest,
			and helps organize <a href="#GAEvents">Workshops</a> to bring people together
			to discuss topics that interest the W3C community.

		<li>
			When there is enough interest and an engaged community,
			the [=Team=] works with the Membership
			to draft proposed <a href="#WGCharterDevelopment">Interest Group or Working Group charters</a>.
			W3C Members <a href="#CharterReview">review</a> the proposed charters,
			and when there is support within W3C for investing resources in the topic of interest,
			W3C approves the group(s),
			and they begin their work.
	</ol>

	Further sections of this Process Document deal with topics including
	liaisons ([[#Liaisons]]),
	confidentiality ([[#dissemination]]),
	and formal decisions and appeals ([[#decisions]]).


<h2 id="Organization">
Members and the Team</h2>

	W3C's mission is to make the web work — for everyone,
	by bringing together global stakeholders to develop open standards
	that enable a World Wide Web that connects and empowers humanity.
	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.

<h3 id="Members">
Members</h3>

	<dfn lt="W3C Member|Member">W3C Members</dfn> are
	organizations subscribed according to a <a href="https://www.w3.org/membership/agreement/">Membership Agreement</a> [[MEMBER-AGREEMENT]].
	They are represented in W3C processes as follows:

	<ol>
		<li>
			One representative per Member organization participates
			in the [=Advisory Committee=]
			which oversees the work of W3C.

		<li>
			Representatives of Member organizations participate
			in <a href="#GAGeneral">Working Groups and Interest Groups</a>,
			where they author and review <a href="#Reports">technical reports</a>.
	</ol>

	<p id="MemberSubscription">W3C membership is open to all entities,
	as described in “<a href="https://www.w3.org/membership/join/">How to Join W3C</a>” [[JOIN]];
	(refer to the public list of <a href="https://www.w3.org/membership/list/">current W3C Members</a> [[MEMBER-LIST]]).
	The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure
	that Member participation agreements remain <a href="#Team-only">Team-only</a>
	and that no Member receives preferential treatment within W3C.

	<p id="IndividualParticipation">While W3C does not have a class of membership tailored to individuals,
	individuals <em class="rfc2119">may</em> join W3C.
	Restrictions pertaining to <a href="#MemberRelated">related Members</a> apply
	when the individual also <a href="#member-rep">represents</a> another W3C Member.

<h4 id="MemberBenefits">
Rights of Members</h4>

	Each Member organization enjoys the following rights and benefits:

	<ul>
		<li>
			A seat on the <a href="#AC">Advisory Committee</a>;

		<li>
			Access to <a href="#Member-only">Member-only</a> information;

		<li>
			The <a href="#Submission">Member Submission</a> process;

		<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> [[INTRO]].
	</ul>

	Furthermore, subject to further restrictions included in their Member Agreement,
	representatives of Member organizations participate in W3C as follows:

	<ul>
		<li>
			In <a href="#GAGeneral">Working Groups and Interest Groups</a>.

		<li>
			In [=Workshops=].

			A <dfn id=EventsW>Workshop</dfn> is an event whose goal is usually
			either to convene experts and other interested parties
			for an exchange of ideas about a technology or policy,
			or to address the pressing concerns of W3C Members.
			(See <a href="https://www.w3.org/guide/meetings/workshops">Workshops</a> in [[GUIDE]])

		<li>
			On the Team, as <a href="#fellows">W3C Fellows</a>.
	</ul>

	The rights and benefits of W3C membership [[MEMBER-AGREEMENT]]
	are contingent upon conformance to the processes described in this document.
	Disciplinary action for anyone participating in W3C activities is described in [[#discipline]].

	Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member website</a> [[MEMBER-HP]].

<h4 id="RelatedAndAssociatedMembers" oldids="RelatedAndConsortiumMembers">
Member Associations and Related Members</h4>

<h5 id="MemberAssoc" oldids="MemberConsortia">
Membership Associations</h5>

	A “<dfn lt="Member Association | Member Associations">Member Association</dfn>” means a consortium,
	user society,
	or association of two or more individuals,
	companies,
	organizations or governments,
	or any combination of these entities
	which has the purpose of participating in a common activity
	or pooling resources to achieve a common goal other than participation in,
	or achieving certain goals in,
	W3C.
	A joint-stock corporation or similar entity is not a [=Member Association=]
	merely because it has shareholders or stockholders.
	If it is not clear whether a prospective Member qualifies as a [=Member Association=],
	the [=CEO=] may reasonably make the determination.
	For a [=Member Association=], the rights and privileges of W3C Membership
	described in the W3C Process Document extend to the [=Member Association=]'s paid staff
	and Advisory Committee representative.

	[=Member Associations=] <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>.

	For [=Member Associations=] that have individual people 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.

	For Member Associations that have organizations as Members,
	all such designated representatives <em class="rfc2119">must</em> be an official representative of the Member organization
	(e.g. 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.

	For all representatives of a Member Association,
	IPR commitments are made on behalf of the Member Association,
	unless a further IPR commitment is made by the individuals' employers.

<h5 id="MemberRelated">
Related Members</h5>

	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 <dfn export lt="Related Member">related</dfn> if:

	<ol>
		<li>
			Either Member is a [=subsidiary=] of the other, or

		<li>
			Both Members are [=subsidiaries=] of a common entity, or

		<li>
			The Members have an employment contract or consulting contract that affects W3C participation.
	</ol>

	A <dfn>subsidiary</dfn> is an organization of which effective control and/or majority ownership rests with another,
	single organization.

	[=Related Members=] <em class="rfc2119">must</em> disclose these relationships
	according to the mechanisms described in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [[INTRO]].

<h4 id=standing>
Good Standing</h4>

	[=Members=] who have not lost Good Standing as defined in the [[BYLAWS inline]]
	are considered, for the purposes of this Process,
	to be in <dfn>Good Standing</dfn>.
	A group of [=related Members=] is in Good Standing if
	at least one of them is in Good Standing.

<h3 id="Team" oldids="def-Director">
The W3C Team</h3>

	The <dfn export lt="Team | W3C Team">Team</dfn> consists of
	<dfn>CEO</dfn>,
	W3C paid staff,
	unpaid interns,
	and W3C Fellows.
	<dfn id="fellows">W3C Fellows</dfn> are Member employees working as part of the Team;
	see the <a href="https://www.w3.org/careers/fellows/">W3C Fellows Program</a> [[FELLOWS]].
	The Team provides technical leadership about Web technologies,
	organizes and manages W3C activities to reach goals
	within practical constraints (such as resources available),
	and communicates with the Members and the public
	about the Web and W3C technologies.

	The CEO <em class="rfc2119">may</em> delegate responsibility
	(generally to other individuals in the Team)
	for any of their roles described in this document.
	[=Team Decisions=] derive from the [=CEO=]'s authority,
	even when they are carried out by other members of the [=Team=].

	Oversight over the [=Team=],
	budgeting,
	and other business decisions,
	is provided by the <dfn export lt="BoD | Board | Board of Directors | W3C Board of Directors">W3C Board of Directors</dfn>,
	rather than managed directly by the Process.

	Note: See the [[BYLAWS inline|W3C Bylaws]] for more details
	on the [=Board=] and overall governance of W3C.

<h2 id=groups>
Groups and Participation</h2>

	For the purposes of this Process, a <dfn lt="W3C Group" local-lt="group">W3C Group</dfn> is one of W3C’s
	<a href="#wgparticipant">Working Groups</a>,
	<a href="#igparticipant">Interest Groups</a>,
	<a href="#AC">Advisory Committee</a>,
	<a href="#ABParticipation">Advisory Board</a>,
	or <a href="#tag-participation">TAG</a>,
	and a <dfn>participant</dfn> is a member of such a group.

<h3 id="Policies">
Policies for Participation in W3C Groups</h3>

<h4 id="ParticipationCriteria">
Individual Participation Criteria</h4>

<h5 id="discipline">
Expectations and Discipline</h5>

	There are three qualities an individual is expected to demonstrate in order to participate in W3C:

	<ol>
		<li>
			Technical competence in one's role;

		<li>
			The ability to act fairly;

		<li>
			Social competence in one's role.
	</ol>

	[=Advisory Committee representatives=] who nominate individuals from their organization for participation in W3C activities
	are responsible for assessing and attesting to the qualities of those nominees.

	<p>Participants in any W3C activity <em class="rfc2119">must</em> abide
	by the terms and spirit of the <a href="https://www.w3.org/policies/code-of-conduct/">W3C Code of Conduct</a> [[!COC]]
	and the participation requirements described in
	“Disclosure”
	in the W3C Patent Policy [[!PATENT-POLICY]].

	The [=CEO=] <em class="rfc2119">may</em> take disciplinary action,
	including suspending or removing for cause
	a participant in any group (including the [=AB=] and [=TAG=])
	if serious and/or repeated violations occur,
	such as failure to meet the requirements on individual behavior of
	(a) this process
	and in particular the Code of Conduct,
	(b) their membership agreement, or
	(c) applicable laws.
	Refer to the <a href="https://www.w3.org/guide/process/suspension">Guidelines to suspend or remove participants from groups</a>.

<h5 id="coi">
Conflict of Interest Policy</h5>

	Individuals participating materially in W3C work <em class="rfc2119">must</em> disclose significant relationships
	when those relationships might reasonably be perceived as creating a conflict of interest with the individual's role at W3C.
	These disclosures <em class="rfc2119">must</em> be kept up-to-date
	as the individual's affiliations change and W3C membership evolves
	(since, for example, the individual might have a relationship with an organization that joins or leaves W3C).
	Each section in this document that describes a W3C group
	provides more detail about the disclosure mechanisms for that group.

	The ability of an individual to fulfill a role within a group
	without risking a conflict of interest depends on the individual's affiliations.
	When these affiliations change,
	the individual's assignment to the role <em class="rfc2119">must</em> be evaluated.
	The role <em class="rfc2119">may</em> be reassigned according to the appropriate process.
	For instance,
	the [=Team=] <em class="rfc2119">may</em> appoint a new group [=Chair=]
	when the current Chair changes affiliations
	(e.g., if there is a risk of conflict of interest,
	or if there is risk that the Chair's new employer will be over-represented within a W3C activity).

	The following are some scenarios where disclosure is appropriate:

	<ul>
		<li>
			Paid consulting for an organization whose activity is relevant to W3C,
			or any consulting compensated with equity
			(shares of stock, stock options, or other forms of corporate equity).

		<li>
			A decision-making role/responsibility
			(such as participating on a Board)
			in other organizations relevant to W3C.

		<li>
			A position on a publicly visible advisory body,
			even if no decision-making authority is involved.
	</ul>

	Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the [=Team=].

	[=Team=] members are subject to the <a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/">Conflict of Interest Policy for the W3C Team</a> [[!CONFLICT-POLICY]].

<h5 id="member-rep">
Individuals Representing a Member Organization</h5>

	Generally, individuals representing a Member in an official capacity within W3C
	are employees of the Member organization.
	However, an [=Advisory Committee representative=] <em class="rfc2119">may</em> designate a non-employee
	to represent the Member.
	Non-employee Member representatives <em class="rfc2119">must</em> disclose
	relevant affiliations to the Team and to any group in which the individual participates.

	In exceptional circumstances
	(e.g., situations that might jeopardize the progress of a group or create a <a href="#coi">conflict of interest</a>),
	the [=CEO=] <em class="rfc2119">may</em> decline
	to allow an individual designated by an Advisory Committee representative to participate in a group.

	A group charter <em class="rfc2119">may</em> limit
	the number of individuals representing a W3C Member
	(or group of <a href="#MemberRelated">related Members</a>).

<h4 id="GeneralMeetings" oldids="GAEvents, EventsS">
Meetings</h4>

	The requirements in this section apply to the official meetings of any [=W3C group=],
	as well as to official W3C meetings with open-ended participation from the Membership and/or the public,
	such as [=Workshops=].

	<p>W3C distinguishes two types of meetings:</p>

	<ol>
		<li>
			A <dfn id="ftf-meeting">face-to-face meeting</dfn> is one
			where most of the attendees are expected to participate in the same physical location.

		<li>
			A <dfn id="distributed-meeting">distributed meeting</dfn> is one
			where most of the attendees are expected to participate from remote locations
			(e.g., by telephone, video conferencing, or <abbr title="Internet Relay Chat">IRC</abbr>).
	</ol>

	A [=Chair=] <em class="rfc2119">may</em> invite an individual with a particular expertise
	to attend a meeting on an exceptional basis.
	This person is a meeting guest,
	not a group [=participant=].
	Meeting guests do not have <a href="#Votes">voting rights</a>.
	It is the responsibility of the Chair to ensure
	that all meeting guests respect the chartered <a href="#confidentiality-levels">level of confidentiality</a>
	and other group requirements.

<h5 id="meeting-schedules">
Meeting Scheduling and Announcements</h5>

	Meeting announcements <em class="rfc2119">should</em> be sent to all appropriate group mailing lists,
	i.e. those most relevant to the anticipated meeting participants.

	The following table lists <em class="rfc2119">recommendations</em> for organizing a meeting:

	<table class="data">
	<thead>
		<tr>
			<td>
			<th scope=col>Face-to-face meetings
			<th scope=col>Distributed meetings

	<tbody>
		<tr>
			<th scope=row>Meeting announcement (before)
			<td><span class="time-interval">eight weeks<sup>*</sup></span>
			<td><span class="time-interval">one week<sup>*</sup></span>
		<tr>
			<th scope=row>Agenda available (before)
			<td><span class="time-interval">two weeks</span>
			<td><span class="time-interval">24 hours</span> (or longer if a meeting is scheduled after a weekend or holiday)
		<tr>
			<th scope=row>Participation confirmed (before)
			<td><span class="time-interval">three days</span>
			<td><span class="time-interval">24 hours</span>
		<tr>
			<th scope=row>Action items available (after)
			<td><span class="time-interval">three days</span>
			<td><span class="time-interval">24 hours</span>
		<tr>
			<th scope=row>[=Minutes=] available (after)
			<td><span class="time-interval">two weeks</span>
			<td><span class="time-interval">48 hours</span>
	</table>

	<sup>*</sup> To allow proper planning (e.g., travel arrangements),
	the Chair is responsible for giving sufficient advance notice
	about the date and location of a meeting.
	Shorter notice for a meeting is allowed
	provided that there are no objections from group participants.
	In the case of [=Workshops=],
	shorter notice is not allowed.

<h5 id="meeting-minutes">
Meeting Minutes</h5>

	Groups <em class=rfc2119>should</em> take and retain <dfn>minutes</dfn> of their meetings,
	and <em class="rfc2119">must</em> record
	any official [=group decisions=] made during the meeting discussions.
	Details of the discussion leading to such decisions are not required,
	provided that the rationale for the [=group decision=] is nonetheless clear.

<h5 id="meeting-recording">
Meeting Recordings and Transcripts</h5>

	No-one may take an audio or video recording of a meeting,
	or retain an automated transcript,
	unless the intent is announced at the start of the meeting,
	and no-one participating in the recorded portion of the meeting withholds consent.
	If consent is withheld by anyone, recording/retention <em class=rfc2119>must</em> not occur.
	The announcement <em class=rfc2119>must</em> cover:
	(a) who will have access to the recording or transcript and
	(b) the purpose/use of it and
	(c) how it will be retained (e.g. privately, in a cloud service) and for how long.

<h4 id="tooling">
Tooling and Archiving for Discussions and Publications</h4>

	For [=W3C Groups=] operating under this Process,
	a core operating principle is to allow access across disabilities,
	across country borders,
	and across time.
	Thus in order to allow all would-be participants to effectively participate,
	to allow future participants and observers to understand the rationale and origins of current decisions,
	and to guarantee long-lived access to its publications,
	W3C requires that:

	<ul>
		<li id=report-stability>
			All reports, publications, or other deliverables
			produced by the group for public consumption
			(i.e. intended for use or reference outside its own membership)
			<em class=rfc2119>should</em> be published and promoted at a W3C-controlled URL,
			and backed up by W3C systems
			such that if the underlying service is discontinued,
			W3C can continue to serve such content without breaking incoming links
			or other key functionality.

		<li id=report-accessibility>
			All reports, publications, or other deliverables
			produced by the group for public consumption
			<em class=rfc2119>should</em> follow best practices for internationalization
			and for accessibility to people with disabilities.
			Network access to W3C-controlled domains may be assumed.

		<li id=discussion-archiving>
			Official meeting minutes and other records of decisions made <em class=rfc2119>must</em>
			be archived by W3C for future reference;
			and other persistent text-based discussions
			sponsored by the group,
			pertaining to their work
			and intended to be referenceable by all group members
			<em class=rfc2119>should</em> be.
			This includes discussions conducted over email lists
			or in issue-tracking services
			or any equivalent fora.
			Materials referenced from discussions
			and necessary to understand them
			should be available at a stable URL,
			at a level of confidentiality no stricter than the discussion minutes.

			Note: The lack, or loss, of such archives does not by itself
			invalidate an otherwise-valid decision.

		<li id=tool-accessibility>
			Any tooling used by the group
			for producing its documentation and deliverables
			or for official group discussions
			<em class=rfc2119>should</em> be usable
			(without additional cost)
			by all who wish to participate,
			including people with disabilities,
			to allow their effective participation.

			Note: If a new participant joins who cannot use the tool,
			this can require the [=Working Group=] to change its tooling
			or operate some workaround.

		<li id=where-is-your-stuff>
			All tools and archives used by the group
			for its discussions and recordkeeping
			<em class=rfc2119>should</em> be documented
			such that new participants and observers
			can easily find the group’s tools and records.

	</ul>

	The [=Team=] is responsible for ensuring adherence to these rules
	and for bringing any group not in compliance into compliance.

<h4 id="resignation">
Resignation from a Group</h4>

	A W3C Member or Invited Expert <em class="rfc2119">may</em> resign from a group.
	On written notification from an Advisory Committee representative
	or Invited Expert
	to the [=Team=],
	the Member and their representatives
	or the Invited Expert
	will be deemed to have resigned from the relevant group.
	The [=Team=] <em class="rfc2119">must</em> record the notification.
	See “Exclusion and Resignation from the Working Group” in the W3C Patent Policy [[PATENT-POLICY]]
	for information about obligations remaining after resignation from certain groups.

<h3 id="AC">
The Advisory Committee (AC)</h3>

<h4 id=ac-role>
Role of the Advisory Committee</h4>

	<p id=ReviewAppeal>
	The <dfn export lt="Advisory Committee|AC">Advisory Committee</dfn> represents
	the [=Members=] of W3C at large.
	It is responsible for:

	<ul>
		<li>
			reviewing plans for W3C at each <a href="#ACMeetings">Advisory Committee meeting</a>.

		<li>
			<a href="#ACReview">reviewing formal proposals</a> of W3C:
			<a href="#CharterReview">Charter Proposals</a>,
			<a href="#transition-rec">transitions to Recommendation</a>,
			and <a href="#GAProcess">proposed Process Documents</a>.

		<li>
			electing the <a href="#AB">Advisory Board</a> participants other than the Advisory Board Chair.

		<li>
			electing a majority (6) of the participants on the <a href="#TAG">Technical Architecture Group</a>.
	</ul>

	[=Advisory Committee representatives=] <em class="rfc2119">may</em> initiate
	an <a href="#ACAppeal">Advisory Committee Appeal</a>
	of a [=W3C decision=]
	or [=Team=]'s decision.

	See also the additional roles of [=Advisory Committee representatives=]
	described in the W3C Patent Policy [[PATENT-POLICY]].

<h4 id=ac-participation>
Participation in the Advisory Committee</h4>

	The [=Advisory Committee=]
	is composed of one <dfn export lt="Advisory Committee representative| AC representative">representative</dfn>
	from each Member organization
	(refer to the [=Member-only=] list
	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. [[CURRENT-AC]])

	As defined in the W3C Bylaws,
	each “<i>Consortium Member</i>”
	has one “<i>Consortium Member Representative</i>” [[!BYLAWS]].
	For purposes of the W3C Process,
	this person also serves as the organization's [=Advisory Committee Representative=].
	When a [=Member=] does not qualify as a “<i>Consortium Member</i>”,
	it <em class=rfc2119>must</em> name its [=Advisory Committee representative=]
	upon joining W3C.
	The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [[INTRO]]
	explains how to subscribe or unsubscribe to Advisory Committee mailing lists,
	provides information about <a href="#ACMeetings">Advisory Committee Meetings</a>,
	explains how to name a new representative,
	and more.
	[=Advisory Committee representatives=] <em class="rfc2119">must</em> follow the <a href="#coi">conflict of interest policy</a>
	by disclosing information according to the mechanisms described in the New Member Orientation.

	The AC representative may share their rights and responsibilities under this Process
	with an <dfn export lt="alternate AC representative | alternate Advisory Committee representative | alt AC rep">alternate</dfn>,
	except the ability to designate an alternate.

	Note: The above does not establish an ability to delegate rights and responsibilities
	pertaining to the role of “<i>Consortium Member Representative</i>”
	as defined by the W3C Bylaws.
	Such rights and responsibilities are out of scope for the Process.

<h4 id="ACCommunication">
Advisory Committee Mailing Lists</h4>

	The [=Team=] <em class="rfc2119">must</em> provide two mailing lists for use by the [=Advisory Committee=]:

	<ol>
		<li>
			One for official announcements (e.g., those required by this document) from the [=Team=] to the [=Advisory Committee=].
			This list is read-only for Advisory Committee representatives.

		<li>
			One for discussion among [=Advisory Committee representatives=].
			Though this list is primarily for Advisory Committee representatives,
			the [=Team=] <em class="rfc2119">must</em> monitor discussion
			and <em class="rfc2119">should</em> participate in discussion when appropriate.
			Ongoing detailed discussions <em class="rfc2119">should</em> be moved to other appropriate lists
			(new or existing, such as a mailing list created for a <a href="#GAEvents">Workshop</a>).
	</ol>

	An [=Advisory Committee representative=] <em class="rfc2119">may</em> request
	that additional individuals from their organization be subscribed to these lists.
	Failure to contain distribution internally
	<em class="rfc2119">may</em> result in suspension of additional email addresses,
	at the discretion of the Team.

<h4 id="ACMeetings">
Advisory Committee Meetings</h4>

	The [=Team=] organizes a <a href="#ftf-meeting">face-to-face meeting</a> for the [=Advisory Committee=]
	<span class="time-interval">twice a year</span>.
	The [=Team=] appoints the Chair of these meetings (generally the CEO).
	At each Advisory Committee meeting,
	the Team <em class="rfc2119">should</em> provide an update to the Advisory Committee about:

	<dl>
		<dt><em>Resources</em>
		<dd>
			<ul>
				<li>
					The number of W3C Members at each level.

				<li>
					An overview of the financial status of W3C.
			</ul>

		<dt><em>Allocations</em>
		<dd>
			<ul>
				<li>
					The allocation of the annual budget, including size of the Team and their approximate deployment.

				<li>
					A list of all activities (including but not limited to Working and Interest Groups)
					and brief status statement about each,
					in particular those started or terminated since the previous Advisory Committee meeting.

				<li>
					The allocation of resources to pursuing <a href="#Liaisons">liaisons</a> with other organizations.
			</ul>
		</dd>
	</dl>

	Each Member organization <em class="rfc2119">should</em> send one <a href="#member-rep">representative</a>
	to each Advisory Committee Meeting.
	In exceptional circumstances
	(e.g., during a period of transition between representatives from an organization),
	the meeting Chair <em class="rfc2119">may</em> allow a Member organization to send two representatives to a meeting.

	The [=Team=] <em class="rfc2119">must</em> announce the date and location of each Advisory Committee meeting
	no later than at the end of the previous meeting;
	<span class="time-interval">one year's</span> notice is preferred.
	The Team <em class="rfc2119">must</em> announce the region of each Advisory Committee meeting
	at least <span class="time-interval">one year</span> in advance.

	More information about <a href="https://www.w3.org/events/ac/">Advisory Committee meetings</a> [[AC-MEETING]]
	is available at the Member website.

<h3 id=elected-groups>
Elected Groups: The AB and the TAG</h3>

	The W3C Process defines two types of <dfn id=elected-group export>elected groups</dfn>:
	the [=Advisory Board=] (AB) and
	the [=Technical Architecture Group=] (TAG),
	both elected by the [=Advisory Committee=].

<h4 id="AB">
Advisory Board (AB)</h4>

<h5 id=ab-role>
Role of the Advisory Board</h5>

	The <dfn export lt="Advisory Board|AB">Advisory Board</dfn>
	is elected by the Membership to advance the effectiveness of W3C as a
	standards development organization (<abbr title="standards development organization">SDO</abbr>).
	The [=Advisory Board=]:

	<ul>
	<li>Provides ongoing guidance to the Team
	on issues of strategy, 
	management, 
	legal matters, 
	process, 
	community engagement, 
	and conflict resolution,
	that arise during the the work of the W3C community;
	<li>Serves the Members by
	tracking issues raised between Advisory Committee meetings,
	soliciting Member comments on such issues,
	and proposing actions to resolve these issues;
	<li>Is responsible for the development of the <a href="#GAProcess">Process Document</a>,
	including considering proposals,
	identifying changes and areas for improvement,
	and publishing new versions.
	</ul>

	Members of the [=AB=] also take part in [=W3C Councils=]
	to hear and adjudicate [=Formal Objections=]
	and [=Submission Appeals=].
	
	Details about the Advisory Board
	(e.g., the list of Advisory Board participants,
	mailing list information, and summaries of Advisory Board meetings)
	are available at the <a href="https://www.w3.org/2002/ab/">Advisory Board home page</a> [[AB-HP]].

<h5 id="ABParticipation">
Composition of the Advisory Board</h5>

	The [=Advisory Board=] consists of nine to eleven elected participants and one Chair
	(who <em class=rfc2119>may</em> be one of the elected participants).
	With the input of the [=AB=],
	the [=Team=] appoints the Chair,
	who <em class=rfc2119>should</em> choose a co-chair among the elected participants.
	Upon appointment,
	the Chair(s) are subject to ratification by secret ballot,
	requiring approval by two thirds of the elected participants.
	Chair selection <em class=rfc2119>must</em> be run
	at least at the start of each regular term,
	as well as when a majority of the participants request it;
	and <em class=rfc2119>may</em> be run at other times when initiated by the current chairs or the Team,
	for example if a chair steps down or if a minority of the participants make such a request.

	The team also appoints a [=Staff Contact=],
	as described in <a href="#ReqsAllGroups"></a>.
	The CEO and Staff Contact have a standing invitation
	to all regular Advisory Board sessions.

	The nine to eleven [=Advisory Board=] participants are elected by the W3C [=Advisory Committee=]
	following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.

	The terms of elected Advisory Board participants are for <span class="time-interval">two years</span>.
	Terms are staggered so that each year,
	either five or six terms expire.
	If an individual is elected to fill an incomplete term,
	that individual's term ends at the normal expiration date of that term.
	Regular Advisory Board terms begin on 1 July and end on 30 June.

<h5 id=ab-comm>
Communications of the Advisory Board</h5>

	The [=Team=] <em class="rfc2119">must</em> make available a mailing list,
	confidential to the Advisory Board and Team,
	for the Advisory Board to use for its communication.

	The [=Advisory Board=] <em class="rfc2119">should</em> send a summary of each of its meetings
	to the Advisory Committee and other group Chairs.
	The Advisory Board <em class="rfc2119">should</em> also report on its activities
	at each <a href="#ACMeetings">Advisory Committee meeting</a>.

<h5 id=ab-bod-liaison>
Liaisons between the Advisory Board and the Board of Directors</h5>

	To ensure good communication between the [=AB=] and the [=Board of Directors=]
	and facilitate operational and management consistency,
	the [=AB=] <em class=rfc2119>may</em> appoint up to two of its participants as liaisons to the [=Board=].
	Such appointees are expected to attend and participate in [=Board=] meetings
	and access [=Board=] materials
	as Non-voting Observers. [[BYLAWS]]
	They do not form part of the [=Board=]'s decision-making body,
	and may be excluded from such participation
	in accordance with applicable Board procedures.

	The [=Advisory Board=] <em class=rfc2119>should</em> reevaluate
	who is assigned to this role
	at least at the beginning of each term,
	and <em class=rfc2119>may</em> swap its appointees more frequently
	as they deem appropriate.

<h4 id="TAG">
Technical Architecture Group (TAG)</h4>

<h5 id=tag-role>
Role of the Technical Architecture Group</h5>

	The mission of the <dfn export lt="Technical Architecture Group|TAG">TAG</dfn> is stewardship of the Web architecture.
	There are three aspects to this mission:

	<ol>
		<li>
			to document and build consensus around principles of Web architecture
			and to interpret and clarify these principles when necessary;

		<li>
			to resolve issues involving general Web architecture brought to the TAG;

		<li>