From 9c865a034535ea2ace2532073b0c6c421b38ec4b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 6 Jun 2023 14:19:40 +0900
Subject: [PATCH 001/237] Snapshot the 2023-6-12 version

---
 snapshots/2023-06-12.html | 7091 +++++++++++++++++++++++++++++++++++++
 1 file changed, 7091 insertions(+)
 create mode 100644 snapshots/2023-06-12.html

diff --git a/snapshots/2023-06-12.html b/snapshots/2023-06-12.html
new file mode 100644
index 00000000..a31ff787
--- /dev/null
+++ b/snapshots/2023-06-12.html
@@ -0,0 +1,7091 @@
+<!doctype html><html lang="en">
+ <head>
+  <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+  <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
+  <title>W3C Process Document</title>
+  <link href="https://www.w3.org/StyleSheets/TR/2021/base" rel="stylesheet">
+  <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
+  <meta content="W3C Process, Team, Recommendation, Advisory Committee, Advisory Board, TAG, Working Group, Interest Group, Workshop, charter, Working Draft, Process Document, Candidate Recommendation, Director, Proposed Recommendation, Submission request" name="keywords">
+  <meta content="  	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 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=&quot;https://www.w3.org/Consortium/&quot;>About W3C</a>." name="abstract">
+  <meta content="Bikeshed version 2e3c4c68b, updated Fri Jan 14 14:49:00 2022 -0800" name="generator">
+  <link href="https://www.w3.org/Consortium/Process/" rel="canonical">
+  <meta content="3c7788f8420ffe30d4582e75dc9d3d28f7e02adc" name="document-revision">
+<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 ellipse {
+	stroke-width: 4px;
+}
+g g:hover path,
+g g:hover polygon,
+g g:hover ellipse {
+	stroke-width: 4px;
+}
+: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>
+<style>/* style-autolinks */
+
+.css.css, .property.property, .descriptor.descriptor {
+    color: var(--a-normal-text);
+    font-size: inherit;
+    font-family: inherit;
+}
+.css::before, .property::before, .descriptor::before {
+    content: "‘";
+}
+.css::after, .property::after, .descriptor::after {
+    content: "’";
+}
+.property, .descriptor {
+    /* Don't wrap property and descriptor names */
+    white-space: nowrap;
+}
+.type { /* CSS value <type> */
+    font-style: italic;
+}
+pre .property::before, pre .property::after {
+    content: "";
+}
+[data-link-type="property"]::before,
+[data-link-type="propdesc"]::before,
+[data-link-type="descriptor"]::before,
+[data-link-type="value"]::before,
+[data-link-type="function"]::before,
+[data-link-type="at-rule"]::before,
+[data-link-type="selector"]::before,
+[data-link-type="maybe"]::before {
+    content: "‘";
+}
+[data-link-type="property"]::after,
+[data-link-type="propdesc"]::after,
+[data-link-type="descriptor"]::after,
+[data-link-type="value"]::after,
+[data-link-type="function"]::after,
+[data-link-type="at-rule"]::after,
+[data-link-type="selector"]::after,
+[data-link-type="maybe"]::after {
+    content: "’";
+}
+
+[data-link-type].production::before,
+[data-link-type].production::after,
+.prod [data-link-type]::before,
+.prod [data-link-type]::after {
+    content: "";
+}
+
+[data-link-type=element],
+[data-link-type=element-attr] {
+    font-family: Menlo, Consolas, "DejaVu Sans Mono", monospace;
+    font-size: .9em;
+}
+[data-link-type=element]::before { content: "<" }
+[data-link-type=element]::after  { content: ">" }
+
+[data-link-type=biblio] {
+    white-space: pre;
+}</style>
+<style>/* style-colors */
+
+<style>/* style-counters */
+
+body {
+    counter-reset: example figure issue;
+}
+.issue {
+    counter-increment: issue;
+}
+.issue:not(.no-marker)::before {
+    content: "Issue " counter(issue);
+}
+
+.example {
+    counter-increment: example;
+}
+.example:not(.no-marker)::before {
+    content: "Example " counter(example);
+}
+.invalid.example:not(.no-marker)::before,
+.illegal.example:not(.no-marker)::before {
+    content: "Invalid Example" counter(example);
+}
+
+figcaption {
+    counter-increment: figure;
+}
+figcaption:not(.no-marker)::before {
+    content: "Figure " counter(figure) " ";
+}</style>
+<style>/* style-dfn-panel */
+
+:root {
+    --dfnpanel-bg: #ddd;
+    --dfnpanel-text: var(--text);
+}
+.dfn-panel {
+    position: absolute;
+    z-index: 35;
+    height: auto;
+    width: -webkit-fit-content;
+    width: fit-content;
+    max-width: 300px;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.75em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--dfnpanel-bg);
+    color: var(--dfnpanel-text);
+    border: outset 0.2em;
+}
+.dfn-panel:not(.on) { display: none; }
+.dfn-panel * { margin: 0; padding: 0; text-indent: 0; }
+.dfn-panel > b { display: block; }
+.dfn-panel a { color: var(--dfnpanel-text); }
+.dfn-panel a:not(:hover) { text-decoration: none !important; border-bottom: none !important; }
+.dfn-panel > b + b { margin-top: 0.25em; }
+.dfn-panel ul { padding: 0; }
+.dfn-panel li { list-style: inside; }
+.dfn-panel.activated {
+    display: inline-block;
+    position: fixed;
+    left: .5em;
+    bottom: 2em;
+    margin: 0 auto;
+    max-width: calc(100vw - 1.5em - .4em - .5em);
+    max-height: 30vh;
+}
+
+.dfn-paneled { cursor: pointer; }
+</style>
+<style>/* style-issues */
+
+a[href].issue-return {
+    float: right;
+    float: inline-end;
+    color: var(--issueheading-text);
+    font-weight: bold;
+    text-decoration: none;
+}
+</style>
+<style>/* style-md-lists */
+
+/* This is a weird hack for me not yet following the commonmark spec
+   regarding paragraph and lists. */
+[data-md] > :first-child {
+    margin-top: 0;
+}
+[data-md] > :last-child {
+    margin-bottom: 0;
+}</style>
+<style>/* style-selflinks */
+
+:root {
+    --selflink-text: white;
+    --selflink-bg: gray;
+    --selflink-hover-text: black;
+}
+.heading, .issue, .note, .example, li, dt {
+    position: relative;
+}
+a.self-link {
+    position: absolute;
+    top: 0;
+    left: calc(-1 * (3.5rem - 26px));
+    width: calc(3.5rem - 26px);
+    height: 2em;
+    text-align: center;
+    border: none;
+    transition: opacity .2s;
+    opacity: .5;
+}
+a.self-link:hover {
+    opacity: 1;
+}
+.heading > a.self-link {
+    font-size: 83%;
+}
+li > a.self-link {
+    left: calc(-1 * (3.5rem - 26px) - 2em);
+}
+dfn > a.self-link {
+    top: auto;
+    left: auto;
+    opacity: 0;
+    width: 1.5em;
+    height: 1.5em;
+    background: var(--selflink-bg);
+    color: var(--selflink-text);
+    font-style: normal;
+    transition: opacity .2s, background-color .2s, color .2s;
+}
+dfn:hover > a.self-link {
+    opacity: 1;
+}
+dfn > a.self-link:hover {
+    color: var(--selflink-hover-text);
+}
+
+a.self-link::before            { content: "¶"; }
+.heading > a.self-link::before { content: "§"; }
+dfn > a.self-link::before      { content: "#"; }
+</style>
+ <body class="h-entry">
+  <div class="head">
+   <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
+   <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2023-06-12">12 June 2023</time></p>
+    <div data-fill-with="spec-metadata">
+     <dl>
+      <dt>This version:
+      <dd><a class="u-url" href="https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-06-12">https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-06-12</a>
+      <dt>Latest published version:
+      <dd><a href="https://www.w3.org/Consortium/Process/">https://www.w3.org/Consortium/Process/</a>
+      <dt>Editor's Draft:
+      <dd><a class="u-url" href="https://www.w3.org/Consortium/Process/Drafts/">https://www.w3.org/Consortium/Process/Drafts/</a>
+      <dt>Previous Versions:
+      <dd><a href="https://www.w3.org/2021/Process-20211102/" rel="prev">https://www.w3.org/2021/Process-20211102/</a>
+      <dd><a href="https://www.w3.org/2020/Process-20200915/" rel="prev">https://www.w3.org/2020/Process-20200915/</a>
+      <dd><a href="https://www.w3.org/2019/Process-20190301/" rel="prev">https://www.w3.org/2019/Process-20190301/</a>
+      <dd><a href="https://www.w3.org/2018/Process-20180201/" rel="prev">https://www.w3.org/2018/Process-20180201/</a>
+      <dd><a href="https://www.w3.org/2017/Process-20170301/" rel="prev">https://www.w3.org/2017/Process-20170301/</a>
+      <dt>Feedback:
+      <dd><a href="https://github.com/w3c/w3process/issues/">Github (preferred)</a>
+      <dd><a href="https://lists.w3.org/Archives/Public/public-w3process/">Public mailing list</a>
+      <dd><a href="https://lists.w3.org/Archives/Member/process-issues">Member-only mailing list</a>
+      <dt class="editor">Editors:
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://fantasai.inkedblade.net/contact">Elika J. Etemad / fantasai</a> (<span class="p-org org">Invited Expert</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://florian.rivoal.net/">Florian Rivoal</a> (<span class="p-org org">Invited Expert</span>)
+      <dt class="editor">Former Editors:
+      <dd class="editor p-author h-card vcard"><span class="p-name fn">Natasha Rooney</span> (<span class="p-org org">Invited Expert</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="http://yandex.com">Charles McCathie Nevile</a> (<span class="p-org org">Yandex</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://www.w3.org/">Ian Jacobs</a> (<span class="p-org org">W3C</span>)
+     </dl>
+    </div>
+   <div data-fill-with="warning"></div>
+   <p class="copyright" data-fill-with="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2023 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document" rel="license">permissive document license</a> rules apply. </p>
+   <hr title="Separator for header">
+  </div>
+  <div class="p-summary" data-fill-with="abstract">
+   <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></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 W3C and processes,
+	responsibilities and functions that enable W3C to accomplish its mission.
+	This document does not describe the internal workings of the Team.</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>.</p>
+  </div>
+  <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content">Status of this document</span></h2>
+  <div data-fill-with="status">
+   <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
+	working within the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a> (which anyone can join).
+	This is the 12 June 2023 Draft Community Group Report for the proposed next version of the W3C Process Document. </p>
+   <p>This document,
+
+which is based on the <a href="https://www.w3.org/2021/Process-20211102/">2 November 2021 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/Consortium/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.
+A <a href="https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-04">7 April snapshot</a> was created
+and sent for W3C Advisory Committee Review on 12 April 2023.</p>
+   <p> A <a href="#changes">history of substantial changes</a> from previous versions of the Process Document is provided. </p>
+  </div>
+  <div data-fill-with="at-risk"></div>
+  <nav data-fill-with="table-of-contents" id="toc">
+   <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
+   <ol class="toc" role="directory">
+    <li><a href="#Intro"><span class="secno">1</span> <span class="content"> Introduction</span></a>
+    <li>
+     <a href="#Organization"><span class="secno">2</span> <span class="content"> Members and the Team</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Members"><span class="secno">2.1</span> <span class="content"> Members</span></a>
+       <ol class="toc">
+        <li><a href="#MemberBenefits"><span class="secno">2.1.1</span> <span class="content"> Rights of Members</span></a>
+        <li>
+         <a href="#RelatedAndAssociatedMembers"><span class="secno">2.1.2</span> <span class="content"> Member Associations and Related Members</span></a>
+         <ol class="toc">
+          <li><a href="#MemberAssoc"><span class="secno">2.1.2.1</span> <span class="content"> Membership Associations</span></a>
+          <li><a href="#MemberRelated"><span class="secno">2.1.2.2</span> <span class="content"> Related Members</span></a>
+         </ol>
+       </ol>
+      <li><a href="#Team"><span class="secno">2.2</span> <span class="content"> The W3C Team</span></a>
+     </ol>
+    <li>
+     <a href="#groups"><span class="secno">3</span> <span class="content"> Groups and Participation</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Policies"><span class="secno">3.1</span> <span class="content"> Policies for Participation in W3C Groups</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#ParticipationCriteria"><span class="secno">3.1.1</span> <span class="content"> Individual Participation Criteria</span></a>
+         <ol class="toc">
+          <li><a href="#discipline"><span class="secno">3.1.1.1</span> <span class="content"> Expectations and Discipline</span></a>
+          <li><a href="#coi"><span class="secno">3.1.1.2</span> <span class="content"> Conflict of Interest Policy</span></a>
+          <li><a href="#member-rep"><span class="secno">3.1.1.3</span> <span class="content"> Individuals Representing a Member Organization</span></a>
+         </ol>
+        <li>
+         <a href="#GeneralMeetings"><span class="secno">3.1.2</span> <span class="content"> Meetings</span></a>
+         <ol class="toc">
+          <li><a href="#meeting-schedules"><span class="secno">3.1.2.1</span> <span class="content"> Meeting Scheduling and Announcements</span></a>
+          <li><a href="#meeting-minutes"><span class="secno">3.1.2.2</span> <span class="content"> Meeting Minutes</span></a>
+          <li><a href="#meeting-recording"><span class="secno">3.1.2.3</span> <span class="content"> Meeting Recordings and Transcripts</span></a>
+         </ol>
+        <li><a href="#tooling"><span class="secno">3.1.3</span> <span class="content"> Tooling and Archiving for Discussions and Publications</span></a>
+        <li><a href="#resignation"><span class="secno">3.1.4</span> <span class="content"> Resignation from a Group</span></a>
+       </ol>
+      <li>
+       <a href="#AC"><span class="secno">3.2</span> <span class="content"> The Advisory Committee (AC)</span></a>
+       <ol class="toc">
+        <li><a href="#ac-role"><span class="secno">3.2.1</span> <span class="content"> Role of the Advisory Committee</span></a>
+        <li><a href="#ac-participation"><span class="secno">3.2.2</span> <span class="content"> Participation in the Advisory Committee</span></a>
+        <li><a href="#ACCommunication"><span class="secno">3.2.3</span> <span class="content"> Advisory Committee Mailing Lists</span></a>
+        <li><a href="#ACMeetings"><span class="secno">3.2.4</span> <span class="content"> Advisory Committee Meetings</span></a>
+       </ol>
+      <li>
+       <a href="#elected-groups"><span class="secno">3.3</span> <span class="content"> Elected Groups: The AB and the TAG</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#AB"><span class="secno">3.3.1</span> <span class="content"> Advisory Board (AB)</span></a>
+         <ol class="toc">
+          <li><a href="#ab-role"><span class="secno">3.3.1.1</span> <span class="content"> Role of the Advisory Board</span></a>
+          <li><a href="#ABParticipation"><span class="secno">3.3.1.2</span> <span class="content"> Composition of the Advisory Board</span></a>
+          <li><a href="#ab-comm"><span class="secno">3.3.1.3</span> <span class="content"> Communications of the Advisory Board</span></a>
+          <li><a href="#ab-bod-liaison"><span class="secno">3.3.1.4</span> <span class="content"> Liaisons between the Advisory Board and the Board of Directors</span></a>
+         </ol>
+        <li>
+         <a href="#TAG"><span class="secno">3.3.2</span> <span class="content"> Technical Architecture Group (TAG)</span></a>
+         <ol class="toc">
+          <li><a href="#tag-role"><span class="secno">3.3.2.1</span> <span class="content"> Role of the Technical Architecture Group</span></a>
+          <li><a href="#tag-participation"><span class="secno">3.3.2.2</span> <span class="content"> Composition of the Technical Architecture Group</span></a>
+          <li><a href="#tag-comm"><span class="secno">3.3.2.3</span> <span class="content"> Communications of the Technical Architecture Group</span></a>
+         </ol>
+        <li>
+         <a href="#AB-TAG-participation"><span class="secno">3.3.3</span> <span class="content"> Participation in Elected Groups</span></a>
+         <ol class="toc">
+          <li><a href="#elected-expectations"><span class="secno">3.3.3.1</span> <span class="content"> Expectations for Elected Groups Participants</span></a>
+          <li><a href="#AB-TAG-constraints"><span class="secno">3.3.3.2</span> <span class="content"> Elected Groups Participation Constraints</span></a>
+          <li><a href="#AB-TAG-elections"><span class="secno">3.3.3.3</span> <span class="content"> Advisory Board and Technical Architecture Group Elections</span></a>
+          <li><a href="#TAG-appointments"><span class="secno">3.3.3.4</span> <span class="content"> Technical Architecture Group Appointments</span></a>
+          <li><a href="#random"><span class="secno">3.3.3.5</span> <span class="content"> Verifiable Random Selection Procedure</span></a>
+          <li><a href="#AB-TAG-vacated"><span class="secno">3.3.3.6</span> <span class="content"> Elected Groups Vacated Seats</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#GAGeneral"><span class="secno">3.4</span> <span class="content"> Chartered Groups: Working Groups and Interest Groups</span></a>
+       <ol class="toc">
+        <li><a href="#ReqsAllGroups"><span class="secno">3.4.1</span> <span class="content"> Requirements for All Chartered Groups</span></a>
+        <li><a href="#group-participation"><span class="secno">3.4.2</span> <span class="content"> Participation in Chartered Groups</span></a>
+        <li>
+         <a href="#chartered-group-participants"><span class="secno">3.4.3</span> <span class="content"> Types of Participants in Chartered Groups</span></a>
+         <ol class="toc">
+          <li><a href="#member-rep-wg"><span class="secno">3.4.3.1</span> <span class="content"> Member Representative in a Working Group</span></a>
+          <li><a href="#member-rep-ig"><span class="secno">3.4.3.2</span> <span class="content"> Member Representative in an Interest Group</span></a>
+          <li><a href="#invited-expert-wg"><span class="secno">3.4.3.3</span> <span class="content"> Invited Expert in a Working Group</span></a>
+          <li><a href="#invited-expert-ig"><span class="secno">3.4.3.4</span> <span class="content"> Invited Expert in an Interest Group</span></a>
+          <li><a href="#team-rep-wg"><span class="secno">3.4.3.5</span> <span class="content"> Team Representative in a Working Group</span></a>
+          <li><a href="#team-rep-ig"><span class="secno">3.4.3.6</span> <span class="content"> Team Representative in an Interest Group</span></a>
+         </ol>
+       </ol>
+     </ol>
+    <li>
+     <a href="#group-lifecyle"><span class="secno">4</span> <span class="content"> Lifecycle of Chartered Groups</span></a>
+     <ol class="toc">
+      <li><a href="#WGCharterDevelopment"><span class="secno">4.1</span> <span class="content"> Initiating Charter Development</span></a>
+      <li><a href="#WGCharter"><span class="secno">4.2</span> <span class="content"> Content of a Charter</span></a>
+      <li><a href="#CharterReview"><span class="secno">4.3</span> <span class="content"> Advisory Committee Review of a Charter</span></a>
+      <li><a href="#cfp"><span class="secno">4.4</span> <span class="content"> Call for Participation in a Chartered Group</span></a>
+      <li><a href="#charter-extension"><span class="secno">4.5</span> <span class="content"> Charter Extension</span></a>
+      <li><a href="#GeneralTermination"><span class="secno">4.6</span> <span class="content"> Chartered Group Closure</span></a>
+     </ol>
+    <li>
+     <a href="#decisions"><span class="secno">5</span> <span class="content"> Decisions</span></a>
+     <ol class="toc">
+      <li><a href="#decision-types"><span class="secno">5.1</span> <span class="content"> Types of Decisions</span></a>
+      <li>
+       <a href="#consensus-building"><span class="secno">5.2</span> <span class="content"> Consensus Building</span></a>
+       <ol class="toc">
+        <li><a href="#Consensus"><span class="secno">5.2.1</span> <span class="content"> Consensus</span></a>
+        <li><a href="#managing-dissent"><span class="secno">5.2.2</span> <span class="content"> Managing Dissent</span></a>
+        <li><a href="#Votes"><span class="secno">5.2.3</span> <span class="content"> Deciding by Vote</span></a>
+       </ol>
+      <li><a href="#formal-address"><span class="secno">5.3</span> <span class="content"> Formally Addressing an Issue</span></a>
+      <li><a href="#WGChairReopen"><span class="secno">5.4</span> <span class="content"> Reopening a Decision When Presented With New Information</span></a>
+      <li><a href="#registering-objections"><span class="secno">5.5</span> <span class="content"> Registering Formal Objections</span></a>
+      <li>
+       <a href="#addressing-fo"><span class="secno">5.6</span> <span class="content"> Addressing Formal Objections</span></a>
+       <ol class="toc">
+        <li><a href="#team-fo-mediation"><span class="secno">5.6.1</span> <span class="content"> Investigation and Mediation by the Team</span></a>
+        <li>
+         <a href="#council"><span class="secno">5.6.2</span> <span class="content"> W3C Council</span></a>
+         <ol class="toc">
+          <li><a href="#council-composition"><span class="secno">5.6.2.1</span> <span class="content"> Council Composition</span></a>
+          <li><a href="#council-delegation"><span class="secno">5.6.2.2</span> <span class="content"> Extraordinary Delegation</span></a>
+          <li><a href="#council-participation"><span class="secno">5.6.2.3</span> <span class="content"> Council Participation, Dismissal, and Renunciation</span></a>
+          <li><a href="#council-short-circuit"><span class="secno">5.6.2.4</span> <span class="content"> Unanimous Short Circuit</span></a>
+          <li><a href="#council-chairing"><span class="secno">5.6.2.5</span> <span class="content"> Council Chairing</span></a>
+          <li><a href="#council-deliberations"><span class="secno">5.6.2.6</span> <span class="content"> Council Deliberations</span></a>
+          <li><a href="#council-decision"><span class="secno">5.6.2.7</span> <span class="content"> Council Decision Report</span></a>
+          <li><a href="#council-appeals"><span class="secno">5.6.2.8</span> <span class="content"> Appealing Council Decisions</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#ACReview"><span class="secno">5.7</span> <span class="content"> Advisory Committee Reviews</span></a>
+       <ol class="toc">
+        <li><a href="#ACReviewStart"><span class="secno">5.7.1</span> <span class="content"> Start of a Review Period</span></a>
+        <li><a href="#ACReviewAfter"><span class="secno">5.7.2</span> <span class="content"> After the Review Period</span></a>
+       </ol>
+      <li><a href="#ACVotes"><span class="secno">5.8</span> <span class="content"> Advisory Committee Votes</span></a>
+      <li><a href="#ACAppeal"><span class="secno">5.9</span> <span class="content"> Appeal by Advisory Committee Representatives</span></a>
+     </ol>
+    <li>
+     <a href="#Reports"><span class="secno">6</span> <span class="content"> W3C Technical Reports</span></a>
+     <ol class="toc">
+      <li><a href="#recs-and-notes"><span class="secno">6.1</span> <span class="content"> Types of Technical Reports</span></a>
+      <li>
+       <a href="#general-requirements"><span class="secno">6.2</span> <span class="content"> General Requirements for Technical Reports</span></a>
+       <ol class="toc">
+        <li><a href="#publication"><span class="secno">6.2.1</span> <span class="content"> Publication of Technical Reports</span></a>
+        <li>
+         <a href="#doc-reviews"><span class="secno">6.2.2</span> <span class="content"> Reviews and Review Responsibilities</span></a>
+         <ol class="toc">
+          <li><a href="#wide-review"><span class="secno">6.2.2.1</span> <span class="content"> Wide Review</span></a>
+         </ol>
+        <li><a href="#correction-classes"><span class="secno">6.2.3</span> <span class="content"> Classes of Changes</span></a>
+        <li><a href="#errata"><span class="secno">6.2.4</span> <span class="content"> Errata Management</span></a>
+        <li><a href="#candidate-amendments"><span class="secno">6.2.5</span> <span class="content"> Candidate Amendments</span></a>
+        <li><a href="#contributor-license"><span class="secno">6.2.6</span> <span class="content"> License Grants from Non-Participants</span></a>
+       </ol>
+      <li>
+       <a href="#rec-track"><span class="secno">6.3</span> <span class="content"> The W3C Recommendation Track</span></a>
+       <ol class="toc">
+        <li><a href="#maturity-stages"><span class="secno">6.3.1</span> <span class="content"> Maturity Stages on the Recommendation Track</span></a>
+        <li><a href="#implementation-experience"><span class="secno">6.3.2</span> <span class="content"> Implementation Experience</span></a>
+        <li><a href="#transition-reqs"><span class="secno">6.3.3</span> <span class="content"> Advancement on the Recommendation Track</span></a>
+        <li>
+         <a href="#update-reqs"><span class="secno">6.3.4</span> <span class="content"> Updating Mature Publications on the Recommendation Track</span></a>
+         <ol class="toc">
+          <li><a href="#streamlined-update"><span class="secno">6.3.4.1</span> <span class="content"> Streamlined Publication Approval</span></a>
+         </ol>
+        <li><a href="#first-wd"><span class="secno">6.3.5</span> <span class="content"> Publishing a First Public Working Draft</span></a>
+        <li><a href="#revising-wd"><span class="secno">6.3.6</span> <span class="content"> Revising a Working Draft</span></a>
+        <li><a href="#transition-cr"><span class="secno">6.3.7</span> <span class="content"> Transitioning to Candidate Recommendation</span></a>
+        <li>
+         <a href="#revising-cr"><span class="secno">6.3.8</span> <span class="content"> Revising a Candidate Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#publishing-crrs"><span class="secno">6.3.8.1</span> <span class="content"> Publishing a <span>Candidate Recommendation Snapshot</span></span></a>
+          <li><a href="#publishing-crud"><span class="secno">6.3.8.2</span> <span class="content"> Publishing a <span>Candidate Recommendation Draft</span></span></a>
+         </ol>
+        <li><a href="#transition-pr"><span class="secno">6.3.9</span> <span class="content"> Transitioning to Proposed Recommendation</span></a>
+        <li><a href="#transition-rec"><span class="secno">6.3.10</span> <span class="content"> Transitioning to W3C Recommendation</span></a>
+        <li>
+         <a href="#revising-rec"><span class="secno">6.3.11</span> <span class="content"> Revising a W3C Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#revised-rec-markup"><span class="secno">6.3.11.1</span> <span class="content"> Revising a Recommendation: Markup Changes</span></a>
+          <li><a href="#revised-rec-editorial"><span class="secno">6.3.11.2</span> <span class="content"> Revising a Recommendation: Editorial Changes</span></a>
+          <li><a href="#revised-rec-substantive"><span class="secno">6.3.11.3</span> <span class="content"> Revising a Recommendation: Substantive Changes</span></a>
+          <li><a href="#revised-rec-features"><span class="secno">6.3.11.4</span> <span class="content"> Revising a Recommendation: New Features</span></a>
+          <li><a href="#change-review"><span class="secno">6.3.11.5</span> <span class="content"> Incorporating Candidate Amendments</span></a>
+         </ol>
+        <li><a href="#rec-track-regression"><span class="secno">6.3.12</span> <span class="content"> Regression on the Recommendation Track</span></a>
+        <li>
+         <a href="#tr-end"><span class="secno">6.3.13</span> <span class="content"> Retiring Recommendation Track Documents</span></a>
+         <ol class="toc">
+          <li><a href="#abandon-draft"><span class="secno">6.3.13.1</span> <span class="content"> Abandoning an Unfinished Recommendation</span></a>
+          <li><a href="#rescind-cr"><span class="secno">6.3.13.2</span> <span class="content"> Rescinding a Candidate Recommendation</span></a>
+          <li><a href="#rec-rescind"><span class="secno">6.3.13.3</span> <span class="content"> Abandoning a W3C Recommendation</span></a>
+          <li><a href="#deactivation"><span class="secno">6.3.13.4</span> <span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#note-track"><span class="secno">6.4</span> <span class="content"> The Note Track (Notes and Statements)</span></a>
+       <ol class="toc">
+        <li><a href="#Note"><span class="secno">6.4.1</span> <span class="content"> Group Notes</span></a>
+        <li><a href="#publishing-notes"><span class="secno">6.4.2</span> <span class="content"> Publishing Notes</span></a>
+        <li><a href="#w3c-statement"><span class="secno">6.4.3</span> <span class="content"> Elevating Group Notes to W3C Statement status</span></a>
+        <li><a href="#revising-memo"><span class="secno">6.4.4</span> <span class="content"> Revising W3C Statements</span></a>
+       </ol>
+      <li>
+       <a href="#registries"><span class="secno">6.5</span> <span class="content"> The Registry Track</span></a>
+       <ol class="toc">
+        <li><a href="#reg-def"><span class="secno">6.5.1</span> <span class="content"> Registry Definitions</span></a>
+        <li><a href="#reg-pub"><span class="secno">6.5.2</span> <span class="content"> Publishing Registries</span></a>
+        <li><a href="#reg-table-update"><span class="secno">6.5.3</span> <span class="content"> Updating Registry Tables</span></a>
+        <li><a href="#reg-data-reports"><span class="secno">6.5.4</span> <span class="content"> Registry Data Reports</span></a>
+        <li><a href="#reg-ref-specifications"><span class="secno">6.5.5</span> <span class="content"> Specifications that Reference Registries</span></a>
+       </ol>
+      <li><a href="#switching-tracks"><span class="secno">6.6</span> <span class="content"> Switching Tracks</span></a>
+      <li><a href="#further-reading"><span class="secno">6.7</span> <span class="content"> Further reading</span></a>
+     </ol>
+    <li>
+     <a href="#dissemination"><span class="secno">7</span> <span class="content"> <span></span> Dissemination Policies</span></a>
+     <ol class="toc">
+      <li><a href="#pub-com"><span class="secno">7.1</span> <span class="content"> Public Communication</span></a>
+      <li><a href="#confidentiality-levels"><span class="secno">7.2</span> <span class="content"> Confidentiality Levels</span></a>
+      <li><a href="#confidentiality-change"><span class="secno">7.3</span> <span class="content"> Changing Confidentiality Level</span></a>
+     </ol>
+    <li><a href="#GAEvents"><span class="secno">8</span> <span class="content"> Workshops and Symposia</span></a>
+    <li><a href="#Liaisons"><span class="secno">9</span> <span class="content"> Liaisons</span></a>
+    <li>
+     <a href="#Submission"><span class="secno">10</span> <span class="content"> Member Submission Process</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#SubmissionRights"><span class="secno">10.1</span> <span class="content"> Submitter Rights and Obligations</span></a>
+       <ol class="toc">
+        <li><a href="#SubmissionScope"><span class="secno">10.1.1</span> <span class="content"> Scope of Member Submissions</span></a>
+        <li><a href="#SubmissionReqs"><span class="secno">10.1.2</span> <span class="content"> Information Required in a Submission Request</span></a>
+       </ol>
+      <li><a href="#TeamSubmissionRights"><span class="secno">10.2</span> <span class="content"> Team Rights and Obligations</span></a>
+      <li><a href="#SubmissionYes"><span class="secno">10.3</span> <span class="content"> Acknowledgment of a Submission Request</span></a>
+      <li><a href="#SubmissionNo"><span class="secno">10.4</span> <span class="content"> Rejection of a Submission Request, and Submission Appeals</span></a>
+     </ol>
+    <li><a href="#GAProcess"><span class="secno">11</span> <span class="content"> Process Evolution</span></a>
+    <li><a href="#acks"><span class="secno">12</span> <span class="content"> Acknowledgments</span></a>
+    <li>
+     <a href="#changes"><span class="secno">13</span> <span class="content"> Changes</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#changes-2021"><span class="secno"></span> <span class="content"> Changes since the <span>2 November 2021 Process</span></span></a>
+       <ol class="toc">
+        <li><a href="#dirfree-changes"><span class="secno"></span> <span class="content"> Changes related to the role of the Director</span></a>
+        <li><a href="#other-gov-changes"><span class="secno"></span> <span class="content"> Other Governance Changes</span></a>
+        <li><a href="#misc-changes"><span class="secno"></span> <span class="content"> Other miscellaneous changes</span></a>
+       </ol>
+      <li><a href="#changes-previous"><span class="secno"></span> <span class="content"> Changes since earlier versions</span></a>
+     </ol>
+    <li>
+     <a href="#w3c-conformance"><span class="secno"></span> <span class="content">Conformance</span></a>
+     <ol class="toc">
+      <li><a href="#w3c-conventions"><span class="secno"></span> <span class="content">Document conventions</span></a>
+     </ol>
+    <li>
+     <a href="#index"><span class="secno"></span> <span class="content">Index</span></a>
+     <ol class="toc">
+      <li><a href="#index-defined-here"><span class="secno"></span> <span class="content">Terms defined by this specification</span></a>
+      <li><a href="#index-defined-elsewhere"><span class="secno"></span> <span class="content">Terms defined by reference</span></a>
+     </ol>
+    <li>
+     <a href="#references"><span class="secno"></span> <span class="content">References</span></a>
+     <ol class="toc">
+      <li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
+      <li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
+     </ol>
+   </ol>
+  </nav>
+  <main>
+   <h2 class="no-num no-toc no-ref heading settled" id="pp"><span class="content"> Relation of Process Document to Patent Policy and Other Policies</span></h2>
+   <p>W3C Members' attention is called to the fact
+	that provisions of the Process Document are binding on Members
+	per the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement">[MEMBER-AGREEMENT]</a>.
+	The <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> and other policies
+	incorporated by normative reference as a part of the Process Document
+	are equally binding.</p>
+   <p>The Patent Policy and CEPC 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 CEPC have been designed to allow each to evolve independently.</p>
+   <p>In the Process Document, the term “participant” refers to an individual, not an organization.</p>
+   <h2 class="no-num no-toc no-ref heading settled" id="terms"><span class="content"> Conformance and specialized terms</span></h2>
+   <p>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 data-dfn-type="dfn" data-noexport id="not-required"><em class="rfc2119">not required</em><a class="self-link" href="#not-required"></a></dfn> is equivalent to the term <em class="rfc2119">may</em> as defined in RFC2119 <a data-link-type="biblio" href="#biblio-rfc2119">[RFC2119]</a>.</p>
+   <p>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.</p>
+   <nav data-fill-with="table-of-contents"></nav>
+   <main>
+    <h2 class="heading settled" data-level="1" id="Intro"><span class="secno">1. </span><span class="content"> Introduction</span><a class="self-link" href="#Intro"></a></h2>
+    <p>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>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>. <a href="#group-participation">Participants</a> in W3C include <a href="#member-rep">representatives of its Members</a> and the <a data-link-type="dfn" href="#team" id="ref-for-team">Team</a>,
+	as well as <a href="#invited-expert-wg">Invited Experts</a> who can bring additional expertise or represent additional stakeholders. <a data-link-type="dfn" href="#team" id="ref-for-team①">Team</a> representatives both contribute to the technical work
+	and help ensure each group’s proper integration with the rest of W3C.</p>
+    <p>W3C’s technical standards, called <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C">W3C Recommendations</a>,
+	are developed by its <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG">Working Groups</a>;
+	W3C also has other types of publications,
+	all described in <a href="#Reports">§ 6 W3C Technical Reports</a>.
+	W3C has various types of groups;
+	this document describes the formation and policies
+	of its chartered <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG">Interest Groups</a>,
+	see <a href="#Policies">§ 3.1 Policies for Participation in W3C Groups</a> and <a href="#GAGeneral">§ 3.4 Chartered Groups: Working Groups and Interest Groups</a>.
+	W3C also operates Community and Business Groups,
+	which are separately described in <a href="https://www.w3.org/community/about/agreements/">their own process document</a> <a data-link-type="biblio" href="#biblio-bg-cg">[BG-CG]</a>.</p>
+    <p>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.</p>
+    <p>Here is a general overview of how W3C initiates standardization of a Web technology:</p>
+    <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 <a data-link-type="dfn" href="#team" id="ref-for-team②">Team</a> 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>
+    <p>Further sections of this Process Document deal with topics including
+	liaisons (<a href="#Liaisons">§ 9 Liaisons</a>),
+	confidentiality (<a href="#dissemination">§ 7 Dissemination Policies</a>),
+	and formal decisions and appeals (<a href="#decisions">§ 5 Decisions</a>).</p>
+    <h2 class="heading settled" data-level="2" id="Organization"><span class="secno">2. </span><span class="content"> Members and the Team</span><a class="self-link" href="#Organization"></a></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 class="heading settled" data-level="2.1" id="Members"><span class="secno">2.1. </span><span class="content"> Members</span><a class="self-link" href="#Members"></a></h3>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Member|Member" data-noexport id="w3c-member">W3C Members</dfn> are
+	organizations subscribed according to the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement">[MEMBER-AGREEMENT]</a>.
+	They are represented in W3C processes as follows:</p>
+    <ol>
+     <li> One representative per Member organization participates
+			in the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee">Advisory Committee</a> 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/Consortium/join">How to Join W3C</a>” <a data-link-type="biblio" href="#biblio-join">[JOIN]</a>;
+	(refer to the public list of <a href="https://www.w3.org/Consortium/Member/List">current W3C Members</a> <a data-link-type="biblio" href="#biblio-member-list">[MEMBER-LIST]</a>).
+	The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure
+	that Member participation agreements remain <a href="#Team-only" id="ref-for-Team-only">Team-only</a> and that no Member receives preferential treatment within W3C. </p>
+    <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. </p>
+    <h4 class="heading settled" data-level="2.1.1" id="MemberBenefits"><span class="secno">2.1.1. </span><span class="content"> Rights of Members</span><a class="self-link" href="#MemberBenefits"></a></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> Access to <a href="#Member-only" id="ref-for-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> <a data-link-type="biblio" href="#biblio-intro">[INTRO]</a>. 
+    </ul>
+    <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> In <a href="#GAEvents">Workshops and Symposia</a>; 
+     <li> On the Team, as <a href="#fellows" id="ref-for-fellows">W3C Fellows</a>. 
+    </ul>
+    <p>The rights and benefits of W3C membership <a data-link-type="biblio" href="#biblio-member-agreement">[MEMBER-AGREEMENT]</a> are contingent upon conformance to the processes described in this document.
+	Disciplinary action for anyone participating in W3C activities is described in <a href="#discipline">§ 3.1.1.1 Expectations and Discipline</a>.</p>
+    <p>Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member website</a> <a data-link-type="biblio" href="#biblio-member-hp">[MEMBER-HP]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.2" id="RelatedAndAssociatedMembers"><span class="secno">2.1.2. </span><span class="content"> Member Associations and Related Members</span><span id="RelatedAndConsortiumMembers"></span><a class="self-link" href="#RelatedAndAssociatedMembers"></a></h4>
+    <h5 class="heading settled" data-level="2.1.2.1" id="MemberAssoc"><span class="secno">2.1.2.1. </span><span class="content"> Membership Associations</span><span id="fdn-member-consortium"></span><span id="MemberConsortia"></span><a class="self-link" href="#MemberAssoc"></a></h5>
+    <p>A “<dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Member Association | Member Associations" data-noexport id="member-association">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 <a data-link-type="dfn" href="#member-association" id="ref-for-member-association">Member Association</a> merely because it has shareholders or stockholders.
+	If it is not clear whether a prospective Member qualifies as a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association①">Member Association</a>,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo">CEO</a> may reasonably make the determination.
+	For a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association②">Member Association</a>, the rights and privileges of W3C Membership
+	described in the W3C Process Document extend to the <a data-link-type="dfn" href="#member-association" id="ref-for-member-association③">Member Association</a>'s paid staff
+	and Advisory Committee representative.</p>
+    <p><a data-link-type="dfn" href="#member-association" id="ref-for-member-association④">Member Associations</a> <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>
+    <p>For <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑤">Member Associations</a> 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.</p>
+    <p>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.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="2.1.2.2" id="MemberRelated"><span class="secno">2.1.2.2. </span><span class="content"> Related Members</span><a class="self-link" href="#MemberRelated"></a></h5>
+    <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 <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Related Member" id="related-member">related</dfn> if:</p>
+    <ol>
+     <li> Either Member is a <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary">subsidiary</a> of the other, or 
+     <li> Both Members are <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary①">subsidiaries</a> of a common entity, or 
+     <li> The Members have an employment contract or consulting contract that affects W3C participation. 
+    </ol>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="subsidiary">subsidiary</dfn> is an organization of which effective control and/or majority ownership rests with another,
+	single organization.</p>
+    <p><a data-link-type="dfn" href="#related-member" id="ref-for-related-member">Related Members</a> <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> <a data-link-type="biblio" href="#biblio-intro">[INTRO]</a>.</p>
+    <h3 class="heading settled" data-level="2.2" id="Team"><span class="secno">2.2. </span><span class="content"> The W3C Team</span><span id="def-Director"></span><a class="self-link" href="#Team"></a></h3>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team | W3C Team" id="team">Team</dfn> consists of <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="ceo">CEO</dfn>,
+	W3C paid staff,
+	unpaid interns,
+	and W3C Fellows. <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fellows">W3C Fellows</dfn> are Member employees working as part of the Team;
+	see the <a href="https://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a> <a data-link-type="biblio" href="#biblio-fellows">[FELLOWS]</a>.
+	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.</p>
+    <p>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. <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision">Team Decisions</a> derive from the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo①">CEO</a>'s authority,
+	even when they are carried out by other members of the <a data-link-type="dfn" href="#team" id="ref-for-team③">Team</a>.</p>
+    <p>Oversight over the <a data-link-type="dfn" href="#team" id="ref-for-team④">Team</a>,
+	budgeting,
+	and other business decisions,
+	is provided by the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="BoD | Board | Board of Directors | W3C Board of Directors" id="bod">W3C Board of Directors</dfn>,
+	rather than managed directly by the Process.</p>
+    <p class="note" role="note"><span>Note:</span> See the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf">W3C Bylaws</a> for more details
+	on the <a data-link-type="dfn" href="#bod" id="ref-for-bod">Board</a> and overall governance of W3C.</p>
+    <h2 class="heading settled" data-level="3" id="groups"><span class="secno">3. </span><span class="content"> Groups and Participation</span><a class="self-link" href="#groups"></a></h2>
+    <p>For the purposes of this Process, a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="group" data-noexport id="w3c-group">W3C Group</dfn> is one of W3C’s <a href="#wgparticipant" id="ref-for-wgparticipant">Working Groups</a>, <a href="#igparticipant" id="ref-for-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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="participant">participant</dfn> is a member of such a group.</p>
+    <h3 class="heading settled" data-level="3.1" id="Policies"><span class="secno">3.1. </span><span class="content"> Policies for Participation in W3C Groups</span><a class="self-link" href="#Policies"></a></h3>
+    <h4 class="heading settled" data-level="3.1.1" id="ParticipationCriteria"><span class="secno">3.1.1. </span><span class="content"> Individual Participation Criteria</span><a class="self-link" href="#ParticipationCriteria"></a></h4>
+    <h5 class="heading settled" data-level="3.1.1.1" id="discipline"><span class="secno">3.1.1.1. </span><span class="content"> Expectations and Discipline</span><a class="self-link" href="#discipline"></a></h5>
+    <p>There are three qualities an individual is expected to demonstrate in order to participate in W3C:</p>
+    <ol>
+     <li> Technical competence in one’s role; 
+     <li> The ability to act fairly; 
+     <li> Social competence in one’s role. 
+    </ol>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative">Advisory Committee representatives</a> who nominate individuals from their organization for participation in W3C activities
+	are responsible for assessing and attesting to the qualities of those nominees.</p>
+    <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/Consortium/cepc/">W3C Code of Ethics and Professional Conduct</a> <a data-link-type="biblio" href="#biblio-cepc">[CEPC]</a> and the participation requirements described in
+	“Disclosure”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>. </p>
+    <p>The <a data-link-type="dfn" href="#ceo" id="ref-for-ceo②">CEO</a> <em class="rfc2119">may</em> take disciplinary action,
+	including suspending or removing for cause
+	a participant in any group (including the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group">TAG</a>)
+	if serious and/or repeated violations,
+	such as failure to meet the requirements on individual behavior of
+	(a) this process
+	and in particular the CEPC, or
+	(b) the membership agreement, or
+	(c) applicable laws,
+	occur.
+	Refer to the <a href="https://www.w3.org/Guide/process/banning.html">Guidelines to suspend or remove participants from groups</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.2" id="coi"><span class="secno">3.1.1.2. </span><span class="content"> Conflict of Interest Policy</span><a class="self-link" href="#coi"></a></h5>
+    <p>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.</p>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑤">Team</a> <em class="rfc2119">may</em> appoint a new group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs">Chair</a> 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).</p>
+    <p>The following are some scenarios where disclosure is appropriate:</p>
+    <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>
+    <p>Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the <a data-link-type="dfn" href="#team" id="ref-for-team⑥">Team</a>.</p>
+    <p><a data-link-type="dfn" href="#team" id="ref-for-team⑦">Team</a> members are subject to the <a href="https://www.w3.org/2000/09/06-conflictpolicy">W3C Team conflict of interest policy</a> <a data-link-type="biblio" href="#biblio-conflict-policy">[CONFLICT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.3" id="member-rep"><span class="secno">3.1.1.3. </span><span class="content"> Individuals Representing a Member Organization</span><a class="self-link" href="#member-rep"></a></h5>
+    <p>Generally, individuals representing a Member in an official capacity within W3C
+	are employees of the Member organization.
+	However, an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①">Advisory Committee representative</a> <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.</p>
+    <p>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 <a data-link-type="dfn" href="#ceo" id="ref-for-ceo③">CEO</a> <em class="rfc2119">may</em> decline
+	to allow an individual designated by an Advisory Committee representative to participate in a group.</p>
+    <p>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>).</p>
+    <h4 class="heading settled" data-level="3.1.2" id="GeneralMeetings"><span class="secno">3.1.2. </span><span class="content"> Meetings</span><a class="self-link" href="#GeneralMeetings"></a></h4>
+    <p>The requirements in this section apply to the official meetings of any <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group">W3C group</a>.</p>
+    <p>W3C distinguishes two types of meetings:</p>
+    <ol>
+     <li> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 class="dfn-paneled" data-dfn-type="dfn" data-noexport 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>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①">Chair</a> <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 <a data-link-type="dfn" href="#participant" id="ref-for-participant">participant</a>.
+	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.</p>
+    <h5 class="heading settled" data-level="3.1.2.1" id="meeting-schedules"><span class="secno">3.1.2.1. </span><span class="content"> Meeting Scheduling and Announcements</span><a class="self-link" href="#meeting-schedules"></a></h5>
+    <p>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.</p>
+    <p>The following table lists <em class="rfc2119">recommendations</em> for organizing a meeting:</p>
+    <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"><a data-link-type="dfn" href="#minutes" id="ref-for-minutes">Minutes</a> available (after) 
+       <td><span class="time-interval">two weeks</span> 
+       <td><span class="time-interval">48 hours</span> 
+    </table>
+    <p><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.</p>
+    <h5 class="heading settled" data-level="3.1.2.2" id="meeting-minutes"><span class="secno">3.1.2.2. </span><span class="content"> Meeting Minutes</span><a class="self-link" href="#meeting-minutes"></a></h5>
+    <p>Groups <em class="rfc2119">should</em> take and retain <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minutes">minutes</dfn> of their meetings,
+	and <em class="rfc2119">must</em> record
+	any official <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision">group decisions</a> made during the meeting discussions.
+	Details of the discussion leading to such decisions are not required,
+	provided that the rationale for the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision①">group decision</a> is nonetheless clear.</p>
+    <h5 class="heading settled" data-level="3.1.2.3" id="meeting-recording"><span class="secno">3.1.2.3. </span><span class="content"> Meeting Recordings and Transcripts</span><a class="self-link" href="#meeting-recording"></a></h5>
+    <p>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.</p>
+    <h4 class="heading settled" data-level="3.1.3" id="tooling"><span class="secno">3.1.3. </span><span class="content"> Tooling and Archiving for Discussions and Publications</span><a class="self-link" href="#tooling"></a></h4>
+    <p>For <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group①">W3C Groups</a> 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:</p>
+    <ul>
+     <li id="report-stability"><a class="self-link" href="#report-stability"></a> 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"><a class="self-link" href="#report-accessibility"></a> 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">
+      <a class="self-link" href="#discussion-archiving"></a> 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. 
+      <p class="note" role="note"><span>Note:</span> The lack, or loss, of such archives does not by itself
+			invalidate an otherwise-valid decision.</p>
+     <li id="tool-accessibility">
+      <a class="self-link" href="#tool-accessibility"></a> 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. 
+      <p class="note" role="note"><span>Note:</span> If a new participant joins who cannot use the tool,
+			this can require the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②">Working Group</a> to change its tooling
+			or operate some workaround.</p>
+     <li id="where-is-your-stuff"><a class="self-link" href="#where-is-your-stuff"></a> 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>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧">Team</a> is responsible for ensuring adherence to these rules
+	and for bringing any group not in compliance into compliance.</p>
+    <h4 class="heading settled" data-level="3.1.4" id="resignation"><span class="secno">3.1.4. </span><span class="content"> Resignation from a Group</span><a class="self-link" href="#resignation"></a></h4>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑨">Team</a>,
+	the Member and their representatives
+	or the Invited Expert
+	will be deemed to have resigned from the relevant group.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪">Team</a> <em class="rfc2119">must</em> record the notification.
+	See “Exclusion and Resignation from the Working Group” in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> for information about obligations remaining after resignation from certain groups.</p>
+    <h3 class="heading settled" data-level="3.2" id="AC"><span class="secno">3.2. </span><span class="content"> The Advisory Committee (AC)</span><a class="self-link" href="#AC"></a></h3>
+    <h4 class="heading settled" data-level="3.2.1" id="ac-role"><span class="secno">3.2.1. </span><span class="content"> Role of the Advisory Committee</span><a class="self-link" href="#ac-role"></a></h4>
+    <p id="ReviewAppeal"> The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee|AC" id="advisory-committee">Advisory Committee</dfn> represents
+	the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member">Members</a> of W3C at large.
+	It is responsible for: </p>
+    <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="#RecsPR" id="ref-for-RecsPR">Proposed Recommendations</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>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> of a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision">W3C decision</a> or <a data-link-type="dfn" href="#team" id="ref-for-team①①">Team</a>'s decision.</p>
+    <p>See also the additional roles of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③">Advisory Committee representatives</a> described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <h4 class="heading settled" data-level="3.2.2" id="ac-participation"><span class="secno">3.2.2. </span><span class="content"> Participation in the Advisory Committee</span><a class="self-link" href="#ac-participation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①">Advisory Committee</a> is composed of one <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee representative| AC representative" id="advisory-committee-representative">representative</dfn> from each Member organization
+	(refer to the <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①②">Member-only</a> list
+	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. <a data-link-type="biblio" href="#biblio-current-ac">[CURRENT-AC]</a>)</p>
+    <p>When an organization joins W3C
+	(see “<a href="https://www.w3.org/Consortium/join">How to Join W3C</a>” <a data-link-type="biblio" href="#biblio-join">[JOIN]</a>),
+	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement.
+	The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro">[INTRO]</a> 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 <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative④">Advisory Committee representative</a>,
+	and more. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑤">Advisory Committee representatives</a> <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.</p>
+    <p>The AC representative may delegate any of their rights and responsibilities
+	to an <dfn data-dfn-type="dfn" data-export data-lt="alternate AC representative | alternate Advisory Committee representative | alt AC rep" id="alternate-ac-representative">alternate<a class="self-link" href="#alternate-ac-representative"></a></dfn> (except the ability to designate an alternate).</p>
+    <h4 class="heading settled" data-level="3.2.3" id="ACCommunication"><span class="secno">3.2.3. </span><span class="content"> Advisory Committee Mailing Lists</span><a class="self-link" href="#ACCommunication"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②">Team</a> <em class="rfc2119">must</em> provide two mailing lists for use by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②">Advisory Committee</a>:</p>
+    <ol>
+     <li> One for official announcements (e.g., those required by this document) from the <a data-link-type="dfn" href="#team" id="ref-for-team①③">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③">Advisory Committee</a>.
+			This list is read-only for Advisory Committee representatives. 
+     <li> One for discussion among <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑥">Advisory Committee representatives</a>.
+			Though this list is primarily for Advisory Committee representatives,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①④">Team</a> <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>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑦">Advisory Committee representative</a> <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.</p>
+    <h4 class="heading settled" data-level="3.2.4" id="ACMeetings"><span class="secno">3.2.4. </span><span class="content"> Advisory Committee Meetings</span><a class="self-link" href="#ACMeetings"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑤">Team</a> organizes a <a href="#ftf-meeting" id="ref-for-ftf-meeting">face-to-face meeting</a> for the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④">Advisory Committee</a> <span class="time-interval">twice a year</span>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⑥">Team</a> 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:</p>
+    <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>
+    </dl>
+    <p>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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑦">Team</a> <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.</p>
+    <p>More information about <a href="https://www.w3.org/Member/Meeting/">Advisory Committee meetings</a> <a data-link-type="biblio" href="#biblio-ac-meeting">[AC-MEETING]</a> is available at the Member website.</p>
+    <h3 class="heading settled" data-level="3.3" id="elected-groups"><span class="secno">3.3. </span><span class="content"> Elected Groups: The AB and the TAG</span><a class="self-link" href="#elected-groups"></a></h3>
+    <p>The W3C Process defines two types of <dfn data-dfn-type="dfn" data-export id="elected-group">elected groups<a class="self-link" href="#elected-group"></a></dfn>:
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①">Advisory Board</a> (AB) and
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①">Technical Architecture Group</a> (TAG),
+	both elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑤">Advisory Committee</a>.</p>
+    <h4 class="heading settled" data-level="3.3.1" id="AB"><span class="secno">3.3.1. </span><span class="content"> Advisory Board (AB)</span><a class="self-link" href="#AB"></a></h4>
+    <h5 class="heading settled" data-level="3.3.1.1" id="ab-role"><span class="secno">3.3.1.1. </span><span class="content"> Role of the Advisory Board</span><a class="self-link" href="#ab-role"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Board|AB" id="advisory-board">Advisory Board</dfn> 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>.
+	As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council">W3C Council</a>,
+	members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②">Advisory Board</a> hear and adjudicate on <a href="#SubmissionNo">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③">Advisory Board</a> is distinct from the <a data-link-type="dfn" href="#bod" id="ref-for-bod①">Board of Directors</a> and has no decision-making authority within W3C;
+	its role is strictly advisory.</p>
+    <p class="note" role="note"><span>Note:</span> While the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board④">AB</a> as such does not have decision-making authority,
+	its members do when sitting as part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①">W3C Council</a>.</p>
+    <p>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> <a data-link-type="biblio" href="#biblio-ab-hp">[AB-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.1.2" id="ABParticipation"><span class="secno">3.3.1.2. </span><span class="content"> Composition of the Advisory Board</span><a class="self-link" href="#ABParticipation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑤">Advisory Board</a> 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 <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑥">AB</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⑧">Team</a> appoints the Chair,
+	who <em class="rfc2119">should</em> choose a co-chair among the elected participants.
+	The Chair(s) are subject to ratification by secret ballot
+	by two thirds of the AB upon appointment.
+	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.</p>
+    <p>The team also appoints a <a href="https://www.w3.org/Guide/teamcontact/role.html">Team Contact</a>,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.
+	The CEO and Team Contact have a standing invitation
+	to all regular Advisory Board sessions.</p>
+    <p>The nine to eleven <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑦">Advisory Board</a> participants are elected by the W3C <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑥">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.</p>
+    <p>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.</p>
+    <p></p>
+    <h5 class="heading settled" data-level="3.3.1.3" id="ab-comm"><span class="secno">3.3.1.3. </span><span class="content"> Communications of the Advisory Board</span><a class="self-link" href="#ab-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑨">Team</a> <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.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑧">Advisory Board</a> <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>.</p>
+    <h5 class="heading settled" data-level="3.3.1.4" id="ab-bod-liaison"><span class="secno">3.3.1.4. </span><span class="content"> Liaisons between the Advisory Board and the Board of Directors</span><a class="self-link" href="#ab-bod-liaison"></a></h5>
+    <p>To ensure good communication between the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑨">AB</a> and the <a data-link-type="dfn" href="#bod" id="ref-for-bod②">Board of Directors</a> and facilitate operational and management consistency,
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⓪">AB</a> <em class="rfc2119">may</em> appoint up to two of its participants as liaisons to the <a data-link-type="dfn" href="#bod" id="ref-for-bod③">Board</a>.
+	Such appointees are expected to attend and participate in <a data-link-type="dfn" href="#bod" id="ref-for-bod④">Board</a> meetings
+	and access <a data-link-type="dfn" href="#bod" id="ref-for-bod⑤">Board</a> materials
+	as Non-voting Observers. <a data-link-type="biblio" href="#biblio-bylaws">[BYLAWS]</a> They do not form part of the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑥">Board</a>'s decision-making body,
+	and may be excluded from such participation
+	in accordance with applicable Board procedures.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①①">Advisory Board</a> <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.</p>
+    <h4 class="heading settled" data-level="3.3.2" id="TAG"><span class="secno">3.3.2. </span><span class="content"> Technical Architecture Group (TAG)</span><a class="self-link" href="#TAG"></a></h4>
+    <h5 class="heading settled" data-level="3.3.2.1" id="tag-role"><span class="secno">3.3.2.1. </span><span class="content"> Role of the Technical Architecture Group</span><a class="self-link" href="#tag-role"></a></h5>
+    <p>The mission of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Technical Architecture Group|TAG" id="technical-architecture-group">TAG</dfn> is stewardship of the Web architecture.
+	There are three aspects to this mission:</p>
+    <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> to help coordinate cross-technology architecture developments inside and outside W3C. 
+    </ol>
+    <p>As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②">W3C Council</a>,
+	the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②">TAG</a> hear and adjudicate on <a href="#SubmissionNo">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③">TAG</a>'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/2004/10/27-tag-charter.html">TAG charter</a> <a data-link-type="biblio" href="#biblio-tag-charter">[TAG-CHARTER]</a> for more information about the background and scope of the TAG,
+	and the expected qualifications of TAG participants.</p>
+    <p>When the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④">TAG</a> votes to resolve an issue,
+	each TAG participant
+	(whether appointed, elected, or the Chair)
+	has one vote;
+	see also the section on <a href="https://www.w3.org/2004/10/27-tag-charter.html#Voting">voting in the TAG charter</a> <a data-link-type="biblio" href="#biblio-tag-charter">[TAG-CHARTER]</a> and the general section on <a href="#Votes">votes</a> in this Process Document.</p>
+    <p>Details about the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑤">TAG</a> (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings)
+	are available at the <a href="https://www.w3.org/2001/tag/">TAG home page</a> <a data-link-type="biblio" href="#biblio-tag-hp">[TAG-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.2.2" id="tag-participation"><span class="secno">3.3.2.2. </span><span class="content"> Composition of the Technical Architecture Group</span><a class="self-link" href="#tag-participation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑥">TAG</a> consists of:</p>
+    <ul>
+     <li> Tim Berners-Lee, who is a life member; 
+     <li> Three participants <a href="#TAG-appointments">appointed by the Team</a>; 
+     <li> Six participants elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑦">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>. 
+    </ul>
+    <p>Participants in the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑦">TAG</a> choose by consensus their Chair or co-Chairs;
+	in the absence of consensus, the <a data-link-type="dfn" href="#team" id="ref-for-team②⓪">Team</a> appoints the Chair or co-Chairs of the TAG.
+	The Chair or co-Chairs <em class="rfc2119">must</em> be selected from the participants of the TAG.
+	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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②①">Team</a> also appoints a <a href="https://www.w3.org/Guide/teamcontact/role.html">Team Contact</a> <a data-link-type="biblio" href="#biblio-team-contact">[TEAM-CONTACT]</a> for the TAG,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.</p>
+    <p>The terms of TAG participants last for <span class="time-interval">two years</span>.
+	Terms are staggered so that three elected terms
+	and either one or two appointed terms expire each year.
+	If an individual is appointed or elected to fill an incomplete term,
+	that individual’s term ends at the normal expiration date of that term.
+	Regular TAG terms begin on 1 February and end on 31 January.</p>
+    <h5 class="heading settled" data-level="3.3.2.3" id="tag-comm"><span class="secno">3.3.2.3. </span><span class="content"> Communications of the Technical Architecture Group</span><a class="self-link" href="#tag-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②②">Team</a> <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
+    <ul>
+     <li> a public discussion (not just input) list for issues of Web architecture.
+			The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑧">TAG</a> will conduct its public business on this list. 
+     <li> a <a href="#Member-only" id="ref-for-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. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑨">TAG</a> <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" id="ref-for-Member-only①④">Member-only</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⓪">TAG</a> <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 <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①①">TAG</a> <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
+    <h4 class="heading settled" data-level="3.3.3" id="AB-TAG-participation"><span class="secno">3.3.3. </span><span class="content"> Participation in Elected Groups</span><a class="self-link" href="#AB-TAG-participation"></a></h4>
+    <h5 class="heading settled" data-level="3.3.3.1" id="elected-expectations"><span class="secno">3.3.3.1. </span><span class="content"> Expectations for Elected Groups Participants</span><a class="self-link" href="#elected-expectations"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①②">Advisory Board</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①②">TAG</a> participants have a special role within W3C:
+	they are elected by the Membership and appointed by the <a data-link-type="dfn" href="#team" id="ref-for-team②③">Team</a> with the expectation that they will use their best judgment
+	to find the best solutions for the Web,
+	not just for any particular network,
+	technology,
+	vendor,
+	or user.
+	Advisory Board and TAG participants are expected to participate regularly and fully.
+	Advisory Board and TAG participants <em class="rfc2119">should</em> attend <a href="#ACMeetings">Advisory Committee meetings</a>.</p>
+    <p>Individuals elected or appointed to the Advisory Board or TAG act in their personal capacity,
+	to serve the needs of the W3C membership as a whole,
+	and the Web community.
+	Whether they are Member representatives or Invited Experts,
+	their activities in those roles are separate and distinct from their activities on the Advisory Board or TAG.</p>
+    <p>An individual participates on the Advisory Board or TAG
+	from the moment the individual’s term begins until the seat is <a href="#AB-TAG-vacated">vacated</a> (e.g. because the term ends).
+	Although Advisory Board and TAG participants do not advocate for the commercial interests of their employers,
+	their participation does carry the responsibilities associated with Member representation,
+	Invited Expert status,
+	or Team representation
+	(as described in the section on the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>).</p>
+    <p>Participation in the TAG or AB is afforded to the specific individuals elected or appointed to those positions,
+	and a participant’s seat <em class="rfc2119">must not</em> be delegated to any other person.</p>
+    <h5 class="heading settled" data-level="3.3.3.2" id="AB-TAG-constraints"><span class="secno">3.3.3.2. </span><span class="content"> Elected Groups Participation Constraints</span><a class="self-link" href="#AB-TAG-constraints"></a></h5>
+    <p>Given the few seats available on the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①③">Advisory Board</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①③">TAG</a>,
+	and in order to ensure that the diversity of W3C Members is represented:</p>
+    <ul>
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the TAG
+			except when this is caused by a change of affiliation of an existing participant.
+			At the completion of the next regularly scheduled election for the TAG,
+			the organization <em class="rfc2119">must</em> have returned to having at most one seat. 
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation①">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the AB.
+			If, for whatever reason, these constraints are not satisfied
+			(e.g., because an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①④">AB</a> participant changes jobs),
+			one participant <em class="rfc2119">must</em> cease <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑤">AB</a> participation
+			until the situation has been resolved.
+			If after <span class="time-interval">30 days</span> the situation has not been resolved,
+			the Chair will apply
+			the <a href="#random">verifiable random selection procedure</a> described below
+			to choose one person for continued participation and declare the other seat(s) vacant. 
+     <li> An individual <em class="rfc2119">must not</em> participate on both the TAG and the AB. 
+    </ul>
+    <h5 class="heading settled" data-level="3.3.3.3" id="AB-TAG-elections"><span class="secno">3.3.3.3. </span><span class="content"> Advisory Board and Technical Architecture Group Elections</span><a class="self-link" href="#AB-TAG-elections"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑥">Advisory Board</a> and a portion of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①④">Technical Architecture Group</a> are elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑧">Advisory Committee</a>,
+	using a Single Transferable Vote system.
+	An election begins when the Team sends a Call for Nominations to the Advisory Committee.
+	Any Call for Nominations specifies the minimum and maximum number of available seats,
+	the deadline for nominations,
+	details about the specific vote tabulation system selected by the Team for the election,
+	and operational information such as how to nominate a candidate.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②④">Team</a> <em class="rfc2119">may</em> modify the tabulation system after the Call for Nominations
+	but <em class="rfc2119">must</em> stabilize it no later than the Call for Votes.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②⑤">Team</a> announces appointments
+	after the results of the election are known,
+	and before the start of the term,
+	as described in <a href="#TAG-appointments">§ 3.3.3.4 Technical Architecture Group Appointments</a>.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑤">TAG</a>,
+	the minimum and maximum number of available seats are the same:
+	the 3 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑦">AB</a>,
+	the minimum and maximum number of available seats differ:
+	The maximum number is the 5 or 6 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats;
+	the minimum number is such that when added to the occupied seats from the prior year,
+	the minimum size of the AB (9) is reached.</p>
+    <p>Each Member (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member①">related Members</a>) <em class="rfc2119">may</em> nominate one individual.
+	A nomination <em class="rfc2119">must</em> be made with the consent of the nominee.
+	In order for an individual to be nominated as a Member representative,
+	the individual <em class="rfc2119">must</em> qualify for <a href="#member-rep">Member representation</a> and the Member’s <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑧">Advisory Committee representative</a> <em class="rfc2119">must</em> include in the nomination
+	the (same) <a href="#member-rep-info">information required for a Member representative in a Working Group</a>.
+	In order for an individual to be nominated as an Invited Expert,
+	the individual <em class="rfc2119">must</em> provide
+	the (same) <a href="#inv-expert-info" id="ref-for-inv-expert-info">information required for an Invited Expert in a Working Group</a> and the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑨">Advisory Committee representative</a> <em class="rfc2119">must</em> include that information in the nomination.
+	In order for an individual to be nominated as a <a data-link-type="dfn" href="#team" id="ref-for-team②⑥">Team</a> representative,
+	the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⓪">Advisory Committee representative</a> <em class="rfc2119">must</em> first secure approval from <a data-link-type="dfn" href="#team" id="ref-for-team②⑦">Team</a> management.
+	A nominee is <em class="rfc2119">not required</em> to be an employee of a Member organization,
+	and <em class="rfc2119">may</em> be a <a href="#fellows" id="ref-for-fellows①">W3C Fellow</a>.
+	The nomination form <em class="rfc2119">must</em> ask for the nominee’s <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation②">primary affiliation</a>,
+	and this will be reported on the ballot.
+	For most nominees,
+	the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="primary-affiliation">primary affiliation</dfn> is their employer and will match their affiliation in the W3C database.
+	For contractors and invited experts,
+	this will normally be their contracting company
+	or their invited expert status;
+	in some cases
+	(e.g. where a consultant is consulting for only one organization)
+	this <em class="rfc2119">may</em> be the organization for whom the nominee is consulting.
+	A <a href="#AB-TAG-constraints">change of affiliation</a> is defined
+	such that this field would carry a different answer
+	if the nominee were to be re-nominated
+	(therefore,
+	terminating employment,
+	or accepting new employment,
+	are changes of affiliation).
+	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
+	Each nomination <em class="rfc2119">should</em> include
+	a few informative paragraphs about the nominee.</p>
+    <p>If, after the deadline for nominations, the number of nominees is:</p>
+    <ul>
+     <li> Greater than or equal to the minimum number of available seats
+			and less than or equal to the maximum number of available seats,
+			those nominees are thereby elected.
+			This situation constitutes a tie for the purpose of assigning <a href="#short-term">incomplete terms</a>.
+			Furthermore, if the number is less than the maximum number of available seats,
+			the longest terms are filled first. 
+     <li> Less than the minimum number of available seats,
+			Calls for Nominations are issued until a sufficient number of people have been nominated.
+			Those already nominated do not need to be renominated after a renewed call. 
+     <li> Greater than the maximum number of available seats,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team②⑧">Team</a> issues a Call for Votes
+			that includes the names of all candidates,
+			the (maximum) number of available seats,
+			the deadline for votes,
+			details about the vote tabulation system selected by the Team for the election,
+			and operational information. 
+    </ul>
+    <p>When there is a vote,
+	each Member
+	(or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member②">related Members</a>) <em class="rfc2119">may</em> submit one ballot that ranks candidates in the Member’s preferred order.
+	Once the deadline for votes has passed,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team②⑨">Team</a> announces the results to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑨">Advisory Committee</a>.
+	In case of a tie the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to fill the available seats.</p>
+    <p id="short-term">The shortest incomplete term is assigned to the elected candidate ranked lowest by the tabulation of votes,
+	the next shortest term to the next-lowest ranked elected candidate,
+	and so on.
+	In the case of a tie among those eligible for a incomplete term,
+	the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to assign the incomplete term. </p>
+    <p>Refer to <a href="https://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a> <a data-link-type="biblio" href="#biblio-election-howto">[ELECTION-HOWTO]</a> for more details.</p>
+    <h5 class="heading settled" data-level="3.3.3.4" id="TAG-appointments"><span class="secno">3.3.3.4. </span><span class="content"> Technical Architecture Group Appointments</span><a class="self-link" href="#TAG-appointments"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③⓪">Team</a> is responsible for appointing
+	3 of the participants to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑥">Technical Architecture Group</a>.
+	This mechanism complements the election process.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③①">Team</a> <em class="rfc2119">should</em> use its appointments to support
+	a diverse and well-balanced <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑦">TAG</a>,
+	including diversity of technical background, knowledge, and skill sets.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③②">Team</a> <em class="rfc2119">should</em> actively seek
+	candidates for appointment to the TAG,
+	and <em class="rfc2119">must</em> make available to
+	the W3C community at large
+	a means to propose candidates for consideration,
+	explicitly soliciting input from at least
+	current and incoming <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑧">TAG</a> members, the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⓪">Advisory Committee</a>, and <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②">Chairs</a>.</p>
+    <p>The constraints for appointment to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑨">TAG</a> are
+	the same as for elected participants
+	(see <a href="#AB-TAG-constraints">§ 3.3.3.2 Elected Groups Participation Constraints</a> and <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a>),
+	with the additional constraint that
+	a person <em class="rfc2119">must not</em> be appointed
+	for more than two <em>consecutive</em> terms.
+	(Partial terms used to fill a vacated seat do not count towards this limit.)</p>
+    <p class="note" role="note"><span>Note:</span> Individuals who have reached the limit of two consecutive appointed terms <em class="rfc2119">may</em> freely run for election
+	if they wish to continue serving on the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⓪">TAG</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③③">Team</a>'s choice of appointee(s)
+	is subject to ratification by secret ballot
+	by both the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑧">AB</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②①">TAG</a>,
+	each requiring a two-thirds approval.
+	In the case of regularly scheduled elections,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②②">TAG</a> participants in this ratification are
+	its members for the upcoming term.</p>
+    <p>For regularly scheduled elections,
+	selection begins once the results of the elections are known,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team③④">Team</a> <em class="rfc2119">should</em> announce the ratified appointment(s)
+	no later than the start of the regularly scheduled term.
+	When an appointed seat is vacated outside of a regularly scheduled election,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⑤">Team</a> <em class="rfc2119">should</em> seek to appoint a replacement
+	unless a regular Call for Nominations is scheduled within 2 months,
+	and it <em class="rfc2119">must</em> announce the ratified appointment
+	no later than the Call for Nominations of the next scheduled election.</p>
+    <h5 class="heading settled" data-level="3.3.3.5" id="random"><span class="secno">3.3.3.5. </span><span class="content"> Verifiable Random Selection Procedure</span><a class="self-link" href="#random"></a></h5>
+    <p>When it is necessary to use a verifiable random selection process
+	(e.g., in an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑨">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②③">TAG</a> election,
+	to “draw straws” in case of a tie
+	or to fill a incomplete term),
+	W3C uses the random and verifiable procedure defined in <a href="https://www.ietf.org/rfc/rfc3797.txt">RFC 3797</a> <a data-link-type="biblio" href="#biblio-rfc3797">[RFC3797]</a>.
+	The procedure orders an input list of names
+	(listed in alphabetical order by family name unless otherwise specified)
+	into a “result order”.</p>
+    <p>W3C applies this procedure as follows:</p>
+    <p></p>
+    <ol>
+     <li> When N people have tied for M (less than N) seats.
+			In this case, only the names of the N individuals who tied
+			are provided as input to the procedure.
+			The M seats are assigned in result order. 
+     <li> After all elected individuals have been identified,
+			when N people are eligible for M (less than N) incomplete terms.
+			In this case, only the names of those N individuals are provided as input to the procedure.
+			The incomplete terms are assigned in result order. 
+    </ol>
+    <h5 class="heading settled" data-level="3.3.3.6" id="AB-TAG-vacated"><span class="secno">3.3.3.6. </span><span class="content"> Elected Groups Vacated Seats</span><a class="self-link" href="#AB-TAG-vacated"></a></h5>
+    <p>An <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⓪">Advisory Board</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②④">TAG</a> participant’s seat is vacated when:</p>
+    <ul>
+     <li> the participant resigns, or 
+     <li> an Advisory Board or TAG participant changes affiliations
+			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
+			or 
+     <li> the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo④">CEO</a> dismisses the participant
+			for failing to meet the criteria in section <a href="#ParticipationCriteria">§ 3.1.1 Individual Participation Criteria</a>,
+			or 
+     <li> their term ends. 
+    </ul>
+    <p>If a participant changes affiliation,
+	but the <a href="#AB-TAG-constraints">participation constraints</a> are met,
+	that participant’s seat becomes vacant at the next regularly scheduled election for that group.</p>
+    <p>Vacated seats are filled according to this schedule:</p>
+    <ul>
+     <li> When an appointed <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑤">TAG</a> seat is vacated,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team③⑥">Team</a> <a href="#TAG-appointments">appoints</a> a replacement. 
+     <li>
+       When an elected seat on either the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②①">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑥">TAG</a> is vacated,
+			the seat is filled at the next regularly scheduled election for the group
+			unless the group Chair requests that W3C hold an election before then
+			(for instance, due to the group’s workload). 
+      <ul>
+       <li> The group Chair <em class="rfc2119">should not</em> request such an election
+					if the next regularly scheduled election is fewer than three months away. 
+       <li> The group Chair <em class="rfc2119">may</em> request an election,
+					and the election may begin, as soon as a current member gives notice of a resignation,
+					including a resignation effective as of a given date in the future. 
+      </ul>
+      <p>When such an election is held,
+			the minimum number of available seats is such that
+			when added to the number of continuing participants,
+			the minimum total number of elected seats is met
+			(6 for the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑦">TAG</a>, 9 for the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②②">AB</a>);
+			and the maximum number corresponds to all unoccupied seats.
+			Except for the number of available seats and the length of the terms,
+			the <a href="#AB-TAG-elections">usual rules for Advisory Board and Technical Architecture Group Elections</a> apply.</p>
+    </ul>
+    <h3 class="heading settled" data-level="3.4" id="GAGeneral"><span class="secno">3.4. </span><span class="content"> Chartered Groups: Working Groups and Interest Groups</span><span id="ChapterGroups"></span><span id="WG-and-IG"></span><a class="self-link" href="#GAGeneral"></a></h3>
+    <p id="GAGroups">This document defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chartered-group">chartered groups</dfn>: </p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsWG"><a href="#GroupsWG" id="ref-for-GroupsWG⑨③">Working Groups</a></dfn>. 
+     <dd>
+       Working Groups typically produce deliverables
+			(e.g., <a href="#rec-advance">Recommendation Track technical reports</a>,
+			software,
+			test suites,
+			and reviews of the deliverables of other groups)
+			as defined in their <a href="#WGCharter">charter</a>. 
+      <p>Working Groups have additional participation requirements
+			described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>,
+			see particularly the “<a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Obligations">Licensing Obligations of Working Group Participants</a>”
+			and the patent claim exclusion process
+			in “<a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">Exclusion From W3C RF Licensing Requirements</a>”.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsIG"><a href="#GroupsIG" id="ref-for-GroupsIG①①">Interest Groups</a></dfn>. 
+     <dd>
+       The primary goal of an Interest Group
+			is to bring together people who wish to evaluate potential Web technologies and policies.
+			An Interest Group is a forum for the exchange of ideas. 
+      <p>Interest Groups do not publish <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑥">Recommendation Track technical reports</a>;
+			but can publish <a href="#WGNote" id="ref-for-WGNote">technical reports on the Note Track</a>.</p>
+    </dl>
+    <h4 class="heading settled" data-level="3.4.1" id="ReqsAllGroups"><span class="secno">3.4.1. </span><span class="content"> Requirements for All Chartered Groups</span><a class="self-link" href="#ReqsAllGroups"></a></h4>
+    <p>Each group <em class="rfc2119">must</em> have a <a data-link-type="dfn" href="#charter" id="ref-for-charter">charter</a>.
+	Requirements for the charter depend on the group type.
+	All group charters <em class="rfc2119">must</em> be public
+	(even if other proceedings of the group are <a href="#Member-only" id="ref-for-Member-only①⑤">Member-only</a>).</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GeneralChairs">Chair</dfn> (or co-Chairs)
+	to coordinate the group’s tasks.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③⑦">Team</a> appoints (and re-appoints) Chairs for all groups.
+	The Chair is a <a href="#member-rep">Member representative</a>,
+	a <a href="#Team">Team representative</a>,
+	or an <a href="#invited-expert-wg">Invited Expert</a>,
+	(invited by the <a data-link-type="dfn" href="#team" id="ref-for-team③⑧">Team</a>).
+	The requirements of this document that apply to those types of participants apply to Chairs as well.</p>
+    <p class="note" role="note"><span>Note:</span> The <a href="https://www.w3.org/Guide/chair/role.html">role of the Chair</a> <a data-link-type="biblio" href="#biblio-chair">[CHAIR]</a> is described
+	in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide">[GUIDE]</a>.</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="TeamContact">Team Contact</dfn>,
+	who acts as the interface between the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③">Chair</a>,
+	group participants,
+	and the rest of the Team.</p>
+    <p class="note" role="note"><span>Note:</span> The <a href="https://www.w3.org/Guide/teamcontact/role.html">role of the Team Contact</a> <a data-link-type="biblio" href="#biblio-team-contact">[TEAM-CONTACT]</a> is described in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide">[GUIDE]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs④">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact">Team Contact</a> of a group <em class="rfc2119">should not</em> be the same individual.</p>
+    <p>Each group <em class="rfc2119">must</em> have an archived mailing list
+	for formal group communication
+	(e.g., for meeting announcements and <a data-link-type="dfn" href="#minutes" id="ref-for-minutes①">minutes</a>,
+	documentation of decisions,
+	and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②">Formal Objections</a> to decisions).
+	It is the responsibility of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑤">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①">Team Contact</a> to ensure that new participants are subscribed to all relevant mailing lists.
+	Refer to the list of <a href="https://www.w3.org/groups/">group mailing lists</a> <a data-link-type="biblio" href="#biblio-group-mail">[GROUP-MAIL]</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑥">Chair</a> <em class="rfc2119">may</em> form task forces
+	(composed of group participants)
+	to carry out assignments for the group.
+	The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group’s charter.
+	A group <em class="rfc2119">should</em> document the process it uses
+	to create task forces
+	(e.g., each task force might have an informal "charter").
+	Task forces do not publish <a href="#Reports">technical reports</a>;
+	the Working Group <em class="rfc2119">may</em> choose to publish their results as part of a technical report. </p>
+    <h4 class="heading settled" data-level="3.4.2" id="group-participation"><span class="secno">3.4.2. </span><span class="content"> Participation in Chartered Groups</span><a class="self-link" href="#group-participation"></a></h4>
+    <p>There are three types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="wgparticipant">participants in a Working Group</dfn>: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
+	and <a href="#Team">Team representatives</a> (including the <a href="#TeamContact" id="ref-for-TeamContact⑦">Team Contact</a>).</p>
+    <p>There are four types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="igparticipant">participants in an Interest Group</dfn>:
+	the same three types as for Working Groups plus,
+	for an Interest Group where the only <a href="#ig-mail-only">participation requirement is mailing list subscription</a>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="public-participant-ig">public participants</dfn>.</p>
+    <p>Except where noted in this document or in a group charter,
+	all participants share the same rights and responsibilities in a group;
+	see also the <a href="#ParticipationCriteria">individual participation criteria</a>.</p>
+    <p>A participant <em class="rfc2119">may</em> represent more than one organization
+	in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①">Interest Group</a>.
+	Those organizations <em class="rfc2119">must</em> all be members of the group.</p>
+    <p>An individual <em class="rfc2119">may</em> become
+	a Working or Interest Group participant
+	at any time during the group’s existence.
+	See also relevant requirements in
+	“Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <p>On an exceptional basis,
+	a Working or Interest Group participant <em class="rfc2119">may</em> designate
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mtg-substitute">substitute</dfn> to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑦">Chair</a>.
+	The substitute <em class="rfc2119">may</em> act on behalf of the participant,
+	including for <a href="#Votes">votes</a>.
+	For the substitute to vote,
+	the participant <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑧">Chair</a> in writing in advance.
+	As a courtesy to the group,
+	if the substitute is not well-versed in the group’s discussions,
+	the regular participant <em class="rfc2119">should</em> authorize another participant to act as <a href="#proxy" id="ref-for-proxy">proxy</a> for votes.</p>
+    <p>To allow rapid progress,
+	Working Groups are intended to be small
+	(typically fewer than 15 people)
+	and composed of experts in the area defined by the charter.
+	In principle,
+	Interest Groups have no limit on the number of participants.
+	When a Working Group grows too large to be effective,
+	W3C <em class="rfc2119">may</em> split it into an Interest Group
+	(a discussion forum)
+	and a much smaller Working Group
+	(a core group of highly dedicated participants).</p>
+    <h4 class="heading settled" data-level="3.4.3" id="chartered-group-participants"><span class="secno">3.4.3. </span><span class="content"> Types of Participants in Chartered Groups</span><a class="self-link" href="#chartered-group-participants"></a></h4>
+    <h5 class="heading settled" data-level="3.4.3.1" id="member-rep-wg"><span class="secno">3.4.3.1. </span><span class="content"> Member Representative in a Working Group</span><a class="self-link" href="#member-rep-wg"></a></h5>
+    <p>An individual is a <dfn data-dfn-type="dfn" data-export id="member-representative-in-a-working-group">Member representative in a Working Group<a class="self-link" href="#member-representative-in-a-working-group"></a></dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Advisory Committee representative of the Member in question
+			has designated the individual as a Working Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a Member representative in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤">Working Group</a>,
+	an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①①">Advisory Committee representative</a> <em class="rfc2119">must</em> provide the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑨">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact②">Team Contact</a> with all of the following <span id="member-rep-info">information</span>,
+	in addition to any other information required by the <a href="#cfp">Call for Participation</a> and charter
+	(including the participation requirements of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>):</p>
+    <ol>
+     <li> The name of the W3C Member the individual represents
+			and whether the individual is an employee of that Member organization; 
+     <li> A statement that the individual accepts the participation terms
+			set forth in the charter
+			(with an indication of charter date or version); 
+     <li> A statement that the Member will provide the necessary financial support for participation
+			(e.g., for travel, telephone calls, and conferences). 
+    </ol>
+    <p>A Member participates in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥">Working Group</a> from the moment the first Member representative joins the group
+	until either of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Member <a href="#resignation">resigns</a> from the Working Group;
+			this is done through the Member’s Advisory Committee representative. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.2" id="member-rep-ig"><span class="secno">3.4.3.2. </span><span class="content"> Member Representative in an Interest Group</span><a class="self-link" href="#member-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-an-interest-group">Member representative in an Interest Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①②">Advisory Committee representative</a> of the Member in question has designated the individual
+			as an Interest Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a <a data-link-type="dfn" href="#member-representative-in-an-interest-group" id="ref-for-member-representative-in-an-interest-group">Member representative in an Interest Group</a>,
+	the Advisory Committee representative <em class="rfc2119">must</em> follow the instructions
+	in the <a href="#cfp">Call for Participation</a> and charter.</p>
+    <p>Member participation in an Interest Group ceases under the same conditions as for a Working Group.</p>
+    <h5 class="heading settled" data-level="3.4.3.3" id="invited-expert-wg"><span class="secno">3.4.3.3. </span><span class="content"> Invited Expert in a Working Group</span><a class="self-link" href="#invited-expert-wg"></a></h5>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⓪">Chair</a> <em class="rfc2119">may</em> invite an individual with a particular expertise
+	to participate in a Working Group.
+	This individual <em class="rfc2119">may</em> represent an organization in the group
+	(e.g., if acting as a liaison with another organization).</p>
+    <p>An individual is an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-a-working-group">Invited Expert in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Chair has designated the individual as a group participant, 
+     <li> the Team Contact has agreed with the Chair’s choice, and 
+     <li> the individual has provided the <a href="#inv-expert-info" id="ref-for-inv-expert-info①">information required of an Invited Expert</a> to the Chair and Team Contact. 
+    </ul>
+    <p>To designate an individual as an Invited Expert in a Working Group,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①①">Chair</a> <em class="rfc2119">must</em> inform the Team Contact
+	and provide rationale for the choice.
+	When the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①②">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact③">Team Contact</a> disagree about a designation,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑤">CEO</a> determines
+	whether the individual will be invited to participate in the Working Group.</p>
+    <p>To <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="inv-expert-info">participate in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦">Working Group</a> as an Invited Expert</dfn>,
+	an individual <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> identify the organization, if any, the individual represents as a participant in this group, 
+     <li> agree to the terms of the <a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">invited expert and collaborators agreement</a> <a data-link-type="biblio" href="#biblio-collaborators-agreement">[COLLABORATORS-AGREEMENT]</a>, 
+     <li> accept the participation terms set forth in the charter,
+			including the participation requirements of
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>,
+			especially in “Note on Licensing Commitments for Invited Experts”
+			and in “Disclosure”,
+			indicating a specific charter date or version, 
+     <li> disclose whether the individual is an employee of a W3C Member;
+			see the <a href="#coi">conflict of interest policy</a>, 
+     <li> provide a statement of who will provide the necessary financial support
+			for the individual’s participation
+			(e.g., for travel, telephone calls, and conferences), and 
+     <li> if the individual’s employer (including a self-employed individual)
+			or the organization the individual represents
+			is not a W3C Member,
+			indicate whether that organization intends to join W3C.
+			If the organization does not intend to join W3C,
+			indicate reasons the individual is aware of for this choice. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①③">Chair</a> <em class="rfc2119">should not</em> designate as an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group">Invited Expert in a Working Group</a> an individual who is an employee of a W3C Member.
+	The Chair <em class="rfc2119">must not</em> use Invited Expert status
+	to circumvent participation limits imposed by the <a href="#WGCharter">charter</a>.</p>
+    <p>An Invited Expert participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Chair or <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑥">CEO</a> withdraws the invitation to participate, or 
+     <li> the individual <a href="#resignation">resigns</a>. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.4" id="invited-expert-ig"><span class="secno">3.4.3.4. </span><span class="content"> Invited Expert in an Interest Group</span><a class="self-link" href="#invited-expert-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	the participation requirements for an <dfn data-dfn-type="dfn" data-export id="invited-expert-in-an-interest-group">Invited Expert in an Interest Group<a class="self-link" href="#invited-expert-in-an-interest-group"></a></dfn> are the same as those for an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group①">Invited Expert in a Working Group</a>.</p>
+    <h5 class="heading settled" data-level="3.4.3.5" id="team-rep-wg"><span class="secno">3.4.3.5. </span><span class="content"> Team Representative in a Working Group</span><a class="self-link" href="#team-rep-wg"></a></h5>
+    <p>An individual is a <dfn data-dfn-type="dfn" data-export id="team-representative-in-a-working-group">Team representative in a Working Group<a class="self-link" href="#team-representative-in-a-working-group"></a></dfn> when so designated by W3C management.
+	Team representatives both contribute to the technical work
+	and help ensure the group’s proper integration with the rest of W3C.</p>
+    <p>A Team representative participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> W3C management changes Team representation by sending email to the Chair,
+			copying the group mailing list. 
+    </ul>
+    <p>The Team participates in a Working Group
+	from the moment the creation of the group is announced
+	until the group closes.</p>
+    <h5 class="heading settled" data-level="3.4.3.6" id="team-rep-ig"><span class="secno">3.4.3.6. </span><span class="content"> Team Representative in an Interest Group</span><a class="self-link" href="#team-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn data-dfn-type="dfn" data-export id="team-representative-in-an-interest-group">Team representative in an Interest Group<a class="self-link" href="#team-representative-in-an-interest-group"></a></dfn> when so designated by W3C management.</p>
+    <h2 class="heading settled" data-level="4" id="group-lifecyle"><span class="secno">4. </span><span class="content"> Lifecycle of Chartered Groups</span><a class="self-link" href="#group-lifecyle"></a></h2>
+    <h3 class="heading settled" data-level="4.1" id="WGCharterDevelopment"><span class="secno">4.1. </span><span class="content"> Initiating Charter Development</span><a class="self-link" href="#WGCharterDevelopment"></a></h3>
+    <p>W3C creates charters for <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group">chartered groups</a> based on interest from the Members and Team.
+	The Team <em class="rfc2119">must</em> notify the Advisory Committee
+	when a charter for a new Working Group or Interest Group is in development.
+	This is intended to raise awareness,
+	even if no formal proposal is yet available.
+	Advisory Committee representatives <em class="rfc2119">may</em> provide
+	feedback on the <a href="#ACCommunication">Advisory Committee discussion list</a> or via other designated channels.</p>
+    <p>W3C <em class="rfc2119">may</em> begin work
+	on a Working Group or Interest Group charter
+	at any time.</p>
+    <h3 class="heading settled" data-level="4.2" id="WGCharter"><span class="secno">4.2. </span><span class="content"> Content of a Charter</span><a class="self-link" href="#WGCharter"></a></h3>
+    <p>A Working Group or Interest Group <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="charter">charter</dfn> <em class="rfc2119">must</em> include all of the following information.</p>
+    <ul>
+     <li> The group’s mission
+			(e.g., develop a technology or process, review the work of other groups). 
+     <li> The scope of the group’s work and criteria for success. 
+     <li> The duration of the group (typically from six months to two years). 
+     <li> The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software). 
+     <li>
+       Expected milestone dates where available. 
+      <p class="note" role="note"><span>Note:</span> A charter is <em class="rfc2119">not required</em> to include schedules for review of other group’s deliverables.</p>
+     <li> The process for the group to approve the release of deliverables
+			(including intermediate results). 
+     <li> Any dependencies by groups within or outside of W3C on the deliverables of this group.
+			For any dependencies, the charter <em class="rfc2119">must</em> specify
+			the mechanisms for communication about the deliverables. 
+     <li> Any dependencies of this group on other groups within or outside of W3C.
+			Such dependencies include interactions with <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter">[CHARTER]</a>. 
+     <li> The <a href="#confidentiality-levels">level of confidentiality</a> of the group’s proceedings and deliverables. 
+     <li> Meeting mechanisms and expected frequency. 
+     <li> If known,
+			the date of the first <a href="#ftf-meeting" id="ref-for-ftf-meeting①">face-to-face meeting</a>.
+			The date of the first face-to-face meeting of a proposed group <em class="rfc2119">must not</em> be sooner than <span class="time-interval">eight weeks</span> after the date of the proposal. 
+     <li> Communication mechanisms to be employed within the group,
+			between the group and the rest of W3C,
+			and with the general public. 
+     <li> Any voting procedures or requirements
+			other than those specified in <a href="#Votes">§ 5.2.3 Deciding by Vote</a>. 
+     <li> An estimate of the expected time commitment from participants. 
+     <li> The expected time commitment and level of involvement by the Team
+			(e.g., to track developments,
+			write and edit technical reports,
+			develop code,
+			or organize pilot experiments). 
+     <li> Intellectual property information.
+			What are the intellectual property (including patents and copyright)
+			considerations affecting the success of the Group?
+			In particular, is there any reason to believe
+			that it will be difficult to meet the Royalty-Free licensing goals
+			in “Licensing Goals for W3C Specifications”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>? 
+    </ul>
+    <p>See also the charter requirements in “Licensing Goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <p>For every Recommendation Track deliverable
+	that continues work on <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report">technical report</a> published under any other Charter (including a predecessor group of the same name),
+	for which there is at least an existing <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd">First Public Working Draft</a> the description of that deliverable in the proposed charter of the adopting Working Group <em class="rfc2119">must</em> provide the following information:</p>
+    <ul>
+     <li> The title,
+			stable URL,
+			and publication date of the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD">Working Draft</a> or other Recommendation-track document
+			that will serve as the basis for work on the deliverable
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="adopted-draft">Adopted Draft</dfn>”); 
+     <li> The title,
+			stable URL,
+			and publication date of the document
+			that was used as the basis for its most recent Exclusion Opportunity
+			as per
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft">Exclusion Draft</dfn>”); and 
+     <li> The stable URL of the Working Group charter
+			under which the Exclusion Draft was published
+			(labeled the “<dfn data-dfn-type="dfn" data-export id="exclusion-draft-charter">Exclusion Draft Charter<span id="other-charter"></span><a class="self-link" href="#exclusion-draft-charter"></a></dfn>”). 
+    </ul>
+    <p>All of the above data <em class="rfc2119">must</em> be identified
+	in the adopting Working Group’s charter using the labels indicated.</p>
+    <p>The <a data-link-type="dfn" href="#adopted-draft" id="ref-for-adopted-draft">Adopted Draft</a> and the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft">Exclusion Draft</a> <em class="rfc2119">must</em> each be adopted in their entirety and without any modification.
+	The proposed charter <em class="rfc2119">must</em> state
+	the dates on which the Exclusion Opportunity
+	that arose on publishing the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft①">Exclusion Draft</a> began and ended.
+	As per “Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>,
+	this potentially means that exclusions can only be made immediately on joining a Working Group.</p>
+    <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding participation,
+	including specifying
+	that the <span id="ig-mail-only">only requirement for participation (by anyone) in
+	the Interest Group is subscription to the Interest Group mailing list</span>.
+	This type of Interest Group <em class="rfc2119">may</em> have <a href="#public-participant-ig" id="ref-for-public-participant-ig">public participants</a>. </p>
+    <p>A charter <em class="rfc2119">may</em> include
+	provisions other than those required by this document.
+	The charter <em class="rfc2119">should</em> highlight
+	whether additional provisions impose constraints
+	beyond those of the W3C 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>
+    <h3 class="heading settled" data-level="4.3" id="CharterReview"><span class="secno">4.3. </span><span class="content"> Advisory Committee Review of a Charter</span><a class="self-link" href="#CharterReview"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③⑨">Team</a> <em class="rfc2119">must</em> solicit <a href="#ACReview">Advisory Committee review</a> of every new or substantively modified Working Group or Interest Group charter,
+	except for either:</p>
+    <ul>
+     <li data-md>
+      <p>a charter extension</p>
+     <li data-md>
+      <p>substantive changes to a charter that do not affect the way the group functions in any significant way.</p>
+    </ul>
+    <p>The review period <em class="rfc2119">must</em> be at least 28 days.
+	The following are examples of substantive changes that would not require an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review">Advisory Committee Review</a>:
+	the addition of an in-scope deliverable,
+	a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact④">Team Contact</a>,
+	or a change of <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①④">Chair</a>.
+	Such changes must nonetheless be announced
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①①">Advisory Committee</a> and to <a href="#wgparticipant" id="ref-for-wgparticipant①"> participants in the Working</a> or <a href="#igparticipant" id="ref-for-igparticipant①">in the Interest Group</a>,
+	and a rationale must be provided.</p>
+    <p>The Call for Review of a substantively modified charter <em class="rfc2119">must</em> highlight important changes
+	(e.g., regarding deliverables or resource allocation)
+	and include rationale for the changes.</p>
+    <p>As part of the Advisory Committee review of any new or substantively modified Working Group charter,
+	any Advisory Committee representative <em class="rfc2119">may</em> request an extended review period.</p>
+    <p>Such a request must be submitted with a Member’s comments
+	in response to the Call for Review.
+	Upon receipt of any such request,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④⓪">Team</a> <em class="rfc2119">must</em> ensure
+	that the Call for Participation for the Working Group
+	occurs at least 60 days
+	after the Call for Review of the charter.</p>
+    <h3 class="heading settled" data-level="4.4" id="cfp"><span class="secno">4.4. </span><span class="content"> Call for Participation in a Chartered Group</span><a class="self-link" href="#cfp"></a></h3>
+    <p>Deciding whether to adopt a proposed <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG②">Interest Group</a> <a data-link-type="dfn" href="#charter" id="ref-for-charter①">charter</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①">W3C Decision</a>.
+	Charters <em class="rfc2119">may</em> be amended based on review comments
+	per <a href="#ACReviewAfter">§ 5.7.2 After the Review Period</a> before the Call for Participation.</p>
+    <p>If the decision is to charter the group,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④①">Team</a> <em class="rfc2119">must</em> issue a Call for Participation to the Advisory Committee.
+	For a new group, this announcement officially creates the group.
+	The announcement <em class="rfc2119">must</em> include a reference to the <a href="#WGCharter">charter</a>,
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑤">Chair</a>(s),
+	and the name(s) of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑤">Team Contact</a>(s).</p>
+    <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).
+	When a group is re-chartered,
+	individuals participating in the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG③">Interest Group</a> before the new Call for Participation
+	may attend any meetings held within forty-five (45) days of the Call for Participation
+	even if they have not yet formally rejoined the group
+	(i.e., committed to the terms of the charter and patent policy).</p>
+    <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against the decision to create
+	or substantially modify
+	a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.5" id="charter-extension"><span class="secno">4.5. </span><span class="content"> Charter Extension</span><a class="self-link" href="#charter-extension"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④②">Team</a> <em class="rfc2119">may</em> decide
+	to extend a Working Group or Interest Group charter
+	with no other substantive modifications.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team④③">Team</a> <em class="rfc2119">must</em> announce
+	such <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="charter extension" id="dfn-charter-extension">extensions</dfn> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①②">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate the new duration.
+	The announcement <em class="rfc2119">must</em> also include rationale for the extension,
+	a reference to the <a href="#WGCharter">charter</a>,
+	and the Group homepage
+	(which includes at least
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑥">Chair</a>(s),
+	the name of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑥">Team Contact</a>,
+	and instructions for joining the group).</p>
+    <p>After a charter extension,
+	Advisory Committee representatives
+	and the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑦">Chair</a> 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> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①">Team decision</a> regarding the extension of a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.6" id="GeneralTermination"><span class="secno">4.6. </span><span class="content"> Chartered Group Closure</span><a class="self-link" href="#GeneralTermination"></a></h3>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⓪">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG④">Interest Group</a> charter specifies a duration for the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④④">Team</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑧">TAG</a>, or the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②③">AB</a> <em class="rfc2119">may</em> propose to close a group
+	prior to the date specified in the charter in any of the following circumstances:</p>
+    <ul>
+     <li data-md>
+      <p>There are insufficient member resources to produce chartered deliverables
+or to maintain the group,
+according to priorities established within W3C.</p>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="https://www.w3.org/Consortium/Patent-Policy/#patent-advisory-group" id="ref-for-patent-advisory-group">Patent Advisory Group</a> concluded that the work <em class="rfc2119">should</em> be terminated.</p>
+     <li data-md>
+      <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑨">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②④">AB</a> determined that continuing operation of the chartered group or its work
+would be detrimental to W3C or its mission.</p>
+     <li data-md>
+      <p>The group produced all chartered deliverables ahead of schedule.</p>
+    </ul>
+    <p>Such a proposal to close a group must be accompanied by rationale,
+	and the proposal must be confirmed by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision②">W3C Decision</a>.</p>
+    <p>Closing a Working Group has implications
+	with respect to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <h2 class="heading settled" data-level="5" id="decisions"><span class="secno">5. </span><span class="content"> Decisions</span><a class="self-link" href="#decisions"></a></h2>
+    <p>W3C attempts to resolve issues through dialog.
+	Individuals who disagree strongly with a decision <em class="rfc2119">should</em> register with the Chair any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③">Formal Objections</a>.</p>
+    <h3 class="heading settled" data-level="5.1" id="decision-types"><span class="secno">5.1. </span><span class="content"> Types of Decisions</span><a class="self-link" href="#decision-types"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑧">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①①">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑤">Interest Group</a> has the prerogative
+	to make certain decisions based on their own judgment.
+	Such decisions are called <dfn data-dfn-type="dfn" data-export id="chair-decisions">chair decisions<a class="self-link" href="#chair-decisions"></a></dfn>.</p>
+    <p>In contrast,
+	decisions taken by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑨">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①②">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑥">Interest Group</a> on the basis of having assessed the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus">consensus</a> of the group
+	or following a vote (see <a href="#Votes">§ 5.2.3 Deciding by Vote</a>)
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="group decision | resolution" id="group-decision">group decisions</dfn> (also known as group “resolutions”).</p>
+    <p>Decisions made by members of the <a data-link-type="dfn" href="#team" id="ref-for-team④⑤">Team</a> in connection with this Process,
+	based on their own individual or collective judgement,
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Team Decision | Team’s Decision" data-noexport id="team-decision">Team Decisions</dfn>.</p>
+    <p>In contrast,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-w3c-decision">W3C decision</dfn> is
+	determined by the <a data-link-type="dfn" href="#team" id="ref-for-team④⑥">Team</a> on behalf of the W3C community
+	by assessing the consensus of the W3C Community after an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②">Advisory Committee review</a>.</p>
+    <h3 class="heading settled" data-level="5.2" id="consensus-building"><span class="secno">5.2. </span><span class="content"> Consensus Building</span><a class="self-link" href="#consensus-building"></a></h3>
+    <h4 class="heading settled" data-level="5.2.1" id="Consensus"><span class="secno">5.2.1. </span><span class="content"> Consensus</span><a class="self-link" href="#Consensus"></a></h4>
+    <p>Consensus is a core value of W3C.
+	To promote consensus,
+	the W3C process requires Chairs to ensure
+	that groups consider all legitimate views and objections,
+	and endeavor to resolve them,
+	whether these views and objections are expressed by the active participants of the group
+	or by others
+	(e.g., another W3C group,
+	a group in another organization,
+	or the general public).
+	Decisions <em class="rfc2119">may</em> be made during meetings
+	(<a href="#ftf-meeting" id="ref-for-ftf-meeting②">face-to-face</a> or <a href="#distributed-meeting" id="ref-for-distributed-meeting">distributed</a>)
+	as well as through <a href="#discussion-archiving">persistent text-based discussions</a>.</p>
+    <p class="note" role="note"><span>Note:</span> The CEO has the role of
+	assessing consensus within the Advisory Committee.</p>
+    <p>The following terms are used in this document
+	to describe the level of support for a decision among a set of eligible individuals:</p>
+    <dl>
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Consensus">Consensus</dfn>: 
+     <dd> A substantial number of individuals in the set
+			support the decision
+			and there is no sustained objection from anybody in the set.
+			Individuals in the set <em class="rfc2119">may</em> abstain.
+			Abstention is either an explicit expression of no opinion
+			or silence by an individual in the set. 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Unanimity">Unanimity</dfn>: 
+     <dd> The particular case of <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①">consensus</a> where all individuals in the set support the decision
+			(i.e., no individual in the set abstains). 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Dissent">Dissent</dfn>: 
+     <dd> At least one individual in the set sustains an objection. 
+    </dl>
+    <p class="note" role="note"><span>Note:</span> A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④">Formal Objection</a> always indicates a sustained objection,
+	but isn’t necessary to express it
+	(except in the context of formal <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③">AC Reviews</a>).
+	Disagreement with a proposed decision,
+	however, does not always rise to the level of sustained objection,
+	as individuals could be willing to accept a decision
+	while expressing disagreement.</p>
+    <p>By default, the set of individuals eligible to participate in a decision is the set of group participants.
+	The Process Document does not require a quorum for decisions
+	(i.e., the minimal number of eligible participants required to be present before the Chair can call a question).
+	A charter <em class="rfc2119">may</em> include a quorum requirement for consensus decisions.</p>
+    <p>Where <a data-link-type="dfn" href="#def-Unanimity" id="ref-for-def-Unanimity">unanimity</a> is not possible,
+	a group <em class="rfc2119">should</em> strive to make <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②">consensus</a> decisions
+	where there is significant support and few abstentions.
+	The Process Document does not require a particular percentage of eligible participants
+	to agree to a motion in order for a decision to be made.
+	To avoid decisions where there is widespread apathy,
+	(i.e., little support and many abstentions),
+	groups <em class="rfc2119">should</em> set minimum thresholds of active support before a decision can be recorded.
+	The appropriate percentage <em class="rfc2119">may</em> vary depending on the size of the group
+	and the nature of the decision.
+	A charter <em class="rfc2119">may</em> include threshold requirements for consensus decisions.
+	For instance, a charter might require a supermajority of eligible participants
+	(i.e., some established percentage above 50%)
+	to support certain types of consensus decisions.</p>
+    <div class="note" role="note">
+      Note: Chairs have substantial flexibility
+	in how they obtain and assess consensus among their groups.
+	Unless otherwise constrained by charter,
+	they may use modes including but not limited to explicit calls for consensus,
+	polls of participants,
+	“lazy consensus” in which lack of objection after sufficient notice is taken as assent;
+	or they may also delegate and empower a document editor
+	to assess consensus on their behalf,
+	whether in general
+	or for specific pre-determined circumstances
+	(e.g. in non-controversial situations, for specific types of issues, etc.). 
+     <p>If questions or disagreements arise,
+	the final determination of consensus remains with the chair.</p>
+    </div>
+    <h4 class="heading settled" data-level="5.2.2" id="managing-dissent"><span class="secno">5.2.2. </span><span class="content"> Managing Dissent</span><a class="self-link" href="#managing-dissent"></a></h4>
+    <p>In some cases, even after careful consideration of all points of view,
+	a group might find itself unable to reach consensus.
+	The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⓪">Chair</a> <em class="rfc2119">may</em> record a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent">dissent</a> so that the group can make progress
+	(for example, to produce a deliverable in a timely manner).
+	Dissenters cannot stop a group’s work
+	simply by saying that they cannot live with a decision.
+	When the Chair believes that the Group has duly considered
+	the legitimate concerns of dissenters as far as is possible and reasonable,
+	the group <em class="rfc2119">should</em> move on.</p>
+    <p>Groups <em class="rfc2119">should</em> favor proposals that create the weakest objections.
+	This is preferred over proposals that are supported by a large majority
+	but that cause strong objections from a few people.
+	As part of making a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent①">dissent</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②①">Chair</a> is expected to be aware of which participants work for the same
+	(or <a href="#MemberRelated">related</a>)
+	Member organizations and weigh their input accordingly.</p>
+    <p class="note" role="note"><span>Note:</span> Dissenters can escalate their sustained objection to a decision by registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑤">Formal Objection</a>.</p>
+    <h4 class="heading settled" data-level="5.2.3" id="Votes"><span class="secno">5.2.3. </span><span class="content"> Deciding by Vote</span><a class="self-link" href="#Votes"></a></h4>
+    <p>A group <em class="rfc2119">should</em> only conduct a vote to resolve a <em>substantive issue</em> after the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②②">Chair</a> has determined that all available means of <a href="#Consensus">reaching consensus</a> through technical discussion and compromise have failed,
+	and that a vote is necessary to break a deadlock.
+	In this case the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②③">Chair</a> <em class="rfc2119">must</em> record
+	(e.g., in the <a data-link-type="dfn" href="#minutes" id="ref-for-minutes②">minutes</a> of the meeting or in an archived email message):</p>
+    <ul>
+     <li> an explanation of the issue being voted on; 
+     <li> the decision to conduct a vote
+			(e.g., a simple majority vote) to resolve the issue; 
+     <li> the outcome of the vote; 
+     <li> any Formal Objections. 
+    </ul>
+    <p>In order to vote to resolve a substantive issue,
+	an individual <em class="rfc2119">must</em> be a group <a data-link-type="dfn" href="#participant" id="ref-for-participant①">participant</a>.
+	Each organization represented in the group <em class="rfc2119">must</em> have at most one vote,
+	even when the organization is represented by several participants in the group
+	(including Invited Experts).
+	For the purposes of voting:</p>
+    <ul>
+     <li> A Member or group of <a href="#MemberRelated">related Members</a> is considered a single organization. 
+     <li> The <a href="#Team">Team</a> is considered an organization. 
+    </ul>
+    <p>Unless the charter states otherwise, <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">may</em> vote.</p>
+    <p>If a participant is unable to attend a vote,
+	that individual <em class="rfc2119">may</em> authorize anyone at the meeting
+	to act as a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proxy">proxy</dfn>.
+	The absent participant <em class="rfc2119">must</em> inform the Chair in writing
+	who is acting as proxy, with written instructions on the use of the proxy.
+	For a Working Group or Interest Group,
+	see the related requirements regarding an individual
+	who attends a meeting as a <a href="#mtg-substitute" id="ref-for-mtg-substitute">substitute</a> for a participant.</p>
+    <p>A group <em class="rfc2119">may</em> vote for other purposes than to resolve a substantive issue.
+	For instance, the Chair often conducts a “straw poll” vote
+	as a means of determining whether there is consensus about a potential decision.</p>
+    <p>A group <em class="rfc2119">may</em> also vote to make a process decision.
+	For example,
+	it is appropriate to decide by simple majority
+	whether to hold a meeting in San Francisco or San Jose
+	(there’s not much difference geographically).
+	When simple majority votes are used to decide minor issues,
+	voters are <em class="rfc2119">not required</em> to state the reasons for votes,
+	and the group is <em class="rfc2119">not required</em> to record individual votes.</p>
+    <p>A group charter <em class="rfc2119">may</em> include formal voting procedures
+	(e.g., quorum or threshold requirements)
+	for making decisions about substantive issues.</p>
+    <h3 class="heading settled" data-level="5.3" id="formal-address"><span class="secno">5.3. </span><span class="content"> Formally Addressing an Issue</span><a class="self-link" href="#formal-address"></a></h3>
+    <p>In the context of this document,
+	a group has <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="formally-addressed">formally addressed</dfn> an issue when it has sent a public, substantive response
+	to the reviewer who raised the issue.
+	A substantive response is expected to include rationale for decisions
+	(e.g., a technical explanation, a pointer to charter scope, or a pointer to a requirements document).
+	The adequacy of a response is measured
+	against what a W3C reviewer would generally consider to be technically sound.
+	If a group believes that a reviewer’s comments result from a misunderstanding,
+	the group <em class="rfc2119">should</em> seek clarification before reaching a decision.</p>
+    <p>As a courtesy,
+	both Chairs and reviewers <em class="rfc2119">should</em> set expectations
+	for the schedule of responses and acknowledgments.
+	The group <em class="rfc2119">should</em> reply to a reviewer’s initial comments
+	in a timely manner.
+	The group <em class="rfc2119">should</em> set a time limit
+	for acknowledgment by a reviewer of the group’s substantive response;
+	a reviewer cannot block a group’s progress.
+	It is common for a reviewer to require a week or more
+	to acknowledge and comment on a substantive response.
+	The group’s responsibility to respond to reviewers
+	does not end once a reasonable amount of time has elapsed.
+	However, reviewers <em class="rfc2119">should</em> realize
+	that their comments will carry less weight
+	if not sent to the group in a timely manner.</p>
+    <p>Substantive responses <em class="rfc2119">should</em> be recorded.
+	The group <em class="rfc2119">should</em> maintain an accurate summary
+	of all substantive issues and responses to them
+	(e.g., in the form of an issues list with links to mailing list archives).</p>
+    <h3 class="heading settled" data-level="5.4" id="WGChairReopen"><span class="secno">5.4. </span><span class="content"> Reopening a Decision When Presented With New Information</span><a class="self-link" href="#WGChairReopen"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②④">Chair</a> <em class="rfc2119">may</em> reopen a decision
+	when presented with new information, including:</p>
+    <ul>
+     <li> additional technical information, 
+     <li> comments by email from participants who were unable to attend a scheduled meeting, 
+     <li> comments by email from meeting attendees
+			who chose not to speak out during a meeting
+			(e.g., so they could confer later with colleagues or for cultural reasons). 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑤">Chair</a> <em class="rfc2119">should</em> record
+	that a decision has been reopened,
+	and <em class="rfc2119">must</em> do so upon request from a group participant.</p>
+    <h3 class="heading settled" data-level="5.5" id="registering-objections"><span class="secno">5.5. </span><span class="content"> Registering Formal Objections</span><span id="WGArchiveMinorityViews"></span><span id="WGAppeals"></span><span id="wg-decision-appeal"></span><span id="chair-decision-appeal"></span><a class="self-link" href="#registering-objections"></a></h3>
+    <p>Any individual
+	(regardless of whether they are associated with a Member) <em class="rfc2119">may</em> appeal any decision made in connection with this Process
+	(except those having a different appeal process)
+	by registering a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="FormalObjection">Formal Objection</dfn> with the <a data-link-type="dfn" href="#team" id="ref-for-team④⑦">Team</a>.
+	Group participants <em class="rfc2119">should</em> inform
+	their <a href="#TeamContact" id="ref-for-TeamContact⑧">Team Contact</a> as well as the group’s Chair(s).
+	The Team Contact <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑦">CEO</a> when a group participant has also raised concerns about due process.</p>
+    <p class="note" role="note"><span>Note:</span> In this document, the term <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑥">Formal Objection</a> is used to emphasize this process implication:
+	Formal Objections receive formal consideration and a formal response.
+	The word “objection” used alone has its ordinary English connotations.
+	See <a href="#consensus-building">§ 5.2 Consensus Building</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑦">Formal Objection</a> <em class="rfc2119">must</em> include a summary of
+	the issue (whether technical or procedural),
+	the decision being appealed,
+	and the rationale for the objection.
+	It <em class="rfc2119">should</em> cite technical arguments
+	and propose changes that would remove the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑧">Formal Objection</a>;
+	these proposals <em class="rfc2119">may</em> be vague or incomplete. <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑨">Formal Objections</a> that do not provide substantive arguments
+	or rationale are unlikely to receive serious consideration.
+	Counter-arguments,
+	rationales,
+	and decisions <em class="rfc2119">should</em> also be recorded.</p>
+    <p>A record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⓪">Formal Objection</a> against a decision regarding a publicly-available document <em class="rfc2119">must</em> be made <a href="#confidentiality-change">publicly available</a>;
+	likewise, a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①①">Formal Objection</a> against a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①">Member-visible</a> decision <em class="rfc2119">must</em> be made <a href="#confidentiality-change">available to Members</a>.
+	A Call for Review to the Advisory Committee <em class="rfc2119">must</em> identify any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①②">Formal Objections</a> related to that review.</p>
+    <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①③">Formal Objections</a> against matter in a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①">technical report</a> are required to be addressed before <a href="#rec-advance">requesting advancement</a> of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②">technical report</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①④">Formal Objection</a> filed during an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review④">Advisory Committee Review</a> is considered registered at the close of the review period.</p>
+    <h3 class="heading settled" data-level="5.6" id="addressing-fo"><span class="secno">5.6. </span><span class="content"> Addressing Formal Objections</span><a class="self-link" href="#addressing-fo"></a></h3>
+    <h4 class="heading settled" data-level="5.6.1" id="team-fo-mediation"><span class="secno">5.6.1. </span><span class="content"> Investigation and Mediation by the Team</span><a class="self-link" href="#team-fo-mediation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④⑧">Team</a> considers the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑤">Formal objection</a>,
+	researches the question,
+	interviews parties,
+	and so on,
+	to make sure the problem and the various viewpoints are well understood,
+	and to the extent possible,
+	to arrive at a recommended disposition.
+	If the <a data-link-type="dfn" href="#team" id="ref-for-team④⑨">Team</a> can resolve the issue
+	to the satisfaction of the individual that filed the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑥">Formal Objection</a>,
+	the individual withdraws the objection and the disposition process terminates.</p>
+    <p>Otherwise,
+	upon concluding that consensus cannot be found,
+	and no later than 90 days after the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑦">Formal Objection</a> being registered,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⓪">Team</a> <em class="rfc2119">must</em> initiate formation of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③">W3C Council</a>,
+	which should be <a href="#council-convention">convened</a> within 45 days of being initiated.
+	Concurrently, it must prepare a report for the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council④">Council</a> documenting its findings and attempts to find consensus.</p>
+    <h4 class="heading settled" data-level="5.6.2" id="council"><span class="secno">5.6.2. </span><span class="content"> W3C Council</span><a class="self-link" href="#council"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-local-lt="Council" id="w3c-council">W3C Council</dfn> is the body convened to resolve <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑧">Formal Objections</a> by combining the capabilities and perspectives of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑤">AB</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⓪">TAG</a>, and the <a data-link-type="dfn" href="#team" id="ref-for-team⑤①">Team</a>,
+	and is tasked with doing so in the best interests of the Web and W3C.</p>
+    <h5 class="heading settled" data-level="5.6.2.1" id="council-composition"><span class="secno">5.6.2.1. </span><span class="content"> Council Composition</span><a class="self-link" href="#council-composition"></a></h5>
+    <p>Each <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑤">W3C Council</a> is composed of the following members (excepting any <a href="#council-participation">renounced or dismissed</a>):</p>
+    <ul>
+     <li data-md>
+      <p>the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑧">CEO</a> or their chosen <a data-link-type="dfn" href="#team" id="ref-for-team⑤②">Team</a> delegate</p>
+     <li data-md>
+      <p>the members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑥">Advisory Board</a></p>
+     <li data-md>
+      <p>the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③①">Technical Architecture Group</a></p>
+    </ul>
+    <p>Participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑥">W3C Council</a> <em class="rfc2119">must not</em> require attendance of <a data-link-type="dfn" href="#ftf-meeting" id="ref-for-ftf-meeting③">face-to-face meetings</a>.</p>
+    <p>A distinct instance of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑦">W3C Council</a> is convened for each decision being appealed or objected to.
+	Membership of each <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑧">Council</a> instance is fixed at formation,
+	and is not changed by any <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑦">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③②">TAG</a> elections
+	occurring before that Council has reached a conclusion.
+	However, if participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑨">Council</a> falls so low as to hinder effective and balanced deliberations,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair">W3C Council Chair</a> <em class="rfc2119">should</em> dissolve the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⓪">Council</a> and call for a new one to be convened.</p>
+    <p>A <a data-link-type="dfn" href="#team" id="ref-for-team⑤③">Team</a> member is assigned
+	to act as the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-team-contact">Council Team Contact</dfn>,
+	to support this Council
+	and to facilitate adherence to this Process.</p>
+    <h5 class="heading settled" data-level="5.6.2.2" id="council-delegation"><span class="secno">5.6.2.2. </span><span class="content"> Extraordinary Delegation</span><a class="self-link" href="#council-delegation"></a></h5>
+    <p>In extraordinary cases,
+	if they feel a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①①">Council</a> would not be the appropriate deciding body,
+	a member of the <a data-link-type="dfn" href="#team" id="ref-for-team⑤④">Team</a> (particularly the Legal Counsel) or
+	any potential Council member
+	may suggest that the decision for that specific Formal Objection be delegated
+	to the W3C Board of Directors,
+	to an officer of its corporation (such as the Legal Counsel),
+	or to one or more specific individuals from the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑤">Team</a>.
+	The potential Council members then <em class="rfc2119">may</em> confidentially discuss
+	and <em class="rfc2119">must</em> vote
+	whether to delegate the decision for that specific <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑨">Formal Objection</a>.
+	A decision to delegate <em class="rfc2119">must</em> be supported by a two-thirds supermajority vote
+	(i.e., at least twice as many votes in favor as against).
+	Delegation in such cases cannot be later revoked.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑥">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①③">Advisory Committee</a> when a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⓪">Formal Objection</a> has been delegated,
+	and to whom it has been delegated.</p>
+    <h5 class="heading settled" data-level="5.6.2.3" id="council-participation"><span class="secno">5.6.2.3. </span><span class="content"> Council Participation, Dismissal, and Renunciation</span><a class="self-link" href="#council-participation"></a></h5>
+    <p>A potential Council member may be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="dismissed | dismiss | dismissal" data-noexport id="dismissed">dismissed</dfn> from the Council.
+	In order to apply consistent criteria,
+	the potential Council members decide collectively
+	which reasons against service
+	rise to a sufficient level for a potential member to be <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed">dismissed</a>.
+	No-one is automatically dismissed,
+	and individual recusal is not used in the Council. <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed①">Dismissal</a> applies to an individual person in the context of a specific Council,
+	and should be used rarely in order to preserve the greatest diversity on the Council.</p>
+    <p class="note" role="note"><span>Note:</span> A W3C Council is a deliberative body whose purpose is
+	to find the best way forward for the Web and for W3C.
+	It is not a judicial body tasked with determining right or wrong.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑦">Team</a> <em class="rfc2119">must</em> draft a list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①②">Council</a> members,
+	with annotations of possible reasons for dismissal against each one.
+	The W3C community,
+	including members and team, and potential council members, <em class="rfc2119">must</em> be given an opportunity to contribute possible reasons to this list.
+	Affected members <em class="rfc2119">must</em> be given
+	an opportunity to respond to such comments about themselves.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑧">Team</a> may report comments verbatim
+	or may paraphrase them while preserving their intent;
+	they may also elide inappropriate comments,
+	such as any that violate applicable laws or the <a data-link-type="biblio" href="#biblio-cepc">[CEPC]</a>.</p>
+    <p>Before a Council forms,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑨">Team</a> presents the entire list of potential members
+	and collected reasons and responses
+	to the potential Council members,
+	who then consider for each potential member
+	whether that individual’s participation
+	would compromise the integrity of the Council decision,
+	and vote whether to dismiss that potential member.
+	No one is allowed to vote on their own dismissal;
+	each dismissal is decided by simple majority of those not abstaining.</p>
+    <p class="note" role="note"><span>Note:</span> Since dismissal is individual,
+	when the decision being objected to was made by the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③③">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑧">AB</a> acting as a body,
+	the entire <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③④">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑨">AB</a> is not expected or required to be dismissed.</p>
+    <p>An individual <em class="rfc2119">may</em> also <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="renounce | renunciation" data-noexport id="renounce">renounce</dfn> their seat on a Council, for strong reason,
+	such as being forbidden by their employer to serve. The individual chooses the extent to which they explain
+	their renunciation.
+	Renunciation is disqualification from participation,
+	not abstention,
+	and <em class="rfc2119">should not</em> be used
+	to excuse an absence of participation.</p>
+    <p>Any person who has been <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed②">dismissed</a> or who <a data-link-type="dfn" href="#renounce" id="ref-for-renounce">renounces</a> their seat
+	does not receive <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①③">Council</a> materials,
+	take part in its deliberations,
+	help in the determination of consensus,
+	or vote.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①④">W3C Council</a> <em class="rfc2110">may</em> still solicit and hear their testimony,
+	as they can of anyone else in the W3C community.</p>
+    <h5 class="heading settled" data-level="5.6.2.4" id="council-short-circuit"><span class="secno">5.6.2.4. </span><span class="content"> Unanimous Short Circuit</span><a class="self-link" href="#council-short-circuit"></a></h5>
+    <p>The full Council process <em class="rfc2119">may</em> be short-circuited if
+	the Team recommends a resolution
+	and every potential member of a Council who is not renouncing their seat
+	votes affirmatively (no abstentions) to adopt this resolution.</p>
+    <p>This step <em class="rfc2119">may</em> be run concurrently with <a href="#council-participation">§ 5.6.2.3 Council Participation, Dismissal, and Renunciation</a> and prior to choosing a <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair①">Chair</a>.</p>
+    <p class="note" role="note"><span>Note:</span> This is intended for exceptional cases
+	that don’t seem to warrant a full Council response
+	because they are, for instance, too trivial, duplicative, etc.</p>
+    <h5 class="heading settled" data-level="5.6.2.5" id="council-chairing"><span class="secno">5.6.2.5. </span><span class="content"> Council Chairing</span><a class="self-link" href="#council-chairing"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Council Chair" data-noexport id="w3c-council-chair">Chair</dfn> of each W3C Council is chosen by its members,
+	by consensus if possible,
+	falling back to a vote if that fails.
+	The chair must be a member of that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑤">W3C Council</a>.
+	Chair selection happens during formation of each Council,
+	and <em class="rfc2119">must</em> be re-run
+	if requested by the <a data-link-type="dfn" href="#council-team-contact" id="ref-for-council-team-contact">Council Team Contact</a> or by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑥">Chair</a> during the Council’s operation.</p>
+    <h5 class="heading settled" data-level="5.6.2.6" id="council-deliberations"><span class="secno">5.6.2.6. </span><span class="content"> Council Deliberations</span><a class="self-link" href="#council-deliberations"></a></h5>
+    <p id="council-convention"> Upon appointment of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair②">W3C Council Chair</a> and delivery of the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⓪">Team</a>’s report,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑥">W3C Council</a> is considered to be convened
+	and can start deliberations. </p>
+    <p>Having reviewed the information gathered by the <a data-link-type="dfn" href="#team" id="ref-for-team⑥①">Team</a>,
+	the Council <em class="rfc2119">may</em> conduct additional research or analysis,
+	or request additional information or interviews from anyone,
+	including the Team.</p>
+    <p id="broker-consensus"> The Council <em class="rfc2119">may</em> further attempt to broker consensus,
+	which, if successful, disposes the formal objection. </p>
+    <p>Otherwise,
+	after sufficient deliberation,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑦">W3C Council</a> decides whether to <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="uphold | upholds | upheld | upholding" data-noexport id="uphold">uphold</dfn> or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="overrule">overrule</dfn> the objection.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑧">W3C Council</a> <em class="rfc2119">may</em> <a data-link-type="dfn" href="#overrule" id="ref-for-overrule">overrule</a> the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②①">Formal Objection</a> even if it agrees with some of the supportive arguments.</p>
+    <p id="fo-mitigations"> When <a data-link-type="dfn" href="#uphold" id="ref-for-uphold">upholding</a> an objection,
+	it <em class="rfc2199">should</em> recommend a way forward.
+	If the overturned decision has already had consequences
+	(e.g., if the objection concerns material already in a published document)
+	the Council <em class="rfc2119">should</em> suggest how these consequences might be mitigated.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑥②">Team</a> is responsible for making sure that adequate mitigations are enacted in a timely fashion;
+	and the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②②">Formal Objection</a> is not considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fully-addressed">fully addressed</dfn> until then. </p>
+    <p class="note" role="note"><span>Note:</span> This does not create new powers for the <a data-link-type="dfn" href="#team" id="ref-for-team⑥③">Team</a>,
+	such as the ability to “unpublish” documents.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑥④">Team</a>'s role is to ensure the responsible parties enact adequate mitigations,
+	by whatever means they already have at their disposal.</p>
+    <p>A Council <em class="rfc2119">may</em> form sub-groups for deliberation,
+	who may return with a recommendation,
+	but the full Council issues the final decision.
+	The decision of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑨">W3C Council</a> <em class="rfc2119">should</em> be unanimous,
+	and <em class="rfc2119">may</em> be issued under consensus.
+	However, if despite careful deliberation
+	a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⓪">W3C Council</a> is unable to reach consensus,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair③">W3C Council Chair</a> may instead resort to voting.
+	In that case,
+	the decision is made by simple majority,
+	with the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair④">W3C Council Chair</a> breaking any tie.
+	In case of a vote,
+	if two members of a Council who share the same affiliation cast an identical ballot,
+	then their ballots count as a one vote,
+	not two.</p>
+    <p>In the case of non-unanimous decisions,
+	members of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②①">W3C Council</a> who disagree with the decision <em class="rfc2119">may</em> write a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minority-opinion">Minority Opinion</dfn> explaining the reason for their disagreement.</p>
+    <p>The deliberations of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②②">W3C Council</a> are confidential to that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②③">W3C Council</a> and its <a data-link-type="dfn" href="#council-team-contact" id="ref-for-council-team-contact①">Council Team Contact</a>.</p>
+    <p>If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②④">W3C Council</a> is unable to come to a conclusion within 45 days of being <a href="#council-convention">convened</a>,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑤">W3C Council Chair</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①④">AC</a> of this delay
+	and of the status of the discussions.
+	The <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑥">W3C Council Chair</a> <em class="rfc2119">may</em> additionally make this report <a href="#confidentiality-levels">public</a>.</p>
+    <h5 class="heading settled" data-level="5.6.2.7" id="council-decision"><span class="secno">5.6.2.7. </span><span class="content"> Council Decision Report</span><a class="self-link" href="#council-decision"></a></h5>
+    <p>A <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑤">Council</a> terminates by issuing a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-report">Council Report</dfn>,
+	which:</p>
+    <ul>
+     <li data-md>
+      <p><em class="rfc2119">must</em> state whether the Council <a data-link-type="dfn" href="#uphold" id="ref-for-uphold①">upholds</a> or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule①">overrules</a> the objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> provide a rationale supporting the decision,
+which <em class="rfc2119">should</em> address each argument raised in the Formal Objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include any recommendation decided by the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑥">Council</a>.</p>
+     <li data-md>
+      <p>if the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②③">Formal Objection</a> has been upheld, <em class="rfc2119">should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include the <a data-link-type="dfn" href="#minority-opinion" id="ref-for-minority-opinion">Minority Opinion</a>(s), if any.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of those who were <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed③">dismissed</a> or <a data-link-type="dfn" href="#renounce" id="ref-for-renounce①">renounced</a> their seat as well as those who were qualified to serve.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of the individuals who participated in the final decision.</p>
+     <li data-md>
+      <p><em class="rfc2119">may</em> report vote totals, if any vote was held.</p>
+     <li data-md>
+      <p><em class="rfc2119">must not</em> attribute any position to any individual on the Council.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑤">Team</a> <em class="rfc2119">must</em> maintain a <a data-biblio-display="inline" data-link-type="biblio" href="https://beta.w3.org/about/council/">public page on the W3C website</a> indexing all completed <a data-link-type="dfn" href="#council-report" id="ref-for-council-report">Council Reports</a>.
+	If a Council decision is later overturned by an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal">AC Appeal</a>,
+	this <em class="rfc2119">must</em> also be mentioned. <a data-link-type="dfn" href="#council-report" id="ref-for-council-report①">Council Reports</a> <em class="rfc2119">must</em> be no more confidential
+	than the decision or document being objected to.</p>
+    <p>The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑦">Council</a> <em class="rfc2119">may</em> also issue a <dfn data-dfn-type="dfn" data-export id="supplemental-confidential-council-report">Supplemental Confidential Council Report<a class="self-link" href="#supplemental-confidential-council-report"></a></dfn> with a more restricted <a href="#confidentiality-levels">level of confidentiality</a> than its main report
+	when it believes that additional commentary on confidential aspects of the case
+	would be informative.
+	However, the main <a data-link-type="dfn" href="#council-report" id="ref-for-council-report②">Council Report</a> <em class="rfc2119">should</em> be self-sufficient
+	and understandable without reference to Supplemental Confidential Council Reports.</p>
+    <h5 class="heading settled" data-level="5.6.2.8" id="council-appeals"><span class="secno">5.6.2.8. </span><span class="content"> Appealing Council Decisions</span><a class="self-link" href="#council-appeals"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①③">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①">Advisory Committee Appeal</a> of a Council decision issued in a <a data-link-type="dfn" href="#council-report" id="ref-for-council-report③">Council Report</a>.</p>
+    <h3 class="heading settled" data-level="5.7" id="ACReview"><span class="secno">5.7. </span><span class="content"> Advisory Committee Reviews</span><a class="self-link" href="#ACReview"></a></h3>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee review | AC Review" id="advisory-committee-review"> Advisory Committee review</dfn> is the process
+	by which the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑤">Advisory Committee</a> formally confers its approval
+	on <a data-link-type="dfn" href="#charter" id="ref-for-charter②">charters</a>, <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③">technical reports</a>,
+	and other matters.</p>
+    <h4 class="heading settled" data-level="5.7.1" id="ACReviewStart"><span class="secno">5.7.1. </span><span class="content"> Start of a Review Period</span><a class="self-link" href="#ACReviewStart"></a></h4>
+    <p>Each <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑤">Advisory Committee review</a> period
+	begins with a Call for Review from the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑥">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑥">Advisory Committee</a>.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="reviewform">Call for Review</dfn> describes the proposal,
+	raises attention to deadlines,
+	estimates when the decision will be available,
+	and includes other practical information.
+	Each Member organization <em class="rfc2119">may</em> send one review,
+	which <em class="rfc2119">must</em> be returned by its <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①④">Advisory Committee representative</a>.</p>
+    <p>For clarity,
+	in the context of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑥">AC Review</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent②">dissent</a> <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②④">Formal Objection</a>.</p>
+    <p>The Team <em class="rfc2119">must</em> provide two channels for Advisory Committee review comments:</p>
+    <ol>
+     <li> an archived <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑦">Team-only</a> channel; 
+     <li> an archived <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only②">Member-only</a> channel. 
+    </ol>
+    <p>The <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform">Call for Review</a> <em class="rfc2119">must</em> specify
+	which channel is the default for review comments on that Call.</p>
+    <p>Reviewers <em class="rfc2119">may</em> send information
+	to either or both channels.
+	A reviewer <em class="rfc2119">may</em> also share their own reviews
+	with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>,
+	and <em class="rfc2119">may</em> also make it available to the public.</p>
+    <p>A Member organization <em class="rfc2119">may</em> modify its review
+	during a review period
+	(e.g., in light of comments from other Members).</p>
+    <h4 class="heading settled" data-level="5.7.2" id="ACReviewAfter"><span class="secno">5.7.2. </span><span class="content"> After the Review Period</span><a class="self-link" href="#ACReviewAfter"></a></h4>
+    <p>After the review period,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑦">Team</a> determines the appropriate <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision③">W3C Decision</a>,
+	which they <em class="rfc2119">must</em> announce to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑦">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate
+	the level of support for the proposal
+	(<a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus③">consensus</a> or <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent③">dissent</a>),
+	and specifically
+	whether there were any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑤">Formal Objections</a>,
+	with attention to <a href="#confidentiality-change">changing the confidentiality level</a> of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑥">Formal Objections</a>.</p>
+    <p>If there were <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑦">Formal Objections</a>, at least some of which were <a data-link-type="dfn" href="#uphold" id="ref-for-uphold②">upheld</a>,
+	or if there is not <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus④">consensus</a> because of insufficient support, <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision④">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to improve the proposal. 
+     <li> The proposal is rejected. 
+    </ul>
+    <p>If the proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑤">consensus</a>,
+	or if any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑧">Formal Objections</a> are retracted or overruled
+	and the proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑥">consensus</a>,
+	this <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑤">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is adopted,
+			possibly with additional changes integrated
+			in order to address the comments of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑧">AC</a> (see below). 
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to make desirable changes identified during the review
+			and to resubmit. 
+    </ul>
+    <p>If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>,
+	then those changes <em class="rfc2119">must</em> be announced to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑨">AC</a> and to the <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group②">Group</a> that owns the document (if any).</p>
+    <p>Additionally, when adopting a proposal with <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change">substantive changes</a> integrated,
+	the announcement <em class="rfc2119">must</em> include rationale
+	for the substantive changes,
+	and those changes must have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑦">consensus</a> of the subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⓪">AC</a> that voted on the proposal
+	(including anyone who explicitly abstained).
+	For publications which have conditions in addition to <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②①">AC</a> approval
+	for introducing <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①">substantive changes</a> (such as <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group③">Group</a> consensus or implementation experience),
+	those other conditions must also be re-fulfilled.</p>
+    <div class="example" id="example-978a60c7"><a class="self-link" href="#example-978a60c7"></a> For example, to make <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change②">substantive changes</a> to a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①④">Proposed Recommendations</a>,
+		the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④">technical report</a> could be returned to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR">Candidate Recommendation</a>.
+		Alternatively, the desired changes can be introduced as non-substantive amendments
+		using the process for <a href="#revising-rec">revising a Recommendation</a>.
+		However, they cannot be directly integrated between <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①">PR</a> and <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①">REC</a>,
+		because that would fail to trigger a patent exclusion opportunity. </div>
+    <p>This document does not specify
+	time intervals between the end of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑦">Advisory Committee review</a> period
+	and the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑥">W3C decision</a>.
+	This is to ensure that the Members and <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑧">Team</a> have sufficient time to consider comments
+	gathered during the review.
+	The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②②">Advisory Committee</a> <em class="rfc2119">should not</em> expect an announcement
+	sooner than <span class="time-interval">two weeks</span> after the end of a review period.
+	If, after <span class="time-interval">three weeks</span>, the outcome has not been announced,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑨">Team</a> <em class="rfc2119">should</em> provide the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②③">Advisory Committee</a> with an update.</p>
+    <h3 class="heading settled" data-level="5.8" id="ACVotes"><span class="secno">5.8. </span><span class="content"> Advisory Committee Votes</span><a class="self-link" href="#ACVotes"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②④">Advisory Committee</a> votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>,
+	and in the event of an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal②">Advisory Committee Appeal</a> achieving the required support to trigger an appeal vote.
+	Whenever the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑤">Advisory Committee</a> votes,
+	each Member or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member③">related Members</a> has one vote.</p>
+    <h3 class="heading settled" data-level="5.9" id="ACAppeal"><span class="secno">5.9. </span><span class="content"> Appeal by Advisory Committee Representatives</span><a class="self-link" href="#ACAppeal"></a></h3>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑤">Advisory Committee representatives</a> <em class="rfc2119">may</em> appeal certain decisions,
+	though appeals are only expected to occur in extraordinary circumstances.</p>
+    <p>When a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑦">W3C decision</a> is made following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑧">Advisory Committee review</a>, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑥">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee Appeal|AC Appeal| Appeal" id="advisory-committee-appeal">Advisory Committee Appeal</dfn>.
+	These <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑧">W3C decisions</a> include those related to group creation and modification,
+	and transitions to new maturity stages for Recommendation Track documents
+	and the Process document.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑦">Advisory Committee representatives</a> <em class="rfc2119">may</em> also initiate an appeal
+	for decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑧">W3C Council</a>, and
+	for certain decisions that do not involve an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑨">Advisory Committee review</a>.
+	These cases are identified in the sections
+	which describe the requirements for the decision
+	and include
+	additional (non-reviewed) maturity stages of Recommendation Track documents,
+	group <a data-link-type="dfn" href="#dfn-charter-extension" id="ref-for-dfn-charter-extension">charter extensions</a> and closures,
+	and <a data-link-type="dfn" href="https://www.w3.org/Consortium/Process/#mou" id="ref-for-mou">Memoranda of Understanding</a>.</p>
+    <p>In all cases,
+	an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal③">appeal</a> <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the decision.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑧">Advisory Committee representative</a> initiates an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal④">appeal</a> by sending a request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⓪">Team</a>,
+	and should also share this request with the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑥">Advisory Committee</a>.
+	The request should say “I appeal this Decision”
+	and identify the decision,
+	and may also include their rationale for appealing the decision.</p>
+    <p class="note" role="note"><span>Note:</span> See <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/Guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a> for a recommendation
+	on how to communicate an appeal request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑦①">Team</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑦">AC</a>.</p>
+    <p>Within one week the <a data-link-type="dfn" href="#team" id="ref-for-team⑦②">Team</a> <em class="rfc2119">must</em> announce the appeal process
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑧">Advisory Committee</a> and provide a mechanism for <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑨">Advisory Committee representatives</a> to respond with a statement of positive support for this appeal.
+	The archive of these statements <em class="rfc2119">must</em> be <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only③">member-only</a>.
+	If, within <span class="time-interval">one week</span> of the Team’s announcement,
+	5% or more of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑨">Advisory Committee</a> support the appeal request,
+	the Team <em class="rfc2119">must</em> organize an appeal vote
+	asking the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⓪">Advisory Committee</a> “Do you approve of the Decision?”
+	together with links to the decision and the appeal support.</p>
+    <p>The ballot <em class="rfc2119">must</em> allow for three possible responses:
+	“Approve”,
+	“Reject”,
+	and “Abstain”,
+	together with Comments.</p>
+    <p>If the number of votes to reject
+	exceeds the number of votes to approve,
+	the decision is overturned.
+	In that case, there are the following possible next steps:</p>
+    <ol>
+     <li> The proposal is rejected. 
+     <li> The proposal is returned for additional work,
+			after which the applicable decision process is re-initiated. 
+    </ol>
+    <h2 class="heading settled" data-level="6" id="Reports"><span class="secno">6. </span><span class="content"> W3C Technical Reports</span><a class="self-link" href="#Reports"></a></h2>
+    <p>The W3C technical report development process is the set of steps and requirements
+	followed by W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①③">Working Groups</a> to standardize Web technology.
+	The W3C technical report development process is designed to:</p>
+    <ul>
+     <li> support multiple specification development methodologies 
+     <li> maximize <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑧">consensus</a> about the content of stable technical reports 
+     <li> ensure high technical and editorial quality 
+     <li> promote consistency among specifications 
+     <li> facilitate royalty-free, interoperable implementations of Web Standards, and 
+     <li> earn endorsement by W3C and the broader community. 
+    </ul>
+    <p>See also “licensing goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.1" id="recs-and-notes"><span class="secno">6.1. </span><span class="content"> Types of Technical Reports</span><a class="self-link" href="#recs-and-notes"></a></h3>
+    <p>This chapter describes the formal requirements
+	for <a data-link-type="dfn" href="#publishing" id="ref-for-publishing">publishing</a> and maintaining a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②">W3C Recommendation</a>, <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②②">Note</a>,
+	or <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report">Registry Report</a>.</p>
+    <dl>
+     <dt>Recommendations 
+     <dd> <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①④">Working Groups</a> develop technical reports on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track">W3C Recommendation Track</a> in order to produce normative specifications or guidelines
+			as standards for the Web.
+			The <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①">Recommendation Track</a> process incorporates requirements for <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review">wide review</a>, <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation">adequate implementation experience</a>,
+			and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑨">consensus</a>-building,
+			and is subject to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>,
+			under which participants commit to Royalty-Free IPR licenses for implementations.
+			See <a href="#rec-track">§ 6.3 The W3C Recommendation Track</a> for details. 
+     <dt>Notes 
+     <dd> Groups can also publish documents as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①">W3C Notes</a> and <a data-link-type="dfn" href="#statement" id="ref-for-statement">W3C Statements</a>,
+			typically either to document information
+			other than technical specifications,
+			such as use cases motivating a specification
+			and best practices for its use.
+			See <a href="#note-track">§ 6.4 The Note Track (Notes and Statements)</a> for details. 
+     <dt>Registries 
+     <dd> <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑤">Working Groups</a> can also publish <a data-link-type="dfn" href="#registry" id="ref-for-registry">registries</a> in order to document collections of values or other data.
+			These are typically published in a separate <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report①">registry report</a>,
+			although they can also be directly embedded in <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track②">Recommendation Track</a> documents
+			as a <a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section">registry section</a>. <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition">Defining a registry</a> requires <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①">wide review</a> and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⓪">consensus</a>,
+			but once set up, changes to registry entries are lightweight
+			and can even be done without a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑥">Working Group</a>.
+			See <a href="#registries">§ 6.5 The Registry Track</a> for details. 
+    </dl>
+    <p>Individual <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑦">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑦">Interest Groups</a> <em class="rfc2119">should</em> adopt additional processes
+	for developing publications,
+	so long as they do not conflict with the requirements in this chapter.</p>
+    <h3 class="heading settled" data-level="6.2" id="general-requirements"><span class="secno">6.2. </span><span class="content"> General Requirements for Technical Reports</span><a class="self-link" href="#general-requirements"></a></h3>
+    <h4 class="heading settled" data-level="6.2.1" id="publication"><span class="secno">6.2.1. </span><span class="content"> Publication of Technical Reports</span><a class="self-link" href="#publication"></a></h4>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="publish" data-noexport id="publishing">Publishing</dfn> as used in this document
+	refers to producing a version which is listed as a W3C <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="technical-report">Technical Report</dfn> on its <a href="https://www.w3.org/TR/">Technical Reports index at https://www.w3.org/TR</a> <a data-link-type="biblio" href="#biblio-tr">[TR]</a>.
+	Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public document.
+	W3C strives to make archival documents indefinitely available
+	at their original address in their original form.</p>
+    <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate its <a href="#maturity-stages">maturity stage</a>,
+	and <em class="rfc2119" id="DocumentStatus">must</em> include information about the status of the document.
+	This status information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> be unique each time a specification is <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①">published</a>, 
+     <li> <em class="rfc2119">must</em> state which <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑧">Working Group</a> developed the specification, 
+     <li> <em class="rfc2119">must</em> state how to send comments or file bugs,
+			and where these are recorded, 
+     <li> <em class="rfc2119">must</em> include expectations about next steps, 
+     <li> <em class="rfc2119">should</em> explain how the technology relates to existing international standards
+			and related work inside or outside W3C,
+			and 
+     <li> <em class="rfc2119">should</em> explain
+			or link to
+			an explanation of significant changes from the previous version. 
+    </ul>
+    <p>Every Technical Report published
+	as part of the Technical Report development process
+	is edited by one or more editors
+	appointed by a Group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑦">Chair</a>.
+	It is the responsibility of these editors to ensure that the decisions of the Group are
+	correctly reflected in subsequent drafts of the technical report.
+	An editor <em class="rfc2119">must</em> be a participant,
+	per <a href="#group-participation">§ 3.4.2 Participation in Chartered Groups</a> in the Group responsible for the document(s) they are editing.</p>
+    <p>The Team is <em class="rfc2119">not required</em> to publish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑤">Technical Report</a> that does not conform to the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules">[PUBRULES]</a> (e.g., for <span id="DocumentName">naming</span>,
+	status information,
+	style,
+	and <span id="document-copyright">copyright requirements</span>).
+	These rules are subject to change by the Team from time to time.
+	The Team <em class="rfc2119">must</em> inform group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑧">Chairs</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③①">Advisory Committee</a> of any changes to these rules.</p>
+    <p>The primary language for W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑥">Technical Reports</a> is English.
+	W3C encourages the translation of its <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑦">Technical Reports</a>. <a href="https://www.w3.org/Consortium/Translation/">Information about translations of W3C technical reports</a> <a data-link-type="biblio" href="#biblio-translation">[TRANSLATION]</a> is available at the W3C website.</p>
+    <h4 class="heading settled" data-level="6.2.2" id="doc-reviews"><span class="secno">6.2.2. </span><span class="content"> Reviews and Review Responsibilities</span><a class="self-link" href="#doc-reviews"></a></h4>
+    <p>A document is available for review
+	from the moment it is first <a data-link-type="dfn" href="#publishing" id="ref-for-publishing②">published</a>.
+	Working Groups <em class="rfc2119">should</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed">formally address</a> <em>any</em> substantive review comment
+	about a technical report in a timely manner.</p>
+    <p>Reviewers <em class="rfc2119">should</em> send substantive technical reviews as early as possible. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑨">Working Groups</a> are often reluctant to make <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change③">substantive changes</a> to a mature document,
+	particularly if this would cause significant compatibility problems
+	due to existing implementation. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⓪">Working Groups</a> <em class="rfc2119">should</em> record substantive
+	or interesting proposals raised by reviews
+	but not incorporated into a current specification.</p>
+    <h5 class="heading settled" data-level="6.2.2.1" id="wide-review"><span class="secno">6.2.2.1. </span><span class="content"> Wide Review</span><a class="self-link" href="#wide-review"></a></h5>
+    <p>The requirements for <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="dfn-wide-review">wide review</dfn> are not precisely defined by the W3C Process.
+	The objective is to ensure that the entire set of stakeholders of the Web community,
+	including the general public,
+	have had adequate notice of the progress of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②①">Working Group</a> (for example through notices posted to <a href="https://lists.w3.org/Archives/Public/public-review-announce/">public-review-announce@w3.org</a>)
+	and were able to actually perform reviews of and provide comments on the specification.
+	A second objective is to encourage groups to request reviews
+	early enough that comments and suggested changes
+	can still be reasonably incorporated in response to the review.
+	Before approving transitions,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦③">Team</a> will consider who has been explicitly offered
+	a reasonable opportunity to review the document,
+	who has provided comments,
+	the record of requests to and responses from reviewers,
+	especially <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter">[CHARTER]</a> and groups identified as dependencies in the charter
+	or identified as <a href="https://www.w3.org/2001/11/StdLiaison.html">liaisons</a> <a data-link-type="biblio" href="#biblio-liaison">[LIAISON]</a>,
+	and seek evidence of clear communication to the general public
+	about appropriate times and which content to review
+	and whether such reviews actually occurred.</p>
+    <p>For example,
+	inviting review of new or significantly revised sections published in Working Drafts,
+	and tracking those comments
+	and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②②">Working Group</a>'s responses,
+	is generally a good practice which would often be considered positive evidence of wide review. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②③">Working Groups</a> <em class="rfc2119">should</em> follow the <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">W3C Horizontal Groups</a>’ review processes,
+	and <em class="rfc2119">should</em> announce to other W3C Working Groups
+	as well as the general public,
+	especially those affected by this specification,
+	a proposal to enter <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①">Candidate Recommendation</a> (for example in approximately 28 days).
+	By contrast a generic statement in a document
+	requesting review at any time
+	is likely not to be considered as sufficient evidence
+	that the group has solicited wide review.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②④">Working Group</a> could present evidence that wide review has been received,
+	irrespective of solicitation.
+	But it is important to note that receiving many detailed reviews
+	is not necessarily the same as wide review,
+	since they might only represent comment
+	from a small segment of the relevant stakeholder community.</p>
+    <h4 class="heading settled" data-level="6.2.3" id="correction-classes"><span class="secno">6.2.3. </span><span class="content"> Classes of Changes</span><a class="self-link" href="#correction-classes"></a></h4>
+    <p>This document distinguishes the following 5 classes of changes to a document.
+	The first two classes of change are considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="editorial change" data-noexport id="editorial-change">editorial changes</dfn>,
+	the next two <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="substantive change" data-noexport id="substantive-change">substantive changes</dfn>,
+	and the last one <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="registry change" data-noexport id="registry-change">registry changes</dfn>.</p>
+    <dl>
+     <dt id="class-1">
+      <a class="self-link" href="#class-1"></a> 
+      <ol>
+       <li data-md>
+        <p>No changes to text content</p>
+      </ol>
+     <dd> These changes include fixing broken links, style sheets, or invalid markup. 
+     <dt id="class-2">
+      <a class="self-link" href="#class-2"></a> 
+      <ol start="2">
+       <li data-md>
+        <p>Changes that do not functionally affect interpretation of the document</p>
+      </ol>
+     <dd> For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track③">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑧">technical reports</a> specifically,
+            this constitutes changes that do not affect conformance,
+            i.e. changes that reasonable implementers
+			would not interpret as changing architectural
+			or interoperability requirements
+			or their implementation.
+			Changes which resolve ambiguities in the specification
+			are considered to change (by clarification) the implementation requirements
+			and do not fall into this class. 
+     <dd> Examples of changes in this class include
+			correcting non-normative examples
+			which clearly conflict with normative requirements,
+			clarifying informative use cases or other non-normative text,
+			fixing typos or grammatical errors
+			where the change does not change requirements. 
+     <dd> If there is any doubt or disagreement
+			as to whether a change functionally affects interpretation,
+			that change does not fall into this class. 
+     <dt id="class-3">
+      <a class="self-link" href="#class-3"></a> 
+      <ol start="3">
+       <li data-md>
+        <p>Other changes that do not add new features</p>
+      </ol>
+     <dd>
+       For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track④">Recommendation-track</a> documents,
+            these changes <em class="rfc2119">may</em> affect conformance to the specification.
+			A change that affects conformance is one that: 
+      <ul>
+       <li> makes conforming data, processors, or other conforming agents become non-conforming according to the new version,
+					or 
+       <li> makes non-conforming data, processors, or other agents become conforming,
+					or 
+       <li> clears up an ambiguity or under-specified part of the specification
+					in such a way that data,
+					a processor,
+					or an agent
+					whose conformance was once unclear
+					becomes clearly either conforming or non-conforming. 
+      </ul>
+     <dt id="class-4">
+      <a class="self-link" href="#class-4"></a> 
+      <ol start="4">
+       <li data-md>
+        <p>New features</p>
+      </ol>
+     <dd> Changes that add new functionality,
+			such as new elements, new APIs, new rules, etc. 
+     <dt id="class-5">
+      <a class="self-link" href="#class-5"></a> 
+      <ol start="5">
+       <li data-md>
+        <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table">registry table</a></p>
+      </ol>
+     <dd> Changes that add, remove, or alter <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry">registry entries</a> in a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①">registry table</a>. 
+    </dl>
+    <h4 class="heading settled" data-level="6.2.4" id="errata"><span class="secno">6.2.4. </span><span class="content"> Errata Management</span><a class="self-link" href="#errata"></a></h4>
+    <p>Tracking errors is an important part of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑤">Working Group</a>'s ongoing care of a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑨">technical report</a>;
+	for this reason,
+	the scope of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑥">Working Group</a> charter generally allows time
+	for work after publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③">Recommendation</a>.
+	In this Process Document,
+	the term “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="erratum | errata" id="erratum">erratum</dfn>”
+	(plural “errata”) refers to any error
+	that can be resolved by one or more changes in classes 1-3
+	of section <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑦">Working Groups</a> <em class="rfc2119">must</em> keep
+	a public record of errors
+	that are reported by readers and implementers
+	for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④">Recommendations</a>.
+	Such error reports <em class="rfc2119">should</em> be compiled
+	no less frequently than quarterly.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑧">Working Groups</a> decide how to document errata.
+	Such documentation <em class="rfc2119">must</em> identify
+	the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⓪">technical report</a> text
+	and describe the error;
+	it <em class="rfc2119">may</em> also describe some possible solution(s).
+	Readers of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①①">technical report</a> <em class="rfc2119">should</em> be able easily
+	to find and see the errata
+	that apply to that specific <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①②">technical report</a> with their associated tests.
+	Errata <em class="rfc2119">may</em> be documented
+	in a separate errata page or tracking system.
+	They <em class="rfc2119">may</em>,
+	in addition or alternatively,
+	be annotated inline
+	alongside the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①③">technical report</a> text
+	or at the start or end of the most relevant section(s).</p>
+    <h4 class="heading settled" data-level="6.2.5" id="candidate-amendments"><span class="secno">6.2.5. </span><span class="content"> Candidate Amendments</span><span id="candidate-changes"></span><a class="self-link" href="#candidate-amendments"></a></h4>
+    <p>An <a data-link-type="dfn" href="#erratum" id="ref-for-erratum">erratum</a> <em class="rfc2119">may</em> be accompanied by an informative, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-correction">candidate correction</dfn> approved by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision②">group decision</a>.
+	When annotated inline,
+	errata—<wbr>including their <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction">candidate corrections</a>—<wbr>must be marked as such,
+	are treated as <a href="#correction-classes">class 2 changes</a>,
+	and are published accordingly.</p>
+    <p class="note" role="note"><span>Note:</span> Annotating changes in this way allows more mature documents
+	such as <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤">Recommendations</a> and <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②">Candidate Recommendations</a> to be updated quickly with the Working Group’s most current thinking,
+	even when the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment">candidate amendments</a> have not yet received
+	sufficient review or implementation experience
+	to be normatively incorporated into the specification proper.</p>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-addition">candidate addition</dfn> is similar to a <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction①">candidate correction</a>,
+	except that it proposes a new feature
+	rather than an error correction.</p>
+    <p>If there is no group chartered to maintain a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①④">technical report</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦④">Team</a> <em class="rfc2119">may</em> maintain its <a data-link-type="dfn" href="#erratum" id="ref-for-erratum①">errata</a> and associated <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction②">candidate corrections</a>.
+	Such corrections <em class="rfc2119">must</em> be marked
+	as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="team-correction">Team correction</dfn>,
+	and do not constitute
+	a normative portion of the Recommendation,
+	as defined in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> (i.e. they are not covered by the Patent Policy).
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑤">Team</a> <em class="rfc2119">must</em> solicit <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review②">wide review</a> on <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction">Team corrections</a> that it produces.</p>
+    <p><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction③">Candidate corrections</a> and <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition">candidate additions</a> are collectively known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="candidate amendment" data-noexport id="candidate-amendment">candidate amendments</dfn>.</p>
+    <p>In addition to their actual <a href="#maturity-stages">maturity stage</a>, <a data-link-type="dfn" href="#publishing" id="ref-for-publishing③">published</a> <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑤">REC Track</a> documents with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①">candidate amendments</a> are also considered,
+	for the purpose of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>,
+	to be <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①">Working Drafts</a> with those <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment②">candidate amendments</a> treated as normative.</p>
+    <h4 class="heading settled" data-level="6.2.6" id="contributor-license"><span class="secno">6.2.6. </span><span class="content"> License Grants from Non-Participants</span><a class="self-link" href="#contributor-license"></a></h4>
+    <p>When a party who is not already obligated under the Patent Policy
+	offers a change in class 3 or 4
+	(as described in <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>) to a technical report under this process
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑥">Team</a> <em class="rfc2119">must</em> request
+	a recorded royalty-free patent commitment;
+	for a change in class 4, the Team <em class="rfc2119">must</em> secure such commitment.
+	Such commitment <em class="rfc2119">should</em> cover,
+	at a minimum,
+	all the party’s Essential Claims both in the contribution,
+	and that become Essential Claims as a result of incorporating the contribution into the draft
+	that existed at the time of the contribution,
+	on the terms specified in the “W3C Royalty-Free (RF) Licensing Requirements” section of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.3" id="rec-track"><span class="secno">6.3. </span><span class="content"> The W3C Recommendation Track</span><span id="rec-advance"></span><a class="self-link" href="#rec-track"></a></h3>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑨">Working Groups</a> create specifications and guidelines
+	to complete the scope of work envisioned by a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⓪">Working Group</a>'s <a data-link-type="dfn" href="#charter" id="ref-for-charter③">charter</a>.
+	These <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑤">technical reports</a> undergo cycles of revision and review
+	as they advance towards <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥">W3C Recommendation</a> status.
+	Once review suggests the Working Group has met their requirements for a new standard,
+	including <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review③">wide review</a>,
+	a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR③">Candidate Recommendation</a> phase
+	allows the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③①">Working Group</a> to formally collect <a href="#implementation-experience">implementation experience</a> to demonstrate that the specification works in practice.
+	At the end of the process,
+	the Advisory Committee reviews the mature technical report,
+	and if there is support from its Membership,
+	W3C publishes it as a <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑦">Recommendation</a>.</p>
+    <p>In summary, the <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track" data-noexport id="w3c-recommendation-track">W3C Recommendation Track</dfn> consists of:</p>
+    <ol>
+     <li>Publication of the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd①">First Public Working Draft</a>. 
+     <li>Publication of zero or more revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD②">Working Drafts</a>. 
+     <li>Publication of one or more <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR④">Candidate Recommendations</a>. 
+     <li>Publication of a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR②">Proposed Recommendation</a>. 
+     <li>Publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦">W3C Recommendation</a>. 
+    </ol>
+    <div aria-label="Basic W3C Recommendation Track" role="region">
+     <svg viewBox="-5 40 630 180" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Basic W3C Recommendation Track</title>
+      <g role="list">
+       <g fill="#060" role="listitem">
+        <a href="#wd-1">
+         <rect fill="white" height="45" role="img" width="57" y="122">
+          <title>First Public Working Draft (FPWD) - Exclusion opportunity</title>
+         </rect>
+         <text font-size="8">
+          <tspan aria-hidden="true" x="0" y="132">First Public WD</tspan>
+          <tspan x="0" y="152">WG Decision +</tspan>
+          <tspan x="0" y="160">Team Approval</tspan>
+         </text>
+         <path d="M0,140h53" fill="none" stroke="#060"></path>
+         <polygon points="47,136 57,140 47,144"></polygon>
+        </a>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="97" cy="140" fill="#fff" id="wd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Working Draft (WD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="97" y="144">WD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Publish a new Working Draft</title>
+           </g>
+           <text font-size="8">
+            <tspan x="70" y="100">WG Decision</tspan>
+           </text>
+           <path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114" fill="none" stroke="black" stroke-dasharray="6 2"></path>
+           <polygon points="120,114 116,124 114,113"></polygon>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Advance to Candidate Recommendation</title>
+           </g>
+           <text font-size="8" x="138" y="126">WG Decision +</text>
+           <text font-size="8" x="138" y="134">Team Approval</text>
+           <path d="M135,140h81" stroke="#060"></path>
+           <polygon points="211,136 221,140 211,144"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#pr-1">
+         <ellipse cx="260" cy="140" fill="#fff" id="cr-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="144">CRS</text>
+        </a>
+        <a href="#crd-1">
+         <ellipse cx="260" cy="80" fill="#fff" id="crd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Draft (CRD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="84">CRD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8">
+            <tspan x="182" y="110">WG Decision</tspan>
+           </text>
+           <path d="M234,127v-34" stroke="#000"></path>
+           <polygon points="234,92 230,102 238,102"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8">
+            <tspan x="282" y="52">WG Decision</tspan>
+           </text>
+           <path d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="282,54 277,64 275,53"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="102">WG Decision +</tspan>
+            <tspan x="290" y="110">Team Approval</tspan>
+           </text>
+           <path d="M286,127v-34" stroke="#000"></path>
+           <polygon points="286,128 282,118 290,118"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="102">WG Decision</tspan>
+            <tspan x="290" y="110">Team Approval</tspan>
+           </text>
+           <path d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114" fill="none" stroke="#000" stroke-dasharray="6 10"></path>
+           <path d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114" fill="none" stroke="#000" stroke-dasharray="6 10" stroke-dashoffset="8"></path>
+           <polygon points="282,114 277,124 275,113"></polygon>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#pr-1">
+           <g role="img">
+            <title>Advance to Proposed Recommendation</title>
+           </g>
+           <text font-size="8" x="300" y="126">WG Decision +</text>
+           <text font-size="8" x="300" y="134">Team Approval</text>
+           <path d="M298,140h77" stroke="#060"></path>
+           <polygon points="374,136 384,140 374,144"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="230" y="160">WG Decision</tspan>
+            <tspan font-size="6" x="230" y="168">(or Team Decision with AB+TAG Approval)</tspan>
+           </text>
+           <path d="M140,147h84" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="140,145 133,147 140,149"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="413" cy="140" fill="#fff" id="pr-1" role="img" rx="28" ry="18" stroke="black">
+          <title>Proposed Recommendation (PR) — AC Review</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="413" y="144">PR</text>
+         <text area-hidden="true" font-size="6" text-anchor="middle" x="413" y="150">AC Review</text>
+        </a>
+        <g role="list">
+         <g fill="#060" role="listitem">
+          <a href="#rec-1">
+           <g role="img">
+            <title>Advance to Recommendation</title>
+           </g>
+           <text font-size="8" x="300" y="138">
+            <tspan x="445" y="134">W3C Decision</tspan>
+           </text>
+           <path d="M441,140h100" stroke="#060"></path>
+           <polygon points="534,136 544,140 534,144"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Return to Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="385" y="160">W3C Decision</tspan>
+           </text>
+           <path d="M301,147h88" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="301,145 296,147 301,149"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="410" y="185">W3C Decision</tspan>
+           </text>
+           <path d="M413,158v32h-316v-26" fill="none" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="95,164 97,159 99,164"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <ellipse cx="573" cy="140" fill="#fff" id="rec-1" role="img" rx="28" ry="18" stroke="black" stroke-width="2">
+         <title>Recommendation (Rec)</title>
+        </ellipse>
+        <text aria-hidden="true" font-size="16" font-weight="bold" stroke-width=".3" text-anchor="middle" x="573" y="144">REC</text>
+       </g>
+      </g>
+     </svg>
+    </div>
+    <p>This Process defines certain <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑥">Recommendation Track</a> publications as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="patent-review-drafts">Patent Review Drafts</dfn>.
+	Under the 2004 Patent Policy (and its 2017 update) <a data-link-type="biblio" href="#biblio-patent-policy-2004">[PATENT-POLICY-2004]</a>,
+	these correspond to “Last Call Working Draft” in the Patent Policy;
+	Starting from the 2020 Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy-2020">[PATENT-POLICY-2020]</a>,
+	these correspond to “Patent Review Draft” in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <p>W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.</p>
+    <p>As described in <a href="#transition-reqs">§ 6.3.3 Advancement on the Recommendation Track</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑦">Team</a> will decline a request to advance in maturity stage
+	and return the specification to a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③②">Working Group</a> for further work
+	if it determines that the requirements for advancement
+	have not been met.</p>
+    <h4 class="heading settled" data-level="6.3.1" id="maturity-stages"><span class="secno">6.3.1. </span><span class="content"> Maturity Stages on the Recommendation Track</span><span id="maturity-levels"></span><a class="self-link" href="#maturity-stages"></a></h4>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Working Draft | Working Draft | WD" id="RecsWD">Working Draft</dfn> (<abbr>WD</abbr>) 
+     <dd>
+       A Working Draft is a document that W3C has <a data-link-type="dfn" href="#publishing" id="ref-for-publishing④">published</a> on the <a href="https://www.w3.org/TR/">W3C’s Technical Reports page</a> <a data-link-type="biblio" href="#biblio-tr">[TR]</a> for review by the community (including W3C Members), the public,
+			and other technical organizations,
+			and for simple historical reference.
+			Some, but not all, Working Drafts are meant to advance to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑧">Recommendation</a>;
+			see the <a href="#DocumentStatus">document status section</a> of a Working Draft
+			for the group’s expectations. <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD③">Working Drafts</a> do not necessarily represent a <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①①">consensus</a> of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③③">Working Group</a> with respect to their content,
+			and do not imply any endorsement by W3C
+			or its members beyond agreement to work on a general area of technology.
+			Nevertheless the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③④">Working Group</a> decided to adopt the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD④">Working Draft</a> as the basis for their work at the time of adoption.
+			A <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑤">Working Draft</a> is suitable for gathering <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review④">wide review</a> prior to advancing to the next stage of maturity. 
+      <p>For all Working Drafts a Working Group:</p>
+      <ul>
+       <li> <em class="rfc2119">should</em> document outstanding issues,
+					and parts of the document on which the Working Group does not have consensus,
+					and 
+       <li> <em class="rfc2119">may</em> request publication of a Working Draft
+					even if its content is considered unstable
+					and does not meet all Working Group requirements. 
+      </ul>
+      <p>The first Working Draft of a technical report is called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="fpwd">First Public Working Draft</dfn> (<abbr>FPWD</abbr>),
+			and has patent implications as defined in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Candidate Recommendation | Candidate Recommendation | CR" id="RecsCR">Candidate Recommendation</dfn> (<abbr>CR</abbr>) 
+     <dd>
+       A Candidate Recommendation is a document that satisfies the technical
+			requirements of the Working Group that produced it and their dependencies,
+			and has already received wide review.
+			W3C publishes a Candidate Recommendation to 
+      <ul>
+       <li> signal to the wider community that it is time to do a final review 
+       <li> gather <a href="#implementation-experience">implementation experience</a> 
+      </ul>
+      <p class="note" role="note"><span>Note:</span> Advancing to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑤">Candidate Recommendation</a> indicates
+			that the document is considered complete and fit for purpose,
+			and that no further refinement to the text is expected
+			without additional implementation experience and testing;
+			additional features in a later revision may however be expected.
+			A <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑥">Candidate Recommendation</a> is expected to be as well-written,
+			detailed,
+			self-consistent,
+			and technically complete
+			as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑨">Recommendation</a>,
+			and acceptable as such
+			if and when the requirements for further advancement are met.</p>
+      <p>Candidate Recommendation publications take one of two forms:</p>
+      <dl>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Snapshot | CRS" id="candidate-recommendation-snapshot">Candidate Recommendation Snapshot</dfn> (<abbr>CRS</abbr>) 
+       <dd>
+         A Candidate Recommendation Snapshot
+					corresponds to a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts">Patent Review Draft</a> as used in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.
+					Publishing a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts①">Patent Review Draft</a> triggers a Call for Exclusions,
+					per “Exclusion From W3C RF Licensing Requirements”
+					in the W3C Patent Policy. 
+        <p>Publication as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a> requires verification of either a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req">Transition Request</a> (for the first <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑦">Candidate Recommendation</a> publication from another maturity stage)
+					or an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests">Update Request</a> (for subsequent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①">Candidate Recommendation Snapshots</a>).</p>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Draft | CRD" id="candidate-recommendation-draft">Candidate Recommendation Draft</dfn> (<abbr>CRD</abbr>) 
+       <dd>
+         A Candidate Recommendation Draft
+					is published on the <a href="https://www.w3.org/TR/">W3C’s Technical Reports page</a> <a data-link-type="biblio" href="#biblio-tr">[TR]</a> to integrate changes from the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot②">Candidate Recommendation Snapshot</a> that the Working Group intends to include
+					in a subsequent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot③">Candidate Recommendation Snapshot</a>.
+					This allows for wider review of the changes
+					and for ease of reference to the integrated specification. 
+        <p>Any changes published directly into a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft">Candidate Recommendation Draft</a> should be at the same level of quality as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot④">Candidate Recommendation Snapshot</a>.
+					However, the process requirements are minimized
+					so that the Working Group can easily keep the specification up to date.</p>
+        <p>A <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft①">Candidate Recommendation Draft</a> <em>does not</em> provide an exclusion opportunity;
+					instead, it is considered a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑥">Working Draft</a> for the purpose of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+      </dl>
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rescinded-candidate-recommendation">Rescinded Candidate Recommendation</dfn> is a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑧">Candidate Recommendation</a> in which significant problems have been discovered
+			such that W3C cannot endorse it or continue work on it,
+			for example due to burdensome patent claims that affect implementers and cannot be resolved
+			(see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> and in particular “PAG Conclusion”).
+			There is no path to restoration for a <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a>.
+			See “W3C Royalty-Free (RF) Licensing Requirements”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> for implication on patent licensing obligations.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Proposed Recommendation | Proposed Recommendation | PR" id="RecsPR">Proposed Recommendation</dfn> (<abbr>PR</abbr>) 
+     <dd> A Proposed Recommendation is a document
+			that has been accepted by W3C
+			as of sufficient quality to become a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⓪">W3C Recommendation</a>.
+			This phase triggers formal review by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③②">Advisory Committee</a>,
+			who <em class="rfc2119">may</em> recommend
+			that the document be <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑤">published</a> as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①①">W3C Recommendation</a>,
+			returned to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑤">Working Group</a> for further work,
+			or abandoned. <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change④">Substantive changes</a> <em class="rfc2119">must not</em> be made to a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR③">Proposed Recommendation</a> except by <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑥">publishing</a> a new <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑦">Working Draft</a> or <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑨">Candidate Recommendation</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation | Recommendation | REC" id="RecsW3C">W3C Recommendation</dfn> (<abbr>REC</abbr>) 
+     <dd>
+       A W3C Recommendation is a specification
+			or set of guidelines
+			or requirements that,
+			after extensive <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①②">consensus</a>-building,
+			has received the endorsement of W3C and its Members.
+			W3C recommends the wide deployment
+			of its Recommendations as standards for the Web.
+			The W3C Royalty-Free IPR licenses
+			granted under the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> apply to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①②">W3C Recommendations</a>.
+			As technology evolves,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①③">W3C Recommendation</a> may become: 
+      <dl>
+       <dt> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsSup">Superseded Recommendation</dfn> 
+       <dd>
+         A Superseded Recommendation is a specification
+					that has been replaced by a newer version
+					that W3C recommends for new adoption.
+					An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs">Obsolete</a> or Superseded specification
+					has the same status as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①④">W3C Recommendation</a> with regards to W3C Royalty-Free IPR Licenses granted under the Patent Policy. 
+        <p class="note" role="note"><span>Note:</span> When a Technical Report which had previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑤">Recommendation</a> is again published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑥">Recommendation</a> after following the necessary steps to <a href="#revising-rec">revise</a> it,
+					the latest version replaces the previous one,
+					without the need to invoke the steps of <a href="#rec-rescind">§ 6.3.13.3 Abandoning a W3C Recommendation</a>:
+					it is the same document, updated.
+					Explicitly declaring a documented superseded, using the process documented in <a href="#rec-rescind">§ 6.3.13.3 Abandoning a W3C Recommendation</a>,
+					is intended for cases where a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑦">Recommendation</a> is superseded by a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑥">Technical Report</a> (or by a document managed outside of W3C).</p>
+       <dt> An <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsObs">Obsolete Recommendation</dfn> 
+       <dd> An Obsolete Recommendation is a specification
+					that W3C has determined lacks sufficient market relevance
+					to continue recommending it for implementation,
+					but which does not have fundamental problems
+					that would require it to be <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec">Rescinded</a>.
+					If an Obsolete specification gains sufficient market relevance,
+					W3C may decide to restore it to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑧">Recommendation</a> status. 
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RescindedRec">Rescinded Recommendation</dfn> 
+       <dd> A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses,
+					and believes is unlikely to ever be restored to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑨">Recommendation</a> status.
+					See also “W3C Royalty-Free (RF) Licensing Requirements”
+					in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>. 
+      </dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="discontinuedREC">Discontinued Draft</dfn> 
+     <dd> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑦">technical report</a> representing the state of a Recommendation-track document
+			at the point at which work on it was discontinued.
+			See <a href="#abandon-draft">§ 6.3.13.1 Abandoning an Unfinished Recommendation</a>. 
+    </dl>
+    <p>Only sufficiently technically mature work should be advanced.</p>
+    <p class="note" role="note"><span>Note:</span> Should faster advancement to meet scheduling considerations be desired,
+	this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring
+	less stable features to other technical reports.</p>
+    <p>When publishing an updated version of an existing <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⓪">Candidate Recommendation</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⓪">Recommendation</a>,
+	technical reports are expected to meet the same maturity criteria as when they are first published under that status.
+	However, in the interest of replacing stale documents with improved ones in a timely manner,
+	if flaws have been discovered in the technical report after its initial publication as a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①①">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②①">REC</a> that would have been severe enough to reject that publication had they be known in time,
+	it is also permissible to publish an updated <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①②">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②②">REC</a> following the usual process,
+	even if only some of these flaws have been satisfactorily addressed.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑥">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑧">Interest Groups</a> <em class="rfc2119">may</em> make available <a data-link-type="dfn" href="#editors-draft" id="ref-for-editors-draft">Editor’s drafts</a>. <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Editor’s Draft | Editor Draft | ED" id="editors-draft">Editor’s drafts</dfn> (<abbr>ED</abbr>) have no official standing whatsoever,
+	and do not necessarily imply consensus of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑦">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑨">Interest Group</a>,
+	nor are their contents endorsed in any way by W3C.</p>
+    <h4 class="heading settled" data-level="6.3.2" id="implementation-experience"><span class="secno">6.3.2. </span><span class="content"> Implementation Experience</span><a class="self-link" href="#implementation-experience"></a></h4>
+    <p>Implementation experience is required to show that a specification is sufficiently clear,
+	complete,
+	and relevant to market needs,
+	to ensure that independent interoperable implementations
+	of each feature of the specification will be realized.
+	While no exhaustive list of requirements is provided here,
+	when assessing that there is <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="adequate-implementation">adequate implementation experience</dfn> the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑧">Team</a> will consider (though not be limited to):</p>
+    <ul>
+     <li> is each feature of the current specification implemented,
+			and how is this demonstrated? 
+     <li> are there independent interoperable implementations of the current specification? 
+     <li> are there implementations created by people other than the authors of the specification? 
+     <li> are implementations publicly deployed? 
+     <li> is there implementation experience
+			at all levels of the specification’s ecosystem
+			(authoring, consuming, publishing…)? 
+     <li> are there reports of difficulties or problems with implementation? 
+    </ul>
+    <p>Planning and accomplishing a demonstration of (interoperable) implementations can be very time consuming.
+	Groups are often able to work more effectively
+	if they plan how they will demonstrate interoperable implementations
+	early in the development process;
+	for example, developing tests in concert with implementation efforts.</p>
+    <h4 class="heading settled" data-level="6.3.3" id="transition-reqs"><span class="secno">6.3.3. </span><span class="content"> Advancement on the Recommendation Track</span><a class="self-link" href="#transition-reqs"></a></h4>
+    <p>For <em>all</em> requests to advance a specification
+	to a new maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="trans-req">Transition Requests</dfn>),
+	the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request advancement. 
+     <li> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑨">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team⑧⓪">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision②">Team decision</a>) <em class="rfc2119">must</em> be withheld if any Process requirements are not met
+			or if there remain any unresolved Formal Objections
+			(including any <a data-link-type="dfn" href="#uphold" id="ref-for-uphold③">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑨">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed">fully addressed</a>),
+			or if the document does not adequately reflect all relevant decisions of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⓪">W3C Council</a> (or its delegates).
+			If the <a data-link-type="dfn" href="#team" id="ref-for-team⑧①">Team</a> rejects a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req①">Transition Request</a> it <em class="rfc2119">must</em> indicate its rationale
+			to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③③">Advisory Committee</a> and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑧">Working Group</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change">editorial changes</a> have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed①">formally address</a> all issues
+			raised about the document since the previous <a href="#maturity-stages">maturity stage</a>. 
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑨">Formal Objections</a>. 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑨">Working Group</a>'s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⓪">Working Group</a>. 
+    </ul>
+    <p>For a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd②">First Public Working Draft</a> there is no “previous maturity stage”,
+	so many requirements do not apply,
+	and verification is normally fairly straightforward.
+	For later stages,
+	especially transition to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①③">Candidate</a> or <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR④">Proposed Recommendation</a>,
+	there is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p><a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req②">Transition Requests</a> to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd③">First Public Working Draft</a> or <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①④">Candidate Recommendation</a> will not normally be approved
+	while a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④①">Working Group</a>'s <a data-link-type="dfn" href="#charter" id="ref-for-charter④">charter</a> is undergoing or awaiting a decision
+	on an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⓪">Advisory Committee Review</a>.</p>
+    <p></p>
+    <h4 class="heading settled" data-level="6.3.4" id="update-reqs"><span class="secno">6.3.4. </span><span class="content"> Updating Mature Publications on the Recommendation Track</span><a class="self-link" href="#update-reqs"></a></h4>
+    <p>Certain requests to re-publish a specification
+	within its current maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="update-requests">Update Requests</dfn>)
+	require extra verification.
+	For such <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①">update requests</a>, the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request the update. 
+     <li> <em class="rfc2119">must</em> show that the changes have received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑤">wide review</a>. 
+     <li> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑧②">Team</a> verification,
+			or fulfill the criteria for <a href="#streamlined-update">§ 6.3.4.1 Streamlined Publication Approval</a>. <a data-link-type="dfn" href="#team" id="ref-for-team⑧③">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision③">Team decision</a>), <em>should</em> be withheld if any Process requirements are not met,
+			and <em class="rfc2119">may</em> be withheld in consideration of unresolved Formal Objections
+			(including any <a data-link-type="dfn" href="#uphold" id="ref-for-uphold④">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③①">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed①">fully addressed</a>)
+			or if the document does not adequately reflect all relevant decisions of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③②">W3C Council</a> (or its delegates).
+			If the <a data-link-type="dfn" href="#team" id="ref-for-team⑧④">Team</a> rejects an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests②">Update Request</a>,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④②">Working Group</a>.
+			If it waives any Process requirements,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③④">AC</a>. 
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⓪">Formal Objections</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document of all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①">editorial changes</a> changes have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> show that the revised specification
+			meets all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④③">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④④">Working Group</a>'s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑤">Working Group</a>. 
+    </ul>
+    <p>There is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests③">Update request</a> verification is expected to be fairly simple
+	compared to verification of a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req③">transition request</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑤">Team</a> <em class="rfc2119">must</em> announce the publication
+	of the revised specification
+	to other W3C groups and the Public.</p>
+    <h5 class="heading settled" data-level="6.3.4.1" id="streamlined-update"><span class="secno">6.3.4.1. </span><span class="content"> Streamlined Publication Approval</span><a class="self-link" href="#streamlined-update"></a></h5>
+    <p class="note" role="note"><span>Note:</span> These criteria are intentionally stricter than
+	the general requirements for an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests④">update request</a>.
+	This is in order to minimize ambiguities and the need for expert judgment,
+	and to make self-evaluation practical.</p>
+    <p>In order to streamline the publication process in non-controversial cases,
+	verification of an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑤">update request</a> is automatically granted without formal review
+	when the following <em>additional</em> criteria are fulfilled:</p>
+    <ul>
+     <li> There <em class="rfc2119">must</em> have been no changes to <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑥">Working Group</a> requirements about this document. 
+     <li> For each of the <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter">[CHARTER]</a>,
+			if the Horizontal Review Group has made available a set criteria
+			under which their review is not necessary,
+			the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑦">Working Group</a> <em class="rfc2119">must</em> document that these criteria have been fulfilled.
+			Otherwise, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑧">Working Group</a> <em class="rfc2119">must</em> show
+			that review from that group has been solicited and received. 
+     <li> No <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③①">Formal Objection</a> has been registered against the document. 
+     <li>
+       The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑨">Working Group</a> <em class="rfc2119">must</em> have <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed②">formally addressed</a>: 
+      <ul>
+       <li data-md>
+        <p>all issues raised against the document that resulted in changes since the previous publication</p>
+       <li data-md>
+        <p>all issues raised against changes since the previous publication</p>
+       <li data-md>
+        <p>all issues raised against the document that were closed since the previous publication with no change to the document</p>
+      </ul>
+      <p>The response to each of these issues <em class="rfc2119">must</em> be to the satisfaction
+			of the person who raised it:
+			their proposal has been accepted,
+			or a compromise has been found,
+			or they accepted the Working Group’s rationale for rejecting it.</p>
+      <p class="note" role="note"><span>Note:</span> This is stricter than the general Transition Request criteria.</p>
+    </ul>
+    <p>Additionally, for updates to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②③">Recommendations</a> with <a href="#revised-rec-substantive">substantive changes</a> or <a href="#revised-rec-features">with new features</a>:</p>
+    <ul>
+     <li> Changes to the document are limited to <a data-link-type="dfn" href="#proposed-corrections" id="ref-for-proposed-corrections">proposed corrections</a> that were included in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections" id="ref-for-last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a> possibly combined with <a href="#correction-classes">class 1 or 2 changes</a>,
+			and/or (in the case of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②④">Recommendation</a> that <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features">allows new features</a>) <a data-link-type="dfn" href="#proposed-additions" id="ref-for-proposed-additions">proposed additions</a> that were included in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-additions" id="ref-for-last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a>. 
+     <li>
+       The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⓪">Working Group</a> <em class="rfc2119">must</em> show
+			that all changes have been implemented in at least 2 distinct products by 2 different implementers,
+			as evidenced by passing tests of a test suite
+			providing extensive coverage of the changes,
+			or an alternative streamlined verification implementation requirement
+			described in the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤①">working Group</a> charter has been met. 
+      <p class="note" role="note"><span>Note:</span> This is stricter than the general criteria for <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation①">adequate implementation experience</a>.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤②">Working Group</a> must provide written evidence for these claims,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑥">Team</a> must make these answers publicly and permanently available.</p>
+    <p>After publication,
+	if an AC Representative
+	or Team member
+	doubts that the evidence presented supports the claims,
+	they <em class="rfc2119">may</em> request that a formal review meeting be convened post facto.
+	If that review finds that the requirements were not fulfilled,
+	the Team <em class="rfc2119">may</em> revert the changes
+	by updating in place the status section to indicate that it has been reverted,
+	and by republishing the previously approved version of the technical report.</p>
+    <h4 class="heading settled" data-level="6.3.5" id="first-wd"><span class="secno">6.3.5. </span><span class="content"> Publishing a First Public Working Draft</span><a class="self-link" href="#first-wd"></a></h4>
+    <p>To publish the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd④">First Public Working Draft</a> of a document,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤③">Working Group</a> <em class="rfc2119">must</em> meet the applicable <a href="#transition-reqs">requirements for advancement</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑦">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑤">First Public Working Draft</a> to other W3C groups and to the public.</p>
+    <h4 class="heading settled" data-level="6.3.6" id="revising-wd"><span class="secno">6.3.6. </span><span class="content"> Revising a Working Draft</span><span id="revised-wd"></span><a class="self-link" href="#revising-wd"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤④">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑦">publish</a> a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑧">Working Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>If 6 months elapse without significant changes to a specification,
+	a Working Group <em class="rfc2119">should</em> publish a revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑨">Working Draft</a>,
+	whose status section <em class="rfc2119">should</em> indicate reasons for the lack of change.</p>
+    <p>To publish a revision of a Working draft, a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication. <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①③">Consensus</a> is not required,
+			as this is a procedural step, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑤">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①⓪">Working Draft</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change②">editorial changes</a> to the technical report
+			since the previous step, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups, 
+    </ul>
+    <p>Possible next steps for any Working Draft:</p>
+    <ul>
+     <li>Revised <a href="#revising-wd">Working Draft</a> 
+     <li><a href="#transition-cr">Candidate Recommendation</a> 
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.7" id="transition-cr"><span class="secno">6.3.7. </span><span class="content"> Transitioning to Candidate Recommendation</span><span id="candidate-rec"></span><span id="last-call"></span><a class="self-link" href="#transition-cr"></a></h4>
+    <p>To publish a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑤">Candidate Recommendation</a>,
+	in addition to meeting the <a href="#transition-reqs">requirements for advancement</a> a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑤">Working Group</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> show that the specification
+			has met all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑥">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">must</em> document changes to dependencies during the development of the specification, 
+     <li> <em class="rfc2119">must</em> document
+			how <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation②">adequate implementation experience</a> will be demonstrated, 
+     <li> <em class="rfc2119">must</em> specify the deadline for comments,
+			delineating the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-recommendation-review-period">Candidate Recommendation review period</dfn>,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">must</em> show that the specification has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑥">wide review</a>, and 
+     <li> <em class="rfc2119">may</em> identify features in the document as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="at-risk">at risk</dfn>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑤">Proposed Recommendation</a> without a requirement to publish a new <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑥">Candidate Recommendation</a>. 
+    </ul>
+    <p>The first Candidate Recommendation publication
+	after verification of having met the requirements for a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req④">Transition Request</a> is always a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑤">Candidate Recommendation Snapshot</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑧">Team</a> <em class="rfc2119">must</em> announce
+	the publication of the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑥">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑦">Candidate Recommendation Snapshot</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Proposed Recommendation</a>
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <p><a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑤">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 class="heading settled" data-level="6.3.8" id="revising-cr"><span class="secno">6.3.8. </span><span class="content"> Revising a Candidate Recommendation</span><span id="revised-cr"></span><a class="self-link" href="#revising-cr"></a></h4>
+    <h5 class="heading settled" data-level="6.3.8.1" id="publishing-crrs"><span class="secno">6.3.8.1. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑧">Candidate Recommendation Snapshot</a></span><a class="self-link" href="#publishing-crrs"></a></h5>
+    <p>If there are any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑥">substantive changes</a> made to a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑦">Candidate Recommendation</a> since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑨">Candidate Recommendation Snapshot</a> other than to remove features explicitly identified as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk">at risk</a>,
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑦">Working Group</a> <em class="rfc2119">must</em> meet the requirements of an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑥">update request</a> in order to republish.</p>
+    <p>In addition the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> specify the deadline for further comments,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">may</em> identify features in the document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk①">at risk</a>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑥">Proposed Recommendation</a> without a requirement to publish a new <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑧">Candidate Recommendation</a>. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑨">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a revised <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⓪">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>To provide timely updates and patent protection,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①①">Candidate Recommendation Snapshot</a> <em class="rfc2119">should</em> be published
+	within 24 months of the Working Group accepting
+	any proposal for a substantive change
+	(and preferably sooner).
+	To make scheduling reviews easier,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①②">Candidate Recommendation Snapshot</a> <em class="rfc2119">should not</em> be published
+	more often than approximately once every 6 months.</p>
+    <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑦">Substantive changes</a> trigger a new Exclusion Opportunity
+	per “Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.8.2" id="publishing-crud"><span class="secno">6.3.8.2. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft②">Candidate Recommendation Draft</a></span><a class="self-link" href="#publishing-crud"></a></h5>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑧">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑧">publish</a> an <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft③">Update Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft④">Candidate Recommendation Draft</a>,
+	a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑧">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①③">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change③">editorial changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①④">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> document outstanding issues,
+			and parts of the document on which the Working Group does not have consensus, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+    </ul>
+    <p class="note" role="note"><span>Note:</span> A Working Group <em>does not</em> need to
+	meet the requirements of a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑤">Candidate Recommendation Snapshot</a> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑦">update request</a> in order to publish a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑤">Candidate Recommendation Draft</a>.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑥">Candidate Recommendation Draft</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Proposed Recommendation</a>,
+		if there are no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑨">substantive change</a> other than dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk②">at risk</a> features
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.9" id="transition-pr"><span class="secno">6.3.9. </span><span class="content"> Transitioning to Proposed Recommendation</span><span id="rec-pr"></span><a class="self-link" href="#transition-pr"></a></h4>
+    <p>In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,</p>
+    <ul>
+     <li> The status information <em class="rfc2119">must</em> specify the deadline for <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①①">Advisory Committee review</a>,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days
+			after the publication of the <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑦">Proposed Recommendation</a> and <em class="rfc2119">should</em> be at least 10 days
+			after the end of the last Exclusion Opportunity
+			per ”Exclusion From W3C RF Licensing Requirements”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>. 
+    </ul>
+    <p>A Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation③">adequate implementation experience</a> except where an exception is approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision④">Team Decision</a>, 
+     <li> <em class="rfc2119">must</em> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑦">wide review</a>, 
+     <li> <em class="rfc2119">must</em> show that all issues
+			raised during the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period">Candidate Recommendation review period</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed③">formally addressed</a>, 
+     <li> <em class="rfc2119">must </em>identify any substantive issues
+			raised since the close of the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period①">Candidate Recommendation review period</a>, 
+     <li> <em class="rfc2119">must not</em> have made any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①⓪">substantive changes</a> to the document
+			since the most recent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑥">Candidate Recommendation Snapshot</a>,
+			other than dropping features identified <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk③">at risk</a>. 
+     <li> <em class="rfc2119">may</em> have removed features
+			identified in the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑦">Candidate Recommendation Snapshot</a> document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk④">at risk</a> without republishing the specification as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑧">Candidate Recommendation Snapshot</a>. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑨⓪">Team</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> announce the publication of a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑧">Proposed Recommendation</a> to the <a href="#AC">Advisory Committee</a>,
+			and <em class="rfc2119">must</em> begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①②">Advisory Committee Review</a> on the question of whether the specification is appropriate to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑨">publish</a> as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑤">W3C Recommendation</a>. 
+     <li> <em class="rfc2119">may</em> approve a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑨">Proposed Recommendation</a> with minimal <a href="#implementation-experience">implementation experience</a> where there is a compelling reason to do so.
+			In such a case, the <a data-link-type="dfn" href="#team" id="ref-for-team⑨①">Team</a> <em class="rfc2119">must</em> explain the reasons for that decision,
+			and that information <em class="rfc2119">must</em> be included in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform①">Call for Review</a> proposing advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑥">W3C Recommendation</a>. 
+    </ul>
+    <p>Since a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑦">W3C Recommendation</a> <em class="rfc2119">must not</em> include any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①①">substantive changes</a> from the <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①⓪">Proposed Recommendation</a> it is based on,
+	to make any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①②">substantive change</a> to a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①①">Proposed Recommendation</a> the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑨">Working Group</a> <em class="rfc2119">must</em> return the specification to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑨">Candidate Recommendation</a> or <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①①">Working Draft</a>.</p>
+    <p id="expandable-rec"> A <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①②">Proposed Recommendation</a> may identify itself
+	as intending to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="allow-new-features">allow new features</dfn> (<a href="#correction-classes">class 4 changes</a>)
+	after its initial publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑧">Recommendation</a>,
+	as described in <a href="#revised-rec-features">§ 6.3.11.4 Revising a Recommendation: New Features</a>.
+	Such an allowance cannot be added
+	to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑧">technical report</a> previously published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑨">Recommendation</a> that did not allow such changes. </p>
+    <p>Possible Next Steps:</p>
+    <ul>
+     <li> Return to <a href="#revising-wd">Working Draft</a> 
+     <li> Return to <a href="#transition-cr">Candidate Recommendation</a> 
+     <li> <a href="#transition-rec">Recommendation status</a>,
+			(the expected next step). 
+     <li> <a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⓪">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑤">Advisory Committee Appeal</a> of the decision to advance the technical report.</p>
+    <h4 class="heading settled" data-level="6.3.10" id="transition-rec"><span class="secno">6.3.10. </span><span class="content"> Transitioning to W3C Recommendation</span><span id="rec-publication"></span><a class="self-link" href="#transition-rec"></a></h4>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⓪">Recommendation</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑨">W3C Decision</a>.</p>
+    <p>In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,</p>
+    <ul>
+     <li> A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③①">Recommendation</a> <em class="rfc2119">must</em> identify where errata are tracked, and 
+     <li> A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③②">Recommendation</a> <em class="rfc2119">must not</em> include any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①③">substantive changes</a> from the <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①③">Proposed Recommendation</a> on which it is based. 
+     <li> If there was any <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent④">dissent</a> in Advisory Committee reviews,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team⑨②">Team</a> <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 data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed④">formally address</a> the comment
+			at least 14 days before publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③③">W3C Recommendation</a>. 
+     <li> <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②①">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+			an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑥">Advisory Committee Appeal</a> of the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⓪">W3C decision</a> 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team⑨③">Team</a> <em class="rfc2119">must</em> announce the publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③④">W3C Recommendation</a> to <a href="#AC">Advisory Committee</a>,
+			other W3C groups
+			and to the public. 
+    </ul>
+    <p>Possible next steps:
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑤">W3C Recommendation</a> normally retains its status indefinitely.
+	However it <em class="rfc2119">may</em> be:</p>
+    <ul>
+     <li> republished as a <a href="#revising-rec">revised Recommendation</a>, or 
+     <li> republished as a <a href="#transition-cr">Candidate Recommendation</a> to be developed towards a revised <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑥">Recommendation</a>, or 
+     <li> declared <a href="#rec-rescind">superseded or obsolete</a>, or 
+     <li> <a href="#rec-rescind">rescinded</a>. 
+    </ul>
+    <h4 class="heading settled" data-level="6.3.11" id="revising-rec"><span class="secno">6.3.11. </span><span class="content"> Revising a W3C Recommendation</span><span id="rec-modify"></span><span id="revised-rec"></span><a class="self-link" href="#revising-rec"></a></h4>
+    <p>This section details the process for making changes to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑦">Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.11.1" id="revised-rec-markup"><span class="secno">6.3.11.1. </span><span class="content"> Revising a Recommendation: Markup Changes</span><a class="self-link" href="#revised-rec-markup"></a></h5>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⓪">Working group</a> <em class="rfc2119">may</em> request republication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑧">Recommendation</a> to make corrections that do not result
+	in any changes to the text of the specification.
+	(See <a href="#correction-classes">class 1 changes</a>.)</p>
+    <p>If there is no <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥①">Working Group</a> chartered to maintain a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑨">Recommendation</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨④">Team</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⓪">Recommendation</a> with such changes incorporated.</p>
+    <h5 class="heading settled" data-level="6.3.11.2" id="revised-rec-editorial"><span class="secno">6.3.11.2. </span><span class="content"> Revising a Recommendation: Editorial Changes</span><a class="self-link" href="#revised-rec-editorial"></a></h5>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change④">Editorial changes</a> to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④①">Recommendation</a> require no technical review of the intended changes.
+	A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥②">Working Group</a>,
+	provided there are no votes against the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision③">decision</a> to publish, <em class="rfc2119">may</em> request publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④②">Recommendation</a> to make this class of change without passing through earlier maturity stages.
+	(See <a href="#correction-classes">class 2 changes</a>.)</p>
+    <p>If there is no <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥③">Working Group</a> chartered to maintain a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④③">Recommendation</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑤">Team</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④④">Recommendation</a> with such changes incorporated,
+	including <a data-link-type="dfn" href="#erratum" id="ref-for-erratum②">errata</a> and <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction①">Team corrections</a>.</p>
+    <h5 class="heading settled" data-level="6.3.11.3" id="revised-rec-substantive"><span class="secno">6.3.11.3. </span><span class="content"> Revising a Recommendation: Substantive Changes</span><a class="self-link" href="#revised-rec-substantive"></a></h5>
+    <p>A <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction④">candidate correction</a> can be made normative
+	and be folded into the main text of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑤">Recommendation</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑥">Recommendation</a>,
+	including review by the community to ensure
+	the technical and editorial soundness of the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment③">candidate amendments</a>.
+	To validate this, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥④">Working Group</a> must request
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review">Last Call for Review of Proposed Amendments</a>,
+	followed by an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑧">update request</a>.
+	See <a href="#change-review">§ 6.3.11.5 Incorporating Candidate Amendments</a>.</p>
+    <p>Alternatively,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑤">Working Group</a> <em class="rfc2119">may</em> incorporate the changes
+	and <a href="#revising-wd">publish as a Working Draft</a>—<wbr>or, if the relevant criteria are fulfilled, <a href="#transition-cr">publish as a Candidate Recommendation</a>—<wbr>and advance the specification from that state.
+	(See <a href="#correction-classes">class 3 changes</a>.)</p>
+    <p class="note" role="note"><span>Note:</span> If there is no <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑥">Working Group</a> chartered to maintain a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑦">Recommendation</a> the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑥">Team</a> cannot make substantive changes and republish the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑧">Recommendation</a>.
+	It can, however, informatively highlight problems and desirable changes
+	using <a data-link-type="dfn" href="#erratum" id="ref-for-erratum③">errata</a> and <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑤">candidate corrections</a> and republish as described in <a href="#revised-rec-editorial">the previous section</a>.</p>
+    <h5 class="heading settled" data-level="6.3.11.4" id="revised-rec-features"><span class="secno">6.3.11.4. </span><span class="content"> Revising a Recommendation: New Features</span><a class="self-link" href="#revised-rec-features"></a></h5>
+    <p>New features (see <a href="#correction-classes">class 4 changes</a>)
+	may be incorporated into a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑨">Recommendation</a> explicitly identified as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features①">allowing new features</a> using <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition①">candidate additions</a>.
+	A <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition②">candidate addition</a> can be made normative
+	and be folded into the main text of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⓪">Recommendation</a> using the same process as for <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment④">candidate amendments</a>,
+	as detailed in <a href="#revised-rec-substantive">§ 6.3.11.3 Revising a Recommendation: Substantive Changes</a>.</p>
+    <p class="note" role="note"><span>Note:</span> This prohibition against new features unless explicitly allowed
+	enables third parties to depend on Recommendations having a stable feature-set,
+	as they have prior to the 2020 revision of this Process.</p>
+    <p>To make changes which introduce a new feature
+	to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤①">Recommendation</a> that does not <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features②">allow new features</a>,
+	W3C <em class="rfc2119">must</em> create a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑨">technical report</a>,
+	following the full process of <a href="#rec-advance">advancing a technical report to Recommendation</a> beginning with a new <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑥">First Public Working Draft</a>.</p>
+    <h5 class="heading settled" data-level="6.3.11.5" id="change-review"><span class="secno">6.3.11.5. </span><span class="content"> Incorporating Candidate Amendments</span><a class="self-link" href="#change-review"></a></h5>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-review">Last Call for Review of Proposed Amendments</dfn> verifies acceptance by the W3C community of <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑤">candidate amendments</a> by combining an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①③">AC Review</a> with a patent exclusion opportunity.</p>
+    <p>The <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review①">Last Call for Review of Proposed Amendments</a> must be announced to other W3C groups, the public, and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑥">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Identify whether this is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</dfn>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</dfn>,
+			or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</dfn>. 
+     <li> Identify the specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑥">candidate amendments</a> under review
+			as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-amendments">proposed amendments</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-corrections">proposed corrections</dfn>/<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-additions">proposed additions<span id="proposed-addition"></span></dfn>). 
+     <li> Specify the deadline for review comments,
+			which must not be any sooner than 60 days from the Call for Review. 
+     <li> Solicit review and, if it does not already have it, implementation experience. 
+    </ul>
+    <p>The combination of the existing <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤②">Recommendation</a> with the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments">proposed amendments</a> included in the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review②">Last Call for Review of Proposed Amendments</a> is considered a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts②">Patent Review Draft</a> for the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.
+	Also, the review initiated by the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review③">Last Call for Review of Proposed Amendments</a> is an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①④">Advisory Committee Review</a>.</p>
+    <p class="note" role="note"><span>Note:</span> <a data-link-type="dfn" href="#last-call-for-review-of-proposed-additions" id="ref-for-last-call-for-review-of-proposed-additions①">Last Call for Review of Proposed Additions</a> and <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections-and-additions" id="ref-for-last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a> can only be issued for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤③">Recommendations</a> that <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features③">allow new features</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑦">Working Group</a> <em class="rfc2119">may</em> batch
+	multiple <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①">proposed amendments</a> into a single <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review④">Last Call for Review of Proposed Amendments</a>.
+	To facilitate review,
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑤">Last Call for Review of Proposed Amendments</a> on a given specification <em class="rfc2119">should not</em> be issued more frequently
+	than approximately once every 6 months.</p>
+    <p>At the end of the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑥">Last Call for Review of Proposed Amendments</a>,
+	the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①①">W3C Decision</a> may either be
+	to reject the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments②">proposed amendment</a>,
+	or to clear the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments③">proposed amendment</a> for advancement as is,
+	or to return the proposal to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑧">Working Group</a> with a request to <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑤">formally address</a> comments made on the changes under review.
+	If the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑨">Working Group</a> needs to amend a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments④">proposed amendment</a> in response to review feedback
+	it must issue another <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑦">Last Call for Review of Proposed Amendments</a> on the revised change
+	before it can be incorporated into the main text.</p>
+    <p>Once all comments on a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑤">proposed amendment</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑥">formally addressed</a>,
+	and after the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⓪">Working Group</a> can show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation④">adequate implementation experience</a> and the fulfillment of all other requirements of Recommendation text,
+	it may incorporate the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑥">proposed amendment</a> into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤④">Recommendation</a> by issuing an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑨">update request</a> for publication of the updated <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑤">Recommendation</a>.</p>
+    <p>To ensure adequate review of <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑦">proposed amendment</a> combinations,
+	only <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑧">proposed amendments</a> included in the most recent <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑧">Last Call for Review of Proposed Amendments</a> can be incorporated into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑥">Recommendation</a> text.
+	(Thus if incorporation of a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑨">proposed amendment</a> is postponed,
+	it may need to be included in multiple Last Calls for Review of Proposed Amendments.)</p>
+    <h4 class="heading settled" data-level="6.3.12" id="rec-track-regression"><span class="secno">6.3.12. </span><span class="content"> Regression on the Recommendation Track</span><a class="self-link" href="#rec-track-regression"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦①">Working Group</a> may republish a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑦">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⓪">technical report</a> at a lower <a href="#maturity-stages">maturity stage</a> by fulfilling the requirements to transition to that maturity stage,
+	as described above.</p>
+    <p>Additionally,
+	with the approval of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑤">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⓪">AB</a> the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑦">Team</a> <em class="rfc2119">may</em> return
+	the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②①">technical report</a> to a lower <a href="#maturity-stages">maturity stage</a> in response to <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑧">wide review</a> or a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③②">formal objection</a>.</p>
+    <h4 class="heading settled" data-level="6.3.13" id="tr-end"><span class="secno">6.3.13. </span><span class="content"> Retiring Recommendation Track Documents</span><a class="self-link" href="#tr-end"></a></h4>
+    <p>Work on a technical report <em class="rfc2119">may</em> cease at any time.
+	Work <em class="rfc2119 new">should</em> cease
+	if W3C or a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦②">Working Group</a> determines
+	that it cannot productively carry the work any further.</p>
+    <h5 class="heading settled" data-level="6.3.13.1" id="abandon-draft"><span class="secno">6.3.13.1. </span><span class="content"> Abandoning an Unfinished Recommendation</span><a class="self-link" href="#abandon-draft"></a></h5>
+    <p>Any <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑧">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②②">technical report</a> no longer intended
+	to advance or to be maintained,
+	and that is not being rescinded, <em class="rfc2119">should</em> be <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①⓪">published</a> as a <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC">Discontinued Draft</a>,
+	with no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①④">substantive change</a> compared to the previous publication.
+	This can happen if
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦③">Working Group</a> decided
+	to abandon work on the report,
+	or as the result of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑤">AC Review</a> requiring the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦④">Working Group</a> to discontinue work on the technical report before completion.
+	If a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑤">Working Group</a> is made to <a href="#GeneralTermination">close</a>,
+	W3C <em class="rfc2119">must</em> re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing①①">publish</a> any unfinished <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②③">technical report</a> on the Recommendation track as <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC①">Discontinued Draft</a>.</p>
+    <p>Such a document should include in its status section
+	an explanation of why it was discontinued.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑥">Working Group</a> <em class="rfc2119">may</em> resume work
+	on such a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②④">technical report</a> within the scope of its charter
+	at any time,
+	by re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing①②">publishing</a> it as a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①②">Working Draft</a>.</p>
+    <h5 class="heading settled" data-level="6.3.13.2" id="rescind-cr"><span class="secno">6.3.13.2. </span><span class="content"> Rescinding a Candidate Recommendation</span><a class="self-link" href="#rescind-cr"></a></h5>
+    <p>The process for rescinding a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②⓪">Candidate Recommendation</a> is the same as for rescinding a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑦">Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.13.3" id="rec-rescind"><span class="secno">6.3.13.3. </span><span class="content"> Abandoning a W3C Recommendation</span><a class="self-link" href="#rec-rescind"></a></h5>
+    <p>It is possible that W3C decides
+	that implementing a particular <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑧">Recommendation</a> is no longer recommended.
+	There are three designations for such specifications,
+	chosen depending on the advice W3C wishes to give about further use of the specification.</p>
+    <p>W3C <em class="rfc2119">may</em> obsolete a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑨">Recommendation</a>,
+	for example if the W3C Community decides that the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⓪">Recommendation</a> no longer represents best practices,
+	or is not adopted and is not apparently likely to be adopted.
+	An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs①">Obsolete Recommendation</a> <em class="rfc2119">may</em> be restored to normal <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥①">Recommendation</a>,
+	for example because despite marking it Obsolete the specification is later more broadly adopted.</p>
+    <p>W3C <em class="rfc2119">may</em> declare a Recommendation Superseded
+	if a newer version exists which W3C recommends for new adoption.
+	The process for declaring a Recommendation Superseded is the same as for declaring it Obsolete, below;
+	only the name and explanation change.</p>
+    <p>W3C <em class="rfc2119">may</em> rescind a Recommendation
+	if W3C believes there is no reasonable prospect of it being restored
+	for example due to burdensome patent claims that affect implementers and cannot be resolved;
+	see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> and in particular “W3C Royalty-Free (RF) Licensing Requirements”
+	and “PAG Conclusion”.</p>
+    <p>W3C only rescinds, supersedes, or obsoletes entire Recommendations.
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥②">Recommendation</a> can be both superseded and obsolete.
+	To rescind, supersede, or obsolete some part of a Recommendation,
+	W3C follows the process for <a href="#revising-rec">modifying a Recommendation</a>.</p>
+    <p class="note" role="note"><span>Note:</span> For the purposes of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs②">Obsolete</a> or <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup">Superseded Recommendation</a> has the status of an active <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥③">Recommendation</a>,
+	although it is not recommended for future implementation;
+	a <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec①">Rescinded Recommendation</a> ceases to be in effect
+	and no new licenses are granted under the Patent Policy.</p>
+    <div aria-label="Retiring a W3C Recommendation" role="region">
+     <svg viewBox="0 0 300 135" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Supersede, Obsolete or Rescind a W3C Recommendation</title>
+      <g role="list">
+       <g role="listitem">
+        <ellipse cx="40" cy="50" fill="#fff" id="rec-3" role="img" rx="30" ry="20" stroke="black" stroke-width="2">
+         <title>Recommendation (Rec)</title>
+        </ellipse>
+        <text aria-hidden="true" font-size="18" stroke-width=".3" text-anchor="middle" x="40" y="55">REC</text>
+        <g role="list">
+         <g role="listitem">
+          <title>A major problem and an AC review can lead to a Recommendation being Rescinded.
+								There are no new IPR licences issued under the W3C Patent Policy,
+								and reinstating the Recommendation requires going through the full Rec-track process again.</title>
+          <path d="M40,29v-5s0,-5 5,-5h150" fill="none" stroke="black" stroke-dasharray="3 1" stroke-width="2"></path>
+          <text font-size="8" text-anchor="middle" x="105" y="16">Major problem, AC review</text>
+          <polygon points="195,16 195,22 199,19"></polygon>
+          <rect fill="#fff" height="36" id="rescinded" role="img" stroke="black" stroke-width="2" width="80" x="200" y="4"></rect>
+          <title>Rescinded Recommendation - no new IPR licenses</title>
+          <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="240" y="19">Rescinded</text>
+          <path d="M198,42l84,-40" stroke="red" stroke-width="2"></path>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="28">No new IPR licenses</text>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="37">No reinstatement path</text>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="black" stroke-dasharray="4 4"></path>
+           <title>With little uptake, following AC review a specification may become an Obsolete Recommendation</title>
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="red" stroke-dasharray="2 6" stroke-dashoffset="3"></path>
+           <polygon points="204,75 200,72 200,78"></polygon>
+           <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="42">Minimal usage, AC review</text>
+           <rect fill="#fff" height="26" id="obsolete" rx="8" stroke="black" stroke-dasharray="3 3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <title>Obsolete Recommendation</title>
+           <rect fill="none" height="26" rx="8" stroke="red" stroke-dasharray="3 3" stroke-dashoffset="3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="242" y="84">Obsolete</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <path d="M204,82h-149s-5,0 -5,-5v-5" fill="none" stroke="black" stroke-dasharray="2 3"></path>
+             <title>If there is new uptake, with AC review an Obsolete Recommendation may return to normal Recommendation status</title>
+             <polygon points="50,70 47,74 53,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="79">New uptake, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M40,71v29s0,5 5,5h153" fill="none" stroke="black"></path>
+           <polygon points="199,105 195,102 195,108"></polygon>
+           <text font-size="8" text-anchor="middle" x="115" y="102">Replaced by a new version, AC review</text>
+           <rect fill="#fff" height="30" id="superseded" role="img" rx="3" stroke="#600" stroke-width="2" width="80" x="200" y="100">
+            <title>Superseded Recommendation</title>
+           </rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="240" y="119">Superseded</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <title>A Superseded Recommendation can become a normal Recommendation with AC review</title>
+             <path d="M199,125h-164s-5,0 -5,-5v-52" fill="none" stroke="black" stroke-dasharray="1 4"></path>
+             <polygon points="30,70 27,74 33,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="122">Oops! The Web still needs this, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+    </div>
+    <h5 class="heading settled" data-level="6.3.13.4" id="deactivation"><span class="secno">6.3.13.4. </span><span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span><a class="self-link" href="#deactivation"></a></h5>
+    <p>The process of rescinding, obsoleting,
+	superseding,
+	or restoring
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥④">Recommendation</a> can be initiated
+	either by a request from the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑧">Team</a> or via a request from any of the following:</p>
+    <ul>
+     <li> The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑦">Working Group</a> who produced,
+			or is chartered to maintain,
+			the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑤">Recommendation</a> 
+     <li> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑥">TAG</a>, if there is no such <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑧">Working Group</a> 
+     <li> Any individual who made a request to the relevant <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑨">Working Group</a> as described above,
+			or the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑦">TAG</a> if such a group does not exist, to obsolete, rescind, supersede, or restore a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑥">Recommendation</a>,
+			where the request was not answered within 90 days 
+     <li> 5% of the members of the Advisory Committee 
+    </ul>
+    <p id="proposed-rescinded-rec">The <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑨">Team</a> <em class="rfc2119">must</em> then
+	submit the request to the <a href="#AC">Advisory Committee</a> for review.
+	For any <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑥">Advisory Committee review</a> of a proposal to
+	rescind,
+	obsolete,
+	supersede,
+	or restore
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑦">Recommendation</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⓪">Team</a> <em class="rfc2119">must</em>: </p>
+    <ul>
+     <li> announce the proposal to all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⓪">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑨">Chairs</a>,
+			and to the Public,
+			as well as to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑦">Advisory Committee</a> 
+     <li> indicate that this is a proposal to
+			Rescind,
+			Obsolete,
+			Supersede,
+			or restore,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑧">Recommendation</a> as appropriate 
+     <li> identify the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑨">Recommendation</a> by URL 
+     <li> publish a rationale for the proposal 
+     <li> identify known dependencies
+			and solicit review from all dependent <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧①">Working Groups</a> 
+     <li> solicit public review 
+     <li> specify the deadline for review comments,
+			which <em class="rfc2119">must</em> be at least 28 days
+			after the announcement 
+    </ul>
+    <p>and <em class="rfc2119">should</em></p>
+    <ul>
+     <li> identify known implementations. 
+    </ul>
+    <p>If there was any <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑤">dissent</a> in the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑦">Advisory Committee review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪①">Team</a> <em class="rfc2119">must</em> publish
+	the substantive content of the dissent to W3C <strong>and the public</strong>,
+	and <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑦">formally address</a> the dissent
+	at least 14 days
+	before publication as an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs③">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec②">Rescinded Recommendation</a>.</p>
+    <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑦">Advisory Committee Appeal</a> of the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪②">Team</a>'s decision.</p>
+    <p>W3C <em class="rfc2119">must</em> publish an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs④">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec③">Rescinded Recommendation</a> 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 <em class="rfc2119">should</em> link
+	to the explanation of <a href="https://www.w3.org/2016/11/obsoleting-rescinding/">Obsoleting and Rescinding W3C Specifications</a> <a data-link-type="biblio" href="#biblio-obs-resc">[OBS-RESC]</a> as appropriate.</p>
+    <p>Once W3C has published a Rescinded Recommendation,
+	future W3C technical reports <em class="rfc2119">must not</em> include normative references
+	to that technical report.</p>
+    <p class="note" role="note"><span>Note:</span> W3C strives to ensure that all Technical Reports
+	will continue to be available at their version-specific URL.</p>
+    <h3 class="heading settled" data-level="6.4" id="note-track"><span class="secno">6.4. </span><span class="content"> The Note Track (Notes and Statements)</span><a class="self-link" href="#note-track"></a></h3>
+    <h4 class="heading settled" data-level="6.4.1" id="Note"><span class="secno">6.4.1. </span><span class="content"> Group Notes</span><a class="self-link" href="#Note"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Group Note | Note | W3C Note | Working Group Note | Interest Group Note | AB Note | TAG Note" id="WGNote">Group Note</dfn> (<abbr>NOTE</abbr>)
+	is published
+	to provide a stable reference for a useful document
+	that is not intended to be a formal standard.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧②">Working Groups</a>, <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①⓪">Interest Groups</a>,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑧">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③①">AB</a> <em class="rfc2119">may</em> publish work as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②">Notes</a>.
+	Examples include:</p>
+    <ul>
+     <li> supporting documentation for a specification,
+			such as explanations of design principles
+			or use cases and requirements 
+     <li> non-normative guides to good practices 
+    </ul>
+    <p>Some <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote③">Notes</a> are developed through successive <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Draft Note" data-noexport id="draft-note">Draft Notes</dfn> before publication as a full <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote④">Notes</a>,
+	while others are <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①③">published</a> directly as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑤">Note</a>.
+	There are few formal requirements to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①④">publish</a> a document as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑥">Note</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note">Draft Note</a>,
+	and they have no standing as a recommendation of W3C
+	but are simply documents preserved for historical reference.</p>
+    <p class="note" role="note"><span>Note:</span> The W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> does not apply any licensing requirements or commitments for <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑦">Notes</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note①">Draft Notes</a>.</p>
+    <h4 class="heading settled" data-level="6.4.2" id="publishing-notes"><span class="secno">6.4.2. </span><span class="content"> Publishing Notes</span><a class="self-link" href="#publishing-notes"></a></h4>
+    <p>In order to publish a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑧">Note</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note②">Draft Note</a>,
+	the group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record their decision
+			to request publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑨">Note</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note③">Draft Note</a>, and 
+     <li> <em class="rfc2119">should</em> publish documentation
+			of significant changes to the technical report
+			since any previous publication. 
+    </ul>
+    <p>Both <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⓪">Notes</a> and <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note④">Draft Notes</a> can be updated by republishing
+	as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①①">Note</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note⑤">Draft Note</a>.
+	A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑤">technical report</a> <em class="rfc2119">may</em> remain
+	a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①②">Note</a> indefinitely.</p>
+    <p>If a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①③">Note</a> produced by a <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group①">chartered group</a> is no longer in scope for any group,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪③">Team</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①④">Note</a> with <a href="#correction-classes">class 1</a> changes incorporated,
+	as well as with <a data-link-type="dfn" href="#erratum" id="ref-for-erratum④">errata</a> and <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction②">Team corrections</a> annotated.</p>
+    <h4 class="heading settled" data-level="6.4.3" id="w3c-statement"><span class="secno">6.4.3. </span><span class="content"> Elevating Group Notes to W3C Statement status</span><span id="memo"></span><a class="self-link" href="#w3c-statement"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Statement | W3C Statement" data-noexport id="statement">W3C Statement</dfn> is a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑤">Note</a> that has been endorsed by W3C as a whole.
+	In order to elevate a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑥">Note</a> to <a data-link-type="dfn" href="#statement" id="ref-for-statement①">W3C Statement</a> status,
+	A group <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑨">wide review</a>. 
+     <li> record the group’s decision to request publication as a <a data-link-type="dfn" href="#statement" id="ref-for-statement②">W3C Statement</a>. 
+     <li> show that all issues raised against the document
+			since its first publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑦">Note</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑧">formally addressed</a>. 
+     <li> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③③">Formal Objections</a>. 
+    </ul>
+    <p>A <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑧">Note</a> specifying implementable technology <em class="rfc2119">should not</em> be elevated to <a data-link-type="dfn" href="#statement" id="ref-for-statement③">W3C Statement</a> status;
+	if it does,
+	the request to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement④">Statement</a> <em class="rfc2119">must</em> include rationale
+	for why it should be elevated,
+	and why it is not on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑨">Recommendation track</a>.</p>
+    <p>Once these conditions are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪④">Team</a> <em class="rfc2119">must</em> then
+	begin an Advisory Committee Review on the question of
+	whether the document is appropriate to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑤">W3C Statement</a>.
+	During this review period,
+	the <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑨">Note</a> <em class="rfc2119">must not</em> be updated.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#statement" id="ref-for-statement⑥">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①②">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②②">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑧">Advisory Committee Appeal</a> of the decision.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑤">Team</a> must announce the publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑦">W3C Statement</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑧">Advisory Committee</a>, other W3C groups, and the public.</p>
+    <h4 class="heading settled" data-level="6.4.4" id="revising-memo"><span class="secno">6.4.4. </span><span class="content"> Revising W3C Statements</span><a class="self-link" href="#revising-memo"></a></h4>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision④">group decision</a> to do so,
+	groups can request publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑧">W3C Statement</a> with <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑤">editorial changes</a>—<wbr>including <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑦">candidate amendment</a>—<wbr>without any additional process.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑧">candidate amendment</a> can be folded into the main text of the <a data-link-type="dfn" href="#statement" id="ref-for-statement⑨">W3C Statement</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①⓪">Statement</a>,
+	including review by the community to ensure
+	the substantive and editorial soundness of the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑨">candidate amendments</a>.
+	To validate this, the group must request
+	an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑧">Advisory Committee review</a> of the changes it wishes to incorporate.
+	The specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①⓪">candidate amendments</a> under review <em class="rfc2119">must</em> be identified as <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①⓪">proposed amendments</a> just as in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections" id="ref-for-last-call-for-review-of-proposed-corrections①">Last Call for Review of Proposed Corrections</a>.</p>
+    <p>The decision to incorporate <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①①">proposed amendments</a> into <a data-link-type="dfn" href="#statement" id="ref-for-statement①①">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①③">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②③">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑨">Advisory Committee Appeal</a> of the decision.</p>
+    <h3 class="heading settled" data-level="6.5" id="registries"><span class="secno">6.5. </span><span class="content"> The Registry Track</span><a class="self-link" href="#registries"></a></h3>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry">registry</dfn> documents a data set
+	consisting of one or more associated <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry table" id="registry-table">registry tables</dfn>,
+	each table representing an updatable collection
+	of logically independent, consistently-structured <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry entry" id="registry-entry">registry entries</dfn>.
+	A registry has three associated components:</p>
+    <ul>
+     <li>the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①">registry definition</a>, defining how the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②">registry tables</a> are structured and maintained 
+     <li>one or more <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table③">registry tables</a>, holding the data set represented by the <a data-link-type="dfn" href="#registry" id="ref-for-registry①">registry</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data">registry data</dfn>) 
+     <li>one or more referencing specifications, which make use of the <a data-link-type="dfn" href="#registry" id="ref-for-registry②">registry</a> 
+    </ul>
+    <p>The purposes of maintaining a <a data-link-type="dfn" href="#registry" id="ref-for-registry③">registry</a> can include:</p>
+    <dl>
+     <dt>non-collision 
+     <dd> Avoiding the problem
+			of two entities using the same value with different semantics. 
+     <dt>non-duplication 
+     <dd> Avoiding the problem
+			of having two or more different values in use with the same semantics. 
+     <dt>information 
+     <dd> Providing a central index
+			where anyone can find out
+			what a value means
+			and what its formal definition is
+			(and where it is). 
+     <dt>submission 
+     <dd> Ease of adding new terms,
+			including by stakeholders external to the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian">custodian</a> organization. 
+     <dt>consensus 
+     <dd> Promoting a clear consensus of the community on the terms. 
+    </dl>
+    <p>This section of the W3C Process provides a specialized process
+	facilitating the publication and maintenance of such <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table④">registry tables</a>,
+	particularly those required by or closely related to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦⓪">W3C Recommendations</a>.</p>
+    <p class="note" role="note"><span>Note:</span> Not every table in a specification is a potential registry.
+	If the intent or effect is that the table enumerates
+	all the possibilities the authors of the specification expect or envisage,
+	then the table by itself is enough.
+	Similarly, if the table is managed by the Working Group
+	and only updated as part of specification update,
+	then the complexities of registry management are not needed.</p>
+    <h4 class="heading settled" data-level="6.5.1" id="reg-def"><span class="secno">6.5.1. </span><span class="content"> Registry Definitions</span><a class="self-link" href="#reg-def"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-definition">registry definition</dfn> defines what each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑤">registry table</a> is and how it is maintained.
+	It <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Define the scope and purpose of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑥">registry table</a>. 
+     <li> Define the fields of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑦">registry table</a> and their constraints
+			(e.g. values must be drawn from a defined set, or be unique,
+			or only reference publicly available resources,
+			etc.) 
+     <li>
+       Define the policy for changes to existing entries, such as 
+      <ul>
+       <li>whether entries can be deleted or deprecated 
+       <li>whether entries can be changed after being published, and what kinds of changes are allowed 
+       <li>whether previously-deleted unique identifiers can be re-used, or are reserved indefinitely 
+      </ul>
+     <li> Define the method and criteria by which changes are proposed, approved, and incorporated.
+			(For example, a <a data-link-type="dfn" href="#registry" id="ref-for-registry④">registry</a> could define
+			that changes to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry①">registry entries</a> can be proposed using a particular web form or email address,
+			that they must be accompanied by certain background information,
+			or that they do or do not need to be approved by any member of a particular Working Group.) 
+     <li>
+       Identify the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="custodian">custodian</dfn> of the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑧">registry table</a>:
+			the entity to which requests for <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change">registry changes</a> must be sent,
+			and which is responsible for evaluating whether such requests
+			satisfy the criteria defined in the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition②">registry definition</a>. 
+      <p>The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian①">custodian</a> may be the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧③">Working Group</a>, the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑥">Team</a>, or a delegated entity.
+			The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian②">custodian</a> for all <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑨">registry tables</a> in a single <a data-link-type="dfn" href="#registry" id="ref-for-registry⑤">registry</a> <em class="rfc2119">should</em> generally be the same entity.</p>
+    </ul>
+    <h4 class="heading settled" data-level="6.5.2" id="reg-pub"><span class="secno">6.5.2. </span><span class="content"> Publishing Registries</span><a class="self-link" href="#reg-pub"></a></h4>
+    <p><a data-link-type="dfn" href="#registry" id="ref-for-registry⑥">Registries</a> can be published either
+	as a stand-alone <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑥">technical report</a> on the <a data-link-type="dfn" href="#registry-track" id="ref-for-registry-track">Registry Track</a> called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-report">registry report</dfn>,
+	or incorporated as part of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦①">Recommendation</a> as a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-section">registry section</dfn>.</p>
+    <p>A <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report②">registry report</a> or <a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section①">registry section</a> is purely documentational,
+	is not subject to the W3C Patent Policy,
+	and <em class="rfc2119">must not</em> contain any requirements on implementations.
+	For the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>,
+	any <a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section②">registry section</a> in a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⓪">Recommendation track</a> document
+	is not a normative portion of that specification.</p>
+    <p>The <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report③">registry report</a> or <a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section③">registry section</a> <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Clearly label the <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report④">registry report</a>/<a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section④">section</a>,
+			its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⓪">tables</a>,
+			and its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition③">registry definitions</a> as such,
+			including a link to <a href="#registries">§ 6.5 The Registry Track</a> in this Process. 
+     <li> Include the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition④">registry definition</a> for each of its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①①">registry tables</a>. 
+     <li>
+       Provide the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data">registry data</a> by either: 
+      <ul>
+       <li> Including the entire contents of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①②">registry table</a>,
+					either inline in the report
+					(e.g. formatted as a table, or list, or other appropriate representation),
+					or in a machine-readable file published as part of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑦">technical report</a>,
+					or (preferably) both. 
+       <li> Linking to one or more standalone <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report">Registry Data Reports</a> containing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①③">registry tables</a> in human-readable form, machine-readable form,
+					or (preferably) both. 
+      </ul>
+     <li> Include, if the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①④">registry table</a> is provided in a machine-readable file,
+			a definition of the format of that file. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑦">Team</a> <em class="rfc2119">must</em> make available
+	a means for interested parties to be notified of any updates to a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑤">registry table</a>.</p>
+    <p class="note" role="note"><span>Note:</span> Since the Process does not impose requirements
+	on changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑥">registry table</a> other than those imposed by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑤">registry definition</a>,
+	acceptance of proposed <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change①">registry changes</a> on behalf of the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian③">custodian</a> and
+	publication of an updated <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report⑤">registry report</a> that contains
+	only <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change②">registry changes</a> since the previous publication
+	can be automated
+	if satisfaction of those rules can be automatically verified.</p>
+    <p>Rules for publication and advancement on the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-track">Registry Track</dfn> are identical to that of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①①">Recommendation Track</a> with the following exceptions:</p>
+    <ul>
+     <li> <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report⑥">Registry reports</a> are not subject to the <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>,
+			and therefore none of their publications correspond,
+			to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑦">First Public Working Draft</a>, <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①③">Working Draft</a>,
+			or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts③">Patent Review Draft</a> for the purposes of the <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>. 
+     <li> For the same reason,
+			there is no equivalent to <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec④">Rescinded Recommendation</a> nor to <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation①">Rescinded Candidate Recommendation</a> for <a data-link-type="dfn" href="#registry" id="ref-for-registry⑦">Registries</a>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①④">Working Draft</a> is called <dfn data-dfn-type="dfn" data-export id="draft-registry">Draft Registry<a class="self-link" href="#draft-registry"></a></dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②①">Candidate Recommendation</a> is called <dfn data-dfn-type="dfn" data-export id="candidate-registry">Candidate Registry<a class="self-link" href="#candidate-registry"></a></dfn>,
+			with <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑨">Candidate Recommendation Snapshot</a> and <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑦">Candidate Recommendation Draft</a> corresponding to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-snapshot">Candidate Registry Snapshot</dfn> and <dfn data-dfn-type="dfn" data-export id="candidate-registry-draft">Candidate Registry Draft<a class="self-link" href="#candidate-registry-draft"></a></dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦②">W3C Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="w3c-registry">W3C Registry</dfn>; <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs⑤">Obsolete Recommendation</a> and <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup①">Superseded Recommendation</a> correspond to <dfn data-dfn-type="dfn" data-export id="obsolete-registry">Obsolete Registry<a class="self-link" href="#obsolete-registry"></a></dfn> and <dfn data-dfn-type="dfn" data-export id="superseded-registry">Superseded Registry<a class="self-link" href="#superseded-registry"></a></dfn>. 
+     <li> There is no equivalent to the Proposed Recommendation phase.
+			Instead,
+			an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑨">Advisory Committee Review</a> is started
+			upon publication of each <a data-link-type="dfn" href="#candidate-registry-snapshot" id="ref-for-candidate-registry-snapshot">Candidate Registry Snapshot</a>. 
+     <li> Changes that add new features (i.e. <a href="#correction-classes">class 4 changes</a>) are allowed
+			in all <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry">W3C Registries</a>,
+			without needing the to explicitly indicate that this is allowed. 
+    </ul>
+    <h4 class="heading settled" data-level="6.5.3" id="reg-table-update"><span class="secno">6.5.3. </span><span class="content"> Updating Registry Tables</span><a class="self-link" href="#reg-table-update"></a></h4>
+    <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑦">registry table</a> that are in accordance with the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑥">registry definition</a>,
+	(i.e. <a href="#correction-classes">Class 5 changes</a>)
+	can be made by re-publishing the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑧">technical report</a> that contains the affected table,
+	without needing to satisfy any other requirements for the publication
+	(not even Working Group consensus, unless this is required by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑦">registry definition</a>).
+	Such <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change③">registry changes</a> do not trigger new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⓪">Advisory Committee Reviews</a>,
+	nor Exclusion Opportunities,
+	and do not require verification via an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①⓪">update request</a>,
+	even for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑨">technical reports</a> at maturities where this would normally be expected.
+	Such publications can be made
+	even in the absence of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧④">Working Group</a> chartered to maintain the registry
+	when the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian④">custodian</a> is another entity.</p>
+    <p class="note" role="note"><span>Note:</span> The custodian is only empowered to make <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change④">registry changes</a>.
+	If the Working Group establishing the registry wishes
+	to empower the custodian to add commentary on individual entries,
+	this needs to be part of the registry table’s definition.
+	If other changes are desired,
+	they must be requested of the responsible Working Group—<wbr>or in the absence of a Working Group, of the Team.</p>
+    <p>Changes to the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑧">registry tables</a> made in accordance with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①①">candidate</a> or <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①②">proposed amendments</a> to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑧">registry definition</a> which would not be allowed by the unamended <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑨">registry definition</a> <em class="rfc2119">must</em> be identified as such.</p>
+    <h4 class="heading settled" data-level="6.5.4" id="reg-data-reports"><span class="secno">6.5.4. </span><span class="content"> Registry Data Reports</span><a class="self-link" href="#reg-data-reports"></a></h4>
+    <p>When the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data①">registry data</a> is published in a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⓪">technical report</a> from its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⓪">registry definition</a>,
+	that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③①">report</a> is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data-report">Registry Data Report</dfn>.
+	This <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③②">technical report</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">Must</em> link to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①①">registry definition</a> establishing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑨">registry tables</a> that it contain. 
+     <li> <em class="rfc2119">May</em> contain informative introductory text, examples, and notes
+			about the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②⓪">registry tables</a> and <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry②">entries</a> that it contains.
+			(Changes to these parts are deemed to be <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑥">editorial changes</a>). 
+    </ul>
+    <p><a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report①">Registry Data Reports</a> do not have maturity stages in and of themselves;
+	The maturity stage of the <a data-link-type="dfn" href="#registry" id="ref-for-registry⑧">registry</a> whose <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data②">data</a> they record
+	is that of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③③">technical report</a> holding the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①②">registry definition</a>.</p>
+    <p>Anytime a change is made to a <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①③">registry definition</a>,
+	the Working Group <em class="rfc2119">must</em> update and republish
+	any document holding the corresponding <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②①">registry tables</a> to make it consistent with these changes.</p>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑤">group decision</a> to do so,
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑤">Working Group</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report②">Registry Data Report</a> to incorporate <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑦">editorial changes</a>.
+	If there is no <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑥">Working Group</a> chartered to maintain this registry,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑧">Team</a> <em class="rfc2119">may</em> do so instead.</p>
+    <h4 class="heading settled" data-level="6.5.5" id="reg-ref-specifications"><span class="secno">6.5.5. </span><span class="content"> Specifications that Reference Registries</span><a class="self-link" href="#reg-ref-specifications"></a></h4>
+    <p>Registries document values,
+	they do not define any architectural or interoperability requirements
+	related to those values.
+	All architectural and interoperability requirements
+	pertaining to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry③">registry entries</a> <em class="rfc2119">must</em> be contained in the specifications that reference the registry,
+	and are therefore subject to the processes
+	(including approval and intellectual property provisions)
+	applicable to those referencing specifications.</p>
+    <p>If there are entries that must be implemented,
+	or any other such restrictions,
+	they <em class="rfc2119">must</em> be defined or documented
+	in the referencing specification
+	without dependency on the registry.</p>
+    <div class="example" id="example-cbb39e74"><a class="self-link" href="#example-cbb39e74"></a> For example,
+		“All implementations must implement the <code>Basic-Method</code> as defined in the registry”
+		is not acceptable;
+		a change to the definition of the <code>Basic-Method</code> in the registry would then affect conformance.
+		Instead, the requirement must be complete in the specification,
+		directly or by reference to another specification.
+		For example
+		“All implementations must recognize the name <code>Basic-Method</code>,
+		and implement it as defined by section yy of IETF RFC xxxx”.
+		(The Registry should nonetheless contain Basic-Method as an entry.) </div>
+    <h3 class="heading settled" data-level="6.6" id="switching-tracks"><span class="secno">6.6. </span><span class="content"> Switching Tracks</span><a class="self-link" href="#switching-tracks"></a></h3>
+    <p>Given a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑥">Group decision</a> to do so, <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑦">Working Groups</a> can republish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③④">technical report</a> on a different track than the one it is on,
+	under the following restrictions:</p>
+    <ul>
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑤">technical report</a> that is or was
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦③">W3C Recommendation</a>, <a data-link-type="dfn" href="#statement" id="ref-for-statement①②">W3C Statement</a>, or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts④">Patent Review Draft</a> cannot switch tracks. 
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑥">technical report</a> should not switch away from the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①②">Recommendation Track</a> without due consideration of the Patent Policy implications
+			and approval of W3C’s legal counsel
+			if the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑧">Working Group</a> envisions a likelihood of returning to it later. 
+    </ul>
+    <p><a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑦">Technical reports</a> that switch tracks start at
+	their new track’s initial maturity stage,
+	while retaining any established identity (url, shortname, etc.).</p>
+    <h3 class="heading settled" data-level="6.7" id="further-reading"><span class="secno">6.7. </span><span class="content"> Further reading</span><a class="self-link" href="#further-reading"></a></h3>
+    <p>Refer to <a href="https://www.w3.org/Guide/transitions">"How to Organize a Recommendation Track Transition"</a> <a data-link-type="biblio" href="#biblio-transition">[TRANSITION]</a> in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide">[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 data-link-type="biblio" href="#biblio-rec-tips">[REC-TIPS]</a>.
+	Please see also the <a href="https://www.w3.org/2003/01/republishing/">Requirements for modification of W3C Technical Reports</a> <a data-link-type="biblio" href="#biblio-republishing">[REPUBLISHING]</a>.</p>
+    <h2 class="heading settled" data-level="7" id="dissemination"><span class="secno">7. </span><span class="content"> <span id="chapterDissemination"></span> Dissemination Policies</span><a class="self-link" href="#dissemination"></a></h2>
+    <h3 class="heading settled" data-level="7.1" id="pub-com"><span class="secno">7.1. </span><span class="content"> Public Communication</span><a class="self-link" href="#pub-com"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑨">Team</a> is responsible for managing communication within W3C
+	and with the general public
+	(e.g., news services, press releases, managing the website and access privileges, and managing calendars).
+	Members <em class="rfc2119">should</em> solicit review by the Team
+	prior to issuing press releases about their work within W3C.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①①⓪">Team</a> makes every effort to ensure the persistence and availability of the following public information:</p>
+    <ul>
+     <li> <a href="#Reports">W3C technical reports</a> whose publication has been approved.
+			Per <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231"><cite>W3C IPR Policies</cite></a>,
+			W3C technical reports (and software) are available free of charge to the general public. 
+     <li> A <a href="https://www.w3.org/Consortium/mission">mission statement</a> <a data-link-type="biblio" href="#biblio-mission">[MISSION]</a> that explains the purpose and mission of W3C,
+			the key benefits for Members,
+			and the organizational structure of W3C. 
+     <li> Legal documents,
+			including the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement">[MEMBER-AGREEMENT]</a> and documentation of any legal commitments W3C has with other entities. 
+     <li> The Process Document. 
+     <li> Public results of W3C activities and <a href="#GAEvents">Workshops</a>. 
+    </ul>
+    <p>To keep the Members abreast of W3C meetings, <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW">Workshops</a>,
+	and review deadlines,
+	the Team provides them with a regular (e.g., weekly) news service
+	and maintains a <a href="https://www.w3.org/participate/eventscal">calendar</a> <a data-link-type="biblio" href="#biblio-calendar">[CALENDAR]</a> of official W3C events.
+	Members are encouraged to send schedule and event information to the Team for inclusion on this calendar.</p>
+    <h3 class="heading settled" data-level="7.2" id="confidentiality-levels"><span class="secno">7.2. </span><span class="content"> Confidentiality Levels</span><a class="self-link" href="#confidentiality-levels"></a></h3>
+    <p>There are three principal levels of access to W3C information
+	(on the W3C website, in W3C meetings, etc.):
+	public,
+	Member-only,
+	and Team-only.</p>
+    <p>While much information made available by W3C is public,
+	“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Member-Only" id="Member-only">Member-only</dfn>” information
+	is available to authorized parties only,
+	including representatives of Member organizations, <a href="#invited-expert-wg">Invited Experts</a>,
+	the Advisory Board,
+	the TAG,
+	and the Team.
+	For example,
+	the <a href="#WGCharter">charter</a> of some Working Groups <em class="rfc2119">may</em> specify a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only④">Member-only</a> confidentiality level for group proceedings.</p>
+    <p>“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team-Only" id="Team-only">Team-only</dfn>” information
+	is available to the Team and other authorized parties.</p>
+    <p>Those authorized to access <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑤">Member-only</a> and <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only①">Team-only</a> information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> treat the information as confidential within W3C, 
+     <li> <em class="rfc2119">must</em> use reasonable efforts to maintain the proper level of confidentiality, and 
+     <li> <em class="rfc2119">must not</em> release this information to the general public or press. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①①①">Team</a> <em class="rfc2119">must</em> provide mechanisms
+	to protect the confidentiality of <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑥">Member-only</a> information
+	and ensure that authorized parties have proper access to this information.
+	Documents <em class="rfc2119">should</em> clearly indicate
+	whether they require <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑦">Member-only</a> confidentiality.
+	Individuals uncertain of the confidentiality level of a piece of information <em class="rfc2119">should</em> contact the Team.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②④">Advisory Committee representatives</a> <em class="rfc2119">may</em> authorize <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑧">Member-only</a> access to <a href="#member-rep">Member representatives</a> and other individuals employed by the Member
+	who are considered appropriate recipients.
+	For instance,
+	it is the responsibility of the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑤">Advisory Committee representative</a> and other employees
+	and official representatives of the organization
+	to ensure that Member-only news announcements
+	are distributed for internal use only within their organization.
+	Information about Member mailing lists is available
+	in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro">[INTRO]</a>.</p>
+    <h3 class="heading settled" data-level="7.3" id="confidentiality-change"><span class="secno">7.3. </span><span class="content"> Changing Confidentiality Level</span><a class="self-link" href="#confidentiality-change"></a></h3>
+    <p>As a benefit of membership,
+	W3C provides some <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only②">Team-only</a> and <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑨">Member-only</a> channels
+	for certain types of communication.
+	For example, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑥">Advisory Committee representatives</a> can send <a href="#ACReview">reviews</a> to a <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only③">Team-only</a> channel.
+	However, for W3C processes with a significant public component,
+	such as the technical report development process,
+	it is also important for information that affects decision-making to be publicly available.
+	The Team <em class="rfc2119">may</em> need to communicate <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only④">Team-only</a> information to a Working Group or the public.
+	Similarly, a Working Group whose proceedings are <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①⓪">Member-only</a> <em class="rfc2119">must</em> make public
+	information pertinent to the technical report development process.</p>
+    <p>This document clearly indicates which information <em class="rfc2119">must</em> be available to Members or the public,
+	even though that information was initially communicated on <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑤">Team-only</a> or <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①①">Member-only</a> channels.
+	Only the <a data-link-type="dfn" href="#team" id="ref-for-team①①②">Team</a> and parties authorized by the Team
+	may change the level of confidentiality of this information.
+	When doing so:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①①③">Team</a> <em class="rfc2119">must</em> use a version of the information
+			that was expressly provided by the author for the new confidentiality level.
+			In Calls for Review and other similar messages,
+			the Team <em class="rfc2119">should</em> remind recipients to provide such alternatives. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①①④">Team</a> <em class="rfc2119">must not</em> attribute the version
+			for the new confidentiality level to the author without the author’s consent. 
+     <li> If the author has not conveyed to the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑤">Team</a> a version
+			that is suitable for another confidentiality level,
+			the Team <em class="rfc2119">may</em> make available a version that reasonably communicates what is required,
+			while respecting the original level of confidentiality,
+			and without attribution to the original author. 
+    </ol>
+    <h2 class="heading settled" data-level="8" id="GAEvents"><span class="secno">8. </span><span class="content"> Workshops and Symposia</span><a class="self-link" href="#GAEvents"></a></h2>
+    <p>The Team organizes <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="EventsW">Workshops</dfn> and <dfn data-dfn-type="dfn" data-export data-lt="Symposium | Symposia" id="EventsS">Symposia<a class="self-link" href="#EventsS"></a></dfn> to promote early involvement in the development of W3C activities
+	from Members and the public.</p>
+    <p>The goal of a Workshop 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.
+	Organizers of the first type of Workshop <em class="rfc2119">may</em> solicit position papers for the Workshop program
+	and <em class="rfc2119">may</em> use those papers
+	to choose attendees and/or presenters.</p>
+    <p>The goal of a Symposium is usually
+	to educate interested parties about a particular subject.</p>
+    <p>The Call for Participation in a Workshop or Symposium <em class="rfc2119">may</em> indicate participation requirements or limits,
+	and expected deliverables
+	(e.g., reports and <a data-link-type="dfn" href="#minutes" id="ref-for-minutes③">minutes</a>).
+	Organization of an event does not guarantee
+	further investment by W3C in a particular topic,
+	but <em class="rfc2119">may</em> lead to proposals for new activities or groups.</p>
+    <p>Workshops and Symposia generally last one to three days.
+	If a Workshop is being organized to address the pressing concerns of Members,
+	the Team <em class="rfc2119">must</em> issue the Call for Participation
+	no later than <span class="time-interval">six weeks</span> prior to the Workshop’s scheduled start date.
+	For other Workshops and Symposia,
+	the Team <em class="rfc2119">must</em> issue a Call for Participation
+	no later than <span class="time-interval">eight weeks</span> prior to the meeting’s scheduled start date.
+	This helps ensure that speakers and authors
+	have adequate time to prepare position papers and talks.</p>
+    <h2 class="heading settled" data-level="9" id="Liaisons"><span class="secno">9. </span><span class="content"> Liaisons</span><a class="self-link" href="#Liaisons"></a></h2>
+    <p>W3C uses the term <dfn data-dfn-type="dfn" data-export id="liaison">liaison<a class="self-link" href="#liaison"></a></dfn> 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 <a data-link-type="dfn" href="#team" id="ref-for-team①①⑥">Team</a> due to requirements for public communication;
+	patent,
+	copyright,
+	and other IPR policies;
+	confidentiality agreements;
+	and mutual membership agreements.</p>
+    <p>W3C <em class="rfc2119">may</em> negotiate <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement">technical agreements</a> with another organization.
+	For purposes of the W3C Process,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="agreement" data-noexport id="technical-agreement">technical agreement</dfn> is a formal contract,
+	or a Memorandum of Understanding (<abbr id="mou">MoU</abbr>),
+	or a similar document,
+	between W3C and another party or parties,
+	that relates to the technical activity of the Consortium
+	(e.g., its publications, groups, or liaisons).
+	It specifies rights and obligations of each party toward the others.
+	These rights and obligations <em class="rfc2119">may</em> include joint deliverables,
+	an agreed share of technical responsibilities with due coordination,
+	and/or considerations for confidentiality and specific IPR.</p>
+    <p>Non-technical agreements, including
+	those between W3C and its <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member①">Members</a> for the purposes of membership,
+	between W3C and its Partners for the purposes of partnership <a data-link-type="biblio" href="#biblio-bylaws">[BYLAWS]</a>,
+	and other agreements related to the operation of the Consortium
+	or to the ordinary provision of services,
+	are not subject to these Process provisions.</p>
+    <p>When considering a <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①">technical agreement</a> (i.e., before the decision whether to sign is made),
+	the Team <em class="rfc2119">should</em> provide
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑨">Advisory Committee</a> with a draft of the proposed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement②">agreement</a>,
+	along with an explanation of how W3C would benefit from signing this <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement③">agreement</a>,
+	for their review and discussion.
+	After addressing any comments,
+	and subject to any management or governance procedures that apply
+	(e.g., formal review of proposed contracts by legal counsel or by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑦">Board</a>),
+	if the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑤">Team decides</a> to proceed with signing the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement④">agreement</a>,
+	the Team <em class="rfc2119">must</em> announce the intent to sign,
+	and provide the final text of the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑤">agreement</a>,
+	with an explanation of signing rationale, to
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④⓪">Advisory Committee</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑦">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①⓪">Advisory Committee Appeal</a> of the decision to sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑥">agreement</a>.
+	If the proposal is rejected on <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①①">appeal</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑦">Team</a> <em class="rfc2119">must not</em> sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑦">agreement</a> on behalf of W3C
+	unless directed to do so by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑧">Board</a>.
+	A signed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑧">agreement</a> <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> <a data-link-type="biblio" href="#biblio-liaison">[LIAISON]</a> and the guidelines W3C follows when creating a liaison is available on the Web.</p>
+    <h2 class="heading settled" data-level="10" id="Submission"><span class="secno">10. </span><span class="content"> Member Submission Process</span><a class="self-link" href="#Submission"></a></h2>
+    <p>The Member Submission process allows Members
+	to propose technology
+	or other ideas
+	for consideration by the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑧">Team</a>.
+	After review,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑨">Team</a> <em class="rfc2119">may</em> make the material available at the W3C website.
+	The formal process affords Members a record of their contribution
+	and gives them a mechanism for disclosing the details of the transaction with the Team
+	(including IPR claims).
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①②⓪">Team</a> also makes review comments on the Submitted materials available for W3C Members,
+	the public,
+	and the media.</p>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="MemberSubmission">Member Submission</dfn> consists of:</p>
+    <ul>
+     <li> One or more documents developed outside of the W3C process, and 
+     <li> Information about the documents,
+			provided by the Submitter. 
+    </ul>
+    <p>One or more Members (called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="submitter" id="submitter">Submitter(s)</dfn>) <em class="rfc2119">may</em> participate in a Member Submission.
+	Only W3C Members <em class="rfc2119">may</em> be listed as <a data-link-type="dfn" href="#submitter" id="ref-for-submitter">Submitters</a>.</p>
+    <p>The Submission process consists of the following steps:</p>
+    <ol>
+     <li> One of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①">Submitters</a> sends a request to the Team to acknowledge the Submission request.
+			The Team and <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②">Submitter</a>(s) communicate to ensure that the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission">Member Submission</a> is complete. 
+     <li>
+       After review, the <a data-link-type="dfn" href="#team" id="ref-for-team①②①">Team</a> <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> make the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission①">Member Submission</a> available
+					at the public W3C website,
+					in addition to Team comments about the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission②">Member Submission</a>. 
+       <li>If <a href="#SubmissionNo">rejected</a>,
+					the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter③">Submitter</a>(s) <em class="rfc2119">may</em> initiate a <a href="#SubmissionNo">Submission Appeal</a>. 
+      </ul>
+    </ol>
+    <div class="note" role="note">
+      Note: To avoid confusion about the Member Submission process, please note that: 
+     <ul>
+      <li> Documents in a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission③">Member Submission</a> are developed outside
+				of the W3C <a href="#Reports">technical report development process</a> (and therefore are not included in the <a href="https://www.w3.org/TR/">index of W3C technical reports</a> <a data-link-type="biblio" href="#biblio-tr">[TR]</a>). 
+      <li> The Submission process is <strong>not</strong> a means
+				by which Members ask for “ratification” of these documents
+				as <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦④">W3C Recommendations</a>. 
+      <li> There is no requirement or guarantee
+				that technology which is part of an acknowledged Submission request
+				will receive further consideration by W3C
+				(e.g., by a W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑨">Working Group</a>). 
+     </ul>
+    </div>
+    <p>Making a Member Submission available at the W3C website
+	does not imply endorsement by W3C,
+	including the W3C Team or Members.
+	The acknowledgment of a Submission request
+	does not imply that any action will be taken by W3C.
+	It merely records publicly
+	that the Submission request has been made by the Submitter.
+	A Member Submission made available by W3C <em class="rfc2119">must not</em> be referred to as “work in progress” of W3C.</p>
+    <p>The list of <a href="https://www.w3.org/Submission/">acknowledged Member Submissions</a> <a data-link-type="biblio" href="#biblio-submission-list">[SUBMISSION-LIST]</a> is available at the W3C website.</p>
+    <h3 class="heading settled" data-level="10.1" id="SubmissionRights"><span class="secno">10.1. </span><span class="content"> Submitter Rights and Obligations</span><a class="self-link" href="#SubmissionRights"></a></h3>
+    <p>When more than one Member jointly participates in a Submission request,
+	only one Member formally sends in the request.
+	That Member <em class="rfc2119">must</em> copy
+	each of the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑧">Advisory Committee representatives</a> of the other participating Members,
+	and each of those <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑨">Advisory Committee representatives</a> <em class="rfc2119">must</em> confirm
+	(by email to the Team)
+	their participation in the Submission request.</p>
+    <p>At any time prior to acknowledgment,
+	any <a data-link-type="dfn" href="#submitter" id="ref-for-submitter④">Submitter</a> <em class="rfc2119">may</em> withdraw support for a Submission request
+	(described in "<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>" <a data-link-type="biblio" href="#biblio-submission-req">[SUBMISSION-REQ]</a>).
+	A Submission request is “withdrawn” when no Submitter(s) support it.
+	The Team <em class="rfc2119">must not</em> make statements
+	about withdrawn Submission requests.</p>
+    <p>Prior to acknowledgment,
+	the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑤">Submitter</a>(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>,
+	refer to a document as “submitted to the World Wide Web Consortium”
+	or “under consideration by W3C” or any similar phrase
+	either in public or Member communication.
+	The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑥">Submitter</a>(s) <em class="rfc2119">must not</em> imply
+	in public or Member communication
+	that W3C is working (with the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑦">Submitter</a>(s)) on the material in the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission④">Member Submission</a>.
+	The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑧">Submitter</a>(s) <em class="rfc2119">may</em> release the documents in the Member Submission to the public
+	prior to acknowledgment
+	(without reference to the Submission request).</p>
+    <p>After acknowledgment,
+	the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑨">Submitter</a>(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>,
+	imply W3C investment in the Member Submission
+	until, and unless, the material has been adopted as a deliverable
+	of a W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨⓪">Working Group</a>.</p>
+    <h4 class="heading settled" data-level="10.1.1" id="SubmissionScope"><span class="secno">10.1.1. </span><span class="content"> Scope of Member Submissions</span><a class="self-link" href="#SubmissionScope"></a></h4>
+    <p>When a technology overlaps in scope with the work of a chartered Working Group,
+	Members <em class="rfc2119">should</em> <a href="#group-participation">participate in the Working Group</a> and contribute the technology to the group’s process
+	rather than seek publication through the Member Submission process.
+	The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨①">Working Group</a> <em class="rfc2119">may</em> incorporate the contributed technology into its deliverables.
+	If the Working Group does not incorporate the technology,
+	it <em class="rfc2119">should not</em> publish the contributed documents
+	as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②⓪">Working Group Notes</a> since <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②①">Working Group Notes</a> represent group output,
+	not input to the group.</p>
+    <p>On the other hand,
+	while W3C is in the early stages of developing a charter,
+	Members <em class="rfc2119">should</em> use the Submission process
+	to build consensus around concrete proposals for new work.</p>
+    <p>Members <em class="rfc2119">should not</em> submit materials
+	covering topics well outside the scope of <a href="https://www.w3.org/Consortium/mission">W3C’s mission</a> <a data-link-type="biblio" href="#biblio-mission">[MISSION]</a>.</p>
+    <h4 class="heading settled" data-level="10.1.2" id="SubmissionReqs"><span class="secno">10.1.2. </span><span class="content"> Information Required in a Submission Request</span><a class="self-link" href="#SubmissionReqs"></a></h4>
+    <p>The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⓪">Submitter</a>(s)
+	and any other authors of the submitted material <em class="rfc2119">must</em> agree that,
+	if the request is acknowledged,
+	the documents in the Member Submission will be subject to the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> <a data-link-type="biblio" href="#biblio-doc-license">[DOC-LICENSE]</a> and will include a reference to it.
+	The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①①">Submitter</a>(s) <em class="rfc2119">may</em> hold the copyright for the documents in a Member Submission.</p>
+    <p>The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments
+	in “Licensing Commitments in W3C Submissions”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①②">Submitter</a>(s) <em class="rfc2119">must</em> include the following information:</p>
+    <ul>
+     <li> The list of all submitting Members. 
+     <li> Position statements from all submitting Members (gathered by the Submitter).
+			All position statements <em class="rfc2119">must</em> appear in a separate document. 
+     <li> Complete electronic copies of any documents submitted for consideration
+			(e.g., a technical specification,
+			a position paper,
+			etc.)
+			If the Submission request is acknowledged,
+			these documents will be made available by W3C
+			and therefore <em class="rfc2119">must</em> satisfy the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules">[PUBRULES]</a>. <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①③">Submitters</a> <em class="rfc2119">may</em> hold the copyright for the material contained in these documents,
+			but when made available by W3C,
+			these documents <em class="rfc2119">must</em> be subject to the provisions
+			of the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> <a data-link-type="biblio" href="#biblio-doc-license">[DOC-LICENSE]</a>. 
+    </ul>
+    <p>The request <em class="rfc2119">must</em> also answer the following questions.</p>
+    <ul>
+     <li> What proprietary technology is required to implement the areas addressed by the request,
+			and what terms are associated with its use?
+			Again, many answers are possible,
+			but the specific answer will affect the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑥">Team’s Decision</a>. 
+     <li> What resources, if any,
+			does the Submitter intend to make available
+			if W3C acknowledges the Submission request
+			and takes action on it? 
+     <li> What action would the Submitter like W3C to take
+			if the Submission request is acknowledged? 
+     <li> What mechanisms are there to make changes to the specification being submitted?
+			This includes, but is not limited to,
+			stating where change control will reside
+			if the request is acknowledged. 
+    </ul>
+    <p>For other administrative requirements related to Submission requests,
+	see “<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>” <a data-link-type="biblio" href="#biblio-member-sub">[MEMBER-SUB]</a>.</p>
+    <h3 class="heading settled" data-level="10.2" id="TeamSubmissionRights"><span class="secno">10.2. </span><span class="content"> Team Rights and Obligations</span><a class="self-link" href="#TeamSubmissionRights"></a></h3>
+    <p>Although they are not technical reports,
+	the documents in a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission⑤">Member Submission</a> <em class="rfc2119">must</em> fulfill the requirements established by the <a data-link-type="dfn" href="#team" id="ref-for-team①②②">Team</a>,
+	including the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules">[PUBRULES]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②③">Team</a> sends a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="validation-notice">validation notice</dfn> to the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①④">Submitter</a>(s)
+	once the Team has reviewed a Submission request
+	and judged it complete and correct.</p>
+    <p>Prior to a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑦">decision</a> to <a href="#SubmissionYes">acknowledge</a> or <a href="#SubmissionNo">reject</a> the request,
+	the request is <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑥">Team-only</a>,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team①②④">Team</a> <em class="rfc2119">must</em> hold it in the strictest confidentiality.
+	In particular,
+	the Team <em class="rfc2119">must not</em> comment to the media
+	about the Submission request.</p>
+    <h3 class="heading settled" data-level="10.3" id="SubmissionYes"><span class="secno">10.3. </span><span class="content"> Acknowledgment of a Submission Request</span><a class="self-link" href="#SubmissionYes"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑤">Team</a> <a href="#SubmissionYes">acknowledges</a> a Submission request
+	by sending an announcement to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④①">Advisory Committee</a>.
+	Though the announcement <em class="rfc2119">may</em> be made at any time,
+	the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑤">Submitter</a>(s) can expect an announcement between <span class="time-interval">four to six weeks</span> after the <a data-link-type="dfn" href="#validation-notice" id="ref-for-validation-notice">validation notice</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑥">Team</a> <em class="rfc2119">must</em> keep the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑥">Submitter</a>(s) informed
+	of when an announcement is likely to be made.</p>
+    <p>Once a Submission request has been acknowledged,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑦">Team</a> <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Make the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission⑥">Member Submission</a> available at the W3C website. 
+     <li> Make the Team comments about the Submission request available at the W3C website. 
+    </ul>
+    <p>If the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑦">Submitter</a>(s) wishes to modify
+	a document made available as the result of acknowledgment,
+	the Submitter(s) <em class="rfc2119">must</em> start the Submission process from the beginning,
+	even just to correct <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑧">editorial changes</a>.</p>
+    <h3 class="heading settled" data-level="10.4" id="SubmissionNo"><span class="secno">10.4. </span><span class="content"> Rejection of a Submission Request, and Submission Appeals</span><a class="self-link" href="#SubmissionNo"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑧">Team</a> <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 jeopardize the progress of the group. 
+     <li> The IPR statement made by the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑧">Submitter</a>(s) is inconsistent with W3C’s
+			Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a> and in particular the “Licensing Commitments in W3C Submissions”, <a href="https://www.w3.org/Consortium/Legal/copyright-documents">Document License</a> <a data-link-type="biblio" href="#biblio-doc-license">[DOC-LICENSE]</a>,
+			or other IPR policies. 
+     <li> The ideas expressed in the request are poor,
+			might harm the Web,
+			or run counter to <a href="https://www.w3.org/Consortium/mission">W3C’s mission</a> <a data-link-type="biblio" href="#biblio-mission">[MISSION]</a>. 
+     <li> The ideas expressed in the request lie well outside the scope of W3C’s mission. 
+    </ul>
+    <p>In case of a rejection,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑨">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⓪">Advisory Committee representative</a>(s)
+	of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑨">Submitter</a>(s).
+	If requested by the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②⓪">Submitter</a>(s),
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③⓪">Team</a> <em class="rfc2119">must</em> provide rationale
+	to the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②①">Submitter</a>(s) about the rejection.
+	Other than to the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②②">Submitter</a>(s),
+	the Team <em class="rfc2119">must not</em> make statements about why a Submission request was rejected.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③①">Advisory Committee representative</a>(s) of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②③">Submitters</a>(s) <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals">Submission Appeal</a>.
+	The procedure for handling <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="submission-appeals">Submission Appeals</dfn> is the same as for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③④">Formal Objections</a>,
+	except that an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①②">AC Appeal</a> is not possible
+	and both the Formal Objection and the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report④">Council Report</a> are confidential to the <a data-link-type="dfn" href="#team" id="ref-for-team①③①">Team</a>, <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑨">TAG</a>, and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③②">AB</a>.</p>
+    <h2 class="heading settled" data-level="11" id="GAProcess"><span class="secno">11. </span><span class="content"> Process Evolution</span><a class="self-link" href="#GAProcess"></a></h2>
+    <p>Revision of the W3C Process and related documents (see below) undergoes similar <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①④">consensus</a>-building processes as for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑧">technical reports</a>,
+	with the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③③">Advisory Board</a>—<wbr>acting as the sponsoring <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨②">Working Group</a>.
+	The documents may be developed by the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③④">AB</a> or by another group to whom the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑤">AB</a> has delegated development.
+	Review includes
+	soliciting input from the W3C community,
+	and in particular the Team.</p>
+    <p>The documents covered by this section are:</p>
+    <ul>
+     <li data-md>
+      <p>the W3C Process (this document)</p>
+     <li data-md>
+      <p>the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy">[PATENT-POLICY]</a></p>
+     <li data-md>
+      <p>the W3C Code of Ethics and Professional Conduct <a data-link-type="biblio" href="#biblio-cepc">[CEPC]</a></p>
+     <li data-md>
+      <p>The W3C Document License <a data-link-type="biblio" href="#biblio-doc-license">[DOC-LICENSE]</a></p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑥">Advisory Board</a> initiates review as follows:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③②">Team</a> sends a Call for Review to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④②">Advisory Committee</a> and other W3C groups. 
+     <li> After comments have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑨">formally addressed</a> and the document possibly modified,
+			the Team seeks endorsement from the Members by initiating an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②①">Advisory Committee review</a>.
+			The review period <em class="rfc2119">must</em> last at least <span class="time-interval">28 days</span>. 
+     <li> <a href="#ACReviewAfter">After the Advisory Committee review</a>,
+			following a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①④">W3C decision</a> to adopt the document(s),
+			the Team does so
+			and sends an announcement to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④③">Advisory Committee</a>.
+			Advisory Committee representatives <em class="rfc2119">may</em> initiate
+			an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①③">Advisory Committee Appeal</a> to W3C. 
+    </ol>
+    <p class="note" role="note"><span>Note:</span> As of June 2020,
+	the <a data-link-type="biblio" href="#biblio-patent-policy">Patent Policy</a> is developed in the <a href="https://www.w3.org/2004/pp/psig/">Patents and Standards Interest Group</a>,
+	the <a data-link-type="biblio" href="#biblio-cepc">Code of Ethics and Professional Conduct</a> in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
+	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.</p>
+    <h2 class="non-normative heading settled" data-level="12" id="acks"><span class="secno">12. </span><span class="content"> Acknowledgments</span><a class="self-link" href="#acks"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>The editors are grateful to the following people,
+	who as interested individuals and/or with the affiliation(s) listed,
+	have contributed to this proposal for a revised Process:
+	Brian Kardell,
+	Carine Bournez (W3C),
+	Charles McCathie Nevile (ConsenSys),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	David Singer (Apple),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Fuqiao Xue (W3C),
+	Jeff Jaffe (W3C),
+	Jeffrey Yasskin (Google),
+	Kevin Fleming (Bloomberg),
+	Léonie Watson (The Paciello Group),
+	Mark Nottingham (Cloudflare),
+	Michael Champion (Microsoft),
+	Nigel Megitt (BBC),
+	Philippe Le Hégaret (W3C),
+	Ralph Swick (W3C),
+	Samuel Weiler (W3C),
+	Sandro Hawke (W3C),
+	Shawn Lawton Henry,
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Virginia Fournier (Apple),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <p>The editors are sorry for forgetting any names,
+	and grateful to those who have listened patiently to conversations about this document
+	without feeling a need to add more.</p>
+    <p>The following individuals contributed to the development of earlier versions of the Process:
+	Alex Russell (Google),
+	Andreas Tai (Institut fuer Rundfunktechnik),
+	Andrew Betts (Fastly),
+	Ann Bassetti (The Boeing Company),
+	Anne van Kesteren,
+	Art Barstow (Nokia, unaffiliated),
+	Bede McCall (MITRE),
+	Ben Wilson,
+	Brad Hill (Facebook),
+	Brian Kardell (JQuery),
+	Carine Bournez (W3C),
+	Carl Cargill (Netscape, Sun Microsystems, Adobe),
+	Chris Lilley (W3C),
+	Chris Wilson (Google),
+	Claus von Riegen (SAP AG),
+	Coralie Mercier (W3C),
+	Cullen Jennings (Cisco),
+	Dan Appelquist (Telefonica, Samsung),
+	Dan Connolly (W3C),
+	Daniel Dardailler (W3C),
+	Daniel Glazman (Disruptive Innovations),
+	David Baron (Mozilla),
+	David Fallside (IBM),
+	David Singer (Apple),
+	David Singer (IBM),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Don Brutzman (Web3D),
+	Don Deutsch (Oracle),
+	Eduardo Gutentag (Sun Microsystems),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Florian Rivoal,
+	Fuqiao Xue (W3C),
+	Geoffrey Creighton (Microsoft),
+	Giri Mandyam (Qualcomm),
+	Gregg Kellogg,
+	Hadley Beeman,
+	Helene Workman (Apple),
+	Henri Sivonen (Mozilla),
+	Håkon Wium Lie (Opera Software),
+	Ian Hickson (Google),
+	Ian Jacobs (W3C),
+	Ivan Herman (W3C),
+	J Alan Bird (W3C),
+	Jay Kishigami 岸上順一 (NTT),
+	Jean-Charles Verdié (MStar),
+	Jean-François Abramatic (IBM, ILOG, W3C),
+	Jeff Jaffe (W3C),
+	Jim Bell (HP),
+	Jim Miller (W3C),
+	Joe Hall (CDT),
+	John Klensin (MCI),
+	Josh Soref (BlackBerry, unaffiliated),
+	Judy Brewer (W3C),
+	Judy Zhu 朱红儒 (Alibaba),
+	Kari Laihonen (Ericsson),
+	Karl Dubost (Mozilla),
+	Ken Laskey (MITRE),
+	Kevin Fleming (Bloomberg),
+	Klaus Birkenbihl (Fraunhofer Gesellschaft),
+	Larry Masinter (Adobe Systems),
+	Lauren Wood (unaffiliated),
+	Liam Quin (W3C),
+	Léonie Watson (The Paciello Group),
+	Marcos Cáceres (Mozilla),
+	Maria Courtemanche (IBM),
+	Mark Crawford (SAP),
+	Mark Nottingham,
+	Michael Champion (Microsoft),
+	Michael Geldblum (Oracle),
+	Mike West (Google),
+	Mitch Stoltz (EFF),
+	Natasha Rooney (GSMA),
+	Nigel Megitt (BBC),
+	Olle Olsson (SICS),
+	Ora Lassila (Nokia),
+	Paul Cotton (Microsoft),
+	Paul Grosso (Arbortext),
+	Peter Linss,
+	Peter Patel-Schneider,
+	Philippe Le Hégaret (W3C),
+	Qiuling Pan (Huawei),
+	Ralph Swick (W3C),
+	Renato Iannella (IPR Systems),
+	Rigo Wenning (W3C),
+	Rob Sanderson (J Paul Getty Trust),
+	Robin Berjon (W3C),
+	Sally Khudairi (W3C),
+	Sam Ruby (IBM),
+	Sam Sneddon,
+	Sandro Hawke (W3C),
+	Sangwhan Moon (Odd Concepts),
+	Scott Peterson (Google),
+	Steve Holbrook (IBM),
+	Steve Zilles (Adobe Systems)
+	Steven Pemberton (CWI),
+	TV Raman (Google),
+	Tantek Çelik (Mozilla),
+	Terence Eden (Her Majesty’s Government),
+	Thomas Reardon (Microsoft),
+	Tim Berners-Lee (W3C),
+	Tim Krauskopf (Spyglass),
+	Travis Leithead (Microsoft),
+	Virginia Fournier (Apple),
+	Virginie Galindo (Gemalto),
+	Wayne Carr (Intel),
+	Wendy Fong (Hewlett-Packard),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <h2 class="non-normative heading settled" data-level="13" id="changes"><span class="secno">13. </span><span class="content"> Changes</span><a class="self-link" href="#changes"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <h3 class="no-num heading settled" id="changes-2021"><span class="content"> Changes since the <a href="https://www.w3.org/2021/Process-20211102/">2 November 2021 Process</a></span><a class="self-link" href="#changes-2021"></a></h3>
+    <p>This document is based on the <a href="https://www.w3.org/2021/Process-20211102/">2 November 2021 Process</a>.
+	A <a href="https://github.com/w3c/w3process/issues?q=milestone%3A%22Process+2022%22+is%3Aclosed">list of issues addressed</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2F">diff from Process 2021 to this latest version</a>,
+	as well as
+	a <a href="https://github.com/w3c/w3process/compare/p2021...main">detailed log of all changes since then</a> are available. </p>
+    <p>In addition to a number of editorial adjustments
+	and minor teaks,
+	the following is a summary of the main differences:</p>
+    <h4 class="heading settled" id="dirfree-changes"><span class="content"> Changes related to the role of the Director</span><a class="self-link" href="#dirfree-changes"></a></h4>
+    <ul>
+     <li> <a href="#ACReviewAfter">Outcomes of AC Reviews</a> are no longer unconstrained decisions (by the Director),
+			but instead must be based on the content of the review,
+			with specific rules (based on current best practices)
+			about what can or cannot be adjusted post review,
+			and under what circumstances. 
+     <li> Rather than the Director, the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③③">W3C Council</a>,
+			which is composed of TAG+AB+CEO,
+			will now hear and resolve formal objections. 
+     <li> The W3C Council will also hear <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals①">Submission Appeals</a>,
+			which were previously handled separately by either the TAG or the AB,
+			depending on the grounds for the appeal. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③③">Team</a> rather than the Director is charged with <a href="#TAG-appointments">appointing</a> the 3 non-elected <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④⓪">TAG</a> members,
+			subject to ratification by the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④①">TAG</a> and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑦">AB</a>. 
+     <li> There is no longer an ex-officio seat for the Director on the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④②">TAG</a>,
+			but Tim Berners-Lee personally does continue to hold one. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③④">Team</a> rather than the Director is charged with verification that the various expectations of the Process
+			have been fulfilled for <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req⑤">Transition Requests</a> and <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①①">Update Requests</a>. 
+     <li> Require AB and TAG approval when the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑤">Team</a> wants to <a href="#rec-track-regression">lower the maturity stage</a> of a technical report without a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑦">Group Decision</a>. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③⑥">Team</a>, <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑧">AB</a>, or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④③">TAG</a> rather than the Director is now responsible
+			for proposing group creation and forcible closure; <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②②">AC Review</a> is now required for forcible <a href="#GeneralTermination">group closure</a> (it already was for group creation). 
+     <li> The <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑨">CEO</a> rather than the Director is charged with <a href="#discipline">disciplinary questions</a>. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③⑦">Team</a> rather than the Director is charged with negotiating <a data-link-type="dfn" href="https://www.w3.org/Consortium/Process/#mou" id="ref-for-mou①">MoUs</a> (now called <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑨">technical agreements</a>)
+			and other agreements related to the technical program. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③⑧">Team</a> rather than the Director is charged with handling various participation-related judgement calls
+			(see <a href="#MemberAssoc">§ 2.1.2.1 Membership Associations</a>, <a href="#coi">§ 3.1.1.2 Conflict of Interest Policy</a>, <a href="#member-rep">§ 3.1.1.3 Individuals Representing a Member Organization</a>, <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>, and <a href="#invited-expert-wg">§ 3.4.3.3 Invited Expert in a Working Group</a>). 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③⑨">Team</a> rather than the Director is charged with handling <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission⑦">Member Submission</a> requests
+			(but see also <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals②">Submission Appeals</a>). 
+    </ul>
+    <h4 class="heading settled" id="other-gov-changes"><span class="content"> Other Governance Changes</span><a class="self-link" href="#other-gov-changes"></a></h4>
+    <ul>
+     <li> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④④">TAG</a> now picks its own chair(s),
+			and the timing of AB and TAG chair selection is clarified. 
+     <li> Appointed <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④⑤">TAG</a> seats now have consecutive term limits. 
+     <li> Remove mentions of the Hosts,
+			add recognition of the existence of the W3C Inc. Board of Directors,
+			and adjust language for W3C being rooted in W3C Inc. 
+     <li> Codify that the AB is expected to pick up to two of its participants
+			as <a href="#ab-bod-liaison">liaisons for the board</a>. 
+     <li> Clarify interactions between AC / Team / Board about MoUs
+			(now called <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①⓪">technical agreements</a>). 
+    </ul>
+    <h4 class="heading settled" id="misc-changes"><span class="content"> Other miscellaneous changes</span><a class="self-link" href="#misc-changes"></a></h4>
+    <ul>
+     <li> Improve the definition of consensus
+			to make the notion usable even in contexts
+			where Formal Objections would be inappropriate
+			(such as inside a W3C Council,
+			or when the TAG or AB pick their chair),
+			and to avoid circular definitions. 
+     <li> Merge Chair Decision Appeal, Group Decision Appeal, and Formal Objection;
+			clarify what can be objected to. 
+     <li> Define editorial vs substantive changes for non-REC-track documents. 
+     <li> Expect supporting material to meeting minutes to be archived as the minutes are. 
+     <li> Encourage people requesting an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①④">AC Appeal</a> to share their request with the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④④">Advisory Committee</a> in addition to the <a data-link-type="dfn" href="#team" id="ref-for-team①④⓪">Team</a>. 
+     <li> Allow <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦⑤">Recommendations</a> to transition directly to <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①⑤">Working Draft</a> without having to go through <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②②">Candidate Recommendation</a> when making <a href="#revised-rec-substantive">substantive changes</a>. 
+     <li> Place the W3C Document License under the same <a href="#GAProcess">revision process and requirements</a> as this document, the CEPC, or the Patent Policy. 
+     <li> Similarly to the pre-existing requirement that a public record be made
+			about confidential Formal Objections about public things,
+			added a requirement that a member visible record be made
+			about confidential Formal Objections about member-visible things. 
+     <li> Stop excluding comments from AC Reps from those that have to be addressed
+			while <a href="#transition-pr">transitioning to Proposed Recommendation</a>;
+			just because there will be an opportunity to address them later
+			doesn’t mean they shouldn’t be handled at the first opportunity. 
+     <li> Clarify what the term <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period②">Candidate Recommendation review period</a> refers to. 
+     <li> Clarify how the advance notice period for <a data-link-type="dfn" href="https://www.w3.org/Consortium/Process/#mou" id="ref-for-mou②">MoU</a> works. 
+     <li> Various bits of information that were so far required
+			to be included in announcements of <a data-link-type="dfn" href="#dfn-charter-extension" id="ref-for-dfn-charter-extension①">charter extensions</a> are covered in the group’s homepage,
+			making it sufficient to point to that page
+			rather than having to inline everything in the announcement. 
+     <li> Be more rigorous in references to the Patent Policy,
+			using dated versions when appropriate. 
+     <li> Rename “Member Consortia” into <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑥">Member Associations</a> to align with terminology in the Bylaws
+			(and to avoid confusion with W3C itself). 
+     <li> Rename “maturity level” into “maturity stage”. 
+    </ul>
+    <h3 class="no-num heading settled" id="changes-previous"><span class="content"> Changes since earlier versions</span><span id="changes-2020"></span><span id="changes-2019"></span><span id="changes-2018"></span><span id="changes-2017"></span><a class="self-link" href="#changes-previous"></a></h3>
+    <p>Changes since earlier versions of the Process are detailed
+	in the <a href="https://www.w3.org/2021/Process-20211102/#changes">changes section of the previous version</a> of the Process.</p>
+   </main>
+   <div data-fill-with="conformance">
+    <h2 class="no-ref no-num heading settled" id="w3c-conformance"><span class="content">Conformance</span><a class="self-link" href="#w3c-conformance"></a></h2>
+    <h3 class="no-ref no-num heading settled" id="w3c-conventions"><span class="content">Document conventions</span><a class="self-link" href="#w3c-conventions"></a></h3>
+    <p>Conformance requirements are expressed
+    with a combination of descriptive assertions
+    and RFC 2119 terminology.
+    The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
+    in the normative parts of this document
+    are to be interpreted as described in RFC 2119.
+    However, for readability,
+    these words do not appear in all uppercase letters in this specification. </p>
+    <p>All of the text of this specification is normative
+    except sections explicitly marked as non-normative, examples, and notes. <a data-link-type="biblio" href="#biblio-rfc2119">[RFC2119]</a> </p>
+    <p>Examples in this specification are introduced with the words “for example”
+    or are set apart from the normative text
+    with <code>class="example"</code>,
+    like this: </p>
+    <div class="example" id="w3c-example">
+     <a class="self-link" href="#w3c-example"></a> 
+     <p>This is an example of an informative example. </p>
+    </div>
+    <p>Informative notes begin with the word “Note”
+    and are set apart from the normative text
+    with <code>class="note"</code>,
+    like this: </p>
+    <p class="note" role="note">Note, this is an informative note.</p>
+   </div>
+<script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script>
+  </main>
+  <h2 class="no-num no-ref heading settled" id="index"><span class="content">Index</span><a class="self-link" href="#index"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="content">Terms defined by this specification</span><a class="self-link" href="#index-defined-here"></a></h3>
+  <ul class="index">
+   <li><a href="#advisory-board">AB</a><span>, in § 3.3.1.1</span>
+   <li><a href="#WGNote">AB Note</a><span>, in § 6.4.1</span>
+   <li><a href="#advisory-committee">AC</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">AC Appeal</a><span>, in § 5.9</span>
+   <li><a href="#advisory-committee-representative">AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">AC Review</a><span>, in § 5.7</span>
+   <li><a href="#adequate-implementation">adequate implementation experience</a><span>, in § 6.3.2</span>
+   <li><a href="#adopted-draft">Adopted Draft</a><span>, in § 4.2</span>
+   <li><a href="#advisory-board">Advisory Board</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">Advisory Committee</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">Advisory Committee Appeal</a><span>, in § 5.9</span>
+   <li><a href="#advisory-committee-representative">Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">Advisory Committee review</a><span>, in § 5.7</span>
+   <li><a href="#technical-agreement">agreement</a><span>, in § 9</span>
+   <li><a href="#allow-new-features">allow new features</a><span>, in § 6.3.9</span>
+   <li><a href="#alternate-ac-representative">alt AC rep</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-appeal">Appeal</a><span>, in § 5.9</span>
+   <li><a href="#at-risk">at risk</a><span>, in § 6.3.7</span>
+   <li><a href="#bod">Board</a><span>, in § 2.2</span>
+   <li><a href="#bod">Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#bod">BoD</a><span>, in § 2.2</span>
+   <li><a href="#reviewform">Call for Review</a><span>, in § 5.7.1</span>
+   <li><a href="#candidate-addition">candidate addition</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-amendment">candidate amendment</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-correction">candidate correction</a><span>, in § 6.2.5</span>
+   <li><a href="#RecsCR">Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">Candidate Recommendation Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-review-period">Candidate Recommendation review period</a><span>, in § 6.3.7</span>
+   <li><a href="#candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-registry">Candidate Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-draft">Candidate Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-snapshot">Candidate Registry Snapshot</a><span>, in § 6.5.2</span>
+   <li><a href="#ceo">CEO</a><span>, in § 2.2</span>
+   <li><a href="#GeneralChairs">Chair</a><span>, in § 3.4.1</span>
+   <li><a href="#chair-decisions">chair decisions</a><span>, in § 5.1</span>
+   <li><a href="#charter">charter</a><span>, in § 4.2</span>
+   <li><a href="#chartered-group">chartered groups</a><span>, in § 3.4</span>
+   <li><a href="#dfn-charter-extension">charter extension</a><span>, in § 4.5</span>
+   <li><a href="#def-Consensus">Consensus</a><span>, in § 5.2.1</span>
+   <li><a href="#w3c-council">Council</a><span>, in § 5.6.2</span>
+   <li><a href="#council-report">Council Report</a><span>, in § 5.6.2.7</span>
+   <li><a href="#council-team-contact">Council Team Contact</a><span>, in § 5.6.2.1</span>
+   <li><a href="#RecsCR">CR</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">CRD</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-snapshot">CRS</a><span>, in § 6.3.1</span>
+   <li><a href="#custodian">custodian</a><span>, in § 6.5.1</span>
+   <li><a href="#discontinuedREC">Discontinued Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#dismissed">dismiss</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissal</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissed</a><span>, in § 5.6.2.3</span>
+   <li><a href="#def-Dissent">Dissent</a><span>, in § 5.2.1</span>
+   <li><a href="#distributed-meeting">distributed meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#draft-note">Draft Note</a><span>, in § 6.4.1</span>
+   <li><a href="#draft-registry">Draft Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#editors-draft">ED</a><span>, in § 6.3.1</span>
+   <li><a href="#editors-draft">Editor Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#editorial-change">editorial change</a><span>, in § 6.2.3</span>
+   <li><a href="#editors-draft">Editor’s Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#elected-group">elected groups</a><span>, in § 3.3</span>
+   <li><a href="#erratum">errata</a><span>, in § 6.2.4</span>
+   <li><a href="#erratum">erratum</a><span>, in § 6.2.4</span>
+   <li><a href="#exclusion-draft">Exclusion Draft</a><span>, in § 4.2</span>
+   <li><a href="#exclusion-draft-charter">Exclusion Draft Charter</a><span>, in § 4.2</span>
+   <li><a href="#ftf-meeting">face-to-face meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#fpwd">First Public Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#formally-addressed">formally addressed</a><span>, in § 5.3</span>
+   <li><a href="#FormalObjection">Formal Objection</a><span>, in § 5.5</span>
+   <li><a href="#fully-addressed">fully addressed</a><span>, in § 5.6.2.6</span>
+   <li><a href="#w3c-group">group</a><span>, in § 3</span>
+   <li><a href="#group-decision">group decision</a><span>, in § 5.1</span>
+   <li><a href="#WGNote">Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#WGNote">Interest Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsIG">Interest Groups</a><span>, in § 3.4</span>
+   <li><a href="#invited-expert-in-an-interest-group">Invited Expert in an Interest Group</a><span>, in § 3.4.3.4</span>
+   <li><a href="#invited-expert-in-a-working-group">Invited Expert in a Working Group</a><span>, in § 3.4.3.3</span>
+   <li><a href="#last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a><span>, in § 6.3.11.5</span>
+   <li><a href="#last-call-review">Last Call for Review of Proposed Amendments</a><span>, in § 6.3.11.5</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a><span>, in § 6.3.11.5</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a><span>, in § 6.3.11.5</span>
+   <li><a href="#liaison">liaison</a><span>, in § 9</span>
+   <li><a href="#w3c-member">Member</a><span>, in § 2.1</span>
+   <li><a href="#member-association">Member Association</a><span>, in § 2.1.2.1</span>
+   <li><a href="#member-association">Member Associations</a><span>, in § 2.1.2.1</span>
+   <li><a href="#Member-only">Member-Only</a><span>, in § 7.2</span>
+   <li><a href="#member-representative-in-an-interest-group">Member representative in an Interest Group</a><span>, in § 3.4.3.2</span>
+   <li><a href="#member-representative-in-a-working-group">Member representative in a Working Group</a><span>, in § 3.4.3.1</span>
+   <li><a href="#MemberSubmission">Member Submission</a><span>, in § 10</span>
+   <li><a href="#minority-opinion">Minority Opinion</a><span>, in § 5.6.2.6</span>
+   <li><a href="#minutes">minutes</a><span>, in § 3.1.2.2</span>
+   <li><a href="#WGNote">Note</a><span>, in § 6.4.1</span>
+   <li><a href="#not-required">not required</a><span>, in § Unnumbered section</span>
+   <li><a href="#RecsObs">Obsolete Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#obsolete-registry">Obsolete Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#overrule">overrule</a><span>, in § 5.6.2.6</span>
+   <li><a href="#participant">participant</a><span>, in § 3</span>
+   <li><a href="#igparticipant">participants in an Interest Group</a><span>, in § 3.4.2</span>
+   <li><a href="#wgparticipant">participants in a Working Group</a><span>, in § 3.4.2</span>
+   <li><a href="#inv-expert-info">participate in a Working Group as an Invited Expert</a><span>, in § 3.4.3.3</span>
+   <li><a href="#patent-review-drafts">Patent Review Drafts</a><span>, in § 6.3</span>
+   <li><a href="#RecsPR">PR</a><span>, in § 6.3.1</span>
+   <li><a href="#primary-affiliation">primary affiliation</a><span>, in § 3.3.3.3</span>
+   <li><a href="#proposed-additions">proposed additions</a><span>, in § 6.3.11.5</span>
+   <li><a href="#proposed-amendments">proposed amendments</a><span>, in § 6.3.11.5</span>
+   <li><a href="#proposed-corrections">proposed corrections</a><span>, in § 6.3.11.5</span>
+   <li><a href="#RecsPR">Proposed Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#proxy">proxy</a><span>, in § 5.2.3</span>
+   <li><a href="#public-participant-ig">public participants</a><span>, in § 3.4.2</span>
+   <li><a href="#publishing">publish</a><span>, in § 6.2.1</span>
+   <li><a href="#RecsW3C">REC</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsW3C">Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">Recommendation-track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">REC Track</a><span>, in § 6.3</span>
+   <li><a href="#registry">registry</a><span>, in § 6.5</span>
+   <li><a href="#registry-change">registry change</a><span>, in § 6.2.3</span>
+   <li><a href="#registry-data">registry data</a><span>, in § 6.5</span>
+   <li><a href="#registry-data-report">Registry Data Report</a><span>, in § 6.5.4</span>
+   <li><a href="#registry-definition">registry definition</a><span>, in § 6.5.1</span>
+   <li><a href="#registry-entry">registry entry</a><span>, in § 6.5</span>
+   <li><a href="#registry-report">registry report</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-section">registry section</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-table">registry table</a><span>, in § 6.5</span>
+   <li><a href="#registry-track">Registry Track</a><span>, in § 6.5.2</span>
+   <li><a href="#related-member">Related Member</a><span>, in § 2.1.2.2</span>
+   <li><a href="#renounce">renounce</a><span>, in § 5.6.2.3</span>
+   <li><a href="#renounce">renunciation</a><span>, in § 5.6.2.3</span>
+   <li><a href="#rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#RescindedRec">Rescinded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#group-decision">resolution</a><span>, in § 5.1</span>
+   <li><a href="#statement">Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#submission-appeals">Submission Appeals</a><span>, in § 10.4</span>
+   <li><a href="#submitter">submitter</a><span>, in § 10</span>
+   <li><a href="#subsidiary">subsidiary</a><span>, in § 2.1.2.2</span>
+   <li><a href="#substantive-change">substantive change</a><span>, in § 6.2.3</span>
+   <li><a href="#mtg-substitute">substitute</a><span>, in § 3.4.2</span>
+   <li><a href="#RecsSup">Superseded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#superseded-registry">Superseded Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#supplemental-confidential-council-report">Supplemental Confidential Council Report</a><span>, in § 5.6.2.7</span>
+   <li><a href="#EventsS">Symposia</a><span>, in § 8</span>
+   <li><a href="#EventsS">Symposium</a><span>, in § 8</span>
+   <li><a href="#technical-architecture-group">TAG</a><span>, in § 3.3.2.1</span>
+   <li><a href="#WGNote">TAG Note</a><span>, in § 6.4.1</span>
+   <li><a href="#team">Team</a><span>, in § 2.2</span>
+   <li><a href="#TeamContact">Team Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#team-correction">Team correction</a><span>, in § 6.2.5</span>
+   <li><a href="#team-decision">Team Decision</a><span>, in § 5.1</span>
+   <li><a href="#Team-only">Team-Only</a><span>, in § 7.2</span>
+   <li><a href="#team-representative-in-an-interest-group">Team representative in an Interest Group</a><span>, in § 3.4.3.6</span>
+   <li><a href="#team-representative-in-a-working-group">Team representative in a Working Group</a><span>, in § 3.4.3.5</span>
+   <li><a href="#team-decision">Team’s Decision</a><span>, in § 5.1</span>
+   <li><a href="#technical-agreement">technical agreement</a><span>, in § 9</span>
+   <li><a href="#technical-architecture-group">Technical Architecture Group</a><span>, in § 3.3.2.1</span>
+   <li><a href="#technical-report">Technical Report</a><span>, in § 6.2.1</span>
+   <li><a href="#trans-req">Transition Requests</a><span>, in § 6.3.3</span>
+   <li><a href="#def-Unanimity">Unanimity</a><span>, in § 5.2.1</span>
+   <li><a href="#update-requests">Update Requests</a><span>, in § 6.3.4</span>
+   <li><a href="#uphold">upheld</a><span>, in § 5.6.2.6</span>
+   <li><a href="#uphold">uphold</a><span>, in § 5.6.2.6</span>
+   <li><a href="#uphold">upholding</a><span>, in § 5.6.2.6</span>
+   <li><a href="#uphold">upholds</a><span>, in § 5.6.2.6</span>
+   <li><a href="#validation-notice">validation notice</a><span>, in § 10.2</span>
+   <li><a href="#bod">W3C Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#RecsCR">W3C Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-council">W3C Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">W3C Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#def-w3c-decision">W3C decision</a><span>, in § 5.1</span>
+   <li><a href="#fellows">W3C Fellows</a><span>, in § 2.2</span>
+   <li><a href="#w3c-group">W3C Group</a><span>, in § 3</span>
+   <li><a href="#w3c-member">W3C Member</a><span>, in § 2.1</span>
+   <li><a href="#WGNote">W3C Note</a><span>, in § 6.4.1</span>
+   <li><a href="#RecsPR">W3C Proposed Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsW3C">W3C Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">W3C Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-registry">W3C Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#statement">W3C Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#team">W3C Team</a><span>, in § 2.2</span>
+   <li><a href="#RecsWD">W3C Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsWD">WD</a><span>, in § 6.3.1</span>
+   <li><a href="#dfn-wide-review">wide review</a><span>, in § 6.2.2.1</span>
+   <li><a href="#RecsWD">Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#WGNote">Working Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsWG">Working Groups</a><span>, in § 3.4</span>
+   <li><a href="#EventsW">Workshops</a><span>, in § 8</span>
+  </ul>
+  <aside class="dfn-panel" data-for="term-for-patent-advisory-group">
+   <a href="https://www.w3.org/Consortium/Patent-Policy/#patent-advisory-group">https://www.w3.org/Consortium/Patent-Policy/#patent-advisory-group</a><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-patent-advisory-group">4.6. 
+Chartered Group Closure</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="term-for-mou">
+   <a href="https://www.w3.org/Consortium/Process/#mou">https://www.w3.org/Consortium/Process/#mou</a><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-mou">5.9. 
+Appeal by Advisory Committee Representatives</a>
+    <li><a href="#ref-for-mou①"> Changes related to the role of the Director</a>
+    <li><a href="#ref-for-mou②"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="term-for-mou">
+   <a href="https://www.w3.org/Consortium/Process/#mou">https://www.w3.org/Consortium/Process/#mou</a><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-mou">5.9. 
+Appeal by Advisory Committee Representatives</a>
+    <li><a href="#ref-for-mou①"> Changes related to the role of the Director</a>
+    <li><a href="#ref-for-mou②"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <h3 class="no-num no-ref heading settled" id="index-defined-elsewhere"><span class="content">Terms defined by reference</span><a class="self-link" href="#index-defined-elsewhere"></a></h3>
+  <ul class="index">
+   <li>
+    <a data-link-type="biblio">[w3c-patent-policy]</a> defines the following terms:
+    <ul>
+     <li><span class="dfn-paneled" id="term-for-patent-advisory-group">patent advisory group</span>
+    </ul>
+   <li>
+    <a data-link-type="biblio">[w3c-process]</a> defines the following terms:
+    <ul>
+     <li><span class="dfn-paneled" id="term-for-mou">memoranda of understanding</span>
+     <li><span class="dfn-paneled" id="term-for-mou①">mou</span>
+    </ul>
+  </ul>
+  <h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
+  <dl>
+   <dt id="biblio-cepc">[CEPC]
+   <dd><a href="https://www.w3.org/Consortium/cepc/"><cite>W3C Code of Ethics and Professional Conduct</cite></a>. URL: <a href="https://www.w3.org/Consortium/cepc/">https://www.w3.org/Consortium/cepc/</a>
+   <dt id="biblio-collaborators-agreement">[COLLABORATORS-AGREEMENT]
+   <dd><a href="https://www.w3.org/Consortium/Legal/collaborators-agreement"><cite>Invited expert and collaborators agreement</cite></a>. URL: <a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">https://www.w3.org/Consortium/Legal/collaborators-agreement</a>
+   <dt id="biblio-conflict-policy">[CONFLICT-POLICY]
+   <dd><a href="https://www.w3.org/2000/09/06-conflictpolicy"><cite>Conflict of Interest Policy for W3C Team Members Engaged in Outside Professional Activities</cite></a>. URL: <a href="https://www.w3.org/2000/09/06-conflictpolicy">https://www.w3.org/2000/09/06-conflictpolicy</a>
+   <dt id="biblio-doc-license">[DOC-LICENSE]
+   <dd><a href="https://www.w3.org/Consortium/Legal/copyright-documents"><cite>W3C Document License</cite></a>. URL: <a href="https://www.w3.org/Consortium/Legal/copyright-documents">https://www.w3.org/Consortium/Legal/copyright-documents</a>
+   <dt id="biblio-patent-policy">[PATENT-POLICY]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy/"><cite>The W3C Patent Policy</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy/">https://www.w3.org/Consortium/Patent-Policy/</a>
+   <dt id="biblio-patent-policy-2004">[PATENT-POLICY-2004]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy-20170801/"><cite>The W3C 2004 Patent Policy, Updated 2017</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy-20170801/">https://www.w3.org/Consortium/Patent-Policy-20170801/</a>
+   <dt id="biblio-patent-policy-2020">[PATENT-POLICY-2020]
+   <dd><a href=" https://www.w3.org/Consortium/Patent-Policy-20200915/"><cite>The W3C 2020 Patent Policy</cite></a>. URL: <a href=" https://www.w3.org/Consortium/Patent-Policy-20200915/"> https://www.w3.org/Consortium/Patent-Policy-20200915/</a>
+   <dt id="biblio-pubrules">[PUBRULES]
+   <dd><a href="https://www.w3.org/pubrules/"><cite>Publication Rules</cite></a>. URL: <a href="https://www.w3.org/pubrules/">https://www.w3.org/pubrules/</a>
+   <dt id="biblio-rfc2119">[RFC2119]
+   <dd>S. Bradner. <a href="https://datatracker.ietf.org/doc/html/rfc2119"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. March 1997. Best Current Practice. URL: <a href="https://datatracker.ietf.org/doc/html/rfc2119">https://datatracker.ietf.org/doc/html/rfc2119</a>
+   <dt id="biblio-rfc3797">[RFC3797]
+   <dd>D. Eastlake 3rd. <a href="https://www.rfc-editor.org/rfc/rfc3797"><cite>Publicly Verifiable Nominations Committee (NomCom) Random Selection</cite></a>. June 2004. Informational. URL: <a href="https://www.rfc-editor.org/rfc/rfc3797">https://www.rfc-editor.org/rfc/rfc3797</a>
+   <dt id="biblio-w3c-patent-policy">[W3C-PATENT-POLICY]
+   <dd>Wendy Seltzer. <a href="https://www.w3.org/Consortium/Patent-Policy/"><cite>W3C Patent Policy</cite></a>. 15 September 2020. URL: <a href="https://www.w3.org/Consortium/Patent-Policy/">https://www.w3.org/Consortium/Patent-Policy/</a>
+   <dt id="biblio-w3c-process">[W3C-PROCESS]
+   <dd>Elika J. Etemad (fantasai); Florian Rivoal. <a href="https://www.w3.org/Consortium/Process/"><cite>W3C Process Document</cite></a>. 2 November 2021. URL: <a href="https://www.w3.org/Consortium/Process/">https://www.w3.org/Consortium/Process/</a>
+  </dl>
+  <h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
+  <dl>
+   <dt id="biblio-ab-hp">[AB-HP]
+   <dd><a href="https://www.w3.org/2002/ab/"><cite>The Advisory Board home page</cite></a>. URL: <a href="https://www.w3.org/2002/ab/">https://www.w3.org/2002/ab/</a>
+   <dt id="biblio-ac-meeting">[AC-MEETING]
+   <dd><a href="https://www.w3.org/Member/Meeting/"><cite>Advisory Committee meetings (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/Meeting/">https://www.w3.org/Member/Meeting/</a>
+   <dt id="biblio-bg-cg">[BG-CG]
+   <dd><a href="https://www.w3.org/community/about/process/"><cite>Community and Business Group Process</cite></a>. URL: <a href="https://www.w3.org/community/about/process/">https://www.w3.org/community/about/process/</a>
+   <dt id="biblio-bylaws">[BYLAWS]
+   <dd><a href="https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a>. URL: <a href="https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf">https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf</a>
+   <dt id="biblio-calendar">[CALENDAR]
+   <dd><a href="https://www.w3.org/participate/eventscal"><cite>Calendar of all scheduled official W3C events</cite></a>. URL: <a href="https://www.w3.org/participate/eventscal">https://www.w3.org/participate/eventscal</a>
+   <dt id="biblio-chair">[CHAIR]
+   <dd><a href="https://www.w3.org/Guide/chair/role.html"><cite>W3C Working/Interest Group Chair</cite></a>. URL: <a href="https://www.w3.org/Guide/chair/role.html">https://www.w3.org/Guide/chair/role.html</a>
+   <dt id="biblio-charter">[CHARTER]
+   <dd><a href="https://www.w3.org/Guide/process/charter.html"><cite>How to Create a Working Group or Interest Group</cite></a>. URL: <a href="https://www.w3.org/Guide/process/charter.html">https://www.w3.org/Guide/process/charter.html</a>
+   <dt id="biblio-council-report-index">[COUNCIL-REPORT-INDEX]
+   <dd><a href="https://beta.w3.org/about/council/"><cite>Council Report Index</cite></a>. URL: <a href="https://beta.w3.org/about/council/">https://beta.w3.org/about/council/</a>
+   <dt id="biblio-current-ac">[CURRENT-AC]
+   <dd><a href="https://www.w3.org/Member/ACList"><cite>Current Advisory Committee representatives (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/ACList">https://www.w3.org/Member/ACList</a>
+   <dt id="biblio-decision-appeal">[DECISION-APPEAL]
+   <dd><a href="https://www.w3.org/Guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a>. URL: <a href="https://www.w3.org/Guide/process/ac-appeal">https://www.w3.org/Guide/process/ac-appeal</a>
+   <dt id="biblio-election-howto">[ELECTION-HOWTO]
+   <dd><a href="https://www.w3.org/2002/10/election-howto"><cite>How to Organize an Advisory Board or TAG election</cite></a>. URL: <a href="https://www.w3.org/2002/10/election-howto">https://www.w3.org/2002/10/election-howto</a>
+   <dt id="biblio-fellows">[FELLOWS]
+   <dd><a href="https://www.w3.org/Consortium/Recruitment/Fellows"><cite>W3C Fellows Program</cite></a>. URL: <a href="https://www.w3.org/Consortium/Recruitment/Fellows">https://www.w3.org/Consortium/Recruitment/Fellows</a>
+   <dt id="biblio-group-mail">[GROUP-MAIL]
+   <dd><a href="https://www.w3.org/groups/"><cite>Group mailing lists</cite></a>. URL: <a href="https://www.w3.org/groups/">https://www.w3.org/groups/</a>
+   <dt id="biblio-guide">[GUIDE]
+   <dd><a href="https://www.w3.org/Guide/"><cite>The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators</cite></a>. URL: <a href="https://www.w3.org/Guide/">https://www.w3.org/Guide/</a>
+   <dt id="biblio-intro">[INTRO]
+   <dd><a href="https://www.w3.org/Member/Intro"><cite>Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/Intro">https://www.w3.org/Member/Intro</a>
+   <dt id="biblio-join">[JOIN]
+   <dd><a href="https://www.w3.org/Consortium/join"><cite>How to Join W3C</cite></a>. URL: <a href="https://www.w3.org/Consortium/join">https://www.w3.org/Consortium/join</a>
+   <dt id="biblio-liaison">[LIAISON]
+   <dd><a href="https://www.w3.org/2001/11/StdLiaison"><cite>W3C liaisons with other organizations</cite></a>. URL: <a href="https://www.w3.org/2001/11/StdLiaison">https://www.w3.org/2001/11/StdLiaison</a>
+   <dt id="biblio-member-agreement">[MEMBER-AGREEMENT]
+   <dd><a href="https://www.w3.org/Consortium/Agreement/Member-Agreement"><cite>W3C Membership Agreement</cite></a>. URL: <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">https://www.w3.org/Consortium/Agreement/Member-Agreement</a>
+   <dt id="biblio-member-hp">[MEMBER-HP]
+   <dd><a href="https://www.w3.org/Member/"><cite>Member website (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/">https://www.w3.org/Member/</a>
+   <dt id="biblio-member-list">[MEMBER-LIST]
+   <dd><a href="https://www.w3.org/Consortium/Member/List"><cite>The list of current W3C Members</cite></a>. URL: <a href="https://www.w3.org/Consortium/Member/List">https://www.w3.org/Consortium/Member/List</a>
+   <dt id="biblio-member-sub">[MEMBER-SUB]
+   <dd><a href="https://www.w3.org/2000/09/submission"><cite>How to send a Submission request</cite></a>. URL: <a href="https://www.w3.org/2000/09/submission">https://www.w3.org/2000/09/submission</a>
+   <dt id="biblio-mission">[MISSION]
+   <dd><a href="https://www.w3.org/Consortium/mission"><cite>The W3C Mission statement</cite></a>. URL: <a href="https://www.w3.org/Consortium/mission">https://www.w3.org/Consortium/mission</a>
+   <dt id="biblio-obs-resc">[OBS-RESC]
+   <dd><a href="https://www.w3.org/2016/11/obsoleting-rescinding/"><cite>Obsoleting and Rescinding W3C Specifications</cite></a>. URL: <a href="https://www.w3.org/2016/11/obsoleting-rescinding/">https://www.w3.org/2016/11/obsoleting-rescinding/</a>
+   <dt id="biblio-rec-tips">[REC-TIPS]
+   <dd><a href="https://www.w3.org/2002/05/rec-tips"><cite>Tips for Getting to Recommendation Faster</cite></a>. URL: <a href="https://www.w3.org/2002/05/rec-tips">https://www.w3.org/2002/05/rec-tips</a>
+   <dt id="biblio-republishing">[REPUBLISHING]
+   <dd><a href="https://www.w3.org/2003/01/republishing/"><cite>In-place modification of W3C Technical Reports</cite></a>. URL: <a href="https://www.w3.org/2003/01/republishing/">https://www.w3.org/2003/01/republishing/</a>
+   <dt id="biblio-submission-list">[SUBMISSION-LIST]
+   <dd><a href="https://www.w3.org/Submission/"><cite>The list of acknowledged Member Submissions</cite></a>. URL: <a href="https://www.w3.org/Submission/">https://www.w3.org/Submission/</a>
+   <dt id="biblio-submission-req">[SUBMISSION-REQ]
+   <dd><a href="https://www.w3.org/2000/09/submission"><cite>Make or Withdraw a Member Submission Request (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/2000/09/submission">https://www.w3.org/2000/09/submission</a>
+   <dt id="biblio-tag-charter">[TAG-CHARTER]
+   <dd><a href="https://www.w3.org/2004/10/27-tag-charter.html"><cite>Technical Architecture Group (TAG) Charter</cite></a>. URL: <a href="https://www.w3.org/2004/10/27-tag-charter.html">https://www.w3.org/2004/10/27-tag-charter.html</a>
+   <dt id="biblio-tag-hp">[TAG-HP]
+   <dd><a href="https://www.w3.org/2001/tag/"><cite>The TAG home page</cite></a>. URL: <a href="https://www.w3.org/2001/tag/">https://www.w3.org/2001/tag/</a>
+   <dt id="biblio-team-contact">[TEAM-CONTACT]
+   <dd><a href="https://www.w3.org/Guide/teamcontact/role.html"><cite>Role of the Team Contact</cite></a>. URL: <a href="https://www.w3.org/Guide/teamcontact/role.html">https://www.w3.org/Guide/teamcontact/role.html</a>
+   <dt id="biblio-tr">[TR]
+   <dd><a href="https://www.w3.org/TR/"><cite>The W3C technical reports index</cite></a>. URL: <a href="https://www.w3.org/TR/">https://www.w3.org/TR/</a>
+   <dt id="biblio-transition">[TRANSITION]
+   <dd><a href="https://www.w3.org/Guide/transitions"><cite>Organize a Technical Report Transition</cite></a>. URL: <a href="https://www.w3.org/Guide/transitions">https://www.w3.org/Guide/transitions</a>
+   <dt id="biblio-translation">[TRANSLATION]
+   <dd><a href="https://www.w3.org/Consortium/Translation/"><cite>Translations of W3C technical reports</cite></a>. URL: <a href="https://www.w3.org/Consortium/Translation/">https://www.w3.org/Consortium/Translation/</a>
+   <dt id="biblio-w3c-ipr">[W3C-IPR]
+   <dd><a href="https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231"><cite>W3C IPR Policies</cite></a>. URL: <a href="https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231">https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231</a>
+  </dl>
+  <aside class="dfn-panel" data-for="w3c-member">
+   <b><a href="#w3c-member">#w3c-member</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-w3c-member">3.2.1. 
+Role of the Advisory Committee</a>
+    <li><a href="#ref-for-w3c-member①">9. 
+Liaisons</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="member-association">
+   <b><a href="#member-association">#member-association</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-member-association">2.1.2.1. 
+Membership Associations</a> <a href="#ref-for-member-association①">(2)</a> <a href="#ref-for-member-association②">(3)</a> <a href="#ref-for-member-association③">(4)</a> <a href="#ref-for-member-association④">(5)</a> <a href="#ref-for-member-association⑤">(6)</a>
+    <li><a href="#ref-for-member-association⑥"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="related-member">
+   <b><a href="#related-member">#related-member</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-related-member">2.1.2.2. 
+Related Members</a>
+    <li><a href="#ref-for-related-member①">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a> <a href="#ref-for-related-member②">(2)</a>
+    <li><a href="#ref-for-related-member③">5.8. 
+Advisory Committee Votes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="subsidiary">
+   <b><a href="#subsidiary">#subsidiary</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-subsidiary">2.1.2.2. 
+Related Members</a> <a href="#ref-for-subsidiary①">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="team">
+   <b><a href="#team">#team</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-team">1. 
+Introduction</a> <a href="#ref-for-team①">(2)</a> <a href="#ref-for-team②">(3)</a>
+    <li><a href="#ref-for-team③">2.2. 
+The W3C Team</a> <a href="#ref-for-team④">(2)</a>
+    <li><a href="#ref-for-team⑤">3.1.1.2. 
+Conflict of Interest Policy</a> <a href="#ref-for-team⑥">(2)</a> <a href="#ref-for-team⑦">(3)</a>
+    <li><a href="#ref-for-team⑧">3.1.3. 
+Tooling and Archiving for Discussions and Publications</a>
+    <li><a href="#ref-for-team⑨">3.1.4. 
+Resignation from a Group</a> <a href="#ref-for-team①⓪">(2)</a>
+    <li><a href="#ref-for-team①①">3.2.1. 
+Role of the Advisory Committee</a>
+    <li><a href="#ref-for-team①②">3.2.3. 
+Advisory Committee Mailing Lists</a> <a href="#ref-for-team①③">(2)</a> <a href="#ref-for-team①④">(3)</a>
+    <li><a href="#ref-for-team①⑤">3.2.4. 
+Advisory Committee Meetings</a> <a href="#ref-for-team①⑥">(2)</a> <a href="#ref-for-team①⑦">(3)</a>
+    <li><a href="#ref-for-team①⑧">3.3.1.2. 
+Composition of the Advisory Board</a>
+    <li><a href="#ref-for-team①⑨">3.3.1.3. 
+Communications of the Advisory Board</a>
+    <li><a href="#ref-for-team②⓪">3.3.2.2. 
+Composition of the Technical Architecture Group</a> <a href="#ref-for-team②①">(2)</a>
+    <li><a href="#ref-for-team②②">3.3.2.3. 
+Communications of the Technical Architecture Group</a>
+    <li><a href="#ref-for-team②③">3.3.3.1. 
+Expectations for Elected Groups Participants</a>
+    <li><a href="#ref-for-team②④">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a> <a href="#ref-for-team②⑤">(2)</a> <a href="#ref-for-team②⑥">(3)</a> <a href="#ref-for-team②⑦">(4)</a> <a href="#ref-for-team②⑧">(5)</a> <a href="#ref-for-team②⑨">(6)</a>
+    <li><a href="#ref-for-team③⓪">3.3.3.4. 
+Technical Architecture Group Appointments</a> <a href="#ref-for-team③①">(2)</a> <a href="#ref-for-team③②">(3)</a> <a href="#ref-for-team③③">(4)</a> <a href="#ref-for-team③④">(5)</a> <a href="#ref-for-team③⑤">(6)</a>
+    <li><a href="#ref-for-team③⑥">3.3.3.6. 
+Elected Groups Vacated Seats</a>
+    <li><a href="#ref-for-team③⑦">3.4.1. 
+Requirements for All Chartered Groups</a> <a href="#ref-for-team③⑧">(2)</a>
+    <li><a href="#ref-for-team③⑨">4.3. 
+Advisory Committee Review of a Charter</a> <a href="#ref-for-team④⓪">(2)</a>
+    <li><a href="#ref-for-team④①">4.4. 
+Call for Participation in a Chartered Group</a>
+    <li><a href="#ref-for-team④②">4.5. 
+Charter Extension</a> <a href="#ref-for-team④③">(2)</a>
+    <li><a href="#ref-for-team④④">4.6. 
+Chartered Group Closure</a>
+    <li><a href="#ref-for-team④⑤">5.1. 
+Types of Decisions</a> <a href="#ref-for-team④⑥">(2)</a>
+    <li><a href="#ref-for-team④⑦">5.5. 
+Registering Formal Objections</a>
+    <li><a href="#ref-for-team④⑧">5.6.1. 
+Investigation and Mediation by the Team</a> <a href="#ref-for-team④⑨">(2)</a> <a href="#ref-for-team⑤⓪">(3)</a>
+    <li><a href="#ref-for-team⑤①">5.6.2. 
+W3C Council</a>
+    <li><a href="#ref-for-team⑤②">5.6.2.1. 
+Council Composition</a> <a href="#ref-for-team⑤③">(2)</a>
+    <li><a href="#ref-for-team⑤④">5.6.2.2. 
+Extraordinary Delegation</a> <a href="#ref-for-team⑤⑤">(2)</a> <a href="#ref-for-team⑤⑥">(3)</a>
+    <li><a href="#ref-for-team⑤⑦">5.6.2.3. 
+Council Participation, Dismissal, and Renunciation</a> <a href="#ref-for-team⑤⑧">(2)</a> <a href="#ref-for-team⑤⑨">(3)</a>
+    <li><a href="#ref-for-team⑥⓪">5.6.2.6. 
+Council Deliberations</a> <a href="#ref-for-team⑥①">(2)</a> <a href="#ref-for-team⑥②">(3)</a> <a href="#ref-for-team⑥③">(4)</a> <a href="#ref-for-team⑥④">(5)</a>
+    <li><a href="#ref-for-team⑥⑤">5.6.2.7. 
+Council Decision Report</a>
+    <li><a href="#ref-for-team⑥⑥">5.7.1. 
+Start of a Review Period</a>
+    <li><a href="#ref-for-team⑥⑦">5.7.2. 
+After the Review Period</a> <a href="#ref-for-team⑥⑧">(2)</a> <a href="#ref-for-team⑥⑨">(3)</a>
+    <li><a href="#ref-for-team⑦⓪">5.9. 
+Appeal by Advisory Committee Representatives</a> <a href="#ref-for-team⑦①">(2)</a> <a href="#ref-for-team⑦②">(3)</a>
+    <li><a href="#ref-for-team⑦③">6.2.2.1. 
+Wide Review</a>
+    <li><a href="#ref-for-team⑦④">6.2.5. 
+Candidate Amendments</a> <a href="#ref-for-team⑦⑤">(2)</a>
+    <li><a href="#ref-for-team⑦⑥">6.2.6. 
+License Grants from Non-Participants</a>
+    <li><a href="#ref-for-team⑦⑦">6.3. 
+The W3C Recommendation Track</a>
+    <li><a href="#ref-for-team⑦⑧">6.3.2. 
+Implementation Experience</a>
+    <li><a href="#ref-for-team⑦⑨">6.3.3. 
+Advancement on the Recommendation Track</a> <a href="#ref-for-team⑧⓪">(2)</a> <a href="#ref-for-team⑧①">(3)</a>
+    <li><a href="#ref-for-team⑧②">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a> <a href="#ref-for-team⑧③">(2)</a> <a href="#ref-for-team⑧④">(3)</a> <a href="#ref-for-team⑧⑤">(4)</a>
+    <li><a href="#ref-for-team⑧⑥">6.3.4.1. 
+Streamlined Publication Approval</a>
+    <li><a href="#ref-for-team⑧⑦">6.3.5. 
+Publishing a First Public Working Draft</a>
+    <li><a href="#ref-for-team⑧⑧">6.3.7. 
+Transitioning to Candidate Recommendation</a>
+    <li><a href="#ref-for-team⑧⑨">6.3.8.1. 
+Publishing a Candidate Recommendation Snapshot</a>
+    <li><a href="#ref-for-team⑨⓪">6.3.9. 
+Transitioning to Proposed Recommendation</a> <a href="#ref-for-team⑨①">(2)</a>
+    <li><a href="#ref-for-team⑨②">6.3.10. 
+Transitioning to W3C Recommendation</a> <a href="#ref-for-team⑨③">(2)</a>
+    <li><a href="#ref-for-team⑨④">6.3.11.1. 
+Revising a Recommendation: Markup Changes</a>
+    <li><a href="#ref-for-team⑨⑤">6.3.11.2. 
+Revising a Recommendation: Editorial Changes</a>
+    <li><a href="#ref-for-team⑨⑥">6.3.11.3. 
+Revising a Recommendation: Substantive Changes</a>
+    <li><a href="#ref-for-team⑨⑦">6.3.12. 
+Regression on the Recommendation Track</a>
+    <li><a href="#ref-for-team⑨⑧">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a> <a href="#ref-for-team⑨⑨">(2)</a> <a href="#ref-for-team①⓪⓪">(3)</a> <a href="#ref-for-team①⓪①">(4)</a> <a href="#ref-for-team①⓪②">(5)</a>
+    <li><a href="#ref-for-team①⓪③">6.4.2. 
+Publishing Notes</a>
+    <li><a href="#ref-for-team①⓪④">6.4.3. 
+Elevating Group Notes to W3C Statement status</a> <a href="#ref-for-team①⓪⑤">(2)</a>
+    <li><a href="#ref-for-team①⓪⑥">6.5.1. 
+Registry Definitions</a>
+    <li><a href="#ref-for-team①⓪⑦">6.5.2. 
+Publishing Registries</a>
+    <li><a href="#ref-for-team①⓪⑧">6.5.4. 
+Registry Data Reports</a>
+    <li><a href="#ref-for-team①⓪⑨">7.1. 
+Public Communication</a> <a href="#ref-for-team①①⓪">(2)</a>
+    <li><a href="#ref-for-team①①①">7.2. 
+Confidentiality Levels</a>
+    <li><a href="#ref-for-team①①②">7.3. 
+Changing Confidentiality Level</a> <a href="#ref-for-team①①③">(2)</a> <a href="#ref-for-team①①④">(3)</a> <a href="#ref-for-team①①⑤">(4)</a>
+    <li><a href="#ref-for-team①①⑥">9. 
+Liaisons</a> <a href="#ref-for-team①①⑦">(2)</a>
+    <li><a href="#ref-for-team①①⑧">10. 
+Member Submission Process</a> <a href="#ref-for-team①①⑨">(2)</a> <a href="#ref-for-team①②⓪">(3)</a> <a href="#ref-for-team①②①">(4)</a>
+    <li><a href="#ref-for-team①②②">10.2. 
+Team Rights and Obligations</a> <a href="#ref-for-team①②③">(2)</a> <a href="#ref-for-team①②④">(3)</a>
+    <li><a href="#ref-for-team①②⑤">10.3. 
+Acknowledgment of a Submission Request</a> <a href="#ref-for-team①②⑥">(2)</a> <a href="#ref-for-team①②⑦">(3)</a>
+    <li><a href="#ref-for-team①②⑧">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a> <a href="#ref-for-team①②⑨">(2)</a> <a href="#ref-for-team①③⓪">(3)</a> <a href="#ref-for-team①③①">(4)</a>
+    <li><a href="#ref-for-team①③②">11. 
+Process Evolution</a>
+    <li><a href="#ref-for-team①③③"> Changes related to the role of the Director</a> <a href="#ref-for-team①③④">(2)</a> <a href="#ref-for-team①③⑤">(3)</a> <a href="#ref-for-team①③⑥">(4)</a> <a href="#ref-for-team①③⑦">(5)</a> <a href="#ref-for-team①③⑧">(6)</a> <a href="#ref-for-team①③⑨">(7)</a>
+    <li><a href="#ref-for-team①④⓪"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="ceo">
+   <b><a href="#ceo">#ceo</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-ceo">2.1.2.1. 
+Membership Associations</a>
+    <li><a href="#ref-for-ceo①">2.2. 
+The W3C Team</a>
+    <li><a href="#ref-for-ceo②">3.1.1.1. 
+Expectations and Discipline</a>
+    <li><a href="#ref-for-ceo③">3.1.1.3. 
+Individuals Representing a Member Organization</a>
+    <li><a href="#ref-for-ceo④">3.3.3.6. 
+Elected Groups Vacated Seats</a>
+    <li><a href="#ref-for-ceo⑤">3.4.3.3. 
+Invited Expert in a Working Group</a> <a href="#ref-for-ceo⑥">(2)</a>
+    <li><a href="#ref-for-ceo⑦">5.5. 
+Registering Formal Objections</a>
+    <li><a href="#ref-for-ceo⑧">5.6.2.1. 
+Council Composition</a>
+    <li><a href="#ref-for-ceo⑨"> Changes related to the role of the Director</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="fellows">
+   <b><a href="#fellows">#fellows</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-fellows">2.1.1. 
+Rights of Members</a>
+    <li><a href="#ref-for-fellows">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="bod">
+   <b><a href="#bod">#bod</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-bod">2.2. 
+The W3C Team</a>
+    <li><a href="#ref-for-bod①">3.3.1.1. 
+Role of the Advisory Board</a>
+    <li><a href="#ref-for-bod②">3.3.1.4. 
+Liaisons between the Advisory Board and the Board of Directors</a> <a href="#ref-for-bod③">(2)</a> <a href="#ref-for-bod④">(3)</a> <a href="#ref-for-bod⑤">(4)</a> <a href="#ref-for-bod⑥">(5)</a>
+    <li><a href="#ref-for-bod⑦">9. 
+Liaisons</a> <a href="#ref-for-bod⑧">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="w3c-group">
+   <b><a href="#w3c-group">#w3c-group</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-w3c-group">3.1.2. 
+Meetings</a>
+    <li><a href="#ref-for-w3c-group①">3.1.3. 
+Tooling and Archiving for Discussions and Publications</a>
+    <li><a href="#ref-for-w3c-group②">5.7.2. 
+After the Review Period</a> <a href="#ref-for-w3c-group③">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="participant">
+   <b><a href="#participant">#participant</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-participant">3.1.2. 
+Meetings</a>
+    <li><a href="#ref-for-participant①">5.2.3. 
+Deciding by Vote</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="ftf-meeting">
+   <b><a href="#ftf-meeting">#ftf-meeting</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-ftf-meeting">3.2.4. 
+Advisory Committee Meetings</a>
+    <li><a href="#ref-for-ftf-meeting">4.2. 
+Content of a Charter</a>
+    <li><a href="#ref-for-ftf-meeting">5.2.1. 
+Consensus</a>
+    <li><a href="#ref-for-ftf-meeting">5.6.2.1. 
+Council Composition</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="distributed-meeting">
+   <b><a href="#distributed-meeting">#distributed-meeting</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-distributed-meeting">5.2.1. 
+Consensus</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="minutes">
+   <b><a href="#minutes">#minutes</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-minutes">3.1.2.1. 
+Meeting Scheduling and Announcements</a>
+    <li><a href="#ref-for-minutes①">3.4.1. 
+Requirements for All Chartered Groups</a>
+    <li><a href="#ref-for-minutes②">5.2.3. 
+Deciding by Vote</a>
+    <li><a href="#ref-for-minutes③">8. 
+Workshops and Symposia</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="advisory-committee">
+   <b><a href="#advisory-committee">#advisory-committee</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-advisory-committee">2.1. 
+Members</a>
+    <li><a href="#ref-for-advisory-committee①">3.2.2. 
+Participation in the Advisory Committee</a>
+    <li><a href="#ref-for-advisory-committee②">3.2.3. 
+Advisory Committee Mailing Lists</a> <a href="#ref-for-advisory-committee③">(2)</a>
+    <li><a href="#ref-for-advisory-committee④">3.2.4. 
+Advisory Committee Meetings</a>
+    <li><a href="#ref-for-advisory-committee⑤">3.3. 
+Elected Groups: The AB and the TAG</a>
+    <li><a href="#ref-for-advisory-committee⑥">3.3.1.2. 
+Composition of the Advisory Board</a>
+    <li><a href="#ref-for-advisory-committee⑦">3.3.2.2. 
+Composition of the Technical Architecture Group</a>
+    <li><a href="#ref-for-advisory-committee⑧">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a> <a href="#ref-for-advisory-committee⑨">(2)</a>
+    <li><a href="#ref-for-advisory-committee①⓪">3.3.3.4. 
+Technical Architecture Group Appointments</a>
+    <li><a href="#ref-for-advisory-committee①①">4.3. 
+Advisory Committee Review of a Charter</a>
+    <li><a href="#ref-for-advisory-committee①②">4.5. 
+Charter Extension</a>
+    <li><a href="#ref-for-advisory-committee①③">5.6.2.2. 
+Extraordinary Delegation</a>
+    <li><a href="#ref-for-advisory-committee①④">5.6.2.6. 
+Council Deliberations</a>
+    <li><a href="#ref-for-advisory-committee①⑤">5.7. 
+Advisory Committee Reviews</a>
+    <li><a href="#ref-for-advisory-committee①⑥">5.7.1. 
+Start of a Review Period</a>
+    <li><a href="#ref-for-advisory-committee①⑦">5.7.2. 
+After the Review Period</a> <a href="#ref-for-advisory-committee①⑧">(2)</a> <a href="#ref-for-advisory-committee①⑨">(3)</a> <a href="#ref-for-advisory-committee②⓪">(4)</a> <a href="#ref-for-advisory-committee②①">(5)</a> <a href="#ref-for-advisory-committee②②">(6)</a> <a href="#ref-for-advisory-committee②③">(7)</a>
+    <li><a href="#ref-for-advisory-committee②④">5.8. 
+Advisory Committee Votes</a> <a href="#ref-for-advisory-committee②⑤">(2)</a>
+    <li><a href="#ref-for-advisory-committee②⑥">5.9. 
+Appeal by Advisory Committee Representatives</a> <a href="#ref-for-advisory-committee②⑦">(2)</a> <a href="#ref-for-advisory-committee②⑧">(3)</a> <a href="#ref-for-advisory-committee②⑨">(4)</a> <a href="#ref-for-advisory-committee③⓪">(5)</a>
+    <li><a href="#ref-for-advisory-committee③①">6.2.1. 
+Publication of Technical Reports</a>
+    <li><a href="#ref-for-advisory-committee③②">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-advisory-committee③③">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-advisory-committee③④">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a>
+    <li><a href="#ref-for-advisory-committee③⑤">6.3.7. 
+Transitioning to Candidate Recommendation</a>
+    <li><a href="#ref-for-advisory-committee③⑥">6.3.11.5. 
+Incorporating Candidate Amendments</a>
+    <li><a href="#ref-for-advisory-committee③⑦">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a>
+    <li><a href="#ref-for-advisory-committee③⑧">6.4.3. 
+Elevating Group Notes to W3C Statement status</a>
+    <li><a href="#ref-for-advisory-committee③⑨">9. 
+Liaisons</a> <a href="#ref-for-advisory-committee④⓪">(2)</a>
+    <li><a href="#ref-for-advisory-committee④①">10.3. 
+Acknowledgment of a Submission Request</a>
+    <li><a href="#ref-for-advisory-committee④②">11. 
+Process Evolution</a> <a href="#ref-for-advisory-committee④③">(2)</a>
+    <li><a href="#ref-for-advisory-committee④④"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="advisory-committee-representative">
+   <b><a href="#advisory-committee-representative">#advisory-committee-representative</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-advisory-committee-representative">3.1.1.1. 
+Expectations and Discipline</a>
+    <li><a href="#ref-for-advisory-committee-representative①">3.1.1.3. 
+Individuals Representing a Member Organization</a>
+    <li><a href="#ref-for-advisory-committee-representative②">3.2.1. 
+Role of the Advisory Committee</a> <a href="#ref-for-advisory-committee-representative③">(2)</a>
+    <li><a href="#ref-for-advisory-committee-representative④">3.2.2. 
+Participation in the Advisory Committee</a> <a href="#ref-for-advisory-committee-representative⑤">(2)</a>
+    <li><a href="#ref-for-advisory-committee-representative⑥">3.2.3. 
+Advisory Committee Mailing Lists</a> <a href="#ref-for-advisory-committee-representative⑦">(2)</a>
+    <li><a href="#ref-for-advisory-committee-representative⑧">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a> <a href="#ref-for-advisory-committee-representative⑨">(2)</a> <a href="#ref-for-advisory-committee-representative①⓪">(3)</a>
+    <li><a href="#ref-for-advisory-committee-representative①①">3.4.3.1. 
+Member Representative in a Working Group</a>
+    <li><a href="#ref-for-advisory-committee-representative①②">3.4.3.2. 
+Member Representative in an Interest Group</a>
+    <li><a href="#ref-for-advisory-committee-representative①③">5.6.2.8. 
+Appealing Council Decisions</a>
+    <li><a href="#ref-for-advisory-committee-representative①④">5.7.1. 
+Start of a Review Period</a>
+    <li><a href="#ref-for-advisory-committee-representative①⑤">5.9. 
+Appeal by Advisory Committee Representatives</a> <a href="#ref-for-advisory-committee-representative①⑥">(2)</a> <a href="#ref-for-advisory-committee-representative①⑦">(3)</a> <a href="#ref-for-advisory-committee-representative①⑧">(4)</a> <a href="#ref-for-advisory-committee-representative①⑨">(5)</a>
+    <li><a href="#ref-for-advisory-committee-representative②⓪">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-advisory-committee-representative②①">6.3.10. 
+Transitioning to W3C Recommendation</a>
+    <li><a href="#ref-for-advisory-committee-representative②②">6.4.3. 
+Elevating Group Notes to W3C Statement status</a>
+    <li><a href="#ref-for-advisory-committee-representative②③">6.4.4. 
+Revising W3C Statements</a>
+    <li><a href="#ref-for-advisory-committee-representative②④">7.2. 
+Confidentiality Levels</a> <a href="#ref-for-advisory-committee-representative②⑤">(2)</a>
+    <li><a href="#ref-for-advisory-committee-representative②⑥">7.3. 
+Changing Confidentiality Level</a>
+    <li><a href="#ref-for-advisory-committee-representative②⑦">9. 
+Liaisons</a>
+    <li><a href="#ref-for-advisory-committee-representative②⑧">10.1. 
+Submitter Rights and Obligations</a> <a href="#ref-for-advisory-committee-representative②⑨">(2)</a>
+    <li><a href="#ref-for-advisory-committee-representative③⓪">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a> <a href="#ref-for-advisory-committee-representative③①">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="advisory-board">
+   <b><a href="#advisory-board">#advisory-board</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-advisory-board">3.1.1.1. 
+Expectations and Discipline</a>
+    <li><a href="#ref-for-advisory-board①">3.3. 
+Elected Groups: The AB and the TAG</a>
+    <li><a href="#ref-for-advisory-board②">3.3.1.1. 
+Role of the Advisory Board</a> <a href="#ref-for-advisory-board③">(2)</a> <a href="#ref-for-advisory-board④">(3)</a>
+    <li><a href="#ref-for-advisory-board⑤">3.3.1.2. 
+Composition of the Advisory Board</a> <a href="#ref-for-advisory-board⑥">(2)</a> <a href="#ref-for-advisory-board⑦">(3)</a>
+    <li><a href="#ref-for-advisory-board⑧">3.3.1.3. 
+Communications of the Advisory Board</a>
+    <li><a href="#ref-for-advisory-board⑨">3.3.1.4. 
+Liaisons between the Advisory Board and the Board of Directors</a> <a href="#ref-for-advisory-board①⓪">(2)</a> <a href="#ref-for-advisory-board①①">(3)</a>
+    <li><a href="#ref-for-advisory-board①②">3.3.3.1. 
+Expectations for Elected Groups Participants</a>
+    <li><a href="#ref-for-advisory-board①③">3.3.3.2. 
+Elected Groups Participation Constraints</a> <a href="#ref-for-advisory-board①④">(2)</a> <a href="#ref-for-advisory-board①⑤">(3)</a>
+    <li><a href="#ref-for-advisory-board①⑥">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a> <a href="#ref-for-advisory-board①⑦">(2)</a>
+    <li><a href="#ref-for-advisory-board①⑧">3.3.3.4. 
+Technical Architecture Group Appointments</a>
+    <li><a href="#ref-for-advisory-board①⑨">3.3.3.5. 
+Verifiable Random Selection Procedure</a>
+    <li><a href="#ref-for-advisory-board②⓪">3.3.3.6. 
+Elected Groups Vacated Seats</a> <a href="#ref-for-advisory-board②①">(2)</a> <a href="#ref-for-advisory-board②②">(3)</a>
+    <li><a href="#ref-for-advisory-board②③">4.6. 
+Chartered Group Closure</a> <a href="#ref-for-advisory-board②④">(2)</a>
+    <li><a href="#ref-for-advisory-board②⑤">5.6.2. 
+W3C Council</a>
+    <li><a href="#ref-for-advisory-board②⑥">5.6.2.1. 
+Council Composition</a> <a href="#ref-for-advisory-board②⑦">(2)</a>
+    <li><a href="#ref-for-advisory-board②⑧">5.6.2.3. 
+Council Participation, Dismissal, and Renunciation</a> <a href="#ref-for-advisory-board②⑨">(2)</a>
+    <li><a href="#ref-for-advisory-board③⓪">6.3.12. 
+Regression on the Recommendation Track</a>
+    <li><a href="#ref-for-advisory-board③①">6.4.1. 
+Group Notes</a>
+    <li><a href="#ref-for-advisory-board③②">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a>
+    <li><a href="#ref-for-advisory-board③③">11. 
+Process Evolution</a> <a href="#ref-for-advisory-board③④">(2)</a> <a href="#ref-for-advisory-board③⑤">(3)</a> <a href="#ref-for-advisory-board③⑥">(4)</a>
+    <li><a href="#ref-for-advisory-board③⑦"> Changes related to the role of the Director</a> <a href="#ref-for-advisory-board③⑧">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="technical-architecture-group">
+   <b><a href="#technical-architecture-group">#technical-architecture-group</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-technical-architecture-group">3.1.1.1. 
+Expectations and Discipline</a>
+    <li><a href="#ref-for-technical-architecture-group①">3.3. 
+Elected Groups: The AB and the TAG</a>
+    <li><a href="#ref-for-technical-architecture-group②">3.3.2.1. 
+Role of the Technical Architecture Group</a> <a href="#ref-for-technical-architecture-group③">(2)</a> <a href="#ref-for-technical-architecture-group④">(3)</a> <a href="#ref-for-technical-architecture-group⑤">(4)</a>
+    <li><a href="#ref-for-technical-architecture-group⑥">3.3.2.2. 
+Composition of the Technical Architecture Group</a> <a href="#ref-for-technical-architecture-group⑦">(2)</a>
+    <li><a href="#ref-for-technical-architecture-group⑧">3.3.2.3. 
+Communications of the Technical Architecture Group</a> <a href="#ref-for-technical-architecture-group⑨">(2)</a> <a href="#ref-for-technical-architecture-group①⓪">(3)</a> <a href="#ref-for-technical-architecture-group①①">(4)</a>
+    <li><a href="#ref-for-technical-architecture-group①②">3.3.3.1. 
+Expectations for Elected Groups Participants</a>
+    <li><a href="#ref-for-technical-architecture-group①③">3.3.3.2. 
+Elected Groups Participation Constraints</a>
+    <li><a href="#ref-for-technical-architecture-group①④">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a> <a href="#ref-for-technical-architecture-group①⑤">(2)</a>
+    <li><a href="#ref-for-technical-architecture-group①⑥">3.3.3.4. 
+Technical Architecture Group Appointments</a> <a href="#ref-for-technical-architecture-group①⑦">(2)</a> <a href="#ref-for-technical-architecture-group①⑧">(3)</a> <a href="#ref-for-technical-architecture-group①⑨">(4)</a> <a href="#ref-for-technical-architecture-group②⓪">(5)</a> <a href="#ref-for-technical-architecture-group②①">(6)</a> <a href="#ref-for-technical-architecture-group②②">(7)</a>
+    <li><a href="#ref-for-technical-architecture-group②③">3.3.3.5. 
+Verifiable Random Selection Procedure</a>
+    <li><a href="#ref-for-technical-architecture-group②④">3.3.3.6. 
+Elected Groups Vacated Seats</a> <a href="#ref-for-technical-architecture-group②⑤">(2)</a> <a href="#ref-for-technical-architecture-group②⑥">(3)</a> <a href="#ref-for-technical-architecture-group②⑦">(4)</a>
+    <li><a href="#ref-for-technical-architecture-group②⑧">4.6. 
+Chartered Group Closure</a> <a href="#ref-for-technical-architecture-group②⑨">(2)</a>
+    <li><a href="#ref-for-technical-architecture-group③⓪">5.6.2. 
+W3C Council</a>
+    <li><a href="#ref-for-technical-architecture-group③①">5.6.2.1. 
+Council Composition</a> <a href="#ref-for-technical-architecture-group③②">(2)</a>
+    <li><a href="#ref-for-technical-architecture-group③③">5.6.2.3. 
+Council Participation, Dismissal, and Renunciation</a> <a href="#ref-for-technical-architecture-group③④">(2)</a>
+    <li><a href="#ref-for-technical-architecture-group③⑤">6.3.12. 
+Regression on the Recommendation Track</a>
+    <li><a href="#ref-for-technical-architecture-group③⑥">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a> <a href="#ref-for-technical-architecture-group③⑦">(2)</a>
+    <li><a href="#ref-for-technical-architecture-group③⑧">6.4.1. 
+Group Notes</a>
+    <li><a href="#ref-for-technical-architecture-group③⑨">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a>
+    <li><a href="#ref-for-technical-architecture-group④⓪"> Changes related to the role of the Director</a> <a href="#ref-for-technical-architecture-group④①">(2)</a> <a href="#ref-for-technical-architecture-group④②">(3)</a> <a href="#ref-for-technical-architecture-group④③">(4)</a>
+    <li><a href="#ref-for-technical-architecture-group④④"> Other Governance Changes</a> <a href="#ref-for-technical-architecture-group④⑤">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="primary-affiliation">
+   <b><a href="#primary-affiliation">#primary-affiliation</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-primary-affiliation">3.3.3.2. 
+Elected Groups Participation Constraints</a> <a href="#ref-for-primary-affiliation①">(2)</a>
+    <li><a href="#ref-for-primary-affiliation②">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="chartered-group">
+   <b><a href="#chartered-group">#chartered-group</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-chartered-group">4.1. 
+Initiating Charter Development</a>
+    <li><a href="#ref-for-chartered-group①">6.4.2. 
+Publishing Notes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="GroupsWG">
+   <b><a href="#GroupsWG">#GroupsWG</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-GroupsWG">1. 
+Introduction</a> <a href="#ref-for-GroupsWG①">(2)</a>
+    <li><a href="#ref-for-GroupsWG②">3.1.3. 
+Tooling and Archiving for Discussions and Publications</a>
+    <li><a href="#ref-for-GroupsWG③">3.3.3.4. 
+Technical Architecture Group Appointments</a>
+    <li><a href="#ref-for-GroupsWG">3.4. 
+Chartered Groups: Working Groups and Interest Groups</a>
+    <li><a href="#ref-for-GroupsWG④">3.4.2. 
+Participation in Chartered Groups</a>
+    <li><a href="#ref-for-GroupsWG⑤">3.4.3.1. 
+Member Representative in a Working Group</a> <a href="#ref-for-GroupsWG⑥">(2)</a>
+    <li><a href="#ref-for-GroupsWG⑦">3.4.3.3. 
+Invited Expert in a Working Group</a>
+    <li><a href="#ref-for-GroupsWG⑧">4.4. 
+Call for Participation in a Chartered Group</a> <a href="#ref-for-GroupsWG⑨">(2)</a>
+    <li><a href="#ref-for-GroupsWG①⓪">4.6. 
+Chartered Group Closure</a>
+    <li><a href="#ref-for-GroupsWG①①">5.1. 
+Types of Decisions</a> <a href="#ref-for-GroupsWG①②">(2)</a>
+    <li><a href="#ref-for-GroupsWG①③">6. 
+W3C Technical Reports</a>
+    <li><a href="#ref-for-GroupsWG①④">6.1. 
+Types of Technical Reports</a> <a href="#ref-for-GroupsWG①⑤">(2)</a> <a href="#ref-for-GroupsWG①⑥">(3)</a> <a href="#ref-for-GroupsWG①⑦">(4)</a>
+    <li><a href="#ref-for-GroupsWG①⑧">6.2.1. 
+Publication of Technical Reports</a>
+    <li><a href="#ref-for-GroupsWG①⑨">6.2.2. 
+Reviews and Review Responsibilities</a> <a href="#ref-for-GroupsWG②⓪">(2)</a>
+    <li><a href="#ref-for-GroupsWG②①">6.2.2.1. 
+Wide Review</a> <a href="#ref-for-GroupsWG②②">(2)</a> <a href="#ref-for-GroupsWG②③">(3)</a> <a href="#ref-for-GroupsWG②④">(4)</a>
+    <li><a href="#ref-for-GroupsWG②⑤">6.2.4. 
+Errata Management</a> <a href="#ref-for-GroupsWG②⑥">(2)</a> <a href="#ref-for-GroupsWG②⑦">(3)</a> <a href="#ref-for-GroupsWG②⑧">(4)</a>
+    <li><a href="#ref-for-GroupsWG②⑨">6.3. 
+The W3C Recommendation Track</a> <a href="#ref-for-GroupsWG③⓪">(2)</a> <a href="#ref-for-GroupsWG③①">(3)</a> <a href="#ref-for-GroupsWG③②">(4)</a>
+    <li><a href="#ref-for-GroupsWG③③">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-GroupsWG③④">(2)</a> <a href="#ref-for-GroupsWG③⑤">(3)</a> <a href="#ref-for-GroupsWG③⑥">(4)</a> <a href="#ref-for-GroupsWG③⑦">(5)</a>
+    <li><a href="#ref-for-GroupsWG③⑧">6.3.3. 
+Advancement on the Recommendation Track</a> <a href="#ref-for-GroupsWG③⑨">(2)</a> <a href="#ref-for-GroupsWG④⓪">(3)</a> <a href="#ref-for-GroupsWG④①">(4)</a>
+    <li><a href="#ref-for-GroupsWG④②">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a> <a href="#ref-for-GroupsWG④③">(2)</a> <a href="#ref-for-GroupsWG④④">(3)</a> <a href="#ref-for-GroupsWG④⑤">(4)</a>
+    <li><a href="#ref-for-GroupsWG④⑥">6.3.4.1. 
+Streamlined Publication Approval</a> <a href="#ref-for-GroupsWG④⑦">(2)</a> <a href="#ref-for-GroupsWG④⑧">(3)</a> <a href="#ref-for-GroupsWG④⑨">(4)</a> <a href="#ref-for-GroupsWG⑤⓪">(5)</a> <a href="#ref-for-GroupsWG⑤①">(6)</a> <a href="#ref-for-GroupsWG⑤②">(7)</a>
+    <li><a href="#ref-for-GroupsWG⑤③">6.3.5. 
+Publishing a First Public Working Draft</a>
+    <li><a href="#ref-for-GroupsWG⑤④">6.3.6. 
+Revising a Working Draft</a>
+    <li><a href="#ref-for-GroupsWG⑤⑤">6.3.7. 
+Transitioning to Candidate Recommendation</a> <a href="#ref-for-GroupsWG⑤⑥">(2)</a>
+    <li><a href="#ref-for-GroupsWG⑤⑦">6.3.8.1. 
+Publishing a Candidate Recommendation Snapshot</a>
+    <li><a href="#ref-for-GroupsWG⑤⑧">6.3.8.2. 
+Publishing a Candidate Recommendation Draft</a>
+    <li><a href="#ref-for-GroupsWG⑤⑨">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-GroupsWG⑥⓪">6.3.11.1. 
+Revising a Recommendation: Markup Changes</a> <a href="#ref-for-GroupsWG⑥①">(2)</a>
+    <li><a href="#ref-for-GroupsWG⑥②">6.3.11.2. 
+Revising a Recommendation: Editorial Changes</a> <a href="#ref-for-GroupsWG⑥③">(2)</a>
+    <li><a href="#ref-for-GroupsWG⑥④">6.3.11.3. 
+Revising a Recommendation: Substantive Changes</a> <a href="#ref-for-GroupsWG⑥⑤">(2)</a> <a href="#ref-for-GroupsWG⑥⑥">(3)</a>
+    <li><a href="#ref-for-GroupsWG⑥⑦">6.3.11.5. 
+Incorporating Candidate Amendments</a> <a href="#ref-for-GroupsWG⑥⑧">(2)</a> <a href="#ref-for-GroupsWG⑥⑨">(3)</a> <a href="#ref-for-GroupsWG⑦⓪">(4)</a>
+    <li><a href="#ref-for-GroupsWG⑦①">6.3.12. 
+Regression on the Recommendation Track</a>
+    <li><a href="#ref-for-GroupsWG⑦②">6.3.13. 
+Retiring Recommendation Track Documents</a>
+    <li><a href="#ref-for-GroupsWG⑦③">6.3.13.1. 
+Abandoning an Unfinished Recommendation</a> <a href="#ref-for-GroupsWG⑦④">(2)</a> <a href="#ref-for-GroupsWG⑦⑤">(3)</a> <a href="#ref-for-GroupsWG⑦⑥">(4)</a>
+    <li><a href="#ref-for-GroupsWG⑦⑦">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a> <a href="#ref-for-GroupsWG⑦⑧">(2)</a> <a href="#ref-for-GroupsWG⑦⑨">(3)</a> <a href="#ref-for-GroupsWG⑧⓪">(4)</a> <a href="#ref-for-GroupsWG⑧①">(5)</a>
+    <li><a href="#ref-for-GroupsWG⑧②">6.4.1. 
+Group Notes</a>
+    <li><a href="#ref-for-GroupsWG⑧③">6.5.1. 
+Registry Definitions</a>
+    <li><a href="#ref-for-GroupsWG⑧④">6.5.3. 
+Updating Registry Tables</a>
+    <li><a href="#ref-for-GroupsWG⑧⑤">6.5.4. 
+Registry Data Reports</a> <a href="#ref-for-GroupsWG⑧⑥">(2)</a>
+    <li><a href="#ref-for-GroupsWG⑧⑦">6.6. 
+Switching Tracks</a> <a href="#ref-for-GroupsWG⑧⑧">(2)</a>
+    <li><a href="#ref-for-GroupsWG⑧⑨">10. 
+Member Submission Process</a>
+    <li><a href="#ref-for-GroupsWG⑨⓪">10.1. 
+Submitter Rights and Obligations</a>
+    <li><a href="#ref-for-GroupsWG⑨①">10.1.1. 
+Scope of Member Submissions</a>
+    <li><a href="#ref-for-GroupsWG⑨②">11. 
+Process Evolution</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="GroupsIG">
+   <b><a href="#GroupsIG">#GroupsIG</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-GroupsIG">1. 
+Introduction</a>
+    <li><a href="#ref-for-GroupsIG">3.4. 
+Chartered Groups: Working Groups and Interest Groups</a>
+    <li><a href="#ref-for-GroupsIG①">3.4.2. 
+Participation in Chartered Groups</a>
+    <li><a href="#ref-for-GroupsIG②">4.4. 
+Call for Participation in a Chartered Group</a> <a href="#ref-for-GroupsIG③">(2)</a>
+    <li><a href="#ref-for-GroupsIG④">4.6. 
+Chartered Group Closure</a>
+    <li><a href="#ref-for-GroupsIG⑤">5.1. 
+Types of Decisions</a> <a href="#ref-for-GroupsIG⑥">(2)</a>
+    <li><a href="#ref-for-GroupsIG⑦">6.1. 
+Types of Technical Reports</a>
+    <li><a href="#ref-for-GroupsIG⑧">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-GroupsIG⑨">(2)</a>
+    <li><a href="#ref-for-GroupsIG①⓪">6.4.1. 
+Group Notes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="GeneralChairs">
+   <b><a href="#GeneralChairs">#GeneralChairs</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-GeneralChairs">3.1.1.2. 
+Conflict of Interest Policy</a>
+    <li><a href="#ref-for-GeneralChairs①">3.1.2. 
+Meetings</a>
+    <li><a href="#ref-for-GeneralChairs②">3.3.3.4. 
+Technical Architecture Group Appointments</a>
+    <li><a href="#ref-for-GeneralChairs③">3.4.1. 
+Requirements for All Chartered Groups</a> <a href="#ref-for-GeneralChairs④">(2)</a> <a href="#ref-for-GeneralChairs⑤">(3)</a> <a href="#ref-for-GeneralChairs⑥">(4)</a>
+    <li><a href="#ref-for-GeneralChairs⑦">3.4.2. 
+Participation in Chartered Groups</a> <a href="#ref-for-GeneralChairs⑧">(2)</a>
+    <li><a href="#ref-for-GeneralChairs⑨">3.4.3.1. 
+Member Representative in a Working Group</a>
+    <li><a href="#ref-for-GeneralChairs①⓪">3.4.3.3. 
+Invited Expert in a Working Group</a> <a href="#ref-for-GeneralChairs①①">(2)</a> <a href="#ref-for-GeneralChairs①②">(3)</a> <a href="#ref-for-GeneralChairs①③">(4)</a>
+    <li><a href="#ref-for-GeneralChairs①④">4.3. 
+Advisory Committee Review of a Charter</a>
+    <li><a href="#ref-for-GeneralChairs①⑤">4.4. 
+Call for Participation in a Chartered Group</a>
+    <li><a href="#ref-for-GeneralChairs①⑥">4.5. 
+Charter Extension</a> <a href="#ref-for-GeneralChairs①⑦">(2)</a>
+    <li><a href="#ref-for-GeneralChairs①⑧">5.1. 
+Types of Decisions</a> <a href="#ref-for-GeneralChairs①⑨">(2)</a>
+    <li><a href="#ref-for-GeneralChairs②⓪">5.2.2. 
+Managing Dissent</a> <a href="#ref-for-GeneralChairs②①">(2)</a>
+    <li><a href="#ref-for-GeneralChairs②②">5.2.3. 
+Deciding by Vote</a> <a href="#ref-for-GeneralChairs②③">(2)</a>
+    <li><a href="#ref-for-GeneralChairs②④">5.4. 
+Reopening a Decision When Presented With New Information</a> <a href="#ref-for-GeneralChairs②⑤">(2)</a>
+    <li><a href="#ref-for-GeneralChairs②⑥">5.6.2.5. 
+Council Chairing</a>
+    <li><a href="#ref-for-GeneralChairs②⑦">6.2.1. 
+Publication of Technical Reports</a> <a href="#ref-for-GeneralChairs②⑧">(2)</a>
+    <li><a href="#ref-for-GeneralChairs②⑨">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="TeamContact">
+   <b><a href="#TeamContact">#TeamContact</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-TeamContact">3.4.1. 
+Requirements for All Chartered Groups</a> <a href="#ref-for-TeamContact①">(2)</a>
+    <li><a href="#ref-for-TeamContact">3.4.2. 
+Participation in Chartered Groups</a>
+    <li><a href="#ref-for-TeamContact②">3.4.3.1. 
+Member Representative in a Working Group</a>
+    <li><a href="#ref-for-TeamContact③">3.4.3.3. 
+Invited Expert in a Working Group</a>
+    <li><a href="#ref-for-TeamContact④">4.3. 
+Advisory Committee Review of a Charter</a>
+    <li><a href="#ref-for-TeamContact⑤">4.4. 
+Call for Participation in a Chartered Group</a>
+    <li><a href="#ref-for-TeamContact⑥">4.5. 
+Charter Extension</a>
+    <li><a href="#ref-for-TeamContact">5.5. 
+Registering Formal Objections</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="wgparticipant">
+   <b><a href="#wgparticipant">#wgparticipant</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-wgparticipant">3. 
+Groups and Participation</a>
+    <li><a href="#ref-for-wgparticipant">4.3. 
+Advisory Committee Review of a Charter</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="igparticipant">
+   <b><a href="#igparticipant">#igparticipant</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-igparticipant">3. 
+Groups and Participation</a>
+    <li><a href="#ref-for-igparticipant">4.3. 
+Advisory Committee Review of a Charter</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="public-participant-ig">
+   <b><a href="#public-participant-ig">#public-participant-ig</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-public-participant-ig">4.2. 
+Content of a Charter</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="mtg-substitute">
+   <b><a href="#mtg-substitute">#mtg-substitute</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-mtg-substitute">5.2.3. 
+Deciding by Vote</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="member-representative-in-an-interest-group">
+   <b><a href="#member-representative-in-an-interest-group">#member-representative-in-an-interest-group</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-member-representative-in-an-interest-group">3.4.3.2. 
+Member Representative in an Interest Group</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="invited-expert-in-a-working-group">
+   <b><a href="#invited-expert-in-a-working-group">#invited-expert-in-a-working-group</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-invited-expert-in-a-working-group">3.4.3.3. 
+Invited Expert in a Working Group</a>
+    <li><a href="#ref-for-invited-expert-in-a-working-group①">3.4.3.4. 
+Invited Expert in an Interest Group</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="inv-expert-info">
+   <b><a href="#inv-expert-info">#inv-expert-info</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-inv-expert-info">3.3.3.3. 
+Advisory Board and Technical Architecture Group Elections</a>
+    <li><a href="#ref-for-inv-expert-info">3.4.3.3. 
+Invited Expert in a Working Group</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="charter">
+   <b><a href="#charter">#charter</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-charter">3.4.1. 
+Requirements for All Chartered Groups</a>
+    <li><a href="#ref-for-charter①">4.4. 
+Call for Participation in a Chartered Group</a>
+    <li><a href="#ref-for-charter②">5.7. 
+Advisory Committee Reviews</a>
+    <li><a href="#ref-for-charter③">6.3. 
+The W3C Recommendation Track</a>
+    <li><a href="#ref-for-charter④">6.3.3. 
+Advancement on the Recommendation Track</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="adopted-draft">
+   <b><a href="#adopted-draft">#adopted-draft</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-adopted-draft">4.2. 
+Content of a Charter</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="exclusion-draft">
+   <b><a href="#exclusion-draft">#exclusion-draft</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-exclusion-draft">4.2. 
+Content of a Charter</a> <a href="#ref-for-exclusion-draft①">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="dfn-charter-extension">
+   <b><a href="#dfn-charter-extension">#dfn-charter-extension</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-dfn-charter-extension">5.9. 
+Appeal by Advisory Committee Representatives</a>
+    <li><a href="#ref-for-dfn-charter-extension①"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="group-decision">
+   <b><a href="#group-decision">#group-decision</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-group-decision">3.1.2.2. 
+Meeting Minutes</a> <a href="#ref-for-group-decision①">(2)</a>
+    <li><a href="#ref-for-group-decision②">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-group-decision③">6.3.11.2. 
+Revising a Recommendation: Editorial Changes</a>
+    <li><a href="#ref-for-group-decision④">6.4.4. 
+Revising W3C Statements</a>
+    <li><a href="#ref-for-group-decision⑤">6.5.4. 
+Registry Data Reports</a>
+    <li><a href="#ref-for-group-decision⑥">6.6. 
+Switching Tracks</a>
+    <li><a href="#ref-for-group-decision⑦"> Changes related to the role of the Director</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="team-decision">
+   <b><a href="#team-decision">#team-decision</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-team-decision">2.2. 
+The W3C Team</a>
+    <li><a href="#ref-for-team-decision①">4.5. 
+Charter Extension</a>
+    <li><a href="#ref-for-team-decision②">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-team-decision③">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a>
+    <li><a href="#ref-for-team-decision④">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-team-decision⑤">9. 
+Liaisons</a>
+    <li><a href="#ref-for-team-decision⑥">10.1.2. 
+Information Required in a Submission Request</a>
+    <li><a href="#ref-for-team-decision⑦">10.2. 
+Team Rights and Obligations</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="def-w3c-decision">
+   <b><a href="#def-w3c-decision">#def-w3c-decision</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-def-w3c-decision">3.2.1. 
+Role of the Advisory Committee</a>
+    <li><a href="#ref-for-def-w3c-decision①">4.4. 
+Call for Participation in a Chartered Group</a>
+    <li><a href="#ref-for-def-w3c-decision②">4.6. 
+Chartered Group Closure</a>
+    <li><a href="#ref-for-def-w3c-decision③">5.7.2. 
+After the Review Period</a> <a href="#ref-for-def-w3c-decision④">(2)</a> <a href="#ref-for-def-w3c-decision⑤">(3)</a> <a href="#ref-for-def-w3c-decision⑥">(4)</a>
+    <li><a href="#ref-for-def-w3c-decision⑦">5.9. 
+Appeal by Advisory Committee Representatives</a> <a href="#ref-for-def-w3c-decision⑧">(2)</a>
+    <li><a href="#ref-for-def-w3c-decision⑨">6.3.10. 
+Transitioning to W3C Recommendation</a> <a href="#ref-for-def-w3c-decision①⓪">(2)</a>
+    <li><a href="#ref-for-def-w3c-decision①①">6.3.11.5. 
+Incorporating Candidate Amendments</a>
+    <li><a href="#ref-for-def-w3c-decision①②">6.4.3. 
+Elevating Group Notes to W3C Statement status</a>
+    <li><a href="#ref-for-def-w3c-decision①③">6.4.4. 
+Revising W3C Statements</a>
+    <li><a href="#ref-for-def-w3c-decision①④">11. 
+Process Evolution</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="def-Consensus">
+   <b><a href="#def-Consensus">#def-Consensus</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-def-Consensus">5.1. 
+Types of Decisions</a>
+    <li><a href="#ref-for-def-Consensus①">5.2.1. 
+Consensus</a> <a href="#ref-for-def-Consensus②">(2)</a>
+    <li><a href="#ref-for-def-Consensus③">5.7.2. 
+After the Review Period</a> <a href="#ref-for-def-Consensus④">(2)</a> <a href="#ref-for-def-Consensus⑤">(3)</a> <a href="#ref-for-def-Consensus⑥">(4)</a> <a href="#ref-for-def-Consensus⑦">(5)</a>
+    <li><a href="#ref-for-def-Consensus⑧">6. 
+W3C Technical Reports</a>
+    <li><a href="#ref-for-def-Consensus⑨">6.1. 
+Types of Technical Reports</a> <a href="#ref-for-def-Consensus①⓪">(2)</a>
+    <li><a href="#ref-for-def-Consensus①①">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-def-Consensus①②">(2)</a>
+    <li><a href="#ref-for-def-Consensus①③">6.3.6. 
+Revising a Working Draft</a>
+    <li><a href="#ref-for-def-Consensus①④">11. 
+Process Evolution</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="def-Unanimity">
+   <b><a href="#def-Unanimity">#def-Unanimity</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-def-Unanimity">5.2.1. 
+Consensus</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="def-Dissent">
+   <b><a href="#def-Dissent">#def-Dissent</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-def-Dissent">5.2.2. 
+Managing Dissent</a> <a href="#ref-for-def-Dissent①">(2)</a>
+    <li><a href="#ref-for-def-Dissent②">5.7.1. 
+Start of a Review Period</a>
+    <li><a href="#ref-for-def-Dissent③">5.7.2. 
+After the Review Period</a>
+    <li><a href="#ref-for-def-Dissent④">6.3.10. 
+Transitioning to W3C Recommendation</a>
+    <li><a href="#ref-for-def-Dissent⑤">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="proxy">
+   <b><a href="#proxy">#proxy</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-proxy">3.4.2. 
+Participation in Chartered Groups</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="formally-addressed">
+   <b><a href="#formally-addressed">#formally-addressed</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-formally-addressed">6.2.2. 
+Reviews and Review Responsibilities</a>
+    <li><a href="#ref-for-formally-addressed①">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-formally-addressed②">6.3.4.1. 
+Streamlined Publication Approval</a>
+    <li><a href="#ref-for-formally-addressed③">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-formally-addressed④">6.3.10. 
+Transitioning to W3C Recommendation</a>
+    <li><a href="#ref-for-formally-addressed⑤">6.3.11.5. 
+Incorporating Candidate Amendments</a> <a href="#ref-for-formally-addressed⑥">(2)</a>
+    <li><a href="#ref-for-formally-addressed⑦">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a>
+    <li><a href="#ref-for-formally-addressed⑧">6.4.3. 
+Elevating Group Notes to W3C Statement status</a>
+    <li><a href="#ref-for-formally-addressed⑨">11. 
+Process Evolution</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="FormalObjection">
+   <b><a href="#FormalObjection">#FormalObjection</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-FormalObjection">3.3.1.1. 
+Role of the Advisory Board</a>
+    <li><a href="#ref-for-FormalObjection①">3.3.2.1. 
+Role of the Technical Architecture Group</a>
+    <li><a href="#ref-for-FormalObjection②">3.4.1. 
+Requirements for All Chartered Groups</a>
+    <li><a href="#ref-for-FormalObjection③">5. 
+Decisions</a>
+    <li><a href="#ref-for-FormalObjection④">5.2.1. 
+Consensus</a>
+    <li><a href="#ref-for-FormalObjection⑤">5.2.2. 
+Managing Dissent</a>
+    <li><a href="#ref-for-FormalObjection⑥">5.5. 
+Registering Formal Objections</a> <a href="#ref-for-FormalObjection⑦">(2)</a> <a href="#ref-for-FormalObjection⑧">(3)</a> <a href="#ref-for-FormalObjection⑨">(4)</a> <a href="#ref-for-FormalObjection①⓪">(5)</a> <a href="#ref-for-FormalObjection①①">(6)</a> <a href="#ref-for-FormalObjection①②">(7)</a> <a href="#ref-for-FormalObjection①③">(8)</a> <a href="#ref-for-FormalObjection①④">(9)</a>
+    <li><a href="#ref-for-FormalObjection①⑤">5.6.1. 
+Investigation and Mediation by the Team</a> <a href="#ref-for-FormalObjection①⑥">(2)</a> <a href="#ref-for-FormalObjection①⑦">(3)</a>
+    <li><a href="#ref-for-FormalObjection①⑧">5.6.2. 
+W3C Council</a>
+    <li><a href="#ref-for-FormalObjection①⑨">5.6.2.2. 
+Extraordinary Delegation</a> <a href="#ref-for-FormalObjection②⓪">(2)</a>
+    <li><a href="#ref-for-FormalObjection②①">5.6.2.6. 
+Council Deliberations</a> <a href="#ref-for-FormalObjection②②">(2)</a>
+    <li><a href="#ref-for-FormalObjection②③">5.6.2.7. 
+Council Decision Report</a>
+    <li><a href="#ref-for-FormalObjection②④">5.7.1. 
+Start of a Review Period</a>
+    <li><a href="#ref-for-FormalObjection②⑤">5.7.2. 
+After the Review Period</a> <a href="#ref-for-FormalObjection②⑥">(2)</a> <a href="#ref-for-FormalObjection②⑦">(3)</a> <a href="#ref-for-FormalObjection②⑧">(4)</a>
+    <li><a href="#ref-for-FormalObjection②⑨">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-FormalObjection③⓪">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a>
+    <li><a href="#ref-for-FormalObjection③①">6.3.4.1. 
+Streamlined Publication Approval</a>
+    <li><a href="#ref-for-FormalObjection③②">6.3.12. 
+Regression on the Recommendation Track</a>
+    <li><a href="#ref-for-FormalObjection③③">6.4.3. 
+Elevating Group Notes to W3C Statement status</a>
+    <li><a href="#ref-for-FormalObjection③④">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="w3c-council">
+   <b><a href="#w3c-council">#w3c-council</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-w3c-council">3.3.1.1. 
+Role of the Advisory Board</a> <a href="#ref-for-w3c-council①">(2)</a>
+    <li><a href="#ref-for-w3c-council②">3.3.2.1. 
+Role of the Technical Architecture Group</a>
+    <li><a href="#ref-for-w3c-council③">5.6.1. 
+Investigation and Mediation by the Team</a> <a href="#ref-for-w3c-council④">(2)</a>
+    <li><a href="#ref-for-w3c-council⑤">5.6.2.1. 
+Council Composition</a> <a href="#ref-for-w3c-council⑥">(2)</a> <a href="#ref-for-w3c-council⑦">(3)</a> <a href="#ref-for-w3c-council⑧">(4)</a> <a href="#ref-for-w3c-council⑨">(5)</a> <a href="#ref-for-w3c-council①⓪">(6)</a>
+    <li><a href="#ref-for-w3c-council①①">5.6.2.2. 
+Extraordinary Delegation</a>
+    <li><a href="#ref-for-w3c-council①②">5.6.2.3. 
+Council Participation, Dismissal, and Renunciation</a> <a href="#ref-for-w3c-council①③">(2)</a> <a href="#ref-for-w3c-council①④">(3)</a>
+    <li><a href="#ref-for-w3c-council①⑤">5.6.2.5. 
+Council Chairing</a>
+    <li><a href="#ref-for-w3c-council①⑥">5.6.2.6. 
+Council Deliberations</a> <a href="#ref-for-w3c-council①⑦">(2)</a> <a href="#ref-for-w3c-council①⑧">(3)</a> <a href="#ref-for-w3c-council①⑨">(4)</a> <a href="#ref-for-w3c-council②⓪">(5)</a> <a href="#ref-for-w3c-council②①">(6)</a> <a href="#ref-for-w3c-council②②">(7)</a> <a href="#ref-for-w3c-council②③">(8)</a> <a href="#ref-for-w3c-council②④">(9)</a>
+    <li><a href="#ref-for-w3c-council②⑤">5.6.2.7. 
+Council Decision Report</a> <a href="#ref-for-w3c-council②⑥">(2)</a> <a href="#ref-for-w3c-council②⑦">(3)</a>
+    <li><a href="#ref-for-w3c-council②⑧">5.9. 
+Appeal by Advisory Committee Representatives</a>
+    <li><a href="#ref-for-w3c-council②⑨">6.3.3. 
+Advancement on the Recommendation Track</a> <a href="#ref-for-w3c-council③⓪">(2)</a>
+    <li><a href="#ref-for-w3c-council③①">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a> <a href="#ref-for-w3c-council③②">(2)</a>
+    <li><a href="#ref-for-w3c-council③③"> Changes related to the role of the Director</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="council-team-contact">
+   <b><a href="#council-team-contact">#council-team-contact</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-council-team-contact">5.6.2.5. 
+Council Chairing</a>
+    <li><a href="#ref-for-council-team-contact①">5.6.2.6. 
+Council Deliberations</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="dismissed">
+   <b><a href="#dismissed">#dismissed</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-dismissed">5.6.2.3. 
+Council Participation, Dismissal, and Renunciation</a> <a href="#ref-for-dismissed①">(2)</a> <a href="#ref-for-dismissed②">(3)</a>
+    <li><a href="#ref-for-dismissed③">5.6.2.7. 
+Council Decision Report</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="renounce">
+   <b><a href="#renounce">#renounce</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-renounce">5.6.2.3. 
+Council Participation, Dismissal, and Renunciation</a>
+    <li><a href="#ref-for-renounce①">5.6.2.7. 
+Council Decision Report</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="w3c-council-chair">
+   <b><a href="#w3c-council-chair">#w3c-council-chair</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-w3c-council-chair">5.6.2.1. 
+Council Composition</a>
+    <li><a href="#ref-for-w3c-council-chair①">5.6.2.4. 
+Unanimous Short Circuit</a>
+    <li><a href="#ref-for-w3c-council-chair②">5.6.2.6. 
+Council Deliberations</a> <a href="#ref-for-w3c-council-chair③">(2)</a> <a href="#ref-for-w3c-council-chair④">(3)</a> <a href="#ref-for-w3c-council-chair⑤">(4)</a> <a href="#ref-for-w3c-council-chair⑥">(5)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="uphold">
+   <b><a href="#uphold">#uphold</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-uphold">5.6.2.6. 
+Council Deliberations</a>
+    <li><a href="#ref-for-uphold①">5.6.2.7. 
+Council Decision Report</a>
+    <li><a href="#ref-for-uphold②">5.7.2. 
+After the Review Period</a>
+    <li><a href="#ref-for-uphold③">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-uphold④">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="overrule">
+   <b><a href="#overrule">#overrule</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-overrule">5.6.2.6. 
+Council Deliberations</a>
+    <li><a href="#ref-for-overrule①">5.6.2.7. 
+Council Decision Report</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="fully-addressed">
+   <b><a href="#fully-addressed">#fully-addressed</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-fully-addressed">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-fully-addressed①">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="minority-opinion">
+   <b><a href="#minority-opinion">#minority-opinion</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-minority-opinion">5.6.2.7. 
+Council Decision Report</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="council-report">
+   <b><a href="#council-report">#council-report</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-council-report">5.6.2.7. 
+Council Decision Report</a> <a href="#ref-for-council-report①">(2)</a> <a href="#ref-for-council-report②">(3)</a>
+    <li><a href="#ref-for-council-report③">5.6.2.8. 
+Appealing Council Decisions</a>
+    <li><a href="#ref-for-council-report④">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="advisory-committee-review">
+   <b><a href="#advisory-committee-review">#advisory-committee-review</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-advisory-committee-review">4.3. 
+Advisory Committee Review of a Charter</a>
+    <li><a href="#ref-for-advisory-committee-review①">4.6. 
+Chartered Group Closure</a>
+    <li><a href="#ref-for-advisory-committee-review②">5.1. 
+Types of Decisions</a>
+    <li><a href="#ref-for-advisory-committee-review③">5.2.1. 
+Consensus</a>
+    <li><a href="#ref-for-advisory-committee-review④">5.5. 
+Registering Formal Objections</a>
+    <li><a href="#ref-for-advisory-committee-review⑤">5.7.1. 
+Start of a Review Period</a> <a href="#ref-for-advisory-committee-review⑥">(2)</a>
+    <li><a href="#ref-for-advisory-committee-review⑦">5.7.2. 
+After the Review Period</a>
+    <li><a href="#ref-for-advisory-committee-review⑧">5.9. 
+Appeal by Advisory Committee Representatives</a> <a href="#ref-for-advisory-committee-review⑨">(2)</a>
+    <li><a href="#ref-for-advisory-committee-review①⓪">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-advisory-committee-review①①">6.3.9. 
+Transitioning to Proposed Recommendation</a> <a href="#ref-for-advisory-committee-review①②">(2)</a>
+    <li><a href="#ref-for-advisory-committee-review①③">6.3.11.5. 
+Incorporating Candidate Amendments</a> <a href="#ref-for-advisory-committee-review①④">(2)</a>
+    <li><a href="#ref-for-advisory-committee-review①⑤">6.3.13.1. 
+Abandoning an Unfinished Recommendation</a>
+    <li><a href="#ref-for-advisory-committee-review①⑥">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a> <a href="#ref-for-advisory-committee-review①⑦">(2)</a>
+    <li><a href="#ref-for-advisory-committee-review①⑧">6.4.4. 
+Revising W3C Statements</a>
+    <li><a href="#ref-for-advisory-committee-review①⑨">6.5.2. 
+Publishing Registries</a>
+    <li><a href="#ref-for-advisory-committee-review②⓪">6.5.3. 
+Updating Registry Tables</a>
+    <li><a href="#ref-for-advisory-committee-review②①">11. 
+Process Evolution</a>
+    <li><a href="#ref-for-advisory-committee-review②②"> Changes related to the role of the Director</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="reviewform">
+   <b><a href="#reviewform">#reviewform</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-reviewform">5.7.1. 
+Start of a Review Period</a>
+    <li><a href="#ref-for-reviewform①">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="advisory-committee-appeal">
+   <b><a href="#advisory-committee-appeal">#advisory-committee-appeal</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-advisory-committee-appeal">5.6.2.7. 
+Council Decision Report</a>
+    <li><a href="#ref-for-advisory-committee-appeal①">5.6.2.8. 
+Appealing Council Decisions</a>
+    <li><a href="#ref-for-advisory-committee-appeal②">5.8. 
+Advisory Committee Votes</a>
+    <li><a href="#ref-for-advisory-committee-appeal③">5.9. 
+Appeal by Advisory Committee Representatives</a> <a href="#ref-for-advisory-committee-appeal④">(2)</a>
+    <li><a href="#ref-for-advisory-committee-appeal⑤">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-advisory-committee-appeal⑥">6.3.10. 
+Transitioning to W3C Recommendation</a>
+    <li><a href="#ref-for-advisory-committee-appeal⑦">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a>
+    <li><a href="#ref-for-advisory-committee-appeal⑧">6.4.3. 
+Elevating Group Notes to W3C Statement status</a>
+    <li><a href="#ref-for-advisory-committee-appeal⑨">6.4.4. 
+Revising W3C Statements</a>
+    <li><a href="#ref-for-advisory-committee-appeal①⓪">9. 
+Liaisons</a> <a href="#ref-for-advisory-committee-appeal①①">(2)</a>
+    <li><a href="#ref-for-advisory-committee-appeal①②">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a>
+    <li><a href="#ref-for-advisory-committee-appeal①③">11. 
+Process Evolution</a>
+    <li><a href="#ref-for-advisory-committee-appeal①④"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="publishing">
+   <b><a href="#publishing">#publishing</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-publishing">6.1. 
+Types of Technical Reports</a>
+    <li><a href="#ref-for-publishing①">6.2.1. 
+Publication of Technical Reports</a>
+    <li><a href="#ref-for-publishing②">6.2.2. 
+Reviews and Review Responsibilities</a>
+    <li><a href="#ref-for-publishing③">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-publishing④">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-publishing⑤">(2)</a> <a href="#ref-for-publishing⑥">(3)</a>
+    <li><a href="#ref-for-publishing⑦">6.3.6. 
+Revising a Working Draft</a>
+    <li><a href="#ref-for-publishing⑧">6.3.8.2. 
+Publishing a Candidate Recommendation Draft</a>
+    <li><a href="#ref-for-publishing⑨">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-publishing①⓪">6.3.13.1. 
+Abandoning an Unfinished Recommendation</a> <a href="#ref-for-publishing①①">(2)</a> <a href="#ref-for-publishing①②">(3)</a>
+    <li><a href="#ref-for-publishing①③">6.4.1. 
+Group Notes</a> <a href="#ref-for-publishing①④">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="technical-report">
+   <b><a href="#technical-report">#technical-report</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-technical-report">4.2. 
+Content of a Charter</a>
+    <li><a href="#ref-for-technical-report①">5.5. 
+Registering Formal Objections</a> <a href="#ref-for-technical-report②">(2)</a>
+    <li><a href="#ref-for-technical-report③">5.7. 
+Advisory Committee Reviews</a>
+    <li><a href="#ref-for-technical-report④">5.7.2. 
+After the Review Period</a>
+    <li><a href="#ref-for-technical-report⑤">6.2.1. 
+Publication of Technical Reports</a> <a href="#ref-for-technical-report⑥">(2)</a> <a href="#ref-for-technical-report⑦">(3)</a>
+    <li><a href="#ref-for-technical-report⑧">6.2.3. 
+Classes of Changes</a>
+    <li><a href="#ref-for-technical-report⑨">6.2.4. 
+Errata Management</a> <a href="#ref-for-technical-report①⓪">(2)</a> <a href="#ref-for-technical-report①①">(3)</a> <a href="#ref-for-technical-report①②">(4)</a> <a href="#ref-for-technical-report①③">(5)</a>
+    <li><a href="#ref-for-technical-report①④">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-technical-report①⑤">6.3. 
+The W3C Recommendation Track</a>
+    <li><a href="#ref-for-technical-report①⑥">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-technical-report①⑦">(2)</a>
+    <li><a href="#ref-for-technical-report①⑧">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-technical-report①⑨">6.3.11.4. 
+Revising a Recommendation: New Features</a>
+    <li><a href="#ref-for-technical-report②⓪">6.3.12. 
+Regression on the Recommendation Track</a> <a href="#ref-for-technical-report②①">(2)</a>
+    <li><a href="#ref-for-technical-report②②">6.3.13.1. 
+Abandoning an Unfinished Recommendation</a> <a href="#ref-for-technical-report②③">(2)</a> <a href="#ref-for-technical-report②④">(3)</a>
+    <li><a href="#ref-for-technical-report②⑤">6.4.2. 
+Publishing Notes</a>
+    <li><a href="#ref-for-technical-report②⑥">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-technical-report②⑦">(2)</a>
+    <li><a href="#ref-for-technical-report②⑧">6.5.3. 
+Updating Registry Tables</a> <a href="#ref-for-technical-report②⑨">(2)</a>
+    <li><a href="#ref-for-technical-report③⓪">6.5.4. 
+Registry Data Reports</a> <a href="#ref-for-technical-report③①">(2)</a> <a href="#ref-for-technical-report③②">(3)</a> <a href="#ref-for-technical-report③③">(4)</a>
+    <li><a href="#ref-for-technical-report③④">6.6. 
+Switching Tracks</a> <a href="#ref-for-technical-report③⑤">(2)</a> <a href="#ref-for-technical-report③⑥">(3)</a> <a href="#ref-for-technical-report③⑦">(4)</a>
+    <li><a href="#ref-for-technical-report③⑧">11. 
+Process Evolution</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="dfn-wide-review">
+   <b><a href="#dfn-wide-review">#dfn-wide-review</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-dfn-wide-review">6.1. 
+Types of Technical Reports</a> <a href="#ref-for-dfn-wide-review①">(2)</a>
+    <li><a href="#ref-for-dfn-wide-review②">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-dfn-wide-review③">6.3. 
+The W3C Recommendation Track</a>
+    <li><a href="#ref-for-dfn-wide-review④">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-dfn-wide-review⑤">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a>
+    <li><a href="#ref-for-dfn-wide-review⑥">6.3.7. 
+Transitioning to Candidate Recommendation</a>
+    <li><a href="#ref-for-dfn-wide-review⑦">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-dfn-wide-review⑧">6.3.12. 
+Regression on the Recommendation Track</a>
+    <li><a href="#ref-for-dfn-wide-review⑨">6.4.3. 
+Elevating Group Notes to W3C Statement status</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="editorial-change">
+   <b><a href="#editorial-change">#editorial-change</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-editorial-change">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-editorial-change①">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a>
+    <li><a href="#ref-for-editorial-change②">6.3.6. 
+Revising a Working Draft</a>
+    <li><a href="#ref-for-editorial-change③">6.3.8.2. 
+Publishing a Candidate Recommendation Draft</a>
+    <li><a href="#ref-for-editorial-change④">6.3.11.2. 
+Revising a Recommendation: Editorial Changes</a>
+    <li><a href="#ref-for-editorial-change⑤">6.4.4. 
+Revising W3C Statements</a>
+    <li><a href="#ref-for-editorial-change⑥">6.5.4. 
+Registry Data Reports</a> <a href="#ref-for-editorial-change⑦">(2)</a>
+    <li><a href="#ref-for-editorial-change⑧">10.3. 
+Acknowledgment of a Submission Request</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="substantive-change">
+   <b><a href="#substantive-change">#substantive-change</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-substantive-change">5.7.2. 
+After the Review Period</a> <a href="#ref-for-substantive-change①">(2)</a> <a href="#ref-for-substantive-change②">(3)</a>
+    <li><a href="#ref-for-substantive-change③">6.2.2. 
+Reviews and Review Responsibilities</a>
+    <li><a href="#ref-for-substantive-change④">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-substantive-change⑤">6.3.6. 
+Revising a Working Draft</a>
+    <li><a href="#ref-for-substantive-change⑥">6.3.8.1. 
+Publishing a Candidate Recommendation Snapshot</a> <a href="#ref-for-substantive-change⑦">(2)</a>
+    <li><a href="#ref-for-substantive-change⑧">6.3.8.2. 
+Publishing a Candidate Recommendation Draft</a> <a href="#ref-for-substantive-change⑨">(2)</a>
+    <li><a href="#ref-for-substantive-change①⓪">6.3.9. 
+Transitioning to Proposed Recommendation</a> <a href="#ref-for-substantive-change①①">(2)</a> <a href="#ref-for-substantive-change①②">(3)</a>
+    <li><a href="#ref-for-substantive-change①③">6.3.10. 
+Transitioning to W3C Recommendation</a>
+    <li><a href="#ref-for-substantive-change①④">6.3.13.1. 
+Abandoning an Unfinished Recommendation</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-change">
+   <b><a href="#registry-change">#registry-change</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-change">6.5.1. 
+Registry Definitions</a>
+    <li><a href="#ref-for-registry-change①">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-registry-change②">(2)</a>
+    <li><a href="#ref-for-registry-change③">6.5.3. 
+Updating Registry Tables</a> <a href="#ref-for-registry-change④">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="erratum">
+   <b><a href="#erratum">#erratum</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-erratum">6.2.5. 
+Candidate Amendments</a> <a href="#ref-for-erratum①">(2)</a>
+    <li><a href="#ref-for-erratum②">6.3.11.2. 
+Revising a Recommendation: Editorial Changes</a>
+    <li><a href="#ref-for-erratum③">6.3.11.3. 
+Revising a Recommendation: Substantive Changes</a>
+    <li><a href="#ref-for-erratum④">6.4.2. 
+Publishing Notes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="candidate-correction">
+   <b><a href="#candidate-correction">#candidate-correction</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-candidate-correction">6.2.5. 
+Candidate Amendments</a> <a href="#ref-for-candidate-correction①">(2)</a> <a href="#ref-for-candidate-correction②">(3)</a> <a href="#ref-for-candidate-correction③">(4)</a>
+    <li><a href="#ref-for-candidate-correction④">6.3.11.3. 
+Revising a Recommendation: Substantive Changes</a> <a href="#ref-for-candidate-correction⑤">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="candidate-addition">
+   <b><a href="#candidate-addition">#candidate-addition</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-candidate-addition">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-candidate-addition①">6.3.11.4. 
+Revising a Recommendation: New Features</a> <a href="#ref-for-candidate-addition②">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="team-correction">
+   <b><a href="#team-correction">#team-correction</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-team-correction">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-team-correction①">6.3.11.2. 
+Revising a Recommendation: Editorial Changes</a>
+    <li><a href="#ref-for-team-correction②">6.4.2. 
+Publishing Notes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="candidate-amendment">
+   <b><a href="#candidate-amendment">#candidate-amendment</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-candidate-amendment">6.2.5. 
+Candidate Amendments</a> <a href="#ref-for-candidate-amendment①">(2)</a> <a href="#ref-for-candidate-amendment②">(3)</a>
+    <li><a href="#ref-for-candidate-amendment③">6.3.11.3. 
+Revising a Recommendation: Substantive Changes</a>
+    <li><a href="#ref-for-candidate-amendment④">6.3.11.4. 
+Revising a Recommendation: New Features</a>
+    <li><a href="#ref-for-candidate-amendment⑤">6.3.11.5. 
+Incorporating Candidate Amendments</a> <a href="#ref-for-candidate-amendment⑥">(2)</a>
+    <li><a href="#ref-for-candidate-amendment⑦">6.4.4. 
+Revising W3C Statements</a> <a href="#ref-for-candidate-amendment⑧">(2)</a> <a href="#ref-for-candidate-amendment⑨">(3)</a> <a href="#ref-for-candidate-amendment①⓪">(4)</a>
+    <li><a href="#ref-for-candidate-amendment①①">6.5.3. 
+Updating Registry Tables</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="w3c-recommendation-track">
+   <b><a href="#w3c-recommendation-track">#w3c-recommendation-track</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-w3c-recommendation-track">6.1. 
+Types of Technical Reports</a> <a href="#ref-for-w3c-recommendation-track①">(2)</a> <a href="#ref-for-w3c-recommendation-track②">(3)</a>
+    <li><a href="#ref-for-w3c-recommendation-track③">6.2.3. 
+Classes of Changes</a> <a href="#ref-for-w3c-recommendation-track④">(2)</a>
+    <li><a href="#ref-for-w3c-recommendation-track⑤">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-w3c-recommendation-track⑥">6.3. 
+The W3C Recommendation Track</a>
+    <li><a href="#ref-for-w3c-recommendation-track⑦">6.3.12. 
+Regression on the Recommendation Track</a>
+    <li><a href="#ref-for-w3c-recommendation-track⑧">6.3.13.1. 
+Abandoning an Unfinished Recommendation</a>
+    <li><a href="#ref-for-w3c-recommendation-track⑨">6.4.3. 
+Elevating Group Notes to W3C Statement status</a>
+    <li><a href="#ref-for-w3c-recommendation-track①⓪">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-w3c-recommendation-track①①">(2)</a>
+    <li><a href="#ref-for-w3c-recommendation-track①②">6.6. 
+Switching Tracks</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="patent-review-drafts">
+   <b><a href="#patent-review-drafts">#patent-review-drafts</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-patent-review-drafts">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-patent-review-drafts①">(2)</a>
+    <li><a href="#ref-for-patent-review-drafts②">6.3.11.5. 
+Incorporating Candidate Amendments</a>
+    <li><a href="#ref-for-patent-review-drafts③">6.5.2. 
+Publishing Registries</a>
+    <li><a href="#ref-for-patent-review-drafts④">6.6. 
+Switching Tracks</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="RecsWD">
+   <b><a href="#RecsWD">#RecsWD</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-RecsWD">4.2. 
+Content of a Charter</a>
+    <li><a href="#ref-for-RecsWD①">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-RecsWD②">6.3. 
+The W3C Recommendation Track</a>
+    <li><a href="#ref-for-RecsWD③">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-RecsWD④">(2)</a> <a href="#ref-for-RecsWD⑤">(3)</a> <a href="#ref-for-RecsWD⑥">(4)</a> <a href="#ref-for-RecsWD⑦">(5)</a>
+    <li><a href="#ref-for-RecsWD⑧">6.3.6. 
+Revising a Working Draft</a> <a href="#ref-for-RecsWD⑨">(2)</a> <a href="#ref-for-RecsWD①⓪">(3)</a>
+    <li><a href="#ref-for-RecsWD①①">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-RecsWD①②">6.3.13.1. 
+Abandoning an Unfinished Recommendation</a>
+    <li><a href="#ref-for-RecsWD①③">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-RecsWD①④">(2)</a>
+    <li><a href="#ref-for-RecsWD①⑤"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="fpwd">
+   <b><a href="#fpwd">#fpwd</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-fpwd">4.2. 
+Content of a Charter</a>
+    <li><a href="#ref-for-fpwd①">6.3. 
+The W3C Recommendation Track</a>
+    <li><a href="#ref-for-fpwd②">6.3.3. 
+Advancement on the Recommendation Track</a> <a href="#ref-for-fpwd③">(2)</a>
+    <li><a href="#ref-for-fpwd④">6.3.5. 
+Publishing a First Public Working Draft</a> <a href="#ref-for-fpwd⑤">(2)</a>
+    <li><a href="#ref-for-fpwd⑥">6.3.11.4. 
+Revising a Recommendation: New Features</a>
+    <li><a href="#ref-for-fpwd⑦">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="RecsCR">
+   <b><a href="#RecsCR">#RecsCR</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-RecsCR">5.7.2. 
+After the Review Period</a>
+    <li><a href="#ref-for-RecsCR①">6.2.2.1. 
+Wide Review</a>
+    <li><a href="#ref-for-RecsCR②">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-RecsCR③">6.3. 
+The W3C Recommendation Track</a> <a href="#ref-for-RecsCR④">(2)</a>
+    <li><a href="#ref-for-RecsCR⑤">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-RecsCR⑥">(2)</a> <a href="#ref-for-RecsCR⑦">(3)</a> <a href="#ref-for-RecsCR⑧">(4)</a> <a href="#ref-for-RecsCR⑨">(5)</a> <a href="#ref-for-RecsCR①⓪">(6)</a> <a href="#ref-for-RecsCR①①">(7)</a> <a href="#ref-for-RecsCR①②">(8)</a>
+    <li><a href="#ref-for-RecsCR①③">6.3.3. 
+Advancement on the Recommendation Track</a> <a href="#ref-for-RecsCR①④">(2)</a>
+    <li><a href="#ref-for-RecsCR①⑤">6.3.7. 
+Transitioning to Candidate Recommendation</a> <a href="#ref-for-RecsCR①⑥">(2)</a>
+    <li><a href="#ref-for-RecsCR①⑦">6.3.8.1. 
+Publishing a Candidate Recommendation Snapshot</a> <a href="#ref-for-RecsCR①⑧">(2)</a>
+    <li><a href="#ref-for-RecsCR①⑨">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-RecsCR②⓪">6.3.13.2. 
+Rescinding a Candidate Recommendation</a>
+    <li><a href="#ref-for-RecsCR②①">6.5.2. 
+Publishing Registries</a>
+    <li><a href="#ref-for-RecsCR②②"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="candidate-recommendation-snapshot">
+   <b><a href="#candidate-recommendation-snapshot">#candidate-recommendation-snapshot</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-candidate-recommendation-snapshot">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-candidate-recommendation-snapshot①">(2)</a> <a href="#ref-for-candidate-recommendation-snapshot②">(3)</a> <a href="#ref-for-candidate-recommendation-snapshot③">(4)</a> <a href="#ref-for-candidate-recommendation-snapshot④">(5)</a>
+    <li><a href="#ref-for-candidate-recommendation-snapshot⑤">6.3.7. 
+Transitioning to Candidate Recommendation</a> <a href="#ref-for-candidate-recommendation-snapshot⑥">(2)</a> <a href="#ref-for-candidate-recommendation-snapshot⑦">(3)</a>
+    <li><a href="#ref-for-candidate-recommendation-snapshot⑧">6.3.8.1. 
+Publishing a Candidate Recommendation Snapshot</a> <a href="#ref-for-candidate-recommendation-snapshot⑨">(2)</a> <a href="#ref-for-candidate-recommendation-snapshot①⓪">(3)</a> <a href="#ref-for-candidate-recommendation-snapshot①①">(4)</a> <a href="#ref-for-candidate-recommendation-snapshot①②">(5)</a>
+    <li><a href="#ref-for-candidate-recommendation-snapshot①③">6.3.8.2. 
+Publishing a Candidate Recommendation Draft</a> <a href="#ref-for-candidate-recommendation-snapshot①④">(2)</a> <a href="#ref-for-candidate-recommendation-snapshot①⑤">(3)</a>
+    <li><a href="#ref-for-candidate-recommendation-snapshot①⑥">6.3.9. 
+Transitioning to Proposed Recommendation</a> <a href="#ref-for-candidate-recommendation-snapshot①⑦">(2)</a> <a href="#ref-for-candidate-recommendation-snapshot①⑧">(3)</a>
+    <li><a href="#ref-for-candidate-recommendation-snapshot①⑨">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="candidate-recommendation-draft">
+   <b><a href="#candidate-recommendation-draft">#candidate-recommendation-draft</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-candidate-recommendation-draft">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-candidate-recommendation-draft①">(2)</a>
+    <li><a href="#ref-for-candidate-recommendation-draft②">6.3.8.2. 
+Publishing a Candidate Recommendation Draft</a> <a href="#ref-for-candidate-recommendation-draft③">(2)</a> <a href="#ref-for-candidate-recommendation-draft④">(3)</a> <a href="#ref-for-candidate-recommendation-draft⑤">(4)</a> <a href="#ref-for-candidate-recommendation-draft⑥">(5)</a>
+    <li><a href="#ref-for-candidate-recommendation-draft⑦">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="rescinded-candidate-recommendation">
+   <b><a href="#rescinded-candidate-recommendation">#rescinded-candidate-recommendation</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-rescinded-candidate-recommendation">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-rescinded-candidate-recommendation①">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="RecsPR">
+   <b><a href="#RecsPR">#RecsPR</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-RecsPR">3.2.1. 
+Role of the Advisory Committee</a>
+    <li><a href="#ref-for-RecsPR">5.7.2. 
+After the Review Period</a> <a href="#ref-for-RecsPR①">(2)</a>
+    <li><a href="#ref-for-RecsPR②">6.3. 
+The W3C Recommendation Track</a>
+    <li><a href="#ref-for-RecsPR③">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-RecsPR④">6.3.3. 
+Advancement on the Recommendation Track</a>
+    <li><a href="#ref-for-RecsPR⑤">6.3.7. 
+Transitioning to Candidate Recommendation</a>
+    <li><a href="#ref-for-RecsPR⑥">6.3.8.1. 
+Publishing a Candidate Recommendation Snapshot</a>
+    <li><a href="#ref-for-RecsPR⑦">6.3.9. 
+Transitioning to Proposed Recommendation</a> <a href="#ref-for-RecsPR⑧">(2)</a> <a href="#ref-for-RecsPR⑨">(3)</a> <a href="#ref-for-RecsPR①⓪">(4)</a> <a href="#ref-for-RecsPR①①">(5)</a> <a href="#ref-for-RecsPR①②">(6)</a>
+    <li><a href="#ref-for-RecsPR①③">6.3.10. 
+Transitioning to W3C Recommendation</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="RecsW3C">
+   <b><a href="#RecsW3C">#RecsW3C</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-RecsW3C">1. 
+Introduction</a>
+    <li><a href="#ref-for-RecsW3C">3.4. 
+Chartered Groups: Working Groups and Interest Groups</a>
+    <li><a href="#ref-for-RecsW3C①">5.7.2. 
+After the Review Period</a>
+    <li><a href="#ref-for-RecsW3C②">6.1. 
+Types of Technical Reports</a>
+    <li><a href="#ref-for-RecsW3C③">6.2.4. 
+Errata Management</a> <a href="#ref-for-RecsW3C④">(2)</a>
+    <li><a href="#ref-for-RecsW3C⑤">6.2.5. 
+Candidate Amendments</a>
+    <li><a href="#ref-for-RecsW3C⑥">6.3. 
+The W3C Recommendation Track</a> <a href="#ref-for-RecsW3C">(2)</a> <a href="#ref-for-RecsW3C⑦">(3)</a>
+    <li><a href="#ref-for-RecsW3C⑧">6.3.1. 
+Maturity Stages on the Recommendation Track</a> <a href="#ref-for-RecsW3C⑨">(2)</a> <a href="#ref-for-RecsW3C①⓪">(3)</a> <a href="#ref-for-RecsW3C①①">(4)</a> <a href="#ref-for-RecsW3C①②">(5)</a> <a href="#ref-for-RecsW3C①③">(6)</a> <a href="#ref-for-RecsW3C①④">(7)</a> <a href="#ref-for-RecsW3C①⑤">(8)</a> <a href="#ref-for-RecsW3C①⑥">(9)</a> <a href="#ref-for-RecsW3C①⑦">(10)</a> <a href="#ref-for-RecsW3C①⑧">(11)</a> <a href="#ref-for-RecsW3C①⑨">(12)</a> <a href="#ref-for-RecsW3C②⓪">(13)</a> <a href="#ref-for-RecsW3C②①">(14)</a> <a href="#ref-for-RecsW3C②②">(15)</a>
+    <li><a href="#ref-for-RecsW3C②③">6.3.4.1. 
+Streamlined Publication Approval</a> <a href="#ref-for-RecsW3C②④">(2)</a>
+    <li><a href="#ref-for-RecsW3C②⑤">6.3.9. 
+Transitioning to Proposed Recommendation</a> <a href="#ref-for-RecsW3C②⑥">(2)</a> <a href="#ref-for-RecsW3C②⑦">(3)</a> <a href="#ref-for-RecsW3C②⑧">(4)</a> <a href="#ref-for-RecsW3C②⑨">(5)</a>
+    <li><a href="#ref-for-RecsW3C③⓪">6.3.10. 
+Transitioning to W3C Recommendation</a> <a href="#ref-for-RecsW3C③①">(2)</a> <a href="#ref-for-RecsW3C③②">(3)</a> <a href="#ref-for-RecsW3C③③">(4)</a> <a href="#ref-for-RecsW3C③④">(5)</a> <a href="#ref-for-RecsW3C③⑤">(6)</a> <a href="#ref-for-RecsW3C③⑥">(7)</a>
+    <li><a href="#ref-for-RecsW3C③⑦">6.3.11. 
+Revising a W3C Recommendation</a>
+    <li><a href="#ref-for-RecsW3C③⑧">6.3.11.1. 
+Revising a Recommendation: Markup Changes</a> <a href="#ref-for-RecsW3C③⑨">(2)</a> <a href="#ref-for-RecsW3C④⓪">(3)</a>
+    <li><a href="#ref-for-RecsW3C④①">6.3.11.2. 
+Revising a Recommendation: Editorial Changes</a> <a href="#ref-for-RecsW3C④②">(2)</a> <a href="#ref-for-RecsW3C④③">(3)</a> <a href="#ref-for-RecsW3C④④">(4)</a>
+    <li><a href="#ref-for-RecsW3C④⑤">6.3.11.3. 
+Revising a Recommendation: Substantive Changes</a> <a href="#ref-for-RecsW3C④⑥">(2)</a> <a href="#ref-for-RecsW3C④⑦">(3)</a> <a href="#ref-for-RecsW3C④⑧">(4)</a>
+    <li><a href="#ref-for-RecsW3C④⑨">6.3.11.4. 
+Revising a Recommendation: New Features</a> <a href="#ref-for-RecsW3C⑤⓪">(2)</a> <a href="#ref-for-RecsW3C⑤①">(3)</a>
+    <li><a href="#ref-for-RecsW3C⑤②">6.3.11.5. 
+Incorporating Candidate Amendments</a> <a href="#ref-for-RecsW3C⑤③">(2)</a> <a href="#ref-for-RecsW3C⑤④">(3)</a> <a href="#ref-for-RecsW3C⑤⑤">(4)</a> <a href="#ref-for-RecsW3C⑤⑥">(5)</a>
+    <li><a href="#ref-for-RecsW3C⑤⑦">6.3.13.2. 
+Rescinding a Candidate Recommendation</a>
+    <li><a href="#ref-for-RecsW3C⑤⑧">6.3.13.3. 
+Abandoning a W3C Recommendation</a> <a href="#ref-for-RecsW3C⑤⑨">(2)</a> <a href="#ref-for-RecsW3C⑥⓪">(3)</a> <a href="#ref-for-RecsW3C⑥①">(4)</a> <a href="#ref-for-RecsW3C⑥②">(5)</a> <a href="#ref-for-RecsW3C⑥③">(6)</a>
+    <li><a href="#ref-for-RecsW3C⑥④">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a> <a href="#ref-for-RecsW3C⑥⑤">(2)</a> <a href="#ref-for-RecsW3C⑥⑥">(3)</a> <a href="#ref-for-RecsW3C⑥⑦">(4)</a> <a href="#ref-for-RecsW3C⑥⑧">(5)</a> <a href="#ref-for-RecsW3C⑥⑨">(6)</a>
+    <li><a href="#ref-for-RecsW3C⑦⓪">6.5. 
+The Registry Track</a>
+    <li><a href="#ref-for-RecsW3C⑦①">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-RecsW3C⑦②">(2)</a>
+    <li><a href="#ref-for-RecsW3C⑦③">6.6. 
+Switching Tracks</a>
+    <li><a href="#ref-for-RecsW3C⑦④">10. 
+Member Submission Process</a>
+    <li><a href="#ref-for-RecsW3C⑦⑤"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="RecsSup">
+   <b><a href="#RecsSup">#RecsSup</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-RecsSup">6.3.13.3. 
+Abandoning a W3C Recommendation</a>
+    <li><a href="#ref-for-RecsSup①">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="RecsObs">
+   <b><a href="#RecsObs">#RecsObs</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-RecsObs">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-RecsObs①">6.3.13.3. 
+Abandoning a W3C Recommendation</a> <a href="#ref-for-RecsObs②">(2)</a>
+    <li><a href="#ref-for-RecsObs③">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a> <a href="#ref-for-RecsObs④">(2)</a>
+    <li><a href="#ref-for-RecsObs⑤">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="RescindedRec">
+   <b><a href="#RescindedRec">#RescindedRec</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-RescindedRec">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-RescindedRec①">6.3.13.3. 
+Abandoning a W3C Recommendation</a>
+    <li><a href="#ref-for-RescindedRec②">6.3.13.4. 
+Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</a> <a href="#ref-for-RescindedRec③">(2)</a>
+    <li><a href="#ref-for-RescindedRec④">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="discontinuedREC">
+   <b><a href="#discontinuedREC">#discontinuedREC</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-discontinuedREC">6.3.13.1. 
+Abandoning an Unfinished Recommendation</a> <a href="#ref-for-discontinuedREC①">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="editors-draft">
+   <b><a href="#editors-draft">#editors-draft</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-editors-draft">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="adequate-implementation">
+   <b><a href="#adequate-implementation">#adequate-implementation</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-adequate-implementation">6.1. 
+Types of Technical Reports</a>
+    <li><a href="#ref-for-adequate-implementation①">6.3.4.1. 
+Streamlined Publication Approval</a>
+    <li><a href="#ref-for-adequate-implementation②">6.3.7. 
+Transitioning to Candidate Recommendation</a>
+    <li><a href="#ref-for-adequate-implementation③">6.3.9. 
+Transitioning to Proposed Recommendation</a>
+    <li><a href="#ref-for-adequate-implementation④">6.3.11.5. 
+Incorporating Candidate Amendments</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="trans-req">
+   <b><a href="#trans-req">#trans-req</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-trans-req">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-trans-req①">6.3.3. 
+Advancement on the Recommendation Track</a> <a href="#ref-for-trans-req②">(2)</a>
+    <li><a href="#ref-for-trans-req③">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a>
+    <li><a href="#ref-for-trans-req④">6.3.7. 
+Transitioning to Candidate Recommendation</a>
+    <li><a href="#ref-for-trans-req⑤"> Changes related to the role of the Director</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="update-requests">
+   <b><a href="#update-requests">#update-requests</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-update-requests">6.3.1. 
+Maturity Stages on the Recommendation Track</a>
+    <li><a href="#ref-for-update-requests①">6.3.4. 
+Updating Mature Publications on the Recommendation Track</a> <a href="#ref-for-update-requests②">(2)</a> <a href="#ref-for-update-requests③">(3)</a>
+    <li><a href="#ref-for-update-requests④">6.3.4.1. 
+Streamlined Publication Approval</a> <a href="#ref-for-update-requests⑤">(2)</a>
+    <li><a href="#ref-for-update-requests⑥">6.3.8.1. 
+Publishing a Candidate Recommendation Snapshot</a>
+    <li><a href="#ref-for-update-requests⑦">6.3.8.2. 
+Publishing a Candidate Recommendation Draft</a>
+    <li><a href="#ref-for-update-requests⑧">6.3.11.3. 
+Revising a Recommendation: Substantive Changes</a>
+    <li><a href="#ref-for-update-requests⑨">6.3.11.5. 
+Incorporating Candidate Amendments</a>
+    <li><a href="#ref-for-update-requests①⓪">6.5.3. 
+Updating Registry Tables</a>
+    <li><a href="#ref-for-update-requests①①"> Changes related to the role of the Director</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="candidate-recommendation-review-period">
+   <b><a href="#candidate-recommendation-review-period">#candidate-recommendation-review-period</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-candidate-recommendation-review-period">6.3.9. 
+Transitioning to Proposed Recommendation</a> <a href="#ref-for-candidate-recommendation-review-period①">(2)</a>
+    <li><a href="#ref-for-candidate-recommendation-review-period②"> Other miscellaneous changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="at-risk">
+   <b><a href="#at-risk">#at-risk</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-at-risk">6.3.8.1. 
+Publishing a Candidate Recommendation Snapshot</a> <a href="#ref-for-at-risk①">(2)</a>
+    <li><a href="#ref-for-at-risk②">6.3.8.2. 
+Publishing a Candidate Recommendation Draft</a>
+    <li><a href="#ref-for-at-risk③">6.3.9. 
+Transitioning to Proposed Recommendation</a> <a href="#ref-for-at-risk④">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="allow-new-features">
+   <b><a href="#allow-new-features">#allow-new-features</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-allow-new-features">6.3.4.1. 
+Streamlined Publication Approval</a>
+    <li><a href="#ref-for-allow-new-features①">6.3.11.4. 
+Revising a Recommendation: New Features</a> <a href="#ref-for-allow-new-features②">(2)</a>
+    <li><a href="#ref-for-allow-new-features③">6.3.11.5. 
+Incorporating Candidate Amendments</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="last-call-review">
+   <b><a href="#last-call-review">#last-call-review</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-last-call-review">6.3.11.3. 
+Revising a Recommendation: Substantive Changes</a>
+    <li><a href="#ref-for-last-call-review①">6.3.11.5. 
+Incorporating Candidate Amendments</a> <a href="#ref-for-last-call-review②">(2)</a> <a href="#ref-for-last-call-review③">(3)</a> <a href="#ref-for-last-call-review④">(4)</a> <a href="#ref-for-last-call-review⑤">(5)</a> <a href="#ref-for-last-call-review⑥">(6)</a> <a href="#ref-for-last-call-review⑦">(7)</a> <a href="#ref-for-last-call-review⑧">(8)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="last-call-for-review-of-proposed-corrections">
+   <b><a href="#last-call-for-review-of-proposed-corrections">#last-call-for-review-of-proposed-corrections</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-last-call-for-review-of-proposed-corrections">6.3.4.1. 
+Streamlined Publication Approval</a>
+    <li><a href="#ref-for-last-call-for-review-of-proposed-corrections①">6.4.4. 
+Revising W3C Statements</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="last-call-for-review-of-proposed-additions">
+   <b><a href="#last-call-for-review-of-proposed-additions">#last-call-for-review-of-proposed-additions</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-last-call-for-review-of-proposed-additions">6.3.4.1. 
+Streamlined Publication Approval</a>
+    <li><a href="#ref-for-last-call-for-review-of-proposed-additions①">6.3.11.5. 
+Incorporating Candidate Amendments</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="last-call-for-review-of-proposed-corrections-and-additions">
+   <b><a href="#last-call-for-review-of-proposed-corrections-and-additions">#last-call-for-review-of-proposed-corrections-and-additions</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-last-call-for-review-of-proposed-corrections-and-additions">6.3.11.5. 
+Incorporating Candidate Amendments</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="proposed-amendments">
+   <b><a href="#proposed-amendments">#proposed-amendments</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-proposed-amendments">6.3.11.5. 
+Incorporating Candidate Amendments</a> <a href="#ref-for-proposed-amendments①">(2)</a> <a href="#ref-for-proposed-amendments②">(3)</a> <a href="#ref-for-proposed-amendments③">(4)</a> <a href="#ref-for-proposed-amendments④">(5)</a> <a href="#ref-for-proposed-amendments⑤">(6)</a> <a href="#ref-for-proposed-amendments⑥">(7)</a> <a href="#ref-for-proposed-amendments⑦">(8)</a> <a href="#ref-for-proposed-amendments⑧">(9)</a> <a href="#ref-for-proposed-amendments⑨">(10)</a>
+    <li><a href="#ref-for-proposed-amendments①⓪">6.4.4. 
+Revising W3C Statements</a> <a href="#ref-for-proposed-amendments①①">(2)</a>
+    <li><a href="#ref-for-proposed-amendments①②">6.5.3. 
+Updating Registry Tables</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="proposed-corrections">
+   <b><a href="#proposed-corrections">#proposed-corrections</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-proposed-corrections">6.3.4.1. 
+Streamlined Publication Approval</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="proposed-additions">
+   <b><a href="#proposed-additions">#proposed-additions</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-proposed-additions">6.3.4.1. 
+Streamlined Publication Approval</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="WGNote">
+   <b><a href="#WGNote">#WGNote</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-WGNote">3.4. 
+Chartered Groups: Working Groups and Interest Groups</a>
+    <li><a href="#ref-for-WGNote">6.1. 
+Types of Technical Reports</a> <a href="#ref-for-WGNote①">(2)</a>
+    <li><a href="#ref-for-WGNote②">6.4.1. 
+Group Notes</a> <a href="#ref-for-WGNote③">(2)</a> <a href="#ref-for-WGNote④">(3)</a> <a href="#ref-for-WGNote⑤">(4)</a> <a href="#ref-for-WGNote⑥">(5)</a> <a href="#ref-for-WGNote⑦">(6)</a>
+    <li><a href="#ref-for-WGNote⑧">6.4.2. 
+Publishing Notes</a> <a href="#ref-for-WGNote⑨">(2)</a> <a href="#ref-for-WGNote①⓪">(3)</a> <a href="#ref-for-WGNote①①">(4)</a> <a href="#ref-for-WGNote①②">(5)</a> <a href="#ref-for-WGNote①③">(6)</a> <a href="#ref-for-WGNote①④">(7)</a>
+    <li><a href="#ref-for-WGNote①⑤">6.4.3. 
+Elevating Group Notes to W3C Statement status</a> <a href="#ref-for-WGNote①⑥">(2)</a> <a href="#ref-for-WGNote①⑦">(3)</a> <a href="#ref-for-WGNote①⑧">(4)</a> <a href="#ref-for-WGNote①⑨">(5)</a>
+    <li><a href="#ref-for-WGNote②⓪">10.1.1. 
+Scope of Member Submissions</a> <a href="#ref-for-WGNote②①">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="draft-note">
+   <b><a href="#draft-note">#draft-note</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-draft-note">6.4.1. 
+Group Notes</a> <a href="#ref-for-draft-note①">(2)</a>
+    <li><a href="#ref-for-draft-note②">6.4.2. 
+Publishing Notes</a> <a href="#ref-for-draft-note③">(2)</a> <a href="#ref-for-draft-note④">(3)</a> <a href="#ref-for-draft-note⑤">(4)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="statement">
+   <b><a href="#statement">#statement</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-statement">6.1. 
+Types of Technical Reports</a>
+    <li><a href="#ref-for-statement①">6.4.3. 
+Elevating Group Notes to W3C Statement status</a> <a href="#ref-for-statement②">(2)</a> <a href="#ref-for-statement③">(3)</a> <a href="#ref-for-statement④">(4)</a> <a href="#ref-for-statement⑤">(5)</a> <a href="#ref-for-statement⑥">(6)</a> <a href="#ref-for-statement⑦">(7)</a>
+    <li><a href="#ref-for-statement⑧">6.4.4. 
+Revising W3C Statements</a> <a href="#ref-for-statement⑨">(2)</a> <a href="#ref-for-statement①⓪">(3)</a> <a href="#ref-for-statement①①">(4)</a>
+    <li><a href="#ref-for-statement①②">6.6. 
+Switching Tracks</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry">
+   <b><a href="#registry">#registry</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry">6.1. 
+Types of Technical Reports</a>
+    <li><a href="#ref-for-registry①">6.5. 
+The Registry Track</a> <a href="#ref-for-registry②">(2)</a> <a href="#ref-for-registry③">(3)</a>
+    <li><a href="#ref-for-registry④">6.5.1. 
+Registry Definitions</a> <a href="#ref-for-registry⑤">(2)</a>
+    <li><a href="#ref-for-registry⑥">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-registry⑦">(2)</a>
+    <li><a href="#ref-for-registry⑧">6.5.4. 
+Registry Data Reports</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-table">
+   <b><a href="#registry-table">#registry-table</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-table">6.2.3. 
+Classes of Changes</a> <a href="#ref-for-registry-table①">(2)</a>
+    <li><a href="#ref-for-registry-table②">6.5. 
+The Registry Track</a> <a href="#ref-for-registry-table③">(2)</a> <a href="#ref-for-registry-table④">(3)</a>
+    <li><a href="#ref-for-registry-table⑤">6.5.1. 
+Registry Definitions</a> <a href="#ref-for-registry-table⑥">(2)</a> <a href="#ref-for-registry-table⑦">(3)</a> <a href="#ref-for-registry-table⑧">(4)</a> <a href="#ref-for-registry-table⑨">(5)</a>
+    <li><a href="#ref-for-registry-table①⓪">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-registry-table①①">(2)</a> <a href="#ref-for-registry-table①②">(3)</a> <a href="#ref-for-registry-table①③">(4)</a> <a href="#ref-for-registry-table①④">(5)</a> <a href="#ref-for-registry-table①⑤">(6)</a> <a href="#ref-for-registry-table①⑥">(7)</a>
+    <li><a href="#ref-for-registry-table①⑦">6.5.3. 
+Updating Registry Tables</a> <a href="#ref-for-registry-table①⑧">(2)</a>
+    <li><a href="#ref-for-registry-table①⑨">6.5.4. 
+Registry Data Reports</a> <a href="#ref-for-registry-table②⓪">(2)</a> <a href="#ref-for-registry-table②①">(3)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-entry">
+   <b><a href="#registry-entry">#registry-entry</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-entry">6.2.3. 
+Classes of Changes</a>
+    <li><a href="#ref-for-registry-entry①">6.5.1. 
+Registry Definitions</a>
+    <li><a href="#ref-for-registry-entry②">6.5.4. 
+Registry Data Reports</a>
+    <li><a href="#ref-for-registry-entry③">6.5.5. 
+Specifications that Reference Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-data">
+   <b><a href="#registry-data">#registry-data</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-data">6.5.2. 
+Publishing Registries</a>
+    <li><a href="#ref-for-registry-data①">6.5.4. 
+Registry Data Reports</a> <a href="#ref-for-registry-data②">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-definition">
+   <b><a href="#registry-definition">#registry-definition</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-definition">6.1. 
+Types of Technical Reports</a>
+    <li><a href="#ref-for-registry-definition①">6.5. 
+The Registry Track</a>
+    <li><a href="#ref-for-registry-definition②">6.5.1. 
+Registry Definitions</a>
+    <li><a href="#ref-for-registry-definition③">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-registry-definition④">(2)</a> <a href="#ref-for-registry-definition⑤">(3)</a>
+    <li><a href="#ref-for-registry-definition⑥">6.5.3. 
+Updating Registry Tables</a> <a href="#ref-for-registry-definition⑦">(2)</a> <a href="#ref-for-registry-definition⑧">(3)</a> <a href="#ref-for-registry-definition⑨">(4)</a>
+    <li><a href="#ref-for-registry-definition①⓪">6.5.4. 
+Registry Data Reports</a> <a href="#ref-for-registry-definition①①">(2)</a> <a href="#ref-for-registry-definition①②">(3)</a> <a href="#ref-for-registry-definition①③">(4)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="custodian">
+   <b><a href="#custodian">#custodian</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-custodian">6.5. 
+The Registry Track</a>
+    <li><a href="#ref-for-custodian①">6.5.1. 
+Registry Definitions</a> <a href="#ref-for-custodian②">(2)</a>
+    <li><a href="#ref-for-custodian③">6.5.2. 
+Publishing Registries</a>
+    <li><a href="#ref-for-custodian④">6.5.3. 
+Updating Registry Tables</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-report">
+   <b><a href="#registry-report">#registry-report</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-report">6.1. 
+Types of Technical Reports</a> <a href="#ref-for-registry-report①">(2)</a>
+    <li><a href="#ref-for-registry-report②">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-registry-report③">(2)</a> <a href="#ref-for-registry-report④">(3)</a> <a href="#ref-for-registry-report⑤">(4)</a> <a href="#ref-for-registry-report⑥">(5)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-section">
+   <b><a href="#registry-section">#registry-section</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-section">6.1. 
+Types of Technical Reports</a>
+    <li><a href="#ref-for-registry-section①">6.5.2. 
+Publishing Registries</a> <a href="#ref-for-registry-section②">(2)</a> <a href="#ref-for-registry-section③">(3)</a> <a href="#ref-for-registry-section④">(4)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-track">
+   <b><a href="#registry-track">#registry-track</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-track">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="candidate-registry-snapshot">
+   <b><a href="#candidate-registry-snapshot">#candidate-registry-snapshot</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-candidate-registry-snapshot">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="w3c-registry">
+   <b><a href="#w3c-registry">#w3c-registry</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-w3c-registry">6.5.2. 
+Publishing Registries</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="registry-data-report">
+   <b><a href="#registry-data-report">#registry-data-report</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-registry-data-report">6.5.2. 
+Publishing Registries</a>
+    <li><a href="#ref-for-registry-data-report①">6.5.4. 
+Registry Data Reports</a> <a href="#ref-for-registry-data-report②">(2)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="Member-only">
+   <b><a href="#Member-only">#Member-only</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-Member-only">2.1.1. 
+Rights of Members</a>
+    <li><a href="#ref-for-Member-only">3.2.2. 
+Participation in the Advisory Committee</a>
+    <li><a href="#ref-for-Member-only">3.3.2.3. 
+Communications of the Technical Architecture Group</a> <a href="#ref-for-Member-only">(2)</a>
+    <li><a href="#ref-for-Member-only">3.4.1. 
+Requirements for All Chartered Groups</a>
+    <li><a href="#ref-for-Member-only①">5.5. 
+Registering Formal Objections</a>
+    <li><a href="#ref-for-Member-only②">5.7.1. 
+Start of a Review Period</a>
+    <li><a href="#ref-for-Member-only③">5.9. 
+Appeal by Advisory Committee Representatives</a>
+    <li><a href="#ref-for-Member-only④">7.2. 
+Confidentiality Levels</a> <a href="#ref-for-Member-only⑤">(2)</a> <a href="#ref-for-Member-only⑥">(3)</a> <a href="#ref-for-Member-only⑦">(4)</a> <a href="#ref-for-Member-only⑧">(5)</a>
+    <li><a href="#ref-for-Member-only⑨">7.3. 
+Changing Confidentiality Level</a> <a href="#ref-for-Member-only①⓪">(2)</a> <a href="#ref-for-Member-only①①">(3)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="Team-only">
+   <b><a href="#Team-only">#Team-only</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-Team-only">2.1. 
+Members</a>
+    <li><a href="#ref-for-Team-only">5.7.1. 
+Start of a Review Period</a>
+    <li><a href="#ref-for-Team-only①">7.2. 
+Confidentiality Levels</a>
+    <li><a href="#ref-for-Team-only②">7.3. 
+Changing Confidentiality Level</a> <a href="#ref-for-Team-only③">(2)</a> <a href="#ref-for-Team-only④">(3)</a> <a href="#ref-for-Team-only⑤">(4)</a>
+    <li><a href="#ref-for-Team-only⑥">10.2. 
+Team Rights and Obligations</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="EventsW">
+   <b><a href="#EventsW">#EventsW</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-EventsW">7.1. 
+Public Communication</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="technical-agreement">
+   <b><a href="#technical-agreement">#technical-agreement</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-technical-agreement">9. 
+Liaisons</a> <a href="#ref-for-technical-agreement①">(2)</a> <a href="#ref-for-technical-agreement②">(3)</a> <a href="#ref-for-technical-agreement③">(4)</a> <a href="#ref-for-technical-agreement④">(5)</a> <a href="#ref-for-technical-agreement⑤">(6)</a> <a href="#ref-for-technical-agreement⑥">(7)</a> <a href="#ref-for-technical-agreement⑦">(8)</a> <a href="#ref-for-technical-agreement⑧">(9)</a>
+    <li><a href="#ref-for-technical-agreement⑨"> Changes related to the role of the Director</a>
+    <li><a href="#ref-for-technical-agreement①⓪"> Other Governance Changes</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="MemberSubmission">
+   <b><a href="#MemberSubmission">#MemberSubmission</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-MemberSubmission">10. 
+Member Submission Process</a> <a href="#ref-for-MemberSubmission①">(2)</a> <a href="#ref-for-MemberSubmission②">(3)</a> <a href="#ref-for-MemberSubmission③">(4)</a>
+    <li><a href="#ref-for-MemberSubmission④">10.1. 
+Submitter Rights and Obligations</a>
+    <li><a href="#ref-for-MemberSubmission⑤">10.2. 
+Team Rights and Obligations</a>
+    <li><a href="#ref-for-MemberSubmission⑥">10.3. 
+Acknowledgment of a Submission Request</a>
+    <li><a href="#ref-for-MemberSubmission⑦"> Changes related to the role of the Director</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="submitter">
+   <b><a href="#submitter">#submitter</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-submitter">10. 
+Member Submission Process</a> <a href="#ref-for-submitter①">(2)</a> <a href="#ref-for-submitter②">(3)</a> <a href="#ref-for-submitter③">(4)</a>
+    <li><a href="#ref-for-submitter④">10.1. 
+Submitter Rights and Obligations</a> <a href="#ref-for-submitter⑤">(2)</a> <a href="#ref-for-submitter⑥">(3)</a> <a href="#ref-for-submitter⑦">(4)</a> <a href="#ref-for-submitter⑧">(5)</a> <a href="#ref-for-submitter⑨">(6)</a>
+    <li><a href="#ref-for-submitter①⓪">10.1.2. 
+Information Required in a Submission Request</a> <a href="#ref-for-submitter①①">(2)</a> <a href="#ref-for-submitter①②">(3)</a> <a href="#ref-for-submitter①③">(4)</a>
+    <li><a href="#ref-for-submitter①④">10.2. 
+Team Rights and Obligations</a>
+    <li><a href="#ref-for-submitter①⑤">10.3. 
+Acknowledgment of a Submission Request</a> <a href="#ref-for-submitter①⑥">(2)</a> <a href="#ref-for-submitter①⑦">(3)</a>
+    <li><a href="#ref-for-submitter①⑧">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a> <a href="#ref-for-submitter①⑨">(2)</a> <a href="#ref-for-submitter②⓪">(3)</a> <a href="#ref-for-submitter②①">(4)</a> <a href="#ref-for-submitter②②">(5)</a> <a href="#ref-for-submitter②③">(6)</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="validation-notice">
+   <b><a href="#validation-notice">#validation-notice</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-validation-notice">10.3. 
+Acknowledgment of a Submission Request</a>
+   </ul>
+  </aside>
+  <aside class="dfn-panel" data-for="submission-appeals">
+   <b><a href="#submission-appeals">#submission-appeals</a></b><b>Referenced in:</b>
+   <ul>
+    <li><a href="#ref-for-submission-appeals">10.4. 
+Rejection of a Submission Request, and Submission Appeals</a>
+    <li><a href="#ref-for-submission-appeals①"> Changes related to the role of the Director</a> <a href="#ref-for-submission-appeals②">(2)</a>
+   </ul>
+  </aside>
+<script>/* script-dfn-panel */
+
+document.body.addEventListener("click", function(e) {
+    var queryAll = function(sel) { return [].slice.call(document.querySelectorAll(sel)); }
+    // Find the dfn element or panel, if any, that was clicked on.
+    var el = e.target;
+    var target;
+    var hitALink = false;
+    while(el.parentElement) {
+        if(el.tagName == "A") {
+            // Clicking on a link in a <dfn> shouldn't summon the panel
+            hitALink = true;
+        }
+        if(el.classList.contains("dfn-paneled")) {
+            target = "dfn";
+            break;
+        }
+        if(el.classList.contains("dfn-panel")) {
+            target = "dfn-panel";
+            break;
+        }
+        el = el.parentElement;
+    }
+    if(target != "dfn-panel") {
+        // Turn off any currently "on" or "activated" panels.
+        queryAll(".dfn-panel.on, .dfn-panel.activated").forEach(function(el){
+            el.classList.remove("on");
+            el.classList.remove("activated");
+        });
+    }
+    if(target == "dfn" && !hitALink) {
+        // open the panel
+        var dfnPanel = document.querySelector(".dfn-panel[data-for='" + el.id + "']");
+        if(dfnPanel) {
+            dfnPanel.classList.add("on");
+            var rect = el.getBoundingClientRect();
+            dfnPanel.style.left = window.scrollX + rect.right + 5 + "px";
+            dfnPanel.style.top = window.scrollY + rect.top + "px";
+            var panelRect = dfnPanel.getBoundingClientRect();
+            var panelWidth = panelRect.right - panelRect.left;
+            if(panelRect.right > document.body.scrollWidth && (rect.left - (panelWidth + 5)) > 0) {
+                // Reposition, because the panel is overflowing
+                dfnPanel.style.left = window.scrollX + rect.left - (panelWidth + 5) + "px";
+            }
+        } else {
+            console.log("Couldn't find .dfn-panel[data-for='" + el.id + "']");
+        }
+    } else if(target == "dfn-panel") {
+        // Switch it to "activated" state, which pins it.
+        el.classList.add("activated");
+        el.style.left = null;
+        el.style.top = null;
+    }
+
+});
+</script>

From 343278e218bc11b33565b6c6c4ab1ee5dcad6dd4 Mon Sep 17 00:00:00 2001
From: Daniel <dmontalvo@w3.org>
Date: Mon, 12 Jun 2023 17:02:47 +0200
Subject: [PATCH 002/237] Teaks -> tweaks

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index ae59b6a1..cca35334 100644
--- a/index.bs
+++ b/index.bs
@@ -5651,7 +5651,7 @@ Changes since the <a href="https://www.w3.org/2021/Process-20211102/">2 November
 	are available.
 
 	In addition to a number of editorial adjustments
-	and minor teaks,
+	and minor tweaks,
 	the following is a summary of the main differences:
 
 <h4 id=dirfree-changes>

From 9c3fc1eeda395946d1efcfb93089777c6a95edf8 Mon Sep 17 00:00:00 2001
From: Denis Ah-Kang <denis@w3.org>
Date: Tue, 20 Jun 2023 16:44:23 +0400
Subject: [PATCH 003/237] new website has been deployed

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index cca35334..d7badec0 100644
--- a/index.bs
+++ b/index.bs
@@ -6029,7 +6029,7 @@ Changes since earlier versions</h3>
 		"title": "W3C IPR Policies"
 	},
 	"COUNCIL-REPORT-INDEX": {
-		"href": "https://beta.w3.org/about/council/",
+		"href": "https://www.w3.org/about/council/",
 		"title": "Council Report Index"
 	}
 

From e5fdfc4f6390815b9b9db03e3036011e34fb348b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Sat, 1 Jul 2023 21:50:49 +0900
Subject: [PATCH 004/237] Post publication update

---
 index.bs | 177 ++++---------------------------------------------------
 1 file changed, 10 insertions(+), 167 deletions(-)

diff --git a/index.bs b/index.bs
index d7badec0..10b9fb98 100644
--- a/index.bs
+++ b/index.bs
@@ -29,6 +29,7 @@ Group: processcg
 Status: CG-DRAFT
 ED: https://www.w3.org/Consortium/Process/Drafts/
 TR: https://www.w3.org/Consortium/Process/
+Previous Version: https://www.w3.org/2023/Process-20230612/
 Previous Version: https://www.w3.org/2021/Process-20211102/
 Previous Version: https://www.w3.org/2020/Process-20200915/
 Previous Version: https://www.w3.org/2019/Process-20190301/
@@ -53,14 +54,12 @@ Abstract:
 	please refer to <a href="https://www.w3.org/Consortium/">About W3C</a>.
 Status Text:
 	This document,
-	which is based on the <a href="https://www.w3.org/2021/Process-20211102/">2 November 2021 Process</a>,
+	which is based on the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 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/Consortium/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.
-	A <a href="https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-04">7 April snapshot</a> was created
-	and sent for W3C Advisory Committee Review on 12 April 2023.
 Issue Tracking: Github (preferred) https://github.com/w3c/w3process/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
@@ -5640,182 +5639,26 @@ Changes</h2>
 
 	<em>This section is non-normative.</em>
 
-<h3 id=changes-2021 class=no-num>
-Changes since the <a href="https://www.w3.org/2021/Process-20211102/">2 November 2021 Process</a></h3>
+<h3 id=changes-2023 class=no-num>
+Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a></h3>
 
-	<p>This document is based on the <a href="https://www.w3.org/2021/Process-20211102/">2 November 2021 Process</a>.
-	A <a href="https://github.com/w3c/w3process/issues?q=milestone%3A%22Process+2022%22+is%3Aclosed">list of issues addressed</a>,
-	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2F">diff from Process 2021 to this latest version</a>,
+	<p>This document is based on the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a>.
+	A <a href="https://github.com/w3c/w3process/issues?q=milestone%3A%22Process+2023-1%22+is%3Aclosed">list of issues addressed</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2F">diff from Process 2023 to this latest version</a>,
 	as well as
-	a <a href="https://github.com/w3c/w3process/compare/p2021...main">detailed log of all changes since then</a>
+	a <a href="https://github.com/w3c/w3process/compare/p2023...main">detailed log of all changes since then</a>
 	are available.
 
 	In addition to a number of editorial adjustments
 	and minor tweaks,
 	the following is a summary of the main differences:
 
-<h4 id=dirfree-changes>
-Changes related to the role of the Director</h4>
-
 	<ul>
-		<li>
-			<a href="#ACReviewAfter">Outcomes of AC Reviews</a> are no longer unconstrained decisions (by the Director),
-			but instead must be based on the content of the review,
-			with specific rules (based on current best practices)
-			about what can or cannot be adjusted post review,
-			and under what circumstances.
-
-		<li>
-			Rather than the Director, the [=W3C Council=],
-			which is composed of TAG+AB+CEO,
-			will now hear and resolve formal objections.
-
-		<li>
-			The W3C Council will also hear [=Submission Appeals=],
-			which were previously handled separately by either the TAG or the AB,
-			depending on the grounds for the appeal.
-
-		<li>
-			The [=Team=] rather than the Director is charged with
-			[[#TAG-appointments|appointing]] the 3 non-elected [=TAG=] members,
-			subject to ratification by the [=TAG=] and [=AB=].
-
-		<li>
-			There is no longer an ex-officio seat for the Director on the [=TAG=],
-			but Tim Berners-Lee personally does continue to hold one.
-
-		<li>
-			The [=Team=] rather than the Director is charged with verification that the various expectations of the Process
-			have been fulfilled for [=Transition Requests=] and [=Update Requests=].
-
-		<li>
-			Require AB and TAG approval when the [=Team=] wants to
-			<a href="#rec-track-regression">lower the maturity stage</a>
-			of a technical report without a [=Group Decision=].
-
-		<li>
-			The [=Team=], [=AB=], or [=TAG=] rather than the Director is now responsible
-			for proposing group creation and forcible closure;
-			[=AC Review=] is now required for forcible <a href="#GeneralTermination">group closure</a>
-			(it already was for group creation).
-
-		<li>
-			The [=CEO=] rather than the Director is charged with [[#discipline|disciplinary questions]].
-
-		<li>
-			The [=Team=] rather than the Director is charged with negotiating [=MoUs=]
-			(now called [=technical agreements=])
-			and other agreements related to the technical program.
-
-		<li>
-			The [=Team=] rather than the Director is charged with handling various participation-related judgement calls
-			(see [[#MemberAssoc]], [[#coi]], [[#member-rep]], [[#ReqsAllGroups]], and [[#invited-expert-wg]]).
-
-		<li>
-			The [=Team=] rather than the Director is charged with handling [=Member Submission=] requests
-			(but see also [=Submission Appeals=]).
+		<li><em>None yet</em>
 	</ul>
 
-<h4 id=other-gov-changes>
-Other Governance Changes</h4>
-
-	<ul>
-		<li>
-			The [=TAG=] now picks its own chair(s),
-			and the timing of AB and TAG chair selection is clarified.
-
-		<li>
-			Appointed [=TAG=] seats now have consecutive term limits.
-
-		<li>
-			Remove mentions of the Hosts,
-			add recognition of the existence of the W3C Inc. Board of Directors,
-			and adjust language for W3C being rooted in W3C Inc.
-
-		<li>
-			Codify that the AB is expected to pick up to two of its participants
-			as <a href="#ab-bod-liaison">liaisons for the board</a>.
-
-		<li>
-			Clarify interactions between AC / Team / Board about MoUs
-			(now called [=technical agreements=]).
-	</ul>
-
-<h4 id=misc-changes>
-Other miscellaneous changes</h4>
-
-	<ul>
-		<li>
-			Improve the definition of consensus
-			to make the notion usable even in contexts
-			where Formal Objections would be inappropriate
-			(such as inside a W3C Council,
-			or when the TAG or AB pick their chair),
-			and to avoid circular definitions.
-
-		<li>
-			Merge Chair Decision Appeal, Group Decision Appeal, and Formal Objection;
-			clarify what can be objected to.
-
-		<li>
-			Define editorial vs substantive changes for non-REC-track documents.
-
-		<li>
-			Expect supporting material to meeting minutes to be archived as the minutes are.
-
-		<li>
-			Encourage people requesting an [=AC Appeal=]
-			to share their request with the [=Advisory Committee=]
-			in addition to the [=Team=].
-
-		<li>
-			Allow [=Recommendations=] to transition directly to [=Working Draft=]
-			without having to go through [=Candidate Recommendation=]
-			when making [[#revised-rec-substantive|substantive changes]].
-
-		<li>
-			Place the W3C Document License under the same <a href="#GAProcess">revision process and requirements</a>
-			as this document, the CEPC, or the Patent Policy.
-
-		<li>
-			Similarly to the pre-existing requirement that a public record be made
-			about confidential Formal Objections about public things,
-			added a requirement that a member visible record be made
-			about confidential Formal Objections about member-visible things.
-
-		<li>
-			Stop excluding comments from AC Reps from those that have to be addressed
-			while [[#transition-pr|transitioning to Proposed Recommendation]];
-			just because there will be an opportunity to address them later
-			doesn't mean they shouldn't be handled at the first opportunity.
-
-		<li>
-			Clarify what the term [=Candidate Recommendation review period=] refers to.
-
-		<li>
-			Clarify how the advance notice period for [=MoU=] works.
-
-		<li>
-			Various bits of information that were so far required
-			to be included in announcements of [=charter extensions=]
-			are covered in the group's homepage,
-			making it sufficient to point to that page
-			rather than having to inline everything in the announcement.
-
-		<li>
-			Be more rigorous in references to the Patent Policy,
-			using dated versions when appropriate.
-
-		<li>
-			Rename “Member Consortia” into [=Member Associations=]
-			to align with terminology in the Bylaws
-			(and to avoid confusion with W3C itself).
-
-		<li>
-			Rename “maturity level” into “maturity stage”.
-	</ul>
 
-<h3 id=changes-previous class=no-num oldids="changes-2020, changes-2019, changes-2018, changes-2017">
+<h3 id=changes-previous class=no-num oldids="changes-2021, changes-2020, changes-2019, changes-2018, changes-2017">
 Changes since earlier versions</h3>
 
 	Changes since earlier versions of the Process are detailed

From f9b0ff28092e2be49416c0e56ace69cc88969e5e Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 25 Jul 2023 15:24:57 +0800
Subject: [PATCH 005/237] Expand the TAG from 6+3 to 8+3 participants (#733)

As requested by the TAG and resolved by the AB, and discussed in https://github.com/w3c/AB-memberonly/issues/171.
---
 index.bs | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/index.bs b/index.bs
index 10b9fb98..2a2ad197 100644
--- a/index.bs
+++ b/index.bs
@@ -1005,7 +1005,7 @@ Composition of the Technical Architecture Group</h5>
 			Three participants [[#TAG-appointments|appointed by the Team]];
 
 		<li>
-			Six participants elected by the [=Advisory Committee=]
+			Eight participants elected by the [=Advisory Committee=]
 			following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.
 	</ul>
 
@@ -1022,7 +1022,7 @@ Composition of the Technical Architecture Group</h5>
 	as described in <a href="#ReqsAllGroups"></a>.
 
 	The terms of TAG participants last for <span class="time-interval">two years</span>.
-	Terms are staggered so that three elected terms
+	Terms are staggered so that four elected terms
 	and either one or two appointed terms expire each year.
 	If an individual is appointed or elected to fill an incomplete term,
 	that individual's term ends at the normal expiration date of that term.
@@ -1135,7 +1135,7 @@ Advisory Board and Technical Architecture Group Elections</h5>
 
 	In the case of regularly scheduled elections of the [=TAG=],
 	the minimum and maximum number of available seats are the same:
-	the 3 seats of the terms expiring that year,
+	the 4 seats of the terms expiring that year,
 	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats.
 
 	In the case of regularly scheduled elections of the [=AB=],
@@ -1358,7 +1358,7 @@ Elected Groups Vacated Seats</h5>
 			the minimum number of available seats is such that
 			when added to the number of continuing participants,
 			the minimum total number of elected seats is met
-			(6 for the [=TAG=], 9 for the [=AB=]);
+			(8 for the [=TAG=], 9 for the [=AB=]);
 			and the maximum number corresponds to all unoccupied seats.
 			Except for the number of available seats and the length of the terms,
 			the <a href="#AB-TAG-elections">usual rules for Advisory Board and Technical Architecture Group Elections</a> apply.
@@ -5654,7 +5654,9 @@ Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 20
 	the following is a summary of the main differences:
 
 	<ul>
-		<li><em>None yet</em>
+  		<li>  
+			Expand the TAG from 6 elected and 3 appointed to 8 and 3,
+			to deal with the increased workload.
 	</ul>
 
 

From 7fa69e4a6b956c79c3d47c9d3578d89fc52353e3 Mon Sep 17 00:00:00 2001
From: w3cgruntbot <87540780+w3cgruntbot@users.noreply.github.com>
Date: Tue, 25 Jul 2023 09:26:49 +0200
Subject: [PATCH 006/237] Update Changes section

---
 index.bs | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index 2a2ad197..bcacda96 100644
--- a/index.bs
+++ b/index.bs
@@ -5639,7 +5639,7 @@ Changes</h2>
 
 	<em>This section is non-normative.</em>
 
-<h3 id=changes-2023 class=no-num>
+<h3 id=changes-2023-1 class=no-num>
 Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a></h3>
 
 	<p>This document is based on the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a>.
@@ -5649,9 +5649,13 @@ Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 20
 	a <a href="https://github.com/w3c/w3process/compare/p2023...main">detailed log of all changes since then</a>
 	are available.
 
+	<!--
 	In addition to a number of editorial adjustments
 	and minor tweaks,
 	the following is a summary of the main differences:
+	-->
+
+	The only change is:
 
 	<ul>
   		<li>  
@@ -5660,11 +5664,11 @@ Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 20
 	</ul>
 
 
-<h3 id=changes-previous class=no-num oldids="changes-2021, changes-2020, changes-2019, changes-2018, changes-2017">
+<h3 id=changes-previous class=no-num oldids="changes-2023, changes-2021, changes-2020, changes-2019, changes-2018, changes-2017">
 Changes since earlier versions</h3>
 
 	Changes since earlier versions of the Process are detailed
-	in the <a href="https://www.w3.org/2021/Process-20211102/#changes">changes section of the previous version</a>
+	in the <a href="https://www.w3.org/2023/Process-20230612/#changes">changes section of the previous version</a>
 	of the Process.
 
 <pre class=biblio>

From 3a79292c53f65d1e8c818340b24f8e2420603ed4 Mon Sep 17 00:00:00 2001
From: w3cgruntbot <87540780+w3cgruntbot@users.noreply.github.com>
Date: Tue, 25 Jul 2023 09:31:45 +0200
Subject: [PATCH 007/237] Update affiliation

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index bcacda96..887b6305 100644
--- a/index.bs
+++ b/index.bs
@@ -35,7 +35,7 @@ Previous Version: https://www.w3.org/2020/Process-20200915/
 Previous Version: https://www.w3.org/2019/Process-20190301/
 Previous Version: https://www.w3.org/2018/Process-20180201/
 Previous Version: https://www.w3.org/2017/Process-20170301/
-Editor: Elika J. Etemad / fantasai, Invited Expert, https://fantasai.inkedblade.net/contact
+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, http://yandex.com

From 9efa7e4f400debaab02ec77ccbacb7ea4847feb2 Mon Sep 17 00:00:00 2001
From: w3cgruntbot <87540780+w3cgruntbot@users.noreply.github.com>
Date: Wed, 2 Aug 2023 20:43:49 -0400
Subject: [PATCH 008/237] White space fix

---
 index.bs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 887b6305..bd5462cc 100644
--- a/index.bs
+++ b/index.bs
@@ -3010,8 +3010,8 @@ Classes of Changes</h4>
 			2. Changes that do not functionally affect interpretation of the document
 		<dd>
 			For [=Recommendation-track=] [=technical reports=] specifically,
-            this constitutes changes that do not affect conformance,
-            i.e. changes that reasonable implementers
+			this constitutes changes that do not affect conformance,
+			i.e. changes that reasonable implementers
 			would not interpret as changing architectural
 			or interoperability requirements
 			or their implementation.
@@ -3034,7 +3034,7 @@ Classes of Changes</h4>
 			3. Other changes that do not add new features
 		<dd>
 			For [=Recommendation-track=] documents,
-            these changes <em class="rfc2119">may</em> affect conformance to the specification.
+			these changes <em class="rfc2119">may</em> affect conformance to the specification.
 			A change that affects conformance is one that:
 
 			<ul>
@@ -5658,7 +5658,7 @@ Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 20
 	The only change is:
 
 	<ul>
-  		<li>  
+		<li>
 			Expand the TAG from 6 elected and 3 appointed to 8 and 3,
 			to deal with the increased workload.
 	</ul>

From 7608c9f4e9be32bea334bc8fc90724fb657dc936 Mon Sep 17 00:00:00 2001
From: w3cgruntbot <87540780+w3cgruntbot@users.noreply.github.com>
Date: Wed, 2 Aug 2023 21:05:52 -0400
Subject: [PATCH 009/237] Update changes section

---
 index.bs                      | 4 ++--
 snapshots/2023-05-24-doc.bsi  | 2 +-
 snapshots/2023-05-24-doc.html | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index bd5462cc..5b6b6cb1 100644
--- a/index.bs
+++ b/index.bs
@@ -5659,8 +5659,8 @@ Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 20
 
 	<ul>
 		<li>
-			Expand the TAG from 6 elected and 3 appointed to 8 and 3,
-			to deal with the increased workload.
+			Expand the TAG from 6 elected and 3 appointed to 8 and 3.
+			See <a href="https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-05-24-doc#tag-size">the 2023-05-24 Disposition of Comments</a> for rationale.
 	</ul>
 
 
diff --git a/snapshots/2023-05-24-doc.bsi b/snapshots/2023-05-24-doc.bsi
index 96e5bdad..22262dc5 100644
--- a/snapshots/2023-05-24-doc.bsi
+++ b/snapshots/2023-05-24-doc.bsi
@@ -39,7 +39,7 @@ ul.details li {
 <p>Several review comments received during the AC Review period generated proposals for substantive changes:
 
 <ul class="details substantive">
-  <li><details id="tag-size">
+  <li><details id="tag-size" open>
     <summary>Increasing the size of the TAG</summary>
 
     <p class="metadata">
diff --git a/snapshots/2023-05-24-doc.html b/snapshots/2023-05-24-doc.html
index 5cc521d5..2e4de579 100644
--- a/snapshots/2023-05-24-doc.html
+++ b/snapshots/2023-05-24-doc.html
@@ -68,7 +68,7 @@ <h1>W3C Process Document 2023 (AC Review) Disposition of Comments for 2023-05-24
 <h2>Substantive Changes</h2>
 <p>Several review comments received during the AC Review period generated proposals for substantive changes:
 <ul class="details substantive">
-  <li><details id="tag-size">
+  <li><details id="tag-size" open>
     <summary>Increasing the size of the TAG</summary>
     <p class="metadata">
     See key discussion points in <a href="#issue-24">Issue #24</a>

From 80cac31c369377b5df60b4dab69f55f680d3f4d8 Mon Sep 17 00:00:00 2001
From: w3cgruntbot <87540780+w3cgruntbot@users.noreply.github.com>
Date: Wed, 2 Aug 2023 21:07:47 -0400
Subject: [PATCH 010/237] Add snapshot for P2023 revision 1

---
 snapshots/2023-08.html | 5821 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 5821 insertions(+)
 create mode 100644 snapshots/2023-08.html

diff --git a/snapshots/2023-08.html b/snapshots/2023-08.html
new file mode 100644
index 00000000..fb711fb0
--- /dev/null
+++ b/snapshots/2023-08.html
@@ -0,0 +1,5821 @@
+<!doctype html><html lang="en">
+ <head>
+  <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+  <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
+  <title>W3C Process Document</title>
+  <meta content="CG-DRAFT" name="w3c-status">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/cg-draft" rel="stylesheet">
+  <meta content="Bikeshed version fcb66286b, updated Wed Jul 19 11:14:33 2023 -0700" name="generator">
+  <link href="https://www.w3.org/Consortium/Process/" rel="canonical">
+  <meta content="7608c9f4e9be32bea334bc8fc90724fb657dc936" name="document-revision">
+<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 ellipse {
+	stroke-width: 4px;
+}
+g g:hover path,
+g g:hover polygon,
+g g:hover ellipse {
+	stroke-width: 4px;
+}
+: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>
+<style>/* Boilerplate: style-autolinks */
+.css.css, .property.property, .descriptor.descriptor {
+    color: var(--a-normal-text);
+    font-size: inherit;
+    font-family: inherit;
+}
+.css::before, .property::before, .descriptor::before {
+    content: "‘";
+}
+.css::after, .property::after, .descriptor::after {
+    content: "’";
+}
+.property, .descriptor {
+    /* Don't wrap property and descriptor names */
+    white-space: nowrap;
+}
+.type { /* CSS value <type> */
+    font-style: italic;
+}
+pre .property::before, pre .property::after {
+    content: "";
+}
+[data-link-type="property"]::before,
+[data-link-type="propdesc"]::before,
+[data-link-type="descriptor"]::before,
+[data-link-type="value"]::before,
+[data-link-type="function"]::before,
+[data-link-type="at-rule"]::before,
+[data-link-type="selector"]::before,
+[data-link-type="maybe"]::before {
+    content: "‘";
+}
+[data-link-type="property"]::after,
+[data-link-type="propdesc"]::after,
+[data-link-type="descriptor"]::after,
+[data-link-type="value"]::after,
+[data-link-type="function"]::after,
+[data-link-type="at-rule"]::after,
+[data-link-type="selector"]::after,
+[data-link-type="maybe"]::after {
+    content: "’";
+}
+
+[data-link-type].production::before,
+[data-link-type].production::after,
+.prod [data-link-type]::before,
+.prod [data-link-type]::after {
+    content: "";
+}
+
+[data-link-type=element],
+[data-link-type=element-attr] {
+    font-family: Menlo, Consolas, "DejaVu Sans Mono", monospace;
+    font-size: .9em;
+}
+[data-link-type=element]::before { content: "<" }
+[data-link-type=element]::after  { content: ">" }
+
+[data-link-type=biblio] {
+    white-space: pre;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --selflink-text: black;
+        --selflink-bg: silver;
+        --selflink-hover-text: white;
+    }
+}
+</style>
+<style>/* Boilerplate: style-colors */
+
+/* Any --*-text not paired with a --*-bg is assumed to have a transparent bg */
+:root {
+    color-scheme: light dark;
+
+    --text: black;
+    --bg: white;
+
+    --unofficial-watermark: url(https://www.w3.org/StyleSheets/TR/2016/logos/UD-watermark);
+
+    --logo-bg: #1a5e9a;
+    --logo-active-bg: #c00;
+    --logo-text: white;
+
+    --tocnav-normal-text: #707070;
+    --tocnav-normal-bg: var(--bg);
+    --tocnav-hover-text: var(--tocnav-normal-text);
+    --tocnav-hover-bg: #f8f8f8;
+    --tocnav-active-text: #c00;
+    --tocnav-active-bg: var(--tocnav-normal-bg);
+
+    --tocsidebar-text: var(--text);
+    --tocsidebar-bg: #f7f8f9;
+    --tocsidebar-shadow: rgba(0,0,0,.1);
+    --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+    --toclink-text: var(--text);
+    --toclink-underline: #3980b5;
+    --toclink-visited-text: var(--toclink-text);
+    --toclink-visited-underline: #054572;
+
+    --heading-text: #005a9c;
+
+    --hr-text: var(--text);
+
+    --algo-border: #def;
+
+    --del-text: red;
+    --del-bg: transparent;
+    --ins-text: #080;
+    --ins-bg: transparent;
+
+    --a-normal-text: #034575;
+    --a-normal-underline: #bbb;
+    --a-visited-text: var(--a-normal-text);
+    --a-visited-underline: #707070;
+    --a-hover-bg: rgba(75%, 75%, 75%, .25);
+    --a-active-text: #c00;
+    --a-active-underline: #c00;
+
+    --blockquote-border: silver;
+    --blockquote-bg: transparent;
+    --blockquote-text: currentcolor;
+
+    --issue-border: #e05252;
+    --issue-bg: #fbe9e9;
+    --issue-text: var(--text);
+    --issueheading-text: #831616;
+
+    --example-border: #e0cb52;
+    --example-bg: #fcfaee;
+    --example-text: var(--text);
+    --exampleheading-text: #574b0f;
+
+    --note-border: #52e052;
+    --note-bg: #e9fbe9;
+    --note-text: var(--text);
+    --noteheading-text: hsl(120, 70%, 30%);
+    --notesummary-underline: silver;
+
+    --assertion-border: #aaa;
+    --assertion-bg: #eee;
+    --assertion-text: black;
+
+    --advisement-border: orange;
+    --advisement-bg: #fec;
+    --advisement-text: var(--text);
+    --advisementheading-text: #b35f00;
+
+    --warning-border: red;
+    --warning-bg: hsla(40,100%,50%,0.95);
+    --warning-text: var(--text);
+
+    --amendment-border: #330099;
+    --amendment-bg: #F5F0FF;
+    --amendment-text: var(--text);
+    --amendmentheading-text: #220066;
+
+    --def-border: #8ccbf2;
+    --def-bg: #def;
+    --def-text: var(--text);
+    --defrow-border: #bbd7e9;
+
+    --datacell-border: silver;
+
+    --indexinfo-text: #707070;
+
+    --indextable-hover-text: black;
+    --indextable-hover-bg: #f7f8f9;
+
+    --outdatedspec-bg: rgba(0, 0, 0, .5);
+    --outdatedspec-text: black;
+    --outdated-bg: maroon;
+    --outdated-text: white;
+    --outdated-shadow: red;
+
+    --editedrec-bg: darkorange;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --text: #ddd;
+        --bg: black;
+
+        --unofficial-watermark: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='400' height='400'%3E%3Cg fill='%23100808' transform='translate(200 200) rotate(-45) translate(-200 -200)' stroke='%23100808' stroke-width='3'%3E%3Ctext x='50%25' y='220' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EUNOFFICIAL%3C/text%3E%3Ctext x='50%25' y='305' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EDRAFT%3C/text%3E%3C/g%3E%3C/svg%3E");
+
+        --logo-bg: #1a5e9a;
+        --logo-active-bg: #c00;
+        --logo-text: white;
+
+        --tocnav-normal-text: #999;
+        --tocnav-normal-bg: var(--bg);
+        --tocnav-hover-text: var(--tocnav-normal-text);
+        --tocnav-hover-bg: #080808;
+        --tocnav-active-text: #f44;
+        --tocnav-active-bg: var(--tocnav-normal-bg);
+
+        --tocsidebar-text: var(--text);
+        --tocsidebar-bg: #080808;
+        --tocsidebar-shadow: rgba(255,255,255,.1);
+        --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+        --toclink-text: var(--text);
+        --toclink-underline: #6af;
+        --toclink-visited-text: var(--toclink-text);
+        --toclink-visited-underline: #054572;
+
+        --heading-text: #8af;
+
+        --hr-text: var(--text);
+
+        --algo-border: #456;
+
+        --del-text: #f44;
+        --del-bg: transparent;
+        --ins-text: #4a4;
+        --ins-bg: transparent;
+
+        --a-normal-text: #6af;
+        --a-normal-underline: #555;
+        --a-visited-text: var(--a-normal-text);
+        --a-visited-underline: var(--a-normal-underline);
+        --a-hover-bg: rgba(25%, 25%, 25%, .2);
+        --a-active-text: #f44;
+        --a-active-underline: var(--a-active-text);
+
+        --borderedblock-bg: rgba(255, 255, 255, .05);
+
+        --blockquote-border: silver;
+        --blockquote-bg: var(--borderedblock-bg);
+        --blockquote-text: currentcolor;
+
+        --issue-border: #e05252;
+        --issue-bg: var(--borderedblock-bg);
+        --issue-text: var(--text);
+        --issueheading-text: hsl(0deg, 70%, 70%);
+
+        --example-border: hsl(50deg, 90%, 60%);
+        --example-bg: var(--borderedblock-bg);
+        --example-text: var(--text);
+        --exampleheading-text: hsl(50deg, 70%, 70%);
+
+        --note-border: hsl(120deg, 100%, 35%);
+        --note-bg: var(--borderedblock-bg);
+        --note-text: var(--text);
+        --noteheading-text: hsl(120, 70%, 70%);
+        --notesummary-underline: silver;
+
+        --assertion-border: #444;
+        --assertion-bg: var(--borderedblock-bg);
+        --assertion-text: var(--text);
+
+        --advisement-border: orange;
+        --advisement-bg: #222218;
+        --advisement-text: var(--text);
+        --advisementheading-text: #f84;
+
+        --warning-border: red;
+        --warning-bg: hsla(40,100%,20%,0.95);
+        --warning-text: var(--text);
+
+        --amendment-border: #330099;
+        --amendment-bg: #080010;
+        --amendment-text: var(--text);
+        --amendmentheading-text: #cc00ff;
+
+        --def-border: #8ccbf2;
+        --def-bg: #080818;
+        --def-text: var(--text);
+        --defrow-border: #136;
+
+        --datacell-border: silver;
+
+        --indexinfo-text: #aaa;
+
+        --indextable-hover-text: var(--text);
+        --indextable-hover-bg: #181818;
+
+        --outdatedspec-bg: rgba(255, 255, 255, .5);
+        --outdatedspec-text: black;
+        --outdated-bg: maroon;
+        --outdated-text: white;
+        --outdated-shadow: red;
+
+        --editedrec-bg: darkorange;
+    }
+    /* In case a transparent-bg image doesn't expect to be on a dark bg,
+       which is quite common in practice... */
+    img { background: white; }
+}
+</style>
+<style>/* Boilerplate: style-counters */
+body {
+    counter-reset: example figure issue;
+}
+.issue {
+    counter-increment: issue;
+}
+.issue:not(.no-marker)::before {
+    content: "Issue " counter(issue);
+}
+
+.example {
+    counter-increment: example;
+}
+.example:not(.no-marker)::before {
+    content: "Example " counter(example);
+}
+.invalid.example:not(.no-marker)::before,
+.illegal.example:not(.no-marker)::before {
+    content: "Invalid Example" counter(example);
+}
+
+figcaption {
+    counter-increment: figure;
+}
+figcaption:not(.no-marker)::before {
+    content: "Figure " counter(figure) " ";
+}
+</style>
+<style>/* Boilerplate: style-dfn-panel */
+:root {
+    --dfnpanel-bg: #ddd;
+    --dfnpanel-text: var(--text);
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --dfnpanel-bg: #222;
+        --dfnpanel-text: var(--text);
+    }
+}
+.dfn-panel {
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.75em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--dfnpanel-bg);
+    color: var(--dfnpanel-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+.dfn-panel:not(.on) { display: none; }
+.dfn-panel * { margin: 0; padding: 0; text-indent: 0; }
+.dfn-panel > b { display: block; }
+.dfn-panel a { color: var(--dfnpanel-text); }
+.dfn-panel a:not(:hover) { text-decoration: none !important; border-bottom: none !important; }
+.dfn-panel > b + b { margin-top: 0.25em; }
+.dfn-panel ul { padding: 0 0 0 1em; list-style: none; }
+.dfn-panel li a {
+    white-space: pre;
+    display: inline-block;
+    max-width: calc(300px - 1.5em - 1em);
+    overflow: hidden;
+    text-overflow: ellipsis;
+}
+
+.dfn-panel.activated {
+    display: inline-block;
+    position: fixed;
+    left: .5em;
+    bottom: 2em;
+    margin: 0 auto;
+    max-width: calc(100vw - 1.5em - .4em - .5em);
+    max-height: 30vh;
+}
+
+.dfn-paneled[role="button"] { cursor: pointer; }
+</style>
+<style>/* Boilerplate: style-dfn-panel */
+:root {
+    --dfnpanel-bg: #ddd;
+    --dfnpanel-text: var(--text);
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --dfnpanel-bg: #222;
+        --dfnpanel-text: var(--text);
+    }
+}
+.dfn-panel {
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.75em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--dfnpanel-bg);
+    color: var(--dfnpanel-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+.dfn-panel:not(.on) { display: none; }
+.dfn-panel * { margin: 0; padding: 0; text-indent: 0; }
+.dfn-panel > b { display: block; }
+.dfn-panel a { color: var(--dfnpanel-text); }
+.dfn-panel a:not(:hover) { text-decoration: none !important; border-bottom: none !important; }
+.dfn-panel > b + b { margin-top: 0.25em; }
+.dfn-panel ul { padding: 0 0 0 1em; list-style: none; }
+.dfn-panel li a {
+    white-space: pre;
+    display: inline-block;
+    max-width: calc(300px - 1.5em - 1em);
+    overflow: hidden;
+    text-overflow: ellipsis;
+}
+
+.dfn-panel.activated {
+    display: inline-block;
+    position: fixed;
+    left: .5em;
+    bottom: 2em;
+    margin: 0 auto;
+    max-width: calc(100vw - 1.5em - .4em - .5em);
+    max-height: 30vh;
+}
+
+.dfn-paneled[role="button"] { cursor: pointer; }
+</style>
+<style>/* Boilerplate: style-issues */
+a[href].issue-return {
+    float: right;
+    float: inline-end;
+    color: var(--issueheading-text);
+    font-weight: bold;
+    text-decoration: none;
+}
+</style>
+<style>/* Boilerplate: style-md-lists */
+/* This is a weird hack for me not yet following the commonmark spec
+   regarding paragraph and lists. */
+[data-md] > :first-child {
+    margin-top: 0;
+}
+[data-md] > :last-child {
+    margin-bottom: 0;
+}
+</style>
+<style>/* Boilerplate: style-selflinks */
+
+:root {
+    --selflink-text: white;
+    --selflink-bg: gray;
+    --selflink-hover-text: black;
+}
+.heading, .issue, .note, .example, li, dt {
+    position: relative;
+}
+a.self-link {
+    position: absolute;
+    top: 0;
+    left: calc(-1 * (3.5rem - 26px));
+    width: calc(3.5rem - 26px);
+    height: 2em;
+    text-align: center;
+    border: none;
+    transition: opacity .2s;
+    opacity: .5;
+}
+a.self-link:hover {
+    opacity: 1;
+}
+.heading > a.self-link {
+    font-size: 83%;
+}
+.example > a.self-link,
+.note > a.self-link,
+.issue > a.self-link {
+    /* These blocks are overflow:auto, so positioning outside
+       doesn't work. */
+    left: auto;
+    right: 0;
+}
+li > a.self-link {
+    left: calc(-1 * (3.5rem - 26px) - 2em);
+}
+dfn > a.self-link {
+    top: auto;
+    left: auto;
+    opacity: 0;
+    width: 1.5em;
+    height: 1.5em;
+    background: var(--selflink-bg);
+    color: var(--selflink-text);
+    font-style: normal;
+    transition: opacity .2s, background-color .2s, color .2s;
+}
+dfn:hover > a.self-link {
+    opacity: 1;
+}
+dfn > a.self-link:hover {
+    color: var(--selflink-hover-text);
+}
+
+a.self-link::before            { content: "¶"; }
+.heading > a.self-link::before { content: "§"; }
+dfn > a.self-link::before      { content: "#"; }
+</style>
+ <body class="h-entry">
+  <div class="head">
+   <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
+   <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2023-08-02">2 August 2023</time></p>
+   <details open>
+    <summary>More details about this document</summary>
+    <div data-fill-with="spec-metadata">
+     <dl>
+      <dt>This version:
+      <dd><a class="u-url" href="https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-08">https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-08</a>
+      <dt>Editor's Draft:
+      <dd><a class="u-url" href="https://www.w3.org/Consortium/Process/Drafts/">https://www.w3.org/Consortium/Process/Drafts/</a>
+      <dt>Latest published version:
+      <dd><a href="https://www.w3.org/Consortium/Process/">https://www.w3.org/Consortium/Process/</a>
+      <dt>Previous Versions:
+      <dd><a href="https://www.w3.org/2023/Process-20230612/" rel="prev">https://www.w3.org/2023/Process-20230612/</a>
+      <dd><a href="https://www.w3.org/2021/Process-20211102/" rel="prev">https://www.w3.org/2021/Process-20211102/</a>
+      <dd><a href="https://www.w3.org/2020/Process-20200915/" rel="prev">https://www.w3.org/2020/Process-20200915/</a>
+      <dd><a href="https://www.w3.org/2019/Process-20190301/" rel="prev">https://www.w3.org/2019/Process-20190301/</a>
+      <dd><a href="https://www.w3.org/2018/Process-20180201/" rel="prev">https://www.w3.org/2018/Process-20180201/</a>
+      <dd><a href="https://www.w3.org/2017/Process-20170301/" rel="prev">https://www.w3.org/2017/Process-20170301/</a>
+      <dt>Feedback:
+      <dd><a href="https://github.com/w3c/w3process/issues/">Github (preferred)</a>
+      <dd><a href="https://lists.w3.org/Archives/Public/public-w3process/">Public mailing list</a>
+      <dd><a href="https://lists.w3.org/Archives/Member/process-issues">Member-only mailing list</a>
+      <dt class="editor">Editors:
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://fantasai.inkedblade.net/contact">Elika J. Etemad / fantasai</a> (<span class="p-org org">Apple</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://florian.rivoal.net/">Florian Rivoal</a> (<span class="p-org org">Invited Expert</span>)
+      <dt class="editor">Former Editors:
+      <dd class="editor p-author h-card vcard"><span class="p-name fn">Natasha Rooney</span> (<span class="p-org org">Invited Expert</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="http://yandex.com">Charles McCathie Nevile</a> (<span class="p-org org">Yandex</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://www.w3.org/">Ian Jacobs</a> (<span class="p-org org">W3C</span>)
+     </dl>
+    </div>
+   </details>
+   <div data-fill-with="warning"></div>
+   <p class="copyright" data-fill-with="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2023 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-software" rel="license" title="W3C Software and Document License">permissive document license</a> rules apply. </p>
+   <hr title="Separator for header">
+  </div>
+  <div class="p-summary" data-fill-with="abstract">
+   <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></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 W3C and processes,
+	responsibilities and functions that enable W3C to accomplish its mission.
+	This document does not describe the internal workings of the Team.</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>.</p>
+  </div>
+  <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content">Status of this document</span></h2>
+  <div data-fill-with="status">
+   <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
+	working within the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a> (which anyone can join).
+	This is the 2 August 2023 Draft Community Group Report for the proposed next version of the W3C Process Document. </p>
+   <p>This document,
+
+which is based on the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a>,
+is offered for W3C Advisory Committee Review of the proposal to adopt this
+as the new operative Process document
+per <a href="https://www.w3.org/Consortium/Process/#GAProcess">Section 11 Process Changes</a>.</p>
+   <p> A <a href="#changes">history of substantial changes</a> from previous versions of the Process Document is provided. </p>
+  </div>
+  <div data-fill-with="at-risk"></div>
+  <nav data-fill-with="table-of-contents" id="toc">
+   <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
+   <ol class="toc" role="directory">
+    <li><a href="#Intro"><span class="secno">1</span> <span class="content"> Introduction</span></a>
+    <li>
+     <a href="#Organization"><span class="secno">2</span> <span class="content"> Members and the Team</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Members"><span class="secno">2.1</span> <span class="content"> Members</span></a>
+       <ol class="toc">
+        <li><a href="#MemberBenefits"><span class="secno">2.1.1</span> <span class="content"> Rights of Members</span></a>
+        <li>
+         <a href="#RelatedAndAssociatedMembers"><span class="secno">2.1.2</span> <span class="content"> Member Associations and Related Members</span></a>
+         <ol class="toc">
+          <li><a href="#MemberAssoc"><span class="secno">2.1.2.1</span> <span class="content"> Membership Associations</span></a>
+          <li><a href="#MemberRelated"><span class="secno">2.1.2.2</span> <span class="content"> Related Members</span></a>
+         </ol>
+       </ol>
+      <li><a href="#Team"><span class="secno">2.2</span> <span class="content"> The W3C Team</span></a>
+     </ol>
+    <li>
+     <a href="#groups"><span class="secno">3</span> <span class="content"> Groups and Participation</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Policies"><span class="secno">3.1</span> <span class="content"> Policies for Participation in W3C Groups</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#ParticipationCriteria"><span class="secno">3.1.1</span> <span class="content"> Individual Participation Criteria</span></a>
+         <ol class="toc">
+          <li><a href="#discipline"><span class="secno">3.1.1.1</span> <span class="content"> Expectations and Discipline</span></a>
+          <li><a href="#coi"><span class="secno">3.1.1.2</span> <span class="content"> Conflict of Interest Policy</span></a>
+          <li><a href="#member-rep"><span class="secno">3.1.1.3</span> <span class="content"> Individuals Representing a Member Organization</span></a>
+         </ol>
+        <li>
+         <a href="#GeneralMeetings"><span class="secno">3.1.2</span> <span class="content"> Meetings</span></a>
+         <ol class="toc">
+          <li><a href="#meeting-schedules"><span class="secno">3.1.2.1</span> <span class="content"> Meeting Scheduling and Announcements</span></a>
+          <li><a href="#meeting-minutes"><span class="secno">3.1.2.2</span> <span class="content"> Meeting Minutes</span></a>
+          <li><a href="#meeting-recording"><span class="secno">3.1.2.3</span> <span class="content"> Meeting Recordings and Transcripts</span></a>
+         </ol>
+        <li><a href="#tooling"><span class="secno">3.1.3</span> <span class="content"> Tooling and Archiving for Discussions and Publications</span></a>
+        <li><a href="#resignation"><span class="secno">3.1.4</span> <span class="content"> Resignation from a Group</span></a>
+       </ol>
+      <li>
+       <a href="#AC"><span class="secno">3.2</span> <span class="content"> The Advisory Committee (AC)</span></a>
+       <ol class="toc">
+        <li><a href="#ac-role"><span class="secno">3.2.1</span> <span class="content"> Role of the Advisory Committee</span></a>
+        <li><a href="#ac-participation"><span class="secno">3.2.2</span> <span class="content"> Participation in the Advisory Committee</span></a>
+        <li><a href="#ACCommunication"><span class="secno">3.2.3</span> <span class="content"> Advisory Committee Mailing Lists</span></a>
+        <li><a href="#ACMeetings"><span class="secno">3.2.4</span> <span class="content"> Advisory Committee Meetings</span></a>
+       </ol>
+      <li>
+       <a href="#elected-groups"><span class="secno">3.3</span> <span class="content"> Elected Groups: The AB and the TAG</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#AB"><span class="secno">3.3.1</span> <span class="content"> Advisory Board (AB)</span></a>
+         <ol class="toc">
+          <li><a href="#ab-role"><span class="secno">3.3.1.1</span> <span class="content"> Role of the Advisory Board</span></a>
+          <li><a href="#ABParticipation"><span class="secno">3.3.1.2</span> <span class="content"> Composition of the Advisory Board</span></a>
+          <li><a href="#ab-comm"><span class="secno">3.3.1.3</span> <span class="content"> Communications of the Advisory Board</span></a>
+          <li><a href="#ab-bod-liaison"><span class="secno">3.3.1.4</span> <span class="content"> Liaisons between the Advisory Board and the Board of Directors</span></a>
+         </ol>
+        <li>
+         <a href="#TAG"><span class="secno">3.3.2</span> <span class="content"> Technical Architecture Group (TAG)</span></a>
+         <ol class="toc">
+          <li><a href="#tag-role"><span class="secno">3.3.2.1</span> <span class="content"> Role of the Technical Architecture Group</span></a>
+          <li><a href="#tag-participation"><span class="secno">3.3.2.2</span> <span class="content"> Composition of the Technical Architecture Group</span></a>
+          <li><a href="#tag-comm"><span class="secno">3.3.2.3</span> <span class="content"> Communications of the Technical Architecture Group</span></a>
+         </ol>
+        <li>
+         <a href="#AB-TAG-participation"><span class="secno">3.3.3</span> <span class="content"> Participation in Elected Groups</span></a>
+         <ol class="toc">
+          <li><a href="#elected-expectations"><span class="secno">3.3.3.1</span> <span class="content"> Expectations for Elected Groups Participants</span></a>
+          <li><a href="#AB-TAG-constraints"><span class="secno">3.3.3.2</span> <span class="content"> Elected Groups Participation Constraints</span></a>
+          <li><a href="#AB-TAG-elections"><span class="secno">3.3.3.3</span> <span class="content"> Advisory Board and Technical Architecture Group Elections</span></a>
+          <li><a href="#TAG-appointments"><span class="secno">3.3.3.4</span> <span class="content"> Technical Architecture Group Appointments</span></a>
+          <li><a href="#random"><span class="secno">3.3.3.5</span> <span class="content"> Verifiable Random Selection Procedure</span></a>
+          <li><a href="#AB-TAG-vacated"><span class="secno">3.3.3.6</span> <span class="content"> Elected Groups Vacated Seats</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#GAGeneral"><span class="secno">3.4</span> <span class="content"> Chartered Groups: Working Groups and Interest Groups</span></a>
+       <ol class="toc">
+        <li><a href="#ReqsAllGroups"><span class="secno">3.4.1</span> <span class="content"> Requirements for All Chartered Groups</span></a>
+        <li><a href="#group-participation"><span class="secno">3.4.2</span> <span class="content"> Participation in Chartered Groups</span></a>
+        <li>
+         <a href="#chartered-group-participants"><span class="secno">3.4.3</span> <span class="content"> Types of Participants in Chartered Groups</span></a>
+         <ol class="toc">
+          <li><a href="#member-rep-wg"><span class="secno">3.4.3.1</span> <span class="content"> Member Representative in a Working Group</span></a>
+          <li><a href="#member-rep-ig"><span class="secno">3.4.3.2</span> <span class="content"> Member Representative in an Interest Group</span></a>
+          <li><a href="#invited-expert-wg"><span class="secno">3.4.3.3</span> <span class="content"> Invited Expert in a Working Group</span></a>
+          <li><a href="#invited-expert-ig"><span class="secno">3.4.3.4</span> <span class="content"> Invited Expert in an Interest Group</span></a>
+          <li><a href="#team-rep-wg"><span class="secno">3.4.3.5</span> <span class="content"> Team Representative in a Working Group</span></a>
+          <li><a href="#team-rep-ig"><span class="secno">3.4.3.6</span> <span class="content"> Team Representative in an Interest Group</span></a>
+         </ol>
+       </ol>
+     </ol>
+    <li>
+     <a href="#group-lifecyle"><span class="secno">4</span> <span class="content"> Lifecycle of Chartered Groups</span></a>
+     <ol class="toc">
+      <li><a href="#WGCharterDevelopment"><span class="secno">4.1</span> <span class="content"> Initiating Charter Development</span></a>
+      <li><a href="#WGCharter"><span class="secno">4.2</span> <span class="content"> Content of a Charter</span></a>
+      <li><a href="#CharterReview"><span class="secno">4.3</span> <span class="content"> Advisory Committee Review of a Charter</span></a>
+      <li><a href="#cfp"><span class="secno">4.4</span> <span class="content"> Call for Participation in a Chartered Group</span></a>
+      <li><a href="#charter-extension"><span class="secno">4.5</span> <span class="content"> Charter Extension</span></a>
+      <li><a href="#GeneralTermination"><span class="secno">4.6</span> <span class="content"> Chartered Group Closure</span></a>
+     </ol>
+    <li>
+     <a href="#decisions"><span class="secno">5</span> <span class="content"> Decisions</span></a>
+     <ol class="toc">
+      <li><a href="#decision-types"><span class="secno">5.1</span> <span class="content"> Types of Decisions</span></a>
+      <li>
+       <a href="#consensus-building"><span class="secno">5.2</span> <span class="content"> Consensus Building</span></a>
+       <ol class="toc">
+        <li><a href="#Consensus"><span class="secno">5.2.1</span> <span class="content"> Consensus</span></a>
+        <li><a href="#managing-dissent"><span class="secno">5.2.2</span> <span class="content"> Managing Dissent</span></a>
+        <li><a href="#Votes"><span class="secno">5.2.3</span> <span class="content"> Deciding by Vote</span></a>
+       </ol>
+      <li><a href="#formal-address"><span class="secno">5.3</span> <span class="content"> Formally Addressing an Issue</span></a>
+      <li><a href="#WGChairReopen"><span class="secno">5.4</span> <span class="content"> Reopening a Decision When Presented With New Information</span></a>
+      <li><a href="#registering-objections"><span class="secno">5.5</span> <span class="content"> Registering Formal Objections</span></a>
+      <li>
+       <a href="#addressing-fo"><span class="secno">5.6</span> <span class="content"> Addressing Formal Objections</span></a>
+       <ol class="toc">
+        <li><a href="#team-fo-mediation"><span class="secno">5.6.1</span> <span class="content"> Investigation and Mediation by the Team</span></a>
+        <li>
+         <a href="#council"><span class="secno">5.6.2</span> <span class="content"> W3C Council</span></a>
+         <ol class="toc">
+          <li><a href="#council-composition"><span class="secno">5.6.2.1</span> <span class="content"> Council Composition</span></a>
+          <li><a href="#council-delegation"><span class="secno">5.6.2.2</span> <span class="content"> Extraordinary Delegation</span></a>
+          <li><a href="#council-participation"><span class="secno">5.6.2.3</span> <span class="content"> Council Participation, Dismissal, and Renunciation</span></a>
+          <li><a href="#council-short-circuit"><span class="secno">5.6.2.4</span> <span class="content"> Unanimous Short Circuit</span></a>
+          <li><a href="#council-chairing"><span class="secno">5.6.2.5</span> <span class="content"> Council Chairing</span></a>
+          <li><a href="#council-deliberations"><span class="secno">5.6.2.6</span> <span class="content"> Council Deliberations</span></a>
+          <li><a href="#council-decision"><span class="secno">5.6.2.7</span> <span class="content"> Council Decision Report</span></a>
+          <li><a href="#council-appeals"><span class="secno">5.6.2.8</span> <span class="content"> Appealing Council Decisions</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#ACReview"><span class="secno">5.7</span> <span class="content"> Advisory Committee Reviews</span></a>
+       <ol class="toc">
+        <li><a href="#ACReviewStart"><span class="secno">5.7.1</span> <span class="content"> Start of a Review Period</span></a>
+        <li><a href="#ACReviewAfter"><span class="secno">5.7.2</span> <span class="content"> After the Review Period</span></a>
+       </ol>
+      <li><a href="#ACVotes"><span class="secno">5.8</span> <span class="content"> Advisory Committee Votes</span></a>
+      <li><a href="#ACAppeal"><span class="secno">5.9</span> <span class="content"> Appeal by Advisory Committee Representatives</span></a>
+     </ol>
+    <li>
+     <a href="#Reports"><span class="secno">6</span> <span class="content"> W3C Technical Reports</span></a>
+     <ol class="toc">
+      <li><a href="#recs-and-notes"><span class="secno">6.1</span> <span class="content"> Types of Technical Reports</span></a>
+      <li>
+       <a href="#general-requirements"><span class="secno">6.2</span> <span class="content"> General Requirements for Technical Reports</span></a>
+       <ol class="toc">
+        <li><a href="#publication"><span class="secno">6.2.1</span> <span class="content"> Publication of Technical Reports</span></a>
+        <li>
+         <a href="#doc-reviews"><span class="secno">6.2.2</span> <span class="content"> Reviews and Review Responsibilities</span></a>
+         <ol class="toc">
+          <li><a href="#wide-review"><span class="secno">6.2.2.1</span> <span class="content"> Wide Review</span></a>
+         </ol>
+        <li><a href="#correction-classes"><span class="secno">6.2.3</span> <span class="content"> Classes of Changes</span></a>
+        <li><a href="#errata"><span class="secno">6.2.4</span> <span class="content"> Errata Management</span></a>
+        <li><a href="#candidate-amendments"><span class="secno">6.2.5</span> <span class="content"> Candidate Amendments</span></a>
+        <li><a href="#contributor-license"><span class="secno">6.2.6</span> <span class="content"> License Grants from Non-Participants</span></a>
+       </ol>
+      <li>
+       <a href="#rec-track"><span class="secno">6.3</span> <span class="content"> The W3C Recommendation Track</span></a>
+       <ol class="toc">
+        <li><a href="#maturity-stages"><span class="secno">6.3.1</span> <span class="content"> Maturity Stages on the Recommendation Track</span></a>
+        <li><a href="#implementation-experience"><span class="secno">6.3.2</span> <span class="content"> Implementation Experience</span></a>
+        <li><a href="#transition-reqs"><span class="secno">6.3.3</span> <span class="content"> Advancement on the Recommendation Track</span></a>
+        <li>
+         <a href="#update-reqs"><span class="secno">6.3.4</span> <span class="content"> Updating Mature Publications on the Recommendation Track</span></a>
+         <ol class="toc">
+          <li><a href="#streamlined-update"><span class="secno">6.3.4.1</span> <span class="content"> Streamlined Publication Approval</span></a>
+         </ol>
+        <li><a href="#first-wd"><span class="secno">6.3.5</span> <span class="content"> Publishing a First Public Working Draft</span></a>
+        <li><a href="#revising-wd"><span class="secno">6.3.6</span> <span class="content"> Revising a Working Draft</span></a>
+        <li><a href="#transition-cr"><span class="secno">6.3.7</span> <span class="content"> Transitioning to Candidate Recommendation</span></a>
+        <li>
+         <a href="#revising-cr"><span class="secno">6.3.8</span> <span class="content"> Revising a Candidate Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#publishing-crrs"><span class="secno">6.3.8.1</span> <span class="content"> Publishing a <span>Candidate Recommendation Snapshot</span></span></a>
+          <li><a href="#publishing-crud"><span class="secno">6.3.8.2</span> <span class="content"> Publishing a <span>Candidate Recommendation Draft</span></span></a>
+         </ol>
+        <li><a href="#transition-pr"><span class="secno">6.3.9</span> <span class="content"> Transitioning to Proposed Recommendation</span></a>
+        <li><a href="#transition-rec"><span class="secno">6.3.10</span> <span class="content"> Transitioning to W3C Recommendation</span></a>
+        <li>
+         <a href="#revising-rec"><span class="secno">6.3.11</span> <span class="content"> Revising a W3C Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#revised-rec-markup"><span class="secno">6.3.11.1</span> <span class="content"> Revising a Recommendation: Markup Changes</span></a>
+          <li><a href="#revised-rec-editorial"><span class="secno">6.3.11.2</span> <span class="content"> Revising a Recommendation: Editorial Changes</span></a>
+          <li><a href="#revised-rec-substantive"><span class="secno">6.3.11.3</span> <span class="content"> Revising a Recommendation: Substantive Changes</span></a>
+          <li><a href="#revised-rec-features"><span class="secno">6.3.11.4</span> <span class="content"> Revising a Recommendation: New Features</span></a>
+          <li><a href="#change-review"><span class="secno">6.3.11.5</span> <span class="content"> Incorporating Candidate Amendments</span></a>
+         </ol>
+        <li><a href="#rec-track-regression"><span class="secno">6.3.12</span> <span class="content"> Regression on the Recommendation Track</span></a>
+        <li>
+         <a href="#tr-end"><span class="secno">6.3.13</span> <span class="content"> Retiring Recommendation Track Documents</span></a>
+         <ol class="toc">
+          <li><a href="#abandon-draft"><span class="secno">6.3.13.1</span> <span class="content"> Abandoning an Unfinished Recommendation</span></a>
+          <li><a href="#rescind-cr"><span class="secno">6.3.13.2</span> <span class="content"> Rescinding a Candidate Recommendation</span></a>
+          <li><a href="#rec-rescind"><span class="secno">6.3.13.3</span> <span class="content"> Abandoning a W3C Recommendation</span></a>
+          <li><a href="#deactivation"><span class="secno">6.3.13.4</span> <span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#note-track"><span class="secno">6.4</span> <span class="content"> The Note Track (Notes and Statements)</span></a>
+       <ol class="toc">
+        <li><a href="#Note"><span class="secno">6.4.1</span> <span class="content"> Group Notes</span></a>
+        <li><a href="#publishing-notes"><span class="secno">6.4.2</span> <span class="content"> Publishing Notes</span></a>
+        <li><a href="#w3c-statement"><span class="secno">6.4.3</span> <span class="content"> Elevating Group Notes to W3C Statement status</span></a>
+        <li><a href="#revising-memo"><span class="secno">6.4.4</span> <span class="content"> Revising W3C Statements</span></a>
+       </ol>
+      <li>
+       <a href="#registries"><span class="secno">6.5</span> <span class="content"> The Registry Track</span></a>
+       <ol class="toc">
+        <li><a href="#reg-def"><span class="secno">6.5.1</span> <span class="content"> Registry Definitions</span></a>
+        <li><a href="#reg-pub"><span class="secno">6.5.2</span> <span class="content"> Publishing Registries</span></a>
+        <li><a href="#reg-table-update"><span class="secno">6.5.3</span> <span class="content"> Updating Registry Tables</span></a>
+        <li><a href="#reg-data-reports"><span class="secno">6.5.4</span> <span class="content"> Registry Data Reports</span></a>
+        <li><a href="#reg-ref-specifications"><span class="secno">6.5.5</span> <span class="content"> Specifications that Reference Registries</span></a>
+       </ol>
+      <li><a href="#switching-tracks"><span class="secno">6.6</span> <span class="content"> Switching Tracks</span></a>
+      <li><a href="#further-reading"><span class="secno">6.7</span> <span class="content"> Further reading</span></a>
+     </ol>
+    <li>
+     <a href="#dissemination"><span class="secno">7</span> <span class="content"> <span></span> Dissemination Policies</span></a>
+     <ol class="toc">
+      <li><a href="#pub-com"><span class="secno">7.1</span> <span class="content"> Public Communication</span></a>
+      <li><a href="#confidentiality-levels"><span class="secno">7.2</span> <span class="content"> Confidentiality Levels</span></a>
+      <li><a href="#confidentiality-change"><span class="secno">7.3</span> <span class="content"> Changing Confidentiality Level</span></a>
+     </ol>
+    <li><a href="#GAEvents"><span class="secno">8</span> <span class="content"> Workshops and Symposia</span></a>
+    <li><a href="#Liaisons"><span class="secno">9</span> <span class="content"> Liaisons</span></a>
+    <li>
+     <a href="#Submission"><span class="secno">10</span> <span class="content"> Member Submission Process</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#SubmissionRights"><span class="secno">10.1</span> <span class="content"> Submitter Rights and Obligations</span></a>
+       <ol class="toc">
+        <li><a href="#SubmissionScope"><span class="secno">10.1.1</span> <span class="content"> Scope of Member Submissions</span></a>
+        <li><a href="#SubmissionReqs"><span class="secno">10.1.2</span> <span class="content"> Information Required in a Submission Request</span></a>
+       </ol>
+      <li><a href="#TeamSubmissionRights"><span class="secno">10.2</span> <span class="content"> Team Rights and Obligations</span></a>
+      <li><a href="#SubmissionYes"><span class="secno">10.3</span> <span class="content"> Acknowledgment of a Submission Request</span></a>
+      <li><a href="#SubmissionNo"><span class="secno">10.4</span> <span class="content"> Rejection of a Submission Request, and Submission Appeals</span></a>
+     </ol>
+    <li><a href="#GAProcess"><span class="secno">11</span> <span class="content"> Process Evolution</span></a>
+    <li><a href="#acks"><span class="secno">12</span> <span class="content"> Acknowledgments</span></a>
+    <li>
+     <a href="#changes"><span class="secno">13</span> <span class="content"> Changes</span></a>
+     <ol class="toc">
+      <li><a href="#changes-2023-1"><span class="secno"></span> <span class="content"> Changes since the <span>12 June 2023 Process</span></span></a>
+      <li><a href="#changes-previous"><span class="secno"></span> <span class="content"> Changes since earlier versions</span></a>
+     </ol>
+    <li>
+     <a href="#w3c-conformance"><span class="secno"></span> <span class="content">Conformance</span></a>
+     <ol class="toc">
+      <li><a href="#w3c-conventions"><span class="secno"></span> <span class="content">Document conventions</span></a>
+     </ol>
+    <li>
+     <a href="#index"><span class="secno"></span> <span class="content">Index</span></a>
+     <ol class="toc">
+      <li><a href="#index-defined-here"><span class="secno"></span> <span class="content">Terms defined by this specification</span></a>
+      <li><a href="#index-defined-elsewhere"><span class="secno"></span> <span class="content">Terms defined by reference</span></a>
+     </ol>
+    <li>
+     <a href="#references"><span class="secno"></span> <span class="content">References</span></a>
+     <ol class="toc">
+      <li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
+      <li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
+     </ol>
+   </ol>
+  </nav>
+  <main>
+   <h2 class="no-num no-toc no-ref heading settled" id="pp"><span class="content"> Relation of Process Document to Patent Policy and Other Policies</span></h2>
+   <p>W3C Members' attention is called to the fact
+	that provisions of the Process Document are binding on Members
+	per the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	The <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and other policies
+	incorporated by normative reference as a part of the Process Document
+	are equally binding.</p>
+   <p>The Patent Policy and CEPC 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 CEPC have been designed to allow each to evolve independently.</p>
+   <p>In the Process Document, the term “participant” refers to an individual, not an organization.</p>
+   <h2 class="no-num no-toc no-ref heading settled" id="terms"><span class="content"> Conformance and specialized terms</span></h2>
+   <p>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 data-dfn-type="dfn" data-noexport id="not-required"><em class="rfc2119">not required</em><a class="self-link" href="#not-required"></a></dfn> is equivalent to the term <em class="rfc2119">may</em> as defined in RFC2119 <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a>.</p>
+   <p>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.</p>
+   <nav data-fill-with="table-of-contents"></nav>
+   <main>
+    <h2 class="heading settled" data-level="1" id="Intro"><span class="secno">1. </span><span class="content"> Introduction</span><a class="self-link" href="#Intro"></a></h2>
+    <p>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>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>. <a href="#group-participation">Participants</a> in W3C include <a href="#member-rep">representatives of its Members</a> and the <a data-link-type="dfn" href="#team" id="ref-for-team">Team</a>,
+	as well as <a href="#invited-expert-wg">Invited Experts</a> who can bring additional expertise or represent additional stakeholders. <a data-link-type="dfn" href="#team" id="ref-for-team①">Team</a> representatives both contribute to the technical work
+	and help ensure each group’s proper integration with the rest of W3C.</p>
+    <p>W3C’s technical standards, called <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C">W3C Recommendations</a>,
+	are developed by its <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG">Working Groups</a>;
+	W3C also has other types of publications,
+	all described in <a href="#Reports">§ 6 W3C Technical Reports</a>.
+	W3C has various types of groups;
+	this document describes the formation and policies
+	of its chartered <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG">Interest Groups</a>,
+	see <a href="#Policies">§ 3.1 Policies for Participation in W3C Groups</a> and <a href="#GAGeneral">§ 3.4 Chartered Groups: Working Groups and Interest Groups</a>.
+	W3C also operates Community and Business Groups,
+	which are separately described in <a href="https://www.w3.org/community/about/agreements/">their own process document</a> <a data-link-type="biblio" href="#biblio-bg-cg" title="Community and Business Group Process">[BG-CG]</a>.</p>
+    <p>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.</p>
+    <p>Here is a general overview of how W3C initiates standardization of a Web technology:</p>
+    <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 <a data-link-type="dfn" href="#team" id="ref-for-team②">Team</a> 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>
+    <p>Further sections of this Process Document deal with topics including
+	liaisons (<a href="#Liaisons">§ 9 Liaisons</a>),
+	confidentiality (<a href="#dissemination">§ 7 Dissemination Policies</a>),
+	and formal decisions and appeals (<a href="#decisions">§ 5 Decisions</a>).</p>
+    <h2 class="heading settled" data-level="2" id="Organization"><span class="secno">2. </span><span class="content"> Members and the Team</span><a class="self-link" href="#Organization"></a></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 class="heading settled" data-level="2.1" id="Members"><span class="secno">2.1. </span><span class="content"> Members</span><a class="self-link" href="#Members"></a></h3>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Member|Member" data-noexport id="w3c-member">W3C Members</dfn> are
+	organizations subscribed according to the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	They are represented in W3C processes as follows:</p>
+    <ol>
+     <li> One representative per Member organization participates
+			in the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee">Advisory Committee</a> 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/Consortium/join">How to Join W3C</a>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>;
+	(refer to the public list of <a href="https://www.w3.org/Consortium/Member/List">current W3C Members</a> <a data-link-type="biblio" href="#biblio-member-list" title="The list of current W3C Members">[MEMBER-LIST]</a>).
+	The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure
+	that Member participation agreements remain <a href="#Team-only" id="ref-for-Team-only">Team-only</a> and that no Member receives preferential treatment within W3C. </p>
+    <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. </p>
+    <h4 class="heading settled" data-level="2.1.1" id="MemberBenefits"><span class="secno">2.1.1. </span><span class="content"> Rights of Members</span><a class="self-link" href="#MemberBenefits"></a></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> Access to <a href="#Member-only" id="ref-for-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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>. 
+    </ul>
+    <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> In <a href="#GAEvents">Workshops and Symposia</a>; 
+     <li> On the Team, as <a href="#fellows" id="ref-for-fellows">W3C Fellows</a>. 
+    </ul>
+    <p>The rights and benefits of W3C membership <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> are contingent upon conformance to the processes described in this document.
+	Disciplinary action for anyone participating in W3C activities is described in <a href="#discipline">§ 3.1.1.1 Expectations and Discipline</a>.</p>
+    <p>Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member website</a> <a data-link-type="biblio" href="#biblio-member-hp" title="Member website (Member-only access)">[MEMBER-HP]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.2" id="RelatedAndAssociatedMembers"><span class="secno">2.1.2. </span><span class="content"> Member Associations and Related Members</span><span id="RelatedAndConsortiumMembers"></span><a class="self-link" href="#RelatedAndAssociatedMembers"></a></h4>
+    <h5 class="heading settled" data-level="2.1.2.1" id="MemberAssoc"><span class="secno">2.1.2.1. </span><span class="content"> Membership Associations</span><span id="fdn-member-consortium"></span><span id="MemberConsortia"></span><a class="self-link" href="#MemberAssoc"></a></h5>
+    <p>A “<dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Member Association | Member Associations" data-noexport id="member-association">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 <a data-link-type="dfn" href="#member-association" id="ref-for-member-association">Member Association</a> merely because it has shareholders or stockholders.
+	If it is not clear whether a prospective Member qualifies as a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association①">Member Association</a>,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo">CEO</a> may reasonably make the determination.
+	For a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association②">Member Association</a>, the rights and privileges of W3C Membership
+	described in the W3C Process Document extend to the <a data-link-type="dfn" href="#member-association" id="ref-for-member-association③">Member Association</a>'s paid staff
+	and Advisory Committee representative.</p>
+    <p><a data-link-type="dfn" href="#member-association" id="ref-for-member-association④">Member Associations</a> <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>
+    <p>For <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑤">Member Associations</a> 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.</p>
+    <p>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.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="2.1.2.2" id="MemberRelated"><span class="secno">2.1.2.2. </span><span class="content"> Related Members</span><a class="self-link" href="#MemberRelated"></a></h5>
+    <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 <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Related Member" id="related-member">related</dfn> if:</p>
+    <ol>
+     <li> Either Member is a <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary">subsidiary</a> of the other, or 
+     <li> Both Members are <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary①">subsidiaries</a> of a common entity, or 
+     <li> The Members have an employment contract or consulting contract that affects W3C participation. 
+    </ol>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="subsidiary">subsidiary</dfn> is an organization of which effective control and/or majority ownership rests with another,
+	single organization.</p>
+    <p><a data-link-type="dfn" href="#related-member" id="ref-for-related-member">Related Members</a> <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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h3 class="heading settled" data-level="2.2" id="Team"><span class="secno">2.2. </span><span class="content"> The W3C Team</span><span id="def-Director"></span><a class="self-link" href="#Team"></a></h3>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team | W3C Team" id="team">Team</dfn> consists of <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="ceo">CEO</dfn>,
+	W3C paid staff,
+	unpaid interns,
+	and W3C Fellows. <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fellows">W3C Fellows</dfn> are Member employees working as part of the Team;
+	see the <a href="https://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a> <a data-link-type="biblio" href="#biblio-fellows" title="W3C Fellows Program">[FELLOWS]</a>.
+	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.</p>
+    <p>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. <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision">Team Decisions</a> derive from the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo①">CEO</a>'s authority,
+	even when they are carried out by other members of the <a data-link-type="dfn" href="#team" id="ref-for-team③">Team</a>.</p>
+    <p>Oversight over the <a data-link-type="dfn" href="#team" id="ref-for-team④">Team</a>,
+	budgeting,
+	and other business decisions,
+	is provided by the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="BoD | Board | Board of Directors | W3C Board of Directors" id="bod">W3C Board of Directors</dfn>,
+	rather than managed directly by the Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf">W3C Bylaws</a> for more details
+	on the <a data-link-type="dfn" href="#bod" id="ref-for-bod">Board</a> and overall governance of W3C.</p>
+    <h2 class="heading settled" data-level="3" id="groups"><span class="secno">3. </span><span class="content"> Groups and Participation</span><a class="self-link" href="#groups"></a></h2>
+    <p>For the purposes of this Process, a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="group" data-noexport id="w3c-group">W3C Group</dfn> is one of W3C’s <a href="#wgparticipant" id="ref-for-wgparticipant">Working Groups</a>, <a href="#igparticipant" id="ref-for-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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="participant">participant</dfn> is a member of such a group.</p>
+    <h3 class="heading settled" data-level="3.1" id="Policies"><span class="secno">3.1. </span><span class="content"> Policies for Participation in W3C Groups</span><a class="self-link" href="#Policies"></a></h3>
+    <h4 class="heading settled" data-level="3.1.1" id="ParticipationCriteria"><span class="secno">3.1.1. </span><span class="content"> Individual Participation Criteria</span><a class="self-link" href="#ParticipationCriteria"></a></h4>
+    <h5 class="heading settled" data-level="3.1.1.1" id="discipline"><span class="secno">3.1.1.1. </span><span class="content"> Expectations and Discipline</span><a class="self-link" href="#discipline"></a></h5>
+    <p>There are three qualities an individual is expected to demonstrate in order to participate in W3C:</p>
+    <ol>
+     <li> Technical competence in one’s role; 
+     <li> The ability to act fairly; 
+     <li> Social competence in one’s role. 
+    </ol>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative">Advisory Committee representatives</a> who nominate individuals from their organization for participation in W3C activities
+	are responsible for assessing and attesting to the qualities of those nominees.</p>
+    <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/Consortium/cepc/">W3C Code of Ethics and Professional Conduct</a> <a data-link-type="biblio" href="#biblio-cepc" title="W3C Code of Ethics and Professional Conduct">[CEPC]</a> and the participation requirements described in
+	“Disclosure”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. </p>
+    <p>The <a data-link-type="dfn" href="#ceo" id="ref-for-ceo②">CEO</a> <em class="rfc2119">may</em> take disciplinary action,
+	including suspending or removing for cause
+	a participant in any group (including the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group">TAG</a>)
+	if serious and/or repeated violations,
+	such as failure to meet the requirements on individual behavior of
+	(a) this process
+	and in particular the CEPC, or
+	(b) the membership agreement, or
+	(c) applicable laws,
+	occur.
+	Refer to the <a href="https://www.w3.org/Guide/process/banning.html">Guidelines to suspend or remove participants from groups</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.2" id="coi"><span class="secno">3.1.1.2. </span><span class="content"> Conflict of Interest Policy</span><a class="self-link" href="#coi"></a></h5>
+    <p>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.</p>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑤">Team</a> <em class="rfc2119">may</em> appoint a new group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs">Chair</a> 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).</p>
+    <p>The following are some scenarios where disclosure is appropriate:</p>
+    <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>
+    <p>Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the <a data-link-type="dfn" href="#team" id="ref-for-team⑥">Team</a>.</p>
+    <p><a data-link-type="dfn" href="#team" id="ref-for-team⑦">Team</a> members are subject to the <a href="https://www.w3.org/2000/09/06-conflictpolicy">W3C Team conflict of interest policy</a> <a data-link-type="biblio" href="#biblio-conflict-policy" title="Conflict of Interest Policy for W3C Team Members Engaged in Outside Professional Activities">[CONFLICT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.3" id="member-rep"><span class="secno">3.1.1.3. </span><span class="content"> Individuals Representing a Member Organization</span><a class="self-link" href="#member-rep"></a></h5>
+    <p>Generally, individuals representing a Member in an official capacity within W3C
+	are employees of the Member organization.
+	However, an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①">Advisory Committee representative</a> <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.</p>
+    <p>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 <a data-link-type="dfn" href="#ceo" id="ref-for-ceo③">CEO</a> <em class="rfc2119">may</em> decline
+	to allow an individual designated by an Advisory Committee representative to participate in a group.</p>
+    <p>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>).</p>
+    <h4 class="heading settled" data-level="3.1.2" id="GeneralMeetings"><span class="secno">3.1.2. </span><span class="content"> Meetings</span><a class="self-link" href="#GeneralMeetings"></a></h4>
+    <p>The requirements in this section apply to the official meetings of any <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group">W3C group</a>.</p>
+    <p>W3C distinguishes two types of meetings:</p>
+    <ol>
+     <li> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 class="dfn-paneled" data-dfn-type="dfn" data-noexport 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>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①">Chair</a> <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 <a data-link-type="dfn" href="#participant" id="ref-for-participant">participant</a>.
+	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.</p>
+    <h5 class="heading settled" data-level="3.1.2.1" id="meeting-schedules"><span class="secno">3.1.2.1. </span><span class="content"> Meeting Scheduling and Announcements</span><a class="self-link" href="#meeting-schedules"></a></h5>
+    <p>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.</p>
+    <p>The following table lists <em class="rfc2119">recommendations</em> for organizing a meeting:</p>
+    <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"><a data-link-type="dfn" href="#minutes" id="ref-for-minutes">Minutes</a> available (after) 
+       <td><span class="time-interval">two weeks</span> 
+       <td><span class="time-interval">48 hours</span> 
+    </table>
+    <p><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.</p>
+    <h5 class="heading settled" data-level="3.1.2.2" id="meeting-minutes"><span class="secno">3.1.2.2. </span><span class="content"> Meeting Minutes</span><a class="self-link" href="#meeting-minutes"></a></h5>
+    <p>Groups <em class="rfc2119">should</em> take and retain <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minutes">minutes</dfn> of their meetings,
+	and <em class="rfc2119">must</em> record
+	any official <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision">group decisions</a> made during the meeting discussions.
+	Details of the discussion leading to such decisions are not required,
+	provided that the rationale for the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision①">group decision</a> is nonetheless clear.</p>
+    <h5 class="heading settled" data-level="3.1.2.3" id="meeting-recording"><span class="secno">3.1.2.3. </span><span class="content"> Meeting Recordings and Transcripts</span><a class="self-link" href="#meeting-recording"></a></h5>
+    <p>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.</p>
+    <h4 class="heading settled" data-level="3.1.3" id="tooling"><span class="secno">3.1.3. </span><span class="content"> Tooling and Archiving for Discussions and Publications</span><a class="self-link" href="#tooling"></a></h4>
+    <p>For <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group①">W3C Groups</a> 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:</p>
+    <ul>
+     <li id="report-stability"><a class="self-link" href="#report-stability"></a> 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"><a class="self-link" href="#report-accessibility"></a> 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">
+      <a class="self-link" href="#discussion-archiving"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> The lack, or loss, of such archives does not by itself
+			invalidate an otherwise-valid decision.</p>
+     <li id="tool-accessibility">
+      <a class="self-link" href="#tool-accessibility"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> If a new participant joins who cannot use the tool,
+			this can require the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②">Working Group</a> to change its tooling
+			or operate some workaround.</p>
+     <li id="where-is-your-stuff"><a class="self-link" href="#where-is-your-stuff"></a> 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>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧">Team</a> is responsible for ensuring adherence to these rules
+	and for bringing any group not in compliance into compliance.</p>
+    <h4 class="heading settled" data-level="3.1.4" id="resignation"><span class="secno">3.1.4. </span><span class="content"> Resignation from a Group</span><a class="self-link" href="#resignation"></a></h4>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑨">Team</a>,
+	the Member and their representatives
+	or the Invited Expert
+	will be deemed to have resigned from the relevant group.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪">Team</a> <em class="rfc2119">must</em> record the notification.
+	See “Exclusion and Resignation from the Working Group” in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for information about obligations remaining after resignation from certain groups.</p>
+    <h3 class="heading settled" data-level="3.2" id="AC"><span class="secno">3.2. </span><span class="content"> The Advisory Committee (AC)</span><a class="self-link" href="#AC"></a></h3>
+    <h4 class="heading settled" data-level="3.2.1" id="ac-role"><span class="secno">3.2.1. </span><span class="content"> Role of the Advisory Committee</span><a class="self-link" href="#ac-role"></a></h4>
+    <p id="ReviewAppeal"> The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee|AC" id="advisory-committee">Advisory Committee</dfn> represents
+	the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member">Members</a> of W3C at large.
+	It is responsible for: </p>
+    <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="#RecsPR" id="ref-for-RecsPR">Proposed Recommendations</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>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> of a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision">W3C decision</a> or <a data-link-type="dfn" href="#team" id="ref-for-team①①">Team</a>'s decision.</p>
+    <p>See also the additional roles of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③">Advisory Committee representatives</a> described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h4 class="heading settled" data-level="3.2.2" id="ac-participation"><span class="secno">3.2.2. </span><span class="content"> Participation in the Advisory Committee</span><a class="self-link" href="#ac-participation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①">Advisory Committee</a> is composed of one <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee representative| AC representative" id="advisory-committee-representative">representative</dfn> from each Member organization
+	(refer to the <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①②">Member-only</a> list
+	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. <a data-link-type="biblio" href="#biblio-current-ac" title="Current Advisory Committee representatives (Member-only access)">[CURRENT-AC]</a>)</p>
+    <p>When an organization joins W3C
+	(see “<a href="https://www.w3.org/Consortium/join">How to Join W3C</a>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>),
+	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement.
+	The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a> 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 <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative④">Advisory Committee representative</a>,
+	and more. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑤">Advisory Committee representatives</a> <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.</p>
+    <p>The AC representative may delegate any of their rights and responsibilities
+	to an <dfn data-dfn-type="dfn" data-export data-lt="alternate AC representative | alternate Advisory Committee representative | alt AC rep" id="alternate-ac-representative">alternate<a class="self-link" href="#alternate-ac-representative"></a></dfn> (except the ability to designate an alternate).</p>
+    <h4 class="heading settled" data-level="3.2.3" id="ACCommunication"><span class="secno">3.2.3. </span><span class="content"> Advisory Committee Mailing Lists</span><a class="self-link" href="#ACCommunication"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②">Team</a> <em class="rfc2119">must</em> provide two mailing lists for use by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②">Advisory Committee</a>:</p>
+    <ol>
+     <li> One for official announcements (e.g., those required by this document) from the <a data-link-type="dfn" href="#team" id="ref-for-team①③">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③">Advisory Committee</a>.
+			This list is read-only for Advisory Committee representatives. 
+     <li> One for discussion among <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑥">Advisory Committee representatives</a>.
+			Though this list is primarily for Advisory Committee representatives,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①④">Team</a> <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>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑦">Advisory Committee representative</a> <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.</p>
+    <h4 class="heading settled" data-level="3.2.4" id="ACMeetings"><span class="secno">3.2.4. </span><span class="content"> Advisory Committee Meetings</span><a class="self-link" href="#ACMeetings"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑤">Team</a> organizes a <a href="#ftf-meeting" id="ref-for-ftf-meeting">face-to-face meeting</a> for the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④">Advisory Committee</a> <span class="time-interval">twice a year</span>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⑥">Team</a> 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:</p>
+    <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>
+    </dl>
+    <p>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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑦">Team</a> <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.</p>
+    <p>More information about <a href="https://www.w3.org/Member/Meeting/">Advisory Committee meetings</a> <a data-link-type="biblio" href="#biblio-ac-meeting" title="Advisory Committee meetings (Member-only access)">[AC-MEETING]</a> is available at the Member website.</p>
+    <h3 class="heading settled" data-level="3.3" id="elected-groups"><span class="secno">3.3. </span><span class="content"> Elected Groups: The AB and the TAG</span><a class="self-link" href="#elected-groups"></a></h3>
+    <p>The W3C Process defines two types of <dfn data-dfn-type="dfn" data-export id="elected-group">elected groups<a class="self-link" href="#elected-group"></a></dfn>:
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①">Advisory Board</a> (AB) and
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①">Technical Architecture Group</a> (TAG),
+	both elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑤">Advisory Committee</a>.</p>
+    <h4 class="heading settled" data-level="3.3.1" id="AB"><span class="secno">3.3.1. </span><span class="content"> Advisory Board (AB)</span><a class="self-link" href="#AB"></a></h4>
+    <h5 class="heading settled" data-level="3.3.1.1" id="ab-role"><span class="secno">3.3.1.1. </span><span class="content"> Role of the Advisory Board</span><a class="self-link" href="#ab-role"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Board|AB" id="advisory-board">Advisory Board</dfn> 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>.
+	As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council">W3C Council</a>,
+	members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②">Advisory Board</a> hear and adjudicate on <a href="#SubmissionNo">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③">Advisory Board</a> is distinct from the <a data-link-type="dfn" href="#bod" id="ref-for-bod①">Board of Directors</a> and has no decision-making authority within W3C;
+	its role is strictly advisory.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> While the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board④">AB</a> as such does not have decision-making authority,
+	its members do when sitting as part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①">W3C Council</a>.</p>
+    <p>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> <a data-link-type="biblio" href="#biblio-ab-hp" title="The Advisory Board home page">[AB-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.1.2" id="ABParticipation"><span class="secno">3.3.1.2. </span><span class="content"> Composition of the Advisory Board</span><a class="self-link" href="#ABParticipation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑤">Advisory Board</a> 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 <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑥">AB</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⑧">Team</a> appoints the Chair,
+	who <em class="rfc2119">should</em> choose a co-chair among the elected participants.
+	The Chair(s) are subject to ratification by secret ballot
+	by two thirds of the AB upon appointment.
+	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.</p>
+    <p>The team also appoints a <a href="https://www.w3.org/Guide/teamcontact/role.html">Team Contact</a>,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.
+	The CEO and Team Contact have a standing invitation
+	to all regular Advisory Board sessions.</p>
+    <p>The nine to eleven <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑦">Advisory Board</a> participants are elected by the W3C <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑥">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.</p>
+    <p>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.</p>
+    <p></p>
+    <h5 class="heading settled" data-level="3.3.1.3" id="ab-comm"><span class="secno">3.3.1.3. </span><span class="content"> Communications of the Advisory Board</span><a class="self-link" href="#ab-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑨">Team</a> <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.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑧">Advisory Board</a> <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>.</p>
+    <h5 class="heading settled" data-level="3.3.1.4" id="ab-bod-liaison"><span class="secno">3.3.1.4. </span><span class="content"> Liaisons between the Advisory Board and the Board of Directors</span><a class="self-link" href="#ab-bod-liaison"></a></h5>
+    <p>To ensure good communication between the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑨">AB</a> and the <a data-link-type="dfn" href="#bod" id="ref-for-bod②">Board of Directors</a> and facilitate operational and management consistency,
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⓪">AB</a> <em class="rfc2119">may</em> appoint up to two of its participants as liaisons to the <a data-link-type="dfn" href="#bod" id="ref-for-bod③">Board</a>.
+	Such appointees are expected to attend and participate in <a data-link-type="dfn" href="#bod" id="ref-for-bod④">Board</a> meetings
+	and access <a data-link-type="dfn" href="#bod" id="ref-for-bod⑤">Board</a> materials
+	as Non-voting Observers. <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a> They do not form part of the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑥">Board</a>'s decision-making body,
+	and may be excluded from such participation
+	in accordance with applicable Board procedures.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①①">Advisory Board</a> <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.</p>
+    <h4 class="heading settled" data-level="3.3.2" id="TAG"><span class="secno">3.3.2. </span><span class="content"> Technical Architecture Group (TAG)</span><a class="self-link" href="#TAG"></a></h4>
+    <h5 class="heading settled" data-level="3.3.2.1" id="tag-role"><span class="secno">3.3.2.1. </span><span class="content"> Role of the Technical Architecture Group</span><a class="self-link" href="#tag-role"></a></h5>
+    <p>The mission of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Technical Architecture Group|TAG" id="technical-architecture-group">TAG</dfn> is stewardship of the Web architecture.
+	There are three aspects to this mission:</p>
+    <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> to help coordinate cross-technology architecture developments inside and outside W3C. 
+    </ol>
+    <p>As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②">W3C Council</a>,
+	the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②">TAG</a> hear and adjudicate on <a href="#SubmissionNo">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③">TAG</a>'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/2004/10/27-tag-charter.html">TAG charter</a> <a data-link-type="biblio" href="#biblio-tag-charter" title="Technical Architecture Group (TAG) Charter">[TAG-CHARTER]</a> for more information about the background and scope of the TAG,
+	and the expected qualifications of TAG participants.</p>
+    <p>When the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④">TAG</a> votes to resolve an issue,
+	each TAG participant
+	(whether appointed, elected, or the Chair)
+	has one vote;
+	see also the section on <a href="https://www.w3.org/2004/10/27-tag-charter.html#Voting">voting in the TAG charter</a> <a data-link-type="biblio" href="#biblio-tag-charter" title="Technical Architecture Group (TAG) Charter">[TAG-CHARTER]</a> and the general section on <a href="#Votes">votes</a> in this Process Document.</p>
+    <p>Details about the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑤">TAG</a> (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings)
+	are available at the <a href="https://www.w3.org/2001/tag/">TAG home page</a> <a data-link-type="biblio" href="#biblio-tag-hp" title="The TAG home page">[TAG-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.2.2" id="tag-participation"><span class="secno">3.3.2.2. </span><span class="content"> Composition of the Technical Architecture Group</span><a class="self-link" href="#tag-participation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑥">TAG</a> consists of:</p>
+    <ul>
+     <li> Tim Berners-Lee, who is a life member; 
+     <li> Three participants <a href="#TAG-appointments">appointed by the Team</a>; 
+     <li> Eight participants elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑦">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>. 
+    </ul>
+    <p>Participants in the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑦">TAG</a> choose by consensus their Chair or co-Chairs;
+	in the absence of consensus, the <a data-link-type="dfn" href="#team" id="ref-for-team②⓪">Team</a> appoints the Chair or co-Chairs of the TAG.
+	The Chair or co-Chairs <em class="rfc2119">must</em> be selected from the participants of the TAG.
+	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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②①">Team</a> also appoints a <a href="https://www.w3.org/Guide/teamcontact/role.html">Team Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> for the TAG,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.</p>
+    <p>The terms of TAG participants last for <span class="time-interval">two years</span>.
+	Terms are staggered so that four elected terms
+	and either one or two appointed terms expire each year.
+	If an individual is appointed or elected to fill an incomplete term,
+	that individual’s term ends at the normal expiration date of that term.
+	Regular TAG terms begin on 1 February and end on 31 January.</p>
+    <h5 class="heading settled" data-level="3.3.2.3" id="tag-comm"><span class="secno">3.3.2.3. </span><span class="content"> Communications of the Technical Architecture Group</span><a class="self-link" href="#tag-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②②">Team</a> <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
+    <ul>
+     <li> a public discussion (not just input) list for issues of Web architecture.
+			The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑧">TAG</a> will conduct its public business on this list. 
+     <li> a <a href="#Member-only" id="ref-for-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. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑨">TAG</a> <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" id="ref-for-Member-only①④">Member-only</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⓪">TAG</a> <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 <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①①">TAG</a> <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
+    <h4 class="heading settled" data-level="3.3.3" id="AB-TAG-participation"><span class="secno">3.3.3. </span><span class="content"> Participation in Elected Groups</span><a class="self-link" href="#AB-TAG-participation"></a></h4>
+    <h5 class="heading settled" data-level="3.3.3.1" id="elected-expectations"><span class="secno">3.3.3.1. </span><span class="content"> Expectations for Elected Groups Participants</span><a class="self-link" href="#elected-expectations"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①②">Advisory Board</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①②">TAG</a> participants have a special role within W3C:
+	they are elected by the Membership and appointed by the <a data-link-type="dfn" href="#team" id="ref-for-team②③">Team</a> with the expectation that they will use their best judgment
+	to find the best solutions for the Web,
+	not just for any particular network,
+	technology,
+	vendor,
+	or user.
+	Advisory Board and TAG participants are expected to participate regularly and fully.
+	Advisory Board and TAG participants <em class="rfc2119">should</em> attend <a href="#ACMeetings">Advisory Committee meetings</a>.</p>
+    <p>Individuals elected or appointed to the Advisory Board or TAG act in their personal capacity,
+	to serve the needs of the W3C membership as a whole,
+	and the Web community.
+	Whether they are Member representatives or Invited Experts,
+	their activities in those roles are separate and distinct from their activities on the Advisory Board or TAG.</p>
+    <p>An individual participates on the Advisory Board or TAG
+	from the moment the individual’s term begins until the seat is <a href="#AB-TAG-vacated">vacated</a> (e.g. because the term ends).
+	Although Advisory Board and TAG participants do not advocate for the commercial interests of their employers,
+	their participation does carry the responsibilities associated with Member representation,
+	Invited Expert status,
+	or Team representation
+	(as described in the section on the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>).</p>
+    <p>Participation in the TAG or AB is afforded to the specific individuals elected or appointed to those positions,
+	and a participant’s seat <em class="rfc2119">must not</em> be delegated to any other person.</p>
+    <h5 class="heading settled" data-level="3.3.3.2" id="AB-TAG-constraints"><span class="secno">3.3.3.2. </span><span class="content"> Elected Groups Participation Constraints</span><a class="self-link" href="#AB-TAG-constraints"></a></h5>
+    <p>Given the few seats available on the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①③">Advisory Board</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①③">TAG</a>,
+	and in order to ensure that the diversity of W3C Members is represented:</p>
+    <ul>
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the TAG
+			except when this is caused by a change of affiliation of an existing participant.
+			At the completion of the next regularly scheduled election for the TAG,
+			the organization <em class="rfc2119">must</em> have returned to having at most one seat. 
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation①">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the AB.
+			If, for whatever reason, these constraints are not satisfied
+			(e.g., because an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①④">AB</a> participant changes jobs),
+			one participant <em class="rfc2119">must</em> cease <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑤">AB</a> participation
+			until the situation has been resolved.
+			If after <span class="time-interval">30 days</span> the situation has not been resolved,
+			the Chair will apply
+			the <a href="#random">verifiable random selection procedure</a> described below
+			to choose one person for continued participation and declare the other seat(s) vacant. 
+     <li> An individual <em class="rfc2119">must not</em> participate on both the TAG and the AB. 
+    </ul>
+    <h5 class="heading settled" data-level="3.3.3.3" id="AB-TAG-elections"><span class="secno">3.3.3.3. </span><span class="content"> Advisory Board and Technical Architecture Group Elections</span><a class="self-link" href="#AB-TAG-elections"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑥">Advisory Board</a> and a portion of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①④">Technical Architecture Group</a> are elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑧">Advisory Committee</a>,
+	using a Single Transferable Vote system.
+	An election begins when the Team sends a Call for Nominations to the Advisory Committee.
+	Any Call for Nominations specifies the minimum and maximum number of available seats,
+	the deadline for nominations,
+	details about the specific vote tabulation system selected by the Team for the election,
+	and operational information such as how to nominate a candidate.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②④">Team</a> <em class="rfc2119">may</em> modify the tabulation system after the Call for Nominations
+	but <em class="rfc2119">must</em> stabilize it no later than the Call for Votes.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②⑤">Team</a> announces appointments
+	after the results of the election are known,
+	and before the start of the term,
+	as described in <a href="#TAG-appointments">§ 3.3.3.4 Technical Architecture Group Appointments</a>.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑤">TAG</a>,
+	the minimum and maximum number of available seats are the same:
+	the 4 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑦">AB</a>,
+	the minimum and maximum number of available seats differ:
+	The maximum number is the 5 or 6 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats;
+	the minimum number is such that when added to the occupied seats from the prior year,
+	the minimum size of the AB (9) is reached.</p>
+    <p>Each Member (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member①">related Members</a>) <em class="rfc2119">may</em> nominate one individual.
+	A nomination <em class="rfc2119">must</em> be made with the consent of the nominee.
+	In order for an individual to be nominated as a Member representative,
+	the individual <em class="rfc2119">must</em> qualify for <a href="#member-rep">Member representation</a> and the Member’s <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑧">Advisory Committee representative</a> <em class="rfc2119">must</em> include in the nomination
+	the (same) <a href="#member-rep-info">information required for a Member representative in a Working Group</a>.
+	In order for an individual to be nominated as an Invited Expert,
+	the individual <em class="rfc2119">must</em> provide
+	the (same) <a href="#inv-expert-info" id="ref-for-inv-expert-info">information required for an Invited Expert in a Working Group</a> and the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑨">Advisory Committee representative</a> <em class="rfc2119">must</em> include that information in the nomination.
+	In order for an individual to be nominated as a <a data-link-type="dfn" href="#team" id="ref-for-team②⑥">Team</a> representative,
+	the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⓪">Advisory Committee representative</a> <em class="rfc2119">must</em> first secure approval from <a data-link-type="dfn" href="#team" id="ref-for-team②⑦">Team</a> management.
+	A nominee is <em class="rfc2119">not required</em> to be an employee of a Member organization,
+	and <em class="rfc2119">may</em> be a <a href="#fellows" id="ref-for-fellows①">W3C Fellow</a>.
+	The nomination form <em class="rfc2119">must</em> ask for the nominee’s <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation②">primary affiliation</a>,
+	and this will be reported on the ballot.
+	For most nominees,
+	the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="primary-affiliation">primary affiliation</dfn> is their employer and will match their affiliation in the W3C database.
+	For contractors and invited experts,
+	this will normally be their contracting company
+	or their invited expert status;
+	in some cases
+	(e.g. where a consultant is consulting for only one organization)
+	this <em class="rfc2119">may</em> be the organization for whom the nominee is consulting.
+	A <a href="#AB-TAG-constraints">change of affiliation</a> is defined
+	such that this field would carry a different answer
+	if the nominee were to be re-nominated
+	(therefore,
+	terminating employment,
+	or accepting new employment,
+	are changes of affiliation).
+	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
+	Each nomination <em class="rfc2119">should</em> include
+	a few informative paragraphs about the nominee.</p>
+    <p>If, after the deadline for nominations, the number of nominees is:</p>
+    <ul>
+     <li> Greater than or equal to the minimum number of available seats
+			and less than or equal to the maximum number of available seats,
+			those nominees are thereby elected.
+			This situation constitutes a tie for the purpose of assigning <a href="#short-term">incomplete terms</a>.
+			Furthermore, if the number is less than the maximum number of available seats,
+			the longest terms are filled first. 
+     <li> Less than the minimum number of available seats,
+			Calls for Nominations are issued until a sufficient number of people have been nominated.
+			Those already nominated do not need to be renominated after a renewed call. 
+     <li> Greater than the maximum number of available seats,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team②⑧">Team</a> issues a Call for Votes
+			that includes the names of all candidates,
+			the (maximum) number of available seats,
+			the deadline for votes,
+			details about the vote tabulation system selected by the Team for the election,
+			and operational information. 
+    </ul>
+    <p>When there is a vote,
+	each Member
+	(or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member②">related Members</a>) <em class="rfc2119">may</em> submit one ballot that ranks candidates in the Member’s preferred order.
+	Once the deadline for votes has passed,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team②⑨">Team</a> announces the results to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑨">Advisory Committee</a>.
+	In case of a tie the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to fill the available seats.</p>
+    <p id="short-term">The shortest incomplete term is assigned to the elected candidate ranked lowest by the tabulation of votes,
+	the next shortest term to the next-lowest ranked elected candidate,
+	and so on.
+	In the case of a tie among those eligible for a incomplete term,
+	the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to assign the incomplete term. </p>
+    <p>Refer to <a href="https://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a> <a data-link-type="biblio" href="#biblio-election-howto" title="How to Organize an Advisory Board or TAG election">[ELECTION-HOWTO]</a> for more details.</p>
+    <h5 class="heading settled" data-level="3.3.3.4" id="TAG-appointments"><span class="secno">3.3.3.4. </span><span class="content"> Technical Architecture Group Appointments</span><a class="self-link" href="#TAG-appointments"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③⓪">Team</a> is responsible for appointing
+	3 of the participants to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑥">Technical Architecture Group</a>.
+	This mechanism complements the election process.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③①">Team</a> <em class="rfc2119">should</em> use its appointments to support
+	a diverse and well-balanced <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑦">TAG</a>,
+	including diversity of technical background, knowledge, and skill sets.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③②">Team</a> <em class="rfc2119">should</em> actively seek
+	candidates for appointment to the TAG,
+	and <em class="rfc2119">must</em> make available to
+	the W3C community at large
+	a means to propose candidates for consideration,
+	explicitly soliciting input from at least
+	current and incoming <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑧">TAG</a> members, the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⓪">Advisory Committee</a>, and <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②">Chairs</a>.</p>
+    <p>The constraints for appointment to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑨">TAG</a> are
+	the same as for elected participants
+	(see <a href="#AB-TAG-constraints">§ 3.3.3.2 Elected Groups Participation Constraints</a> and <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a>),
+	with the additional constraint that
+	a person <em class="rfc2119">must not</em> be appointed
+	for more than two <em>consecutive</em> terms.
+	(Partial terms used to fill a vacated seat do not count towards this limit.)</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Individuals who have reached the limit of two consecutive appointed terms <em class="rfc2119">may</em> freely run for election
+	if they wish to continue serving on the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⓪">TAG</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③③">Team</a>'s choice of appointee(s)
+	is subject to ratification by secret ballot
+	by both the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑧">AB</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②①">TAG</a>,
+	each requiring a two-thirds approval.
+	In the case of regularly scheduled elections,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②②">TAG</a> participants in this ratification are
+	its members for the upcoming term.</p>
+    <p>For regularly scheduled elections,
+	selection begins once the results of the elections are known,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team③④">Team</a> <em class="rfc2119">should</em> announce the ratified appointment(s)
+	no later than the start of the regularly scheduled term.
+	When an appointed seat is vacated outside of a regularly scheduled election,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⑤">Team</a> <em class="rfc2119">should</em> seek to appoint a replacement
+	unless a regular Call for Nominations is scheduled within 2 months,
+	and it <em class="rfc2119">must</em> announce the ratified appointment
+	no later than the Call for Nominations of the next scheduled election.</p>
+    <h5 class="heading settled" data-level="3.3.3.5" id="random"><span class="secno">3.3.3.5. </span><span class="content"> Verifiable Random Selection Procedure</span><a class="self-link" href="#random"></a></h5>
+    <p>When it is necessary to use a verifiable random selection process
+	(e.g., in an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑨">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②③">TAG</a> election,
+	to “draw straws” in case of a tie
+	or to fill a incomplete term),
+	W3C uses the random and verifiable procedure defined in <a href="https://www.ietf.org/rfc/rfc3797.txt">RFC 3797</a> <a data-link-type="biblio" href="#biblio-rfc3797" title="Publicly Verifiable Nominations Committee (NomCom) Random Selection">[RFC3797]</a>.
+	The procedure orders an input list of names
+	(listed in alphabetical order by family name unless otherwise specified)
+	into a “result order”.</p>
+    <p>W3C applies this procedure as follows:</p>
+    <p></p>
+    <ol>
+     <li> When N people have tied for M (less than N) seats.
+			In this case, only the names of the N individuals who tied
+			are provided as input to the procedure.
+			The M seats are assigned in result order. 
+     <li> After all elected individuals have been identified,
+			when N people are eligible for M (less than N) incomplete terms.
+			In this case, only the names of those N individuals are provided as input to the procedure.
+			The incomplete terms are assigned in result order. 
+    </ol>
+    <h5 class="heading settled" data-level="3.3.3.6" id="AB-TAG-vacated"><span class="secno">3.3.3.6. </span><span class="content"> Elected Groups Vacated Seats</span><a class="self-link" href="#AB-TAG-vacated"></a></h5>
+    <p>An <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⓪">Advisory Board</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②④">TAG</a> participant’s seat is vacated when:</p>
+    <ul>
+     <li> the participant resigns, or 
+     <li> an Advisory Board or TAG participant changes affiliations
+			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
+			or 
+     <li> the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo④">CEO</a> dismisses the participant
+			for failing to meet the criteria in section <a href="#ParticipationCriteria">§ 3.1.1 Individual Participation Criteria</a>,
+			or 
+     <li> their term ends. 
+    </ul>
+    <p>If a participant changes affiliation,
+	but the <a href="#AB-TAG-constraints">participation constraints</a> are met,
+	that participant’s seat becomes vacant at the next regularly scheduled election for that group.</p>
+    <p>Vacated seats are filled according to this schedule:</p>
+    <ul>
+     <li> When an appointed <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑤">TAG</a> seat is vacated,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team③⑥">Team</a> <a href="#TAG-appointments">appoints</a> a replacement. 
+     <li>
+       When an elected seat on either the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②①">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑥">TAG</a> is vacated,
+			the seat is filled at the next regularly scheduled election for the group
+			unless the group Chair requests that W3C hold an election before then
+			(for instance, due to the group’s workload). 
+      <ul>
+       <li> The group Chair <em class="rfc2119">should not</em> request such an election
+					if the next regularly scheduled election is fewer than three months away. 
+       <li> The group Chair <em class="rfc2119">may</em> request an election,
+					and the election may begin, as soon as a current member gives notice of a resignation,
+					including a resignation effective as of a given date in the future. 
+      </ul>
+      <p>When such an election is held,
+			the minimum number of available seats is such that
+			when added to the number of continuing participants,
+			the minimum total number of elected seats is met
+			(8 for the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑦">TAG</a>, 9 for the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②②">AB</a>);
+			and the maximum number corresponds to all unoccupied seats.
+			Except for the number of available seats and the length of the terms,
+			the <a href="#AB-TAG-elections">usual rules for Advisory Board and Technical Architecture Group Elections</a> apply.</p>
+    </ul>
+    <h3 class="heading settled" data-level="3.4" id="GAGeneral"><span class="secno">3.4. </span><span class="content"> Chartered Groups: Working Groups and Interest Groups</span><span id="ChapterGroups"></span><span id="WG-and-IG"></span><a class="self-link" href="#GAGeneral"></a></h3>
+    <p id="GAGroups">This document defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chartered-group">chartered groups</dfn>: </p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsWG"><a href="#GroupsWG" id="ref-for-GroupsWG⑨③">Working Groups</a></dfn>. 
+     <dd>
+       Working Groups typically produce deliverables
+			(e.g., <a href="#rec-advance">Recommendation Track technical reports</a>,
+			software,
+			test suites,
+			and reviews of the deliverables of other groups)
+			as defined in their <a href="#WGCharter">charter</a>. 
+      <p>Working Groups have additional participation requirements
+			described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			see particularly the “<a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Obligations">Licensing Obligations of Working Group Participants</a>”
+			and the patent claim exclusion process
+			in “<a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">Exclusion From W3C RF Licensing Requirements</a>”.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsIG"><a href="#GroupsIG" id="ref-for-GroupsIG①①">Interest Groups</a></dfn>. 
+     <dd>
+       The primary goal of an Interest Group
+			is to bring together people who wish to evaluate potential Web technologies and policies.
+			An Interest Group is a forum for the exchange of ideas. 
+      <p>Interest Groups do not publish <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑤">Recommendation Track technical reports</a>;
+			but can publish <a href="#WGNote" id="ref-for-WGNote">technical reports on the Note Track</a>.</p>
+    </dl>
+    <h4 class="heading settled" data-level="3.4.1" id="ReqsAllGroups"><span class="secno">3.4.1. </span><span class="content"> Requirements for All Chartered Groups</span><a class="self-link" href="#ReqsAllGroups"></a></h4>
+    <p>Each group <em class="rfc2119">must</em> have a <a data-link-type="dfn" href="#charter" id="ref-for-charter">charter</a>.
+	Requirements for the charter depend on the group type.
+	All group charters <em class="rfc2119">must</em> be public
+	(even if other proceedings of the group are <a href="#Member-only" id="ref-for-Member-only①⑤">Member-only</a>).</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GeneralChairs">Chair</dfn> (or co-Chairs)
+	to coordinate the group’s tasks.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③⑦">Team</a> appoints (and re-appoints) Chairs for all groups.
+	The Chair is a <a href="#member-rep">Member representative</a>,
+	a <a href="#Team">Team representative</a>,
+	or an <a href="#invited-expert-wg">Invited Expert</a>,
+	(invited by the <a data-link-type="dfn" href="#team" id="ref-for-team③⑧">Team</a>).
+	The requirements of this document that apply to those types of participants apply to Chairs as well.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/Guide/chair/role.html">role of the Chair</a> <a data-link-type="biblio" href="#biblio-chair" title="W3C Working/Interest Group Chair">[CHAIR]</a> is described
+	in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="TeamContact">Team Contact</dfn>,
+	who acts as the interface between the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③">Chair</a>,
+	group participants,
+	and the rest of the Team.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/Guide/teamcontact/role.html">role of the Team Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> is described in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs④">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact">Team Contact</a> of a group <em class="rfc2119">should not</em> be the same individual.</p>
+    <p>Each group <em class="rfc2119">must</em> have an archived mailing list
+	for formal group communication
+	(e.g., for meeting announcements and <a data-link-type="dfn" href="#minutes" id="ref-for-minutes①">minutes</a>,
+	documentation of decisions,
+	and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②">Formal Objections</a> to decisions).
+	It is the responsibility of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑤">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①">Team Contact</a> to ensure that new participants are subscribed to all relevant mailing lists.
+	Refer to the list of <a href="https://www.w3.org/groups/">group mailing lists</a> <a data-link-type="biblio" href="#biblio-group-mail" title="Group mailing lists">[GROUP-MAIL]</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑥">Chair</a> <em class="rfc2119">may</em> form task forces
+	(composed of group participants)
+	to carry out assignments for the group.
+	The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group’s charter.
+	A group <em class="rfc2119">should</em> document the process it uses
+	to create task forces
+	(e.g., each task force might have an informal "charter").
+	Task forces do not publish <a href="#Reports">technical reports</a>;
+	the Working Group <em class="rfc2119">may</em> choose to publish their results as part of a technical report. </p>
+    <h4 class="heading settled" data-level="3.4.2" id="group-participation"><span class="secno">3.4.2. </span><span class="content"> Participation in Chartered Groups</span><a class="self-link" href="#group-participation"></a></h4>
+    <p>There are three types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="wgparticipant">participants in a Working Group</dfn>: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
+	and <a href="#Team">Team representatives</a> (including the <a href="#TeamContact" id="ref-for-TeamContact⑦">Team Contact</a>).</p>
+    <p>There are four types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="igparticipant">participants in an Interest Group</dfn>:
+	the same three types as for Working Groups plus,
+	for an Interest Group where the only <a href="#ig-mail-only">participation requirement is mailing list subscription</a>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="public-participant-ig">public participants</dfn>.</p>
+    <p>Except where noted in this document or in a group charter,
+	all participants share the same rights and responsibilities in a group;
+	see also the <a href="#ParticipationCriteria">individual participation criteria</a>.</p>
+    <p>A participant <em class="rfc2119">may</em> represent more than one organization
+	in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①">Interest Group</a>.
+	Those organizations <em class="rfc2119">must</em> all be members of the group.</p>
+    <p>An individual <em class="rfc2119">may</em> become
+	a Working or Interest Group participant
+	at any time during the group’s existence.
+	See also relevant requirements in
+	“Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>On an exceptional basis,
+	a Working or Interest Group participant <em class="rfc2119">may</em> designate
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mtg-substitute">substitute</dfn> to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑦">Chair</a>.
+	The substitute <em class="rfc2119">may</em> act on behalf of the participant,
+	including for <a href="#Votes">votes</a>.
+	For the substitute to vote,
+	the participant <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑧">Chair</a> in writing in advance.
+	As a courtesy to the group,
+	if the substitute is not well-versed in the group’s discussions,
+	the regular participant <em class="rfc2119">should</em> authorize another participant to act as <a href="#proxy" id="ref-for-proxy">proxy</a> for votes.</p>
+    <p>To allow rapid progress,
+	Working Groups are intended to be small
+	(typically fewer than 15 people)
+	and composed of experts in the area defined by the charter.
+	In principle,
+	Interest Groups have no limit on the number of participants.
+	When a Working Group grows too large to be effective,
+	W3C <em class="rfc2119">may</em> split it into an Interest Group
+	(a discussion forum)
+	and a much smaller Working Group
+	(a core group of highly dedicated participants).</p>
+    <h4 class="heading settled" data-level="3.4.3" id="chartered-group-participants"><span class="secno">3.4.3. </span><span class="content"> Types of Participants in Chartered Groups</span><a class="self-link" href="#chartered-group-participants"></a></h4>
+    <h5 class="heading settled" data-level="3.4.3.1" id="member-rep-wg"><span class="secno">3.4.3.1. </span><span class="content"> Member Representative in a Working Group</span><a class="self-link" href="#member-rep-wg"></a></h5>
+    <p>An individual is a <dfn data-dfn-type="dfn" data-export id="member-representative-in-a-working-group">Member representative in a Working Group<a class="self-link" href="#member-representative-in-a-working-group"></a></dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Advisory Committee representative of the Member in question
+			has designated the individual as a Working Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a Member representative in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤">Working Group</a>,
+	an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①①">Advisory Committee representative</a> <em class="rfc2119">must</em> provide the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑨">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact②">Team Contact</a> with all of the following <span id="member-rep-info">information</span>,
+	in addition to any other information required by the <a href="#cfp">Call for Participation</a> and charter
+	(including the participation requirements of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>):</p>
+    <ol>
+     <li> The name of the W3C Member the individual represents
+			and whether the individual is an employee of that Member organization; 
+     <li> A statement that the individual accepts the participation terms
+			set forth in the charter
+			(with an indication of charter date or version); 
+     <li> A statement that the Member will provide the necessary financial support for participation
+			(e.g., for travel, telephone calls, and conferences). 
+    </ol>
+    <p>A Member participates in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥">Working Group</a> from the moment the first Member representative joins the group
+	until either of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Member <a href="#resignation">resigns</a> from the Working Group;
+			this is done through the Member’s Advisory Committee representative. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.2" id="member-rep-ig"><span class="secno">3.4.3.2. </span><span class="content"> Member Representative in an Interest Group</span><a class="self-link" href="#member-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-an-interest-group">Member representative in an Interest Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①②">Advisory Committee representative</a> of the Member in question has designated the individual
+			as an Interest Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a <a data-link-type="dfn" href="#member-representative-in-an-interest-group" id="ref-for-member-representative-in-an-interest-group">Member representative in an Interest Group</a>,
+	the Advisory Committee representative <em class="rfc2119">must</em> follow the instructions
+	in the <a href="#cfp">Call for Participation</a> and charter.</p>
+    <p>Member participation in an Interest Group ceases under the same conditions as for a Working Group.</p>
+    <h5 class="heading settled" data-level="3.4.3.3" id="invited-expert-wg"><span class="secno">3.4.3.3. </span><span class="content"> Invited Expert in a Working Group</span><a class="self-link" href="#invited-expert-wg"></a></h5>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⓪">Chair</a> <em class="rfc2119">may</em> invite an individual with a particular expertise
+	to participate in a Working Group.
+	This individual <em class="rfc2119">may</em> represent an organization in the group
+	(e.g., if acting as a liaison with another organization).</p>
+    <p>An individual is an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-a-working-group">Invited Expert in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Chair has designated the individual as a group participant, 
+     <li> the Team Contact has agreed with the Chair’s choice, and 
+     <li> the individual has provided the <a href="#inv-expert-info" id="ref-for-inv-expert-info①">information required of an Invited Expert</a> to the Chair and Team Contact. 
+    </ul>
+    <p>To designate an individual as an Invited Expert in a Working Group,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①①">Chair</a> <em class="rfc2119">must</em> inform the Team Contact
+	and provide rationale for the choice.
+	When the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①②">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact③">Team Contact</a> disagree about a designation,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑤">CEO</a> determines
+	whether the individual will be invited to participate in the Working Group.</p>
+    <p>To <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="inv-expert-info">participate in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦">Working Group</a> as an Invited Expert</dfn>,
+	an individual <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> identify the organization, if any, the individual represents as a participant in this group, 
+     <li> agree to the terms of the <a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">invited expert and collaborators agreement</a> <a data-link-type="biblio" href="#biblio-collaborators-agreement" title="Invited expert and collaborators agreement">[COLLABORATORS-AGREEMENT]</a>, 
+     <li> accept the participation terms set forth in the charter,
+			including the participation requirements of
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			especially in “Note on Licensing Commitments for Invited Experts”
+			and in “Disclosure”,
+			indicating a specific charter date or version, 
+     <li> disclose whether the individual is an employee of a W3C Member;
+			see the <a href="#coi">conflict of interest policy</a>, 
+     <li> provide a statement of who will provide the necessary financial support
+			for the individual’s participation
+			(e.g., for travel, telephone calls, and conferences), and 
+     <li> if the individual’s employer (including a self-employed individual)
+			or the organization the individual represents
+			is not a W3C Member,
+			indicate whether that organization intends to join W3C.
+			If the organization does not intend to join W3C,
+			indicate reasons the individual is aware of for this choice. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①③">Chair</a> <em class="rfc2119">should not</em> designate as an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group">Invited Expert in a Working Group</a> an individual who is an employee of a W3C Member.
+	The Chair <em class="rfc2119">must not</em> use Invited Expert status
+	to circumvent participation limits imposed by the <a href="#WGCharter">charter</a>.</p>
+    <p>An Invited Expert participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Chair or <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑥">CEO</a> withdraws the invitation to participate, or 
+     <li> the individual <a href="#resignation">resigns</a>. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.4" id="invited-expert-ig"><span class="secno">3.4.3.4. </span><span class="content"> Invited Expert in an Interest Group</span><a class="self-link" href="#invited-expert-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	the participation requirements for an <dfn data-dfn-type="dfn" data-export id="invited-expert-in-an-interest-group">Invited Expert in an Interest Group<a class="self-link" href="#invited-expert-in-an-interest-group"></a></dfn> are the same as those for an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group①">Invited Expert in a Working Group</a>.</p>
+    <h5 class="heading settled" data-level="3.4.3.5" id="team-rep-wg"><span class="secno">3.4.3.5. </span><span class="content"> Team Representative in a Working Group</span><a class="self-link" href="#team-rep-wg"></a></h5>
+    <p>An individual is a <dfn data-dfn-type="dfn" data-export id="team-representative-in-a-working-group">Team representative in a Working Group<a class="self-link" href="#team-representative-in-a-working-group"></a></dfn> when so designated by W3C management.
+	Team representatives both contribute to the technical work
+	and help ensure the group’s proper integration with the rest of W3C.</p>
+    <p>A Team representative participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> W3C management changes Team representation by sending email to the Chair,
+			copying the group mailing list. 
+    </ul>
+    <p>The Team participates in a Working Group
+	from the moment the creation of the group is announced
+	until the group closes.</p>
+    <h5 class="heading settled" data-level="3.4.3.6" id="team-rep-ig"><span class="secno">3.4.3.6. </span><span class="content"> Team Representative in an Interest Group</span><a class="self-link" href="#team-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn data-dfn-type="dfn" data-export id="team-representative-in-an-interest-group">Team representative in an Interest Group<a class="self-link" href="#team-representative-in-an-interest-group"></a></dfn> when so designated by W3C management.</p>
+    <h2 class="heading settled" data-level="4" id="group-lifecyle"><span class="secno">4. </span><span class="content"> Lifecycle of Chartered Groups</span><a class="self-link" href="#group-lifecyle"></a></h2>
+    <h3 class="heading settled" data-level="4.1" id="WGCharterDevelopment"><span class="secno">4.1. </span><span class="content"> Initiating Charter Development</span><a class="self-link" href="#WGCharterDevelopment"></a></h3>
+    <p>W3C creates charters for <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group">chartered groups</a> based on interest from the Members and Team.
+	The Team <em class="rfc2119">must</em> notify the Advisory Committee
+	when a charter for a new Working Group or Interest Group is in development.
+	This is intended to raise awareness,
+	even if no formal proposal is yet available.
+	Advisory Committee representatives <em class="rfc2119">may</em> provide
+	feedback on the <a href="#ACCommunication">Advisory Committee discussion list</a> or via other designated channels.</p>
+    <p>W3C <em class="rfc2119">may</em> begin work
+	on a Working Group or Interest Group charter
+	at any time.</p>
+    <h3 class="heading settled" data-level="4.2" id="WGCharter"><span class="secno">4.2. </span><span class="content"> Content of a Charter</span><a class="self-link" href="#WGCharter"></a></h3>
+    <p>A Working Group or Interest Group <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="charter">charter</dfn> <em class="rfc2119">must</em> include all of the following information.</p>
+    <ul>
+     <li> The group’s mission
+			(e.g., develop a technology or process, review the work of other groups). 
+     <li> The scope of the group’s work and criteria for success. 
+     <li> The duration of the group (typically from six months to two years). 
+     <li> The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software). 
+     <li>
+       Expected milestone dates where available. 
+      <p class="note" role="note"><span class="marker">Note:</span> A charter is <em class="rfc2119">not required</em> to include schedules for review of other group’s deliverables.</p>
+     <li> The process for the group to approve the release of deliverables
+			(including intermediate results). 
+     <li> Any dependencies by groups within or outside of W3C on the deliverables of this group.
+			For any dependencies, the charter <em class="rfc2119">must</em> specify
+			the mechanisms for communication about the deliverables. 
+     <li> Any dependencies of this group on other groups within or outside of W3C.
+			Such dependencies include interactions with <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a>. 
+     <li> The <a href="#confidentiality-levels">level of confidentiality</a> of the group’s proceedings and deliverables. 
+     <li> Meeting mechanisms and expected frequency. 
+     <li> If known,
+			the date of the first <a href="#ftf-meeting" id="ref-for-ftf-meeting①">face-to-face meeting</a>.
+			The date of the first face-to-face meeting of a proposed group <em class="rfc2119">must not</em> be sooner than <span class="time-interval">eight weeks</span> after the date of the proposal. 
+     <li> Communication mechanisms to be employed within the group,
+			between the group and the rest of W3C,
+			and with the general public. 
+     <li> Any voting procedures or requirements
+			other than those specified in <a href="#Votes">§ 5.2.3 Deciding by Vote</a>. 
+     <li> An estimate of the expected time commitment from participants. 
+     <li> The expected time commitment and level of involvement by the Team
+			(e.g., to track developments,
+			write and edit technical reports,
+			develop code,
+			or organize pilot experiments). 
+     <li> Intellectual property information.
+			What are the intellectual property (including patents and copyright)
+			considerations affecting the success of the Group?
+			In particular, is there any reason to believe
+			that it will be difficult to meet the Royalty-Free licensing goals
+			in “Licensing Goals for W3C Specifications”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>? 
+    </ul>
+    <p>See also the charter requirements in “Licensing Goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>For every Recommendation Track deliverable
+	that continues work on <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report">technical report</a> published under any other Charter (including a predecessor group of the same name),
+	for which there is at least an existing <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd">First Public Working Draft</a> the description of that deliverable in the proposed charter of the adopting Working Group <em class="rfc2119">must</em> provide the following information:</p>
+    <ul>
+     <li> The title,
+			stable URL,
+			and publication date of the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD">Working Draft</a> or other Recommendation-track document
+			that will serve as the basis for work on the deliverable
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="adopted-draft">Adopted Draft</dfn>”); 
+     <li> The title,
+			stable URL,
+			and publication date of the document
+			that was used as the basis for its most recent Exclusion Opportunity
+			as per
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft">Exclusion Draft</dfn>”); and 
+     <li> The stable URL of the Working Group charter
+			under which the Exclusion Draft was published
+			(labeled the “<dfn data-dfn-type="dfn" data-export id="exclusion-draft-charter">Exclusion Draft Charter<span id="other-charter"></span><a class="self-link" href="#exclusion-draft-charter"></a></dfn>”). 
+    </ul>
+    <p>All of the above data <em class="rfc2119">must</em> be identified
+	in the adopting Working Group’s charter using the labels indicated.</p>
+    <p>The <a data-link-type="dfn" href="#adopted-draft" id="ref-for-adopted-draft">Adopted Draft</a> and the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft">Exclusion Draft</a> <em class="rfc2119">must</em> each be adopted in their entirety and without any modification.
+	The proposed charter <em class="rfc2119">must</em> state
+	the dates on which the Exclusion Opportunity
+	that arose on publishing the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft①">Exclusion Draft</a> began and ended.
+	As per “Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	this potentially means that exclusions can only be made immediately on joining a Working Group.</p>
+    <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding participation,
+	including specifying
+	that the <span id="ig-mail-only">only requirement for participation (by anyone) in
+	the Interest Group is subscription to the Interest Group mailing list</span>.
+	This type of Interest Group <em class="rfc2119">may</em> have <a href="#public-participant-ig" id="ref-for-public-participant-ig">public participants</a>. </p>
+    <p>A charter <em class="rfc2119">may</em> include
+	provisions other than those required by this document.
+	The charter <em class="rfc2119">should</em> highlight
+	whether additional provisions impose constraints
+	beyond those of the W3C 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>
+    <h3 class="heading settled" data-level="4.3" id="CharterReview"><span class="secno">4.3. </span><span class="content"> Advisory Committee Review of a Charter</span><a class="self-link" href="#CharterReview"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③⑨">Team</a> <em class="rfc2119">must</em> solicit <a href="#ACReview">Advisory Committee review</a> of every new or substantively modified Working Group or Interest Group charter,
+	except for either:</p>
+    <ul>
+     <li data-md>
+      <p>a charter extension</p>
+     <li data-md>
+      <p>substantive changes to a charter that do not affect the way the group functions in any significant way.</p>
+    </ul>
+    <p>The review period <em class="rfc2119">must</em> be at least 28 days.
+	The following are examples of substantive changes that would not require an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review">Advisory Committee Review</a>:
+	the addition of an in-scope deliverable,
+	a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact④">Team Contact</a>,
+	or a change of <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①④">Chair</a>.
+	Such changes must nonetheless be announced
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①①">Advisory Committee</a> and to <a href="#wgparticipant" id="ref-for-wgparticipant①"> participants in the Working</a> or <a href="#igparticipant" id="ref-for-igparticipant①">in the Interest Group</a>,
+	and a rationale must be provided.</p>
+    <p>The Call for Review of a substantively modified charter <em class="rfc2119">must</em> highlight important changes
+	(e.g., regarding deliverables or resource allocation)
+	and include rationale for the changes.</p>
+    <p>As part of the Advisory Committee review of any new or substantively modified Working Group charter,
+	any Advisory Committee representative <em class="rfc2119">may</em> request an extended review period.</p>
+    <p>Such a request must be submitted with a Member’s comments
+	in response to the Call for Review.
+	Upon receipt of any such request,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④⓪">Team</a> <em class="rfc2119">must</em> ensure
+	that the Call for Participation for the Working Group
+	occurs at least 60 days
+	after the Call for Review of the charter.</p>
+    <h3 class="heading settled" data-level="4.4" id="cfp"><span class="secno">4.4. </span><span class="content"> Call for Participation in a Chartered Group</span><a class="self-link" href="#cfp"></a></h3>
+    <p>Deciding whether to adopt a proposed <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG②">Interest Group</a> <a data-link-type="dfn" href="#charter" id="ref-for-charter①">charter</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①">W3C Decision</a>.
+	Charters <em class="rfc2119">may</em> be amended based on review comments
+	per <a href="#ACReviewAfter">§ 5.7.2 After the Review Period</a> before the Call for Participation.</p>
+    <p>If the decision is to charter the group,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④①">Team</a> <em class="rfc2119">must</em> issue a Call for Participation to the Advisory Committee.
+	For a new group, this announcement officially creates the group.
+	The announcement <em class="rfc2119">must</em> include a reference to the <a href="#WGCharter">charter</a>,
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑤">Chair</a>(s),
+	and the name(s) of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑤">Team Contact</a>(s).</p>
+    <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).
+	When a group is re-chartered,
+	individuals participating in the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG③">Interest Group</a> before the new Call for Participation
+	may attend any meetings held within forty-five (45) days of the Call for Participation
+	even if they have not yet formally rejoined the group
+	(i.e., committed to the terms of the charter and patent policy).</p>
+    <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against the decision to create
+	or substantially modify
+	a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.5" id="charter-extension"><span class="secno">4.5. </span><span class="content"> Charter Extension</span><a class="self-link" href="#charter-extension"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④②">Team</a> <em class="rfc2119">may</em> decide
+	to extend a Working Group or Interest Group charter
+	with no other substantive modifications.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team④③">Team</a> <em class="rfc2119">must</em> announce
+	such <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="charter extension" id="dfn-charter-extension">extensions</dfn> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①②">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate the new duration.
+	The announcement <em class="rfc2119">must</em> also include rationale for the extension,
+	a reference to the <a href="#WGCharter">charter</a>,
+	and the Group homepage
+	(which includes at least
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑥">Chair</a>(s),
+	the name of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑥">Team Contact</a>,
+	and instructions for joining the group).</p>
+    <p>After a charter extension,
+	Advisory Committee representatives
+	and the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑦">Chair</a> 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> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①">Team decision</a> regarding the extension of a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.6" id="GeneralTermination"><span class="secno">4.6. </span><span class="content"> Chartered Group Closure</span><a class="self-link" href="#GeneralTermination"></a></h3>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⓪">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG④">Interest Group</a> charter specifies a duration for the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④④">Team</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑧">TAG</a>, or the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②③">AB</a> <em class="rfc2119">may</em> propose to close a group
+	prior to the date specified in the charter in any of the following circumstances:</p>
+    <ul>
+     <li data-md>
+      <p>There are insufficient member resources to produce chartered deliverables
+or to maintain the group,
+according to priorities established within W3C.</p>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="https://www.w3.org/Consortium/Patent-Policy/#patent-advisory-group" id="ref-for-patent-advisory-group">Patent Advisory Group</a> concluded that the work <em class="rfc2119">should</em> be terminated.</p>
+     <li data-md>
+      <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑨">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②④">AB</a> determined that continuing operation of the chartered group or its work
+would be detrimental to W3C or its mission.</p>
+     <li data-md>
+      <p>The group produced all chartered deliverables ahead of schedule.</p>
+    </ul>
+    <p>Such a proposal to close a group must be accompanied by rationale,
+	and the proposal must be confirmed by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision②">W3C Decision</a>.</p>
+    <p>Closing a Working Group has implications
+	with respect to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h2 class="heading settled" data-level="5" id="decisions"><span class="secno">5. </span><span class="content"> Decisions</span><a class="self-link" href="#decisions"></a></h2>
+    <p>W3C attempts to resolve issues through dialog.
+	Individuals who disagree strongly with a decision <em class="rfc2119">should</em> register with the Chair any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③">Formal Objections</a>.</p>
+    <h3 class="heading settled" data-level="5.1" id="decision-types"><span class="secno">5.1. </span><span class="content"> Types of Decisions</span><a class="self-link" href="#decision-types"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑧">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①①">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑤">Interest Group</a> has the prerogative
+	to make certain decisions based on their own judgment.
+	Such decisions are called <dfn data-dfn-type="dfn" data-export id="chair-decisions">chair decisions<a class="self-link" href="#chair-decisions"></a></dfn>.</p>
+    <p>In contrast,
+	decisions taken by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑨">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①②">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑥">Interest Group</a> on the basis of having assessed the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus">consensus</a> of the group
+	or following a vote (see <a href="#Votes">§ 5.2.3 Deciding by Vote</a>)
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="group decision | resolution" id="group-decision">group decisions</dfn> (also known as group “resolutions”).</p>
+    <p>Decisions made by members of the <a data-link-type="dfn" href="#team" id="ref-for-team④⑤">Team</a> in connection with this Process,
+	based on their own individual or collective judgement,
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Team Decision | Team’s Decision" data-noexport id="team-decision">Team Decisions</dfn>.</p>
+    <p>In contrast,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-w3c-decision">W3C decision</dfn> is
+	determined by the <a data-link-type="dfn" href="#team" id="ref-for-team④⑥">Team</a> on behalf of the W3C community
+	by assessing the consensus of the W3C Community after an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②">Advisory Committee review</a>.</p>
+    <h3 class="heading settled" data-level="5.2" id="consensus-building"><span class="secno">5.2. </span><span class="content"> Consensus Building</span><a class="self-link" href="#consensus-building"></a></h3>
+    <h4 class="heading settled" data-level="5.2.1" id="Consensus"><span class="secno">5.2.1. </span><span class="content"> Consensus</span><a class="self-link" href="#Consensus"></a></h4>
+    <p>Consensus is a core value of W3C.
+	To promote consensus,
+	the W3C process requires Chairs to ensure
+	that groups consider all legitimate views and objections,
+	and endeavor to resolve them,
+	whether these views and objections are expressed by the active participants of the group
+	or by others
+	(e.g., another W3C group,
+	a group in another organization,
+	or the general public).
+	Decisions <em class="rfc2119">may</em> be made during meetings
+	(<a href="#ftf-meeting" id="ref-for-ftf-meeting②">face-to-face</a> or <a href="#distributed-meeting" id="ref-for-distributed-meeting">distributed</a>)
+	as well as through <a href="#discussion-archiving">persistent text-based discussions</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The CEO has the role of
+	assessing consensus within the Advisory Committee.</p>
+    <p>The following terms are used in this document
+	to describe the level of support for a decision among a set of eligible individuals:</p>
+    <dl>
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Consensus">Consensus</dfn>: 
+     <dd> A substantial number of individuals in the set
+			support the decision
+			and there is no sustained objection from anybody in the set.
+			Individuals in the set <em class="rfc2119">may</em> abstain.
+			Abstention is either an explicit expression of no opinion
+			or silence by an individual in the set. 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Unanimity">Unanimity</dfn>: 
+     <dd> The particular case of <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①">consensus</a> where all individuals in the set support the decision
+			(i.e., no individual in the set abstains). 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Dissent">Dissent</dfn>: 
+     <dd> At least one individual in the set sustains an objection. 
+    </dl>
+    <p class="note" role="note"><span class="marker">Note:</span> A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④">Formal Objection</a> always indicates a sustained objection,
+	but isn’t necessary to express it
+	(except in the context of formal <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③">AC Reviews</a>).
+	Disagreement with a proposed decision,
+	however, does not always rise to the level of sustained objection,
+	as individuals could be willing to accept a decision
+	while expressing disagreement.</p>
+    <p>By default, the set of individuals eligible to participate in a decision is the set of group participants.
+	The Process Document does not require a quorum for decisions
+	(i.e., the minimal number of eligible participants required to be present before the Chair can call a question).
+	A charter <em class="rfc2119">may</em> include a quorum requirement for consensus decisions.</p>
+    <p>Where <a data-link-type="dfn" href="#def-Unanimity" id="ref-for-def-Unanimity">unanimity</a> is not possible,
+	a group <em class="rfc2119">should</em> strive to make <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②">consensus</a> decisions
+	where there is significant support and few abstentions.
+	The Process Document does not require a particular percentage of eligible participants
+	to agree to a motion in order for a decision to be made.
+	To avoid decisions where there is widespread apathy,
+	(i.e., little support and many abstentions),
+	groups <em class="rfc2119">should</em> set minimum thresholds of active support before a decision can be recorded.
+	The appropriate percentage <em class="rfc2119">may</em> vary depending on the size of the group
+	and the nature of the decision.
+	A charter <em class="rfc2119">may</em> include threshold requirements for consensus decisions.
+	For instance, a charter might require a supermajority of eligible participants
+	(i.e., some established percentage above 50%)
+	to support certain types of consensus decisions.</p>
+    <div class="note" role="note">
+      Note: Chairs have substantial flexibility
+	in how they obtain and assess consensus among their groups.
+	Unless otherwise constrained by charter,
+	they may use modes including but not limited to explicit calls for consensus,
+	polls of participants,
+	“lazy consensus” in which lack of objection after sufficient notice is taken as assent;
+	or they may also delegate and empower a document editor
+	to assess consensus on their behalf,
+	whether in general
+	or for specific pre-determined circumstances
+	(e.g. in non-controversial situations, for specific types of issues, etc.). 
+     <p>If questions or disagreements arise,
+	the final determination of consensus remains with the chair.</p>
+    </div>
+    <h4 class="heading settled" data-level="5.2.2" id="managing-dissent"><span class="secno">5.2.2. </span><span class="content"> Managing Dissent</span><a class="self-link" href="#managing-dissent"></a></h4>
+    <p>In some cases, even after careful consideration of all points of view,
+	a group might find itself unable to reach consensus.
+	The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⓪">Chair</a> <em class="rfc2119">may</em> record a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent">dissent</a> so that the group can make progress
+	(for example, to produce a deliverable in a timely manner).
+	Dissenters cannot stop a group’s work
+	simply by saying that they cannot live with a decision.
+	When the Chair believes that the Group has duly considered
+	the legitimate concerns of dissenters as far as is possible and reasonable,
+	the group <em class="rfc2119">should</em> move on.</p>
+    <p>Groups <em class="rfc2119">should</em> favor proposals that create the weakest objections.
+	This is preferred over proposals that are supported by a large majority
+	but that cause strong objections from a few people.
+	As part of making a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent①">dissent</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②①">Chair</a> is expected to be aware of which participants work for the same
+	(or <a href="#MemberRelated">related</a>)
+	Member organizations and weigh their input accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Dissenters can escalate their sustained objection to a decision by registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑤">Formal Objection</a>.</p>
+    <h4 class="heading settled" data-level="5.2.3" id="Votes"><span class="secno">5.2.3. </span><span class="content"> Deciding by Vote</span><a class="self-link" href="#Votes"></a></h4>
+    <p>A group <em class="rfc2119">should</em> only conduct a vote to resolve a <em>substantive issue</em> after the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②②">Chair</a> has determined that all available means of <a href="#Consensus">reaching consensus</a> through technical discussion and compromise have failed,
+	and that a vote is necessary to break a deadlock.
+	In this case the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②③">Chair</a> <em class="rfc2119">must</em> record
+	(e.g., in the <a data-link-type="dfn" href="#minutes" id="ref-for-minutes②">minutes</a> of the meeting or in an archived email message):</p>
+    <ul>
+     <li> an explanation of the issue being voted on; 
+     <li> the decision to conduct a vote
+			(e.g., a simple majority vote) to resolve the issue; 
+     <li> the outcome of the vote; 
+     <li> any Formal Objections. 
+    </ul>
+    <p>In order to vote to resolve a substantive issue,
+	an individual <em class="rfc2119">must</em> be a group <a data-link-type="dfn" href="#participant" id="ref-for-participant①">participant</a>.
+	Each organization represented in the group <em class="rfc2119">must</em> have at most one vote,
+	even when the organization is represented by several participants in the group
+	(including Invited Experts).
+	For the purposes of voting:</p>
+    <ul>
+     <li> A Member or group of <a href="#MemberRelated">related Members</a> is considered a single organization. 
+     <li> The <a href="#Team">Team</a> is considered an organization. 
+    </ul>
+    <p>Unless the charter states otherwise, <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">may</em> vote.</p>
+    <p>If a participant is unable to attend a vote,
+	that individual <em class="rfc2119">may</em> authorize anyone at the meeting
+	to act as a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proxy">proxy</dfn>.
+	The absent participant <em class="rfc2119">must</em> inform the Chair in writing
+	who is acting as proxy, with written instructions on the use of the proxy.
+	For a Working Group or Interest Group,
+	see the related requirements regarding an individual
+	who attends a meeting as a <a href="#mtg-substitute" id="ref-for-mtg-substitute">substitute</a> for a participant.</p>
+    <p>A group <em class="rfc2119">may</em> vote for other purposes than to resolve a substantive issue.
+	For instance, the Chair often conducts a “straw poll” vote
+	as a means of determining whether there is consensus about a potential decision.</p>
+    <p>A group <em class="rfc2119">may</em> also vote to make a process decision.
+	For example,
+	it is appropriate to decide by simple majority
+	whether to hold a meeting in San Francisco or San Jose
+	(there’s not much difference geographically).
+	When simple majority votes are used to decide minor issues,
+	voters are <em class="rfc2119">not required</em> to state the reasons for votes,
+	and the group is <em class="rfc2119">not required</em> to record individual votes.</p>
+    <p>A group charter <em class="rfc2119">may</em> include formal voting procedures
+	(e.g., quorum or threshold requirements)
+	for making decisions about substantive issues.</p>
+    <h3 class="heading settled" data-level="5.3" id="formal-address"><span class="secno">5.3. </span><span class="content"> Formally Addressing an Issue</span><a class="self-link" href="#formal-address"></a></h3>
+    <p>In the context of this document,
+	a group has <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="formally-addressed">formally addressed</dfn> an issue when it has sent a public, substantive response
+	to the reviewer who raised the issue.
+	A substantive response is expected to include rationale for decisions
+	(e.g., a technical explanation, a pointer to charter scope, or a pointer to a requirements document).
+	The adequacy of a response is measured
+	against what a W3C reviewer would generally consider to be technically sound.
+	If a group believes that a reviewer’s comments result from a misunderstanding,
+	the group <em class="rfc2119">should</em> seek clarification before reaching a decision.</p>
+    <p>As a courtesy,
+	both Chairs and reviewers <em class="rfc2119">should</em> set expectations
+	for the schedule of responses and acknowledgments.
+	The group <em class="rfc2119">should</em> reply to a reviewer’s initial comments
+	in a timely manner.
+	The group <em class="rfc2119">should</em> set a time limit
+	for acknowledgment by a reviewer of the group’s substantive response;
+	a reviewer cannot block a group’s progress.
+	It is common for a reviewer to require a week or more
+	to acknowledge and comment on a substantive response.
+	The group’s responsibility to respond to reviewers
+	does not end once a reasonable amount of time has elapsed.
+	However, reviewers <em class="rfc2119">should</em> realize
+	that their comments will carry less weight
+	if not sent to the group in a timely manner.</p>
+    <p>Substantive responses <em class="rfc2119">should</em> be recorded.
+	The group <em class="rfc2119">should</em> maintain an accurate summary
+	of all substantive issues and responses to them
+	(e.g., in the form of an issues list with links to mailing list archives).</p>
+    <h3 class="heading settled" data-level="5.4" id="WGChairReopen"><span class="secno">5.4. </span><span class="content"> Reopening a Decision When Presented With New Information</span><a class="self-link" href="#WGChairReopen"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②④">Chair</a> <em class="rfc2119">may</em> reopen a decision
+	when presented with new information, including:</p>
+    <ul>
+     <li> additional technical information, 
+     <li> comments by email from participants who were unable to attend a scheduled meeting, 
+     <li> comments by email from meeting attendees
+			who chose not to speak out during a meeting
+			(e.g., so they could confer later with colleagues or for cultural reasons). 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑤">Chair</a> <em class="rfc2119">should</em> record
+	that a decision has been reopened,
+	and <em class="rfc2119">must</em> do so upon request from a group participant.</p>
+    <h3 class="heading settled" data-level="5.5" id="registering-objections"><span class="secno">5.5. </span><span class="content"> Registering Formal Objections</span><span id="WGArchiveMinorityViews"></span><span id="WGAppeals"></span><span id="wg-decision-appeal"></span><span id="chair-decision-appeal"></span><a class="self-link" href="#registering-objections"></a></h3>
+    <p>Any individual
+	(regardless of whether they are associated with a Member) <em class="rfc2119">may</em> appeal any decision made in connection with this Process
+	(except those having a different appeal process)
+	by registering a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="FormalObjection">Formal Objection</dfn> with the <a data-link-type="dfn" href="#team" id="ref-for-team④⑦">Team</a>.
+	Group participants <em class="rfc2119">should</em> inform
+	their <a href="#TeamContact" id="ref-for-TeamContact⑧">Team Contact</a> as well as the group’s Chair(s).
+	The Team Contact <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑦">CEO</a> when a group participant has also raised concerns about due process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> In this document, the term <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑥">Formal Objection</a> is used to emphasize this process implication:
+	Formal Objections receive formal consideration and a formal response.
+	The word “objection” used alone has its ordinary English connotations.
+	See <a href="#consensus-building">§ 5.2 Consensus Building</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑦">Formal Objection</a> <em class="rfc2119">must</em> include a summary of
+	the issue (whether technical or procedural),
+	the decision being appealed,
+	and the rationale for the objection.
+	It <em class="rfc2119">should</em> cite technical arguments
+	and propose changes that would remove the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑧">Formal Objection</a>;
+	these proposals <em class="rfc2119">may</em> be vague or incomplete. <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑨">Formal Objections</a> that do not provide substantive arguments
+	or rationale are unlikely to receive serious consideration.
+	Counter-arguments,
+	rationales,
+	and decisions <em class="rfc2119">should</em> also be recorded.</p>
+    <p>A record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⓪">Formal Objection</a> against a decision regarding a publicly-available document <em class="rfc2119">must</em> be made <a href="#confidentiality-change">publicly available</a>;
+	likewise, a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①①">Formal Objection</a> against a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①">Member-visible</a> decision <em class="rfc2119">must</em> be made <a href="#confidentiality-change">available to Members</a>.
+	A Call for Review to the Advisory Committee <em class="rfc2119">must</em> identify any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①②">Formal Objections</a> related to that review.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①③">Formal Objections</a> against matter in a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①">technical report</a> are required to be addressed before <a href="#rec-advance">requesting advancement</a> of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②">technical report</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①④">Formal Objection</a> filed during an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review④">Advisory Committee Review</a> is considered registered at the close of the review period.</p>
+    <h3 class="heading settled" data-level="5.6" id="addressing-fo"><span class="secno">5.6. </span><span class="content"> Addressing Formal Objections</span><a class="self-link" href="#addressing-fo"></a></h3>
+    <h4 class="heading settled" data-level="5.6.1" id="team-fo-mediation"><span class="secno">5.6.1. </span><span class="content"> Investigation and Mediation by the Team</span><a class="self-link" href="#team-fo-mediation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④⑧">Team</a> considers the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑤">Formal objection</a>,
+	researches the question,
+	interviews parties,
+	and so on,
+	to make sure the problem and the various viewpoints are well understood,
+	and to the extent possible,
+	to arrive at a recommended disposition.
+	If the <a data-link-type="dfn" href="#team" id="ref-for-team④⑨">Team</a> can resolve the issue
+	to the satisfaction of the individual that filed the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑥">Formal Objection</a>,
+	the individual withdraws the objection and the disposition process terminates.</p>
+    <p>Otherwise,
+	upon concluding that consensus cannot be found,
+	and no later than 90 days after the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑦">Formal Objection</a> being registered,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⓪">Team</a> <em class="rfc2119">must</em> initiate formation of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③">W3C Council</a>,
+	which should be <a href="#council-convention">convened</a> within 45 days of being initiated.
+	Concurrently, it must prepare a report for the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council④">Council</a> documenting its findings and attempts to find consensus.</p>
+    <h4 class="heading settled" data-level="5.6.2" id="council"><span class="secno">5.6.2. </span><span class="content"> W3C Council</span><a class="self-link" href="#council"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-local-lt="Council" id="w3c-council">W3C Council</dfn> is the body convened to resolve <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑧">Formal Objections</a> by combining the capabilities and perspectives of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑤">AB</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⓪">TAG</a>, and the <a data-link-type="dfn" href="#team" id="ref-for-team⑤①">Team</a>,
+	and is tasked with doing so in the best interests of the Web and W3C.</p>
+    <h5 class="heading settled" data-level="5.6.2.1" id="council-composition"><span class="secno">5.6.2.1. </span><span class="content"> Council Composition</span><a class="self-link" href="#council-composition"></a></h5>
+    <p>Each <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑤">W3C Council</a> is composed of the following members (excepting any <a href="#council-participation">renounced or dismissed</a>):</p>
+    <ul>
+     <li data-md>
+      <p>the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑧">CEO</a> or their chosen <a data-link-type="dfn" href="#team" id="ref-for-team⑤②">Team</a> delegate</p>
+     <li data-md>
+      <p>the members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑥">Advisory Board</a></p>
+     <li data-md>
+      <p>the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③①">Technical Architecture Group</a></p>
+    </ul>
+    <p>Participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑥">W3C Council</a> <em class="rfc2119">must not</em> require attendance of <a data-link-type="dfn" href="#ftf-meeting" id="ref-for-ftf-meeting③">face-to-face meetings</a>.</p>
+    <p>A distinct instance of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑦">W3C Council</a> is convened for each decision being appealed or objected to.
+	Membership of each <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑧">Council</a> instance is fixed at formation,
+	and is not changed by any <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑦">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③②">TAG</a> elections
+	occurring before that Council has reached a conclusion.
+	However, if participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑨">Council</a> falls so low as to hinder effective and balanced deliberations,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair">W3C Council Chair</a> <em class="rfc2119">should</em> dissolve the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⓪">Council</a> and call for a new one to be convened.</p>
+    <p>A <a data-link-type="dfn" href="#team" id="ref-for-team⑤③">Team</a> member is assigned
+	to act as the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-team-contact">Council Team Contact</dfn>,
+	to support this Council
+	and to facilitate adherence to this Process.</p>
+    <h5 class="heading settled" data-level="5.6.2.2" id="council-delegation"><span class="secno">5.6.2.2. </span><span class="content"> Extraordinary Delegation</span><a class="self-link" href="#council-delegation"></a></h5>
+    <p>In extraordinary cases,
+	if they feel a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①①">Council</a> would not be the appropriate deciding body,
+	a member of the <a data-link-type="dfn" href="#team" id="ref-for-team⑤④">Team</a> (particularly the Legal Counsel) or
+	any potential Council member
+	may suggest that the decision for that specific Formal Objection be delegated
+	to the W3C Board of Directors,
+	to an officer of its corporation (such as the Legal Counsel),
+	or to one or more specific individuals from the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑤">Team</a>.
+	The potential Council members then <em class="rfc2119">may</em> confidentially discuss
+	and <em class="rfc2119">must</em> vote
+	whether to delegate the decision for that specific <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑨">Formal Objection</a>.
+	A decision to delegate <em class="rfc2119">must</em> be supported by a two-thirds supermajority vote
+	(i.e., at least twice as many votes in favor as against).
+	Delegation in such cases cannot be later revoked.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑥">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①③">Advisory Committee</a> when a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⓪">Formal Objection</a> has been delegated,
+	and to whom it has been delegated.</p>
+    <h5 class="heading settled" data-level="5.6.2.3" id="council-participation"><span class="secno">5.6.2.3. </span><span class="content"> Council Participation, Dismissal, and Renunciation</span><a class="self-link" href="#council-participation"></a></h5>
+    <p>A potential Council member may be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="dismissed | dismiss | dismissal" data-noexport id="dismissed">dismissed</dfn> from the Council.
+	In order to apply consistent criteria,
+	the potential Council members decide collectively
+	which reasons against service
+	rise to a sufficient level for a potential member to be <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed">dismissed</a>.
+	No-one is automatically dismissed,
+	and individual recusal is not used in the Council. <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed①">Dismissal</a> applies to an individual person in the context of a specific Council,
+	and should be used rarely in order to preserve the greatest diversity on the Council.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> A W3C Council is a deliberative body whose purpose is
+	to find the best way forward for the Web and for W3C.
+	It is not a judicial body tasked with determining right or wrong.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑦">Team</a> <em class="rfc2119">must</em> draft a list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①②">Council</a> members,
+	with annotations of possible reasons for dismissal against each one.
+	The W3C community,
+	including members and team, and potential council members, <em class="rfc2119">must</em> be given an opportunity to contribute possible reasons to this list.
+	Affected members <em class="rfc2119">must</em> be given
+	an opportunity to respond to such comments about themselves.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑧">Team</a> may report comments verbatim
+	or may paraphrase them while preserving their intent;
+	they may also elide inappropriate comments,
+	such as any that violate applicable laws or the <a data-link-type="biblio" href="#biblio-cepc" title="W3C Code of Ethics and Professional Conduct">[CEPC]</a>.</p>
+    <p>Before a Council forms,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑨">Team</a> presents the entire list of potential members
+	and collected reasons and responses
+	to the potential Council members,
+	who then consider for each potential member
+	whether that individual’s participation
+	would compromise the integrity of the Council decision,
+	and vote whether to dismiss that potential member.
+	No one is allowed to vote on their own dismissal;
+	each dismissal is decided by simple majority of those not abstaining.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since dismissal is individual,
+	when the decision being objected to was made by the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③③">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑧">AB</a> acting as a body,
+	the entire <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③④">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑨">AB</a> is not expected or required to be dismissed.</p>
+    <p>An individual <em class="rfc2119">may</em> also <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="renounce | renunciation" data-noexport id="renounce">renounce</dfn> their seat on a Council, for strong reason,
+	such as being forbidden by their employer to serve. The individual chooses the extent to which they explain
+	their renunciation.
+	Renunciation is disqualification from participation,
+	not abstention,
+	and <em class="rfc2119">should not</em> be used
+	to excuse an absence of participation.</p>
+    <p>Any person who has been <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed②">dismissed</a> or who <a data-link-type="dfn" href="#renounce" id="ref-for-renounce">renounces</a> their seat
+	does not receive <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①③">Council</a> materials,
+	take part in its deliberations,
+	help in the determination of consensus,
+	or vote.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①④">W3C Council</a> <em class="rfc2110">may</em> still solicit and hear their testimony,
+	as they can of anyone else in the W3C community.</p>
+    <h5 class="heading settled" data-level="5.6.2.4" id="council-short-circuit"><span class="secno">5.6.2.4. </span><span class="content"> Unanimous Short Circuit</span><a class="self-link" href="#council-short-circuit"></a></h5>
+    <p>The full Council process <em class="rfc2119">may</em> be short-circuited if
+	the Team recommends a resolution
+	and every potential member of a Council who is not renouncing their seat
+	votes affirmatively (no abstentions) to adopt this resolution.</p>
+    <p>This step <em class="rfc2119">may</em> be run concurrently with <a href="#council-participation">§ 5.6.2.3 Council Participation, Dismissal, and Renunciation</a> and prior to choosing a <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair①">Chair</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This is intended for exceptional cases
+	that don’t seem to warrant a full Council response
+	because they are, for instance, too trivial, duplicative, etc.</p>
+    <h5 class="heading settled" data-level="5.6.2.5" id="council-chairing"><span class="secno">5.6.2.5. </span><span class="content"> Council Chairing</span><a class="self-link" href="#council-chairing"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Council Chair" data-noexport id="w3c-council-chair">Chair</dfn> of each W3C Council is chosen by its members,
+	by consensus if possible,
+	falling back to a vote if that fails.
+	The chair must be a member of that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑤">W3C Council</a>.
+	Chair selection happens during formation of each Council,
+	and <em class="rfc2119">must</em> be re-run
+	if requested by the <a data-link-type="dfn" href="#council-team-contact" id="ref-for-council-team-contact">Council Team Contact</a> or by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑥">Chair</a> during the Council’s operation.</p>
+    <h5 class="heading settled" data-level="5.6.2.6" id="council-deliberations"><span class="secno">5.6.2.6. </span><span class="content"> Council Deliberations</span><a class="self-link" href="#council-deliberations"></a></h5>
+    <p id="council-convention"> Upon appointment of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair②">W3C Council Chair</a> and delivery of the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⓪">Team</a>’s report,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑥">W3C Council</a> is considered to be convened
+	and can start deliberations. </p>
+    <p>Having reviewed the information gathered by the <a data-link-type="dfn" href="#team" id="ref-for-team⑥①">Team</a>,
+	the Council <em class="rfc2119">may</em> conduct additional research or analysis,
+	or request additional information or interviews from anyone,
+	including the Team.</p>
+    <p id="broker-consensus"> The Council <em class="rfc2119">may</em> further attempt to broker consensus,
+	which, if successful, disposes the formal objection. </p>
+    <p>Otherwise,
+	after sufficient deliberation,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑦">W3C Council</a> decides whether to <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="uphold | upholds | upheld | upholding" data-noexport id="uphold">uphold</dfn> or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="overrule">overrule</dfn> the objection.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑧">W3C Council</a> <em class="rfc2119">may</em> <a data-link-type="dfn" href="#overrule" id="ref-for-overrule">overrule</a> the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②①">Formal Objection</a> even if it agrees with some of the supportive arguments.</p>
+    <p id="fo-mitigations"> When <a data-link-type="dfn" href="#uphold" id="ref-for-uphold">upholding</a> an objection,
+	it <em class="rfc2199">should</em> recommend a way forward.
+	If the overturned decision has already had consequences
+	(e.g., if the objection concerns material already in a published document)
+	the Council <em class="rfc2119">should</em> suggest how these consequences might be mitigated.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑥②">Team</a> is responsible for making sure that adequate mitigations are enacted in a timely fashion;
+	and the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②②">Formal Objection</a> is not considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fully-addressed">fully addressed</dfn> until then. </p>
+    <p class="note" role="note"><span class="marker">Note:</span> This does not create new powers for the <a data-link-type="dfn" href="#team" id="ref-for-team⑥③">Team</a>,
+	such as the ability to “unpublish” documents.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑥④">Team</a>'s role is to ensure the responsible parties enact adequate mitigations,
+	by whatever means they already have at their disposal.</p>
+    <p>A Council <em class="rfc2119">may</em> form sub-groups for deliberation,
+	who may return with a recommendation,
+	but the full Council issues the final decision.
+	The decision of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑨">W3C Council</a> <em class="rfc2119">should</em> be unanimous,
+	and <em class="rfc2119">may</em> be issued under consensus.
+	However, if despite careful deliberation
+	a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⓪">W3C Council</a> is unable to reach consensus,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair③">W3C Council Chair</a> may instead resort to voting.
+	In that case,
+	the decision is made by simple majority,
+	with the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair④">W3C Council Chair</a> breaking any tie.
+	In case of a vote,
+	if two members of a Council who share the same affiliation cast an identical ballot,
+	then their ballots count as a one vote,
+	not two.</p>
+    <p>In the case of non-unanimous decisions,
+	members of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②①">W3C Council</a> who disagree with the decision <em class="rfc2119">may</em> write a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minority-opinion">Minority Opinion</dfn> explaining the reason for their disagreement.</p>
+    <p>The deliberations of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②②">W3C Council</a> are confidential to that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②③">W3C Council</a> and its <a data-link-type="dfn" href="#council-team-contact" id="ref-for-council-team-contact①">Council Team Contact</a>.</p>
+    <p>If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②④">W3C Council</a> is unable to come to a conclusion within 45 days of being <a href="#council-convention">convened</a>,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑤">W3C Council Chair</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①④">AC</a> of this delay
+	and of the status of the discussions.
+	The <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑥">W3C Council Chair</a> <em class="rfc2119">may</em> additionally make this report <a href="#confidentiality-levels">public</a>.</p>
+    <h5 class="heading settled" data-level="5.6.2.7" id="council-decision"><span class="secno">5.6.2.7. </span><span class="content"> Council Decision Report</span><a class="self-link" href="#council-decision"></a></h5>
+    <p>A <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑤">Council</a> terminates by issuing a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-report">Council Report</dfn>,
+	which:</p>
+    <ul>
+     <li data-md>
+      <p><em class="rfc2119">must</em> state whether the Council <a data-link-type="dfn" href="#uphold" id="ref-for-uphold①">upholds</a> or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule①">overrules</a> the objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> provide a rationale supporting the decision,
+which <em class="rfc2119">should</em> address each argument raised in the Formal Objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include any recommendation decided by the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑥">Council</a>.</p>
+     <li data-md>
+      <p>if the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②③">Formal Objection</a> has been upheld, <em class="rfc2119">should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include the <a data-link-type="dfn" href="#minority-opinion" id="ref-for-minority-opinion">Minority Opinion</a>(s), if any.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of those who were <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed③">dismissed</a> or <a data-link-type="dfn" href="#renounce" id="ref-for-renounce①">renounced</a> their seat as well as those who were qualified to serve.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of the individuals who participated in the final decision.</p>
+     <li data-md>
+      <p><em class="rfc2119">may</em> report vote totals, if any vote was held.</p>
+     <li data-md>
+      <p><em class="rfc2119">must not</em> attribute any position to any individual on the Council.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑤">Team</a> <em class="rfc2119">must</em> maintain a <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/about/council/">public page on the W3C website</a> indexing all completed <a data-link-type="dfn" href="#council-report" id="ref-for-council-report">Council Reports</a>.
+	If a Council decision is later overturned by an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal">AC Appeal</a>,
+	this <em class="rfc2119">must</em> also be mentioned. <a data-link-type="dfn" href="#council-report" id="ref-for-council-report①">Council Reports</a> <em class="rfc2119">must</em> be no more confidential
+	than the decision or document being objected to.</p>
+    <p>The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑦">Council</a> <em class="rfc2119">may</em> also issue a <dfn data-dfn-type="dfn" data-export id="supplemental-confidential-council-report">Supplemental Confidential Council Report<a class="self-link" href="#supplemental-confidential-council-report"></a></dfn> with a more restricted <a href="#confidentiality-levels">level of confidentiality</a> than its main report
+	when it believes that additional commentary on confidential aspects of the case
+	would be informative.
+	However, the main <a data-link-type="dfn" href="#council-report" id="ref-for-council-report②">Council Report</a> <em class="rfc2119">should</em> be self-sufficient
+	and understandable without reference to Supplemental Confidential Council Reports.</p>
+    <h5 class="heading settled" data-level="5.6.2.8" id="council-appeals"><span class="secno">5.6.2.8. </span><span class="content"> Appealing Council Decisions</span><a class="self-link" href="#council-appeals"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①③">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①">Advisory Committee Appeal</a> of a Council decision issued in a <a data-link-type="dfn" href="#council-report" id="ref-for-council-report③">Council Report</a>.</p>
+    <h3 class="heading settled" data-level="5.7" id="ACReview"><span class="secno">5.7. </span><span class="content"> Advisory Committee Reviews</span><a class="self-link" href="#ACReview"></a></h3>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee review | AC Review" id="advisory-committee-review"> Advisory Committee review</dfn> is the process
+	by which the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑤">Advisory Committee</a> formally confers its approval
+	on <a data-link-type="dfn" href="#charter" id="ref-for-charter②">charters</a>, <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③">technical reports</a>,
+	and other matters.</p>
+    <h4 class="heading settled" data-level="5.7.1" id="ACReviewStart"><span class="secno">5.7.1. </span><span class="content"> Start of a Review Period</span><a class="self-link" href="#ACReviewStart"></a></h4>
+    <p>Each <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑤">Advisory Committee review</a> period
+	begins with a Call for Review from the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑥">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑥">Advisory Committee</a>.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="reviewform">Call for Review</dfn> describes the proposal,
+	raises attention to deadlines,
+	estimates when the decision will be available,
+	and includes other practical information.
+	Each Member organization <em class="rfc2119">may</em> send one review,
+	which <em class="rfc2119">must</em> be returned by its <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①④">Advisory Committee representative</a>.</p>
+    <p>For clarity,
+	in the context of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑥">AC Review</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent②">dissent</a> <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②④">Formal Objection</a>.</p>
+    <p>The Team <em class="rfc2119">must</em> provide two channels for Advisory Committee review comments:</p>
+    <ol>
+     <li> an archived <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑦">Team-only</a> channel; 
+     <li> an archived <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only②">Member-only</a> channel. 
+    </ol>
+    <p>The <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform">Call for Review</a> <em class="rfc2119">must</em> specify
+	which channel is the default for review comments on that Call.</p>
+    <p>Reviewers <em class="rfc2119">may</em> send information
+	to either or both channels.
+	A reviewer <em class="rfc2119">may</em> also share their own reviews
+	with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>,
+	and <em class="rfc2119">may</em> also make it available to the public.</p>
+    <p>A Member organization <em class="rfc2119">may</em> modify its review
+	during a review period
+	(e.g., in light of comments from other Members).</p>
+    <h4 class="heading settled" data-level="5.7.2" id="ACReviewAfter"><span class="secno">5.7.2. </span><span class="content"> After the Review Period</span><a class="self-link" href="#ACReviewAfter"></a></h4>
+    <p>After the review period,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑦">Team</a> determines the appropriate <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision③">W3C Decision</a>,
+	which they <em class="rfc2119">must</em> announce to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑦">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate
+	the level of support for the proposal
+	(<a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus③">consensus</a> or <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent③">dissent</a>),
+	and specifically
+	whether there were any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑤">Formal Objections</a>,
+	with attention to <a href="#confidentiality-change">changing the confidentiality level</a> of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑥">Formal Objections</a>.</p>
+    <p>If there were <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑦">Formal Objections</a>, at least some of which were <a data-link-type="dfn" href="#uphold" id="ref-for-uphold②">upheld</a>,
+	or if there is not <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus④">consensus</a> because of insufficient support, <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision④">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to improve the proposal. 
+     <li> The proposal is rejected. 
+    </ul>
+    <p>If the proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑤">consensus</a>,
+	or if any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑧">Formal Objections</a> are retracted or overruled
+	and the proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑥">consensus</a>,
+	this <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑤">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is adopted,
+			possibly with additional changes integrated
+			in order to address the comments of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑧">AC</a> (see below). 
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to make desirable changes identified during the review
+			and to resubmit. 
+    </ul>
+    <p>If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>,
+	then those changes <em class="rfc2119">must</em> be announced to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑨">AC</a> and to the <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group②">Group</a> that owns the document (if any).</p>
+    <p>Additionally, when adopting a proposal with <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change">substantive changes</a> integrated,
+	the announcement <em class="rfc2119">must</em> include rationale
+	for the substantive changes,
+	and those changes must have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑦">consensus</a> of the subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⓪">AC</a> that voted on the proposal
+	(including anyone who explicitly abstained).
+	For publications which have conditions in addition to <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②①">AC</a> approval
+	for introducing <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①">substantive changes</a> (such as <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group③">Group</a> consensus or implementation experience),
+	those other conditions must also be re-fulfilled.</p>
+    <div class="example" id="example-978a60c7"><a class="self-link" href="#example-978a60c7"></a> For example, to make <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change②">substantive changes</a> to a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①④">Proposed Recommendations</a>,
+		the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④">technical report</a> could be returned to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR">Candidate Recommendation</a>.
+		Alternatively, the desired changes can be introduced as non-substantive amendments
+		using the process for <a href="#revising-rec">revising a Recommendation</a>.
+		However, they cannot be directly integrated between <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①">PR</a> and <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①">REC</a>,
+		because that would fail to trigger a patent exclusion opportunity. </div>
+    <p>This document does not specify
+	time intervals between the end of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑦">Advisory Committee review</a> period
+	and the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑥">W3C decision</a>.
+	This is to ensure that the Members and <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑧">Team</a> have sufficient time to consider comments
+	gathered during the review.
+	The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②②">Advisory Committee</a> <em class="rfc2119">should not</em> expect an announcement
+	sooner than <span class="time-interval">two weeks</span> after the end of a review period.
+	If, after <span class="time-interval">three weeks</span>, the outcome has not been announced,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑨">Team</a> <em class="rfc2119">should</em> provide the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②③">Advisory Committee</a> with an update.</p>
+    <h3 class="heading settled" data-level="5.8" id="ACVotes"><span class="secno">5.8. </span><span class="content"> Advisory Committee Votes</span><a class="self-link" href="#ACVotes"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②④">Advisory Committee</a> votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>,
+	and in the event of an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal②">Advisory Committee Appeal</a> achieving the required support to trigger an appeal vote.
+	Whenever the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑤">Advisory Committee</a> votes,
+	each Member or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member③">related Members</a> has one vote.</p>
+    <h3 class="heading settled" data-level="5.9" id="ACAppeal"><span class="secno">5.9. </span><span class="content"> Appeal by Advisory Committee Representatives</span><a class="self-link" href="#ACAppeal"></a></h3>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑤">Advisory Committee representatives</a> <em class="rfc2119">may</em> appeal certain decisions,
+	though appeals are only expected to occur in extraordinary circumstances.</p>
+    <p>When a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑦">W3C decision</a> is made following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑧">Advisory Committee review</a>, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑥">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee Appeal|AC Appeal| Appeal" id="advisory-committee-appeal">Advisory Committee Appeal</dfn>.
+	These <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑧">W3C decisions</a> include those related to group creation and modification,
+	and transitions to new maturity stages for Recommendation Track documents
+	and the Process document.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑦">Advisory Committee representatives</a> <em class="rfc2119">may</em> also initiate an appeal
+	for decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑧">W3C Council</a>, and
+	for certain decisions that do not involve an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑨">Advisory Committee review</a>.
+	These cases are identified in the sections
+	which describe the requirements for the decision
+	and include
+	additional (non-reviewed) maturity stages of Recommendation Track documents,
+	group <a data-link-type="dfn" href="#dfn-charter-extension" id="ref-for-dfn-charter-extension">charter extensions</a> and closures,
+	and <a data-link-type="dfn">Memoranda of Understanding</a>.</p>
+    <p>In all cases,
+	an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal③">appeal</a> <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the decision.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑧">Advisory Committee representative</a> initiates an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal④">appeal</a> by sending a request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⓪">Team</a>,
+	and should also share this request with the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑥">Advisory Committee</a>.
+	The request should say “I appeal this Decision”
+	and identify the decision,
+	and may also include their rationale for appealing the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/Guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a> for a recommendation
+	on how to communicate an appeal request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑦①">Team</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑦">AC</a>.</p>
+    <p>Within one week the <a data-link-type="dfn" href="#team" id="ref-for-team⑦②">Team</a> <em class="rfc2119">must</em> announce the appeal process
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑧">Advisory Committee</a> and provide a mechanism for <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑨">Advisory Committee representatives</a> to respond with a statement of positive support for this appeal.
+	The archive of these statements <em class="rfc2119">must</em> be <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only③">member-only</a>.
+	If, within <span class="time-interval">one week</span> of the Team’s announcement,
+	5% or more of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑨">Advisory Committee</a> support the appeal request,
+	the Team <em class="rfc2119">must</em> organize an appeal vote
+	asking the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⓪">Advisory Committee</a> “Do you approve of the Decision?”
+	together with links to the decision and the appeal support.</p>
+    <p>The ballot <em class="rfc2119">must</em> allow for three possible responses:
+	“Approve”,
+	“Reject”,
+	and “Abstain”,
+	together with Comments.</p>
+    <p>If the number of votes to reject
+	exceeds the number of votes to approve,
+	the decision is overturned.
+	In that case, there are the following possible next steps:</p>
+    <ol>
+     <li> The proposal is rejected. 
+     <li> The proposal is returned for additional work,
+			after which the applicable decision process is re-initiated. 
+    </ol>
+    <h2 class="heading settled" data-level="6" id="Reports"><span class="secno">6. </span><span class="content"> W3C Technical Reports</span><a class="self-link" href="#Reports"></a></h2>
+    <p>The W3C technical report development process is the set of steps and requirements
+	followed by W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①③">Working Groups</a> to standardize Web technology.
+	The W3C technical report development process is designed to:</p>
+    <ul>
+     <li> support multiple specification development methodologies 
+     <li> maximize <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑧">consensus</a> about the content of stable technical reports 
+     <li> ensure high technical and editorial quality 
+     <li> promote consistency among specifications 
+     <li> facilitate royalty-free, interoperable implementations of Web Standards, and 
+     <li> earn endorsement by W3C and the broader community. 
+    </ul>
+    <p>See also “licensing goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.1" id="recs-and-notes"><span class="secno">6.1. </span><span class="content"> Types of Technical Reports</span><a class="self-link" href="#recs-and-notes"></a></h3>
+    <p>This chapter describes the formal requirements
+	for <a data-link-type="dfn" href="#publishing" id="ref-for-publishing">publishing</a> and maintaining a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②">W3C Recommendation</a>, <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②②">Note</a>,
+	or <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report">Registry Report</a>.</p>
+    <dl>
+     <dt>Recommendations 
+     <dd> <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①④">Working Groups</a> develop technical reports on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track">W3C Recommendation Track</a> in order to produce normative specifications or guidelines
+			as standards for the Web.
+			The <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①">Recommendation Track</a> process incorporates requirements for <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review">wide review</a>, <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation">adequate implementation experience</a>,
+			and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑨">consensus</a>-building,
+			and is subject to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			under which participants commit to Royalty-Free IPR licenses for implementations.
+			See <a href="#rec-track">§ 6.3 The W3C Recommendation Track</a> for details. 
+     <dt>Notes 
+     <dd> Groups can also publish documents as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①">W3C Notes</a> and <a data-link-type="dfn" href="#statement" id="ref-for-statement">W3C Statements</a>,
+			typically either to document information
+			other than technical specifications,
+			such as use cases motivating a specification
+			and best practices for its use.
+			See <a href="#note-track">§ 6.4 The Note Track (Notes and Statements)</a> for details. 
+     <dt>Registries 
+     <dd> <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑤">Working Groups</a> can also publish <a data-link-type="dfn" href="#registry" id="ref-for-registry">registries</a> in order to document collections of values or other data.
+			These are typically published in a separate <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report①">registry report</a>,
+			although they can also be directly embedded in <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track②">Recommendation Track</a> documents
+			as a <a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section">registry section</a>. <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition">Defining a registry</a> requires <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①">wide review</a> and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⓪">consensus</a>,
+			but once set up, changes to registry entries are lightweight
+			and can even be done without a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑥">Working Group</a>.
+			See <a href="#registries">§ 6.5 The Registry Track</a> for details. 
+    </dl>
+    <p>Individual <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑦">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑦">Interest Groups</a> <em class="rfc2119">should</em> adopt additional processes
+	for developing publications,
+	so long as they do not conflict with the requirements in this chapter.</p>
+    <h3 class="heading settled" data-level="6.2" id="general-requirements"><span class="secno">6.2. </span><span class="content"> General Requirements for Technical Reports</span><a class="self-link" href="#general-requirements"></a></h3>
+    <h4 class="heading settled" data-level="6.2.1" id="publication"><span class="secno">6.2.1. </span><span class="content"> Publication of Technical Reports</span><a class="self-link" href="#publication"></a></h4>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="publish" data-noexport id="publishing">Publishing</dfn> as used in this document
+	refers to producing a version which is listed as a W3C <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="technical-report">Technical Report</dfn> on its <a href="https://www.w3.org/TR/">Technical Reports index at https://www.w3.org/TR</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a>.
+	Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public document.
+	W3C strives to make archival documents indefinitely available
+	at their original address in their original form.</p>
+    <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate its <a href="#maturity-stages">maturity stage</a>,
+	and <em class="rfc2119" id="DocumentStatus">must</em> include information about the status of the document.
+	This status information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> be unique each time a specification is <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①">published</a>, 
+     <li> <em class="rfc2119">must</em> state which <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑧">Working Group</a> developed the specification, 
+     <li> <em class="rfc2119">must</em> state how to send comments or file bugs,
+			and where these are recorded, 
+     <li> <em class="rfc2119">must</em> include expectations about next steps, 
+     <li> <em class="rfc2119">should</em> explain how the technology relates to existing international standards
+			and related work inside or outside W3C,
+			and 
+     <li> <em class="rfc2119">should</em> explain
+			or link to
+			an explanation of significant changes from the previous version. 
+    </ul>
+    <p>Every Technical Report published
+	as part of the Technical Report development process
+	is edited by one or more editors
+	appointed by a Group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑦">Chair</a>.
+	It is the responsibility of these editors to ensure that the decisions of the Group are
+	correctly reflected in subsequent drafts of the technical report.
+	An editor <em class="rfc2119">must</em> be a participant,
+	per <a href="#group-participation">§ 3.4.2 Participation in Chartered Groups</a> in the Group responsible for the document(s) they are editing.</p>
+    <p>The Team is <em class="rfc2119">not required</em> to publish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑤">Technical Report</a> that does not conform to the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules" title="Publication Rules">[PUBRULES]</a> (e.g., for <span id="DocumentName">naming</span>,
+	status information,
+	style,
+	and <span id="document-copyright">copyright requirements</span>).
+	These rules are subject to change by the Team from time to time.
+	The Team <em class="rfc2119">must</em> inform group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑧">Chairs</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③①">Advisory Committee</a> of any changes to these rules.</p>
+    <p>The primary language for W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑥">Technical Reports</a> is English.
+	W3C encourages the translation of its <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑦">Technical Reports</a>. <a href="https://www.w3.org/Consortium/Translation/">Information about translations of W3C technical reports</a> <a data-link-type="biblio" href="#biblio-translation" title="Translations of W3C technical reports">[TRANSLATION]</a> is available at the W3C website.</p>
+    <h4 class="heading settled" data-level="6.2.2" id="doc-reviews"><span class="secno">6.2.2. </span><span class="content"> Reviews and Review Responsibilities</span><a class="self-link" href="#doc-reviews"></a></h4>
+    <p>A document is available for review
+	from the moment it is first <a data-link-type="dfn" href="#publishing" id="ref-for-publishing②">published</a>.
+	Working Groups <em class="rfc2119">should</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed">formally address</a> <em>any</em> substantive review comment
+	about a technical report in a timely manner.</p>
+    <p>Reviewers <em class="rfc2119">should</em> send substantive technical reviews as early as possible. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑨">Working Groups</a> are often reluctant to make <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change③">substantive changes</a> to a mature document,
+	particularly if this would cause significant compatibility problems
+	due to existing implementation. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⓪">Working Groups</a> <em class="rfc2119">should</em> record substantive
+	or interesting proposals raised by reviews
+	but not incorporated into a current specification.</p>
+    <h5 class="heading settled" data-level="6.2.2.1" id="wide-review"><span class="secno">6.2.2.1. </span><span class="content"> Wide Review</span><a class="self-link" href="#wide-review"></a></h5>
+    <p>The requirements for <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="dfn-wide-review">wide review</dfn> are not precisely defined by the W3C Process.
+	The objective is to ensure that the entire set of stakeholders of the Web community,
+	including the general public,
+	have had adequate notice of the progress of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②①">Working Group</a> (for example through notices posted to <a href="https://lists.w3.org/Archives/Public/public-review-announce/">public-review-announce@w3.org</a>)
+	and were able to actually perform reviews of and provide comments on the specification.
+	A second objective is to encourage groups to request reviews
+	early enough that comments and suggested changes
+	can still be reasonably incorporated in response to the review.
+	Before approving transitions,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦③">Team</a> will consider who has been explicitly offered
+	a reasonable opportunity to review the document,
+	who has provided comments,
+	the record of requests to and responses from reviewers,
+	especially <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a> and groups identified as dependencies in the charter
+	or identified as <a href="https://www.w3.org/2001/11/StdLiaison.html">liaisons</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a>,
+	and seek evidence of clear communication to the general public
+	about appropriate times and which content to review
+	and whether such reviews actually occurred.</p>
+    <p>For example,
+	inviting review of new or significantly revised sections published in Working Drafts,
+	and tracking those comments
+	and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②②">Working Group</a>'s responses,
+	is generally a good practice which would often be considered positive evidence of wide review. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②③">Working Groups</a> <em class="rfc2119">should</em> follow the <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">W3C Horizontal Groups</a>’ review processes,
+	and <em class="rfc2119">should</em> announce to other W3C Working Groups
+	as well as the general public,
+	especially those affected by this specification,
+	a proposal to enter <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①">Candidate Recommendation</a> (for example in approximately 28 days).
+	By contrast a generic statement in a document
+	requesting review at any time
+	is likely not to be considered as sufficient evidence
+	that the group has solicited wide review.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②④">Working Group</a> could present evidence that wide review has been received,
+	irrespective of solicitation.
+	But it is important to note that receiving many detailed reviews
+	is not necessarily the same as wide review,
+	since they might only represent comment
+	from a small segment of the relevant stakeholder community.</p>
+    <h4 class="heading settled" data-level="6.2.3" id="correction-classes"><span class="secno">6.2.3. </span><span class="content"> Classes of Changes</span><a class="self-link" href="#correction-classes"></a></h4>
+    <p>This document distinguishes the following 5 classes of changes to a document.
+	The first two classes of change are considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="editorial change" data-noexport id="editorial-change">editorial changes</dfn>,
+	the next two <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="substantive change" data-noexport id="substantive-change">substantive changes</dfn>,
+	and the last one <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="registry change" data-noexport id="registry-change">registry changes</dfn>.</p>
+    <dl>
+     <dt id="class-1">
+      <a class="self-link" href="#class-1"></a> 
+      <ol>
+       <li data-md>
+        <p>No changes to text content</p>
+      </ol>
+     <dd> These changes include fixing broken links, style sheets, or invalid markup. 
+     <dt id="class-2">
+      <a class="self-link" href="#class-2"></a> 
+      <ol start="2">
+       <li data-md>
+        <p>Changes that do not functionally affect interpretation of the document</p>
+      </ol>
+     <dd> For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track③">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑧">technical reports</a> specifically,
+			this constitutes changes that do not affect conformance,
+			i.e. changes that reasonable implementers
+			would not interpret as changing architectural
+			or interoperability requirements
+			or their implementation.
+			Changes which resolve ambiguities in the specification
+			are considered to change (by clarification) the implementation requirements
+			and do not fall into this class. 
+     <dd> Examples of changes in this class include
+			correcting non-normative examples
+			which clearly conflict with normative requirements,
+			clarifying informative use cases or other non-normative text,
+			fixing typos or grammatical errors
+			where the change does not change requirements. 
+     <dd> If there is any doubt or disagreement
+			as to whether a change functionally affects interpretation,
+			that change does not fall into this class. 
+     <dt id="class-3">
+      <a class="self-link" href="#class-3"></a> 
+      <ol start="3">
+       <li data-md>
+        <p>Other changes that do not add new features</p>
+      </ol>
+     <dd>
+       For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track④">Recommendation-track</a> documents,
+			these changes <em class="rfc2119">may</em> affect conformance to the specification.
+			A change that affects conformance is one that: 
+      <ul>
+       <li> makes conforming data, processors, or other conforming agents become non-conforming according to the new version,
+					or 
+       <li> makes non-conforming data, processors, or other agents become conforming,
+					or 
+       <li> clears up an ambiguity or under-specified part of the specification
+					in such a way that data,
+					a processor,
+					or an agent
+					whose conformance was once unclear
+					becomes clearly either conforming or non-conforming. 
+      </ul>
+     <dt id="class-4">
+      <a class="self-link" href="#class-4"></a> 
+      <ol start="4">
+       <li data-md>
+        <p>New features</p>
+      </ol>
+     <dd> Changes that add new functionality,
+			such as new elements, new APIs, new rules, etc. 
+     <dt id="class-5">
+      <a class="self-link" href="#class-5"></a> 
+      <ol start="5">
+       <li data-md>
+        <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table">registry table</a></p>
+      </ol>
+     <dd> Changes that add, remove, or alter <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry">registry entries</a> in a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①">registry table</a>. 
+    </dl>
+    <h4 class="heading settled" data-level="6.2.4" id="errata"><span class="secno">6.2.4. </span><span class="content"> Errata Management</span><a class="self-link" href="#errata"></a></h4>
+    <p>Tracking errors is an important part of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑤">Working Group</a>'s ongoing care of a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑨">technical report</a>;
+	for this reason,
+	the scope of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑥">Working Group</a> charter generally allows time
+	for work after publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③">Recommendation</a>.
+	In this Process Document,
+	the term “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="erratum | errata" id="erratum">erratum</dfn>”
+	(plural “errata”) refers to any error
+	that can be resolved by one or more changes in classes 1-3
+	of section <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑦">Working Groups</a> <em class="rfc2119">must</em> keep
+	a public record of errors
+	that are reported by readers and implementers
+	for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④">Recommendations</a>.
+	Such error reports <em class="rfc2119">should</em> be compiled
+	no less frequently than quarterly.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑧">Working Groups</a> decide how to document errata.
+	Such documentation <em class="rfc2119">must</em> identify
+	the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⓪">technical report</a> text
+	and describe the error;
+	it <em class="rfc2119">may</em> also describe some possible solution(s).
+	Readers of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①①">technical report</a> <em class="rfc2119">should</em> be able easily
+	to find and see the errata
+	that apply to that specific <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①②">technical report</a> with their associated tests.
+	Errata <em class="rfc2119">may</em> be documented
+	in a separate errata page or tracking system.
+	They <em class="rfc2119">may</em>,
+	in addition or alternatively,
+	be annotated inline
+	alongside the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①③">technical report</a> text
+	or at the start or end of the most relevant section(s).</p>
+    <h4 class="heading settled" data-level="6.2.5" id="candidate-amendments"><span class="secno">6.2.5. </span><span class="content"> Candidate Amendments</span><span id="candidate-changes"></span><a class="self-link" href="#candidate-amendments"></a></h4>
+    <p>An <a data-link-type="dfn" href="#erratum" id="ref-for-erratum">erratum</a> <em class="rfc2119">may</em> be accompanied by an informative, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-correction">candidate correction</dfn> approved by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision②">group decision</a>.
+	When annotated inline,
+	errata—<wbr>including their <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction">candidate corrections</a>—<wbr>must be marked as such,
+	are treated as <a href="#correction-classes">class 2 changes</a>,
+	and are published accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Annotating changes in this way allows more mature documents
+	such as <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤">Recommendations</a> and <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②">Candidate Recommendations</a> to be updated quickly with the Working Group’s most current thinking,
+	even when the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment">candidate amendments</a> have not yet received
+	sufficient review or implementation experience
+	to be normatively incorporated into the specification proper.</p>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-addition">candidate addition</dfn> is similar to a <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction①">candidate correction</a>,
+	except that it proposes a new feature
+	rather than an error correction.</p>
+    <p>If there is no group chartered to maintain a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①④">technical report</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦④">Team</a> <em class="rfc2119">may</em> maintain its <a data-link-type="dfn" href="#erratum" id="ref-for-erratum①">errata</a> and associated <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction②">candidate corrections</a>.
+	Such corrections <em class="rfc2119">must</em> be marked
+	as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="team-correction">Team correction</dfn>,
+	and do not constitute
+	a normative portion of the Recommendation,
+	as defined in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (i.e. they are not covered by the Patent Policy).
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑤">Team</a> <em class="rfc2119">must</em> solicit <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review②">wide review</a> on <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction">Team corrections</a> that it produces.</p>
+    <p><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction③">Candidate corrections</a> and <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition">candidate additions</a> are collectively known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="candidate amendment" data-noexport id="candidate-amendment">candidate amendments</dfn>.</p>
+    <p>In addition to their actual <a href="#maturity-stages">maturity stage</a>, <a data-link-type="dfn" href="#publishing" id="ref-for-publishing③">published</a> <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑤">REC Track</a> documents with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①">candidate amendments</a> are also considered,
+	for the purpose of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	to be <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①">Working Drafts</a> with those <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment②">candidate amendments</a> treated as normative.</p>
+    <h4 class="heading settled" data-level="6.2.6" id="contributor-license"><span class="secno">6.2.6. </span><span class="content"> License Grants from Non-Participants</span><a class="self-link" href="#contributor-license"></a></h4>
+    <p>When a party who is not already obligated under the Patent Policy
+	offers a change in class 3 or 4
+	(as described in <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>) to a technical report under this process
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑥">Team</a> <em class="rfc2119">must</em> request
+	a recorded royalty-free patent commitment;
+	for a change in class 4, the Team <em class="rfc2119">must</em> secure such commitment.
+	Such commitment <em class="rfc2119">should</em> cover,
+	at a minimum,
+	all the party’s Essential Claims both in the contribution,
+	and that become Essential Claims as a result of incorporating the contribution into the draft
+	that existed at the time of the contribution,
+	on the terms specified in the “W3C Royalty-Free (RF) Licensing Requirements” section of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.3" id="rec-track"><span class="secno">6.3. </span><span class="content"> The W3C Recommendation Track</span><span id="rec-advance"></span><a class="self-link" href="#rec-track"></a></h3>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑨">Working Groups</a> create specifications and guidelines
+	to complete the scope of work envisioned by a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⓪">Working Group</a>'s <a data-link-type="dfn" href="#charter" id="ref-for-charter③">charter</a>.
+	These <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑤">technical reports</a> undergo cycles of revision and review
+	as they advance towards <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥">W3C Recommendation</a> status.
+	Once review suggests the Working Group has met their requirements for a new standard,
+	including <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review③">wide review</a>,
+	a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR③">Candidate Recommendation</a> phase
+	allows the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③①">Working Group</a> to formally collect <a href="#implementation-experience">implementation experience</a> to demonstrate that the specification works in practice.
+	At the end of the process,
+	the Advisory Committee reviews the mature technical report,
+	and if there is support from its Membership,
+	W3C publishes it as a <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑥">Recommendation</a>.</p>
+    <p>In summary, the <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track" data-noexport id="w3c-recommendation-track">W3C Recommendation Track</dfn> consists of:</p>
+    <ol>
+     <li>Publication of the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd①">First Public Working Draft</a>. 
+     <li>Publication of zero or more revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD②">Working Drafts</a>. 
+     <li>Publication of one or more <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR④">Candidate Recommendations</a>. 
+     <li>Publication of a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR②">Proposed Recommendation</a>. 
+     <li>Publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦">W3C Recommendation</a>. 
+    </ol>
+    <div aria-label="Basic W3C Recommendation Track" role="region">
+     <svg viewBox="-5 40 630 180" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Basic W3C Recommendation Track</title>
+      <g role="list">
+       <g fill="#060" role="listitem">
+        <a href="#wd-1">
+         <rect fill="white" height="45" role="img" width="57" y="122">
+          <title>First Public Working Draft (FPWD) - Exclusion opportunity</title>
+         </rect>
+         <text font-size="8">
+          <tspan aria-hidden="true" x="0" y="132">First Public WD</tspan>
+          <tspan x="0" y="152">WG Decision +</tspan>
+          <tspan x="0" y="160">Team Approval</tspan>
+         </text>
+         <path d="M0,140h53" fill="none" stroke="#060"></path>
+         <polygon points="47,136 57,140 47,144"></polygon>
+        </a>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="97" cy="140" fill="#fff" id="wd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Working Draft (WD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="97" y="144">WD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Publish a new Working Draft</title>
+           </g>
+           <text font-size="8">
+            <tspan x="70" y="100">WG Decision</tspan>
+           </text>
+           <path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114" fill="none" stroke="black" stroke-dasharray="6 2"></path>
+           <polygon points="120,114 116,124 114,113"></polygon>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Advance to Candidate Recommendation</title>
+           </g>
+           <text font-size="8" x="138" y="126">WG Decision +</text>
+           <text font-size="8" x="138" y="134">Team Approval</text>
+           <path d="M135,140h81" stroke="#060"></path>
+           <polygon points="211,136 221,140 211,144"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#pr-1">
+         <ellipse cx="260" cy="140" fill="#fff" id="cr-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="144">CRS</text>
+        </a>
+        <a href="#crd-1">
+         <ellipse cx="260" cy="80" fill="#fff" id="crd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Draft (CRD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="84">CRD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8">
+            <tspan x="182" y="110">WG Decision</tspan>
+           </text>
+           <path d="M234,127v-34" stroke="#000"></path>
+           <polygon points="234,92 230,102 238,102"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8">
+            <tspan x="282" y="52">WG Decision</tspan>
+           </text>
+           <path d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="282,54 277,64 275,53"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="102">WG Decision +</tspan>
+            <tspan x="290" y="110">Team Approval</tspan>
+           </text>
+           <path d="M286,127v-34" stroke="#000"></path>
+           <polygon points="286,128 282,118 290,118"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="102">WG Decision</tspan>
+            <tspan x="290" y="110">Team Approval</tspan>
+           </text>
+           <path d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114" fill="none" stroke="#000" stroke-dasharray="6 10"></path>
+           <path d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114" fill="none" stroke="#000" stroke-dasharray="6 10" stroke-dashoffset="8"></path>
+           <polygon points="282,114 277,124 275,113"></polygon>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#pr-1">
+           <g role="img">
+            <title>Advance to Proposed Recommendation</title>
+           </g>
+           <text font-size="8" x="300" y="126">WG Decision +</text>
+           <text font-size="8" x="300" y="134">Team Approval</text>
+           <path d="M298,140h77" stroke="#060"></path>
+           <polygon points="374,136 384,140 374,144"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="230" y="160">WG Decision</tspan>
+            <tspan font-size="6" x="230" y="168">(or Team Decision with AB+TAG Approval)</tspan>
+           </text>
+           <path d="M140,147h84" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="140,145 133,147 140,149"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="413" cy="140" fill="#fff" id="pr-1" role="img" rx="28" ry="18" stroke="black">
+          <title>Proposed Recommendation (PR) — AC Review</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="413" y="144">PR</text>
+         <text area-hidden="true" font-size="6" text-anchor="middle" x="413" y="150">AC Review</text>
+        </a>
+        <g role="list">
+         <g fill="#060" role="listitem">
+          <a href="#rec-1">
+           <g role="img">
+            <title>Advance to Recommendation</title>
+           </g>
+           <text font-size="8" x="300" y="138">
+            <tspan x="445" y="134">W3C Decision</tspan>
+           </text>
+           <path d="M441,140h100" stroke="#060"></path>
+           <polygon points="534,136 544,140 534,144"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Return to Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="385" y="160">W3C Decision</tspan>
+           </text>
+           <path d="M301,147h88" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="301,145 296,147 301,149"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="410" y="185">W3C Decision</tspan>
+           </text>
+           <path d="M413,158v32h-316v-26" fill="none" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="95,164 97,159 99,164"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <ellipse cx="573" cy="140" fill="#fff" id="rec-1" role="img" rx="28" ry="18" stroke="black" stroke-width="2">
+         <title>Recommendation (Rec)</title>
+        </ellipse>
+        <text aria-hidden="true" font-size="16" font-weight="bold" stroke-width=".3" text-anchor="middle" x="573" y="144">REC</text>
+       </g>
+      </g>
+     </svg>
+    </div>
+    <p>This Process defines certain <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑥">Recommendation Track</a> publications as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="patent-review-drafts">Patent Review Drafts</dfn>.
+	Under the 2004 Patent Policy (and its 2017 update) <a data-link-type="biblio" href="#biblio-patent-policy-2004" title="The W3C 2004 Patent Policy, Updated 2017">[PATENT-POLICY-2004]</a>,
+	these correspond to “Last Call Working Draft” in the Patent Policy;
+	Starting from the 2020 Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy-2020" title="The W3C 2020 Patent Policy">[PATENT-POLICY-2020]</a>,
+	these correspond to “Patent Review Draft” in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.</p>
+    <p>As described in <a href="#transition-reqs">§ 6.3.3 Advancement on the Recommendation Track</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑦">Team</a> will decline a request to advance in maturity stage
+	and return the specification to a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③②">Working Group</a> for further work
+	if it determines that the requirements for advancement
+	have not been met.</p>
+    <h4 class="heading settled" data-level="6.3.1" id="maturity-stages"><span class="secno">6.3.1. </span><span class="content"> Maturity Stages on the Recommendation Track</span><span id="maturity-levels"></span><a class="self-link" href="#maturity-stages"></a></h4>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Working Draft | Working Draft | WD" id="RecsWD">Working Draft</dfn> (<abbr>WD</abbr>) 
+     <dd>
+       A Working Draft is a document that W3C has <a data-link-type="dfn" href="#publishing" id="ref-for-publishing④">published</a> on the <a href="https://www.w3.org/TR/">W3C’s Technical Reports page</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a> for review by the community (including W3C Members), the public,
+			and other technical organizations,
+			and for simple historical reference.
+			Some, but not all, Working Drafts are meant to advance to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑧">Recommendation</a>;
+			see the <a href="#DocumentStatus">document status section</a> of a Working Draft
+			for the group’s expectations. <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD③">Working Drafts</a> do not necessarily represent a <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①①">consensus</a> of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③③">Working Group</a> with respect to their content,
+			and do not imply any endorsement by W3C
+			or its members beyond agreement to work on a general area of technology.
+			Nevertheless the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③④">Working Group</a> decided to adopt the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD④">Working Draft</a> as the basis for their work at the time of adoption.
+			A <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑤">Working Draft</a> is suitable for gathering <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review④">wide review</a> prior to advancing to the next stage of maturity. 
+      <p>For all Working Drafts a Working Group:</p>
+      <ul>
+       <li> <em class="rfc2119">should</em> document outstanding issues,
+					and parts of the document on which the Working Group does not have consensus,
+					and 
+       <li> <em class="rfc2119">may</em> request publication of a Working Draft
+					even if its content is considered unstable
+					and does not meet all Working Group requirements. 
+      </ul>
+      <p>The first Working Draft of a technical report is called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="fpwd">First Public Working Draft</dfn> (<abbr>FPWD</abbr>),
+			and has patent implications as defined in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Candidate Recommendation | Candidate Recommendation | CR" id="RecsCR">Candidate Recommendation</dfn> (<abbr>CR</abbr>) 
+     <dd>
+       A Candidate Recommendation is a document that satisfies the technical
+			requirements of the Working Group that produced it and their dependencies,
+			and has already received wide review.
+			W3C publishes a Candidate Recommendation to 
+      <ul>
+       <li> signal to the wider community that it is time to do a final review 
+       <li> gather <a href="#implementation-experience">implementation experience</a> 
+      </ul>
+      <p class="note" role="note"><span class="marker">Note:</span> Advancing to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑤">Candidate Recommendation</a> indicates
+			that the document is considered complete and fit for purpose,
+			and that no further refinement to the text is expected
+			without additional implementation experience and testing;
+			additional features in a later revision may however be expected.
+			A <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑥">Candidate Recommendation</a> is expected to be as well-written,
+			detailed,
+			self-consistent,
+			and technically complete
+			as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑨">Recommendation</a>,
+			and acceptable as such
+			if and when the requirements for further advancement are met.</p>
+      <p>Candidate Recommendation publications take one of two forms:</p>
+      <dl>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Snapshot | CRS" id="candidate-recommendation-snapshot">Candidate Recommendation Snapshot</dfn> (<abbr>CRS</abbr>) 
+       <dd>
+         A Candidate Recommendation Snapshot
+					corresponds to a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts">Patent Review Draft</a> as used in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+					Publishing a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts①">Patent Review Draft</a> triggers a Call for Exclusions,
+					per “Exclusion From W3C RF Licensing Requirements”
+					in the W3C Patent Policy. 
+        <p>Publication as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a> requires verification of either a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req">Transition Request</a> (for the first <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑦">Candidate Recommendation</a> publication from another maturity stage)
+					or an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests">Update Request</a> (for subsequent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①">Candidate Recommendation Snapshots</a>).</p>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Draft | CRD" id="candidate-recommendation-draft">Candidate Recommendation Draft</dfn> (<abbr>CRD</abbr>) 
+       <dd>
+         A Candidate Recommendation Draft
+					is published on the <a href="https://www.w3.org/TR/">W3C’s Technical Reports page</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a> to integrate changes from the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot②">Candidate Recommendation Snapshot</a> that the Working Group intends to include
+					in a subsequent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot③">Candidate Recommendation Snapshot</a>.
+					This allows for wider review of the changes
+					and for ease of reference to the integrated specification. 
+        <p>Any changes published directly into a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft">Candidate Recommendation Draft</a> should be at the same level of quality as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot④">Candidate Recommendation Snapshot</a>.
+					However, the process requirements are minimized
+					so that the Working Group can easily keep the specification up to date.</p>
+        <p>A <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft①">Candidate Recommendation Draft</a> <em>does not</em> provide an exclusion opportunity;
+					instead, it is considered a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑥">Working Draft</a> for the purpose of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+      </dl>
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rescinded-candidate-recommendation">Rescinded Candidate Recommendation</dfn> is a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑧">Candidate Recommendation</a> in which significant problems have been discovered
+			such that W3C cannot endorse it or continue work on it,
+			for example due to burdensome patent claims that affect implementers and cannot be resolved
+			(see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “PAG Conclusion”).
+			There is no path to restoration for a <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a>.
+			See “W3C Royalty-Free (RF) Licensing Requirements”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for implication on patent licensing obligations.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Proposed Recommendation | Proposed Recommendation | PR" id="RecsPR">Proposed Recommendation</dfn> (<abbr>PR</abbr>) 
+     <dd> A Proposed Recommendation is a document
+			that has been accepted by W3C
+			as of sufficient quality to become a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⓪">W3C Recommendation</a>.
+			This phase triggers formal review by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③②">Advisory Committee</a>,
+			who <em class="rfc2119">may</em> recommend
+			that the document be <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑤">published</a> as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①①">W3C Recommendation</a>,
+			returned to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑤">Working Group</a> for further work,
+			or abandoned. <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change④">Substantive changes</a> <em class="rfc2119">must not</em> be made to a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR③">Proposed Recommendation</a> except by <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑥">publishing</a> a new <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑦">Working Draft</a> or <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑨">Candidate Recommendation</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation | Recommendation | REC" id="RecsW3C">W3C Recommendation</dfn> (<abbr>REC</abbr>) 
+     <dd>
+       A W3C Recommendation is a specification
+			or set of guidelines
+			or requirements that,
+			after extensive <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①②">consensus</a>-building,
+			has received the endorsement of W3C and its Members.
+			W3C recommends the wide deployment
+			of its Recommendations as standards for the Web.
+			The W3C Royalty-Free IPR licenses
+			granted under the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> apply to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①②">W3C Recommendations</a>.
+			As technology evolves,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①③">W3C Recommendation</a> may become: 
+      <dl>
+       <dt> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsSup">Superseded Recommendation</dfn> 
+       <dd>
+         A Superseded Recommendation is a specification
+					that has been replaced by a newer version
+					that W3C recommends for new adoption.
+					An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs">Obsolete</a> or Superseded specification
+					has the same status as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①④">W3C Recommendation</a> with regards to W3C Royalty-Free IPR Licenses granted under the Patent Policy. 
+        <p class="note" role="note"><span class="marker">Note:</span> When a Technical Report which had previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑤">Recommendation</a> is again published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑥">Recommendation</a> after following the necessary steps to <a href="#revising-rec">revise</a> it,
+					the latest version replaces the previous one,
+					without the need to invoke the steps of <a href="#rec-rescind">§ 6.3.13.3 Abandoning a W3C Recommendation</a>:
+					it is the same document, updated.
+					Explicitly declaring a documented superseded, using the process documented in <a href="#rec-rescind">§ 6.3.13.3 Abandoning a W3C Recommendation</a>,
+					is intended for cases where a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑦">Recommendation</a> is superseded by a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑥">Technical Report</a> (or by a document managed outside of W3C).</p>
+       <dt> An <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsObs">Obsolete Recommendation</dfn> 
+       <dd> An Obsolete Recommendation is a specification
+					that W3C has determined lacks sufficient market relevance
+					to continue recommending it for implementation,
+					but which does not have fundamental problems
+					that would require it to be <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec">Rescinded</a>.
+					If an Obsolete specification gains sufficient market relevance,
+					W3C may decide to restore it to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑧">Recommendation</a> status. 
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RescindedRec">Rescinded Recommendation</dfn> 
+       <dd> A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses,
+					and believes is unlikely to ever be restored to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑨">Recommendation</a> status.
+					See also “W3C Royalty-Free (RF) Licensing Requirements”
+					in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+      </dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="discontinuedREC">Discontinued Draft</dfn> 
+     <dd> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑦">technical report</a> representing the state of a Recommendation-track document
+			at the point at which work on it was discontinued.
+			See <a href="#abandon-draft">§ 6.3.13.1 Abandoning an Unfinished Recommendation</a>. 
+    </dl>
+    <p>Only sufficiently technically mature work should be advanced.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Should faster advancement to meet scheduling considerations be desired,
+	this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring
+	less stable features to other technical reports.</p>
+    <p>When publishing an updated version of an existing <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⓪">Candidate Recommendation</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⓪">Recommendation</a>,
+	technical reports are expected to meet the same maturity criteria as when they are first published under that status.
+	However, in the interest of replacing stale documents with improved ones in a timely manner,
+	if flaws have been discovered in the technical report after its initial publication as a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①①">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②①">REC</a> that would have been severe enough to reject that publication had they be known in time,
+	it is also permissible to publish an updated <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①②">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②②">REC</a> following the usual process,
+	even if only some of these flaws have been satisfactorily addressed.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑥">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑧">Interest Groups</a> <em class="rfc2119">may</em> make available <a data-link-type="dfn" href="#editors-draft" id="ref-for-editors-draft">Editor’s drafts</a>. <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Editor’s Draft | Editor Draft | ED" id="editors-draft">Editor’s drafts</dfn> (<abbr>ED</abbr>) have no official standing whatsoever,
+	and do not necessarily imply consensus of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑦">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑨">Interest Group</a>,
+	nor are their contents endorsed in any way by W3C.</p>
+    <h4 class="heading settled" data-level="6.3.2" id="implementation-experience"><span class="secno">6.3.2. </span><span class="content"> Implementation Experience</span><a class="self-link" href="#implementation-experience"></a></h4>
+    <p>Implementation experience is required to show that a specification is sufficiently clear,
+	complete,
+	and relevant to market needs,
+	to ensure that independent interoperable implementations
+	of each feature of the specification will be realized.
+	While no exhaustive list of requirements is provided here,
+	when assessing that there is <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="adequate-implementation">adequate implementation experience</dfn> the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑧">Team</a> will consider (though not be limited to):</p>
+    <ul>
+     <li> is each feature of the current specification implemented,
+			and how is this demonstrated? 
+     <li> are there independent interoperable implementations of the current specification? 
+     <li> are there implementations created by people other than the authors of the specification? 
+     <li> are implementations publicly deployed? 
+     <li> is there implementation experience
+			at all levels of the specification’s ecosystem
+			(authoring, consuming, publishing…)? 
+     <li> are there reports of difficulties or problems with implementation? 
+    </ul>
+    <p>Planning and accomplishing a demonstration of (interoperable) implementations can be very time consuming.
+	Groups are often able to work more effectively
+	if they plan how they will demonstrate interoperable implementations
+	early in the development process;
+	for example, developing tests in concert with implementation efforts.</p>
+    <h4 class="heading settled" data-level="6.3.3" id="transition-reqs"><span class="secno">6.3.3. </span><span class="content"> Advancement on the Recommendation Track</span><a class="self-link" href="#transition-reqs"></a></h4>
+    <p>For <em>all</em> requests to advance a specification
+	to a new maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="trans-req">Transition Requests</dfn>),
+	the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request advancement. 
+     <li> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑨">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team⑧⓪">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision②">Team decision</a>) <em class="rfc2119">must</em> be withheld if any Process requirements are not met
+			or if there remain any unresolved Formal Objections
+			(including any <a data-link-type="dfn" href="#uphold" id="ref-for-uphold③">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑨">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed">fully addressed</a>),
+			or if the document does not adequately reflect all relevant decisions of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⓪">W3C Council</a> (or its delegates).
+			If the <a data-link-type="dfn" href="#team" id="ref-for-team⑧①">Team</a> rejects a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req①">Transition Request</a> it <em class="rfc2119">must</em> indicate its rationale
+			to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③③">Advisory Committee</a> and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑧">Working Group</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change">editorial changes</a> have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed①">formally address</a> all issues
+			raised about the document since the previous <a href="#maturity-stages">maturity stage</a>. 
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑨">Formal Objections</a>. 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑨">Working Group</a>'s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⓪">Working Group</a>. 
+    </ul>
+    <p>For a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd②">First Public Working Draft</a> there is no “previous maturity stage”,
+	so many requirements do not apply,
+	and verification is normally fairly straightforward.
+	For later stages,
+	especially transition to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①③">Candidate</a> or <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR④">Proposed Recommendation</a>,
+	there is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p><a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req②">Transition Requests</a> to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd③">First Public Working Draft</a> or <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①④">Candidate Recommendation</a> will not normally be approved
+	while a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④①">Working Group</a>'s <a data-link-type="dfn" href="#charter" id="ref-for-charter④">charter</a> is undergoing or awaiting a decision
+	on an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⓪">Advisory Committee Review</a>.</p>
+    <p></p>
+    <h4 class="heading settled" data-level="6.3.4" id="update-reqs"><span class="secno">6.3.4. </span><span class="content"> Updating Mature Publications on the Recommendation Track</span><a class="self-link" href="#update-reqs"></a></h4>
+    <p>Certain requests to re-publish a specification
+	within its current maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="update-requests">Update Requests</dfn>)
+	require extra verification.
+	For such <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①">update requests</a>, the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request the update. 
+     <li> <em class="rfc2119">must</em> show that the changes have received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑤">wide review</a>. 
+     <li> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑧②">Team</a> verification,
+			or fulfill the criteria for <a href="#streamlined-update">§ 6.3.4.1 Streamlined Publication Approval</a>. <a data-link-type="dfn" href="#team" id="ref-for-team⑧③">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision③">Team decision</a>), <em>should</em> be withheld if any Process requirements are not met,
+			and <em class="rfc2119">may</em> be withheld in consideration of unresolved Formal Objections
+			(including any <a data-link-type="dfn" href="#uphold" id="ref-for-uphold④">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③①">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed①">fully addressed</a>)
+			or if the document does not adequately reflect all relevant decisions of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③②">W3C Council</a> (or its delegates).
+			If the <a data-link-type="dfn" href="#team" id="ref-for-team⑧④">Team</a> rejects an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests②">Update Request</a>,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④②">Working Group</a>.
+			If it waives any Process requirements,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③④">AC</a>. 
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⓪">Formal Objections</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document of all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①">editorial changes</a> changes have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> show that the revised specification
+			meets all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④③">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④④">Working Group</a>'s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑤">Working Group</a>. 
+    </ul>
+    <p>There is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests③">Update request</a> verification is expected to be fairly simple
+	compared to verification of a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req③">transition request</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑤">Team</a> <em class="rfc2119">must</em> announce the publication
+	of the revised specification
+	to other W3C groups and the Public.</p>
+    <h5 class="heading settled" data-level="6.3.4.1" id="streamlined-update"><span class="secno">6.3.4.1. </span><span class="content"> Streamlined Publication Approval</span><a class="self-link" href="#streamlined-update"></a></h5>
+    <p class="note" role="note"><span class="marker">Note:</span> These criteria are intentionally stricter than
+	the general requirements for an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests④">update request</a>.
+	This is in order to minimize ambiguities and the need for expert judgment,
+	and to make self-evaluation practical.</p>
+    <p>In order to streamline the publication process in non-controversial cases,
+	verification of an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑤">update request</a> is automatically granted without formal review
+	when the following <em>additional</em> criteria are fulfilled:</p>
+    <ul>
+     <li> There <em class="rfc2119">must</em> have been no changes to <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑥">Working Group</a> requirements about this document. 
+     <li> For each of the <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a>,
+			if the Horizontal Review Group has made available a set criteria
+			under which their review is not necessary,
+			the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑦">Working Group</a> <em class="rfc2119">must</em> document that these criteria have been fulfilled.
+			Otherwise, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑧">Working Group</a> <em class="rfc2119">must</em> show
+			that review from that group has been solicited and received. 
+     <li> No <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③①">Formal Objection</a> has been registered against the document. 
+     <li>
+       The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑨">Working Group</a> <em class="rfc2119">must</em> have <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed②">formally addressed</a>: 
+      <ul>
+       <li data-md>
+        <p>all issues raised against the document that resulted in changes since the previous publication</p>
+       <li data-md>
+        <p>all issues raised against changes since the previous publication</p>
+       <li data-md>
+        <p>all issues raised against the document that were closed since the previous publication with no change to the document</p>
+      </ul>
+      <p>The response to each of these issues <em class="rfc2119">must</em> be to the satisfaction
+			of the person who raised it:
+			their proposal has been accepted,
+			or a compromise has been found,
+			or they accepted the Working Group’s rationale for rejecting it.</p>
+      <p class="note" role="note"><span class="marker">Note:</span> This is stricter than the general Transition Request criteria.</p>
+    </ul>
+    <p>Additionally, for updates to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②③">Recommendations</a> with <a href="#revised-rec-substantive">substantive changes</a> or <a href="#revised-rec-features">with new features</a>:</p>
+    <ul>
+     <li> Changes to the document are limited to <a data-link-type="dfn" href="#proposed-corrections" id="ref-for-proposed-corrections">proposed corrections</a> that were included in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections" id="ref-for-last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a> possibly combined with <a href="#correction-classes">class 1 or 2 changes</a>,
+			and/or (in the case of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②④">Recommendation</a> that <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features">allows new features</a>) <a data-link-type="dfn" href="#proposed-additions" id="ref-for-proposed-additions">proposed additions</a> that were included in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-additions" id="ref-for-last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a>. 
+     <li>
+       The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⓪">Working Group</a> <em class="rfc2119">must</em> show
+			that all changes have been implemented in at least 2 distinct products by 2 different implementers,
+			as evidenced by passing tests of a test suite
+			providing extensive coverage of the changes,
+			or an alternative streamlined verification implementation requirement
+			described in the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤①">working Group</a> charter has been met. 
+      <p class="note" role="note"><span class="marker">Note:</span> This is stricter than the general criteria for <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation①">adequate implementation experience</a>.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤②">Working Group</a> must provide written evidence for these claims,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑥">Team</a> must make these answers publicly and permanently available.</p>
+    <p>After publication,
+	if an AC Representative
+	or Team member
+	doubts that the evidence presented supports the claims,
+	they <em class="rfc2119">may</em> request that a formal review meeting be convened post facto.
+	If that review finds that the requirements were not fulfilled,
+	the Team <em class="rfc2119">may</em> revert the changes
+	by updating in place the status section to indicate that it has been reverted,
+	and by republishing the previously approved version of the technical report.</p>
+    <h4 class="heading settled" data-level="6.3.5" id="first-wd"><span class="secno">6.3.5. </span><span class="content"> Publishing a First Public Working Draft</span><a class="self-link" href="#first-wd"></a></h4>
+    <p>To publish the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd④">First Public Working Draft</a> of a document,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤③">Working Group</a> <em class="rfc2119">must</em> meet the applicable <a href="#transition-reqs">requirements for advancement</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑦">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑤">First Public Working Draft</a> to other W3C groups and to the public.</p>
+    <h4 class="heading settled" data-level="6.3.6" id="revising-wd"><span class="secno">6.3.6. </span><span class="content"> Revising a Working Draft</span><span id="revised-wd"></span><a class="self-link" href="#revising-wd"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤④">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑦">publish</a> a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑧">Working Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>If 6 months elapse without significant changes to a specification,
+	a Working Group <em class="rfc2119">should</em> publish a revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑨">Working Draft</a>,
+	whose status section <em class="rfc2119">should</em> indicate reasons for the lack of change.</p>
+    <p>To publish a revision of a Working draft, a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication. <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①③">Consensus</a> is not required,
+			as this is a procedural step, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑤">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①⓪">Working Draft</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change②">editorial changes</a> to the technical report
+			since the previous step, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups, 
+    </ul>
+    <p>Possible next steps for any Working Draft:</p>
+    <ul>
+     <li>Revised <a href="#revising-wd">Working Draft</a> 
+     <li><a href="#transition-cr">Candidate Recommendation</a> 
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.7" id="transition-cr"><span class="secno">6.3.7. </span><span class="content"> Transitioning to Candidate Recommendation</span><span id="candidate-rec"></span><span id="last-call"></span><a class="self-link" href="#transition-cr"></a></h4>
+    <p>To publish a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑤">Candidate Recommendation</a>,
+	in addition to meeting the <a href="#transition-reqs">requirements for advancement</a> a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑤">Working Group</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> show that the specification
+			has met all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑥">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">must</em> document changes to dependencies during the development of the specification, 
+     <li> <em class="rfc2119">must</em> document
+			how <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation②">adequate implementation experience</a> will be demonstrated, 
+     <li> <em class="rfc2119">must</em> specify the deadline for comments,
+			delineating the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-recommendation-review-period">Candidate Recommendation review period</dfn>,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">must</em> show that the specification has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑥">wide review</a>, and 
+     <li> <em class="rfc2119">may</em> identify features in the document as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="at-risk">at risk</dfn>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑤">Proposed Recommendation</a> without a requirement to publish a new <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑥">Candidate Recommendation</a>. 
+    </ul>
+    <p>The first Candidate Recommendation publication
+	after verification of having met the requirements for a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req④">Transition Request</a> is always a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑤">Candidate Recommendation Snapshot</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑧">Team</a> <em class="rfc2119">must</em> announce
+	the publication of the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑥">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑦">Candidate Recommendation Snapshot</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Proposed Recommendation</a>
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <p><a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑤">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 class="heading settled" data-level="6.3.8" id="revising-cr"><span class="secno">6.3.8. </span><span class="content"> Revising a Candidate Recommendation</span><span id="revised-cr"></span><a class="self-link" href="#revising-cr"></a></h4>
+    <h5 class="heading settled" data-level="6.3.8.1" id="publishing-crrs"><span class="secno">6.3.8.1. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑧">Candidate Recommendation Snapshot</a></span><a class="self-link" href="#publishing-crrs"></a></h5>
+    <p>If there are any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑥">substantive changes</a> made to a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑦">Candidate Recommendation</a> since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑨">Candidate Recommendation Snapshot</a> other than to remove features explicitly identified as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk">at risk</a>,
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑦">Working Group</a> <em class="rfc2119">must</em> meet the requirements of an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑥">update request</a> in order to republish.</p>
+    <p>In addition the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> specify the deadline for further comments,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">may</em> identify features in the document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk①">at risk</a>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑥">Proposed Recommendation</a> without a requirement to publish a new <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑧">Candidate Recommendation</a>. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑨">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a revised <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⓪">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>To provide timely updates and patent protection,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①①">Candidate Recommendation Snapshot</a> <em class="rfc2119">should</em> be published
+	within 24 months of the Working Group accepting
+	any proposal for a substantive change
+	(and preferably sooner).
+	To make scheduling reviews easier,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①②">Candidate Recommendation Snapshot</a> <em class="rfc2119">should not</em> be published
+	more often than approximately once every 6 months.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑦">Substantive changes</a> trigger a new Exclusion Opportunity
+	per “Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.8.2" id="publishing-crud"><span class="secno">6.3.8.2. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft②">Candidate Recommendation Draft</a></span><a class="self-link" href="#publishing-crud"></a></h5>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑧">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑧">publish</a> an <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft③">Update Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft④">Candidate Recommendation Draft</a>,
+	a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑧">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①③">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change③">editorial changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①④">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> document outstanding issues,
+			and parts of the document on which the Working Group does not have consensus, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+    </ul>
+    <p class="note" role="note"><span class="marker">Note:</span> A Working Group <em>does not</em> need to
+	meet the requirements of a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑤">Candidate Recommendation Snapshot</a> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑦">update request</a> in order to publish a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑤">Candidate Recommendation Draft</a>.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑥">Candidate Recommendation Draft</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Proposed Recommendation</a>,
+		if there are no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑨">substantive change</a> other than dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk②">at risk</a> features
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.9" id="transition-pr"><span class="secno">6.3.9. </span><span class="content"> Transitioning to Proposed Recommendation</span><span id="rec-pr"></span><a class="self-link" href="#transition-pr"></a></h4>
+    <p>In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,</p>
+    <ul>
+     <li> The status information <em class="rfc2119">must</em> specify the deadline for <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①①">Advisory Committee review</a>,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days
+			after the publication of the <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑦">Proposed Recommendation</a> and <em class="rfc2119">should</em> be at least 10 days
+			after the end of the last Exclusion Opportunity
+			per ”Exclusion From W3C RF Licensing Requirements”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+    </ul>
+    <p>A Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation③">adequate implementation experience</a> except where an exception is approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision④">Team Decision</a>, 
+     <li> <em class="rfc2119">must</em> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑦">wide review</a>, 
+     <li> <em class="rfc2119">must</em> show that all issues
+			raised during the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period">Candidate Recommendation review period</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed③">formally addressed</a>, 
+     <li> <em class="rfc2119">must </em>identify any substantive issues
+			raised since the close of the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period①">Candidate Recommendation review period</a>, 
+     <li> <em class="rfc2119">must not</em> have made any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①⓪">substantive changes</a> to the document
+			since the most recent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑥">Candidate Recommendation Snapshot</a>,
+			other than dropping features identified <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk③">at risk</a>. 
+     <li> <em class="rfc2119">may</em> have removed features
+			identified in the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑦">Candidate Recommendation Snapshot</a> document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk④">at risk</a> without republishing the specification as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑧">Candidate Recommendation Snapshot</a>. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑨⓪">Team</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> announce the publication of a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑧">Proposed Recommendation</a> to the <a href="#AC">Advisory Committee</a>,
+			and <em class="rfc2119">must</em> begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①②">Advisory Committee Review</a> on the question of whether the specification is appropriate to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑨">publish</a> as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑤">W3C Recommendation</a>. 
+     <li> <em class="rfc2119">may</em> approve a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR⑨">Proposed Recommendation</a> with minimal <a href="#implementation-experience">implementation experience</a> where there is a compelling reason to do so.
+			In such a case, the <a data-link-type="dfn" href="#team" id="ref-for-team⑨①">Team</a> <em class="rfc2119">must</em> explain the reasons for that decision,
+			and that information <em class="rfc2119">must</em> be included in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform①">Call for Review</a> proposing advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑥">W3C Recommendation</a>. 
+    </ul>
+    <p>Since a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑦">W3C Recommendation</a> <em class="rfc2119">must not</em> include any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①①">substantive changes</a> from the <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①⓪">Proposed Recommendation</a> it is based on,
+	to make any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①②">substantive change</a> to a <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①①">Proposed Recommendation</a> the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑨">Working Group</a> <em class="rfc2119">must</em> return the specification to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑨">Candidate Recommendation</a> or <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①①">Working Draft</a>.</p>
+    <p id="expandable-rec"> A <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①②">Proposed Recommendation</a> may identify itself
+	as intending to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="allow-new-features">allow new features</dfn> (<a href="#correction-classes">class 4 changes</a>)
+	after its initial publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑧">Recommendation</a>,
+	as described in <a href="#revised-rec-features">§ 6.3.11.4 Revising a Recommendation: New Features</a>.
+	Such an allowance cannot be added
+	to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑧">technical report</a> previously published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑨">Recommendation</a> that did not allow such changes. </p>
+    <p>Possible Next Steps:</p>
+    <ul>
+     <li> Return to <a href="#revising-wd">Working Draft</a> 
+     <li> Return to <a href="#transition-cr">Candidate Recommendation</a> 
+     <li> <a href="#transition-rec">Recommendation status</a>,
+			(the expected next step). 
+     <li> <a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⓪">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑤">Advisory Committee Appeal</a> of the decision to advance the technical report.</p>
+    <h4 class="heading settled" data-level="6.3.10" id="transition-rec"><span class="secno">6.3.10. </span><span class="content"> Transitioning to W3C Recommendation</span><span id="rec-publication"></span><a class="self-link" href="#transition-rec"></a></h4>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⓪">Recommendation</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑨">W3C Decision</a>.</p>
+    <p>In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,</p>
+    <ul>
+     <li> A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③①">Recommendation</a> <em class="rfc2119">must</em> identify where errata are tracked, and 
+     <li> A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③②">Recommendation</a> <em class="rfc2119">must not</em> include any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①③">substantive changes</a> from the <a data-link-type="dfn" href="#RecsPR" id="ref-for-RecsPR①③">Proposed Recommendation</a> on which it is based. 
+     <li> If there was any <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent④">dissent</a> in Advisory Committee reviews,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team⑨②">Team</a> <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 data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed④">formally address</a> the comment
+			at least 14 days before publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③③">W3C Recommendation</a>. 
+     <li> <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②①">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+			an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑥">Advisory Committee Appeal</a> of the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⓪">W3C decision</a> 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team⑨③">Team</a> <em class="rfc2119">must</em> announce the publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③④">W3C Recommendation</a> to <a href="#AC">Advisory Committee</a>,
+			other W3C groups
+			and to the public. 
+    </ul>
+    <p>Possible next steps:
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑤">W3C Recommendation</a> normally retains its status indefinitely.
+	However it <em class="rfc2119">may</em> be:</p>
+    <ul>
+     <li> republished as a <a href="#revising-rec">revised Recommendation</a>, or 
+     <li> republished as a <a href="#transition-cr">Candidate Recommendation</a> to be developed towards a revised <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑥">Recommendation</a>, or 
+     <li> declared <a href="#rec-rescind">superseded or obsolete</a>, or 
+     <li> <a href="#rec-rescind">rescinded</a>. 
+    </ul>
+    <h4 class="heading settled" data-level="6.3.11" id="revising-rec"><span class="secno">6.3.11. </span><span class="content"> Revising a W3C Recommendation</span><span id="rec-modify"></span><span id="revised-rec"></span><a class="self-link" href="#revising-rec"></a></h4>
+    <p>This section details the process for making changes to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑦">Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.11.1" id="revised-rec-markup"><span class="secno">6.3.11.1. </span><span class="content"> Revising a Recommendation: Markup Changes</span><a class="self-link" href="#revised-rec-markup"></a></h5>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⓪">Working group</a> <em class="rfc2119">may</em> request republication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑧">Recommendation</a> to make corrections that do not result
+	in any changes to the text of the specification.
+	(See <a href="#correction-classes">class 1 changes</a>.)</p>
+    <p>If there is no <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥①">Working Group</a> chartered to maintain a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑨">Recommendation</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨④">Team</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⓪">Recommendation</a> with such changes incorporated.</p>
+    <h5 class="heading settled" data-level="6.3.11.2" id="revised-rec-editorial"><span class="secno">6.3.11.2. </span><span class="content"> Revising a Recommendation: Editorial Changes</span><a class="self-link" href="#revised-rec-editorial"></a></h5>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change④">Editorial changes</a> to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④①">Recommendation</a> require no technical review of the intended changes.
+	A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥②">Working Group</a>,
+	provided there are no votes against the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision③">decision</a> to publish, <em class="rfc2119">may</em> request publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④②">Recommendation</a> to make this class of change without passing through earlier maturity stages.
+	(See <a href="#correction-classes">class 2 changes</a>.)</p>
+    <p>If there is no <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥③">Working Group</a> chartered to maintain a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④③">Recommendation</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑤">Team</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④④">Recommendation</a> with such changes incorporated,
+	including <a data-link-type="dfn" href="#erratum" id="ref-for-erratum②">errata</a> and <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction①">Team corrections</a>.</p>
+    <h5 class="heading settled" data-level="6.3.11.3" id="revised-rec-substantive"><span class="secno">6.3.11.3. </span><span class="content"> Revising a Recommendation: Substantive Changes</span><a class="self-link" href="#revised-rec-substantive"></a></h5>
+    <p>A <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction④">candidate correction</a> can be made normative
+	and be folded into the main text of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑤">Recommendation</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑥">Recommendation</a>,
+	including review by the community to ensure
+	the technical and editorial soundness of the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment③">candidate amendments</a>.
+	To validate this, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥④">Working Group</a> must request
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review">Last Call for Review of Proposed Amendments</a>,
+	followed by an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑧">update request</a>.
+	See <a href="#change-review">§ 6.3.11.5 Incorporating Candidate Amendments</a>.</p>
+    <p>Alternatively,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑤">Working Group</a> <em class="rfc2119">may</em> incorporate the changes
+	and <a href="#revising-wd">publish as a Working Draft</a>—<wbr>or, if the relevant criteria are fulfilled, <a href="#transition-cr">publish as a Candidate Recommendation</a>—<wbr>and advance the specification from that state.
+	(See <a href="#correction-classes">class 3 changes</a>.)</p>
+    <p class="note" role="note"><span class="marker">Note:</span> If there is no <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑥">Working Group</a> chartered to maintain a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑦">Recommendation</a> the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑥">Team</a> cannot make substantive changes and republish the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑧">Recommendation</a>.
+	It can, however, informatively highlight problems and desirable changes
+	using <a data-link-type="dfn" href="#erratum" id="ref-for-erratum③">errata</a> and <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑤">candidate corrections</a> and republish as described in <a href="#revised-rec-editorial">the previous section</a>.</p>
+    <h5 class="heading settled" data-level="6.3.11.4" id="revised-rec-features"><span class="secno">6.3.11.4. </span><span class="content"> Revising a Recommendation: New Features</span><a class="self-link" href="#revised-rec-features"></a></h5>
+    <p>New features (see <a href="#correction-classes">class 4 changes</a>)
+	may be incorporated into a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑨">Recommendation</a> explicitly identified as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features①">allowing new features</a> using <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition①">candidate additions</a>.
+	A <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition②">candidate addition</a> can be made normative
+	and be folded into the main text of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⓪">Recommendation</a> using the same process as for <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment④">candidate amendments</a>,
+	as detailed in <a href="#revised-rec-substantive">§ 6.3.11.3 Revising a Recommendation: Substantive Changes</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This prohibition against new features unless explicitly allowed
+	enables third parties to depend on Recommendations having a stable feature-set,
+	as they have prior to the 2020 revision of this Process.</p>
+    <p>To make changes which introduce a new feature
+	to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤①">Recommendation</a> that does not <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features②">allow new features</a>,
+	W3C <em class="rfc2119">must</em> create a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑨">technical report</a>,
+	following the full process of <a href="#rec-advance">advancing a technical report to Recommendation</a> beginning with a new <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑥">First Public Working Draft</a>.</p>
+    <h5 class="heading settled" data-level="6.3.11.5" id="change-review"><span class="secno">6.3.11.5. </span><span class="content"> Incorporating Candidate Amendments</span><a class="self-link" href="#change-review"></a></h5>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-review">Last Call for Review of Proposed Amendments</dfn> verifies acceptance by the W3C community of <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑤">candidate amendments</a> by combining an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①③">AC Review</a> with a patent exclusion opportunity.</p>
+    <p>The <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review①">Last Call for Review of Proposed Amendments</a> must be announced to other W3C groups, the public, and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑥">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Identify whether this is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</dfn>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</dfn>,
+			or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</dfn>. 
+     <li> Identify the specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑥">candidate amendments</a> under review
+			as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-amendments">proposed amendments</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-corrections">proposed corrections</dfn>/<dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-additions">proposed additions<span id="proposed-addition"></span></dfn>). 
+     <li> Specify the deadline for review comments,
+			which must not be any sooner than 60 days from the Call for Review. 
+     <li> Solicit review and, if it does not already have it, implementation experience. 
+    </ul>
+    <p>The combination of the existing <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤②">Recommendation</a> with the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments">proposed amendments</a> included in the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review②">Last Call for Review of Proposed Amendments</a> is considered a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts②">Patent Review Draft</a> for the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+	Also, the review initiated by the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review③">Last Call for Review of Proposed Amendments</a> is an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①④">Advisory Committee Review</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#last-call-for-review-of-proposed-additions" id="ref-for-last-call-for-review-of-proposed-additions①">Last Call for Review of Proposed Additions</a> and <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections-and-additions" id="ref-for-last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a> can only be issued for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤③">Recommendations</a> that <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features③">allow new features</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑦">Working Group</a> <em class="rfc2119">may</em> batch
+	multiple <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①">proposed amendments</a> into a single <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review④">Last Call for Review of Proposed Amendments</a>.
+	To facilitate review,
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑤">Last Call for Review of Proposed Amendments</a> on a given specification <em class="rfc2119">should not</em> be issued more frequently
+	than approximately once every 6 months.</p>
+    <p>At the end of the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑥">Last Call for Review of Proposed Amendments</a>,
+	the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①①">W3C Decision</a> may either be
+	to reject the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments②">proposed amendment</a>,
+	or to clear the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments③">proposed amendment</a> for advancement as is,
+	or to return the proposal to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑧">Working Group</a> with a request to <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑤">formally address</a> comments made on the changes under review.
+	If the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑨">Working Group</a> needs to amend a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments④">proposed amendment</a> in response to review feedback
+	it must issue another <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑦">Last Call for Review of Proposed Amendments</a> on the revised change
+	before it can be incorporated into the main text.</p>
+    <p>Once all comments on a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑤">proposed amendment</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑥">formally addressed</a>,
+	and after the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⓪">Working Group</a> can show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation④">adequate implementation experience</a> and the fulfillment of all other requirements of Recommendation text,
+	it may incorporate the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑥">proposed amendment</a> into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤④">Recommendation</a> by issuing an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑨">update request</a> for publication of the updated <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑤">Recommendation</a>.</p>
+    <p>To ensure adequate review of <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑦">proposed amendment</a> combinations,
+	only <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑧">proposed amendments</a> included in the most recent <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑧">Last Call for Review of Proposed Amendments</a> can be incorporated into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑥">Recommendation</a> text.
+	(Thus if incorporation of a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑨">proposed amendment</a> is postponed,
+	it may need to be included in multiple Last Calls for Review of Proposed Amendments.)</p>
+    <h4 class="heading settled" data-level="6.3.12" id="rec-track-regression"><span class="secno">6.3.12. </span><span class="content"> Regression on the Recommendation Track</span><a class="self-link" href="#rec-track-regression"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦①">Working Group</a> may republish a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑦">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⓪">technical report</a> at a lower <a href="#maturity-stages">maturity stage</a> by fulfilling the requirements to transition to that maturity stage,
+	as described above.</p>
+    <p>Additionally,
+	with the approval of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑤">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⓪">AB</a> the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑦">Team</a> <em class="rfc2119">may</em> return
+	the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②①">technical report</a> to a lower <a href="#maturity-stages">maturity stage</a> in response to <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑧">wide review</a> or a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③②">formal objection</a>.</p>
+    <h4 class="heading settled" data-level="6.3.13" id="tr-end"><span class="secno">6.3.13. </span><span class="content"> Retiring Recommendation Track Documents</span><a class="self-link" href="#tr-end"></a></h4>
+    <p>Work on a technical report <em class="rfc2119">may</em> cease at any time.
+	Work <em class="rfc2119 new">should</em> cease
+	if W3C or a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦②">Working Group</a> determines
+	that it cannot productively carry the work any further.</p>
+    <h5 class="heading settled" data-level="6.3.13.1" id="abandon-draft"><span class="secno">6.3.13.1. </span><span class="content"> Abandoning an Unfinished Recommendation</span><a class="self-link" href="#abandon-draft"></a></h5>
+    <p>Any <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑧">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②②">technical report</a> no longer intended
+	to advance or to be maintained,
+	and that is not being rescinded, <em class="rfc2119">should</em> be <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①⓪">published</a> as a <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC">Discontinued Draft</a>,
+	with no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①④">substantive change</a> compared to the previous publication.
+	This can happen if
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦③">Working Group</a> decided
+	to abandon work on the report,
+	or as the result of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑤">AC Review</a> requiring the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦④">Working Group</a> to discontinue work on the technical report before completion.
+	If a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑤">Working Group</a> is made to <a href="#GeneralTermination">close</a>,
+	W3C <em class="rfc2119">must</em> re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing①①">publish</a> any unfinished <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②③">technical report</a> on the Recommendation track as <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC①">Discontinued Draft</a>.</p>
+    <p>Such a document should include in its status section
+	an explanation of why it was discontinued.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑥">Working Group</a> <em class="rfc2119">may</em> resume work
+	on such a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②④">technical report</a> within the scope of its charter
+	at any time,
+	by re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing①②">publishing</a> it as a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①②">Working Draft</a>.</p>
+    <h5 class="heading settled" data-level="6.3.13.2" id="rescind-cr"><span class="secno">6.3.13.2. </span><span class="content"> Rescinding a Candidate Recommendation</span><a class="self-link" href="#rescind-cr"></a></h5>
+    <p>The process for rescinding a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②⓪">Candidate Recommendation</a> is the same as for rescinding a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑦">Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.13.3" id="rec-rescind"><span class="secno">6.3.13.3. </span><span class="content"> Abandoning a W3C Recommendation</span><a class="self-link" href="#rec-rescind"></a></h5>
+    <p>It is possible that W3C decides
+	that implementing a particular <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑧">Recommendation</a> is no longer recommended.
+	There are three designations for such specifications,
+	chosen depending on the advice W3C wishes to give about further use of the specification.</p>
+    <p>W3C <em class="rfc2119">may</em> obsolete a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑨">Recommendation</a>,
+	for example if the W3C Community decides that the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⓪">Recommendation</a> no longer represents best practices,
+	or is not adopted and is not apparently likely to be adopted.
+	An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs①">Obsolete Recommendation</a> <em class="rfc2119">may</em> be restored to normal <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥①">Recommendation</a>,
+	for example because despite marking it Obsolete the specification is later more broadly adopted.</p>
+    <p>W3C <em class="rfc2119">may</em> declare a Recommendation Superseded
+	if a newer version exists which W3C recommends for new adoption.
+	The process for declaring a Recommendation Superseded is the same as for declaring it Obsolete, below;
+	only the name and explanation change.</p>
+    <p>W3C <em class="rfc2119">may</em> rescind a Recommendation
+	if W3C believes there is no reasonable prospect of it being restored
+	for example due to burdensome patent claims that affect implementers and cannot be resolved;
+	see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “W3C Royalty-Free (RF) Licensing Requirements”
+	and “PAG Conclusion”.</p>
+    <p>W3C only rescinds, supersedes, or obsoletes entire Recommendations.
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥②">Recommendation</a> can be both superseded and obsolete.
+	To rescind, supersede, or obsolete some part of a Recommendation,
+	W3C follows the process for <a href="#revising-rec">modifying a Recommendation</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> For the purposes of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs②">Obsolete</a> or <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup">Superseded Recommendation</a> has the status of an active <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥③">Recommendation</a>,
+	although it is not recommended for future implementation;
+	a <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec①">Rescinded Recommendation</a> ceases to be in effect
+	and no new licenses are granted under the Patent Policy.</p>
+    <div aria-label="Retiring a W3C Recommendation" role="region">
+     <svg viewBox="0 0 300 135" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Supersede, Obsolete or Rescind a W3C Recommendation</title>
+      <g role="list">
+       <g role="listitem">
+        <ellipse cx="40" cy="50" fill="#fff" id="rec-3" role="img" rx="30" ry="20" stroke="black" stroke-width="2">
+         <title>Recommendation (Rec)</title>
+        </ellipse>
+        <text aria-hidden="true" font-size="18" stroke-width=".3" text-anchor="middle" x="40" y="55">REC</text>
+        <g role="list">
+         <g role="listitem">
+          <title>A major problem and an AC review can lead to a Recommendation being Rescinded.
+								There are no new IPR licences issued under the W3C Patent Policy,
+								and reinstating the Recommendation requires going through the full Rec-track process again.</title>
+          <path d="M40,29v-5s0,-5 5,-5h150" fill="none" stroke="black" stroke-dasharray="3 1" stroke-width="2"></path>
+          <text font-size="8" text-anchor="middle" x="105" y="16">Major problem, AC review</text>
+          <polygon points="195,16 195,22 199,19"></polygon>
+          <rect fill="#fff" height="36" id="rescinded" role="img" stroke="black" stroke-width="2" width="80" x="200" y="4"></rect>
+          <title>Rescinded Recommendation - no new IPR licenses</title>
+          <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="240" y="19">Rescinded</text>
+          <path d="M198,42l84,-40" stroke="red" stroke-width="2"></path>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="28">No new IPR licenses</text>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="37">No reinstatement path</text>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="black" stroke-dasharray="4 4"></path>
+           <title>With little uptake, following AC review a specification may become an Obsolete Recommendation</title>
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="red" stroke-dasharray="2 6" stroke-dashoffset="3"></path>
+           <polygon points="204,75 200,72 200,78"></polygon>
+           <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="42">Minimal usage, AC review</text>
+           <rect fill="#fff" height="26" id="obsolete" rx="8" stroke="black" stroke-dasharray="3 3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <title>Obsolete Recommendation</title>
+           <rect fill="none" height="26" rx="8" stroke="red" stroke-dasharray="3 3" stroke-dashoffset="3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="242" y="84">Obsolete</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <path d="M204,82h-149s-5,0 -5,-5v-5" fill="none" stroke="black" stroke-dasharray="2 3"></path>
+             <title>If there is new uptake, with AC review an Obsolete Recommendation may return to normal Recommendation status</title>
+             <polygon points="50,70 47,74 53,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="79">New uptake, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M40,71v29s0,5 5,5h153" fill="none" stroke="black"></path>
+           <polygon points="199,105 195,102 195,108"></polygon>
+           <text font-size="8" text-anchor="middle" x="115" y="102">Replaced by a new version, AC review</text>
+           <rect fill="#fff" height="30" id="superseded" role="img" rx="3" stroke="#600" stroke-width="2" width="80" x="200" y="100">
+            <title>Superseded Recommendation</title>
+           </rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="240" y="119">Superseded</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <title>A Superseded Recommendation can become a normal Recommendation with AC review</title>
+             <path d="M199,125h-164s-5,0 -5,-5v-52" fill="none" stroke="black" stroke-dasharray="1 4"></path>
+             <polygon points="30,70 27,74 33,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="122">Oops! The Web still needs this, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+    </div>
+    <h5 class="heading settled" data-level="6.3.13.4" id="deactivation"><span class="secno">6.3.13.4. </span><span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span><a class="self-link" href="#deactivation"></a></h5>
+    <p>The process of rescinding, obsoleting,
+	superseding,
+	or restoring
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥④">Recommendation</a> can be initiated
+	either by a request from the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑧">Team</a> or via a request from any of the following:</p>
+    <ul>
+     <li> The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑦">Working Group</a> who produced,
+			or is chartered to maintain,
+			the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑤">Recommendation</a> 
+     <li> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑥">TAG</a>, if there is no such <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑧">Working Group</a> 
+     <li> Any individual who made a request to the relevant <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑨">Working Group</a> as described above,
+			or the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑦">TAG</a> if such a group does not exist, to obsolete, rescind, supersede, or restore a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑥">Recommendation</a>,
+			where the request was not answered within 90 days 
+     <li> 5% of the members of the Advisory Committee 
+    </ul>
+    <p id="proposed-rescinded-rec">The <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑨">Team</a> <em class="rfc2119">must</em> then
+	submit the request to the <a href="#AC">Advisory Committee</a> for review.
+	For any <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑥">Advisory Committee review</a> of a proposal to
+	rescind,
+	obsolete,
+	supersede,
+	or restore
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑦">Recommendation</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⓪">Team</a> <em class="rfc2119">must</em>: </p>
+    <ul>
+     <li> announce the proposal to all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⓪">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑨">Chairs</a>,
+			and to the Public,
+			as well as to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑦">Advisory Committee</a> 
+     <li> indicate that this is a proposal to
+			Rescind,
+			Obsolete,
+			Supersede,
+			or restore,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑧">Recommendation</a> as appropriate 
+     <li> identify the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑨">Recommendation</a> by URL 
+     <li> publish a rationale for the proposal 
+     <li> identify known dependencies
+			and solicit review from all dependent <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧①">Working Groups</a> 
+     <li> solicit public review 
+     <li> specify the deadline for review comments,
+			which <em class="rfc2119">must</em> be at least 28 days
+			after the announcement 
+    </ul>
+    <p>and <em class="rfc2119">should</em></p>
+    <ul>
+     <li> identify known implementations. 
+    </ul>
+    <p>If there was any <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑤">dissent</a> in the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑦">Advisory Committee review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪①">Team</a> <em class="rfc2119">must</em> publish
+	the substantive content of the dissent to W3C <strong>and the public</strong>,
+	and <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑦">formally address</a> the dissent
+	at least 14 days
+	before publication as an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs③">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec②">Rescinded Recommendation</a>.</p>
+    <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑦">Advisory Committee Appeal</a> of the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪②">Team</a>'s decision.</p>
+    <p>W3C <em class="rfc2119">must</em> publish an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs④">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec③">Rescinded Recommendation</a> 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 <em class="rfc2119">should</em> link
+	to the explanation of <a href="https://www.w3.org/2016/11/obsoleting-rescinding/">Obsoleting and Rescinding W3C Specifications</a> <a data-link-type="biblio" href="#biblio-obs-resc" title="Obsoleting and Rescinding W3C Specifications">[OBS-RESC]</a> as appropriate.</p>
+    <p>Once W3C has published a Rescinded Recommendation,
+	future W3C technical reports <em class="rfc2119">must not</em> include normative references
+	to that technical report.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> W3C strives to ensure that all Technical Reports
+	will continue to be available at their version-specific URL.</p>
+    <h3 class="heading settled" data-level="6.4" id="note-track"><span class="secno">6.4. </span><span class="content"> The Note Track (Notes and Statements)</span><a class="self-link" href="#note-track"></a></h3>
+    <h4 class="heading settled" data-level="6.4.1" id="Note"><span class="secno">6.4.1. </span><span class="content"> Group Notes</span><a class="self-link" href="#Note"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Group Note | Note | W3C Note | Working Group Note | Interest Group Note | AB Note | TAG Note" id="WGNote">Group Note</dfn> (<abbr>NOTE</abbr>)
+	is published
+	to provide a stable reference for a useful document
+	that is not intended to be a formal standard.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧②">Working Groups</a>, <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①⓪">Interest Groups</a>,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑧">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③①">AB</a> <em class="rfc2119">may</em> publish work as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②">Notes</a>.
+	Examples include:</p>
+    <ul>
+     <li> supporting documentation for a specification,
+			such as explanations of design principles
+			or use cases and requirements 
+     <li> non-normative guides to good practices 
+    </ul>
+    <p>Some <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote③">Notes</a> are developed through successive <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Draft Note" data-noexport id="draft-note">Draft Notes</dfn> before publication as a full <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote④">Notes</a>,
+	while others are <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①③">published</a> directly as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑤">Note</a>.
+	There are few formal requirements to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①④">publish</a> a document as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑥">Note</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note">Draft Note</a>,
+	and they have no standing as a recommendation of W3C
+	but are simply documents preserved for historical reference.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> does not apply any licensing requirements or commitments for <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑦">Notes</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note①">Draft Notes</a>.</p>
+    <h4 class="heading settled" data-level="6.4.2" id="publishing-notes"><span class="secno">6.4.2. </span><span class="content"> Publishing Notes</span><a class="self-link" href="#publishing-notes"></a></h4>
+    <p>In order to publish a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑧">Note</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note②">Draft Note</a>,
+	the group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record their decision
+			to request publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑨">Note</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note③">Draft Note</a>, and 
+     <li> <em class="rfc2119">should</em> publish documentation
+			of significant changes to the technical report
+			since any previous publication. 
+    </ul>
+    <p>Both <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⓪">Notes</a> and <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note④">Draft Notes</a> can be updated by republishing
+	as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①①">Note</a> or <a data-link-type="dfn" href="#draft-note" id="ref-for-draft-note⑤">Draft Note</a>.
+	A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑤">technical report</a> <em class="rfc2119">may</em> remain
+	a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①②">Note</a> indefinitely.</p>
+    <p>If a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①③">Note</a> produced by a <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group①">chartered group</a> is no longer in scope for any group,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪③">Team</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①④">Note</a> with <a href="#correction-classes">class 1</a> changes incorporated,
+	as well as with <a data-link-type="dfn" href="#erratum" id="ref-for-erratum④">errata</a> and <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction②">Team corrections</a> annotated.</p>
+    <h4 class="heading settled" data-level="6.4.3" id="w3c-statement"><span class="secno">6.4.3. </span><span class="content"> Elevating Group Notes to W3C Statement status</span><span id="memo"></span><a class="self-link" href="#w3c-statement"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Statement | W3C Statement" data-noexport id="statement">W3C Statement</dfn> is a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑤">Note</a> that has been endorsed by W3C as a whole.
+	In order to elevate a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑥">Note</a> to <a data-link-type="dfn" href="#statement" id="ref-for-statement①">W3C Statement</a> status,
+	A group <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑨">wide review</a>. 
+     <li> record the group’s decision to request publication as a <a data-link-type="dfn" href="#statement" id="ref-for-statement②">W3C Statement</a>. 
+     <li> show that all issues raised against the document
+			since its first publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑦">Note</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑧">formally addressed</a>. 
+     <li> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③③">Formal Objections</a>. 
+    </ul>
+    <p>A <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑧">Note</a> specifying implementable technology <em class="rfc2119">should not</em> be elevated to <a data-link-type="dfn" href="#statement" id="ref-for-statement③">W3C Statement</a> status;
+	if it does,
+	the request to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement④">Statement</a> <em class="rfc2119">must</em> include rationale
+	for why it should be elevated,
+	and why it is not on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑨">Recommendation track</a>.</p>
+    <p>Once these conditions are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪④">Team</a> <em class="rfc2119">must</em> then
+	begin an Advisory Committee Review on the question of
+	whether the document is appropriate to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑤">W3C Statement</a>.
+	During this review period,
+	the <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑨">Note</a> <em class="rfc2119">must not</em> be updated.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#statement" id="ref-for-statement⑥">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①②">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②②">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑧">Advisory Committee Appeal</a> of the decision.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑤">Team</a> must announce the publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑦">W3C Statement</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑧">Advisory Committee</a>, other W3C groups, and the public.</p>
+    <h4 class="heading settled" data-level="6.4.4" id="revising-memo"><span class="secno">6.4.4. </span><span class="content"> Revising W3C Statements</span><a class="self-link" href="#revising-memo"></a></h4>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision④">group decision</a> to do so,
+	groups can request publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑧">W3C Statement</a> with <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑤">editorial changes</a>—<wbr>including <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑦">candidate amendment</a>—<wbr>without any additional process.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑧">candidate amendment</a> can be folded into the main text of the <a data-link-type="dfn" href="#statement" id="ref-for-statement⑨">W3C Statement</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①⓪">Statement</a>,
+	including review by the community to ensure
+	the substantive and editorial soundness of the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑨">candidate amendments</a>.
+	To validate this, the group must request
+	an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑧">Advisory Committee review</a> of the changes it wishes to incorporate.
+	The specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①⓪">candidate amendments</a> under review <em class="rfc2119">must</em> be identified as <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①⓪">proposed amendments</a> just as in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections" id="ref-for-last-call-for-review-of-proposed-corrections①">Last Call for Review of Proposed Corrections</a>.</p>
+    <p>The decision to incorporate <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①①">proposed amendments</a> into <a data-link-type="dfn" href="#statement" id="ref-for-statement①①">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①③">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②③">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑨">Advisory Committee Appeal</a> of the decision.</p>
+    <h3 class="heading settled" data-level="6.5" id="registries"><span class="secno">6.5. </span><span class="content"> The Registry Track</span><a class="self-link" href="#registries"></a></h3>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry">registry</dfn> documents a data set
+	consisting of one or more associated <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry table" id="registry-table">registry tables</dfn>,
+	each table representing an updatable collection
+	of logically independent, consistently-structured <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry entry" id="registry-entry">registry entries</dfn>.
+	A registry has three associated components:</p>
+    <ul>
+     <li>the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①">registry definition</a>, defining how the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②">registry tables</a> are structured and maintained 
+     <li>one or more <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table③">registry tables</a>, holding the data set represented by the <a data-link-type="dfn" href="#registry" id="ref-for-registry①">registry</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data">registry data</dfn>) 
+     <li>one or more referencing specifications, which make use of the <a data-link-type="dfn" href="#registry" id="ref-for-registry②">registry</a> 
+    </ul>
+    <p>The purposes of maintaining a <a data-link-type="dfn" href="#registry" id="ref-for-registry③">registry</a> can include:</p>
+    <dl>
+     <dt>non-collision 
+     <dd> Avoiding the problem
+			of two entities using the same value with different semantics. 
+     <dt>non-duplication 
+     <dd> Avoiding the problem
+			of having two or more different values in use with the same semantics. 
+     <dt>information 
+     <dd> Providing a central index
+			where anyone can find out
+			what a value means
+			and what its formal definition is
+			(and where it is). 
+     <dt>submission 
+     <dd> Ease of adding new terms,
+			including by stakeholders external to the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian">custodian</a> organization. 
+     <dt>consensus 
+     <dd> Promoting a clear consensus of the community on the terms. 
+    </dl>
+    <p>This section of the W3C Process provides a specialized process
+	facilitating the publication and maintenance of such <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table④">registry tables</a>,
+	particularly those required by or closely related to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦⓪">W3C Recommendations</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Not every table in a specification is a potential registry.
+	If the intent or effect is that the table enumerates
+	all the possibilities the authors of the specification expect or envisage,
+	then the table by itself is enough.
+	Similarly, if the table is managed by the Working Group
+	and only updated as part of specification update,
+	then the complexities of registry management are not needed.</p>
+    <h4 class="heading settled" data-level="6.5.1" id="reg-def"><span class="secno">6.5.1. </span><span class="content"> Registry Definitions</span><a class="self-link" href="#reg-def"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-definition">registry definition</dfn> defines what each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑤">registry table</a> is and how it is maintained.
+	It <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Define the scope and purpose of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑥">registry table</a>. 
+     <li> Define the fields of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑦">registry table</a> and their constraints
+			(e.g. values must be drawn from a defined set, or be unique,
+			or only reference publicly available resources,
+			etc.) 
+     <li>
+       Define the policy for changes to existing entries, such as 
+      <ul>
+       <li>whether entries can be deleted or deprecated 
+       <li>whether entries can be changed after being published, and what kinds of changes are allowed 
+       <li>whether previously-deleted unique identifiers can be re-used, or are reserved indefinitely 
+      </ul>
+     <li> Define the method and criteria by which changes are proposed, approved, and incorporated.
+			(For example, a <a data-link-type="dfn" href="#registry" id="ref-for-registry④">registry</a> could define
+			that changes to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry①">registry entries</a> can be proposed using a particular web form or email address,
+			that they must be accompanied by certain background information,
+			or that they do or do not need to be approved by any member of a particular Working Group.) 
+     <li>
+       Identify the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="custodian">custodian</dfn> of the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑧">registry table</a>:
+			the entity to which requests for <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change">registry changes</a> must be sent,
+			and which is responsible for evaluating whether such requests
+			satisfy the criteria defined in the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition②">registry definition</a>. 
+      <p>The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian①">custodian</a> may be the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧③">Working Group</a>, the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑥">Team</a>, or a delegated entity.
+			The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian②">custodian</a> for all <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑨">registry tables</a> in a single <a data-link-type="dfn" href="#registry" id="ref-for-registry⑤">registry</a> <em class="rfc2119">should</em> generally be the same entity.</p>
+    </ul>
+    <h4 class="heading settled" data-level="6.5.2" id="reg-pub"><span class="secno">6.5.2. </span><span class="content"> Publishing Registries</span><a class="self-link" href="#reg-pub"></a></h4>
+    <p><a data-link-type="dfn" href="#registry" id="ref-for-registry⑥">Registries</a> can be published either
+	as a stand-alone <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑥">technical report</a> on the <a data-link-type="dfn" href="#registry-track" id="ref-for-registry-track">Registry Track</a> called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-report">registry report</dfn>,
+	or incorporated as part of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦①">Recommendation</a> as a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-section">registry section</dfn>.</p>
+    <p>A <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report②">registry report</a> or <a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section①">registry section</a> is purely documentational,
+	is not subject to the W3C Patent Policy,
+	and <em class="rfc2119">must not</em> contain any requirements on implementations.
+	For the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	any <a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section②">registry section</a> in a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⓪">Recommendation track</a> document
+	is not a normative portion of that specification.</p>
+    <p>The <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report③">registry report</a> or <a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section③">registry section</a> <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Clearly label the <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report④">registry report</a>/<a data-link-type="dfn" href="#registry-section" id="ref-for-registry-section④">section</a>,
+			its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⓪">tables</a>,
+			and its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition③">registry definitions</a> as such,
+			including a link to <a href="#registries">§ 6.5 The Registry Track</a> in this Process. 
+     <li> Include the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition④">registry definition</a> for each of its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①①">registry tables</a>. 
+     <li>
+       Provide the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data">registry data</a> by either: 
+      <ul>
+       <li> Including the entire contents of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①②">registry table</a>,
+					either inline in the report
+					(e.g. formatted as a table, or list, or other appropriate representation),
+					or in a machine-readable file published as part of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑦">technical report</a>,
+					or (preferably) both. 
+       <li> Linking to one or more standalone <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report">Registry Data Reports</a> containing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①③">registry tables</a> in human-readable form, machine-readable form,
+					or (preferably) both. 
+      </ul>
+     <li> Include, if the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①④">registry table</a> is provided in a machine-readable file,
+			a definition of the format of that file. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑦">Team</a> <em class="rfc2119">must</em> make available
+	a means for interested parties to be notified of any updates to a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑤">registry table</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since the Process does not impose requirements
+	on changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑥">registry table</a> other than those imposed by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑤">registry definition</a>,
+	acceptance of proposed <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change①">registry changes</a> on behalf of the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian③">custodian</a> and
+	publication of an updated <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report⑤">registry report</a> that contains
+	only <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change②">registry changes</a> since the previous publication
+	can be automated
+	if satisfaction of those rules can be automatically verified.</p>
+    <p>Rules for publication and advancement on the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-track">Registry Track</dfn> are identical to that of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①①">Recommendation Track</a> with the following exceptions:</p>
+    <ul>
+     <li> <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report⑥">Registry reports</a> are not subject to the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			and therefore none of their publications correspond,
+			to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑦">First Public Working Draft</a>, <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①③">Working Draft</a>,
+			or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts③">Patent Review Draft</a> for the purposes of the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+     <li> For the same reason,
+			there is no equivalent to <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec④">Rescinded Recommendation</a> nor to <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation①">Rescinded Candidate Recommendation</a> for <a data-link-type="dfn" href="#registry" id="ref-for-registry⑦">Registries</a>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①④">Working Draft</a> is called <dfn data-dfn-type="dfn" data-export id="draft-registry">Draft Registry<a class="self-link" href="#draft-registry"></a></dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②①">Candidate Recommendation</a> is called <dfn data-dfn-type="dfn" data-export id="candidate-registry">Candidate Registry<a class="self-link" href="#candidate-registry"></a></dfn>,
+			with <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑨">Candidate Recommendation Snapshot</a> and <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑦">Candidate Recommendation Draft</a> corresponding to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-snapshot">Candidate Registry Snapshot</dfn> and <dfn data-dfn-type="dfn" data-export id="candidate-registry-draft">Candidate Registry Draft<a class="self-link" href="#candidate-registry-draft"></a></dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦②">W3C Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="w3c-registry">W3C Registry</dfn>; <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs⑤">Obsolete Recommendation</a> and <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup①">Superseded Recommendation</a> correspond to <dfn data-dfn-type="dfn" data-export id="obsolete-registry">Obsolete Registry<a class="self-link" href="#obsolete-registry"></a></dfn> and <dfn data-dfn-type="dfn" data-export id="superseded-registry">Superseded Registry<a class="self-link" href="#superseded-registry"></a></dfn>. 
+     <li> There is no equivalent to the Proposed Recommendation phase.
+			Instead,
+			an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑨">Advisory Committee Review</a> is started
+			upon publication of each <a data-link-type="dfn" href="#candidate-registry-snapshot" id="ref-for-candidate-registry-snapshot">Candidate Registry Snapshot</a>. 
+     <li> Changes that add new features (i.e. <a href="#correction-classes">class 4 changes</a>) are allowed
+			in all <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry">W3C Registries</a>,
+			without needing the to explicitly indicate that this is allowed. 
+    </ul>
+    <h4 class="heading settled" data-level="6.5.3" id="reg-table-update"><span class="secno">6.5.3. </span><span class="content"> Updating Registry Tables</span><a class="self-link" href="#reg-table-update"></a></h4>
+    <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑦">registry table</a> that are in accordance with the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑥">registry definition</a>,
+	(i.e. <a href="#correction-classes">Class 5 changes</a>)
+	can be made by re-publishing the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑧">technical report</a> that contains the affected table,
+	without needing to satisfy any other requirements for the publication
+	(not even Working Group consensus, unless this is required by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑦">registry definition</a>).
+	Such <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change③">registry changes</a> do not trigger new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⓪">Advisory Committee Reviews</a>,
+	nor Exclusion Opportunities,
+	and do not require verification via an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①⓪">update request</a>,
+	even for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑨">technical reports</a> at maturities where this would normally be expected.
+	Such publications can be made
+	even in the absence of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧④">Working Group</a> chartered to maintain the registry
+	when the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian④">custodian</a> is another entity.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The custodian is only empowered to make <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change④">registry changes</a>.
+	If the Working Group establishing the registry wishes
+	to empower the custodian to add commentary on individual entries,
+	this needs to be part of the registry table’s definition.
+	If other changes are desired,
+	they must be requested of the responsible Working Group—<wbr>or in the absence of a Working Group, of the Team.</p>
+    <p>Changes to the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑧">registry tables</a> made in accordance with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①①">candidate</a> or <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①②">proposed amendments</a> to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑧">registry definition</a> which would not be allowed by the unamended <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑨">registry definition</a> <em class="rfc2119">must</em> be identified as such.</p>
+    <h4 class="heading settled" data-level="6.5.4" id="reg-data-reports"><span class="secno">6.5.4. </span><span class="content"> Registry Data Reports</span><a class="self-link" href="#reg-data-reports"></a></h4>
+    <p>When the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data①">registry data</a> is published in a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⓪">technical report</a> from its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⓪">registry definition</a>,
+	that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③①">report</a> is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data-report">Registry Data Report</dfn>.
+	This <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③②">technical report</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">Must</em> link to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①①">registry definition</a> establishing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑨">registry tables</a> that it contain. 
+     <li> <em class="rfc2119">May</em> contain informative introductory text, examples, and notes
+			about the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②⓪">registry tables</a> and <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry②">entries</a> that it contains.
+			(Changes to these parts are deemed to be <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑥">editorial changes</a>). 
+    </ul>
+    <p><a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report①">Registry Data Reports</a> do not have maturity stages in and of themselves;
+	The maturity stage of the <a data-link-type="dfn" href="#registry" id="ref-for-registry⑧">registry</a> whose <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data②">data</a> they record
+	is that of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③③">technical report</a> holding the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①②">registry definition</a>.</p>
+    <p>Anytime a change is made to a <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①③">registry definition</a>,
+	the Working Group <em class="rfc2119">must</em> update and republish
+	any document holding the corresponding <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②①">registry tables</a> to make it consistent with these changes.</p>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑤">group decision</a> to do so,
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑤">Working Group</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report②">Registry Data Report</a> to incorporate <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑦">editorial changes</a>.
+	If there is no <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑥">Working Group</a> chartered to maintain this registry,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑧">Team</a> <em class="rfc2119">may</em> do so instead.</p>
+    <h4 class="heading settled" data-level="6.5.5" id="reg-ref-specifications"><span class="secno">6.5.5. </span><span class="content"> Specifications that Reference Registries</span><a class="self-link" href="#reg-ref-specifications"></a></h4>
+    <p>Registries document values,
+	they do not define any architectural or interoperability requirements
+	related to those values.
+	All architectural and interoperability requirements
+	pertaining to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry③">registry entries</a> <em class="rfc2119">must</em> be contained in the specifications that reference the registry,
+	and are therefore subject to the processes
+	(including approval and intellectual property provisions)
+	applicable to those referencing specifications.</p>
+    <p>If there are entries that must be implemented,
+	or any other such restrictions,
+	they <em class="rfc2119">must</em> be defined or documented
+	in the referencing specification
+	without dependency on the registry.</p>
+    <div class="example" id="example-cbb39e74"><a class="self-link" href="#example-cbb39e74"></a> For example,
+		“All implementations must implement the <code>Basic-Method</code> as defined in the registry”
+		is not acceptable;
+		a change to the definition of the <code>Basic-Method</code> in the registry would then affect conformance.
+		Instead, the requirement must be complete in the specification,
+		directly or by reference to another specification.
+		For example
+		“All implementations must recognize the name <code>Basic-Method</code>,
+		and implement it as defined by section yy of IETF RFC xxxx”.
+		(The Registry should nonetheless contain Basic-Method as an entry.) </div>
+    <h3 class="heading settled" data-level="6.6" id="switching-tracks"><span class="secno">6.6. </span><span class="content"> Switching Tracks</span><a class="self-link" href="#switching-tracks"></a></h3>
+    <p>Given a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑥">Group decision</a> to do so, <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑦">Working Groups</a> can republish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③④">technical report</a> on a different track than the one it is on,
+	under the following restrictions:</p>
+    <ul>
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑤">technical report</a> that is or was
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦③">W3C Recommendation</a>, <a data-link-type="dfn" href="#statement" id="ref-for-statement①②">W3C Statement</a>, or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts④">Patent Review Draft</a> cannot switch tracks. 
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑥">technical report</a> should not switch away from the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①②">Recommendation Track</a> without due consideration of the Patent Policy implications
+			and approval of W3C’s legal counsel
+			if the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑧">Working Group</a> envisions a likelihood of returning to it later. 
+    </ul>
+    <p><a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑦">Technical reports</a> that switch tracks start at
+	their new track’s initial maturity stage,
+	while retaining any established identity (url, shortname, etc.).</p>
+    <h3 class="heading settled" data-level="6.7" id="further-reading"><span class="secno">6.7. </span><span class="content"> Further reading</span><a class="self-link" href="#further-reading"></a></h3>
+    <p>Refer to <a href="https://www.w3.org/Guide/transitions">"How to Organize a Recommendation Track Transition"</a> <a data-link-type="biblio" href="#biblio-transition" title="Organize a Technical Report Transition">[TRANSITION]</a> in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[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 data-link-type="biblio" href="#biblio-rec-tips" title="Tips for Getting to Recommendation Faster">[REC-TIPS]</a>.
+	Please see also the <a href="https://www.w3.org/2003/01/republishing/">Requirements for modification of W3C Technical Reports</a> <a data-link-type="biblio" href="#biblio-republishing" title="In-place modification of W3C Technical Reports">[REPUBLISHING]</a>.</p>
+    <h2 class="heading settled" data-level="7" id="dissemination"><span class="secno">7. </span><span class="content"> <span id="chapterDissemination"></span> Dissemination Policies</span><a class="self-link" href="#dissemination"></a></h2>
+    <h3 class="heading settled" data-level="7.1" id="pub-com"><span class="secno">7.1. </span><span class="content"> Public Communication</span><a class="self-link" href="#pub-com"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑨">Team</a> is responsible for managing communication within W3C
+	and with the general public
+	(e.g., news services, press releases, managing the website and access privileges, and managing calendars).
+	Members <em class="rfc2119">should</em> solicit review by the Team
+	prior to issuing press releases about their work within W3C.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①①⓪">Team</a> makes every effort to ensure the persistence and availability of the following public information:</p>
+    <ul>
+     <li> <a href="#Reports">W3C technical reports</a> whose publication has been approved.
+			Per <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231"><cite>W3C IPR Policies</cite></a>,
+			W3C technical reports (and software) are available free of charge to the general public. 
+     <li> A <a href="https://www.w3.org/Consortium/mission">mission statement</a> <a data-link-type="biblio" href="#biblio-mission" title="The W3C Mission statement">[MISSION]</a> that explains the purpose and mission of W3C,
+			the key benefits for Members,
+			and the organizational structure of W3C. 
+     <li> Legal documents,
+			including the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> and documentation of any legal commitments W3C has with other entities. 
+     <li> The Process Document. 
+     <li> Public results of W3C activities and <a href="#GAEvents">Workshops</a>. 
+    </ul>
+    <p>To keep the Members abreast of W3C meetings, <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW">Workshops</a>,
+	and review deadlines,
+	the Team provides them with a regular (e.g., weekly) news service
+	and maintains a <a href="https://www.w3.org/participate/eventscal">calendar</a> <a data-link-type="biblio" href="#biblio-calendar" title="Calendar of all scheduled official W3C events">[CALENDAR]</a> of official W3C events.
+	Members are encouraged to send schedule and event information to the Team for inclusion on this calendar.</p>
+    <h3 class="heading settled" data-level="7.2" id="confidentiality-levels"><span class="secno">7.2. </span><span class="content"> Confidentiality Levels</span><a class="self-link" href="#confidentiality-levels"></a></h3>
+    <p>There are three principal levels of access to W3C information
+	(on the W3C website, in W3C meetings, etc.):
+	public,
+	Member-only,
+	and Team-only.</p>
+    <p>While much information made available by W3C is public,
+	“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Member-Only" id="Member-only">Member-only</dfn>” information
+	is available to authorized parties only,
+	including representatives of Member organizations, <a href="#invited-expert-wg">Invited Experts</a>,
+	the Advisory Board,
+	the TAG,
+	and the Team.
+	For example,
+	the <a href="#WGCharter">charter</a> of some Working Groups <em class="rfc2119">may</em> specify a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only④">Member-only</a> confidentiality level for group proceedings.</p>
+    <p>“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team-Only" id="Team-only">Team-only</dfn>” information
+	is available to the Team and other authorized parties.</p>
+    <p>Those authorized to access <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑤">Member-only</a> and <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only①">Team-only</a> information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> treat the information as confidential within W3C, 
+     <li> <em class="rfc2119">must</em> use reasonable efforts to maintain the proper level of confidentiality, and 
+     <li> <em class="rfc2119">must not</em> release this information to the general public or press. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①①①">Team</a> <em class="rfc2119">must</em> provide mechanisms
+	to protect the confidentiality of <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑥">Member-only</a> information
+	and ensure that authorized parties have proper access to this information.
+	Documents <em class="rfc2119">should</em> clearly indicate
+	whether they require <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑦">Member-only</a> confidentiality.
+	Individuals uncertain of the confidentiality level of a piece of information <em class="rfc2119">should</em> contact the Team.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②④">Advisory Committee representatives</a> <em class="rfc2119">may</em> authorize <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑧">Member-only</a> access to <a href="#member-rep">Member representatives</a> and other individuals employed by the Member
+	who are considered appropriate recipients.
+	For instance,
+	it is the responsibility of the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑤">Advisory Committee representative</a> and other employees
+	and official representatives of the organization
+	to ensure that Member-only news announcements
+	are distributed for internal use only within their organization.
+	Information about Member mailing lists is available
+	in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h3 class="heading settled" data-level="7.3" id="confidentiality-change"><span class="secno">7.3. </span><span class="content"> Changing Confidentiality Level</span><a class="self-link" href="#confidentiality-change"></a></h3>
+    <p>As a benefit of membership,
+	W3C provides some <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only②">Team-only</a> and <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑨">Member-only</a> channels
+	for certain types of communication.
+	For example, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑥">Advisory Committee representatives</a> can send <a href="#ACReview">reviews</a> to a <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only③">Team-only</a> channel.
+	However, for W3C processes with a significant public component,
+	such as the technical report development process,
+	it is also important for information that affects decision-making to be publicly available.
+	The Team <em class="rfc2119">may</em> need to communicate <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only④">Team-only</a> information to a Working Group or the public.
+	Similarly, a Working Group whose proceedings are <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①⓪">Member-only</a> <em class="rfc2119">must</em> make public
+	information pertinent to the technical report development process.</p>
+    <p>This document clearly indicates which information <em class="rfc2119">must</em> be available to Members or the public,
+	even though that information was initially communicated on <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑤">Team-only</a> or <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①①">Member-only</a> channels.
+	Only the <a data-link-type="dfn" href="#team" id="ref-for-team①①②">Team</a> and parties authorized by the Team
+	may change the level of confidentiality of this information.
+	When doing so:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①①③">Team</a> <em class="rfc2119">must</em> use a version of the information
+			that was expressly provided by the author for the new confidentiality level.
+			In Calls for Review and other similar messages,
+			the Team <em class="rfc2119">should</em> remind recipients to provide such alternatives. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①①④">Team</a> <em class="rfc2119">must not</em> attribute the version
+			for the new confidentiality level to the author without the author’s consent. 
+     <li> If the author has not conveyed to the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑤">Team</a> a version
+			that is suitable for another confidentiality level,
+			the Team <em class="rfc2119">may</em> make available a version that reasonably communicates what is required,
+			while respecting the original level of confidentiality,
+			and without attribution to the original author. 
+    </ol>
+    <h2 class="heading settled" data-level="8" id="GAEvents"><span class="secno">8. </span><span class="content"> Workshops and Symposia</span><a class="self-link" href="#GAEvents"></a></h2>
+    <p>The Team organizes <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="EventsW">Workshops</dfn> and <dfn data-dfn-type="dfn" data-export data-lt="Symposium | Symposia" id="EventsS">Symposia<a class="self-link" href="#EventsS"></a></dfn> to promote early involvement in the development of W3C activities
+	from Members and the public.</p>
+    <p>The goal of a Workshop 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.
+	Organizers of the first type of Workshop <em class="rfc2119">may</em> solicit position papers for the Workshop program
+	and <em class="rfc2119">may</em> use those papers
+	to choose attendees and/or presenters.</p>
+    <p>The goal of a Symposium is usually
+	to educate interested parties about a particular subject.</p>
+    <p>The Call for Participation in a Workshop or Symposium <em class="rfc2119">may</em> indicate participation requirements or limits,
+	and expected deliverables
+	(e.g., reports and <a data-link-type="dfn" href="#minutes" id="ref-for-minutes③">minutes</a>).
+	Organization of an event does not guarantee
+	further investment by W3C in a particular topic,
+	but <em class="rfc2119">may</em> lead to proposals for new activities or groups.</p>
+    <p>Workshops and Symposia generally last one to three days.
+	If a Workshop is being organized to address the pressing concerns of Members,
+	the Team <em class="rfc2119">must</em> issue the Call for Participation
+	no later than <span class="time-interval">six weeks</span> prior to the Workshop’s scheduled start date.
+	For other Workshops and Symposia,
+	the Team <em class="rfc2119">must</em> issue a Call for Participation
+	no later than <span class="time-interval">eight weeks</span> prior to the meeting’s scheduled start date.
+	This helps ensure that speakers and authors
+	have adequate time to prepare position papers and talks.</p>
+    <h2 class="heading settled" data-level="9" id="Liaisons"><span class="secno">9. </span><span class="content"> Liaisons</span><a class="self-link" href="#Liaisons"></a></h2>
+    <p>W3C uses the term <dfn data-dfn-type="dfn" data-export id="liaison">liaison<a class="self-link" href="#liaison"></a></dfn> 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 <a data-link-type="dfn" href="#team" id="ref-for-team①①⑥">Team</a> due to requirements for public communication;
+	patent,
+	copyright,
+	and other IPR policies;
+	confidentiality agreements;
+	and mutual membership agreements.</p>
+    <p>W3C <em class="rfc2119">may</em> negotiate <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement">technical agreements</a> with another organization.
+	For purposes of the W3C Process,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="agreement" data-noexport id="technical-agreement">technical agreement</dfn> is a formal contract,
+	or a Memorandum of Understanding (<abbr id="mou">MoU</abbr>),
+	or a similar document,
+	between W3C and another party or parties,
+	that relates to the technical activity of the Consortium
+	(e.g., its publications, groups, or liaisons).
+	It specifies rights and obligations of each party toward the others.
+	These rights and obligations <em class="rfc2119">may</em> include joint deliverables,
+	an agreed share of technical responsibilities with due coordination,
+	and/or considerations for confidentiality and specific IPR.</p>
+    <p>Non-technical agreements, including
+	those between W3C and its <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member①">Members</a> for the purposes of membership,
+	between W3C and its Partners for the purposes of partnership <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a>,
+	and other agreements related to the operation of the Consortium
+	or to the ordinary provision of services,
+	are not subject to these Process provisions.</p>
+    <p>When considering a <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①">technical agreement</a> (i.e., before the decision whether to sign is made),
+	the Team <em class="rfc2119">should</em> provide
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑨">Advisory Committee</a> with a draft of the proposed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement②">agreement</a>,
+	along with an explanation of how W3C would benefit from signing this <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement③">agreement</a>,
+	for their review and discussion.
+	After addressing any comments,
+	and subject to any management or governance procedures that apply
+	(e.g., formal review of proposed contracts by legal counsel or by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑦">Board</a>),
+	if the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑤">Team decides</a> to proceed with signing the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement④">agreement</a>,
+	the Team <em class="rfc2119">must</em> announce the intent to sign,
+	and provide the final text of the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑤">agreement</a>,
+	with an explanation of signing rationale, to
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④⓪">Advisory Committee</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑦">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①⓪">Advisory Committee Appeal</a> of the decision to sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑥">agreement</a>.
+	If the proposal is rejected on <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①①">appeal</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑦">Team</a> <em class="rfc2119">must not</em> sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑦">agreement</a> on behalf of W3C
+	unless directed to do so by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑧">Board</a>.
+	A signed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑧">agreement</a> <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> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a> and the guidelines W3C follows when creating a liaison is available on the Web.</p>
+    <h2 class="heading settled" data-level="10" id="Submission"><span class="secno">10. </span><span class="content"> Member Submission Process</span><a class="self-link" href="#Submission"></a></h2>
+    <p>The Member Submission process allows Members
+	to propose technology
+	or other ideas
+	for consideration by the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑧">Team</a>.
+	After review,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑨">Team</a> <em class="rfc2119">may</em> make the material available at the W3C website.
+	The formal process affords Members a record of their contribution
+	and gives them a mechanism for disclosing the details of the transaction with the Team
+	(including IPR claims).
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①②⓪">Team</a> also makes review comments on the Submitted materials available for W3C Members,
+	the public,
+	and the media.</p>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="MemberSubmission">Member Submission</dfn> consists of:</p>
+    <ul>
+     <li> One or more documents developed outside of the W3C process, and 
+     <li> Information about the documents,
+			provided by the Submitter. 
+    </ul>
+    <p>One or more Members (called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="submitter" id="submitter">Submitter(s)</dfn>) <em class="rfc2119">may</em> participate in a Member Submission.
+	Only W3C Members <em class="rfc2119">may</em> be listed as <a data-link-type="dfn" href="#submitter" id="ref-for-submitter">Submitters</a>.</p>
+    <p>The Submission process consists of the following steps:</p>
+    <ol>
+     <li> One of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①">Submitters</a> sends a request to the Team to acknowledge the Submission request.
+			The Team and <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②">Submitter</a>(s) communicate to ensure that the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission">Member Submission</a> is complete. 
+     <li>
+       After review, the <a data-link-type="dfn" href="#team" id="ref-for-team①②①">Team</a> <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> make the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission①">Member Submission</a> available
+					at the public W3C website,
+					in addition to Team comments about the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission②">Member Submission</a>. 
+       <li>If <a href="#SubmissionNo">rejected</a>,
+					the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter③">Submitter</a>(s) <em class="rfc2119">may</em> initiate a <a href="#SubmissionNo">Submission Appeal</a>. 
+      </ul>
+    </ol>
+    <div class="note" role="note">
+      Note: To avoid confusion about the Member Submission process, please note that: 
+     <ul>
+      <li> Documents in a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission③">Member Submission</a> are developed outside
+				of the W3C <a href="#Reports">technical report development process</a> (and therefore are not included in the <a href="https://www.w3.org/TR/">index of W3C technical reports</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a>). 
+      <li> The Submission process is <strong>not</strong> a means
+				by which Members ask for “ratification” of these documents
+				as <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦④">W3C Recommendations</a>. 
+      <li> There is no requirement or guarantee
+				that technology which is part of an acknowledged Submission request
+				will receive further consideration by W3C
+				(e.g., by a W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧⑨">Working Group</a>). 
+     </ul>
+    </div>
+    <p>Making a Member Submission available at the W3C website
+	does not imply endorsement by W3C,
+	including the W3C Team or Members.
+	The acknowledgment of a Submission request
+	does not imply that any action will be taken by W3C.
+	It merely records publicly
+	that the Submission request has been made by the Submitter.
+	A Member Submission made available by W3C <em class="rfc2119">must not</em> be referred to as “work in progress” of W3C.</p>
+    <p>The list of <a href="https://www.w3.org/Submission/">acknowledged Member Submissions</a> <a data-link-type="biblio" href="#biblio-submission-list" title="The list of acknowledged Member Submissions">[SUBMISSION-LIST]</a> is available at the W3C website.</p>
+    <h3 class="heading settled" data-level="10.1" id="SubmissionRights"><span class="secno">10.1. </span><span class="content"> Submitter Rights and Obligations</span><a class="self-link" href="#SubmissionRights"></a></h3>
+    <p>When more than one Member jointly participates in a Submission request,
+	only one Member formally sends in the request.
+	That Member <em class="rfc2119">must</em> copy
+	each of the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑧">Advisory Committee representatives</a> of the other participating Members,
+	and each of those <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑨">Advisory Committee representatives</a> <em class="rfc2119">must</em> confirm
+	(by email to the Team)
+	their participation in the Submission request.</p>
+    <p>At any time prior to acknowledgment,
+	any <a data-link-type="dfn" href="#submitter" id="ref-for-submitter④">Submitter</a> <em class="rfc2119">may</em> withdraw support for a Submission request
+	(described in "<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>" <a data-link-type="biblio" href="#biblio-submission-req" title="Make or Withdraw a Member Submission Request (Member-only access)">[SUBMISSION-REQ]</a>).
+	A Submission request is “withdrawn” when no Submitter(s) support it.
+	The Team <em class="rfc2119">must not</em> make statements
+	about withdrawn Submission requests.</p>
+    <p>Prior to acknowledgment,
+	the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑤">Submitter</a>(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>,
+	refer to a document as “submitted to the World Wide Web Consortium”
+	or “under consideration by W3C” or any similar phrase
+	either in public or Member communication.
+	The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑥">Submitter</a>(s) <em class="rfc2119">must not</em> imply
+	in public or Member communication
+	that W3C is working (with the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑦">Submitter</a>(s)) on the material in the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission④">Member Submission</a>.
+	The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑧">Submitter</a>(s) <em class="rfc2119">may</em> release the documents in the Member Submission to the public
+	prior to acknowledgment
+	(without reference to the Submission request).</p>
+    <p>After acknowledgment,
+	the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑨">Submitter</a>(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>,
+	imply W3C investment in the Member Submission
+	until, and unless, the material has been adopted as a deliverable
+	of a W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨⓪">Working Group</a>.</p>
+    <h4 class="heading settled" data-level="10.1.1" id="SubmissionScope"><span class="secno">10.1.1. </span><span class="content"> Scope of Member Submissions</span><a class="self-link" href="#SubmissionScope"></a></h4>
+    <p>When a technology overlaps in scope with the work of a chartered Working Group,
+	Members <em class="rfc2119">should</em> <a href="#group-participation">participate in the Working Group</a> and contribute the technology to the group’s process
+	rather than seek publication through the Member Submission process.
+	The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨①">Working Group</a> <em class="rfc2119">may</em> incorporate the contributed technology into its deliverables.
+	If the Working Group does not incorporate the technology,
+	it <em class="rfc2119">should not</em> publish the contributed documents
+	as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②⓪">Working Group Notes</a> since <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②①">Working Group Notes</a> represent group output,
+	not input to the group.</p>
+    <p>On the other hand,
+	while W3C is in the early stages of developing a charter,
+	Members <em class="rfc2119">should</em> use the Submission process
+	to build consensus around concrete proposals for new work.</p>
+    <p>Members <em class="rfc2119">should not</em> submit materials
+	covering topics well outside the scope of <a href="https://www.w3.org/Consortium/mission">W3C’s mission</a> <a data-link-type="biblio" href="#biblio-mission" title="The W3C Mission statement">[MISSION]</a>.</p>
+    <h4 class="heading settled" data-level="10.1.2" id="SubmissionReqs"><span class="secno">10.1.2. </span><span class="content"> Information Required in a Submission Request</span><a class="self-link" href="#SubmissionReqs"></a></h4>
+    <p>The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⓪">Submitter</a>(s)
+	and any other authors of the submitted material <em class="rfc2119">must</em> agree that,
+	if the request is acknowledged,
+	the documents in the Member Submission will be subject to the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a> and will include a reference to it.
+	The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①①">Submitter</a>(s) <em class="rfc2119">may</em> hold the copyright for the documents in a Member Submission.</p>
+    <p>The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments
+	in “Licensing Commitments in W3C Submissions”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①②">Submitter</a>(s) <em class="rfc2119">must</em> include the following information:</p>
+    <ul>
+     <li> The list of all submitting Members. 
+     <li> Position statements from all submitting Members (gathered by the Submitter).
+			All position statements <em class="rfc2119">must</em> appear in a separate document. 
+     <li> Complete electronic copies of any documents submitted for consideration
+			(e.g., a technical specification,
+			a position paper,
+			etc.)
+			If the Submission request is acknowledged,
+			these documents will be made available by W3C
+			and therefore <em class="rfc2119">must</em> satisfy the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules" title="Publication Rules">[PUBRULES]</a>. <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①③">Submitters</a> <em class="rfc2119">may</em> hold the copyright for the material contained in these documents,
+			but when made available by W3C,
+			these documents <em class="rfc2119">must</em> be subject to the provisions
+			of the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a>. 
+    </ul>
+    <p>The request <em class="rfc2119">must</em> also answer the following questions.</p>
+    <ul>
+     <li> What proprietary technology is required to implement the areas addressed by the request,
+			and what terms are associated with its use?
+			Again, many answers are possible,
+			but the specific answer will affect the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑥">Team’s Decision</a>. 
+     <li> What resources, if any,
+			does the Submitter intend to make available
+			if W3C acknowledges the Submission request
+			and takes action on it? 
+     <li> What action would the Submitter like W3C to take
+			if the Submission request is acknowledged? 
+     <li> What mechanisms are there to make changes to the specification being submitted?
+			This includes, but is not limited to,
+			stating where change control will reside
+			if the request is acknowledged. 
+    </ul>
+    <p>For other administrative requirements related to Submission requests,
+	see “<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>” <a data-link-type="biblio" href="#biblio-member-sub" title="How to send a Submission request">[MEMBER-SUB]</a>.</p>
+    <h3 class="heading settled" data-level="10.2" id="TeamSubmissionRights"><span class="secno">10.2. </span><span class="content"> Team Rights and Obligations</span><a class="self-link" href="#TeamSubmissionRights"></a></h3>
+    <p>Although they are not technical reports,
+	the documents in a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission⑤">Member Submission</a> <em class="rfc2119">must</em> fulfill the requirements established by the <a data-link-type="dfn" href="#team" id="ref-for-team①②②">Team</a>,
+	including the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules" title="Publication Rules">[PUBRULES]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②③">Team</a> sends a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="validation-notice">validation notice</dfn> to the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①④">Submitter</a>(s)
+	once the Team has reviewed a Submission request
+	and judged it complete and correct.</p>
+    <p>Prior to a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑦">decision</a> to <a href="#SubmissionYes">acknowledge</a> or <a href="#SubmissionNo">reject</a> the request,
+	the request is <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑥">Team-only</a>,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team①②④">Team</a> <em class="rfc2119">must</em> hold it in the strictest confidentiality.
+	In particular,
+	the Team <em class="rfc2119">must not</em> comment to the media
+	about the Submission request.</p>
+    <h3 class="heading settled" data-level="10.3" id="SubmissionYes"><span class="secno">10.3. </span><span class="content"> Acknowledgment of a Submission Request</span><a class="self-link" href="#SubmissionYes"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑤">Team</a> <a href="#SubmissionYes">acknowledges</a> a Submission request
+	by sending an announcement to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④①">Advisory Committee</a>.
+	Though the announcement <em class="rfc2119">may</em> be made at any time,
+	the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑤">Submitter</a>(s) can expect an announcement between <span class="time-interval">four to six weeks</span> after the <a data-link-type="dfn" href="#validation-notice" id="ref-for-validation-notice">validation notice</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑥">Team</a> <em class="rfc2119">must</em> keep the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑥">Submitter</a>(s) informed
+	of when an announcement is likely to be made.</p>
+    <p>Once a Submission request has been acknowledged,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑦">Team</a> <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Make the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission⑥">Member Submission</a> available at the W3C website. 
+     <li> Make the Team comments about the Submission request available at the W3C website. 
+    </ul>
+    <p>If the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑦">Submitter</a>(s) wishes to modify
+	a document made available as the result of acknowledgment,
+	the Submitter(s) <em class="rfc2119">must</em> start the Submission process from the beginning,
+	even just to correct <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑧">editorial changes</a>.</p>
+    <h3 class="heading settled" data-level="10.4" id="SubmissionNo"><span class="secno">10.4. </span><span class="content"> Rejection of a Submission Request, and Submission Appeals</span><a class="self-link" href="#SubmissionNo"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑧">Team</a> <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 jeopardize the progress of the group. 
+     <li> The IPR statement made by the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑧">Submitter</a>(s) is inconsistent with W3C’s
+			Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular the “Licensing Commitments in W3C Submissions”, <a href="https://www.w3.org/Consortium/Legal/copyright-documents">Document License</a> <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a>,
+			or other IPR policies. 
+     <li> The ideas expressed in the request are poor,
+			might harm the Web,
+			or run counter to <a href="https://www.w3.org/Consortium/mission">W3C’s mission</a> <a data-link-type="biblio" href="#biblio-mission" title="The W3C Mission statement">[MISSION]</a>. 
+     <li> The ideas expressed in the request lie well outside the scope of W3C’s mission. 
+    </ul>
+    <p>In case of a rejection,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑨">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⓪">Advisory Committee representative</a>(s)
+	of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①⑨">Submitter</a>(s).
+	If requested by the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②⓪">Submitter</a>(s),
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③⓪">Team</a> <em class="rfc2119">must</em> provide rationale
+	to the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②①">Submitter</a>(s) about the rejection.
+	Other than to the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②②">Submitter</a>(s),
+	the Team <em class="rfc2119">must not</em> make statements about why a Submission request was rejected.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③①">Advisory Committee representative</a>(s) of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②③">Submitters</a>(s) <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals">Submission Appeal</a>.
+	The procedure for handling <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="submission-appeals">Submission Appeals</dfn> is the same as for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③④">Formal Objections</a>,
+	except that an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①②">AC Appeal</a> is not possible
+	and both the Formal Objection and the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report④">Council Report</a> are confidential to the <a data-link-type="dfn" href="#team" id="ref-for-team①③①">Team</a>, <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑨">TAG</a>, and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③②">AB</a>.</p>
+    <h2 class="heading settled" data-level="11" id="GAProcess"><span class="secno">11. </span><span class="content"> Process Evolution</span><a class="self-link" href="#GAProcess"></a></h2>
+    <p>Revision of the W3C Process and related documents (see below) undergoes similar <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①④">consensus</a>-building processes as for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑧">technical reports</a>,
+	with the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③③">Advisory Board</a>—<wbr>acting as the sponsoring <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨②">Working Group</a>.
+	The documents may be developed by the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③④">AB</a> or by another group to whom the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑤">AB</a> has delegated development.
+	Review includes
+	soliciting input from the W3C community,
+	and in particular the Team.</p>
+    <p>The documents covered by this section are:</p>
+    <ul>
+     <li data-md>
+      <p>the W3C Process (this document)</p>
+     <li data-md>
+      <p>the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a></p>
+     <li data-md>
+      <p>the W3C Code of Ethics and Professional Conduct <a data-link-type="biblio" href="#biblio-cepc" title="W3C Code of Ethics and Professional Conduct">[CEPC]</a></p>
+     <li data-md>
+      <p>The W3C Document License <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a></p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑥">Advisory Board</a> initiates review as follows:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③②">Team</a> sends a Call for Review to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④②">Advisory Committee</a> and other W3C groups. 
+     <li> After comments have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑨">formally addressed</a> and the document possibly modified,
+			the Team seeks endorsement from the Members by initiating an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②①">Advisory Committee review</a>.
+			The review period <em class="rfc2119">must</em> last at least <span class="time-interval">28 days</span>. 
+     <li> <a href="#ACReviewAfter">After the Advisory Committee review</a>,
+			following a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①④">W3C decision</a> to adopt the document(s),
+			the Team does so
+			and sends an announcement to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④③">Advisory Committee</a>.
+			Advisory Committee representatives <em class="rfc2119">may</em> initiate
+			an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①③">Advisory Committee Appeal</a> to W3C. 
+    </ol>
+    <p class="note" role="note"><span class="marker">Note:</span> As of June 2020,
+	the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">Patent Policy</a> is developed in the <a href="https://www.w3.org/2004/pp/psig/">Patents and Standards Interest Group</a>,
+	the <a data-link-type="biblio" href="#biblio-cepc" title="W3C Code of Ethics and Professional Conduct">Code of Ethics and Professional Conduct</a> in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
+	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.</p>
+    <h2 class="non-normative heading settled" data-level="12" id="acks"><span class="secno">12. </span><span class="content"> Acknowledgments</span><a class="self-link" href="#acks"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>The editors are grateful to the following people,
+	who as interested individuals and/or with the affiliation(s) listed,
+	have contributed to this proposal for a revised Process:
+	Brian Kardell,
+	Carine Bournez (W3C),
+	Charles McCathie Nevile (ConsenSys),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	David Singer (Apple),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Fuqiao Xue (W3C),
+	Jeff Jaffe (W3C),
+	Jeffrey Yasskin (Google),
+	Kevin Fleming (Bloomberg),
+	Léonie Watson (The Paciello Group),
+	Mark Nottingham (Cloudflare),
+	Michael Champion (Microsoft),
+	Nigel Megitt (BBC),
+	Philippe Le Hégaret (W3C),
+	Ralph Swick (W3C),
+	Samuel Weiler (W3C),
+	Sandro Hawke (W3C),
+	Shawn Lawton Henry,
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Virginia Fournier (Apple),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <p>The editors are sorry for forgetting any names,
+	and grateful to those who have listened patiently to conversations about this document
+	without feeling a need to add more.</p>
+    <p>The following individuals contributed to the development of earlier versions of the Process:
+	Alex Russell (Google),
+	Andreas Tai (Institut fuer Rundfunktechnik),
+	Andrew Betts (Fastly),
+	Ann Bassetti (The Boeing Company),
+	Anne van Kesteren,
+	Art Barstow (Nokia, unaffiliated),
+	Bede McCall (MITRE),
+	Ben Wilson,
+	Brad Hill (Facebook),
+	Brian Kardell (JQuery),
+	Carine Bournez (W3C),
+	Carl Cargill (Netscape, Sun Microsystems, Adobe),
+	Chris Lilley (W3C),
+	Chris Wilson (Google),
+	Claus von Riegen (SAP AG),
+	Coralie Mercier (W3C),
+	Cullen Jennings (Cisco),
+	Dan Appelquist (Telefonica, Samsung),
+	Dan Connolly (W3C),
+	Daniel Dardailler (W3C),
+	Daniel Glazman (Disruptive Innovations),
+	David Baron (Mozilla),
+	David Fallside (IBM),
+	David Singer (Apple),
+	David Singer (IBM),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Don Brutzman (Web3D),
+	Don Deutsch (Oracle),
+	Eduardo Gutentag (Sun Microsystems),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Florian Rivoal,
+	Fuqiao Xue (W3C),
+	Geoffrey Creighton (Microsoft),
+	Giri Mandyam (Qualcomm),
+	Gregg Kellogg,
+	Hadley Beeman,
+	Helene Workman (Apple),
+	Henri Sivonen (Mozilla),
+	Håkon Wium Lie (Opera Software),
+	Ian Hickson (Google),
+	Ian Jacobs (W3C),
+	Ivan Herman (W3C),
+	J Alan Bird (W3C),
+	Jay Kishigami 岸上順一 (NTT),
+	Jean-Charles Verdié (MStar),
+	Jean-François Abramatic (IBM, ILOG, W3C),
+	Jeff Jaffe (W3C),
+	Jim Bell (HP),
+	Jim Miller (W3C),
+	Joe Hall (CDT),
+	John Klensin (MCI),
+	Josh Soref (BlackBerry, unaffiliated),
+	Judy Brewer (W3C),
+	Judy Zhu 朱红儒 (Alibaba),
+	Kari Laihonen (Ericsson),
+	Karl Dubost (Mozilla),
+	Ken Laskey (MITRE),
+	Kevin Fleming (Bloomberg),
+	Klaus Birkenbihl (Fraunhofer Gesellschaft),
+	Larry Masinter (Adobe Systems),
+	Lauren Wood (unaffiliated),
+	Liam Quin (W3C),
+	Léonie Watson (The Paciello Group),
+	Marcos Cáceres (Mozilla),
+	Maria Courtemanche (IBM),
+	Mark Crawford (SAP),
+	Mark Nottingham,
+	Michael Champion (Microsoft),
+	Michael Geldblum (Oracle),
+	Mike West (Google),
+	Mitch Stoltz (EFF),
+	Natasha Rooney (GSMA),
+	Nigel Megitt (BBC),
+	Olle Olsson (SICS),
+	Ora Lassila (Nokia),
+	Paul Cotton (Microsoft),
+	Paul Grosso (Arbortext),
+	Peter Linss,
+	Peter Patel-Schneider,
+	Philippe Le Hégaret (W3C),
+	Qiuling Pan (Huawei),
+	Ralph Swick (W3C),
+	Renato Iannella (IPR Systems),
+	Rigo Wenning (W3C),
+	Rob Sanderson (J Paul Getty Trust),
+	Robin Berjon (W3C),
+	Sally Khudairi (W3C),
+	Sam Ruby (IBM),
+	Sam Sneddon,
+	Sandro Hawke (W3C),
+	Sangwhan Moon (Odd Concepts),
+	Scott Peterson (Google),
+	Steve Holbrook (IBM),
+	Steve Zilles (Adobe Systems)
+	Steven Pemberton (CWI),
+	TV Raman (Google),
+	Tantek Çelik (Mozilla),
+	Terence Eden (Her Majesty’s Government),
+	Thomas Reardon (Microsoft),
+	Tim Berners-Lee (W3C),
+	Tim Krauskopf (Spyglass),
+	Travis Leithead (Microsoft),
+	Virginia Fournier (Apple),
+	Virginie Galindo (Gemalto),
+	Wayne Carr (Intel),
+	Wendy Fong (Hewlett-Packard),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <h2 class="non-normative heading settled" data-level="13" id="changes"><span class="secno">13. </span><span class="content"> Changes</span><a class="self-link" href="#changes"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <h3 class="no-num heading settled" id="changes-2023-1"><span class="content"> Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a></span><a class="self-link" href="#changes-2023-1"></a></h3>
+    <p>This document is based on the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a>.
+	A <a href="https://github.com/w3c/w3process/issues?q=milestone%3A%22Process+2023-1%22+is%3Aclosed">list of issues addressed</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2F">diff from Process 2023 to this latest version</a>,
+	as well as
+	a <a href="https://github.com/w3c/w3process/compare/p2023...main">detailed log of all changes since then</a> are available. </p>
+    <p>The only change is:</p>
+    <ul>
+     <li> Expand the TAG from 6 elected and 3 appointed to 8 and 3.
+			See <a href="https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-05-24-doc#tag-size">the 2023-05-24 Disposition of Comments</a> for rationale. 
+    </ul>
+    <h3 class="no-num heading settled" id="changes-previous"><span class="content"> Changes since earlier versions</span><span id="changes-2023"></span><span id="changes-2021"></span><span id="changes-2020"></span><span id="changes-2019"></span><span id="changes-2018"></span><span id="changes-2017"></span><a class="self-link" href="#changes-previous"></a></h3>
+    <p>Changes since earlier versions of the Process are detailed
+	in the <a href="https://www.w3.org/2023/Process-20230612/#changes">changes section of the previous version</a> of the Process.</p>
+   </main>
+   <div data-fill-with="conformance">
+    <h2 class="no-ref no-num heading settled" id="w3c-conformance"><span class="content">Conformance</span><a class="self-link" href="#w3c-conformance"></a></h2>
+    <h3 class="no-ref no-num heading settled" id="w3c-conventions"><span class="content">Document conventions</span><a class="self-link" href="#w3c-conventions"></a></h3>
+    <p>Conformance requirements are expressed
+    with a combination of descriptive assertions
+    and RFC 2119 terminology.
+    The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
+    in the normative parts of this document
+    are to be interpreted as described in RFC 2119.
+    However, for readability,
+    these words do not appear in all uppercase letters in this specification. </p>
+    <p>All of the text of this specification is normative
+    except sections explicitly marked as non-normative, examples, and notes. <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a> </p>
+    <p>Examples in this specification are introduced with the words “for example”
+    or are set apart from the normative text
+    with <code>class="example"</code>,
+    like this: </p>
+    <div class="example" id="w3c-example">
+     <a class="self-link" href="#w3c-example"></a> 
+     <p>This is an example of an informative example. </p>
+    </div>
+    <p>Informative notes begin with the word “Note”
+    and are set apart from the normative text
+    with <code>class="note"</code>,
+    like this: </p>
+    <p class="note" role="note">Note, this is an informative note.</p>
+   </div>
+<script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script>
+  </main>
+  <h2 class="no-num no-ref heading settled" id="index"><span class="content">Index</span><a class="self-link" href="#index"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="content">Terms defined by this specification</span><a class="self-link" href="#index-defined-here"></a></h3>
+  <ul class="index">
+   <li><a href="#advisory-board">AB</a><span>, in § 3.3.1.1</span>
+   <li><a href="#WGNote">AB Note</a><span>, in § 6.4.1</span>
+   <li><a href="#advisory-committee">AC</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">AC Appeal</a><span>, in § 5.9</span>
+   <li><a href="#advisory-committee-representative">AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">AC Review</a><span>, in § 5.7</span>
+   <li><a href="#adequate-implementation">adequate implementation experience</a><span>, in § 6.3.2</span>
+   <li><a href="#adopted-draft">Adopted Draft</a><span>, in § 4.2</span>
+   <li><a href="#advisory-board">Advisory Board</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">Advisory Committee</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">Advisory Committee Appeal</a><span>, in § 5.9</span>
+   <li><a href="#advisory-committee-representative">Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">Advisory Committee review</a><span>, in § 5.7</span>
+   <li><a href="#technical-agreement">agreement</a><span>, in § 9</span>
+   <li><a href="#allow-new-features">allow new features</a><span>, in § 6.3.9</span>
+   <li><a href="#alternate-ac-representative">alt AC rep</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-appeal">Appeal</a><span>, in § 5.9</span>
+   <li><a href="#at-risk">at risk</a><span>, in § 6.3.7</span>
+   <li><a href="#bod">Board</a><span>, in § 2.2</span>
+   <li><a href="#bod">Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#bod">BoD</a><span>, in § 2.2</span>
+   <li><a href="#reviewform">Call for Review</a><span>, in § 5.7.1</span>
+   <li><a href="#candidate-addition">candidate addition</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-amendment">candidate amendment</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-correction">candidate correction</a><span>, in § 6.2.5</span>
+   <li><a href="#RecsCR">Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">Candidate Recommendation Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-review-period">Candidate Recommendation review period</a><span>, in § 6.3.7</span>
+   <li><a href="#candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-registry">Candidate Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-draft">Candidate Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-snapshot">Candidate Registry Snapshot</a><span>, in § 6.5.2</span>
+   <li><a href="#ceo">CEO</a><span>, in § 2.2</span>
+   <li><a href="#GeneralChairs">Chair</a><span>, in § 3.4.1</span>
+   <li><a href="#chair-decisions">chair decisions</a><span>, in § 5.1</span>
+   <li><a href="#charter">charter</a><span>, in § 4.2</span>
+   <li><a href="#chartered-group">chartered groups</a><span>, in § 3.4</span>
+   <li><a href="#dfn-charter-extension">charter extension</a><span>, in § 4.5</span>
+   <li><a href="#def-Consensus">Consensus</a><span>, in § 5.2.1</span>
+   <li><a href="#w3c-council">Council</a><span>, in § 5.6.2</span>
+   <li><a href="#council-report">Council Report</a><span>, in § 5.6.2.7</span>
+   <li><a href="#council-team-contact">Council Team Contact</a><span>, in § 5.6.2.1</span>
+   <li><a href="#RecsCR">CR</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">CRD</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-snapshot">CRS</a><span>, in § 6.3.1</span>
+   <li><a href="#custodian">custodian</a><span>, in § 6.5.1</span>
+   <li><a href="#discontinuedREC">Discontinued Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#dismissed">dismiss</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissal</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissed</a><span>, in § 5.6.2.3</span>
+   <li><a href="#def-Dissent">Dissent</a><span>, in § 5.2.1</span>
+   <li><a href="#distributed-meeting">distributed meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#draft-note">Draft Note</a><span>, in § 6.4.1</span>
+   <li><a href="#draft-registry">Draft Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#editors-draft">ED</a><span>, in § 6.3.1</span>
+   <li><a href="#editors-draft">Editor Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#editorial-change">editorial change</a><span>, in § 6.2.3</span>
+   <li><a href="#editors-draft">Editor’s Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#elected-group">elected groups</a><span>, in § 3.3</span>
+   <li><a href="#erratum">errata</a><span>, in § 6.2.4</span>
+   <li><a href="#erratum">erratum</a><span>, in § 6.2.4</span>
+   <li><a href="#exclusion-draft">Exclusion Draft</a><span>, in § 4.2</span>
+   <li><a href="#exclusion-draft-charter">Exclusion Draft Charter</a><span>, in § 4.2</span>
+   <li><a href="#ftf-meeting">face-to-face meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#fpwd">First Public Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#formally-addressed">formally addressed</a><span>, in § 5.3</span>
+   <li><a href="#FormalObjection">Formal Objection</a><span>, in § 5.5</span>
+   <li><a href="#fully-addressed">fully addressed</a><span>, in § 5.6.2.6</span>
+   <li><a href="#w3c-group">group</a><span>, in § 3</span>
+   <li><a href="#group-decision">group decision</a><span>, in § 5.1</span>
+   <li><a href="#WGNote">Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#WGNote">Interest Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsIG">Interest Groups</a><span>, in § 3.4</span>
+   <li><a href="#invited-expert-in-an-interest-group">Invited Expert in an Interest Group</a><span>, in § 3.4.3.4</span>
+   <li><a href="#invited-expert-in-a-working-group">Invited Expert in a Working Group</a><span>, in § 3.4.3.3</span>
+   <li><a href="#last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a><span>, in § 6.3.11.5</span>
+   <li><a href="#last-call-review">Last Call for Review of Proposed Amendments</a><span>, in § 6.3.11.5</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a><span>, in § 6.3.11.5</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a><span>, in § 6.3.11.5</span>
+   <li><a href="#liaison">liaison</a><span>, in § 9</span>
+   <li><a href="#w3c-member">Member</a><span>, in § 2.1</span>
+   <li><a href="#member-association">Member Association</a><span>, in § 2.1.2.1</span>
+   <li><a href="#member-association">Member Associations</a><span>, in § 2.1.2.1</span>
+   <li><a href="#Member-only">Member-Only</a><span>, in § 7.2</span>
+   <li><a href="#member-representative-in-an-interest-group">Member representative in an Interest Group</a><span>, in § 3.4.3.2</span>
+   <li><a href="#member-representative-in-a-working-group">Member representative in a Working Group</a><span>, in § 3.4.3.1</span>
+   <li><a href="#MemberSubmission">Member Submission</a><span>, in § 10</span>
+   <li><a href="#minority-opinion">Minority Opinion</a><span>, in § 5.6.2.6</span>
+   <li><a href="#minutes">minutes</a><span>, in § 3.1.2.2</span>
+   <li><a href="#WGNote">Note</a><span>, in § 6.4.1</span>
+   <li><a href="#not-required">not required</a><span>, in § Unnumbered section</span>
+   <li><a href="#RecsObs">Obsolete Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#obsolete-registry">Obsolete Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#overrule">overrule</a><span>, in § 5.6.2.6</span>
+   <li><a href="#participant">participant</a><span>, in § 3</span>
+   <li><a href="#igparticipant">participants in an Interest Group</a><span>, in § 3.4.2</span>
+   <li><a href="#wgparticipant">participants in a Working Group</a><span>, in § 3.4.2</span>
+   <li><a href="#inv-expert-info">participate in a Working Group as an Invited Expert</a><span>, in § 3.4.3.3</span>
+   <li><a href="#patent-review-drafts">Patent Review Drafts</a><span>, in § 6.3</span>
+   <li><a href="#RecsPR">PR</a><span>, in § 6.3.1</span>
+   <li><a href="#primary-affiliation">primary affiliation</a><span>, in § 3.3.3.3</span>
+   <li><a href="#proposed-additions">proposed additions</a><span>, in § 6.3.11.5</span>
+   <li><a href="#proposed-amendments">proposed amendments</a><span>, in § 6.3.11.5</span>
+   <li><a href="#proposed-corrections">proposed corrections</a><span>, in § 6.3.11.5</span>
+   <li><a href="#RecsPR">Proposed Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#proxy">proxy</a><span>, in § 5.2.3</span>
+   <li><a href="#public-participant-ig">public participants</a><span>, in § 3.4.2</span>
+   <li><a href="#publishing">publish</a><span>, in § 6.2.1</span>
+   <li><a href="#RecsW3C">REC</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsW3C">Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">Recommendation-track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">REC Track</a><span>, in § 6.3</span>
+   <li><a href="#registry">registry</a><span>, in § 6.5</span>
+   <li><a href="#registry-change">registry change</a><span>, in § 6.2.3</span>
+   <li><a href="#registry-data">registry data</a><span>, in § 6.5</span>
+   <li><a href="#registry-data-report">Registry Data Report</a><span>, in § 6.5.4</span>
+   <li><a href="#registry-definition">registry definition</a><span>, in § 6.5.1</span>
+   <li><a href="#registry-entry">registry entry</a><span>, in § 6.5</span>
+   <li><a href="#registry-report">registry report</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-section">registry section</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-table">registry table</a><span>, in § 6.5</span>
+   <li><a href="#registry-track">Registry Track</a><span>, in § 6.5.2</span>
+   <li><a href="#related-member">Related Member</a><span>, in § 2.1.2.2</span>
+   <li><a href="#renounce">renounce</a><span>, in § 5.6.2.3</span>
+   <li><a href="#renounce">renunciation</a><span>, in § 5.6.2.3</span>
+   <li><a href="#rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#RescindedRec">Rescinded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#group-decision">resolution</a><span>, in § 5.1</span>
+   <li><a href="#statement">Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#submission-appeals">Submission Appeals</a><span>, in § 10.4</span>
+   <li><a href="#submitter">submitter</a><span>, in § 10</span>
+   <li><a href="#subsidiary">subsidiary</a><span>, in § 2.1.2.2</span>
+   <li><a href="#substantive-change">substantive change</a><span>, in § 6.2.3</span>
+   <li><a href="#mtg-substitute">substitute</a><span>, in § 3.4.2</span>
+   <li><a href="#RecsSup">Superseded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#superseded-registry">Superseded Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#supplemental-confidential-council-report">Supplemental Confidential Council Report</a><span>, in § 5.6.2.7</span>
+   <li><a href="#EventsS">Symposia</a><span>, in § 8</span>
+   <li><a href="#EventsS">Symposium</a><span>, in § 8</span>
+   <li><a href="#technical-architecture-group">TAG</a><span>, in § 3.3.2.1</span>
+   <li><a href="#WGNote">TAG Note</a><span>, in § 6.4.1</span>
+   <li><a href="#team">Team</a><span>, in § 2.2</span>
+   <li><a href="#TeamContact">Team Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#team-correction">Team correction</a><span>, in § 6.2.5</span>
+   <li><a href="#team-decision">Team Decision</a><span>, in § 5.1</span>
+   <li><a href="#Team-only">Team-Only</a><span>, in § 7.2</span>
+   <li><a href="#team-representative-in-an-interest-group">Team representative in an Interest Group</a><span>, in § 3.4.3.6</span>
+   <li><a href="#team-representative-in-a-working-group">Team representative in a Working Group</a><span>, in § 3.4.3.5</span>
+   <li><a href="#team-decision">Team’s Decision</a><span>, in § 5.1</span>
+   <li><a href="#technical-agreement">technical agreement</a><span>, in § 9</span>
+   <li><a href="#technical-architecture-group">Technical Architecture Group</a><span>, in § 3.3.2.1</span>
+   <li><a href="#technical-report">Technical Report</a><span>, in § 6.2.1</span>
+   <li><a href="#trans-req">Transition Requests</a><span>, in § 6.3.3</span>
+   <li><a href="#def-Unanimity">Unanimity</a><span>, in § 5.2.1</span>
+   <li><a href="#update-requests">Update Requests</a><span>, in § 6.3.4</span>
+   <li><a href="#uphold">upheld</a><span>, in § 5.6.2.6</span>
+   <li><a href="#uphold">uphold</a><span>, in § 5.6.2.6</span>
+   <li><a href="#uphold">upholding</a><span>, in § 5.6.2.6</span>
+   <li><a href="#uphold">upholds</a><span>, in § 5.6.2.6</span>
+   <li><a href="#validation-notice">validation notice</a><span>, in § 10.2</span>
+   <li><a href="#bod">W3C Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#RecsCR">W3C Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-council">W3C Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">W3C Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#def-w3c-decision">W3C decision</a><span>, in § 5.1</span>
+   <li><a href="#fellows">W3C Fellows</a><span>, in § 2.2</span>
+   <li><a href="#w3c-group">W3C Group</a><span>, in § 3</span>
+   <li><a href="#w3c-member">W3C Member</a><span>, in § 2.1</span>
+   <li><a href="#WGNote">W3C Note</a><span>, in § 6.4.1</span>
+   <li><a href="#RecsPR">W3C Proposed Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsW3C">W3C Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">W3C Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-registry">W3C Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#statement">W3C Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#team">W3C Team</a><span>, in § 2.2</span>
+   <li><a href="#RecsWD">W3C Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsWD">WD</a><span>, in § 6.3.1</span>
+   <li><a href="#dfn-wide-review">wide review</a><span>, in § 6.2.2.1</span>
+   <li><a href="#RecsWD">Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#WGNote">Working Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsWG">Working Groups</a><span>, in § 3.4</span>
+   <li><a href="#EventsW">Workshops</a><span>, in § 8</span>
+  </ul>
+  <h3 class="no-num no-ref heading settled" id="index-defined-elsewhere"><span class="content">Terms defined by reference</span><a class="self-link" href="#index-defined-elsewhere"></a></h3>
+  <ul class="index">
+   <li>
+    <a data-link-type="biblio">[W3C-PATENT-POLICY]</a> defines the following terms:
+    <ul>
+     <li><span class="dfn-paneled" id="b923fc87">patent advisory group</span>
+    </ul>
+  </ul>
+  <h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
+  <dl>
+   <dt id="biblio-cepc">[CEPC]
+   <dd><a href="https://www.w3.org/Consortium/cepc/"><cite>W3C Code of Ethics and Professional Conduct</cite></a>. URL: <a href="https://www.w3.org/Consortium/cepc/">https://www.w3.org/Consortium/cepc/</a>
+   <dt id="biblio-collaborators-agreement">[COLLABORATORS-AGREEMENT]
+   <dd><a href="https://www.w3.org/Consortium/Legal/collaborators-agreement"><cite>Invited expert and collaborators agreement</cite></a>. URL: <a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">https://www.w3.org/Consortium/Legal/collaborators-agreement</a>
+   <dt id="biblio-conflict-policy">[CONFLICT-POLICY]
+   <dd><a href="https://www.w3.org/2000/09/06-conflictpolicy"><cite>Conflict of Interest Policy for W3C Team Members Engaged in Outside Professional Activities</cite></a>. URL: <a href="https://www.w3.org/2000/09/06-conflictpolicy">https://www.w3.org/2000/09/06-conflictpolicy</a>
+   <dt id="biblio-doc-license">[DOC-LICENSE]
+   <dd><a href="https://www.w3.org/Consortium/Legal/copyright-documents"><cite>W3C Document License</cite></a>. URL: <a href="https://www.w3.org/Consortium/Legal/copyright-documents">https://www.w3.org/Consortium/Legal/copyright-documents</a>
+   <dt id="biblio-patent-policy">[PATENT-POLICY]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy/"><cite>The W3C Patent Policy</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy/">https://www.w3.org/Consortium/Patent-Policy/</a>
+   <dt id="biblio-patent-policy-2004">[PATENT-POLICY-2004]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy-20170801/"><cite>The W3C 2004 Patent Policy, Updated 2017</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy-20170801/">https://www.w3.org/Consortium/Patent-Policy-20170801/</a>
+   <dt id="biblio-patent-policy-2020">[PATENT-POLICY-2020]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy-20200915/"><cite>The W3C 2020 Patent Policy</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy-20200915/">https://www.w3.org/Consortium/Patent-Policy-20200915/</a>
+   <dt id="biblio-pubrules">[PUBRULES]
+   <dd><a href="https://www.w3.org/pubrules/"><cite>Publication Rules</cite></a>. URL: <a href="https://www.w3.org/pubrules/">https://www.w3.org/pubrules/</a>
+   <dt id="biblio-rfc2119">[RFC2119]
+   <dd>S. Bradner. <a href="https://datatracker.ietf.org/doc/html/rfc2119"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. March 1997. Best Current Practice. URL: <a href="https://datatracker.ietf.org/doc/html/rfc2119">https://datatracker.ietf.org/doc/html/rfc2119</a>
+   <dt id="biblio-rfc3797">[RFC3797]
+   <dd>D. Eastlake 3rd. <a href="https://www.rfc-editor.org/rfc/rfc3797"><cite>Publicly Verifiable Nominations Committee (NomCom) Random Selection</cite></a>. June 2004. Informational. URL: <a href="https://www.rfc-editor.org/rfc/rfc3797">https://www.rfc-editor.org/rfc/rfc3797</a>
+   <dt id="biblio-w3c-patent-policy">[W3C-PATENT-POLICY]
+   <dd>Wendy Seltzer. <a href="https://www.w3.org/Consortium/Patent-Policy/"><cite>W3C Patent Policy</cite></a>. 15 September 2020. URL: <a href="https://www.w3.org/Consortium/Patent-Policy/">https://www.w3.org/Consortium/Patent-Policy/</a>
+  </dl>
+  <h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
+  <dl>
+   <dt id="biblio-ab-hp">[AB-HP]
+   <dd><a href="https://www.w3.org/2002/ab/"><cite>The Advisory Board home page</cite></a>. URL: <a href="https://www.w3.org/2002/ab/">https://www.w3.org/2002/ab/</a>
+   <dt id="biblio-ac-meeting">[AC-MEETING]
+   <dd><a href="https://www.w3.org/Member/Meeting/"><cite>Advisory Committee meetings (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/Meeting/">https://www.w3.org/Member/Meeting/</a>
+   <dt id="biblio-bg-cg">[BG-CG]
+   <dd><a href="https://www.w3.org/community/about/process/"><cite>Community and Business Group Process</cite></a>. URL: <a href="https://www.w3.org/community/about/process/">https://www.w3.org/community/about/process/</a>
+   <dt id="biblio-bylaws">[BYLAWS]
+   <dd><a href="https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a>. URL: <a href="https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf">https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf</a>
+   <dt id="biblio-calendar">[CALENDAR]
+   <dd><a href="https://www.w3.org/participate/eventscal"><cite>Calendar of all scheduled official W3C events</cite></a>. URL: <a href="https://www.w3.org/participate/eventscal">https://www.w3.org/participate/eventscal</a>
+   <dt id="biblio-chair">[CHAIR]
+   <dd><a href="https://www.w3.org/Guide/chair/role.html"><cite>W3C Working/Interest Group Chair</cite></a>. URL: <a href="https://www.w3.org/Guide/chair/role.html">https://www.w3.org/Guide/chair/role.html</a>
+   <dt id="biblio-charter">[CHARTER]
+   <dd><a href="https://www.w3.org/Guide/process/charter.html"><cite>How to Create a Working Group or Interest Group</cite></a>. URL: <a href="https://www.w3.org/Guide/process/charter.html">https://www.w3.org/Guide/process/charter.html</a>
+   <dt id="biblio-council-report-index">[COUNCIL-REPORT-INDEX]
+   <dd><a href="https://www.w3.org/about/council/"><cite>Council Report Index</cite></a>. URL: <a href="https://www.w3.org/about/council/">https://www.w3.org/about/council/</a>
+   <dt id="biblio-current-ac">[CURRENT-AC]
+   <dd><a href="https://www.w3.org/Member/ACList"><cite>Current Advisory Committee representatives (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/ACList">https://www.w3.org/Member/ACList</a>
+   <dt id="biblio-decision-appeal">[DECISION-APPEAL]
+   <dd><a href="https://www.w3.org/Guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a>. URL: <a href="https://www.w3.org/Guide/process/ac-appeal">https://www.w3.org/Guide/process/ac-appeal</a>
+   <dt id="biblio-election-howto">[ELECTION-HOWTO]
+   <dd><a href="https://www.w3.org/2002/10/election-howto"><cite>How to Organize an Advisory Board or TAG election</cite></a>. URL: <a href="https://www.w3.org/2002/10/election-howto">https://www.w3.org/2002/10/election-howto</a>
+   <dt id="biblio-fellows">[FELLOWS]
+   <dd><a href="https://www.w3.org/Consortium/Recruitment/Fellows"><cite>W3C Fellows Program</cite></a>. URL: <a href="https://www.w3.org/Consortium/Recruitment/Fellows">https://www.w3.org/Consortium/Recruitment/Fellows</a>
+   <dt id="biblio-group-mail">[GROUP-MAIL]
+   <dd><a href="https://www.w3.org/groups/"><cite>Group mailing lists</cite></a>. URL: <a href="https://www.w3.org/groups/">https://www.w3.org/groups/</a>
+   <dt id="biblio-guide">[GUIDE]
+   <dd><a href="https://www.w3.org/Guide/"><cite>The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators</cite></a>. URL: <a href="https://www.w3.org/Guide/">https://www.w3.org/Guide/</a>
+   <dt id="biblio-intro">[INTRO]
+   <dd><a href="https://www.w3.org/Member/Intro"><cite>Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/Intro">https://www.w3.org/Member/Intro</a>
+   <dt id="biblio-join">[JOIN]
+   <dd><a href="https://www.w3.org/Consortium/join"><cite>How to Join W3C</cite></a>. URL: <a href="https://www.w3.org/Consortium/join">https://www.w3.org/Consortium/join</a>
+   <dt id="biblio-liaison">[LIAISON]
+   <dd><a href="https://www.w3.org/2001/11/StdLiaison"><cite>W3C liaisons with other organizations</cite></a>. URL: <a href="https://www.w3.org/2001/11/StdLiaison">https://www.w3.org/2001/11/StdLiaison</a>
+   <dt id="biblio-member-agreement">[MEMBER-AGREEMENT]
+   <dd><a href="https://www.w3.org/Consortium/Agreement/Member-Agreement"><cite>W3C Membership Agreement</cite></a>. URL: <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">https://www.w3.org/Consortium/Agreement/Member-Agreement</a>
+   <dt id="biblio-member-hp">[MEMBER-HP]
+   <dd><a href="https://www.w3.org/Member/"><cite>Member website (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/">https://www.w3.org/Member/</a>
+   <dt id="biblio-member-list">[MEMBER-LIST]
+   <dd><a href="https://www.w3.org/Consortium/Member/List"><cite>The list of current W3C Members</cite></a>. URL: <a href="https://www.w3.org/Consortium/Member/List">https://www.w3.org/Consortium/Member/List</a>
+   <dt id="biblio-member-sub">[MEMBER-SUB]
+   <dd><a href="https://www.w3.org/2000/09/submission"><cite>How to send a Submission request</cite></a>. URL: <a href="https://www.w3.org/2000/09/submission">https://www.w3.org/2000/09/submission</a>
+   <dt id="biblio-mission">[MISSION]
+   <dd><a href="https://www.w3.org/Consortium/mission"><cite>The W3C Mission statement</cite></a>. URL: <a href="https://www.w3.org/Consortium/mission">https://www.w3.org/Consortium/mission</a>
+   <dt id="biblio-obs-resc">[OBS-RESC]
+   <dd><a href="https://www.w3.org/2016/11/obsoleting-rescinding/"><cite>Obsoleting and Rescinding W3C Specifications</cite></a>. URL: <a href="https://www.w3.org/2016/11/obsoleting-rescinding/">https://www.w3.org/2016/11/obsoleting-rescinding/</a>
+   <dt id="biblio-rec-tips">[REC-TIPS]
+   <dd><a href="https://www.w3.org/2002/05/rec-tips"><cite>Tips for Getting to Recommendation Faster</cite></a>. URL: <a href="https://www.w3.org/2002/05/rec-tips">https://www.w3.org/2002/05/rec-tips</a>
+   <dt id="biblio-republishing">[REPUBLISHING]
+   <dd><a href="https://www.w3.org/2003/01/republishing/"><cite>In-place modification of W3C Technical Reports</cite></a>. URL: <a href="https://www.w3.org/2003/01/republishing/">https://www.w3.org/2003/01/republishing/</a>
+   <dt id="biblio-submission-list">[SUBMISSION-LIST]
+   <dd><a href="https://www.w3.org/Submission/"><cite>The list of acknowledged Member Submissions</cite></a>. URL: <a href="https://www.w3.org/Submission/">https://www.w3.org/Submission/</a>
+   <dt id="biblio-submission-req">[SUBMISSION-REQ]
+   <dd><a href="https://www.w3.org/2000/09/submission"><cite>Make or Withdraw a Member Submission Request (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/2000/09/submission">https://www.w3.org/2000/09/submission</a>
+   <dt id="biblio-tag-charter">[TAG-CHARTER]
+   <dd><a href="https://www.w3.org/2004/10/27-tag-charter.html"><cite>Technical Architecture Group (TAG) Charter</cite></a>. URL: <a href="https://www.w3.org/2004/10/27-tag-charter.html">https://www.w3.org/2004/10/27-tag-charter.html</a>
+   <dt id="biblio-tag-hp">[TAG-HP]
+   <dd><a href="https://www.w3.org/2001/tag/"><cite>The TAG home page</cite></a>. URL: <a href="https://www.w3.org/2001/tag/">https://www.w3.org/2001/tag/</a>
+   <dt id="biblio-team-contact">[TEAM-CONTACT]
+   <dd><a href="https://www.w3.org/Guide/teamcontact/role.html"><cite>Role of the Team Contact</cite></a>. URL: <a href="https://www.w3.org/Guide/teamcontact/role.html">https://www.w3.org/Guide/teamcontact/role.html</a>
+   <dt id="biblio-tr">[TR]
+   <dd><a href="https://www.w3.org/TR/"><cite>The W3C technical reports index</cite></a>. URL: <a href="https://www.w3.org/TR/">https://www.w3.org/TR/</a>
+   <dt id="biblio-transition">[TRANSITION]
+   <dd><a href="https://www.w3.org/Guide/transitions"><cite>Organize a Technical Report Transition</cite></a>. URL: <a href="https://www.w3.org/Guide/transitions">https://www.w3.org/Guide/transitions</a>
+   <dt id="biblio-translation">[TRANSLATION]
+   <dd><a href="https://www.w3.org/Consortium/Translation/"><cite>Translations of W3C technical reports</cite></a>. URL: <a href="https://www.w3.org/Consortium/Translation/">https://www.w3.org/Consortium/Translation/</a>
+   <dt id="biblio-w3c-ipr">[W3C-IPR]
+   <dd><a href="https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231"><cite>W3C IPR Policies</cite></a>. URL: <a href="https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231">https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231</a>
+  </dl>
+<script>/* Boilerplate: script-dfn-panel */
+"use strict";
+{
+    const dfnsJson = window.dfnsJson || {};
+
+    function genDfnPanel({dfnID, url, dfnText, refSections, external}) {
+        return mk.aside({
+            class: "dfn-panel",
+            id: `infopanel-for-${dfnID}`,
+            "data-for": dfnID,
+            "aria-labelled-by":`infopaneltitle-for-${dfnID}`,
+            },
+            mk.span({id:`infopaneltitle-for-${dfnID}`, style:"display:none"},
+                `Info about the '${dfnText}' ${external?"external":""} reference.`),
+            mk.a({href:url}, url),
+            mk.b({}, "Referenced in:"),
+            mk.ul({},
+                ...refSections.map(section=>
+                    mk.li({},
+                        ...section.refs.map((ref, refI)=>
+                            [
+                                mk.a({
+                                    href: `#${ref.id}`
+                                    },
+                                    (refI == 0) ? section.title : `(${refI + 1})`
+                                ),
+                                " ",
+                            ]
+                        ),
+                    ),
+                ),
+            ),
+        );
+    }
+
+    function genAllDfnPanels() {
+        for(const panelData of Object.values(window.dfnpanelData)) {
+            const dfnID = panelData.dfnID;
+            const dfn = document.getElementById(dfnID);
+            if(!dfn) {
+                console.log(`Can't find dfn#${dfnID}.`, panelData);
+            } else {
+                const panel = genDfnPanel(panelData);
+                append(document.body, panel);
+                insertDfnPopupAction(dfn, panel)
+            }
+        }
+    }
+
+    document.addEventListener("DOMContentLoaded", ()=>{
+        genAllDfnPanels();
+
+        // Add popup behavior to all dfns to show the corresponding dfn-panel.
+        var dfns = queryAll('.dfn-paneled');
+        for(let dfn of dfns) { ; }
+
+        document.body.addEventListener("click", (e) => {
+            // If not handled already, just hide all dfn panels.
+            hideAllDfnPanels();
+        });
+    })
+
+
+    function hideAllDfnPanels() {
+        // Turn off any currently "on" or "activated" panels.
+        queryAll(".dfn-panel.on, .dfn-panel.activated").forEach(el=>hideDfnPanel(el));
+    }
+
+    function showDfnPanel(dfnPanel, dfn) {
+        hideAllDfnPanels(); // Only display one at this time.
+        dfn.setAttribute("aria-expanded", "true");
+        dfnPanel.classList.add("on");
+        dfnPanel.style.left = "5px";
+        dfnPanel.style.top = "0px";
+        const panelRect = dfnPanel.getBoundingClientRect();
+        const panelWidth = panelRect.right - panelRect.left;
+        if (panelRect.right > document.body.scrollWidth) {
+            // Panel's overflowing the screen.
+            // Just drop it below the dfn and flip it rightward instead.
+            // This still wont' fix things if the screen is *really* wide,
+            // but fixing that's a lot harder without 'anchor()'.
+            dfnPanel.style.top = "1.5em";
+            dfnPanel.style.left = "auto";
+            dfnPanel.style.right = "0px";
+        }
+    }
+
+    function pinDfnPanel(dfnPanel) {
+        // Switch it to "activated" state, which pins it.
+        dfnPanel.classList.add("activated");
+        dfnPanel.style.left = null;
+        dfnPanel.style.top = null;
+    }
+
+    function hideDfnPanel(dfnPanel, dfn) {
+        if(!dfn) {
+            dfn = document.getElementById(dfnPanel.getAttribute("data-for"));
+        }
+        dfn.setAttribute("aria-expanded", "false")
+        dfnPanel.classList.remove("on");
+        dfnPanel.classList.remove("activated");
+    }
+
+    function toggleDfnPanel(dfnPanel, dfn) {
+        if(dfnPanel.classList.contains("on")) {
+            hideDfnPanel(dfnPanel, dfn);
+        } else {
+            showDfnPanel(dfnPanel, dfn);
+        }
+    }
+
+    function insertDfnPopupAction(dfn, dfnPanel) {
+        // Find dfn panel
+        const panelWrapper = document.createElement('span');
+        panelWrapper.appendChild(dfnPanel);
+        panelWrapper.style.position = "relative";
+        panelWrapper.style.height = "0px";
+        dfn.insertAdjacentElement("afterend", panelWrapper);
+        dfn.setAttribute('role', 'button');
+        dfn.setAttribute('aria-expanded', 'false')
+        dfn.tabIndex = 0;
+        dfn.classList.add('has-dfn-panel');
+        dfn.addEventListener('click', (event) => {
+            showDfnPanel(dfnPanel, dfn);
+            event.stopPropagation();
+        });
+        dfn.addEventListener('keypress', (event) => {
+            const kc = event.keyCode;
+            // 32->Space, 13->Enter
+            if(kc == 32 || kc == 13) {
+                toggleDfnPanel(dfnPanel, dfn);
+                event.stopPropagation();
+                event.preventDefault();
+            }
+        });
+
+        dfnPanel.addEventListener('click', (event) => {
+            if (event.target.nodeName == 'A') {
+                pinDfnPanel(dfnPanel);
+            }
+            event.stopPropagation();
+        });
+
+        dfnPanel.addEventListener('keydown', (event) => {
+            if(event.keyCode == 27) { // Escape key
+                hideDfnPanel(dfnPanel, dfn);
+                event.stopPropagation();
+                event.preventDefault();
+            }
+        })
+    }
+}
+</script>
+<script>/* Boilerplate: script-dfn-panel */
+"use strict";
+{
+    const dfnsJson = window.dfnsJson || {};
+
+    function genDfnPanel({dfnID, url, dfnText, refSections, external}) {
+        return mk.aside({
+            class: "dfn-panel",
+            id: `infopanel-for-${dfnID}`,
+            "data-for": dfnID,
+            "aria-labelled-by":`infopaneltitle-for-${dfnID}`,
+            },
+            mk.span({id:`infopaneltitle-for-${dfnID}`, style:"display:none"},
+                `Info about the '${dfnText}' ${external?"external":""} reference.`),
+            mk.a({href:url}, url),
+            mk.b({}, "Referenced in:"),
+            mk.ul({},
+                ...refSections.map(section=>
+                    mk.li({},
+                        ...section.refs.map((ref, refI)=>
+                            [
+                                mk.a({
+                                    href: `#${ref.id}`
+                                    },
+                                    (refI == 0) ? section.title : `(${refI + 1})`
+                                ),
+                                " ",
+                            ]
+                        ),
+                    ),
+                ),
+            ),
+        );
+    }
+
+    function genAllDfnPanels() {
+        for(const panelData of Object.values(window.dfnpanelData)) {
+            const dfnID = panelData.dfnID;
+            const dfn = document.getElementById(dfnID);
+            if(!dfn) {
+                console.log(`Can't find dfn#${dfnID}.`, panelData);
+            } else {
+                const panel = genDfnPanel(panelData);
+                append(document.body, panel);
+                insertDfnPopupAction(dfn, panel)
+            }
+        }
+    }
+
+    document.addEventListener("DOMContentLoaded", ()=>{
+        genAllDfnPanels();
+
+        // Add popup behavior to all dfns to show the corresponding dfn-panel.
+        var dfns = queryAll('.dfn-paneled');
+        for(let dfn of dfns) { ; }
+
+        document.body.addEventListener("click", (e) => {
+            // If not handled already, just hide all dfn panels.
+            hideAllDfnPanels();
+        });
+    })
+
+
+    function hideAllDfnPanels() {
+        // Turn off any currently "on" or "activated" panels.
+        queryAll(".dfn-panel.on, .dfn-panel.activated").forEach(el=>hideDfnPanel(el));
+    }
+
+    function showDfnPanel(dfnPanel, dfn) {
+        hideAllDfnPanels(); // Only display one at this time.
+        dfn.setAttribute("aria-expanded", "true");
+        dfnPanel.classList.add("on");
+        dfnPanel.style.left = "5px";
+        dfnPanel.style.top = "0px";
+        const panelRect = dfnPanel.getBoundingClientRect();
+        const panelWidth = panelRect.right - panelRect.left;
+        if (panelRect.right > document.body.scrollWidth) {
+            // Panel's overflowing the screen.
+            // Just drop it below the dfn and flip it rightward instead.
+            // This still wont' fix things if the screen is *really* wide,
+            // but fixing that's a lot harder without 'anchor()'.
+            dfnPanel.style.top = "1.5em";
+            dfnPanel.style.left = "auto";
+            dfnPanel.style.right = "0px";
+        }
+    }
+
+    function pinDfnPanel(dfnPanel) {
+        // Switch it to "activated" state, which pins it.
+        dfnPanel.classList.add("activated");
+        dfnPanel.style.left = null;
+        dfnPanel.style.top = null;
+    }
+
+    function hideDfnPanel(dfnPanel, dfn) {
+        if(!dfn) {
+            dfn = document.getElementById(dfnPanel.getAttribute("data-for"));
+        }
+        dfn.setAttribute("aria-expanded", "false")
+        dfnPanel.classList.remove("on");
+        dfnPanel.classList.remove("activated");
+    }
+
+    function toggleDfnPanel(dfnPanel, dfn) {
+        if(dfnPanel.classList.contains("on")) {
+            hideDfnPanel(dfnPanel, dfn);
+        } else {
+            showDfnPanel(dfnPanel, dfn);
+        }
+    }
+
+    function insertDfnPopupAction(dfn, dfnPanel) {
+        // Find dfn panel
+        const panelWrapper = document.createElement('span');
+        panelWrapper.appendChild(dfnPanel);
+        panelWrapper.style.position = "relative";
+        panelWrapper.style.height = "0px";
+        dfn.insertAdjacentElement("afterend", panelWrapper);
+        dfn.setAttribute('role', 'button');
+        dfn.setAttribute('aria-expanded', 'false')
+        dfn.tabIndex = 0;
+        dfn.classList.add('has-dfn-panel');
+        dfn.addEventListener('click', (event) => {
+            showDfnPanel(dfnPanel, dfn);
+            event.stopPropagation();
+        });
+        dfn.addEventListener('keypress', (event) => {
+            const kc = event.keyCode;
+            // 32->Space, 13->Enter
+            if(kc == 32 || kc == 13) {
+                toggleDfnPanel(dfnPanel, dfn);
+                event.stopPropagation();
+                event.preventDefault();
+            }
+        });
+
+        dfnPanel.addEventListener('click', (event) => {
+            if (event.target.nodeName == 'A') {
+                pinDfnPanel(dfnPanel);
+            }
+            event.stopPropagation();
+        });
+
+        dfnPanel.addEventListener('keydown', (event) => {
+            if(event.keyCode == 27) { // Escape key
+                hideDfnPanel(dfnPanel, dfn);
+                event.stopPropagation();
+                event.preventDefault();
+            }
+        })
+    }
+}
+</script>
+<script>/* Boilerplate: script-dfn-panel-json */
+window.dfnpanelData = {};
+window.dfnpanelData['b923fc87'] = {"dfnID": "b923fc87", "url": "https://www.w3.org/Consortium/Patent-Policy/#patent-advisory-group", "dfnText": "patent advisory group", "refSections": [{"refs": [{"id": "ref-for-patent-advisory-group"}], "title": "4.6. \nChartered Group Closure"}], "external": true};
+window.dfnpanelData['w3c-member'] = {"dfnID": "w3c-member", "url": "#w3c-member", "dfnText": "W3C Members", "refSections": [{"refs": [{"id": "ref-for-w3c-member"}], "title": "3.2.1. \nRole of the Advisory Committee"}, {"refs": [{"id": "ref-for-w3c-member\u2460"}], "title": "9. \nLiaisons"}], "external": false};
+window.dfnpanelData['member-association'] = {"dfnID": "member-association", "url": "#member-association", "dfnText": "Member Association", "refSections": [{"refs": [{"id": "ref-for-member-association"}, {"id": "ref-for-member-association\u2460"}, {"id": "ref-for-member-association\u2461"}, {"id": "ref-for-member-association\u2462"}, {"id": "ref-for-member-association\u2463"}, {"id": "ref-for-member-association\u2464"}], "title": "2.1.2.1. \nMembership Associations"}], "external": false};
+window.dfnpanelData['related-member'] = {"dfnID": "related-member", "url": "#related-member", "dfnText": "related", "refSections": [{"refs": [{"id": "ref-for-related-member"}], "title": "2.1.2.2. \nRelated Members"}, {"refs": [{"id": "ref-for-related-member\u2460"}, {"id": "ref-for-related-member\u2461"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}, {"refs": [{"id": "ref-for-related-member\u2462"}], "title": "5.8. \nAdvisory Committee Votes"}], "external": false};
+window.dfnpanelData['subsidiary'] = {"dfnID": "subsidiary", "url": "#subsidiary", "dfnText": "subsidiary", "refSections": [{"refs": [{"id": "ref-for-subsidiary"}, {"id": "ref-for-subsidiary\u2460"}], "title": "2.1.2.2. \nRelated Members"}], "external": false};
+window.dfnpanelData['team'] = {"dfnID": "team", "url": "#team", "dfnText": "Team", "refSections": [{"refs": [{"id": "ref-for-team"}, {"id": "ref-for-team\u2460"}, {"id": "ref-for-team\u2461"}], "title": "1. \nIntroduction"}, {"refs": [{"id": "ref-for-team\u2462"}, {"id": "ref-for-team\u2463"}], "title": "2.2. \nThe W3C Team"}, {"refs": [{"id": "ref-for-team\u2464"}, {"id": "ref-for-team\u2465"}, {"id": "ref-for-team\u2466"}], "title": "3.1.1.2. \nConflict of Interest Policy"}, {"refs": [{"id": "ref-for-team\u2467"}], "title": "3.1.3. \nTooling and Archiving for Discussions and Publications"}, {"refs": [{"id": "ref-for-team\u2468"}, {"id": "ref-for-team\u2460\u24ea"}], "title": "3.1.4. \nResignation from a Group"}, {"refs": [{"id": "ref-for-team\u2460\u2460"}], "title": "3.2.1. \nRole of the Advisory Committee"}, {"refs": [{"id": "ref-for-team\u2460\u2461"}, {"id": "ref-for-team\u2460\u2462"}, {"id": "ref-for-team\u2460\u2463"}], "title": "3.2.3. \nAdvisory Committee Mailing Lists"}, {"refs": [{"id": "ref-for-team\u2460\u2464"}, {"id": "ref-for-team\u2460\u2465"}, {"id": "ref-for-team\u2460\u2466"}], "title": "3.2.4. \nAdvisory Committee Meetings"}, {"refs": [{"id": "ref-for-team\u2460\u2467"}], "title": "3.3.1.2. \nComposition of the Advisory Board"}, {"refs": [{"id": "ref-for-team\u2460\u2468"}], "title": "3.3.1.3. \nCommunications of the Advisory Board"}, {"refs": [{"id": "ref-for-team\u2461\u24ea"}, {"id": "ref-for-team\u2461\u2460"}], "title": "3.3.2.2. \nComposition of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-team\u2461\u2461"}], "title": "3.3.2.3. \nCommunications of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-team\u2461\u2462"}], "title": "3.3.3.1. \nExpectations for Elected Groups Participants"}, {"refs": [{"id": "ref-for-team\u2461\u2463"}, {"id": "ref-for-team\u2461\u2464"}, {"id": "ref-for-team\u2461\u2465"}, {"id": "ref-for-team\u2461\u2466"}, {"id": "ref-for-team\u2461\u2467"}, {"id": "ref-for-team\u2461\u2468"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}, {"refs": [{"id": "ref-for-team\u2462\u24ea"}, {"id": "ref-for-team\u2462\u2460"}, {"id": "ref-for-team\u2462\u2461"}, {"id": "ref-for-team\u2462\u2462"}, {"id": "ref-for-team\u2462\u2463"}, {"id": "ref-for-team\u2462\u2464"}], "title": "3.3.3.4. \nTechnical Architecture Group Appointments"}, {"refs": [{"id": "ref-for-team\u2462\u2465"}], "title": "3.3.3.6. \nElected Groups Vacated Seats"}, {"refs": [{"id": "ref-for-team\u2462\u2466"}, {"id": "ref-for-team\u2462\u2467"}], "title": "3.4.1. \nRequirements for All Chartered Groups"}, {"refs": [{"id": "ref-for-team\u2462\u2468"}, {"id": "ref-for-team\u2463\u24ea"}], "title": "4.3. \nAdvisory Committee Review of a Charter"}, {"refs": [{"id": "ref-for-team\u2463\u2460"}], "title": "4.4. \nCall for Participation in a Chartered Group"}, {"refs": [{"id": "ref-for-team\u2463\u2461"}, {"id": "ref-for-team\u2463\u2462"}], "title": "4.5. \nCharter Extension"}, {"refs": [{"id": "ref-for-team\u2463\u2463"}], "title": "4.6. \nChartered Group Closure"}, {"refs": [{"id": "ref-for-team\u2463\u2464"}, {"id": "ref-for-team\u2463\u2465"}], "title": "5.1. \nTypes of Decisions"}, {"refs": [{"id": "ref-for-team\u2463\u2466"}], "title": "5.5. \nRegistering Formal Objections"}, {"refs": [{"id": "ref-for-team\u2463\u2467"}, {"id": "ref-for-team\u2463\u2468"}, {"id": "ref-for-team\u2464\u24ea"}], "title": "5.6.1. \nInvestigation and Mediation by the Team"}, {"refs": [{"id": "ref-for-team\u2464\u2460"}], "title": "5.6.2. \nW3C Council"}, {"refs": [{"id": "ref-for-team\u2464\u2461"}, {"id": "ref-for-team\u2464\u2462"}], "title": "5.6.2.1. \nCouncil Composition"}, {"refs": [{"id": "ref-for-team\u2464\u2463"}, {"id": "ref-for-team\u2464\u2464"}, {"id": "ref-for-team\u2464\u2465"}], "title": "5.6.2.2. \nExtraordinary Delegation"}, {"refs": [{"id": "ref-for-team\u2464\u2466"}, {"id": "ref-for-team\u2464\u2467"}, {"id": "ref-for-team\u2464\u2468"}], "title": "5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"}, {"refs": [{"id": "ref-for-team\u2465\u24ea"}, {"id": "ref-for-team\u2465\u2460"}, {"id": "ref-for-team\u2465\u2461"}, {"id": "ref-for-team\u2465\u2462"}, {"id": "ref-for-team\u2465\u2463"}], "title": "5.6.2.6. \nCouncil Deliberations"}, {"refs": [{"id": "ref-for-team\u2465\u2464"}], "title": "5.6.2.7. \nCouncil Decision Report"}, {"refs": [{"id": "ref-for-team\u2465\u2465"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-team\u2465\u2466"}, {"id": "ref-for-team\u2465\u2467"}, {"id": "ref-for-team\u2465\u2468"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-team\u2466\u24ea"}, {"id": "ref-for-team\u2466\u2460"}, {"id": "ref-for-team\u2466\u2461"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}, {"refs": [{"id": "ref-for-team\u2466\u2462"}], "title": "6.2.2.1. \nWide Review"}, {"refs": [{"id": "ref-for-team\u2466\u2463"}, {"id": "ref-for-team\u2466\u2464"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-team\u2466\u2465"}], "title": "6.2.6. \nLicense Grants from Non-Participants"}, {"refs": [{"id": "ref-for-team\u2466\u2466"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-team\u2466\u2467"}], "title": "6.3.2. \nImplementation Experience"}, {"refs": [{"id": "ref-for-team\u2466\u2468"}, {"id": "ref-for-team\u2467\u24ea"}, {"id": "ref-for-team\u2467\u2460"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-team\u2467\u2461"}, {"id": "ref-for-team\u2467\u2462"}, {"id": "ref-for-team\u2467\u2463"}, {"id": "ref-for-team\u2467\u2464"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-team\u2467\u2465"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-team\u2467\u2466"}], "title": "6.3.5. \nPublishing a First Public Working Draft"}, {"refs": [{"id": "ref-for-team\u2467\u2467"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}, {"refs": [{"id": "ref-for-team\u2467\u2468"}], "title": "6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"}, {"refs": [{"id": "ref-for-team\u2468\u24ea"}, {"id": "ref-for-team\u2468\u2460"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-team\u2468\u2461"}, {"id": "ref-for-team\u2468\u2462"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}, {"refs": [{"id": "ref-for-team\u2468\u2463"}], "title": "6.3.11.1. \nRevising a Recommendation: Markup Changes"}, {"refs": [{"id": "ref-for-team\u2468\u2464"}], "title": "6.3.11.2. \nRevising a Recommendation: Editorial Changes"}, {"refs": [{"id": "ref-for-team\u2468\u2465"}], "title": "6.3.11.3. \nRevising a Recommendation: Substantive Changes"}, {"refs": [{"id": "ref-for-team\u2468\u2466"}], "title": "6.3.12. \nRegression on the Recommendation Track"}, {"refs": [{"id": "ref-for-team\u2468\u2467"}, {"id": "ref-for-team\u2468\u2468"}, {"id": "ref-for-team\u2460\u24ea\u24ea"}, {"id": "ref-for-team\u2460\u24ea\u2460"}, {"id": "ref-for-team\u2460\u24ea\u2461"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-team\u2460\u24ea\u2462"}], "title": "6.4.2. \nPublishing Notes"}, {"refs": [{"id": "ref-for-team\u2460\u24ea\u2463"}, {"id": "ref-for-team\u2460\u24ea\u2464"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-team\u2460\u24ea\u2465"}], "title": "6.5.1. \nRegistry Definitions"}, {"refs": [{"id": "ref-for-team\u2460\u24ea\u2466"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-team\u2460\u24ea\u2467"}], "title": "6.5.4. \nRegistry Data Reports"}, {"refs": [{"id": "ref-for-team\u2460\u24ea\u2468"}, {"id": "ref-for-team\u2460\u2460\u24ea"}], "title": "7.1. \nPublic Communication"}, {"refs": [{"id": "ref-for-team\u2460\u2460\u2460"}], "title": "7.2. \nConfidentiality Levels"}, {"refs": [{"id": "ref-for-team\u2460\u2460\u2461"}, {"id": "ref-for-team\u2460\u2460\u2462"}, {"id": "ref-for-team\u2460\u2460\u2463"}, {"id": "ref-for-team\u2460\u2460\u2464"}], "title": "7.3. \nChanging Confidentiality Level"}, {"refs": [{"id": "ref-for-team\u2460\u2460\u2465"}, {"id": "ref-for-team\u2460\u2460\u2466"}], "title": "9. \nLiaisons"}, {"refs": [{"id": "ref-for-team\u2460\u2460\u2467"}, {"id": "ref-for-team\u2460\u2460\u2468"}, {"id": "ref-for-team\u2460\u2461\u24ea"}, {"id": "ref-for-team\u2460\u2461\u2460"}], "title": "10. \nMember Submission Process"}, {"refs": [{"id": "ref-for-team\u2460\u2461\u2461"}, {"id": "ref-for-team\u2460\u2461\u2462"}, {"id": "ref-for-team\u2460\u2461\u2463"}], "title": "10.2. \nTeam Rights and Obligations"}, {"refs": [{"id": "ref-for-team\u2460\u2461\u2464"}, {"id": "ref-for-team\u2460\u2461\u2465"}, {"id": "ref-for-team\u2460\u2461\u2466"}], "title": "10.3. \nAcknowledgment of a Submission Request"}, {"refs": [{"id": "ref-for-team\u2460\u2461\u2467"}, {"id": "ref-for-team\u2460\u2461\u2468"}, {"id": "ref-for-team\u2460\u2462\u24ea"}, {"id": "ref-for-team\u2460\u2462\u2460"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}, {"refs": [{"id": "ref-for-team\u2460\u2462\u2461"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['ceo'] = {"dfnID": "ceo", "url": "#ceo", "dfnText": "CEO", "refSections": [{"refs": [{"id": "ref-for-ceo"}], "title": "2.1.2.1. \nMembership Associations"}, {"refs": [{"id": "ref-for-ceo\u2460"}], "title": "2.2. \nThe W3C Team"}, {"refs": [{"id": "ref-for-ceo\u2461"}], "title": "3.1.1.1. \nExpectations and Discipline"}, {"refs": [{"id": "ref-for-ceo\u2462"}], "title": "3.1.1.3. \nIndividuals Representing a Member Organization"}, {"refs": [{"id": "ref-for-ceo\u2463"}], "title": "3.3.3.6. \nElected Groups Vacated Seats"}, {"refs": [{"id": "ref-for-ceo\u2464"}, {"id": "ref-for-ceo\u2465"}], "title": "3.4.3.3. \nInvited Expert in a Working Group"}, {"refs": [{"id": "ref-for-ceo\u2466"}], "title": "5.5. \nRegistering Formal Objections"}, {"refs": [{"id": "ref-for-ceo\u2467"}], "title": "5.6.2.1. \nCouncil Composition"}], "external": false};
+window.dfnpanelData['fellows'] = {"dfnID": "fellows", "url": "#fellows", "dfnText": "W3C Fellows", "refSections": [{"refs": [{"id": "ref-for-fellows"}], "title": "2.1.1. \nRights of Members"}, {"refs": [{"id": "ref-for-fellows"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}], "external": false};
+window.dfnpanelData['bod'] = {"dfnID": "bod", "url": "#bod", "dfnText": "W3C Board of Directors", "refSections": [{"refs": [{"id": "ref-for-bod"}], "title": "2.2. \nThe W3C Team"}, {"refs": [{"id": "ref-for-bod\u2460"}], "title": "3.3.1.1. \nRole of the Advisory Board"}, {"refs": [{"id": "ref-for-bod\u2461"}, {"id": "ref-for-bod\u2462"}, {"id": "ref-for-bod\u2463"}, {"id": "ref-for-bod\u2464"}, {"id": "ref-for-bod\u2465"}], "title": "3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"}, {"refs": [{"id": "ref-for-bod\u2466"}, {"id": "ref-for-bod\u2467"}], "title": "9. \nLiaisons"}], "external": false};
+window.dfnpanelData['w3c-group'] = {"dfnID": "w3c-group", "url": "#w3c-group", "dfnText": "W3C Group", "refSections": [{"refs": [{"id": "ref-for-w3c-group"}], "title": "3.1.2. \nMeetings"}, {"refs": [{"id": "ref-for-w3c-group\u2460"}], "title": "3.1.3. \nTooling and Archiving for Discussions and Publications"}, {"refs": [{"id": "ref-for-w3c-group\u2461"}, {"id": "ref-for-w3c-group\u2462"}], "title": "5.7.2. \nAfter the Review Period"}], "external": false};
+window.dfnpanelData['participant'] = {"dfnID": "participant", "url": "#participant", "dfnText": "participant", "refSections": [{"refs": [{"id": "ref-for-participant"}], "title": "3.1.2. \nMeetings"}, {"refs": [{"id": "ref-for-participant\u2460"}], "title": "5.2.3. \nDeciding by Vote"}], "external": false};
+window.dfnpanelData['ftf-meeting'] = {"dfnID": "ftf-meeting", "url": "#ftf-meeting", "dfnText": "face-to-face meeting", "refSections": [{"refs": [{"id": "ref-for-ftf-meeting"}], "title": "3.2.4. \nAdvisory Committee Meetings"}, {"refs": [{"id": "ref-for-ftf-meeting"}], "title": "4.2. \nContent of a Charter"}, {"refs": [{"id": "ref-for-ftf-meeting"}], "title": "5.2.1. \nConsensus"}, {"refs": [{"id": "ref-for-ftf-meeting"}], "title": "5.6.2.1. \nCouncil Composition"}], "external": false};
+window.dfnpanelData['distributed-meeting'] = {"dfnID": "distributed-meeting", "url": "#distributed-meeting", "dfnText": "distributed meeting", "refSections": [{"refs": [{"id": "ref-for-distributed-meeting"}], "title": "5.2.1. \nConsensus"}], "external": false};
+window.dfnpanelData['minutes'] = {"dfnID": "minutes", "url": "#minutes", "dfnText": "minutes", "refSections": [{"refs": [{"id": "ref-for-minutes"}], "title": "3.1.2.1. \nMeeting Scheduling and Announcements"}, {"refs": [{"id": "ref-for-minutes\u2460"}], "title": "3.4.1. \nRequirements for All Chartered Groups"}, {"refs": [{"id": "ref-for-minutes\u2461"}], "title": "5.2.3. \nDeciding by Vote"}, {"refs": [{"id": "ref-for-minutes\u2462"}], "title": "8. \nWorkshops and Symposia"}], "external": false};
+window.dfnpanelData['advisory-committee'] = {"dfnID": "advisory-committee", "url": "#advisory-committee", "dfnText": "Advisory Committee", "refSections": [{"refs": [{"id": "ref-for-advisory-committee"}], "title": "2.1. \nMembers"}, {"refs": [{"id": "ref-for-advisory-committee\u2460"}], "title": "3.2.2. \nParticipation in the Advisory Committee"}, {"refs": [{"id": "ref-for-advisory-committee\u2461"}, {"id": "ref-for-advisory-committee\u2462"}], "title": "3.2.3. \nAdvisory Committee Mailing Lists"}, {"refs": [{"id": "ref-for-advisory-committee\u2463"}], "title": "3.2.4. \nAdvisory Committee Meetings"}, {"refs": [{"id": "ref-for-advisory-committee\u2464"}], "title": "3.3. \nElected Groups: The AB and the TAG"}, {"refs": [{"id": "ref-for-advisory-committee\u2465"}], "title": "3.3.1.2. \nComposition of the Advisory Board"}, {"refs": [{"id": "ref-for-advisory-committee\u2466"}], "title": "3.3.2.2. \nComposition of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-advisory-committee\u2467"}, {"id": "ref-for-advisory-committee\u2468"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}, {"refs": [{"id": "ref-for-advisory-committee\u2460\u24ea"}], "title": "3.3.3.4. \nTechnical Architecture Group Appointments"}, {"refs": [{"id": "ref-for-advisory-committee\u2460\u2460"}], "title": "4.3. \nAdvisory Committee Review of a Charter"}, {"refs": [{"id": "ref-for-advisory-committee\u2460\u2461"}], "title": "4.5. \nCharter Extension"}, {"refs": [{"id": "ref-for-advisory-committee\u2460\u2462"}], "title": "5.6.2.2. \nExtraordinary Delegation"}, {"refs": [{"id": "ref-for-advisory-committee\u2460\u2463"}], "title": "5.6.2.6. \nCouncil Deliberations"}, {"refs": [{"id": "ref-for-advisory-committee\u2460\u2464"}], "title": "5.7. \nAdvisory Committee Reviews"}, {"refs": [{"id": "ref-for-advisory-committee\u2460\u2465"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-advisory-committee\u2460\u2466"}, {"id": "ref-for-advisory-committee\u2460\u2467"}, {"id": "ref-for-advisory-committee\u2460\u2468"}, {"id": "ref-for-advisory-committee\u2461\u24ea"}, {"id": "ref-for-advisory-committee\u2461\u2460"}, {"id": "ref-for-advisory-committee\u2461\u2461"}, {"id": "ref-for-advisory-committee\u2461\u2462"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-advisory-committee\u2461\u2463"}, {"id": "ref-for-advisory-committee\u2461\u2464"}], "title": "5.8. \nAdvisory Committee Votes"}, {"refs": [{"id": "ref-for-advisory-committee\u2461\u2465"}, {"id": "ref-for-advisory-committee\u2461\u2466"}, {"id": "ref-for-advisory-committee\u2461\u2467"}, {"id": "ref-for-advisory-committee\u2461\u2468"}, {"id": "ref-for-advisory-committee\u2462\u24ea"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2460"}], "title": "6.2.1. \nPublication of Technical Reports"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2461"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2462"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2463"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2464"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2465"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2466"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2467"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-advisory-committee\u2462\u2468"}, {"id": "ref-for-advisory-committee\u2463\u24ea"}], "title": "9. \nLiaisons"}, {"refs": [{"id": "ref-for-advisory-committee\u2463\u2460"}], "title": "10.3. \nAcknowledgment of a Submission Request"}, {"refs": [{"id": "ref-for-advisory-committee\u2463\u2461"}, {"id": "ref-for-advisory-committee\u2463\u2462"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['advisory-committee-representative'] = {"dfnID": "advisory-committee-representative", "url": "#advisory-committee-representative", "dfnText": "representative", "refSections": [{"refs": [{"id": "ref-for-advisory-committee-representative"}], "title": "3.1.1.1. \nExpectations and Discipline"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2460"}], "title": "3.1.1.3. \nIndividuals Representing a Member Organization"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461"}, {"id": "ref-for-advisory-committee-representative\u2462"}], "title": "3.2.1. \nRole of the Advisory Committee"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2463"}, {"id": "ref-for-advisory-committee-representative\u2464"}], "title": "3.2.2. \nParticipation in the Advisory Committee"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2465"}, {"id": "ref-for-advisory-committee-representative\u2466"}], "title": "3.2.3. \nAdvisory Committee Mailing Lists"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2467"}, {"id": "ref-for-advisory-committee-representative\u2468"}, {"id": "ref-for-advisory-committee-representative\u2460\u24ea"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2460\u2460"}], "title": "3.4.3.1. \nMember Representative in a Working Group"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2460\u2461"}], "title": "3.4.3.2. \nMember Representative in an Interest Group"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2460\u2462"}], "title": "5.6.2.8. \nAppealing Council Decisions"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2460\u2463"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2460\u2464"}, {"id": "ref-for-advisory-committee-representative\u2460\u2465"}, {"id": "ref-for-advisory-committee-representative\u2460\u2466"}, {"id": "ref-for-advisory-committee-representative\u2460\u2467"}, {"id": "ref-for-advisory-committee-representative\u2460\u2468"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461\u24ea"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461\u2460"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461\u2461"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461\u2462"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461\u2463"}, {"id": "ref-for-advisory-committee-representative\u2461\u2464"}], "title": "7.2. \nConfidentiality Levels"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461\u2465"}], "title": "7.3. \nChanging Confidentiality Level"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461\u2466"}], "title": "9. \nLiaisons"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2461\u2467"}, {"id": "ref-for-advisory-committee-representative\u2461\u2468"}], "title": "10.1. \nSubmitter Rights and Obligations"}, {"refs": [{"id": "ref-for-advisory-committee-representative\u2462\u24ea"}, {"id": "ref-for-advisory-committee-representative\u2462\u2460"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}], "external": false};
+window.dfnpanelData['advisory-board'] = {"dfnID": "advisory-board", "url": "#advisory-board", "dfnText": "Advisory Board", "refSections": [{"refs": [{"id": "ref-for-advisory-board"}], "title": "3.1.1.1. \nExpectations and Discipline"}, {"refs": [{"id": "ref-for-advisory-board\u2460"}], "title": "3.3. \nElected Groups: The AB and the TAG"}, {"refs": [{"id": "ref-for-advisory-board\u2461"}, {"id": "ref-for-advisory-board\u2462"}, {"id": "ref-for-advisory-board\u2463"}], "title": "3.3.1.1. \nRole of the Advisory Board"}, {"refs": [{"id": "ref-for-advisory-board\u2464"}, {"id": "ref-for-advisory-board\u2465"}, {"id": "ref-for-advisory-board\u2466"}], "title": "3.3.1.2. \nComposition of the Advisory Board"}, {"refs": [{"id": "ref-for-advisory-board\u2467"}], "title": "3.3.1.3. \nCommunications of the Advisory Board"}, {"refs": [{"id": "ref-for-advisory-board\u2468"}, {"id": "ref-for-advisory-board\u2460\u24ea"}, {"id": "ref-for-advisory-board\u2460\u2460"}], "title": "3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"}, {"refs": [{"id": "ref-for-advisory-board\u2460\u2461"}], "title": "3.3.3.1. \nExpectations for Elected Groups Participants"}, {"refs": [{"id": "ref-for-advisory-board\u2460\u2462"}, {"id": "ref-for-advisory-board\u2460\u2463"}, {"id": "ref-for-advisory-board\u2460\u2464"}], "title": "3.3.3.2. \nElected Groups Participation Constraints"}, {"refs": [{"id": "ref-for-advisory-board\u2460\u2465"}, {"id": "ref-for-advisory-board\u2460\u2466"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}, {"refs": [{"id": "ref-for-advisory-board\u2460\u2467"}], "title": "3.3.3.4. \nTechnical Architecture Group Appointments"}, {"refs": [{"id": "ref-for-advisory-board\u2460\u2468"}], "title": "3.3.3.5. \nVerifiable Random Selection Procedure"}, {"refs": [{"id": "ref-for-advisory-board\u2461\u24ea"}, {"id": "ref-for-advisory-board\u2461\u2460"}, {"id": "ref-for-advisory-board\u2461\u2461"}], "title": "3.3.3.6. \nElected Groups Vacated Seats"}, {"refs": [{"id": "ref-for-advisory-board\u2461\u2462"}, {"id": "ref-for-advisory-board\u2461\u2463"}], "title": "4.6. \nChartered Group Closure"}, {"refs": [{"id": "ref-for-advisory-board\u2461\u2464"}], "title": "5.6.2. \nW3C Council"}, {"refs": [{"id": "ref-for-advisory-board\u2461\u2465"}, {"id": "ref-for-advisory-board\u2461\u2466"}], "title": "5.6.2.1. \nCouncil Composition"}, {"refs": [{"id": "ref-for-advisory-board\u2461\u2467"}, {"id": "ref-for-advisory-board\u2461\u2468"}], "title": "5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"}, {"refs": [{"id": "ref-for-advisory-board\u2462\u24ea"}], "title": "6.3.12. \nRegression on the Recommendation Track"}, {"refs": [{"id": "ref-for-advisory-board\u2462\u2460"}], "title": "6.4.1. \nGroup Notes"}, {"refs": [{"id": "ref-for-advisory-board\u2462\u2461"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}, {"refs": [{"id": "ref-for-advisory-board\u2462\u2462"}, {"id": "ref-for-advisory-board\u2462\u2463"}, {"id": "ref-for-advisory-board\u2462\u2464"}, {"id": "ref-for-advisory-board\u2462\u2465"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['technical-architecture-group'] = {"dfnID": "technical-architecture-group", "url": "#technical-architecture-group", "dfnText": "TAG", "refSections": [{"refs": [{"id": "ref-for-technical-architecture-group"}], "title": "3.1.1.1. \nExpectations and Discipline"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2460"}], "title": "3.3. \nElected Groups: The AB and the TAG"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2461"}, {"id": "ref-for-technical-architecture-group\u2462"}, {"id": "ref-for-technical-architecture-group\u2463"}, {"id": "ref-for-technical-architecture-group\u2464"}], "title": "3.3.2.1. \nRole of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2465"}, {"id": "ref-for-technical-architecture-group\u2466"}], "title": "3.3.2.2. \nComposition of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2467"}, {"id": "ref-for-technical-architecture-group\u2468"}, {"id": "ref-for-technical-architecture-group\u2460\u24ea"}, {"id": "ref-for-technical-architecture-group\u2460\u2460"}], "title": "3.3.2.3. \nCommunications of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2460\u2461"}], "title": "3.3.3.1. \nExpectations for Elected Groups Participants"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2460\u2462"}], "title": "3.3.3.2. \nElected Groups Participation Constraints"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2460\u2463"}, {"id": "ref-for-technical-architecture-group\u2460\u2464"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2460\u2465"}, {"id": "ref-for-technical-architecture-group\u2460\u2466"}, {"id": "ref-for-technical-architecture-group\u2460\u2467"}, {"id": "ref-for-technical-architecture-group\u2460\u2468"}, {"id": "ref-for-technical-architecture-group\u2461\u24ea"}, {"id": "ref-for-technical-architecture-group\u2461\u2460"}, {"id": "ref-for-technical-architecture-group\u2461\u2461"}], "title": "3.3.3.4. \nTechnical Architecture Group Appointments"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2461\u2462"}], "title": "3.3.3.5. \nVerifiable Random Selection Procedure"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2461\u2463"}, {"id": "ref-for-technical-architecture-group\u2461\u2464"}, {"id": "ref-for-technical-architecture-group\u2461\u2465"}, {"id": "ref-for-technical-architecture-group\u2461\u2466"}], "title": "3.3.3.6. \nElected Groups Vacated Seats"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2461\u2467"}, {"id": "ref-for-technical-architecture-group\u2461\u2468"}], "title": "4.6. \nChartered Group Closure"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2462\u24ea"}], "title": "5.6.2. \nW3C Council"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2462\u2460"}, {"id": "ref-for-technical-architecture-group\u2462\u2461"}], "title": "5.6.2.1. \nCouncil Composition"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2462\u2462"}, {"id": "ref-for-technical-architecture-group\u2462\u2463"}], "title": "5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2462\u2464"}], "title": "6.3.12. \nRegression on the Recommendation Track"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2462\u2465"}, {"id": "ref-for-technical-architecture-group\u2462\u2466"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2462\u2467"}], "title": "6.4.1. \nGroup Notes"}, {"refs": [{"id": "ref-for-technical-architecture-group\u2462\u2468"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}], "external": false};
+window.dfnpanelData['primary-affiliation'] = {"dfnID": "primary-affiliation", "url": "#primary-affiliation", "dfnText": "primary affiliation", "refSections": [{"refs": [{"id": "ref-for-primary-affiliation"}, {"id": "ref-for-primary-affiliation\u2460"}], "title": "3.3.3.2. \nElected Groups Participation Constraints"}, {"refs": [{"id": "ref-for-primary-affiliation\u2461"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}], "external": false};
+window.dfnpanelData['chartered-group'] = {"dfnID": "chartered-group", "url": "#chartered-group", "dfnText": "chartered groups", "refSections": [{"refs": [{"id": "ref-for-chartered-group"}], "title": "4.1. \nInitiating Charter Development"}, {"refs": [{"id": "ref-for-chartered-group\u2460"}], "title": "6.4.2. \nPublishing Notes"}], "external": false};
+window.dfnpanelData['GroupsWG'] = {"dfnID": "GroupsWG", "url": "#GroupsWG", "dfnText": "Working Groups", "refSections": [{"refs": [{"id": "ref-for-GroupsWG"}, {"id": "ref-for-GroupsWG\u2460"}], "title": "1. \nIntroduction"}, {"refs": [{"id": "ref-for-GroupsWG\u2461"}], "title": "3.1.3. \nTooling and Archiving for Discussions and Publications"}, {"refs": [{"id": "ref-for-GroupsWG\u2462"}], "title": "3.3.3.4. \nTechnical Architecture Group Appointments"}, {"refs": [{"id": "ref-for-GroupsWG"}], "title": "3.4. \nChartered Groups: Working Groups and Interest Groups"}, {"refs": [{"id": "ref-for-GroupsWG\u2463"}], "title": "3.4.2. \nParticipation in Chartered Groups"}, {"refs": [{"id": "ref-for-GroupsWG\u2464"}, {"id": "ref-for-GroupsWG\u2465"}], "title": "3.4.3.1. \nMember Representative in a Working Group"}, {"refs": [{"id": "ref-for-GroupsWG\u2466"}], "title": "3.4.3.3. \nInvited Expert in a Working Group"}, {"refs": [{"id": "ref-for-GroupsWG\u2467"}, {"id": "ref-for-GroupsWG\u2468"}], "title": "4.4. \nCall for Participation in a Chartered Group"}, {"refs": [{"id": "ref-for-GroupsWG\u2460\u24ea"}], "title": "4.6. \nChartered Group Closure"}, {"refs": [{"id": "ref-for-GroupsWG\u2460\u2460"}, {"id": "ref-for-GroupsWG\u2460\u2461"}], "title": "5.1. \nTypes of Decisions"}, {"refs": [{"id": "ref-for-GroupsWG\u2460\u2462"}], "title": "6. \nW3C Technical Reports"}, {"refs": [{"id": "ref-for-GroupsWG\u2460\u2463"}, {"id": "ref-for-GroupsWG\u2460\u2464"}, {"id": "ref-for-GroupsWG\u2460\u2465"}, {"id": "ref-for-GroupsWG\u2460\u2466"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-GroupsWG\u2460\u2467"}], "title": "6.2.1. \nPublication of Technical Reports"}, {"refs": [{"id": "ref-for-GroupsWG\u2460\u2468"}, {"id": "ref-for-GroupsWG\u2461\u24ea"}], "title": "6.2.2. \nReviews and Review Responsibilities"}, {"refs": [{"id": "ref-for-GroupsWG\u2461\u2460"}, {"id": "ref-for-GroupsWG\u2461\u2461"}, {"id": "ref-for-GroupsWG\u2461\u2462"}, {"id": "ref-for-GroupsWG\u2461\u2463"}], "title": "6.2.2.1. \nWide Review"}, {"refs": [{"id": "ref-for-GroupsWG\u2461\u2464"}, {"id": "ref-for-GroupsWG\u2461\u2465"}, {"id": "ref-for-GroupsWG\u2461\u2466"}, {"id": "ref-for-GroupsWG\u2461\u2467"}], "title": "6.2.4. \nErrata Management"}, {"refs": [{"id": "ref-for-GroupsWG\u2461\u2468"}, {"id": "ref-for-GroupsWG\u2462\u24ea"}, {"id": "ref-for-GroupsWG\u2462\u2460"}, {"id": "ref-for-GroupsWG\u2462\u2461"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-GroupsWG\u2462\u2462"}, {"id": "ref-for-GroupsWG\u2462\u2463"}, {"id": "ref-for-GroupsWG\u2462\u2464"}, {"id": "ref-for-GroupsWG\u2462\u2465"}, {"id": "ref-for-GroupsWG\u2462\u2466"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-GroupsWG\u2462\u2467"}, {"id": "ref-for-GroupsWG\u2462\u2468"}, {"id": "ref-for-GroupsWG\u2463\u24ea"}, {"id": "ref-for-GroupsWG\u2463\u2460"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-GroupsWG\u2463\u2461"}, {"id": "ref-for-GroupsWG\u2463\u2462"}, {"id": "ref-for-GroupsWG\u2463\u2463"}, {"id": "ref-for-GroupsWG\u2463\u2464"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-GroupsWG\u2463\u2465"}, {"id": "ref-for-GroupsWG\u2463\u2466"}, {"id": "ref-for-GroupsWG\u2463\u2467"}, {"id": "ref-for-GroupsWG\u2463\u2468"}, {"id": "ref-for-GroupsWG\u2464\u24ea"}, {"id": "ref-for-GroupsWG\u2464\u2460"}, {"id": "ref-for-GroupsWG\u2464\u2461"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-GroupsWG\u2464\u2462"}], "title": "6.3.5. \nPublishing a First Public Working Draft"}, {"refs": [{"id": "ref-for-GroupsWG\u2464\u2463"}], "title": "6.3.6. \nRevising a Working Draft"}, {"refs": [{"id": "ref-for-GroupsWG\u2464\u2464"}, {"id": "ref-for-GroupsWG\u2464\u2465"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}, {"refs": [{"id": "ref-for-GroupsWG\u2464\u2466"}], "title": "6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"}, {"refs": [{"id": "ref-for-GroupsWG\u2464\u2467"}], "title": "6.3.8.2. \nPublishing a Candidate Recommendation Draft"}, {"refs": [{"id": "ref-for-GroupsWG\u2464\u2468"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-GroupsWG\u2465\u24ea"}, {"id": "ref-for-GroupsWG\u2465\u2460"}], "title": "6.3.11.1. \nRevising a Recommendation: Markup Changes"}, {"refs": [{"id": "ref-for-GroupsWG\u2465\u2461"}, {"id": "ref-for-GroupsWG\u2465\u2462"}], "title": "6.3.11.2. \nRevising a Recommendation: Editorial Changes"}, {"refs": [{"id": "ref-for-GroupsWG\u2465\u2463"}, {"id": "ref-for-GroupsWG\u2465\u2464"}, {"id": "ref-for-GroupsWG\u2465\u2465"}], "title": "6.3.11.3. \nRevising a Recommendation: Substantive Changes"}, {"refs": [{"id": "ref-for-GroupsWG\u2465\u2466"}, {"id": "ref-for-GroupsWG\u2465\u2467"}, {"id": "ref-for-GroupsWG\u2465\u2468"}, {"id": "ref-for-GroupsWG\u2466\u24ea"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-GroupsWG\u2466\u2460"}], "title": "6.3.12. \nRegression on the Recommendation Track"}, {"refs": [{"id": "ref-for-GroupsWG\u2466\u2461"}], "title": "6.3.13. \nRetiring Recommendation Track Documents"}, {"refs": [{"id": "ref-for-GroupsWG\u2466\u2462"}, {"id": "ref-for-GroupsWG\u2466\u2463"}, {"id": "ref-for-GroupsWG\u2466\u2464"}, {"id": "ref-for-GroupsWG\u2466\u2465"}], "title": "6.3.13.1. \nAbandoning an Unfinished Recommendation"}, {"refs": [{"id": "ref-for-GroupsWG\u2466\u2466"}, {"id": "ref-for-GroupsWG\u2466\u2467"}, {"id": "ref-for-GroupsWG\u2466\u2468"}, {"id": "ref-for-GroupsWG\u2467\u24ea"}, {"id": "ref-for-GroupsWG\u2467\u2460"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-GroupsWG\u2467\u2461"}], "title": "6.4.1. \nGroup Notes"}, {"refs": [{"id": "ref-for-GroupsWG\u2467\u2462"}], "title": "6.5.1. \nRegistry Definitions"}, {"refs": [{"id": "ref-for-GroupsWG\u2467\u2463"}], "title": "6.5.3. \nUpdating Registry Tables"}, {"refs": [{"id": "ref-for-GroupsWG\u2467\u2464"}, {"id": "ref-for-GroupsWG\u2467\u2465"}], "title": "6.5.4. \nRegistry Data Reports"}, {"refs": [{"id": "ref-for-GroupsWG\u2467\u2466"}, {"id": "ref-for-GroupsWG\u2467\u2467"}], "title": "6.6. \nSwitching Tracks"}, {"refs": [{"id": "ref-for-GroupsWG\u2467\u2468"}], "title": "10. \nMember Submission Process"}, {"refs": [{"id": "ref-for-GroupsWG\u2468\u24ea"}], "title": "10.1. \nSubmitter Rights and Obligations"}, {"refs": [{"id": "ref-for-GroupsWG\u2468\u2460"}], "title": "10.1.1. \nScope of Member Submissions"}, {"refs": [{"id": "ref-for-GroupsWG\u2468\u2461"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['GroupsIG'] = {"dfnID": "GroupsIG", "url": "#GroupsIG", "dfnText": "Interest Groups", "refSections": [{"refs": [{"id": "ref-for-GroupsIG"}], "title": "1. \nIntroduction"}, {"refs": [{"id": "ref-for-GroupsIG"}], "title": "3.4. \nChartered Groups: Working Groups and Interest Groups"}, {"refs": [{"id": "ref-for-GroupsIG\u2460"}], "title": "3.4.2. \nParticipation in Chartered Groups"}, {"refs": [{"id": "ref-for-GroupsIG\u2461"}, {"id": "ref-for-GroupsIG\u2462"}], "title": "4.4. \nCall for Participation in a Chartered Group"}, {"refs": [{"id": "ref-for-GroupsIG\u2463"}], "title": "4.6. \nChartered Group Closure"}, {"refs": [{"id": "ref-for-GroupsIG\u2464"}, {"id": "ref-for-GroupsIG\u2465"}], "title": "5.1. \nTypes of Decisions"}, {"refs": [{"id": "ref-for-GroupsIG\u2466"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-GroupsIG\u2467"}, {"id": "ref-for-GroupsIG\u2468"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-GroupsIG\u2460\u24ea"}], "title": "6.4.1. \nGroup Notes"}], "external": false};
+window.dfnpanelData['GeneralChairs'] = {"dfnID": "GeneralChairs", "url": "#GeneralChairs", "dfnText": "Chair", "refSections": [{"refs": [{"id": "ref-for-GeneralChairs"}], "title": "3.1.1.2. \nConflict of Interest Policy"}, {"refs": [{"id": "ref-for-GeneralChairs\u2460"}], "title": "3.1.2. \nMeetings"}, {"refs": [{"id": "ref-for-GeneralChairs\u2461"}], "title": "3.3.3.4. \nTechnical Architecture Group Appointments"}, {"refs": [{"id": "ref-for-GeneralChairs\u2462"}, {"id": "ref-for-GeneralChairs\u2463"}, {"id": "ref-for-GeneralChairs\u2464"}, {"id": "ref-for-GeneralChairs\u2465"}], "title": "3.4.1. \nRequirements for All Chartered Groups"}, {"refs": [{"id": "ref-for-GeneralChairs\u2466"}, {"id": "ref-for-GeneralChairs\u2467"}], "title": "3.4.2. \nParticipation in Chartered Groups"}, {"refs": [{"id": "ref-for-GeneralChairs\u2468"}], "title": "3.4.3.1. \nMember Representative in a Working Group"}, {"refs": [{"id": "ref-for-GeneralChairs\u2460\u24ea"}, {"id": "ref-for-GeneralChairs\u2460\u2460"}, {"id": "ref-for-GeneralChairs\u2460\u2461"}, {"id": "ref-for-GeneralChairs\u2460\u2462"}], "title": "3.4.3.3. \nInvited Expert in a Working Group"}, {"refs": [{"id": "ref-for-GeneralChairs\u2460\u2463"}], "title": "4.3. \nAdvisory Committee Review of a Charter"}, {"refs": [{"id": "ref-for-GeneralChairs\u2460\u2464"}], "title": "4.4. \nCall for Participation in a Chartered Group"}, {"refs": [{"id": "ref-for-GeneralChairs\u2460\u2465"}, {"id": "ref-for-GeneralChairs\u2460\u2466"}], "title": "4.5. \nCharter Extension"}, {"refs": [{"id": "ref-for-GeneralChairs\u2460\u2467"}, {"id": "ref-for-GeneralChairs\u2460\u2468"}], "title": "5.1. \nTypes of Decisions"}, {"refs": [{"id": "ref-for-GeneralChairs\u2461\u24ea"}, {"id": "ref-for-GeneralChairs\u2461\u2460"}], "title": "5.2.2. \nManaging Dissent"}, {"refs": [{"id": "ref-for-GeneralChairs\u2461\u2461"}, {"id": "ref-for-GeneralChairs\u2461\u2462"}], "title": "5.2.3. \nDeciding by Vote"}, {"refs": [{"id": "ref-for-GeneralChairs\u2461\u2463"}, {"id": "ref-for-GeneralChairs\u2461\u2464"}], "title": "5.4. \nReopening a Decision When Presented With New Information"}, {"refs": [{"id": "ref-for-GeneralChairs\u2461\u2465"}], "title": "5.6.2.5. \nCouncil Chairing"}, {"refs": [{"id": "ref-for-GeneralChairs\u2461\u2466"}, {"id": "ref-for-GeneralChairs\u2461\u2467"}], "title": "6.2.1. \nPublication of Technical Reports"}, {"refs": [{"id": "ref-for-GeneralChairs\u2461\u2468"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}], "external": false};
+window.dfnpanelData['TeamContact'] = {"dfnID": "TeamContact", "url": "#TeamContact", "dfnText": "Team Contact", "refSections": [{"refs": [{"id": "ref-for-TeamContact"}, {"id": "ref-for-TeamContact\u2460"}], "title": "3.4.1. \nRequirements for All Chartered Groups"}, {"refs": [{"id": "ref-for-TeamContact"}], "title": "3.4.2. \nParticipation in Chartered Groups"}, {"refs": [{"id": "ref-for-TeamContact\u2461"}], "title": "3.4.3.1. \nMember Representative in a Working Group"}, {"refs": [{"id": "ref-for-TeamContact\u2462"}], "title": "3.4.3.3. \nInvited Expert in a Working Group"}, {"refs": [{"id": "ref-for-TeamContact\u2463"}], "title": "4.3. \nAdvisory Committee Review of a Charter"}, {"refs": [{"id": "ref-for-TeamContact\u2464"}], "title": "4.4. \nCall for Participation in a Chartered Group"}, {"refs": [{"id": "ref-for-TeamContact\u2465"}], "title": "4.5. \nCharter Extension"}, {"refs": [{"id": "ref-for-TeamContact"}], "title": "5.5. \nRegistering Formal Objections"}], "external": false};
+window.dfnpanelData['wgparticipant'] = {"dfnID": "wgparticipant", "url": "#wgparticipant", "dfnText": "participants in a Working Group", "refSections": [{"refs": [{"id": "ref-for-wgparticipant"}], "title": "3. \nGroups and Participation"}, {"refs": [{"id": "ref-for-wgparticipant"}], "title": "4.3. \nAdvisory Committee Review of a Charter"}], "external": false};
+window.dfnpanelData['igparticipant'] = {"dfnID": "igparticipant", "url": "#igparticipant", "dfnText": "participants in an Interest Group", "refSections": [{"refs": [{"id": "ref-for-igparticipant"}], "title": "3. \nGroups and Participation"}, {"refs": [{"id": "ref-for-igparticipant"}], "title": "4.3. \nAdvisory Committee Review of a Charter"}], "external": false};
+window.dfnpanelData['public-participant-ig'] = {"dfnID": "public-participant-ig", "url": "#public-participant-ig", "dfnText": "public participants", "refSections": [{"refs": [{"id": "ref-for-public-participant-ig"}], "title": "4.2. \nContent of a Charter"}], "external": false};
+window.dfnpanelData['mtg-substitute'] = {"dfnID": "mtg-substitute", "url": "#mtg-substitute", "dfnText": "substitute", "refSections": [{"refs": [{"id": "ref-for-mtg-substitute"}], "title": "5.2.3. \nDeciding by Vote"}], "external": false};
+window.dfnpanelData['member-representative-in-an-interest-group'] = {"dfnID": "member-representative-in-an-interest-group", "url": "#member-representative-in-an-interest-group", "dfnText": "Member representative in an Interest Group", "refSections": [{"refs": [{"id": "ref-for-member-representative-in-an-interest-group"}], "title": "3.4.3.2. \nMember Representative in an Interest Group"}], "external": false};
+window.dfnpanelData['invited-expert-in-a-working-group'] = {"dfnID": "invited-expert-in-a-working-group", "url": "#invited-expert-in-a-working-group", "dfnText": "Invited Expert in a Working Group", "refSections": [{"refs": [{"id": "ref-for-invited-expert-in-a-working-group"}], "title": "3.4.3.3. \nInvited Expert in a Working Group"}, {"refs": [{"id": "ref-for-invited-expert-in-a-working-group\u2460"}], "title": "3.4.3.4. \nInvited Expert in an Interest Group"}], "external": false};
+window.dfnpanelData['inv-expert-info'] = {"dfnID": "inv-expert-info", "url": "#inv-expert-info", "dfnText": "participate in a Working Group as an Invited Expert", "refSections": [{"refs": [{"id": "ref-for-inv-expert-info"}], "title": "3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}, {"refs": [{"id": "ref-for-inv-expert-info"}], "title": "3.4.3.3. \nInvited Expert in a Working Group"}], "external": false};
+window.dfnpanelData['charter'] = {"dfnID": "charter", "url": "#charter", "dfnText": "charter", "refSections": [{"refs": [{"id": "ref-for-charter"}], "title": "3.4.1. \nRequirements for All Chartered Groups"}, {"refs": [{"id": "ref-for-charter\u2460"}], "title": "4.4. \nCall for Participation in a Chartered Group"}, {"refs": [{"id": "ref-for-charter\u2461"}], "title": "5.7. \nAdvisory Committee Reviews"}, {"refs": [{"id": "ref-for-charter\u2462"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-charter\u2463"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}], "external": false};
+window.dfnpanelData['adopted-draft'] = {"dfnID": "adopted-draft", "url": "#adopted-draft", "dfnText": "Adopted Draft", "refSections": [{"refs": [{"id": "ref-for-adopted-draft"}], "title": "4.2. \nContent of a Charter"}], "external": false};
+window.dfnpanelData['exclusion-draft'] = {"dfnID": "exclusion-draft", "url": "#exclusion-draft", "dfnText": "Exclusion Draft", "refSections": [{"refs": [{"id": "ref-for-exclusion-draft"}, {"id": "ref-for-exclusion-draft\u2460"}], "title": "4.2. \nContent of a Charter"}], "external": false};
+window.dfnpanelData['dfn-charter-extension'] = {"dfnID": "dfn-charter-extension", "url": "#dfn-charter-extension", "dfnText": "extensions", "refSections": [{"refs": [{"id": "ref-for-dfn-charter-extension"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}], "external": false};
+window.dfnpanelData['group-decision'] = {"dfnID": "group-decision", "url": "#group-decision", "dfnText": "group decisions", "refSections": [{"refs": [{"id": "ref-for-group-decision"}, {"id": "ref-for-group-decision\u2460"}], "title": "3.1.2.2. \nMeeting Minutes"}, {"refs": [{"id": "ref-for-group-decision\u2461"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-group-decision\u2462"}], "title": "6.3.11.2. \nRevising a Recommendation: Editorial Changes"}, {"refs": [{"id": "ref-for-group-decision\u2463"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-group-decision\u2464"}], "title": "6.5.4. \nRegistry Data Reports"}, {"refs": [{"id": "ref-for-group-decision\u2465"}], "title": "6.6. \nSwitching Tracks"}], "external": false};
+window.dfnpanelData['team-decision'] = {"dfnID": "team-decision", "url": "#team-decision", "dfnText": "Team Decisions", "refSections": [{"refs": [{"id": "ref-for-team-decision"}], "title": "2.2. \nThe W3C Team"}, {"refs": [{"id": "ref-for-team-decision\u2460"}], "title": "4.5. \nCharter Extension"}, {"refs": [{"id": "ref-for-team-decision\u2461"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-team-decision\u2462"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-team-decision\u2463"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-team-decision\u2464"}], "title": "9. \nLiaisons"}, {"refs": [{"id": "ref-for-team-decision\u2465"}], "title": "10.1.2. \nInformation Required in a Submission Request"}, {"refs": [{"id": "ref-for-team-decision\u2466"}], "title": "10.2. \nTeam Rights and Obligations"}], "external": false};
+window.dfnpanelData['def-w3c-decision'] = {"dfnID": "def-w3c-decision", "url": "#def-w3c-decision", "dfnText": "W3C decision", "refSections": [{"refs": [{"id": "ref-for-def-w3c-decision"}], "title": "3.2.1. \nRole of the Advisory Committee"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2460"}], "title": "4.4. \nCall for Participation in a Chartered Group"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2461"}], "title": "4.6. \nChartered Group Closure"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2462"}, {"id": "ref-for-def-w3c-decision\u2463"}, {"id": "ref-for-def-w3c-decision\u2464"}, {"id": "ref-for-def-w3c-decision\u2465"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2466"}, {"id": "ref-for-def-w3c-decision\u2467"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2468"}, {"id": "ref-for-def-w3c-decision\u2460\u24ea"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2460\u2460"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2460\u2461"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2460\u2462"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-def-w3c-decision\u2460\u2463"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['def-Consensus'] = {"dfnID": "def-Consensus", "url": "#def-Consensus", "dfnText": "Consensus", "refSections": [{"refs": [{"id": "ref-for-def-Consensus"}], "title": "5.1. \nTypes of Decisions"}, {"refs": [{"id": "ref-for-def-Consensus\u2460"}, {"id": "ref-for-def-Consensus\u2461"}], "title": "5.2.1. \nConsensus"}, {"refs": [{"id": "ref-for-def-Consensus\u2462"}, {"id": "ref-for-def-Consensus\u2463"}, {"id": "ref-for-def-Consensus\u2464"}, {"id": "ref-for-def-Consensus\u2465"}, {"id": "ref-for-def-Consensus\u2466"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-def-Consensus\u2467"}], "title": "6. \nW3C Technical Reports"}, {"refs": [{"id": "ref-for-def-Consensus\u2468"}, {"id": "ref-for-def-Consensus\u2460\u24ea"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-def-Consensus\u2460\u2460"}, {"id": "ref-for-def-Consensus\u2460\u2461"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-def-Consensus\u2460\u2462"}], "title": "6.3.6. \nRevising a Working Draft"}, {"refs": [{"id": "ref-for-def-Consensus\u2460\u2463"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['def-Unanimity'] = {"dfnID": "def-Unanimity", "url": "#def-Unanimity", "dfnText": "Unanimity", "refSections": [{"refs": [{"id": "ref-for-def-Unanimity"}], "title": "5.2.1. \nConsensus"}], "external": false};
+window.dfnpanelData['def-Dissent'] = {"dfnID": "def-Dissent", "url": "#def-Dissent", "dfnText": "Dissent", "refSections": [{"refs": [{"id": "ref-for-def-Dissent"}, {"id": "ref-for-def-Dissent\u2460"}], "title": "5.2.2. \nManaging Dissent"}, {"refs": [{"id": "ref-for-def-Dissent\u2461"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-def-Dissent\u2462"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-def-Dissent\u2463"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}, {"refs": [{"id": "ref-for-def-Dissent\u2464"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}], "external": false};
+window.dfnpanelData['proxy'] = {"dfnID": "proxy", "url": "#proxy", "dfnText": "proxy", "refSections": [{"refs": [{"id": "ref-for-proxy"}], "title": "3.4.2. \nParticipation in Chartered Groups"}], "external": false};
+window.dfnpanelData['formally-addressed'] = {"dfnID": "formally-addressed", "url": "#formally-addressed", "dfnText": "formally addressed", "refSections": [{"refs": [{"id": "ref-for-formally-addressed"}], "title": "6.2.2. \nReviews and Review Responsibilities"}, {"refs": [{"id": "ref-for-formally-addressed\u2460"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-formally-addressed\u2461"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-formally-addressed\u2462"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-formally-addressed\u2463"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}, {"refs": [{"id": "ref-for-formally-addressed\u2464"}, {"id": "ref-for-formally-addressed\u2465"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-formally-addressed\u2466"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-formally-addressed\u2467"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-formally-addressed\u2468"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['FormalObjection'] = {"dfnID": "FormalObjection", "url": "#FormalObjection", "dfnText": "Formal Objection", "refSections": [{"refs": [{"id": "ref-for-FormalObjection"}], "title": "3.3.1.1. \nRole of the Advisory Board"}, {"refs": [{"id": "ref-for-FormalObjection\u2460"}], "title": "3.3.2.1. \nRole of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-FormalObjection\u2461"}], "title": "3.4.1. \nRequirements for All Chartered Groups"}, {"refs": [{"id": "ref-for-FormalObjection\u2462"}], "title": "5. \nDecisions"}, {"refs": [{"id": "ref-for-FormalObjection\u2463"}], "title": "5.2.1. \nConsensus"}, {"refs": [{"id": "ref-for-FormalObjection\u2464"}], "title": "5.2.2. \nManaging Dissent"}, {"refs": [{"id": "ref-for-FormalObjection\u2465"}, {"id": "ref-for-FormalObjection\u2466"}, {"id": "ref-for-FormalObjection\u2467"}, {"id": "ref-for-FormalObjection\u2468"}, {"id": "ref-for-FormalObjection\u2460\u24ea"}, {"id": "ref-for-FormalObjection\u2460\u2460"}, {"id": "ref-for-FormalObjection\u2460\u2461"}, {"id": "ref-for-FormalObjection\u2460\u2462"}, {"id": "ref-for-FormalObjection\u2460\u2463"}], "title": "5.5. \nRegistering Formal Objections"}, {"refs": [{"id": "ref-for-FormalObjection\u2460\u2464"}, {"id": "ref-for-FormalObjection\u2460\u2465"}, {"id": "ref-for-FormalObjection\u2460\u2466"}], "title": "5.6.1. \nInvestigation and Mediation by the Team"}, {"refs": [{"id": "ref-for-FormalObjection\u2460\u2467"}], "title": "5.6.2. \nW3C Council"}, {"refs": [{"id": "ref-for-FormalObjection\u2460\u2468"}, {"id": "ref-for-FormalObjection\u2461\u24ea"}], "title": "5.6.2.2. \nExtraordinary Delegation"}, {"refs": [{"id": "ref-for-FormalObjection\u2461\u2460"}, {"id": "ref-for-FormalObjection\u2461\u2461"}], "title": "5.6.2.6. \nCouncil Deliberations"}, {"refs": [{"id": "ref-for-FormalObjection\u2461\u2462"}], "title": "5.6.2.7. \nCouncil Decision Report"}, {"refs": [{"id": "ref-for-FormalObjection\u2461\u2463"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-FormalObjection\u2461\u2464"}, {"id": "ref-for-FormalObjection\u2461\u2465"}, {"id": "ref-for-FormalObjection\u2461\u2466"}, {"id": "ref-for-FormalObjection\u2461\u2467"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-FormalObjection\u2461\u2468"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-FormalObjection\u2462\u24ea"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-FormalObjection\u2462\u2460"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-FormalObjection\u2462\u2461"}], "title": "6.3.12. \nRegression on the Recommendation Track"}, {"refs": [{"id": "ref-for-FormalObjection\u2462\u2462"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-FormalObjection\u2462\u2463"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}], "external": false};
+window.dfnpanelData['w3c-council'] = {"dfnID": "w3c-council", "url": "#w3c-council", "dfnText": "W3C Council", "refSections": [{"refs": [{"id": "ref-for-w3c-council"}, {"id": "ref-for-w3c-council\u2460"}], "title": "3.3.1.1. \nRole of the Advisory Board"}, {"refs": [{"id": "ref-for-w3c-council\u2461"}], "title": "3.3.2.1. \nRole of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-w3c-council\u2462"}, {"id": "ref-for-w3c-council\u2463"}], "title": "5.6.1. \nInvestigation and Mediation by the Team"}, {"refs": [{"id": "ref-for-w3c-council\u2464"}, {"id": "ref-for-w3c-council\u2465"}, {"id": "ref-for-w3c-council\u2466"}, {"id": "ref-for-w3c-council\u2467"}, {"id": "ref-for-w3c-council\u2468"}, {"id": "ref-for-w3c-council\u2460\u24ea"}], "title": "5.6.2.1. \nCouncil Composition"}, {"refs": [{"id": "ref-for-w3c-council\u2460\u2460"}], "title": "5.6.2.2. \nExtraordinary Delegation"}, {"refs": [{"id": "ref-for-w3c-council\u2460\u2461"}, {"id": "ref-for-w3c-council\u2460\u2462"}, {"id": "ref-for-w3c-council\u2460\u2463"}], "title": "5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"}, {"refs": [{"id": "ref-for-w3c-council\u2460\u2464"}], "title": "5.6.2.5. \nCouncil Chairing"}, {"refs": [{"id": "ref-for-w3c-council\u2460\u2465"}, {"id": "ref-for-w3c-council\u2460\u2466"}, {"id": "ref-for-w3c-council\u2460\u2467"}, {"id": "ref-for-w3c-council\u2460\u2468"}, {"id": "ref-for-w3c-council\u2461\u24ea"}, {"id": "ref-for-w3c-council\u2461\u2460"}, {"id": "ref-for-w3c-council\u2461\u2461"}, {"id": "ref-for-w3c-council\u2461\u2462"}, {"id": "ref-for-w3c-council\u2461\u2463"}], "title": "5.6.2.6. \nCouncil Deliberations"}, {"refs": [{"id": "ref-for-w3c-council\u2461\u2464"}, {"id": "ref-for-w3c-council\u2461\u2465"}, {"id": "ref-for-w3c-council\u2461\u2466"}], "title": "5.6.2.7. \nCouncil Decision Report"}, {"refs": [{"id": "ref-for-w3c-council\u2461\u2467"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}, {"refs": [{"id": "ref-for-w3c-council\u2461\u2468"}, {"id": "ref-for-w3c-council\u2462\u24ea"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-w3c-council\u2462\u2460"}, {"id": "ref-for-w3c-council\u2462\u2461"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}], "external": false};
+window.dfnpanelData['council-team-contact'] = {"dfnID": "council-team-contact", "url": "#council-team-contact", "dfnText": "Council Team Contact", "refSections": [{"refs": [{"id": "ref-for-council-team-contact"}], "title": "5.6.2.5. \nCouncil Chairing"}, {"refs": [{"id": "ref-for-council-team-contact\u2460"}], "title": "5.6.2.6. \nCouncil Deliberations"}], "external": false};
+window.dfnpanelData['dismissed'] = {"dfnID": "dismissed", "url": "#dismissed", "dfnText": "dismissed", "refSections": [{"refs": [{"id": "ref-for-dismissed"}, {"id": "ref-for-dismissed\u2460"}, {"id": "ref-for-dismissed\u2461"}], "title": "5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"}, {"refs": [{"id": "ref-for-dismissed\u2462"}], "title": "5.6.2.7. \nCouncil Decision Report"}], "external": false};
+window.dfnpanelData['renounce'] = {"dfnID": "renounce", "url": "#renounce", "dfnText": "renounce", "refSections": [{"refs": [{"id": "ref-for-renounce"}], "title": "5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"}, {"refs": [{"id": "ref-for-renounce\u2460"}], "title": "5.6.2.7. \nCouncil Decision Report"}], "external": false};
+window.dfnpanelData['w3c-council-chair'] = {"dfnID": "w3c-council-chair", "url": "#w3c-council-chair", "dfnText": "Chair", "refSections": [{"refs": [{"id": "ref-for-w3c-council-chair"}], "title": "5.6.2.1. \nCouncil Composition"}, {"refs": [{"id": "ref-for-w3c-council-chair\u2460"}], "title": "5.6.2.4. \nUnanimous Short Circuit"}, {"refs": [{"id": "ref-for-w3c-council-chair\u2461"}, {"id": "ref-for-w3c-council-chair\u2462"}, {"id": "ref-for-w3c-council-chair\u2463"}, {"id": "ref-for-w3c-council-chair\u2464"}, {"id": "ref-for-w3c-council-chair\u2465"}], "title": "5.6.2.6. \nCouncil Deliberations"}], "external": false};
+window.dfnpanelData['uphold'] = {"dfnID": "uphold", "url": "#uphold", "dfnText": "uphold", "refSections": [{"refs": [{"id": "ref-for-uphold"}], "title": "5.6.2.6. \nCouncil Deliberations"}, {"refs": [{"id": "ref-for-uphold\u2460"}], "title": "5.6.2.7. \nCouncil Decision Report"}, {"refs": [{"id": "ref-for-uphold\u2461"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-uphold\u2462"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-uphold\u2463"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}], "external": false};
+window.dfnpanelData['overrule'] = {"dfnID": "overrule", "url": "#overrule", "dfnText": "overrule", "refSections": [{"refs": [{"id": "ref-for-overrule"}], "title": "5.6.2.6. \nCouncil Deliberations"}, {"refs": [{"id": "ref-for-overrule\u2460"}], "title": "5.6.2.7. \nCouncil Decision Report"}], "external": false};
+window.dfnpanelData['fully-addressed'] = {"dfnID": "fully-addressed", "url": "#fully-addressed", "dfnText": "fully addressed", "refSections": [{"refs": [{"id": "ref-for-fully-addressed"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-fully-addressed\u2460"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}], "external": false};
+window.dfnpanelData['minority-opinion'] = {"dfnID": "minority-opinion", "url": "#minority-opinion", "dfnText": "Minority Opinion", "refSections": [{"refs": [{"id": "ref-for-minority-opinion"}], "title": "5.6.2.7. \nCouncil Decision Report"}], "external": false};
+window.dfnpanelData['council-report'] = {"dfnID": "council-report", "url": "#council-report", "dfnText": "Council Report", "refSections": [{"refs": [{"id": "ref-for-council-report"}, {"id": "ref-for-council-report\u2460"}, {"id": "ref-for-council-report\u2461"}], "title": "5.6.2.7. \nCouncil Decision Report"}, {"refs": [{"id": "ref-for-council-report\u2462"}], "title": "5.6.2.8. \nAppealing Council Decisions"}, {"refs": [{"id": "ref-for-council-report\u2463"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}], "external": false};
+window.dfnpanelData['advisory-committee-review'] = {"dfnID": "advisory-committee-review", "url": "#advisory-committee-review", "dfnText": " Advisory Committee review", "refSections": [{"refs": [{"id": "ref-for-advisory-committee-review"}], "title": "4.3. \nAdvisory Committee Review of a Charter"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2460"}], "title": "4.6. \nChartered Group Closure"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2461"}], "title": "5.1. \nTypes of Decisions"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2462"}], "title": "5.2.1. \nConsensus"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2463"}], "title": "5.5. \nRegistering Formal Objections"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2464"}, {"id": "ref-for-advisory-committee-review\u2465"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2466"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2467"}, {"id": "ref-for-advisory-committee-review\u2468"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2460\u24ea"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2460\u2460"}, {"id": "ref-for-advisory-committee-review\u2460\u2461"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2460\u2462"}, {"id": "ref-for-advisory-committee-review\u2460\u2463"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2460\u2464"}], "title": "6.3.13.1. \nAbandoning an Unfinished Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2460\u2465"}, {"id": "ref-for-advisory-committee-review\u2460\u2466"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2460\u2467"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2460\u2468"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2461\u24ea"}], "title": "6.5.3. \nUpdating Registry Tables"}, {"refs": [{"id": "ref-for-advisory-committee-review\u2461\u2460"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['reviewform'] = {"dfnID": "reviewform", "url": "#reviewform", "dfnText": "Call for Review", "refSections": [{"refs": [{"id": "ref-for-reviewform"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-reviewform\u2460"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}], "external": false};
+window.dfnpanelData['advisory-committee-appeal'] = {"dfnID": "advisory-committee-appeal", "url": "#advisory-committee-appeal", "dfnText": "Advisory Committee Appeal", "refSections": [{"refs": [{"id": "ref-for-advisory-committee-appeal"}], "title": "5.6.2.7. \nCouncil Decision Report"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2460"}], "title": "5.6.2.8. \nAppealing Council Decisions"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2461"}], "title": "5.8. \nAdvisory Committee Votes"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2462"}, {"id": "ref-for-advisory-committee-appeal\u2463"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2464"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2465"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2466"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2467"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2468"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2460\u24ea"}, {"id": "ref-for-advisory-committee-appeal\u2460\u2460"}], "title": "9. \nLiaisons"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2460\u2461"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}, {"refs": [{"id": "ref-for-advisory-committee-appeal\u2460\u2462"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['publishing'] = {"dfnID": "publishing", "url": "#publishing", "dfnText": "Publishing", "refSections": [{"refs": [{"id": "ref-for-publishing"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-publishing\u2460"}], "title": "6.2.1. \nPublication of Technical Reports"}, {"refs": [{"id": "ref-for-publishing\u2461"}], "title": "6.2.2. \nReviews and Review Responsibilities"}, {"refs": [{"id": "ref-for-publishing\u2462"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-publishing\u2463"}, {"id": "ref-for-publishing\u2464"}, {"id": "ref-for-publishing\u2465"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-publishing\u2466"}], "title": "6.3.6. \nRevising a Working Draft"}, {"refs": [{"id": "ref-for-publishing\u2467"}], "title": "6.3.8.2. \nPublishing a Candidate Recommendation Draft"}, {"refs": [{"id": "ref-for-publishing\u2468"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-publishing\u2460\u24ea"}, {"id": "ref-for-publishing\u2460\u2460"}, {"id": "ref-for-publishing\u2460\u2461"}], "title": "6.3.13.1. \nAbandoning an Unfinished Recommendation"}, {"refs": [{"id": "ref-for-publishing\u2460\u2462"}, {"id": "ref-for-publishing\u2460\u2463"}], "title": "6.4.1. \nGroup Notes"}], "external": false};
+window.dfnpanelData['technical-report'] = {"dfnID": "technical-report", "url": "#technical-report", "dfnText": "Technical Report", "refSections": [{"refs": [{"id": "ref-for-technical-report"}], "title": "4.2. \nContent of a Charter"}, {"refs": [{"id": "ref-for-technical-report\u2460"}, {"id": "ref-for-technical-report\u2461"}], "title": "5.5. \nRegistering Formal Objections"}, {"refs": [{"id": "ref-for-technical-report\u2462"}], "title": "5.7. \nAdvisory Committee Reviews"}, {"refs": [{"id": "ref-for-technical-report\u2463"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-technical-report\u2464"}, {"id": "ref-for-technical-report\u2465"}, {"id": "ref-for-technical-report\u2466"}], "title": "6.2.1. \nPublication of Technical Reports"}, {"refs": [{"id": "ref-for-technical-report\u2467"}], "title": "6.2.3. \nClasses of Changes"}, {"refs": [{"id": "ref-for-technical-report\u2468"}, {"id": "ref-for-technical-report\u2460\u24ea"}, {"id": "ref-for-technical-report\u2460\u2460"}, {"id": "ref-for-technical-report\u2460\u2461"}, {"id": "ref-for-technical-report\u2460\u2462"}], "title": "6.2.4. \nErrata Management"}, {"refs": [{"id": "ref-for-technical-report\u2460\u2463"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-technical-report\u2460\u2464"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-technical-report\u2460\u2465"}, {"id": "ref-for-technical-report\u2460\u2466"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-technical-report\u2460\u2467"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-technical-report\u2460\u2468"}], "title": "6.3.11.4. \nRevising a Recommendation: New Features"}, {"refs": [{"id": "ref-for-technical-report\u2461\u24ea"}, {"id": "ref-for-technical-report\u2461\u2460"}], "title": "6.3.12. \nRegression on the Recommendation Track"}, {"refs": [{"id": "ref-for-technical-report\u2461\u2461"}, {"id": "ref-for-technical-report\u2461\u2462"}, {"id": "ref-for-technical-report\u2461\u2463"}], "title": "6.3.13.1. \nAbandoning an Unfinished Recommendation"}, {"refs": [{"id": "ref-for-technical-report\u2461\u2464"}], "title": "6.4.2. \nPublishing Notes"}, {"refs": [{"id": "ref-for-technical-report\u2461\u2465"}, {"id": "ref-for-technical-report\u2461\u2466"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-technical-report\u2461\u2467"}, {"id": "ref-for-technical-report\u2461\u2468"}], "title": "6.5.3. \nUpdating Registry Tables"}, {"refs": [{"id": "ref-for-technical-report\u2462\u24ea"}, {"id": "ref-for-technical-report\u2462\u2460"}, {"id": "ref-for-technical-report\u2462\u2461"}, {"id": "ref-for-technical-report\u2462\u2462"}], "title": "6.5.4. \nRegistry Data Reports"}, {"refs": [{"id": "ref-for-technical-report\u2462\u2463"}, {"id": "ref-for-technical-report\u2462\u2464"}, {"id": "ref-for-technical-report\u2462\u2465"}, {"id": "ref-for-technical-report\u2462\u2466"}], "title": "6.6. \nSwitching Tracks"}, {"refs": [{"id": "ref-for-technical-report\u2462\u2467"}], "title": "11. \nProcess Evolution"}], "external": false};
+window.dfnpanelData['dfn-wide-review'] = {"dfnID": "dfn-wide-review", "url": "#dfn-wide-review", "dfnText": "wide review", "refSections": [{"refs": [{"id": "ref-for-dfn-wide-review"}, {"id": "ref-for-dfn-wide-review\u2460"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-dfn-wide-review\u2461"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-dfn-wide-review\u2462"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-dfn-wide-review\u2463"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-dfn-wide-review\u2464"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-dfn-wide-review\u2465"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}, {"refs": [{"id": "ref-for-dfn-wide-review\u2466"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-dfn-wide-review\u2467"}], "title": "6.3.12. \nRegression on the Recommendation Track"}, {"refs": [{"id": "ref-for-dfn-wide-review\u2468"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}], "external": false};
+window.dfnpanelData['editorial-change'] = {"dfnID": "editorial-change", "url": "#editorial-change", "dfnText": "editorial changes", "refSections": [{"refs": [{"id": "ref-for-editorial-change"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-editorial-change\u2460"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-editorial-change\u2461"}], "title": "6.3.6. \nRevising a Working Draft"}, {"refs": [{"id": "ref-for-editorial-change\u2462"}], "title": "6.3.8.2. \nPublishing a Candidate Recommendation Draft"}, {"refs": [{"id": "ref-for-editorial-change\u2463"}], "title": "6.3.11.2. \nRevising a Recommendation: Editorial Changes"}, {"refs": [{"id": "ref-for-editorial-change\u2464"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-editorial-change\u2465"}, {"id": "ref-for-editorial-change\u2466"}], "title": "6.5.4. \nRegistry Data Reports"}, {"refs": [{"id": "ref-for-editorial-change\u2467"}], "title": "10.3. \nAcknowledgment of a Submission Request"}], "external": false};
+window.dfnpanelData['substantive-change'] = {"dfnID": "substantive-change", "url": "#substantive-change", "dfnText": "substantive changes", "refSections": [{"refs": [{"id": "ref-for-substantive-change"}, {"id": "ref-for-substantive-change\u2460"}, {"id": "ref-for-substantive-change\u2461"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-substantive-change\u2462"}], "title": "6.2.2. \nReviews and Review Responsibilities"}, {"refs": [{"id": "ref-for-substantive-change\u2463"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-substantive-change\u2464"}], "title": "6.3.6. \nRevising a Working Draft"}, {"refs": [{"id": "ref-for-substantive-change\u2465"}, {"id": "ref-for-substantive-change\u2466"}], "title": "6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"}, {"refs": [{"id": "ref-for-substantive-change\u2467"}, {"id": "ref-for-substantive-change\u2468"}], "title": "6.3.8.2. \nPublishing a Candidate Recommendation Draft"}, {"refs": [{"id": "ref-for-substantive-change\u2460\u24ea"}, {"id": "ref-for-substantive-change\u2460\u2460"}, {"id": "ref-for-substantive-change\u2460\u2461"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-substantive-change\u2460\u2462"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}, {"refs": [{"id": "ref-for-substantive-change\u2460\u2463"}], "title": "6.3.13.1. \nAbandoning an Unfinished Recommendation"}], "external": false};
+window.dfnpanelData['registry-change'] = {"dfnID": "registry-change", "url": "#registry-change", "dfnText": "registry changes", "refSections": [{"refs": [{"id": "ref-for-registry-change"}], "title": "6.5.1. \nRegistry Definitions"}, {"refs": [{"id": "ref-for-registry-change\u2460"}, {"id": "ref-for-registry-change\u2461"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-registry-change\u2462"}, {"id": "ref-for-registry-change\u2463"}], "title": "6.5.3. \nUpdating Registry Tables"}], "external": false};
+window.dfnpanelData['erratum'] = {"dfnID": "erratum", "url": "#erratum", "dfnText": "erratum", "refSections": [{"refs": [{"id": "ref-for-erratum"}, {"id": "ref-for-erratum\u2460"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-erratum\u2461"}], "title": "6.3.11.2. \nRevising a Recommendation: Editorial Changes"}, {"refs": [{"id": "ref-for-erratum\u2462"}], "title": "6.3.11.3. \nRevising a Recommendation: Substantive Changes"}, {"refs": [{"id": "ref-for-erratum\u2463"}], "title": "6.4.2. \nPublishing Notes"}], "external": false};
+window.dfnpanelData['candidate-correction'] = {"dfnID": "candidate-correction", "url": "#candidate-correction", "dfnText": "candidate correction", "refSections": [{"refs": [{"id": "ref-for-candidate-correction"}, {"id": "ref-for-candidate-correction\u2460"}, {"id": "ref-for-candidate-correction\u2461"}, {"id": "ref-for-candidate-correction\u2462"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-candidate-correction\u2463"}, {"id": "ref-for-candidate-correction\u2464"}], "title": "6.3.11.3. \nRevising a Recommendation: Substantive Changes"}], "external": false};
+window.dfnpanelData['candidate-addition'] = {"dfnID": "candidate-addition", "url": "#candidate-addition", "dfnText": "candidate addition", "refSections": [{"refs": [{"id": "ref-for-candidate-addition"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-candidate-addition\u2460"}, {"id": "ref-for-candidate-addition\u2461"}], "title": "6.3.11.4. \nRevising a Recommendation: New Features"}], "external": false};
+window.dfnpanelData['team-correction'] = {"dfnID": "team-correction", "url": "#team-correction", "dfnText": "Team correction", "refSections": [{"refs": [{"id": "ref-for-team-correction"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-team-correction\u2460"}], "title": "6.3.11.2. \nRevising a Recommendation: Editorial Changes"}, {"refs": [{"id": "ref-for-team-correction\u2461"}], "title": "6.4.2. \nPublishing Notes"}], "external": false};
+window.dfnpanelData['candidate-amendment'] = {"dfnID": "candidate-amendment", "url": "#candidate-amendment", "dfnText": "candidate amendments", "refSections": [{"refs": [{"id": "ref-for-candidate-amendment"}, {"id": "ref-for-candidate-amendment\u2460"}, {"id": "ref-for-candidate-amendment\u2461"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-candidate-amendment\u2462"}], "title": "6.3.11.3. \nRevising a Recommendation: Substantive Changes"}, {"refs": [{"id": "ref-for-candidate-amendment\u2463"}], "title": "6.3.11.4. \nRevising a Recommendation: New Features"}, {"refs": [{"id": "ref-for-candidate-amendment\u2464"}, {"id": "ref-for-candidate-amendment\u2465"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-candidate-amendment\u2466"}, {"id": "ref-for-candidate-amendment\u2467"}, {"id": "ref-for-candidate-amendment\u2468"}, {"id": "ref-for-candidate-amendment\u2460\u24ea"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-candidate-amendment\u2460\u2460"}], "title": "6.5.3. \nUpdating Registry Tables"}], "external": false};
+window.dfnpanelData['w3c-recommendation-track'] = {"dfnID": "w3c-recommendation-track", "url": "#w3c-recommendation-track", "dfnText": "W3C Recommendation Track", "refSections": [{"refs": [{"id": "ref-for-w3c-recommendation-track"}, {"id": "ref-for-w3c-recommendation-track\u2460"}, {"id": "ref-for-w3c-recommendation-track\u2461"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-w3c-recommendation-track\u2462"}, {"id": "ref-for-w3c-recommendation-track\u2463"}], "title": "6.2.3. \nClasses of Changes"}, {"refs": [{"id": "ref-for-w3c-recommendation-track\u2464"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-w3c-recommendation-track\u2465"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-w3c-recommendation-track\u2466"}], "title": "6.3.12. \nRegression on the Recommendation Track"}, {"refs": [{"id": "ref-for-w3c-recommendation-track\u2467"}], "title": "6.3.13.1. \nAbandoning an Unfinished Recommendation"}, {"refs": [{"id": "ref-for-w3c-recommendation-track\u2468"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-w3c-recommendation-track\u2460\u24ea"}, {"id": "ref-for-w3c-recommendation-track\u2460\u2460"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-w3c-recommendation-track\u2460\u2461"}], "title": "6.6. \nSwitching Tracks"}], "external": false};
+window.dfnpanelData['patent-review-drafts'] = {"dfnID": "patent-review-drafts", "url": "#patent-review-drafts", "dfnText": "Patent Review Drafts", "refSections": [{"refs": [{"id": "ref-for-patent-review-drafts"}, {"id": "ref-for-patent-review-drafts\u2460"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-patent-review-drafts\u2461"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-patent-review-drafts\u2462"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-patent-review-drafts\u2463"}], "title": "6.6. \nSwitching Tracks"}], "external": false};
+window.dfnpanelData['RecsWD'] = {"dfnID": "RecsWD", "url": "#RecsWD", "dfnText": "Working Draft", "refSections": [{"refs": [{"id": "ref-for-RecsWD"}], "title": "4.2. \nContent of a Charter"}, {"refs": [{"id": "ref-for-RecsWD\u2460"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-RecsWD\u2461"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-RecsWD\u2462"}, {"id": "ref-for-RecsWD\u2463"}, {"id": "ref-for-RecsWD\u2464"}, {"id": "ref-for-RecsWD\u2465"}, {"id": "ref-for-RecsWD\u2466"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-RecsWD\u2467"}, {"id": "ref-for-RecsWD\u2468"}, {"id": "ref-for-RecsWD\u2460\u24ea"}], "title": "6.3.6. \nRevising a Working Draft"}, {"refs": [{"id": "ref-for-RecsWD\u2460\u2460"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-RecsWD\u2460\u2461"}], "title": "6.3.13.1. \nAbandoning an Unfinished Recommendation"}, {"refs": [{"id": "ref-for-RecsWD\u2460\u2462"}, {"id": "ref-for-RecsWD\u2460\u2463"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['fpwd'] = {"dfnID": "fpwd", "url": "#fpwd", "dfnText": "First Public Working Draft", "refSections": [{"refs": [{"id": "ref-for-fpwd"}], "title": "4.2. \nContent of a Charter"}, {"refs": [{"id": "ref-for-fpwd\u2460"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-fpwd\u2461"}, {"id": "ref-for-fpwd\u2462"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-fpwd\u2463"}, {"id": "ref-for-fpwd\u2464"}], "title": "6.3.5. \nPublishing a First Public Working Draft"}, {"refs": [{"id": "ref-for-fpwd\u2465"}], "title": "6.3.11.4. \nRevising a Recommendation: New Features"}, {"refs": [{"id": "ref-for-fpwd\u2466"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['RecsCR'] = {"dfnID": "RecsCR", "url": "#RecsCR", "dfnText": "Candidate Recommendation", "refSections": [{"refs": [{"id": "ref-for-RecsCR"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-RecsCR\u2460"}], "title": "6.2.2.1. \nWide Review"}, {"refs": [{"id": "ref-for-RecsCR\u2461"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-RecsCR\u2462"}, {"id": "ref-for-RecsCR\u2463"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-RecsCR\u2464"}, {"id": "ref-for-RecsCR\u2465"}, {"id": "ref-for-RecsCR\u2466"}, {"id": "ref-for-RecsCR\u2467"}, {"id": "ref-for-RecsCR\u2468"}, {"id": "ref-for-RecsCR\u2460\u24ea"}, {"id": "ref-for-RecsCR\u2460\u2460"}, {"id": "ref-for-RecsCR\u2460\u2461"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-RecsCR\u2460\u2462"}, {"id": "ref-for-RecsCR\u2460\u2463"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-RecsCR\u2460\u2464"}, {"id": "ref-for-RecsCR\u2460\u2465"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}, {"refs": [{"id": "ref-for-RecsCR\u2460\u2466"}, {"id": "ref-for-RecsCR\u2460\u2467"}], "title": "6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"}, {"refs": [{"id": "ref-for-RecsCR\u2460\u2468"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-RecsCR\u2461\u24ea"}], "title": "6.3.13.2. \nRescinding a Candidate Recommendation"}, {"refs": [{"id": "ref-for-RecsCR\u2461\u2460"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['candidate-recommendation-snapshot'] = {"dfnID": "candidate-recommendation-snapshot", "url": "#candidate-recommendation-snapshot", "dfnText": "Candidate Recommendation Snapshot", "refSections": [{"refs": [{"id": "ref-for-candidate-recommendation-snapshot"}, {"id": "ref-for-candidate-recommendation-snapshot\u2460"}, {"id": "ref-for-candidate-recommendation-snapshot\u2461"}, {"id": "ref-for-candidate-recommendation-snapshot\u2462"}, {"id": "ref-for-candidate-recommendation-snapshot\u2463"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-candidate-recommendation-snapshot\u2464"}, {"id": "ref-for-candidate-recommendation-snapshot\u2465"}, {"id": "ref-for-candidate-recommendation-snapshot\u2466"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}, {"refs": [{"id": "ref-for-candidate-recommendation-snapshot\u2467"}, {"id": "ref-for-candidate-recommendation-snapshot\u2468"}, {"id": "ref-for-candidate-recommendation-snapshot\u2460\u24ea"}, {"id": "ref-for-candidate-recommendation-snapshot\u2460\u2460"}, {"id": "ref-for-candidate-recommendation-snapshot\u2460\u2461"}], "title": "6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"}, {"refs": [{"id": "ref-for-candidate-recommendation-snapshot\u2460\u2462"}, {"id": "ref-for-candidate-recommendation-snapshot\u2460\u2463"}, {"id": "ref-for-candidate-recommendation-snapshot\u2460\u2464"}], "title": "6.3.8.2. \nPublishing a Candidate Recommendation Draft"}, {"refs": [{"id": "ref-for-candidate-recommendation-snapshot\u2460\u2465"}, {"id": "ref-for-candidate-recommendation-snapshot\u2460\u2466"}, {"id": "ref-for-candidate-recommendation-snapshot\u2460\u2467"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-candidate-recommendation-snapshot\u2460\u2468"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['candidate-recommendation-draft'] = {"dfnID": "candidate-recommendation-draft", "url": "#candidate-recommendation-draft", "dfnText": "Candidate Recommendation Draft", "refSections": [{"refs": [{"id": "ref-for-candidate-recommendation-draft"}, {"id": "ref-for-candidate-recommendation-draft\u2460"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-candidate-recommendation-draft\u2461"}, {"id": "ref-for-candidate-recommendation-draft\u2462"}, {"id": "ref-for-candidate-recommendation-draft\u2463"}, {"id": "ref-for-candidate-recommendation-draft\u2464"}, {"id": "ref-for-candidate-recommendation-draft\u2465"}], "title": "6.3.8.2. \nPublishing a Candidate Recommendation Draft"}, {"refs": [{"id": "ref-for-candidate-recommendation-draft\u2466"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['rescinded-candidate-recommendation'] = {"dfnID": "rescinded-candidate-recommendation", "url": "#rescinded-candidate-recommendation", "dfnText": "Rescinded Candidate Recommendation", "refSections": [{"refs": [{"id": "ref-for-rescinded-candidate-recommendation"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-rescinded-candidate-recommendation\u2460"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['RecsPR'] = {"dfnID": "RecsPR", "url": "#RecsPR", "dfnText": "Proposed Recommendation", "refSections": [{"refs": [{"id": "ref-for-RecsPR"}], "title": "3.2.1. \nRole of the Advisory Committee"}, {"refs": [{"id": "ref-for-RecsPR"}, {"id": "ref-for-RecsPR\u2460"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-RecsPR\u2461"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-RecsPR\u2462"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-RecsPR\u2463"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-RecsPR\u2464"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}, {"refs": [{"id": "ref-for-RecsPR\u2465"}], "title": "6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"}, {"refs": [{"id": "ref-for-RecsPR\u2466"}, {"id": "ref-for-RecsPR\u2467"}, {"id": "ref-for-RecsPR\u2468"}, {"id": "ref-for-RecsPR\u2460\u24ea"}, {"id": "ref-for-RecsPR\u2460\u2460"}, {"id": "ref-for-RecsPR\u2460\u2461"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-RecsPR\u2460\u2462"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}], "external": false};
+window.dfnpanelData['RecsW3C'] = {"dfnID": "RecsW3C", "url": "#RecsW3C", "dfnText": "W3C Recommendation", "refSections": [{"refs": [{"id": "ref-for-RecsW3C"}], "title": "1. \nIntroduction"}, {"refs": [{"id": "ref-for-RecsW3C"}], "title": "3.4. \nChartered Groups: Working Groups and Interest Groups"}, {"refs": [{"id": "ref-for-RecsW3C\u2460"}], "title": "5.7.2. \nAfter the Review Period"}, {"refs": [{"id": "ref-for-RecsW3C\u2461"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-RecsW3C\u2462"}, {"id": "ref-for-RecsW3C\u2463"}], "title": "6.2.4. \nErrata Management"}, {"refs": [{"id": "ref-for-RecsW3C\u2464"}], "title": "6.2.5. \nCandidate Amendments"}, {"refs": [{"id": "ref-for-RecsW3C\u2465"}, {"id": "ref-for-RecsW3C"}, {"id": "ref-for-RecsW3C\u2466"}], "title": "6.3. \nThe W3C Recommendation Track"}, {"refs": [{"id": "ref-for-RecsW3C\u2467"}, {"id": "ref-for-RecsW3C\u2468"}, {"id": "ref-for-RecsW3C\u2460\u24ea"}, {"id": "ref-for-RecsW3C\u2460\u2460"}, {"id": "ref-for-RecsW3C\u2460\u2461"}, {"id": "ref-for-RecsW3C\u2460\u2462"}, {"id": "ref-for-RecsW3C\u2460\u2463"}, {"id": "ref-for-RecsW3C\u2460\u2464"}, {"id": "ref-for-RecsW3C\u2460\u2465"}, {"id": "ref-for-RecsW3C\u2460\u2466"}, {"id": "ref-for-RecsW3C\u2460\u2467"}, {"id": "ref-for-RecsW3C\u2460\u2468"}, {"id": "ref-for-RecsW3C\u2461\u24ea"}, {"id": "ref-for-RecsW3C\u2461\u2460"}, {"id": "ref-for-RecsW3C\u2461\u2461"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-RecsW3C\u2461\u2462"}, {"id": "ref-for-RecsW3C\u2461\u2463"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-RecsW3C\u2461\u2464"}, {"id": "ref-for-RecsW3C\u2461\u2465"}, {"id": "ref-for-RecsW3C\u2461\u2466"}, {"id": "ref-for-RecsW3C\u2461\u2467"}, {"id": "ref-for-RecsW3C\u2461\u2468"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-RecsW3C\u2462\u24ea"}, {"id": "ref-for-RecsW3C\u2462\u2460"}, {"id": "ref-for-RecsW3C\u2462\u2461"}, {"id": "ref-for-RecsW3C\u2462\u2462"}, {"id": "ref-for-RecsW3C\u2462\u2463"}, {"id": "ref-for-RecsW3C\u2462\u2464"}, {"id": "ref-for-RecsW3C\u2462\u2465"}], "title": "6.3.10. \nTransitioning to W3C Recommendation"}, {"refs": [{"id": "ref-for-RecsW3C\u2462\u2466"}], "title": "6.3.11. \nRevising a W3C Recommendation"}, {"refs": [{"id": "ref-for-RecsW3C\u2462\u2467"}, {"id": "ref-for-RecsW3C\u2462\u2468"}, {"id": "ref-for-RecsW3C\u2463\u24ea"}], "title": "6.3.11.1. \nRevising a Recommendation: Markup Changes"}, {"refs": [{"id": "ref-for-RecsW3C\u2463\u2460"}, {"id": "ref-for-RecsW3C\u2463\u2461"}, {"id": "ref-for-RecsW3C\u2463\u2462"}, {"id": "ref-for-RecsW3C\u2463\u2463"}], "title": "6.3.11.2. \nRevising a Recommendation: Editorial Changes"}, {"refs": [{"id": "ref-for-RecsW3C\u2463\u2464"}, {"id": "ref-for-RecsW3C\u2463\u2465"}, {"id": "ref-for-RecsW3C\u2463\u2466"}, {"id": "ref-for-RecsW3C\u2463\u2467"}], "title": "6.3.11.3. \nRevising a Recommendation: Substantive Changes"}, {"refs": [{"id": "ref-for-RecsW3C\u2463\u2468"}, {"id": "ref-for-RecsW3C\u2464\u24ea"}, {"id": "ref-for-RecsW3C\u2464\u2460"}], "title": "6.3.11.4. \nRevising a Recommendation: New Features"}, {"refs": [{"id": "ref-for-RecsW3C\u2464\u2461"}, {"id": "ref-for-RecsW3C\u2464\u2462"}, {"id": "ref-for-RecsW3C\u2464\u2463"}, {"id": "ref-for-RecsW3C\u2464\u2464"}, {"id": "ref-for-RecsW3C\u2464\u2465"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-RecsW3C\u2464\u2466"}], "title": "6.3.13.2. \nRescinding a Candidate Recommendation"}, {"refs": [{"id": "ref-for-RecsW3C\u2464\u2467"}, {"id": "ref-for-RecsW3C\u2464\u2468"}, {"id": "ref-for-RecsW3C\u2465\u24ea"}, {"id": "ref-for-RecsW3C\u2465\u2460"}, {"id": "ref-for-RecsW3C\u2465\u2461"}, {"id": "ref-for-RecsW3C\u2465\u2462"}], "title": "6.3.13.3. \nAbandoning a W3C Recommendation"}, {"refs": [{"id": "ref-for-RecsW3C\u2465\u2463"}, {"id": "ref-for-RecsW3C\u2465\u2464"}, {"id": "ref-for-RecsW3C\u2465\u2465"}, {"id": "ref-for-RecsW3C\u2465\u2466"}, {"id": "ref-for-RecsW3C\u2465\u2467"}, {"id": "ref-for-RecsW3C\u2465\u2468"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-RecsW3C\u2466\u24ea"}], "title": "6.5. \nThe Registry Track"}, {"refs": [{"id": "ref-for-RecsW3C\u2466\u2460"}, {"id": "ref-for-RecsW3C\u2466\u2461"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-RecsW3C\u2466\u2462"}], "title": "6.6. \nSwitching Tracks"}, {"refs": [{"id": "ref-for-RecsW3C\u2466\u2463"}], "title": "10. \nMember Submission Process"}], "external": false};
+window.dfnpanelData['RecsSup'] = {"dfnID": "RecsSup", "url": "#RecsSup", "dfnText": "Superseded Recommendation", "refSections": [{"refs": [{"id": "ref-for-RecsSup"}], "title": "6.3.13.3. \nAbandoning a W3C Recommendation"}, {"refs": [{"id": "ref-for-RecsSup\u2460"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['RecsObs'] = {"dfnID": "RecsObs", "url": "#RecsObs", "dfnText": "Obsolete Recommendation", "refSections": [{"refs": [{"id": "ref-for-RecsObs"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-RecsObs\u2460"}, {"id": "ref-for-RecsObs\u2461"}], "title": "6.3.13.3. \nAbandoning a W3C Recommendation"}, {"refs": [{"id": "ref-for-RecsObs\u2462"}, {"id": "ref-for-RecsObs\u2463"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-RecsObs\u2464"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['RescindedRec'] = {"dfnID": "RescindedRec", "url": "#RescindedRec", "dfnText": "Rescinded Recommendation", "refSections": [{"refs": [{"id": "ref-for-RescindedRec"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-RescindedRec\u2460"}], "title": "6.3.13.3. \nAbandoning a W3C Recommendation"}, {"refs": [{"id": "ref-for-RescindedRec\u2461"}, {"id": "ref-for-RescindedRec\u2462"}], "title": "6.3.13.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}, {"refs": [{"id": "ref-for-RescindedRec\u2463"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['discontinuedREC'] = {"dfnID": "discontinuedREC", "url": "#discontinuedREC", "dfnText": "Discontinued Draft", "refSections": [{"refs": [{"id": "ref-for-discontinuedREC"}, {"id": "ref-for-discontinuedREC\u2460"}], "title": "6.3.13.1. \nAbandoning an Unfinished Recommendation"}], "external": false};
+window.dfnpanelData['editors-draft'] = {"dfnID": "editors-draft", "url": "#editors-draft", "dfnText": "Editor\u2019s drafts", "refSections": [{"refs": [{"id": "ref-for-editors-draft"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}], "external": false};
+window.dfnpanelData['adequate-implementation'] = {"dfnID": "adequate-implementation", "url": "#adequate-implementation", "dfnText": "adequate implementation experience", "refSections": [{"refs": [{"id": "ref-for-adequate-implementation"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-adequate-implementation\u2460"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-adequate-implementation\u2461"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}, {"refs": [{"id": "ref-for-adequate-implementation\u2462"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}, {"refs": [{"id": "ref-for-adequate-implementation\u2463"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}], "external": false};
+window.dfnpanelData['trans-req'] = {"dfnID": "trans-req", "url": "#trans-req", "dfnText": "Transition Requests", "refSections": [{"refs": [{"id": "ref-for-trans-req"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-trans-req\u2460"}, {"id": "ref-for-trans-req\u2461"}], "title": "6.3.3. \nAdvancement on the Recommendation Track"}, {"refs": [{"id": "ref-for-trans-req\u2462"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-trans-req\u2463"}], "title": "6.3.7. \nTransitioning to Candidate Recommendation"}], "external": false};
+window.dfnpanelData['update-requests'] = {"dfnID": "update-requests", "url": "#update-requests", "dfnText": "Update Requests", "refSections": [{"refs": [{"id": "ref-for-update-requests"}], "title": "6.3.1. \nMaturity Stages on the Recommendation Track"}, {"refs": [{"id": "ref-for-update-requests\u2460"}, {"id": "ref-for-update-requests\u2461"}, {"id": "ref-for-update-requests\u2462"}], "title": "6.3.4. \nUpdating Mature Publications on the Recommendation Track"}, {"refs": [{"id": "ref-for-update-requests\u2463"}, {"id": "ref-for-update-requests\u2464"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-update-requests\u2465"}], "title": "6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"}, {"refs": [{"id": "ref-for-update-requests\u2466"}], "title": "6.3.8.2. \nPublishing a Candidate Recommendation Draft"}, {"refs": [{"id": "ref-for-update-requests\u2467"}], "title": "6.3.11.3. \nRevising a Recommendation: Substantive Changes"}, {"refs": [{"id": "ref-for-update-requests\u2468"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-update-requests\u2460\u24ea"}], "title": "6.5.3. \nUpdating Registry Tables"}], "external": false};
+window.dfnpanelData['candidate-recommendation-review-period'] = {"dfnID": "candidate-recommendation-review-period", "url": "#candidate-recommendation-review-period", "dfnText": "Candidate Recommendation review period", "refSections": [{"refs": [{"id": "ref-for-candidate-recommendation-review-period"}, {"id": "ref-for-candidate-recommendation-review-period\u2460"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}], "external": false};
+window.dfnpanelData['at-risk'] = {"dfnID": "at-risk", "url": "#at-risk", "dfnText": "at risk", "refSections": [{"refs": [{"id": "ref-for-at-risk"}, {"id": "ref-for-at-risk\u2460"}], "title": "6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"}, {"refs": [{"id": "ref-for-at-risk\u2461"}], "title": "6.3.8.2. \nPublishing a Candidate Recommendation Draft"}, {"refs": [{"id": "ref-for-at-risk\u2462"}, {"id": "ref-for-at-risk\u2463"}], "title": "6.3.9. \nTransitioning to Proposed Recommendation"}], "external": false};
+window.dfnpanelData['allow-new-features'] = {"dfnID": "allow-new-features", "url": "#allow-new-features", "dfnText": "allow new features", "refSections": [{"refs": [{"id": "ref-for-allow-new-features"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-allow-new-features\u2460"}, {"id": "ref-for-allow-new-features\u2461"}], "title": "6.3.11.4. \nRevising a Recommendation: New Features"}, {"refs": [{"id": "ref-for-allow-new-features\u2462"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}], "external": false};
+window.dfnpanelData['last-call-review'] = {"dfnID": "last-call-review", "url": "#last-call-review", "dfnText": "Last Call for Review of Proposed Amendments", "refSections": [{"refs": [{"id": "ref-for-last-call-review"}], "title": "6.3.11.3. \nRevising a Recommendation: Substantive Changes"}, {"refs": [{"id": "ref-for-last-call-review\u2460"}, {"id": "ref-for-last-call-review\u2461"}, {"id": "ref-for-last-call-review\u2462"}, {"id": "ref-for-last-call-review\u2463"}, {"id": "ref-for-last-call-review\u2464"}, {"id": "ref-for-last-call-review\u2465"}, {"id": "ref-for-last-call-review\u2466"}, {"id": "ref-for-last-call-review\u2467"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}], "external": false};
+window.dfnpanelData['last-call-for-review-of-proposed-corrections'] = {"dfnID": "last-call-for-review-of-proposed-corrections", "url": "#last-call-for-review-of-proposed-corrections", "dfnText": "Last Call for Review of Proposed Corrections", "refSections": [{"refs": [{"id": "ref-for-last-call-for-review-of-proposed-corrections"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-last-call-for-review-of-proposed-corrections\u2460"}], "title": "6.4.4. \nRevising W3C Statements"}], "external": false};
+window.dfnpanelData['last-call-for-review-of-proposed-additions'] = {"dfnID": "last-call-for-review-of-proposed-additions", "url": "#last-call-for-review-of-proposed-additions", "dfnText": "Last Call for Review of Proposed Additions", "refSections": [{"refs": [{"id": "ref-for-last-call-for-review-of-proposed-additions"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}, {"refs": [{"id": "ref-for-last-call-for-review-of-proposed-additions\u2460"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}], "external": false};
+window.dfnpanelData['last-call-for-review-of-proposed-corrections-and-additions'] = {"dfnID": "last-call-for-review-of-proposed-corrections-and-additions", "url": "#last-call-for-review-of-proposed-corrections-and-additions", "dfnText": "Last Call for Review of Proposed Corrections and Additions", "refSections": [{"refs": [{"id": "ref-for-last-call-for-review-of-proposed-corrections-and-additions"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}], "external": false};
+window.dfnpanelData['proposed-amendments'] = {"dfnID": "proposed-amendments", "url": "#proposed-amendments", "dfnText": "proposed amendments", "refSections": [{"refs": [{"id": "ref-for-proposed-amendments"}, {"id": "ref-for-proposed-amendments\u2460"}, {"id": "ref-for-proposed-amendments\u2461"}, {"id": "ref-for-proposed-amendments\u2462"}, {"id": "ref-for-proposed-amendments\u2463"}, {"id": "ref-for-proposed-amendments\u2464"}, {"id": "ref-for-proposed-amendments\u2465"}, {"id": "ref-for-proposed-amendments\u2466"}, {"id": "ref-for-proposed-amendments\u2467"}, {"id": "ref-for-proposed-amendments\u2468"}], "title": "6.3.11.5. \nIncorporating Candidate Amendments"}, {"refs": [{"id": "ref-for-proposed-amendments\u2460\u24ea"}, {"id": "ref-for-proposed-amendments\u2460\u2460"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-proposed-amendments\u2460\u2461"}], "title": "6.5.3. \nUpdating Registry Tables"}], "external": false};
+window.dfnpanelData['proposed-corrections'] = {"dfnID": "proposed-corrections", "url": "#proposed-corrections", "dfnText": "proposed corrections", "refSections": [{"refs": [{"id": "ref-for-proposed-corrections"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}], "external": false};
+window.dfnpanelData['proposed-additions'] = {"dfnID": "proposed-additions", "url": "#proposed-additions", "dfnText": "proposed additions", "refSections": [{"refs": [{"id": "ref-for-proposed-additions"}], "title": "6.3.4.1. \nStreamlined Publication Approval"}], "external": false};
+window.dfnpanelData['WGNote'] = {"dfnID": "WGNote", "url": "#WGNote", "dfnText": "Group Note", "refSections": [{"refs": [{"id": "ref-for-WGNote"}], "title": "3.4. \nChartered Groups: Working Groups and Interest Groups"}, {"refs": [{"id": "ref-for-WGNote"}, {"id": "ref-for-WGNote\u2460"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-WGNote\u2461"}, {"id": "ref-for-WGNote\u2462"}, {"id": "ref-for-WGNote\u2463"}, {"id": "ref-for-WGNote\u2464"}, {"id": "ref-for-WGNote\u2465"}, {"id": "ref-for-WGNote\u2466"}], "title": "6.4.1. \nGroup Notes"}, {"refs": [{"id": "ref-for-WGNote\u2467"}, {"id": "ref-for-WGNote\u2468"}, {"id": "ref-for-WGNote\u2460\u24ea"}, {"id": "ref-for-WGNote\u2460\u2460"}, {"id": "ref-for-WGNote\u2460\u2461"}, {"id": "ref-for-WGNote\u2460\u2462"}, {"id": "ref-for-WGNote\u2460\u2463"}], "title": "6.4.2. \nPublishing Notes"}, {"refs": [{"id": "ref-for-WGNote\u2460\u2464"}, {"id": "ref-for-WGNote\u2460\u2465"}, {"id": "ref-for-WGNote\u2460\u2466"}, {"id": "ref-for-WGNote\u2460\u2467"}, {"id": "ref-for-WGNote\u2460\u2468"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-WGNote\u2461\u24ea"}, {"id": "ref-for-WGNote\u2461\u2460"}], "title": "10.1.1. \nScope of Member Submissions"}], "external": false};
+window.dfnpanelData['draft-note'] = {"dfnID": "draft-note", "url": "#draft-note", "dfnText": "Draft Notes", "refSections": [{"refs": [{"id": "ref-for-draft-note"}, {"id": "ref-for-draft-note\u2460"}], "title": "6.4.1. \nGroup Notes"}, {"refs": [{"id": "ref-for-draft-note\u2461"}, {"id": "ref-for-draft-note\u2462"}, {"id": "ref-for-draft-note\u2463"}, {"id": "ref-for-draft-note\u2464"}], "title": "6.4.2. \nPublishing Notes"}], "external": false};
+window.dfnpanelData['statement'] = {"dfnID": "statement", "url": "#statement", "dfnText": "W3C Statement", "refSections": [{"refs": [{"id": "ref-for-statement"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-statement\u2460"}, {"id": "ref-for-statement\u2461"}, {"id": "ref-for-statement\u2462"}, {"id": "ref-for-statement\u2463"}, {"id": "ref-for-statement\u2464"}, {"id": "ref-for-statement\u2465"}, {"id": "ref-for-statement\u2466"}], "title": "6.4.3. \nElevating Group Notes to W3C Statement status"}, {"refs": [{"id": "ref-for-statement\u2467"}, {"id": "ref-for-statement\u2468"}, {"id": "ref-for-statement\u2460\u24ea"}, {"id": "ref-for-statement\u2460\u2460"}], "title": "6.4.4. \nRevising W3C Statements"}, {"refs": [{"id": "ref-for-statement\u2460\u2461"}], "title": "6.6. \nSwitching Tracks"}], "external": false};
+window.dfnpanelData['registry'] = {"dfnID": "registry", "url": "#registry", "dfnText": "registry", "refSections": [{"refs": [{"id": "ref-for-registry"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-registry\u2460"}, {"id": "ref-for-registry\u2461"}, {"id": "ref-for-registry\u2462"}], "title": "6.5. \nThe Registry Track"}, {"refs": [{"id": "ref-for-registry\u2463"}, {"id": "ref-for-registry\u2464"}], "title": "6.5.1. \nRegistry Definitions"}, {"refs": [{"id": "ref-for-registry\u2465"}, {"id": "ref-for-registry\u2466"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-registry\u2467"}], "title": "6.5.4. \nRegistry Data Reports"}], "external": false};
+window.dfnpanelData['registry-table'] = {"dfnID": "registry-table", "url": "#registry-table", "dfnText": "registry tables", "refSections": [{"refs": [{"id": "ref-for-registry-table"}, {"id": "ref-for-registry-table\u2460"}], "title": "6.2.3. \nClasses of Changes"}, {"refs": [{"id": "ref-for-registry-table\u2461"}, {"id": "ref-for-registry-table\u2462"}, {"id": "ref-for-registry-table\u2463"}], "title": "6.5. \nThe Registry Track"}, {"refs": [{"id": "ref-for-registry-table\u2464"}, {"id": "ref-for-registry-table\u2465"}, {"id": "ref-for-registry-table\u2466"}, {"id": "ref-for-registry-table\u2467"}, {"id": "ref-for-registry-table\u2468"}], "title": "6.5.1. \nRegistry Definitions"}, {"refs": [{"id": "ref-for-registry-table\u2460\u24ea"}, {"id": "ref-for-registry-table\u2460\u2460"}, {"id": "ref-for-registry-table\u2460\u2461"}, {"id": "ref-for-registry-table\u2460\u2462"}, {"id": "ref-for-registry-table\u2460\u2463"}, {"id": "ref-for-registry-table\u2460\u2464"}, {"id": "ref-for-registry-table\u2460\u2465"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-registry-table\u2460\u2466"}, {"id": "ref-for-registry-table\u2460\u2467"}], "title": "6.5.3. \nUpdating Registry Tables"}, {"refs": [{"id": "ref-for-registry-table\u2460\u2468"}, {"id": "ref-for-registry-table\u2461\u24ea"}, {"id": "ref-for-registry-table\u2461\u2460"}], "title": "6.5.4. \nRegistry Data Reports"}], "external": false};
+window.dfnpanelData['registry-entry'] = {"dfnID": "registry-entry", "url": "#registry-entry", "dfnText": "registry entries", "refSections": [{"refs": [{"id": "ref-for-registry-entry"}], "title": "6.2.3. \nClasses of Changes"}, {"refs": [{"id": "ref-for-registry-entry\u2460"}], "title": "6.5.1. \nRegistry Definitions"}, {"refs": [{"id": "ref-for-registry-entry\u2461"}], "title": "6.5.4. \nRegistry Data Reports"}, {"refs": [{"id": "ref-for-registry-entry\u2462"}], "title": "6.5.5. \nSpecifications that Reference Registries"}], "external": false};
+window.dfnpanelData['registry-data'] = {"dfnID": "registry-data", "url": "#registry-data", "dfnText": "registry data", "refSections": [{"refs": [{"id": "ref-for-registry-data"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-registry-data\u2460"}, {"id": "ref-for-registry-data\u2461"}], "title": "6.5.4. \nRegistry Data Reports"}], "external": false};
+window.dfnpanelData['registry-definition'] = {"dfnID": "registry-definition", "url": "#registry-definition", "dfnText": "registry definition", "refSections": [{"refs": [{"id": "ref-for-registry-definition"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-registry-definition\u2460"}], "title": "6.5. \nThe Registry Track"}, {"refs": [{"id": "ref-for-registry-definition\u2461"}], "title": "6.5.1. \nRegistry Definitions"}, {"refs": [{"id": "ref-for-registry-definition\u2462"}, {"id": "ref-for-registry-definition\u2463"}, {"id": "ref-for-registry-definition\u2464"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-registry-definition\u2465"}, {"id": "ref-for-registry-definition\u2466"}, {"id": "ref-for-registry-definition\u2467"}, {"id": "ref-for-registry-definition\u2468"}], "title": "6.5.3. \nUpdating Registry Tables"}, {"refs": [{"id": "ref-for-registry-definition\u2460\u24ea"}, {"id": "ref-for-registry-definition\u2460\u2460"}, {"id": "ref-for-registry-definition\u2460\u2461"}, {"id": "ref-for-registry-definition\u2460\u2462"}], "title": "6.5.4. \nRegistry Data Reports"}], "external": false};
+window.dfnpanelData['custodian'] = {"dfnID": "custodian", "url": "#custodian", "dfnText": "custodian", "refSections": [{"refs": [{"id": "ref-for-custodian"}], "title": "6.5. \nThe Registry Track"}, {"refs": [{"id": "ref-for-custodian\u2460"}, {"id": "ref-for-custodian\u2461"}], "title": "6.5.1. \nRegistry Definitions"}, {"refs": [{"id": "ref-for-custodian\u2462"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-custodian\u2463"}], "title": "6.5.3. \nUpdating Registry Tables"}], "external": false};
+window.dfnpanelData['registry-report'] = {"dfnID": "registry-report", "url": "#registry-report", "dfnText": "registry report", "refSections": [{"refs": [{"id": "ref-for-registry-report"}, {"id": "ref-for-registry-report\u2460"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-registry-report\u2461"}, {"id": "ref-for-registry-report\u2462"}, {"id": "ref-for-registry-report\u2463"}, {"id": "ref-for-registry-report\u2464"}, {"id": "ref-for-registry-report\u2465"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['registry-section'] = {"dfnID": "registry-section", "url": "#registry-section", "dfnText": "registry section", "refSections": [{"refs": [{"id": "ref-for-registry-section"}], "title": "6.1. \nTypes of Technical Reports"}, {"refs": [{"id": "ref-for-registry-section\u2460"}, {"id": "ref-for-registry-section\u2461"}, {"id": "ref-for-registry-section\u2462"}, {"id": "ref-for-registry-section\u2463"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['registry-track'] = {"dfnID": "registry-track", "url": "#registry-track", "dfnText": "Registry Track", "refSections": [{"refs": [{"id": "ref-for-registry-track"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['candidate-registry-snapshot'] = {"dfnID": "candidate-registry-snapshot", "url": "#candidate-registry-snapshot", "dfnText": "Candidate Registry Snapshot", "refSections": [{"refs": [{"id": "ref-for-candidate-registry-snapshot"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['w3c-registry'] = {"dfnID": "w3c-registry", "url": "#w3c-registry", "dfnText": "W3C Registry", "refSections": [{"refs": [{"id": "ref-for-w3c-registry"}], "title": "6.5.2. \nPublishing Registries"}], "external": false};
+window.dfnpanelData['registry-data-report'] = {"dfnID": "registry-data-report", "url": "#registry-data-report", "dfnText": "Registry Data Report", "refSections": [{"refs": [{"id": "ref-for-registry-data-report"}], "title": "6.5.2. \nPublishing Registries"}, {"refs": [{"id": "ref-for-registry-data-report\u2460"}, {"id": "ref-for-registry-data-report\u2461"}], "title": "6.5.4. \nRegistry Data Reports"}], "external": false};
+window.dfnpanelData['Member-only'] = {"dfnID": "Member-only", "url": "#Member-only", "dfnText": "Member-only", "refSections": [{"refs": [{"id": "ref-for-Member-only"}], "title": "2.1.1. \nRights of Members"}, {"refs": [{"id": "ref-for-Member-only"}], "title": "3.2.2. \nParticipation in the Advisory Committee"}, {"refs": [{"id": "ref-for-Member-only"}, {"id": "ref-for-Member-only"}], "title": "3.3.2.3. \nCommunications of the Technical Architecture Group"}, {"refs": [{"id": "ref-for-Member-only"}], "title": "3.4.1. \nRequirements for All Chartered Groups"}, {"refs": [{"id": "ref-for-Member-only\u2460"}], "title": "5.5. \nRegistering Formal Objections"}, {"refs": [{"id": "ref-for-Member-only\u2461"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-Member-only\u2462"}], "title": "5.9. \nAppeal by Advisory Committee Representatives"}, {"refs": [{"id": "ref-for-Member-only\u2463"}, {"id": "ref-for-Member-only\u2464"}, {"id": "ref-for-Member-only\u2465"}, {"id": "ref-for-Member-only\u2466"}, {"id": "ref-for-Member-only\u2467"}], "title": "7.2. \nConfidentiality Levels"}, {"refs": [{"id": "ref-for-Member-only\u2468"}, {"id": "ref-for-Member-only\u2460\u24ea"}, {"id": "ref-for-Member-only\u2460\u2460"}], "title": "7.3. \nChanging Confidentiality Level"}], "external": false};
+window.dfnpanelData['Team-only'] = {"dfnID": "Team-only", "url": "#Team-only", "dfnText": "Team-only", "refSections": [{"refs": [{"id": "ref-for-Team-only"}], "title": "2.1. \nMembers"}, {"refs": [{"id": "ref-for-Team-only"}], "title": "5.7.1. \nStart of a Review Period"}, {"refs": [{"id": "ref-for-Team-only\u2460"}], "title": "7.2. \nConfidentiality Levels"}, {"refs": [{"id": "ref-for-Team-only\u2461"}, {"id": "ref-for-Team-only\u2462"}, {"id": "ref-for-Team-only\u2463"}, {"id": "ref-for-Team-only\u2464"}], "title": "7.3. \nChanging Confidentiality Level"}, {"refs": [{"id": "ref-for-Team-only\u2465"}], "title": "10.2. \nTeam Rights and Obligations"}], "external": false};
+window.dfnpanelData['EventsW'] = {"dfnID": "EventsW", "url": "#EventsW", "dfnText": "Workshops", "refSections": [{"refs": [{"id": "ref-for-EventsW"}], "title": "7.1. \nPublic Communication"}], "external": false};
+window.dfnpanelData['technical-agreement'] = {"dfnID": "technical-agreement", "url": "#technical-agreement", "dfnText": "technical agreement", "refSections": [{"refs": [{"id": "ref-for-technical-agreement"}, {"id": "ref-for-technical-agreement\u2460"}, {"id": "ref-for-technical-agreement\u2461"}, {"id": "ref-for-technical-agreement\u2462"}, {"id": "ref-for-technical-agreement\u2463"}, {"id": "ref-for-technical-agreement\u2464"}, {"id": "ref-for-technical-agreement\u2465"}, {"id": "ref-for-technical-agreement\u2466"}, {"id": "ref-for-technical-agreement\u2467"}], "title": "9. \nLiaisons"}], "external": false};
+window.dfnpanelData['MemberSubmission'] = {"dfnID": "MemberSubmission", "url": "#MemberSubmission", "dfnText": "Member Submission", "refSections": [{"refs": [{"id": "ref-for-MemberSubmission"}, {"id": "ref-for-MemberSubmission\u2460"}, {"id": "ref-for-MemberSubmission\u2461"}, {"id": "ref-for-MemberSubmission\u2462"}], "title": "10. \nMember Submission Process"}, {"refs": [{"id": "ref-for-MemberSubmission\u2463"}], "title": "10.1. \nSubmitter Rights and Obligations"}, {"refs": [{"id": "ref-for-MemberSubmission\u2464"}], "title": "10.2. \nTeam Rights and Obligations"}, {"refs": [{"id": "ref-for-MemberSubmission\u2465"}], "title": "10.3. \nAcknowledgment of a Submission Request"}], "external": false};
+window.dfnpanelData['submitter'] = {"dfnID": "submitter", "url": "#submitter", "dfnText": "Submitter(s)", "refSections": [{"refs": [{"id": "ref-for-submitter"}, {"id": "ref-for-submitter\u2460"}, {"id": "ref-for-submitter\u2461"}, {"id": "ref-for-submitter\u2462"}], "title": "10. \nMember Submission Process"}, {"refs": [{"id": "ref-for-submitter\u2463"}, {"id": "ref-for-submitter\u2464"}, {"id": "ref-for-submitter\u2465"}, {"id": "ref-for-submitter\u2466"}, {"id": "ref-for-submitter\u2467"}, {"id": "ref-for-submitter\u2468"}], "title": "10.1. \nSubmitter Rights and Obligations"}, {"refs": [{"id": "ref-for-submitter\u2460\u24ea"}, {"id": "ref-for-submitter\u2460\u2460"}, {"id": "ref-for-submitter\u2460\u2461"}, {"id": "ref-for-submitter\u2460\u2462"}], "title": "10.1.2. \nInformation Required in a Submission Request"}, {"refs": [{"id": "ref-for-submitter\u2460\u2463"}], "title": "10.2. \nTeam Rights and Obligations"}, {"refs": [{"id": "ref-for-submitter\u2460\u2464"}, {"id": "ref-for-submitter\u2460\u2465"}, {"id": "ref-for-submitter\u2460\u2466"}], "title": "10.3. \nAcknowledgment of a Submission Request"}, {"refs": [{"id": "ref-for-submitter\u2460\u2467"}, {"id": "ref-for-submitter\u2460\u2468"}, {"id": "ref-for-submitter\u2461\u24ea"}, {"id": "ref-for-submitter\u2461\u2460"}, {"id": "ref-for-submitter\u2461\u2461"}, {"id": "ref-for-submitter\u2461\u2462"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}], "external": false};
+window.dfnpanelData['validation-notice'] = {"dfnID": "validation-notice", "url": "#validation-notice", "dfnText": "validation notice", "refSections": [{"refs": [{"id": "ref-for-validation-notice"}], "title": "10.3. \nAcknowledgment of a Submission Request"}], "external": false};
+window.dfnpanelData['submission-appeals'] = {"dfnID": "submission-appeals", "url": "#submission-appeals", "dfnText": "Submission Appeals", "refSections": [{"refs": [{"id": "ref-for-submission-appeals"}], "title": "10.4. \nRejection of a Submission Request, and Submission Appeals"}], "external": false};
+</script>
+<script>/* Boilerplate: script-dom-helper */
+function query(sel) { return document.querySelector(sel); }
+
+function queryAll(sel) { return [...document.querySelectorAll(sel)]; }
+
+function iter(obj) {
+	if(!obj) return [];
+	var it = obj[Symbol.iterator];
+	if(it) return it;
+	return Object.entries(obj);
+}
+
+function mk(tagname, attrs, ...children) {
+	const el = document.createElement(tagname);
+	for(const [k,v] of iter(attrs)) {
+		if(k.slice(0,3) == "_on") {
+			const eventName = k.slice(3);
+			el.addEventListener(eventName, v);
+		} else if(k[0] == "_") {
+			// property, not attribute
+			el[k.slice(1)] = v;
+		} else {
+			if(v === false || v == null) {
+        continue;
+      } else if(v === true) {
+        el.setAttribute(k, "");
+        continue;
+      } else {
+  			el.setAttribute(k, v);
+      }
+		}
+	}
+	append(el, children);
+	return el;
+}
+
+/* Create shortcuts for every known HTML element */
+[
+  "a",
+  "abbr",
+  "acronym",
+  "address",
+  "applet",
+  "area",
+  "article",
+  "aside",
+  "audio",
+  "b",
+  "base",
+  "basefont",
+  "bdo",
+  "big",
+  "blockquote",
+  "body",
+  "br",
+  "button",
+  "canvas",
+  "caption",
+  "center",
+  "cite",
+  "code",
+  "col",
+  "colgroup",
+  "datalist",
+  "dd",
+  "del",
+  "details",
+  "dfn",
+  "dialog",
+  "div",
+  "dl",
+  "dt",
+  "em",
+  "embed",
+  "fieldset",
+  "figcaption",
+  "figure",
+  "font",
+  "footer",
+  "form",
+  "frame",
+  "frameset",
+  "head",
+  "header",
+  "h1",
+  "h2",
+  "h3",
+  "h4",
+  "h5",
+  "h6",
+  "hr",
+  "html",
+  "i",
+  "iframe",
+  "img",
+  "input",
+  "ins",
+  "kbd",
+  "label",
+  "legend",
+  "li",
+  "link",
+  "main",
+  "map",
+  "mark",
+  "meta",
+  "meter",
+  "nav",
+  "nobr",
+  "noscript",
+  "object",
+  "ol",
+  "optgroup",
+  "option",
+  "output",
+  "p",
+  "param",
+  "pre",
+  "progress",
+  "q",
+  "s",
+  "samp",
+  "script",
+  "section",
+  "select",
+  "small",
+  "source",
+  "span",
+  "strike",
+  "strong",
+  "style",
+  "sub",
+  "summary",
+  "sup",
+  "table",
+  "tbody",
+  "td",
+  "template",
+  "textarea",
+  "tfoot",
+  "th",
+  "thead",
+  "time",
+  "title",
+  "tr",
+  "u",
+  "ul",
+  "var",
+  "video",
+  "wbr",
+  "xmp",
+].forEach(tagname=>{
+	mk[tagname] = (...args) => mk(tagname, ...args);
+});
+
+function* nodesFromChildList(children) {
+	for(const child of children.flat(Infinity)) {
+		if(child instanceof Node) {
+			yield child;
+		} else {
+			yield new Text(child);
+		}
+	}
+}
+function append(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		if(el instanceof Node) el.appendChild(child);
+		else el.push(child);
+	}
+	return el;
+}
+
+function insertAfter(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		el.parentNode.insertBefore(child, el.nextSibling);
+	}
+	return el;
+}
+
+function clearContents(el) {
+	el.innerHTML = "";
+	return el;
+}
+
+function parseHTML(markup) {
+	if(markup.toLowerCase().trim().indexOf('<!doctype') === 0) {
+		const doc = document.implementation.createHTMLDocument("");
+		doc.documentElement.innerHTML = markup;
+		return doc;
+	} else {
+		const el = mk.template({});
+		el.innerHTML = markup;
+		return el.content;
+	}
+}
+</script>

From 7723ca396d274e355834938a9a2837a788cd90f6 Mon Sep 17 00:00:00 2001
From: Denis Ah-Kang <1696128+deniak@users.noreply.github.com>
Date: Wed, 6 Sep 2023 03:00:46 +0400
Subject: [PATCH 011/237] update link to W3C submissions (#783)

---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 5b6b6cb1..d52a5547 100644
--- a/index.bs
+++ b/index.bs
@@ -5218,7 +5218,7 @@ Member Submission Process</h2>
 	A Member Submission made available by W3C
 	<em class="rfc2119">must not</em> be referred to as “work in progress” of W3C.
 
-	The list of <a href="https://www.w3.org/Submission/">acknowledged Member Submissions</a> [[SUBMISSION-LIST]]
+	The list of <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a> [[SUBMISSION-LIST]]
 	is available at the W3C website.
 
 <h3 id="SubmissionRights">
@@ -5689,7 +5689,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"SUBMISSION-LIST": {
-		"href": "https://www.w3.org/Submission/",
+		"href": "https://www.w3.org/submissions/",
 		"title": "The list of acknowledged Member Submissions",
 		"publisher": "W3C"
 	},

From 37ed9f6a0367924ad6e6120432abcabed4c226b9 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 11 Oct 2023 09:34:38 +0900
Subject: [PATCH 012/237] Replace stray instance of MoU leftover from renaming
 technical agreement

Follow up on https://github.com/w3c/w3process/commit/38e8f5e3ce881b78de108335a06e6cd1610ae396
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index d52a5547..58cf963e 100644
--- a/index.bs
+++ b/index.bs
@@ -2732,7 +2732,7 @@ Appeal by Advisory Committee Representatives</h3>
 	and include
 	additional (non-reviewed) maturity stages of Recommendation Track documents,
 	group [=charter extensions=] and closures,
-	and [=Memoranda of Understanding=].
+	and [=technical agreements=].
 
 	In all cases,
 	an [=appeal=] <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the decision.

From bbd6368673f93693fbd655389d40d5cf69fc75aa Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Wed, 11 Oct 2023 10:53:03 -0400
Subject: [PATCH 013/237] Must report dismissal vote counts. #748 (#760)

---
 index.bs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 58cf963e..165c4643 100644
--- a/index.bs
+++ b/index.bs
@@ -2552,7 +2552,8 @@ Council Decision Report</h5>
 	* <em class=rfc2119>must</em> include the [=Minority Opinion=](s), if any.
 	* <em class=rfc2119>must</em> report the names of those who were [=dismissed=] or [=renounced=] their seat as well as those who were qualified to serve.
 	* <em class=rfc2119>must</em> report the names of the individuals who participated in the final decision.
-	* <em class=rfc2119>may</em> report vote totals, if any vote was held.
+	* <em class=rfc2119>must</em> report the number of votes for/against dismissing each participant.
+	* <em class=rfc2119>may</em> report vote totals for the Council’s decision, if a formal vote was held.
 	* <em class=rfc2119>must not</em> attribute any position to any individual on the Council.
 
 	The [=Team=] <em class=rfc2119>must</em> maintain a [[COUNCIL-REPORT-INDEX inline|public page on the W3C website]]

From 1ef2a5909d789008b78324a073f48e532f7e439b Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Wed, 11 Oct 2023 10:55:42 -0400
Subject: [PATCH 014/237] Exclude TAG/AB from voting on their own
 decisions/proposals. #749 (#761)

See #749
---
 index.bs | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/index.bs b/index.bs
index 165c4643..9adb2493 100644
--- a/index.bs
+++ b/index.bs
@@ -2521,6 +2521,11 @@ Council Deliberations</h5>
 	In that case,
 	the decision is made by simple majority,
 	with the [=W3C Council Chair=] breaking any tie.
+	However,
+	if the decision or proposal being objected to
+	originated with the TAG or AB,
+	then members of that group at the time the decision or proposal was made
+	must abstain in such a vote.
 	In case of a vote,
 	if two members of a Council who share the same affiliation cast an identical ballot,
 	then their ballots count as a one vote,

From e4d66f492f09691e31c6f0184d8a0d5c2010b630 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 11 Oct 2023 23:58:07 +0900
Subject: [PATCH 015/237] Clarify approvals of TAG+AB for REC track regression

See #741

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 9adb2493..88c29c41 100644
--- a/index.bs
+++ b/index.bs
@@ -4231,7 +4231,7 @@ Regression on the Recommendation Track</h4>
 	as described above.
 
 	Additionally,
-	with the approval of the [=TAG=] and the [=AB=]
+	with the approvals (by [=group decision=]) of each of the [=TAG=] and the [=AB=]
 	the [=Team=] <em class="rfc2119">may</em> return
 	the [=technical report=] to a lower <a href="#maturity-stages">maturity stage</a>
 	in response to [=wide review=] or a [=formal objection=].

From db820bca4d022e6e57d7e8ea016d7d6269424cf8 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 11 Oct 2023 09:21:42 +0900
Subject: [PATCH 016/237] Add requirement to make progress on external issues
 for update requests

See #781
---
 index.bs | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 88c29c41..4f46f9b7 100644
--- a/index.bs
+++ b/index.bs
@@ -3563,7 +3563,10 @@ Updating Mature Publications on the Recommendation Track</h4>
 			<em>should</em> be withheld if any Process requirements are not met,
 			and <em class=rfc2119>may</em> be withheld in consideration of unresolved Formal Objections
 			(including any [=upheld=] by a [=Council=] but not yet [=fully addressed=])
-			or if the document does not adequately reflect all relevant decisions of the [=W3C Council=] (or its delegates).
+			if the document does not adequately reflect all relevant decisions of the [=W3C Council=] (or its delegates),
+			or if the [=Team=] believes the [=Group=] is
+			not making reasonable progress
+			on addressing issues raised by individuals external to the [=Group=].
 			If the [=Team=] rejects an [=Update Request=],
 			it must indicate its rationale to the [=Working Group=].
 			If it waives any Process requirements,

From 5372b2c953fa9403d598fd65509ad5f261eec8cf Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 11 Oct 2023 09:27:33 +0900
Subject: [PATCH 017/237] Reorg long sentence as bulleted list

---
 index.bs | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

diff --git a/index.bs b/index.bs
index 4f46f9b7..870dc075 100644
--- a/index.bs
+++ b/index.bs
@@ -3559,14 +3559,19 @@ Updating Mature Publications on the Recommendation Track</h4>
 		<li>
 			<em class="rfc2119">must </em> obtain [=Team=] verification,
 			or fulfill the criteria for [[#streamlined-update]].
-			[=Team=] verification (a [=Team decision=]),
-			<em>should</em> be withheld if any Process requirements are not met,
-			and <em class=rfc2119>may</em> be withheld in consideration of unresolved Formal Objections
-			(including any [=upheld=] by a [=Council=] but not yet [=fully addressed=])
-			if the document does not adequately reflect all relevant decisions of the [=W3C Council=] (or its delegates),
-			or if the [=Team=] believes the [=Group=] is
-			not making reasonable progress
-			on addressing issues raised by individuals external to the [=Group=].
+			[=Team=] verification (a [=Team decision=]):
+			* <em class=rfc2119>should</em> be withheld
+				if any Process requirements are not met,
+			* <em class=rfc2119>may</em> be withheld
+				in consideration of unresolved Formal Objections
+				(including any [=upheld=] by a [=Council=] but not yet [=fully addressed=]),
+			* <em class=rfc2119>may</em> be withheld
+				if the document does not adequately reflect
+				all relevant decisions of the [=W3C Council=] (or its delegates),
+			* <em class=rfc2119>may</em> be withheld
+				if the Team believes the Group is not making reasonable progress
+				on addressing issues raised by individuals external to the Group.
+
 			If the [=Team=] rejects an [=Update Request=],
 			it must indicate its rationale to the [=Working Group=].
 			If it waives any Process requirements,

From 9324a7721691ff76a6eab2d9defb70d92d6ef7b0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 11 Oct 2023 23:58:49 +0900
Subject: [PATCH 018/237] phrasing tweak

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 870dc075..aa251e74 100644
--- a/index.bs
+++ b/index.bs
@@ -3567,7 +3567,7 @@ Updating Mature Publications on the Recommendation Track</h4>
 				(including any [=upheld=] by a [=Council=] but not yet [=fully addressed=]),
 			* <em class=rfc2119>may</em> be withheld
 				if the document does not adequately reflect
-				all relevant decisions of the [=W3C Council=] (or its delegates),
+				all relevant decisions of a [=W3C Council=] (or its delegates),
 			* <em class=rfc2119>may</em> be withheld
 				if the Team believes the Group is not making reasonable progress
 				on addressing issues raised by individuals external to the Group.

From 01bd3709a91e7fc7adcc7b2bb7e21a7eb9beeda4 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 11 Oct 2023 09:47:29 +0900
Subject: [PATCH 019/237] [editorial] More explicitly Trigger FO handling
 process

See #739
---
 index.bs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/index.bs b/index.bs
index aa251e74..2070d0fc 100644
--- a/index.bs
+++ b/index.bs
@@ -2303,6 +2303,9 @@ Registering Formal Objections</h3>
 	A [=Formal Objection=] filed during an [=Advisory Committee Review=]
 	is considered registered at the close of the review period.
 
+	Registering a [=Formal Objection=] initiates the process of
+	[[#addressing-fo|addressing the Formal Objection]].
+
 <h3 id=addressing-fo>
 Addressing Formal Objections</h3>
 

From f6c06702d0f5589744a7b5197a305ec89c3c45ea Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 9 Nov 2023 01:08:15 +0900
Subject: [PATCH 020/237] Enable Team to replace defunct registry custodians
 when no-one else can (#790)

See issue #699

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/index.bs b/index.bs
index 2070d0fc..88ca23de 100644
--- a/index.bs
+++ b/index.bs
@@ -4663,6 +4663,17 @@ Registry Definitions</h4>
 			The [=custodian=] may be the [=Working Group=], the [=Team=], or a delegated entity.
 			The [=custodian=] for all [=registry tables=] in a single [=registry=]
 			<em class=rfc2119>should</em> generally be the same entity.
+
+			If the [=custodian=] of a [=registry table=]
+			ceases to exist or to operate as a custodian
+			(e.g., the relevant group is disbanded, or 
+			the custodian is unresponsive to repeated attempts to make contact),
+			and the [=Working Group=] that owns the [=registry definition=] 
+			is itself <a href="#GeneralTermination">closed</a> or 
+			unresponsive,
+			the [=Team=] <em class=rfc2119>should</em> propose replacing the [=custodian=],
+			which <em class=rfc2119>must</em> be confirmed
+			by an [=AC Review=] as a [=W3C Decision=].
 	</ul>
 
 <h4 id=reg-pub>

From 79c544a39df32d9d213412a222e2ed787c02df0f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 9 Nov 2023 01:30:28 +0900
Subject: [PATCH 021/237] Post publication update

Includes an update changes list
---
 index.bs | 41 ++++++++++++++++++++++++-----------------
 1 file changed, 24 insertions(+), 17 deletions(-)

diff --git a/index.bs b/index.bs
index 88ca23de..2b2c7fcc 100644
--- a/index.bs
+++ b/index.bs
@@ -29,12 +29,7 @@ Group: processcg
 Status: CG-DRAFT
 ED: https://www.w3.org/Consortium/Process/Drafts/
 TR: https://www.w3.org/Consortium/Process/
-Previous Version: https://www.w3.org/2023/Process-20230612/
-Previous Version: https://www.w3.org/2021/Process-20211102/
-Previous Version: https://www.w3.org/2020/Process-20200915/
-Previous Version: https://www.w3.org/2019/Process-20190301/
-Previous Version: https://www.w3.org/2018/Process-20180201/
-Previous Version: https://www.w3.org/2017/Process-20170301/
+Previous Version: https://www.w3.org/2023/Process-20231103/
 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
@@ -54,7 +49,7 @@ Abstract:
 	please refer to <a href="https://www.w3.org/Consortium/">About W3C</a>.
 Status Text:
 	This document,
-	which is based on the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a>,
+	which is based on the <a href="https://www.w3.org/2023/Process-20231103/">3 November 2023 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/Consortium/Process/#GAProcess">Section 11 Process Changes</a>,
@@ -5667,14 +5662,14 @@ Changes</h2>
 
 	<em>This section is non-normative.</em>
 
-<h3 id=changes-2023-1 class=no-num>
-Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a></h3>
+<h3 id=changes-2024 class=no-num>
+Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November 2023 Process</a></h3>
 
-	<p>This document is based on the <a href="https://www.w3.org/2023/Process-20230612/">12 June 2023 Process</a>.
-	A <a href="https://github.com/w3c/w3process/issues?q=milestone%3A%22Process+2023-1%22+is%3Aclosed">list of issues addressed</a>,
+	<p>This document is based on the <a href="https://www.w3.org/2023/Process-20231103/">3 November 2023 Process</a>.
+	A <a href="https://github.com/w3c/w3process/issues?q=milestone%3A%22Process+2024%22+is%3Aclosed">list of issues addressed</a>,
 	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2F">diff from Process 2023 to this latest version</a>,
 	as well as
-	a <a href="https://github.com/w3c/w3process/compare/p2023...main">detailed log of all changes since then</a>
+	a <a href="https://github.com/w3c/w3process/compare/p2023_1...main">detailed log of all changes since then</a>
 	are available.
 
 	<!--
@@ -5683,20 +5678,32 @@ Changes since the <a href="https://www.w3.org/2023/Process-20230612/">12 June 20
 	the following is a summary of the main differences:
 	-->
 
-	The only change is:
+	In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:
 
 	<ul>
 		<li>
-			Expand the TAG from 6 elected and 3 appointed to 8 and 3.
-			See <a href="https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-05-24-doc#tag-size">the 2023-05-24 Disposition of Comments</a> for rationale.
+			Council dismissal vote counts must be reported.
+			(See <a href="https://github.com/w3c/w3process/issues/748">Issue 748</a>)
+
+		<li>
+			Exclude TAG/AB from voting on their own decisions/proposals.
+			(See <a href="https://github.com/w3c/w3process/issues/749">Issue 749</a>)
+
+		<li>
+			Add a requirement to make progress on external issues for update requests
+			(See <a href="https://github.com/w3c/w3process/issues/781">Issue 781</a>)
+
+		<li>
+			Enable Team to replace defunct registry custodians when no-one else can.
+			(See <a href="https://github.com/w3c/w3process/issues/699">Issue 699</a>)
 	</ul>
 
 
-<h3 id=changes-previous class=no-num oldids="changes-2023, changes-2021, changes-2020, changes-2019, changes-2018, changes-2017">
+<h3 id=changes-previous class=no-num oldids="changes-2023-1, changes-2023, changes-2021, changes-2020, changes-2019, changes-2018, changes-2017">
 Changes since earlier versions</h3>
 
 	Changes since earlier versions of the Process are detailed
-	in the <a href="https://www.w3.org/2023/Process-20230612/#changes">changes section of the previous version</a>
+	in the <a href="https://www.w3.org/2023/Process-20231103/#changes">changes section of the previous version</a>
 	of the Process.
 
 <pre class=biblio>

From fe0320bc0e0049d40f544e02d87bec6ba4dcee13 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 9 Nov 2023 01:33:04 +0900
Subject: [PATCH 022/237] Stop citing the "superseded" TAG charter

See #794
---
 index.bs | 15 +++++----------
 1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/index.bs b/index.bs
index 2b2c7fcc..801e940f 100644
--- a/index.bs
+++ b/index.bs
@@ -972,16 +972,12 @@ Role of the Technical Architecture Group</h5>
 	the W3C Advisory Committee,
 	Advisory Board,
 	and Team.
-	Please refer to the <a href="https://www.w3.org/2004/10/27-tag-charter.html">TAG charter</a> [[TAG-CHARTER]]
-	for more information about the background and scope of the TAG,
-	and the expected qualifications of TAG participants.
 
 	When the [=TAG=] votes to resolve an issue,
 	each TAG participant
 	(whether appointed, elected, or the Chair)
 	has one vote;
-	see also the section on <a href="https://www.w3.org/2004/10/27-tag-charter.html#Voting">voting in the TAG charter</a> [[TAG-CHARTER]]
-	and the general section on <a href="#Votes">votes</a> in this Process Document.
+	see also the general section on <a href="#Votes">votes</a> in this Process Document.
 
 	Details about the [=TAG=]
 	(e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings)
@@ -5696,6 +5692,10 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 		<li>
 			Enable Team to replace defunct registry custodians when no-one else can.
 			(See <a href="https://github.com/w3c/w3process/issues/699">Issue 699</a>)
+
+		<li>
+			Stop citing the superseded TAG charter.
+			(See <a href="https://github.com/w3c/w3process/issues/794">Issue 794</a>)
 	</ul>
 
 
@@ -5763,11 +5763,6 @@ Changes since earlier versions</h3>
 		"title": "Conflict of Interest Policy for W3C Team Members Engaged in Outside Professional Activities",
 		"publisher": "W3C"
 	},
-	"TAG-CHARTER": {
-		"href": "https://www.w3.org/2004/10/27-tag-charter.html",
-		"title": "Technical Architecture Group (TAG) Charter",
-		"publisher": "W3C"
-	},
 	"TAG-HP": {
 		"href": "https://www.w3.org/2001/tag/",
 		"title": "The TAG home page",

From dcd212d3cc2dbb3972b4c68deb730117513d0feb Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 7 Dec 2023 11:30:15 +0900
Subject: [PATCH 023/237] [Editorial] More precise links

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 801e940f..067f1970 100644
--- a/index.bs
+++ b/index.bs
@@ -2003,7 +2003,7 @@ Types of Decisions</h3>
 	In contrast,
 	a <dfn id="def-w3c-decision">W3C decision</dfn> is
 	determined by the [=Team=] on behalf of the W3C community
-	by assessing the consensus of the W3C Community after an [=Advisory Committee review=].
+	by <a href="#ACReviewAfter">assessing the consensus of the W3C Community</a> after an <a href="#ACReview">Advisory Committee review</a>.
 
 <h3 id=consensus-building>
 Consensus Building</h3>

From 40b9132a415ac5d07b0196feb1c1fbddc3eceb55 Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Wed, 13 Dec 2023 22:32:39 -0500
Subject: [PATCH 024/237] Improve headings in AC Review section

See #802

Co-authored-by: Florian Rivoal <git@florian.rivoal.net>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index 067f1970..24a869a3 100644
--- a/index.bs
+++ b/index.bs
@@ -2576,16 +2576,17 @@ Appealing Council Decisions</h5>
 	of a Council decision issued in a [=Council Report=].
 
 <h3 id="ACReview">
-Advisory Committee Reviews</h3>
+Advisory Committee Reviews and W3C Decisions</h3>
 
-	<dfn export lt="Advisory Committee review | AC Review"> Advisory Committee review</dfn> is the process
-	by which the [=Advisory Committee=] formally confers its approval
+	The [=Advisory Committee=] formally confers its approval
 	on [=charters=],
 	[=technical reports=],
-	and other matters.
+	and other matters
+	through an <dfn export lt="Advisory Committee review | AC Review">Advisory Committee review</dfn>
+	and its resulting [=W3C Decision=].
 
 <h4 id="ACReviewStart">
-Start of a Review Period</h4>
+Initiating an Advisory Committee Review</h4>
 
 	Each [=Advisory Committee review=] period
 	begins with a Call for Review from the [=Team=] to the [=Advisory Committee=].
@@ -2624,7 +2625,7 @@ Start of a Review Period</h4>
 	(e.g., in light of comments from other Members).
 
 <h4 id="ACReviewAfter">
-After the Review Period</h4>
+Determining the W3C Decision</h4>
 
 	After the review period,
 	the [=Team=] determines the appropriate [=W3C Decision=],

From 40c7d094d77565b202ad51a479e1e6f62ebcea5a Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 14 Dec 2023 12:40:02 +0900
Subject: [PATCH 025/237] Eliminate a number of non-normative uses of rfc2119
 language

See #745

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Jeffrey Yasskin <jyasskin@gmail.com>
---
 index.bs | 42 ++++++++++++++++++++++--------------------
 1 file changed, 22 insertions(+), 20 deletions(-)

diff --git a/index.bs b/index.bs
index 24a869a3..c8461fcf 100644
--- a/index.bs
+++ b/index.bs
@@ -59,6 +59,7 @@ Issue Tracking: Github (preferred) https://github.com/w3c/w3process/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
+Complain About: accidental-2119 yes
 </pre>
 
 <style>
@@ -1244,9 +1245,10 @@ Technical Architecture Group Appointments</h5>
 	for more than two <em>consecutive</em> terms.
 	(Partial terms used to fill a vacated seat do not count towards this limit.)
 
-	Note: Individuals who have reached the limit of two consecutive appointed terms
-	<em class=rfc2119>may</em> freely run for election
-	if they wish to continue serving on the [=TAG=].
+	Note: Since there are no limits on elected terms,
+	this limit on appointed terms does not constrain
+	term-limited appointees
+	from running for election at any time.
 
 	The [=Team=]'s choice of appointee(s)
 	is subject to ratification by secret ballot
@@ -1733,8 +1735,8 @@ Content of a Charter</h3>
 		<li>
 			Expected milestone dates where available.
 
-			Note: A charter is <em class="rfc2119">not required</em>
-			to include schedules for review of other group's deliverables.
+			Note: A charter does not need to include
+			schedules for review of other group's deliverables.
 
 		<li>
 			The process for the group to approve the release of deliverables
@@ -2085,10 +2087,10 @@ Consensus</h4>
 	Note: Chairs have substantial flexibility
 	in how they obtain and assess consensus among their groups.
 	Unless otherwise constrained by charter,
-	they may use modes including but not limited to explicit calls for consensus,
+	they can use modes including but not limited to explicit calls for consensus,
 	polls of participants,
 	“lazy consensus” in which lack of objection after sufficient notice is taken as assent;
-	or they may also delegate and empower a document editor
+	they can also delegate and empower a document editor
 	to assess consensus on their behalf,
 	whether in general
 	or for specific pre-determined circumstances
@@ -2288,7 +2290,7 @@ Registering Formal Objections</h3>
 	related to that review.
 
 	Note: [=Formal Objections=] against matter in a [=technical report=]
-	are required to be addressed before <a href="#rec-advance">requesting advancement</a>
+	<a href="#adv-verif-reqs">are expected to be fully addressed</a> before <a href="#rec-advance">requesting advancement</a>
 	of the [=technical report=].
 
 	A [=Formal Objection=] filed during an [=Advisory Committee Review=]
@@ -2417,7 +2419,7 @@ Council Participation, Dismissal, and Renunciation</h5>
 
 	Note: Since dismissal is individual,
 	when the decision being objected to was made by the [=TAG=] or [=AB=] acting as a body,
-	the entire [=TAG=] or [=AB=] is not expected or required to be dismissed.
+	the entire [=TAG=] or [=AB=] is not expected to be dismissed.
 
 	An individual <em class=rfc2119>may</em> also <dfn lt="renounce | renunciation">renounce</dfn> their seat on a Council, for strong reason,
 	such as being forbidden by their employer to serve. The individual chooses the extent to which they explain
@@ -3268,7 +3270,7 @@ Maturity Stages on the Recommendation Track</h4>
 			that the document is considered complete and fit for purpose,
 			and that no further refinement to the text is expected
 			without additional implementation experience and testing;
-			additional features in a later revision may however be expected.
+			however, additional features might be expected in a later revision.
 			A [=Candidate Recommendation=] is expected to be as well-written,
 			detailed,
 			self-consistent,
@@ -3479,7 +3481,7 @@ Advancement on the Recommendation Track</h4>
 		<li>
 			<em class="rfc2119">must</em> record the group's decision to request advancement.
 
-		<li>
+		<li id=adv-verif-reqs>
 			<em class="rfc2119">must </em> obtain [=Team=] verification.
 			[=Team=] verification (a [=Team decision=])
 			<em class=rfc2119>must</em> be withheld if any Process requirements are not met
@@ -4312,10 +4314,10 @@ Abandoning a W3C Recommendation</h5>
 	W3C follows the process for <a href="#revising-rec">modifying a Recommendation</a>.
 
 
-	Note: For the purposes of the W3C Patent Policy
+	Note: For the purposes of the W3C Patent Policy,
 	[[PATENT-POLICY]]
 	an [=Obsolete Recommendation|Obsolete=] or [=Superseded Recommendation=] has the status of an active [=Recommendation=],
-	although it is not recommended for future implementation;
+	although it is not advised for future implementation;
 	a [=Rescinded Recommendation=] ceases to be in effect
 	and no new licenses are granted under the Patent Policy.
 
@@ -4792,7 +4794,7 @@ Updating Registry Tables</h4>
 	to empower the custodian to add commentary on individual entries,
 	this needs to be part of the registry table’s definition.
 	If other changes are desired,
-	they must be requested of the responsible Working Group--
+	they need to be requested of the responsible Working Group--
 	or in the absence of a Working Group, of the Team.
 
 	Changes to the [=registry tables=]
@@ -4855,15 +4857,15 @@ Specifications that Reference Registries</h4>
 
 	<div class=example>
 		For example,
-		“All implementations must implement the <code>Basic-Method</code> as defined in the registry”
-		is not acceptable;
+		 <span class=allow-2119>“All implementations must implement the <code>Basic-Method</code> as defined in the registry”</span>
+		is not acceptable because
 		a change to the definition of the <code>Basic-Method</code> in the registry would then affect conformance.
-		Instead, the requirement must be complete in the specification,
+		Instead, the requirement has to be complete in the specification,
 		directly or by reference to another specification.
 		For example
-		“All implementations must recognize the name <code>Basic-Method</code>,
-		and implement it as defined by section yy of IETF RFC xxxx”.
-		(The Registry should nonetheless contain </code>Basic-Method</code> as an entry.)
+		 <span class=allow-2119>“All implementations must recognize the name <code>Basic-Method</code>,
+		and implement it as defined by section yy of IETF RFC xxxx”</span>.
+		(The Registry is nonetheless expected to contain </code>Basic-Method</code> as an entry.)
 	</div>
 
 <h3 id="switching-tracks">

From 29c65c538eee1ec8e8509ee7ca9fe9c6e135270f Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Wed, 24 Jan 2024 07:09:53 -0800
Subject: [PATCH 026/237] Clarify FO publication timing #735 (#808)

Co-authored-by: Florian Rivoal <git@florian.rivoal.net>
---
 index.bs | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index c8461fcf..db8478bb 100644
--- a/index.bs
+++ b/index.bs
@@ -2281,13 +2281,17 @@ Registering Formal Objections</h3>
 	rationales,
 	and decisions <em class="rfc2119">should</em> also be recorded.
 
-	A record of each [=Formal Objection=] against a decision regarding a publicly-available document
+	No later than when the <a href="#team-fo-mediation">relevant Council is initiated</a>,
+	a record of each [=Formal Objection=] against a decision regarding a publicly-available document
 	<em class="rfc2119">must</em> be made <a href="#confidentiality-change">publicly available</a>;
 	likewise, a record of each [=Formal Objection=] against a [=Member-only|Member-visible=] decision
 	<em class="rfc2119">must</em> be made <a href="#confidentiality-change">available to Members</a>.
 	A Call for Review to the Advisory Committee
 	<em class="rfc2119">must</em> identify any [=Formal Objections=]
 	related to that review.
+	This requirement is waived
+	if the [=Formal Objection=] is resolved to the satisfaction of the objector
+	before its <a href="#confidentiality-change">confidentiality is changed</a>.
 
 	Note: [=Formal Objections=] against matter in a [=technical report=]
 	<a href="#adv-verif-reqs">are expected to be fully addressed</a> before <a href="#rec-advance">requesting advancement</a>

From 15cd932e886181de3e1b4f747bb1822f8549da44 Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Wed, 24 Jan 2024 08:06:39 -0800
Subject: [PATCH 027/237] Reduce confusion wrt registry sections (#807)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* Rename “registry section” to “embedded registry”.
* Move paragraph about Patent Policy to its own section.
* Remove the words “purely documentational” because
  it's easy to confuse with “informative” / “non-normative”.
* Add “(only)” to the sentence making registries non-normative
  for Patent Policy purposes.

See #807

Co-authored-by: Florian Rivoal <git@florian.rivoal.net>
Co-authored-by: Chris Needham <chrisn@users.noreply.github.com>
Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 35 +++++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 14 deletions(-)

diff --git a/index.bs b/index.bs
index db8478bb..e7f60eef 100644
--- a/index.bs
+++ b/index.bs
@@ -2849,9 +2849,9 @@ Types of Technical Reports</h3>
 		<dd>
 			[=Working Groups=] can also publish [=registries=]
 			in order to document collections of values or other data.
-			These are typically published in a separate [=registry report=],
-			although they can also be directly embedded in [=Recommendation Track=] documents
-			as a [=registry section=].
+			A registry can be published either as a distinct [=registry report=],
+			or directly within [=Recommendation Track=] a document
+			as an [=embedded registry=].
 			[=registry definition|Defining a registry=] requires [=wide review=] and [=consensus=],
 			but once set up, changes to registry entries are lightweight
 			and can even be done without a [=Working Group=].
@@ -4679,20 +4679,12 @@ Publishing Registries</h4>
 
 	[=Registries=] can be published either
 	as a stand-alone [=technical report=] on the [=Registry Track=] called a <dfn>registry report</dfn>,
-	or incorporated as part of a [=Recommendation=] as a <dfn>registry section</dfn>.
+	or incorporated as part of a [=Recommendation=] as an <dfn oldids="registry-section">embedded registry</dfn>.
 
-	A [=registry report=] or [=registry section=]
-	is purely documentational,
-	is not subject to the W3C Patent Policy,
-	and <em class=rfc2119>must not</em> contain any requirements on implementations.
-	For the purposes of the Patent Policy [[PATENT-POLICY]],
-	any [=registry section=] in a [=Recommendation track=] document
-	is not a normative portion of that specification.
-
-	The [=registry report=] or [=registry section=] <em class=rfc2119>must</em>:
+	The [=registry report=] or [=embedded registry=] <em class=rfc2119>must</em>:
 	<ul>
 		<li>
-			Clearly label the [=registry report=]/[=registry section|section=],
+			Clearly label the [=registry report=] or [=embedded registry=],
 			its [=registry tables|tables=],
 			and its [=registry definitions=] as such,
 			including a link to [[#registries]] in this Process.
@@ -4872,6 +4864,16 @@ Specifications that Reference Registries</h4>
 		(The Registry is nonetheless expected to contain </code>Basic-Method</code> as an entry.)
 	</div>
 
+<h4 id=reg-pat>
+Registries and Patents</h4>
+
+	A [=registry report=] or [=embedded registry=]
+	is not subject to the W3C Patent Policy,
+	and <em class=rfc2119>must not</em> define any requirements on implementations.
+	For the purposes of the Patent Policy [[PATENT-POLICY]] (only),
+	any [=embedded registry=] in a [=Recommendation track=] document
+	is not a normative portion of that specification.
+
 <h3 id="switching-tracks">
 Switching Tracks</h3>
 
@@ -5703,6 +5705,11 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 		<li>
 			Stop citing the superseded TAG charter.
 			(See <a href="https://github.com/w3c/w3process/issues/794">Issue 794</a>)
+
+		<li>
+			Rename “registry sections” to [=embedded registries=]
+			to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
+			(See <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
 	</ul>
 
 

From 590846729cf6510f2c7670f0e3ffb5d005db3d63 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Jan 2024 10:34:00 +0900
Subject: [PATCH 028/237] Fix accidental grammatical oddity

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index e7f60eef..6742564f 100644
--- a/index.bs
+++ b/index.bs
@@ -2850,7 +2850,7 @@ Types of Technical Reports</h3>
 			[=Working Groups=] can also publish [=registries=]
 			in order to document collections of values or other data.
 			A registry can be published either as a distinct [=registry report=],
-			or directly within [=Recommendation Track=] a document
+			or directly within a [=Recommendation Track=] document
 			as an [=embedded registry=].
 			[=registry definition|Defining a registry=] requires [=wide review=] and [=consensus=],
 			but once set up, changes to registry entries are lightweight

From 84977720eeec1ed5d968efc441074404f4b646c0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Jan 2024 11:24:29 +0900
Subject: [PATCH 029/237] Update change section

---
 index.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.bs b/index.bs
index 6742564f..0a398db7 100644
--- a/index.bs
+++ b/index.bs
@@ -5710,6 +5710,10 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 			Rename “registry sections” to [=embedded registries=]
 			to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
 			(See <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
+
+		<li>
+			Put constraints on the timing of making Formal Objections public.
+			(See <a href="https://github.com/w3c/w3process/issues/735">Issue 735</a>)
 	</ul>
 
 

From 70971f92c9888250f03b61f749ffb7fcf013ae7d Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 13 Mar 2024 23:12:07 +0900
Subject: [PATCH 030/237] Clarify what a registry is made of (#818)

The specs that use the registry are necessarily for a registry to be
useful, but they're not part of it.

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index 0a398db7..ce481350 100644
--- a/index.bs
+++ b/index.bs
@@ -4566,14 +4566,13 @@ Revising W3C Statements</h4>
 The Registry Track</h3>
 
 	A <dfn export>registry</dfn> documents a data set
-	consisting of one or more associated <dfn export lt="registry table">registry tables</dfn>,
+	consisting of one or more <dfn export lt="registry table">registry tables</dfn>,
 	each table representing an updatable collection
 	of logically independent, consistently-structured <dfn export lt="registry entry">registry entries</dfn>.
-	A registry has three associated components:
+	A registry consists of:
 	<ul>
 		<li>the [=registry definition=], defining how the [=registry tables=] are structured and maintained
 		<li>one or more [=registry tables=], holding the data set represented by the [=registry=] (the <dfn>registry data</dfn>)
-		<li>one or more referencing specifications, which make use of the [=registry=]
 	</ul>
 
 	The purposes of maintaining a [=registry=] can include:

From 020ae90bdd644108f9b596aee8b8b926462b1cdb Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 14 Mar 2024 17:39:13 +0900
Subject: [PATCH 031/237] Add anchor for convenient linking

---
 index.bs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/index.bs b/index.bs
index ce481350..9c1744c6 100644
--- a/index.bs
+++ b/index.bs
@@ -2539,6 +2539,7 @@ Council Deliberations</h5>
 	The deliberations of a [=W3C Council=] are confidential to that [=W3C Council=]
 	and its [=Council Team Contact=].
 
+	<p id=45-day-update>
 	If a [=W3C Council=] is unable to come to a conclusion within 45 days of being <a href="#council-convention">convened</a>,
 	the [=W3C Council Chair=] <em class=rfc2119>must</em> inform the [=AC=] of this delay
 	and of the status of the discussions.

From c92eacf3ee525ba7cf9f1375410f6f90b9590705 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 18 Mar 2024 23:57:12 +0900
Subject: [PATCH 032/237] Update the CEPC to its new Name (COC)

---
 index.bs | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/index.bs b/index.bs
index 9c1744c6..5db021ff 100644
--- a/index.bs
+++ b/index.bs
@@ -118,9 +118,9 @@ Relation of Process Document to Patent Policy and Other Policies</h2>
 	incorporated by normative reference as a part of the Process Document
 	are equally binding.
 
-	The Patent Policy and CEPC place additional obligations on Members, Team, and other participants in W3C.
+	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 CEPC have been designed to allow each to evolve independently.
+	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.
 
@@ -437,7 +437,7 @@ Expectations and Discipline</h5>
 	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/Consortium/cepc/">W3C Code of Ethics and Professional Conduct</a> [[!CEPC]]
+	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]].
@@ -448,7 +448,7 @@ Expectations and Discipline</h5>
 	if serious and/or repeated violations,
 	such as failure to meet the requirements on individual behavior of
 	(a) this process
-	and in particular the CEPC, or
+	and in particular the Code of Conduct, or
 	(b) the membership agreement, or
 	(c) applicable laws,
 	occur.
@@ -2408,7 +2408,7 @@ Council Participation, Dismissal, and Renunciation</h5>
 	The [=Team=] may report comments verbatim
 	or may paraphrase them while preserving their intent;
 	they may also elide inappropriate comments,
-	such as any that violate applicable laws or the [[CEPC]].
+	such as any that violate applicable laws or the [[COC]].
 
 	Before a Council forms,
 	the [=Team=] presents the entire list of potential members
@@ -5483,7 +5483,7 @@ Process Evolution</h2>
 	The documents covered by this section are:
 	* the W3C Process (this document)
 	* the W3C Patent Policy [[!PATENT-POLICY]]
-	* the W3C Code of Ethics and Professional Conduct [[!CEPC]]
+	* the W3C Code of Conduct [[!COC]]
 	* The W3C Document License [[!DOC-LICENSE]]
 
 	The [=Advisory Board=] initiates review as follows:
@@ -5508,7 +5508,7 @@ Process Evolution</h2>
 
 	Note: As of June 2020,
 	the [[PATENT-POLICY|Patent Policy]] is developed in the <a href="https://www.w3.org/2004/pp/psig/">Patents and Standards Interest Group</a>,
-	the [[CEPC|Code of Ethics and Professional Conduct]] in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
+	the [[COC|Code of Conduct]] in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
 	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.
 
 <h2 id="acks" class=non-normative>
@@ -5841,9 +5841,9 @@ Changes since earlier versions</h3>
 		"title": "The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators",
 		"publisher": "W3C"
 	},
-	"CEPC": {
-		"href": "https://www.w3.org/Consortium/cepc/",
-		"title": "W3C Code of Ethics and Professional Conduct",
+	"COC": {
+		"href": "https://www.w3.org/policies/code-of-conduct/",
+		"title": "W3C Code of Conduct",
 		"publisher": "W3C"
 	},
 	"OBS-RESC": {

From 45b10f03d6d916c50a0a3d5fc874c7b7cf43e275 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 22 Mar 2024 12:39:25 +0900
Subject: [PATCH 033/237] Update links

See #824
---
 index.bs | 58 ++++++++++++++++++++++++++++----------------------------
 1 file changed, 29 insertions(+), 29 deletions(-)

diff --git a/index.bs b/index.bs
index 5db021ff..2bdef76a 100644
--- a/index.bs
+++ b/index.bs
@@ -33,7 +33,7 @@ Previous Version: https://www.w3.org/2023/Process-20231103/
 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, http://yandex.com
+Former Editor: Charles McCathie Nevile, Yandex, https://yandex.com
 Former Editor: Ian Jacobs, W3C, https://www.w3.org/
 Level: none
 Repository: w3c/w3process
@@ -46,7 +46,7 @@ Abstract:
 	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/Consortium/">About W3C</a>.
+	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/2023/Process-20231103/">3 November 2023 Process</a>,
@@ -180,7 +180,7 @@ Introduction</h2>
 	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/agreements/">their own process document</a> [[BG-CG]].
+	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,
@@ -245,8 +245,8 @@ Members</h3>
 	</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>” [[JOIN]];
-	(refer to the public list of <a href="https://www.w3.org/Consortium/Member/List">current W3C Members</a> [[MEMBER-LIST]]).
+	as described in “<a href="https://www.w3.org/Consortium/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.
@@ -378,7 +378,7 @@ The W3C Team</h3>
 	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/Consortium/Recruitment/Fellows">W3C Fellows Program</a> [[FELLOWS]].
+	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),
@@ -452,7 +452,7 @@ Expectations and Discipline</h5>
 	(b) the membership agreement, or
 	(c) applicable laws,
 	occur.
-	Refer to the <a href="https://www.w3.org/Guide/process/banning.html">Guidelines to suspend or remove participants from groups</a>.
+	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>
@@ -745,7 +745,7 @@ Participation in the Advisory Committee</h4>
 	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. [[CURRENT-AC]])
 
 	When an organization joins W3C
-	(see “<a href="https://www.w3.org/Consortium/join">How to Join W3C</a>” [[JOIN]]),
+	(see “<a href="https://www.w3.org/Consortium/join/">How to Join W3C</a>” [[JOIN]]),
 	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement.
 	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,
@@ -833,7 +833,7 @@ Advisory Committee Meetings</h4>
 	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/Member/Meeting/">Advisory Committee meetings</a> [[AC-MEETING]]
+	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>
@@ -1606,7 +1606,7 @@ Invited Expert in a Working Group</h5>
 
 		<li>
 			agree to the terms of the
-			<a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">invited expert and collaborators agreement</a> [[!COLLABORATORS-AGREEMENT]],
+			<a href="https://www.w3.org/invited-experts/agreement-2023/">invited expert and collaborators agreement</a> [[!COLLABORATORS-AGREEMENT]],
 
 		<li>
 			accept the participation terms set forth in the charter,
@@ -2970,7 +2970,7 @@ Wide Review</h5>
 	the record of requests to and responses from reviewers,
 	especially <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> [[CHARTER]]
 	and groups identified as dependencies in the charter
-	or identified as <a href="https://www.w3.org/2001/11/StdLiaison.html">liaisons</a> [[LIAISON]],
+	or identified as <a href="https://www.w3.org/liaisons/">liaisons</a> [[LIAISON]],
 	and seek evidence of clear communication to the general public
 	about appropriate times and which content to review
 	and whether such reviews actually occurred.
@@ -4424,7 +4424,7 @@ Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</h5>
 	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 <em class="rfc2119">should</em> link
-	to the explanation of <a href="https://www.w3.org/2016/11/obsoleting-rescinding/">Obsoleting and Rescinding W3C Specifications</a> [[OBS-RESC]] as appropriate.
+	to the explanation of <a href="https://www.w3.org/Guide/process/obsolete-rescinded-supserseded">Obsoleting and Rescinding W3C Specifications</a> [[OBS-RESC]] as appropriate.
 
 	Once W3C has published a Rescinded Recommendation,
 	future W3C technical reports <em class="rfc2119">must not</em> include normative references
@@ -4902,7 +4902,7 @@ Switching Tracks</h3>
 <h3 id="further-reading">
 Further reading</h3>
 
-	Refer to <a href="https://www.w3.org/Guide/transitions">"How to Organize a Recommendation Track Transition"</a> [[TRANSITION]]
+	Refer to <a href="https://www.w3.org/Guide/transitions/">"How to Organize a Recommendation Track Transition"</a> [[TRANSITION]]
 	in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> [[GUIDE]]
 	for practical information about preparing for the reviews
 	and announcements of the various steps,
@@ -4930,7 +4930,7 @@ Public Communication</h3>
 			W3C technical reports (and software) are available free of charge to the general public.
 
 		<li>
-			A <a href="https://www.w3.org/Consortium/mission">mission statement</a> [[MISSION]]
+			A <a href="https://www.w3.org/mission/">mission statement</a> [[MISSION]]
 			that explains the purpose and mission of W3C,
 			the key benefits for Members,
 			and the organizational structure of W3C.
@@ -4951,7 +4951,7 @@ Public Communication</h3>
 	[=Workshops=],
 	and review deadlines,
 	the Team provides them with a regular (e.g., weekly) news service
-	and maintains a <a href="https://www.w3.org/participate/eventscal">calendar</a> [[CALENDAR]]
+	and maintains a <a href="https://www.w3.org/events/">calendar</a> [[CALENDAR]]
 	of official W3C events.
 	Members are encouraged to send schedule and event information to the Team for inclusion on this calendar.
 
@@ -5157,7 +5157,7 @@ Liaisons</h2>
 	unless directed to do so by the [=Board=].
 	A signed [=agreement=] <em class="rfc2119">should</em> be made public.
 
-	Information about <a href="https://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a> [[LIAISON]]
+	Information about <a href="https://www.w3.org/liaisons/">W3C liaisons with other organizations</a> [[LIAISON]]
 	and the guidelines W3C follows when creating a liaison is available on the Web.
 
 <h2 id="Submission">
@@ -5307,7 +5307,7 @@ Scope of Member Submissions</h4>
 	to build consensus around concrete proposals for new work.
 
 	Members <em class="rfc2119">should not</em> submit materials
-	covering topics well outside the scope of <a href="https://www.w3.org/Consortium/mission">W3C's mission</a> [[MISSION]].
+	covering topics well outside the scope of <a href="https://www.w3.org/mission/">W3C's mission</a> [[MISSION]].
 
 <h4 id="SubmissionReqs">
 Information Required in a Submission Request</h4>
@@ -5316,7 +5316,7 @@ Information Required in a Submission Request</h4>
 	and any other authors of the submitted material
 	<em class="rfc2119">must</em> agree that,
 	if the request is acknowledged,
-	the documents in the Member Submission will be subject to the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> [[!DOC-LICENSE]]
+	the documents in the Member Submission will be subject to the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> [[!DOC-LICENSE]]
 	and will include a reference to it.
 	The [=Submitter=](s) <em class="rfc2119">may</em> hold the copyright for the documents in a Member Submission.
 
@@ -5448,7 +5448,7 @@ Rejection of a Submission Request, and Submission Appeals</h3>
 		<li>
 			The ideas expressed in the request are poor,
 			might harm the Web,
-			or run counter to <a href="https://www.w3.org/Consortium/mission">W3C's mission</a> [[MISSION]].
+			or run counter to <a href="https://www.w3.org/mission/">W3C's mission</a> [[MISSION]].
 
 		<li>
 			The ideas expressed in the request lie well outside the scope of W3C's mission.
@@ -5727,7 +5727,7 @@ Changes since earlier versions</h3>
 <pre class=biblio>
 {
 	"JOIN": {
-		"href": "https://www.w3.org/Consortium/join",
+		"href": "https://www.w3.org/Consortium/join/",
 		"title": "How to Join W3C",
 		"publisher": "W3C"
 		},
@@ -5757,12 +5757,12 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"MISSION": {
-		"href": "https://www.w3.org/Consortium/mission",
+		"href": "https://www.w3.org/mission/",
 		"title": "The W3C Mission statement",
 		"publisher": "W3C"
 	},
 	"COLLABORATORS-AGREEMENT": {
-		"href": "https://www.w3.org/Consortium/Legal/collaborators-agreement",
+		"href": "https://www.w3.org/invited-experts/agreement-2023/",
 		"title": "Invited expert and collaborators agreement",
 		"publisher": "W3C"
 	},
@@ -5792,7 +5792,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"LIAISON": {
-		"href": "https://www.w3.org/2001/11/StdLiaison",
+		"href": "https://www.w3.org/liaisons/",
 		"title": "W3C liaisons with other organizations",
 		"publisher": "W3C"
 	},
@@ -5807,7 +5807,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"FELLOWS": {
-		"href": "https://www.w3.org/Consortium/Recruitment/Fellows",
+		"href": "https://www.w3.org/careers/fellows/",
 		"title": "W3C Fellows Program",
 		"publisher": "W3C"
 	},
@@ -5832,7 +5832,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"CALENDAR": {
-		"href": "https://www.w3.org/participate/eventscal",
+		"href": "https://www.w3.org/events/",
 		"title": "Calendar of all scheduled official W3C events",
 		"publisher": "W3C"
 	},
@@ -5847,7 +5847,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"OBS-RESC": {
-		"href": "https://www.w3.org/2016/11/obsoleting-rescinding/",
+		"href": "https://www.w3.org/Guide/process/obsolete-rescinded-supserseded",
 		"title": "Obsoleting and Rescinding W3C Specifications",
 		"publisher": "W3C"
 	},
@@ -5872,7 +5872,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"AC-MEETING": {
-		"href": "https://www.w3.org/Member/Meeting/",
+		"href": "https://www.w3.org/event/ac/",
 		"title": "Advisory Committee meetings (Member-only access)",
 		"publisher": "W3C"
 	},
@@ -5908,7 +5908,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"TRANSITION": {
-		"href": "https://www.w3.org/Guide/transitions",
+		"href": "https://www.w3.org/Guide/transitions/",
 		"title": "Organize a Technical Report Transition",
 		"publisher": "W3C"
 	},
@@ -5922,7 +5922,7 @@ Changes since earlier versions</h3>
 		"title": "Amended and Restated Bylaws of World Wide Web Consortium, Inc."
 	},
 	"W3C-IPR": {
-		"href": "https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231",
+		"href": "https://www.w3.org/policies/",
 		"title": "W3C IPR Policies"
 	},
 	"COUNCIL-REPORT-INDEX": {

From 2aaddbb554c9f51a72ac2234e714a4d035347842 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 22 Mar 2024 12:45:45 +0900
Subject: [PATCH 034/237] Fix typos in links

Part of #824
---
 index.bs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 2bdef76a..dd7a2a8e 100644
--- a/index.bs
+++ b/index.bs
@@ -245,7 +245,7 @@ Members</h3>
 	</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>” [[JOIN]];
+	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>
@@ -745,7 +745,7 @@ Participation in the Advisory Committee</h4>
 	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. [[CURRENT-AC]])
 
 	When an organization joins W3C
-	(see “<a href="https://www.w3.org/Consortium/join/">How to Join W3C</a>” [[JOIN]]),
+	(see “<a href="https://www.w3.org/membership/join/">How to Join W3C</a>” [[JOIN]]),
 	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement.
 	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,
@@ -5727,7 +5727,7 @@ Changes since earlier versions</h3>
 <pre class=biblio>
 {
 	"JOIN": {
-		"href": "https://www.w3.org/Consortium/join/",
+		"href": "https://www.w3.org/membership/join/",
 		"title": "How to Join W3C",
 		"publisher": "W3C"
 		},
@@ -5872,7 +5872,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"AC-MEETING": {
-		"href": "https://www.w3.org/event/ac/",
+		"href": "https://www.w3.org/events/ac/",
 		"title": "Advisory Committee meetings (Member-only access)",
 		"publisher": "W3C"
 	},

From 6ebd14690beef62870eaaf14dbdc397c5b65ec5c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 22 Mar 2024 12:48:13 +0900
Subject: [PATCH 035/237] Update links

Part of #824
---
 index.bs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index dd7a2a8e..1ccaa652 100644
--- a/index.bs
+++ b/index.bs
@@ -5346,7 +5346,7 @@ Information Required in a Submission Request</h4>
 			[=Submitters=] <em class="rfc2119">may</em> hold the copyright for the material contained in these documents,
 			but when made available by W3C,
 			these documents <em class="rfc2119">must</em> be subject to the provisions
-			of the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> [[!DOC-LICENSE]].
+			of the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> [[!DOC-LICENSE]].
 	</ul>
 
 	The request <em class="rfc2119">must</em> also answer the following questions.
@@ -5442,7 +5442,7 @@ Rejection of a Submission Request, and Submission Appeals</h3>
 			The IPR statement made by the [=Submitter=](s) is inconsistent with W3C's
 			Patent Policy [[!PATENT-POLICY]]
 			and in particular the “Licensing Commitments in W3C Submissions”,
-			<a href="https://www.w3.org/Consortium/Legal/copyright-documents">Document License</a> [[!DOC-LICENSE]],
+			<a href="https://www.w3.org/copyright/document-license-2023/">Document License</a> [[!DOC-LICENSE]],
 			or other IPR policies.
 
 		<li>
@@ -5737,7 +5737,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"MEMBER-LIST": {
-		"href": "https://www.w3.org/Consortium/Member/List",
+		"href": "https://www.w3.org/Consortium/membership/list/",
 		"title": "The list of current W3C Members",
 		"publisher": "W3C"
 	},
@@ -5767,7 +5767,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"DOC-LICENSE": {
-		"href": "https://www.w3.org/Consortium/Legal/copyright-documents",
+		"href": "https://www.w3.org/copyright/document-license-2023/",
 		"title": "W3C Document License",
 		"publisher": "W3C"
 	},

From 77ccd122e9c75db620a3236f4fd05ddfb0f3d18a Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 22 Mar 2024 12:53:18 +0900
Subject: [PATCH 036/237] Fix typos in links

Part of #824
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 1ccaa652..327d22cd 100644
--- a/index.bs
+++ b/index.bs
@@ -5737,7 +5737,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"MEMBER-LIST": {
-		"href": "https://www.w3.org/Consortium/membership/list/",
+		"href": "https://www.w3.org/membership/list/",
 		"title": "The list of current W3C Members",
 		"publisher": "W3C"
 	},

From 59df8e6fb7e4bfd8033a404fe7f79a3956ebbf06 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 28 Mar 2024 00:04:26 +0900
Subject: [PATCH 037/237] Clarify definition of the REC-track document

This makes it clear that a document that uses the various publication
types and transitions of the REC-track is indeed a REC-track document, even
if it isn't planning to go all the way to the end.

Some groups for instance have a declared intention of only going as far
as CR. That doesn't make the documents on the "CR track", as there's no
such thing.

See https://github.com/w3c/strategy/issues/438#issuecomment-1997685426
---
 index.bs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/index.bs b/index.bs
index 327d22cd..3cd5ae5b 100644
--- a/index.bs
+++ b/index.bs
@@ -3196,6 +3196,9 @@ The W3C Recommendation Track</h3>
 		<li>Publication as a [=W3C Recommendation=].
 	</ol>
 
+	A <dfn lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document">W3C Recommendation Track document</dfn>
+	is any document whose current status is one of the five in the numbered list above.
+
 	<div role="region" aria-label="Basic W3C Recommendation Track">
 		<pre class=include-raw>
 			path: basic-rec-track.svg

From 4a4d433ba42d7a5dc58f2813fb933fe7113eb593 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 28 Mar 2024 00:07:12 +0900
Subject: [PATCH 038/237] Clarify confidentiality requirements (#835)

This is an attempt to clarify the confidentiality requirements by
separating concerns.

* the second bullet in the list is about using reasonable effort. It's
  not specifically the different levels of confidentiality, nor about any
  particular action that must be taken. It's only about defining the
  standard of care that is applicable to maintaining confidentiality.
* The third bullet is specifically about "must not disclose".

But the phrasing of the second bullet could be read as if there was some
particular task or activity ("effort") to be performed when dealing with
different levels, suggesting that maybe changing levels was OK, as long
as you do it the right way (maybe by redacting something).

This rephrasing clarifies that "reasonable effort" is a general
requirement about confidentiality, and that disclosing beyond the proper
level is not appropriate.
---
 index.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 3cd5ae5b..ff6a77a9 100644
--- a/index.bs
+++ b/index.bs
@@ -4989,10 +4989,11 @@ Confidentiality Levels</h3>
 			<em class="rfc2119">must</em> treat the information as confidential within W3C,
 
 		<li>
-			<em class="rfc2119">must</em> use reasonable efforts to maintain the proper level of confidentiality, and
+			<em class="rfc2119">must</em> use reasonable efforts to preserve that confidentiality, and
 
 		<li>
-			<em class="rfc2119">must not</em> release this information to the general public or press.
+			<em class="rfc2119">must not</em> release this information to the general public or press,
+			nor beyond the proper level of access.
 	</ul>
 
 	The [=Team=] <em class="rfc2119">must</em> provide mechanisms

From 76ab28c830e7f7c1857f03957ac712ea98489b49 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 1 Apr 2024 10:24:20 +0900
Subject: [PATCH 039/237] Eliminate potential ambiguity in AB chair
 ratification

See this resolves part 1 of https://github.com/w3c/w3process/issues/838
---
 index.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index ff6a77a9..f6ff596e 100644
--- a/index.bs
+++ b/index.bs
@@ -885,8 +885,9 @@ Composition of the Advisory Board</h5>
 	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.
-	The Chair(s) are subject to ratification by secret ballot
-	by two thirds of the AB upon appointment.
+	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;

From 30b55e7a42f974f7c70bb6c47668cba6ff14c70f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 1 Apr 2024 11:20:59 +0900
Subject: [PATCH 040/237] Update changes section

---
 index.bs | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index f6ff596e..2f07efe3 100644
--- a/index.bs
+++ b/index.bs
@@ -5682,12 +5682,6 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 	a <a href="https://github.com/w3c/w3process/compare/p2023_1...main">detailed log of all changes since then</a>
 	are available.
 
-	<!--
-	In addition to a number of editorial adjustments
-	and minor tweaks,
-	the following is a summary of the main differences:
-	-->
-
 	In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:
 
 	<ul>
@@ -5719,6 +5713,14 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 		<li>
 			Put constraints on the timing of making Formal Objections public.
 			(See <a href="https://github.com/w3c/w3process/issues/735">Issue 735</a>)
+
+		<li>
+			Clarify the defition of a Registry (see <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
+			and of Recommendation Track Documents (see <a href="https://github.com/w3c/w3process/pull/831">Pull Request 831</a>).
+
+		<li>
+			Clarify how the outcome of certain ballots are determined.
+			(See <a href="https://github.com/w3c/w3process/issues/838">Issue 838</a>)
 	</ul>
 
 

From bb1c8c1f40b9d9e78d759757d6cb8efd8a45cdac Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 15 Apr 2024 12:14:56 +0900
Subject: [PATCH 041/237] Export term

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 2f07efe3..479090ff 100644
--- a/index.bs
+++ b/index.bs
@@ -3197,7 +3197,7 @@ The W3C Recommendation Track</h3>
 		<li>Publication as a [=W3C Recommendation=].
 	</ol>
 
-	A <dfn lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document">W3C Recommendation Track document</dfn>
+	A <dfn export lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document">W3C Recommendation Track document</dfn>
 	is any document whose current status is one of the five in the numbered list above.
 
 	<div role="region" aria-label="Basic W3C Recommendation Track">

From 6713d68bac5bdfc5708e2e7eb359704febe63fae Mon Sep 17 00:00:00 2001
From: Jeffrey Yasskin <jyasskin@google.com>
Date: Wed, 24 Apr 2024 10:40:47 -0700
Subject: [PATCH 042/237] Link "Advisory Committee Review" in the Statement
 section. (#858)

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 479090ff..6def12cc 100644
--- a/index.bs
+++ b/index.bs
@@ -4534,7 +4534,7 @@ Elevating Group Notes to W3C Statement status</h4>
 
 	Once these conditions are fulfilled,
 	the [=Team=] <em class=rfc2119>must</em> then
-	begin an Advisory Committee Review on the question of
+	begin an [=Advisory Committee Review=] on the question of
 	whether the document is appropriate to publish as a [=W3C Statement=].
 	During this review period,
 	the [=Note=] <em class=rfc2119>must not</em> be updated.

From 2f6684b57711f6090dd12b649dd0d96e6f60a9d3 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 02:42:26 +0900
Subject: [PATCH 043/237] Improve consistency of document status names that use
 the word "Draft" (#819)

See #779
---
 index.bs | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

diff --git a/index.bs b/index.bs
index 6def12cc..b7c2bc93 100644
--- a/index.bs
+++ b/index.bs
@@ -4466,26 +4466,26 @@ Group Notes</h4>
 			non-normative guides to good practices
 	</ul>
 
-	Some [=Notes=] are developed through successive <dfn lt="Draft Note">Draft Notes</dfn>
+	Some [=Notes=] are developed through successive <dfn oldids="draft-note" lt="Note Draft">Note Drafts</dfn>
 	before publication as a full [=Notes=],
 	while others are [=published=] directly as a [=Note=].
-	There are few formal requirements to [=publish=] a document as a [=Note=] or [=Draft Note=],
+	There are few formal requirements to [=publish=] a document as a [=Note=] or [=Note Draft=],
 	and they have no standing as a recommendation of W3C
 	but are simply documents preserved for historical reference.
 
 	Note: The W3C Patent Policy [[PATENT-POLICY]]
-	does not apply any licensing requirements or commitments for [=Notes=] or [=Draft Notes=].
+	does not apply any licensing requirements or commitments for [=Notes=] or [=Note Drafts=].
 
 <h4 id="publishing-notes">
 Publishing Notes</h4>
 
-	In order to publish a [=Note=] or [=Draft Note=],
+	In order to publish a [=Note=] or [=Note Draft=],
 	the group:
 
 	<ul>
 		<li>
 			<em class="rfc2119">must</em> record their decision
-			to request publication as a [=Note=] or [=Draft Note=], and
+			to request publication as a [=Note=] or [=Note Draft=], and
 
 		<li>
 			<em class="rfc2119">should</em> publish documentation
@@ -4493,8 +4493,8 @@ Publishing Notes</h4>
 			since any previous publication.
 	</ul>
 
-	Both [=Notes=] and [=Draft Notes=] can be updated by republishing
-	as a [=Note=] or [=Draft Note=].
+	Both [=Notes=] and [=Note Drafts=] can be updated by republishing
+	as a [=Note=] or [=Note Draft=].
 	A [=technical report=] <em class="rfc2119">may</em> remain
 	a [=Note=] indefinitely.
 
@@ -4749,7 +4749,7 @@ Publishing Registries</h4>
 			nor to [=Rescinded Candidate Recommendation=] for [=Registries=].
 
 		<li>
-			The equivalent of [=Working Draft=] is called <dfn export>Draft Registry</dfn>.
+			The equivalent of [=Working Draft=] is called <dfn oldids="draft-registry" export>Registry Draft</dfn>.
 
 		<li>
 			The equivalent of [=Candidate Recommendation=] is called <dfn export>Candidate Registry</dfn>,
@@ -5714,6 +5714,14 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 			Put constraints on the timing of making Formal Objections public.
 			(See <a href="https://github.com/w3c/w3process/issues/735">Issue 735</a>)
 
+		<li>
+
+			Rename "Draft Note" into "Note Draft",
+			and "Draft Registry" into "Registry Draft"
+			to be consistent with other statuses that uses the word "Draft",
+			and to make that word stand out more.
+			(See <a href="https://github.com/w3c/w3process/issues/779">Issue 779</a>)
+
 		<li>
 			Clarify the defition of a Registry (see <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
 			and of Recommendation Track Documents (see <a href="https://github.com/w3c/w3process/pull/831">Pull Request 831</a>).

From e52fac87e38288e9f191b7a796ed0c1804d7e61f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 02:44:40 +0900
Subject: [PATCH 044/237] Editorial rewrite of section on charter approval
 (#850)

The original text was messy and hard to follow, as well as hard to build
upon. This commit does not make any substantive change, but improves the
readability of this section.

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 57 +++++++++++++++++++++++++++++++-------------------------
 1 file changed, 32 insertions(+), 25 deletions(-)

diff --git a/index.bs b/index.bs
index b7c2bc93..53a8b169 100644
--- a/index.bs
+++ b/index.bs
@@ -1861,39 +1861,46 @@ Content of a Charter</h3>
 	who represent the same Member organization or group of <a href="#MemberRelated">related Members</a>).
 
 <h3 id="CharterReview">
-Advisory Committee Review of a Charter</h3>
+Charter Review and Approval</h3>
 
-	The [=Team=] <em class="rfc2119">must</em> solicit <a href="#ACReview">Advisory Committee review</a>
-	of every new or substantively modified Working Group or Interest Group charter,
-	except for either:
-	* a charter extension
-	* substantive changes to a charter that do not affect the way the group functions in any significant way.
+<h4 id="charter-major-changes">
+New Charters and Major Changes</h4>
 
-	The review period <em class="rfc2119">must</em> be at least 28 days.
-	The following are examples of substantive changes that would not require an [=Advisory Committee Review=]:
-	the addition of an in-scope deliverable,
-	a change of [=Team Contact=],
-	or a change of [=Chair=].
-	Such changes must nonetheless be announced
-	to the [=Advisory Committee=]
-	and to <a href="#wgparticipant"> participants in the Working</a> or <a href="#igparticipant">in the Interest Group</a>,
-	and a rationale must be provided.
+	Any new [=charter=] (including re-chartering of existing [=chartered groups=])
+	and most substantive changes to an already-approved [=charter=]
+	of a [=Working Group=] or [=Interest Group=]
+	<em class=rfc2119>must</em> be approved by a [=W3C Decision=] following an [=AC Review=] of that [=charter=].
+	(See [[#charter-minor-changes]] for minor changes that can be approved by a [=Team Decision=].)
+
+	The review period <em class=rfc2119>must</em> be at least 28 days.
+	Any [=Advisory Committee representative=] <em class=rfc2119>may</em> request an extended review period
+	in response to the Call for Review;
+	upon receipt of any such request,
+	the [=Team=] <em class=rfc2119>must</em> extend the review period
+	to at least 60 days.
 
 	The Call for Review of a substantively modified charter
-	<em class="rfc2119">must</em> highlight important changes
+	<em class=rfc2119>must</em> highlight important changes
 	(e.g., regarding deliverables or resource allocation)
 	and include rationale for the changes.
 
-	As part of the Advisory Committee review of any new or substantively modified Working Group charter,
-	any Advisory Committee representative <em class="rfc2119">may</em> request an extended review period.
+<h4 id="charter-minor-changes">
+Minor Changes to Active Charters</h4>
 
-	Such a request must be submitted with a Member's comments
-	in response to the Call for Review.
-	Upon receipt of any such request,
-	the [=Team=] <em class="rfc2119">must</em> ensure
-	that the Call for Participation for the Working Group
-	occurs at least 60 days
-	after the Call for Review of the charter.
+	Substantive changes to a [=charter=] (including [[#charter-extension|extensions]])
+	that do not affect the way the group functions in any significant way
+	<em class=rfc2119>may</em> be approved by a [=Team Decision=],
+	in which case they do not require an [=Advisory Committee Review=].
+	The following are examples of such changes:
+	the addition of an in-scope deliverable,
+	a change of [=Team Contact=],
+	or a change of [=Chair=].
+
+	Though [=Advisory Committee Review=] is not required,
+	such changes <em class=rfc2119>must</em> still be announced
+	to the [=Advisory Committee=],
+	and to participants in the <a href="#wgparticipant">Working</a> or <a href="#igparticipant">Interest</a> Group,
+	and a rationale must be provided.
 
 <h3 id="cfp">
 Call for Participation in a Chartered Group</h3>

From 8dc76d5242fe0272801fbf341f30cf8365fbac23 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 13:05:56 +0900
Subject: [PATCH 045/237] Retire the Streamlined Publication Approval system
 (#857)

See #856
---
 index.bs | 87 ++------------------------------------------------------
 1 file changed, 2 insertions(+), 85 deletions(-)

diff --git a/index.bs b/index.bs
index 53a8b169..163ef14e 100644
--- a/index.bs
+++ b/index.bs
@@ -3570,8 +3570,7 @@ Updating Mature Publications on the Recommendation Track</h4>
 			<em class="rfc2119">must</em> show that the changes have received [=wide review=].
 
 		<li>
-			<em class="rfc2119">must </em> obtain [=Team=] verification,
-			or fulfill the criteria for [[#streamlined-update]].
+			<em class="rfc2119">must </em> obtain [=Team=] verification.
 			[=Team=] verification (a [=Team decision=]):
 			* <em class=rfc2119>should</em> be withheld
 				if any Process requirements are not met,
@@ -3634,88 +3633,6 @@ Updating Mature Publications on the Recommendation Track</h4>
 	of the revised specification
 	to other W3C groups and the Public.
 
-
-<h5 id="streamlined-update">
-Streamlined Publication Approval</h5>
-
-	Note: These criteria are intentionally stricter than
-	the general requirements for an [=update request=].
-	This is in order to minimize ambiguities and the need for expert judgment,
-	and to make self-evaluation practical.
-
-	In order to streamline the publication process in non-controversial cases,
-	verification of an [=update request=] is automatically granted without formal review
-	when the following <em>additional</em> criteria are fulfilled:
-
-	<ul>
-		<li>
-			There <em class=rfc2119>must</em> have been no changes to [=Working Group=] requirements about this document.
-
-		<li>
-			For each of the
-			<a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> [[CHARTER]],
-			if the Horizontal Review Group has made available a set criteria
-			under which their review is not necessary,
-			the [=Working Group=] <em class=rfc2119>must</em> document that these criteria have been fulfilled.
-			Otherwise, the [=Working Group=] <em class=rfc2119>must</em> show
-			that review from that group has been solicited and received.
-
-		<li>
-			No [=Formal Objection=] has been registered against the document.
-
-		<li>
-			The [=Working Group=] <em class=rfc2119>must</em>
-			have [=formally addressed=]:
-			* all issues raised against the document that resulted in changes since the previous publication
-			* all issues raised against changes since the previous publication
-			* all issues raised against the document that were closed since the previous publication with no change to the document
-
-			The response to each of these issues <em class=rfc2119>must</em> be to the satisfaction
-			of the person who raised it:
-			their proposal has been accepted,
-			or a compromise has been found,
-			or they accepted the Working Group's rationale for rejecting it.
-
-			Note: This is stricter than the general Transition Request criteria.
-	</ul>
-
-	Additionally, for updates to [=Recommendations=]
-	with <a href="#revised-rec-substantive">substantive changes</a>
-	or <a href="#revised-rec-features">with new features</a>:
-
-	<ul>
-
-		<li>
-			Changes to the document are limited to
-			[=proposed corrections=] that were included in a [=Last Call for Review of Proposed Corrections=]
-			possibly combined with <a href=#correction-classes>class 1 or 2 changes</a>,
-			and/or (in the case of a [=Recommendation=] that [=allow new feature|allows new features=])
-			[=proposed additions=] that were included in a [=Last Call for Review of Proposed Additions=].
-
-		<li>
-			The [=Working Group=] <em class=rfc2119>must</em> show
-			that all changes have been implemented in at least 2 distinct products by 2 different implementers,
-			as evidenced by passing tests of a test suite
-			providing extensive coverage of the changes,
-			or an alternative streamlined verification implementation requirement
-			described in the [=working Group=] charter has been met.
-
-			Note: This is stricter than the general criteria for [=adequate implementation experience=].
-	</ul>
-
-	The [=Working Group=] must provide written evidence for these claims,
-	and the [=Team=] must make these answers publicly and permanently available.
-
-	After publication,
-	if an AC Representative
-	or Team member
-	doubts that the evidence presented supports the claims,
-	they <em class=rfc2119>may</em> request that a formal review meeting be convened post facto.
-	If that review finds that the requirements were not fulfilled,
-	the Team <em class=rfc2119>may</em> revert the changes
-	by updating in place the status section to indicate that it has been reverted,
-	and by republishing the previously approved version of the technical report.
-
 <h4 id="first-wd">
 Publishing a First Public Working Draft</h4>
 
@@ -4192,7 +4109,7 @@ Incorporating Candidate Amendments</h5>
 		<li>
 			Identify the specific [=candidate amendments=] under review
 			as <dfn>proposed amendments</dfn>
-			(<dfn>proposed corrections</dfn>/<dfn oldids="proposed-addition">proposed additions</dfn>).
+			(<dfn export>proposed corrections</dfn>/<dfn oldids="proposed-addition" export>proposed additions</dfn>).
 
 		<li>
 			Specify the deadline for review comments,

From 41970399d98beb0a5b1b5aac7b505e05fbd7cc2c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 13:05:14 +0900
Subject: [PATCH 046/237] Update changelog

---
 index.bs | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/index.bs b/index.bs
index 163ef14e..87d8c850 100644
--- a/index.bs
+++ b/index.bs
@@ -5653,6 +5653,21 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 		<li>
 			Clarify how the outcome of certain ballots are determined.
 			(See <a href="https://github.com/w3c/w3process/issues/838">Issue 838</a>)
+
+		<li>
+			Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.
+			This change, while moderate in size, is purely editorial.
+			(See <a href="https://github.com/w3c/w3process/pull/850">Pull Request 850</a>)
+
+		<li oldids="streamlined-update">
+			Retire “<a href="https://www.w3.org/2023/Process-20231103/#streamlined-update">Streamlined Publication Approval</a>”.
+			This was meant to enable REC track publication with fewer/faster approval steps
+			when some stricter than usual criteria were fulfilled.
+			However, regular REC track publication have improved enough
+			that this became unnecessary,
+			and nobody was using it.
+			(See <a href="https://github.com/w3c/w3process/issues/856">Issue 856</a>)
+
 	</ul>
 
 

From 7c2b0079cbbc899f1c57a6b1dc83190526ab0cd7 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 13:17:47 +0900
Subject: [PATCH 047/237] Clarifies Council votes (#842)

This clarifies whether we count a majority of the ballots or of the
potential voters, and how to process abstentions.

Resolves part 4 of https://github.com/w3c/w3process/issues/838
---
 index.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 87d8c850..9aeef4bb 100644
--- a/index.bs
+++ b/index.bs
@@ -2527,8 +2527,9 @@ Council Deliberations</h5>
 	a [=W3C Council=] is unable to reach consensus,
 	the [=W3C Council Chair=] may instead resort to voting.
 	In that case,
-	the decision is made by simple majority,
-	with the [=W3C Council Chair=] breaking any tie.
+	the decision is adopted if there are more ballots for than against;
+	in case of a tie,
+	the [=W3C Council Chair=] determines the outcome.
 	However,
 	if the decision or proposal being objected to
 	originated with the TAG or AB,

From f8313a424b4a4227631031705efe6843b204bab2 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 13:18:04 +0900
Subject: [PATCH 048/237] Eliminate potential ambiguity in dismissal (#841)

This resolves part 3 of https://github.com/w3c/w3process/issues/838
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 9aeef4bb..c650801d 100644
--- a/index.bs
+++ b/index.bs
@@ -2427,7 +2427,7 @@ Council Participation, Dismissal, and Renunciation</h5>
 	would compromise the integrity of the Council decision,
 	and vote whether to dismiss that potential member.
 	No one is allowed to vote on their own dismissal;
-	each dismissal is decided by simple majority of those not abstaining.
+	each dismissal is enacted if there are at least as many ballots for as against.
 
 	Note: Since dismissal is individual,
 	when the decision being objected to was made by the [=TAG=] or [=AB=] acting as a body,

From 480ef014be81131ae279550d06d7bcae18e00320 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 13:22:24 +0900
Subject: [PATCH 049/237] Markup fix

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index c650801d..38ae2fae 100644
--- a/index.bs
+++ b/index.bs
@@ -5660,7 +5660,7 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 			This change, while moderate in size, is purely editorial.
 			(See <a href="https://github.com/w3c/w3process/pull/850">Pull Request 850</a>)
 
-		<li oldids="streamlined-update">
+		<li id="streamlined-update">
 			Retire “<a href="https://www.w3.org/2023/Process-20231103/#streamlined-update">Streamlined Publication Approval</a>”.
 			This was meant to enable REC track publication with fewer/faster approval steps
 			when some stricter than usual criteria were fulfilled.

From 3ffd35a649f4149a9d3dc0defb9f55bfd8f76bc0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 13:27:23 +0900
Subject: [PATCH 050/237] Disambiguate what "each" means in TAG appointment
 ratification (#837)

Co-authored-by: Martin Thomson <mt@lowentropy.net>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 38ae2fae..1be3eb10 100644
--- a/index.bs
+++ b/index.bs
@@ -1254,7 +1254,7 @@ Technical Architecture Group Appointments</h5>
 	The [=Team=]'s choice of appointee(s)
 	is subject to ratification by secret ballot
 	by both the [=AB=] and the [=TAG=],
-	each requiring a two-thirds approval.
+	requiring a two-thirds approval from each.
 	In the case of regularly scheduled elections,
 	the [=TAG=] participants in this ratification are
 	its members for the upcoming term.

From ad90a5e9db1280fc94b06e973e2a0e8c37bc86b9 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 25 Apr 2024 13:28:59 +0900
Subject: [PATCH 051/237] Update changelog

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 1be3eb10..0b8217df 100644
--- a/index.bs
+++ b/index.bs
@@ -5653,7 +5653,7 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 
 		<li>
 			Clarify how the outcome of certain ballots are determined.
-			(See <a href="https://github.com/w3c/w3process/issues/838">Issue 838</a>)
+			(See <a href="https://github.com/w3c/w3process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/w3process/pull/838">Issue 838</a>)
 
 		<li>
 			Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.

From 22fd24ceb2d632c0a5e1163a961279760bd3962f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 1 May 2024 12:22:31 +0900
Subject: [PATCH 052/237] Fix SVG diagram overflow with certain fonts

---
 retiring-rec.svg | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/retiring-rec.svg b/retiring-rec.svg
index 7f79fdd9..a3ebc419 100644
--- a/retiring-rec.svg
+++ b/retiring-rec.svg
@@ -46,21 +46,21 @@
 
 						<g role="listitem"><!-- Superseded -->
 							<g role="img">
-								<path d="M40,71v29s0,5 5,5h153" stroke="black" fill="none"/>
-								<polygon points="199,105 195,102 195,108"/>
+								<path d="M40,71v29s0,5 5,5h140" stroke="black" fill="none"/>
+								<polygon points="189,105 185,102 185,108"/>
 								<text x="115" y="102" text-anchor="middle" font-size="8">Replaced by a new version, AC review</text>
-								<rect role="img" id="superseded" rx="3" y="100" x="200" height="30" width="80" stroke="#600" fill="#fff" stroke-width="2">
+								<rect role="img" id="superseded" rx="3" y="100" x="190" height="30" width="90" stroke="#600" fill="#fff" stroke-width="2">
 									<title>Superseded Recommendation</title>
 								</rect>
-								<text aria-hidden="true" font-size="16" y="119" x="240" text-anchor="middle" stroke-width=".3">Superseded</text>
+								<text aria-hidden="true" font-size="16" y="119" x="235" text-anchor="middle" stroke-width=".3">Superseded</text>
 							</g>
 							<g role="list">
 								<g role="listitem"><!-- Whoops! Not superseded! -->
 									<g role="img">
 										<title>A Superseded Recommendation can become a normal Recommendation with AC review</title>
-										<path d="M199,125h-164s-5,0 -5,-5v-52" stroke-dasharray="1 4" fill="none" stroke="black"/>
+										<path d="M189,125h-154s-5,0 -5,-5v-52" stroke-dasharray="1 4" fill="none" stroke="black"/>
 										<polygon points="30,70 27,74 33,74"/>
-										<text aria-hidden="true" x="115" y="122" text-anchor="middle" font-size="8">Oops! The Web still needs this, AC review</text>
+										<text aria-hidden="true" x="110" y="122" text-anchor="middle" font-size="8">Oops! The Web still needs this, AC review</text>
 									</g>
 								</g>
 							</g>

From 519a9b025d8f07b80f1262743235485b6df6955e Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 1 May 2024 12:23:18 +0900
Subject: [PATCH 053/237] Fix SVG diagram hovering

---
 index.bs | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 0b8217df..67478ddf 100644
--- a/index.bs
+++ b/index.bs
@@ -75,13 +75,15 @@ table { margin-left: auto; margin-right: auto }
 
 :focus path,
 :focus polygon,
+:focus rect,
 :focus ellipse {
-	stroke-width: 4px;
+	stroke-width: 3px;
 }
 g g:hover path,
 g g:hover polygon,
+g g:hover rect,
 g g:hover ellipse {
-	stroke-width: 4px;
+	stroke-width: 3px;
 }
 :focus text,
 g g:hover text {

From adcfb707ff764e13a2f7a727d27739bc62f53b6f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 1 May 2024 11:59:14 +0900
Subject: [PATCH 054/237] Fix bug in diagram

---
 basic-rec-track.svg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/basic-rec-track.svg b/basic-rec-track.svg
index a8936059..3d8d04d3 100644
--- a/basic-rec-track.svg
+++ b/basic-rec-track.svg
@@ -56,7 +56,7 @@
 				</g>
 			<!-- CRS -->
 				<g role="listitem">
-					<a href="#pr-1">
+					<a href="#cr-1">
 						<ellipse role="img" id="cr-1" ry="18" rx="38" cy="140" cx="260" stroke="black" fill="#fff">
 						<title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
 						</ellipse>

From 73e4446b0cf2d082e15214ec8bb4e893354400e1 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 1 May 2024 12:04:31 +0900
Subject: [PATCH 055/237] Improve label/arrow alignment

---
 basic-rec-track.svg | 39 +++++++++++++++++++--------------------
 1 file changed, 19 insertions(+), 20 deletions(-)

diff --git a/basic-rec-track.svg b/basic-rec-track.svg
index 3d8d04d3..5ef03557 100644
--- a/basic-rec-track.svg
+++ b/basic-rec-track.svg
@@ -1,4 +1,4 @@
-		<svg xmlns="http://www.w3.org/2000/svg" viewBox="-5 40 630 180" width="100%">
+		<svg xmlns="http://www.w3.org/2000/svg" viewBox="-5 30 630 180" width="100%">
 			<title>Basic W3C Recommendation Track</title>
 			<!-- basic maturity states -->
 			<g role="list">
@@ -33,8 +33,8 @@
 								<g role="img">
 									<title>Publish a new Working Draft</title>
 								</g>
-								<text font-size="8">
-									<tspan x="70" y="100">WG Decision</tspan>
+								<text font-size="8" text-anchor="middle">
+									<tspan x="97" y="100">WG Decision</tspan>
 								</text>
 								<path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114" fill="none" stroke="black" stroke-dasharray="6 2"></path>
 								<polygon points="120,114 116,124 114,113"></polygon>
@@ -46,8 +46,8 @@
 								<g role="img">
 									<title>Advance to Candidate Recommendation</title>
 								</g>
-								<text x="138" y="126" font-size="8">WG Decision +</text>
-								<text x="138" y="134" font-size="8">Team Approval</text>
+								<text x="135" y="129" font-size="8">WG Decision +</text>
+								<text x="135" y="137" font-size="8">Team Approval</text>
 								<path stroke="#060" d="M135,140h81"></path>
 								<polygon points="211,136 221,140 211,144"></polygon>
 							</a>
@@ -77,8 +77,8 @@
 								<g role="img">
 									<title>Publish revised Candidate Recommendation Draft</title>
 								</g>
-								<text font-size="8">
-									<tspan x="182" y="110">WG Decision</tspan>
+								<text font-size="8" text-anchor="end">
+									<tspan x="232" y="118">WG</tspan><tspan x="232" y="126">Decision</tspan>
 								</text>
 								<path stroke="#000" d="M234,127v-34"></path>
 								<polygon points="234,92 230,102 238,102"></polygon>
@@ -90,8 +90,8 @@
 								<g role="img">
 									<title>Publish revised Candidate Recommendation Draft</title>
 								</g>
-								<text font-size="8">
-									<tspan x="282" y="52">WG Decision</tspan>
+								<text font-size="8" text-anchor="middle">
+									<tspan x="259" y="41">WG Decision</tspan>
 								</text>
 								<path stroke="#000" d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke-dasharray="6 2"></path>
 								<polygon points="282,54 277,64 275,53"></polygon>
@@ -104,8 +104,8 @@
 									<title>Publish revised Candidate Recommendation Snapshot</title>
 								</g>
 								<text font-size="8">
-									<tspan x="290" y="102">WG Decision +</tspan>
-									<tspan x="290" y="110">Team Approval</tspan>
+									<tspan x="290" y="99">WG Decision +</tspan>
+									<tspan x="290" y="107">Team Approval</tspan>
 								</text>
 								<path stroke="#000" d="M286,127v-34"></path>
 								<polygon points="286,128 282,118 290,118"></polygon>
@@ -118,12 +118,10 @@
 									<title>Publish revised Candidate Recommendation Snapshot</title>
 								</g>
 								<text font-size="8">
-									<tspan x="290" y="102">WG Decision</tspan>
-									<tspan x="290" y="110">Team Approval</tspan>
+									<tspan x="290" y="99">WG Decision</tspan>
+									<tspan x="290" y="107">Team Approval</tspan>
 								</text>
-								<path stroke="#000" d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114" stroke-dasharray="6 10" fill="none"></path>
-								<path stroke="#000" d="M242,124C238,114 244,104 260,104 271,104 277,108 279,114" stroke-dasharray="6 10" stroke-dashoffset="8" fill="none"></path>
-								<polygon points="282,114 277,124 275,113"></polygon>
+								<path stroke="#000" d="M242,124C238,114 244,104 260,104 271,104 285,108 286,117" stroke-dasharray="6 2" fill="none"></path>
 							</a>
 						</g>
 					<!-- Advance to PR -->
@@ -132,8 +130,9 @@
 							<g role="img">
 							<title>Advance to Proposed Recommendation</title>
 							</g>
-							<text x="300" y="126" font-size="8">WG Decision +</text>
-							<text x="300" y="134" font-size="8">Team Approval</text>
+							<text x="298" y="121" font-size="8">WG Decision +</text>
+							<text x="298" y="129" font-size="8">Team Approval +</text>
+							<text x="298" y="137" font-size="8">AC Review</text>
 							<path d="M298,140h77" stroke="#060"></path>
 							<polygon points="374,136 384,140 374,144"></polygon>
 						</a>
@@ -145,8 +144,8 @@
 								<title>Return to Working Draft</title>
 								</g>
 								<text font-size="8" text-anchor="end">
-									<tspan x="230" y="160">WG Decision</tspan>
-									<tspan x="230" y="168" font-size="6">(or Team Decision with AB+TAG Approval)</tspan>
+									<tspan x="228" y="157">WG Decision</tspan>
+									<tspan font-size="6" x="228" y="165">(or Team Decision with AB+TAG Approval)</tspan>
 								</text>
 								<path d="M140,147h84" stroke-dasharray="4 4" stroke="#900"></path>
 								<polygon points="140,145 133,147 140,149"></polygon>

From 816835fb0a900a14507422388fb7592a45888bfe Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 1 May 2024 17:28:46 +0900
Subject: [PATCH 056/237] Fix state separation and transitions in REC track
 diagram

---
 basic-rec-track.svg | 75 ++++++++++++++++++++++++---------------------
 1 file changed, 40 insertions(+), 35 deletions(-)

diff --git a/basic-rec-track.svg b/basic-rec-track.svg
index 5ef03557..1a074728 100644
--- a/basic-rec-track.svg
+++ b/basic-rec-track.svg
@@ -56,20 +56,13 @@
 				</g>
 			<!-- CRS -->
 				<g role="listitem">
-					<a href="#cr-1">
+					<a href="#pr-1">
 						<ellipse role="img" id="cr-1" ry="18" rx="38" cy="140" cx="260" stroke="black" fill="#fff">
 						<title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
 						</ellipse>
 						<text aria-hidden="true" font-size="14" font-weight="bold"
 						      y="144" x="260" text-anchor="middle" >CRS</text>
 					</a>
-					<a href="#crd-1">
-						<ellipse role="img" id="crd-1" ry="18" rx="38" cy="80" cx="260" stroke="black" fill="#fff">
-						<title>Candidate Recommendation Draft (CRD)</title>
-						</ellipse>
-						<text aria-hidden="true" font-size="14" font-weight="bold"
-						      y="84" x="260" text-anchor="middle">CRD</text>
-					</a>
 					<g role="list">
 					<!-- CRS to CRD -->
 						<g role="listitem">
@@ -84,33 +77,6 @@
 								<polygon points="234,92 230,102 238,102"></polygon>
 							</a>
 						</g>
-					<!-- Update CRD in place -->
-						<g role="listitem">
-							<a href="#crd-1">
-								<g role="img">
-									<title>Publish revised Candidate Recommendation Draft</title>
-								</g>
-								<text font-size="8" text-anchor="middle">
-									<tspan x="259" y="41">WG Decision</tspan>
-								</text>
-								<path stroke="#000" d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke-dasharray="6 2"></path>
-								<polygon points="282,54 277,64 275,53"></polygon>
-							</a>
-						</g>
-					<!-- CRD to CRS -->
-						<g role="listitem">
-							<a href="#cr-1">
-								<g role="img">
-									<title>Publish revised Candidate Recommendation Snapshot</title>
-								</g>
-								<text font-size="8">
-									<tspan x="290" y="99">WG Decision +</tspan>
-									<tspan x="290" y="107">Team Approval</tspan>
-								</text>
-								<path stroke="#000" d="M286,127v-34"></path>
-								<polygon points="286,128 282,118 290,118"></polygon>
-							</a>
-						</g>
 					<!-- Update CRS in place -->
 						<g role="listitem">
 							<a href="#cr-1">
@@ -153,6 +119,45 @@
 						</g>
 					</g>
 				</g>
+			<!-- CDR -->
+				<g role="listitem">
+					<a href="#cr-1">
+						<ellipse role="img" id="crd-1" ry="18" rx="38" cy="80" cx="260" stroke="black" fill="#fff">
+						<title>Candidate Recommendation Draft (CRD)</title>
+						</ellipse>
+						<text aria-hidden="true" font-size="14" font-weight="bold"
+						      y="84" x="260" text-anchor="middle">CRD</text>
+					</a>
+					<g role="list">
+					<!-- Update CRD in place -->
+						<g role="listitem">
+							<a href="#crd-1">
+								<g role="img">
+									<title>Publish revised Candidate Recommendation Draft</title>
+								</g>
+								<text font-size="8" text-anchor="middle">
+									<tspan x="259" y="41">WG Decision</tspan>
+								</text>
+								<path stroke="#000" d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke-dasharray="6 2"></path>
+								<polygon points="282,54 277,64 275,53"></polygon>
+							</a>
+						</g>
+					<!-- CRD to CRS -->
+						<g role="listitem">
+							<a href="#cr-1">
+								<g role="img">
+									<title>Publish revised Candidate Recommendation Snapshot</title>
+								</g>
+								<text font-size="8">
+									<tspan x="290" y="99">WG Decision +</tspan>
+									<tspan x="290" y="107">Team Approval</tspan>
+								</text>
+								<path stroke="#000" d="M286,127v-34"></path>
+								<polygon points="286,128 282,118 290,118"></polygon>
+							</a>
+						</g>
+					</g>
+				</g>
 			<!-- PR -->
 				<g role="listitem">
 					<a href="#rec-1">

From 6fe8d2c56452631634df25719eb87267970925fa Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 9 May 2024 00:04:39 +0900
Subject: [PATCH 057/237] [Editorial] Give context for candidate amendments
 when revising a REC (#862)

This change gives a little bit more context about how to make normative
changes to a REC. Technically, and this is what the existing text talked
about, they are made by folding in candidate amendments. However,
someone just reading that section may not be aware of what candidate
amendments are and how they are made to begin with.

This gives just a little bit of context to help people piece things
together.

This is a small step towards addressing https://github.com/w3c/w3process/issues/700

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 21 +++++++++++++++++----
 1 file changed, 17 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 67478ddf..69f2f717 100644
--- a/index.bs
+++ b/index.bs
@@ -4045,12 +4045,20 @@ Revising a Recommendation: Editorial Changes</h5>
 <h5 id="revised-rec-substantive">
 Revising a Recommendation: Substantive Changes</h5>
 
+	Tentative corrections (see <a href="#class-3">class 3 changes</a>)
+	<em class=rfc2119>may</em> be annotated into a [=Recommendation=]
+	using [=candidate corrections=].
+
+	Note: [=Candidate corrections=] do not normatively modify the document;
+	they editorially indicate how one might do so.
+	They are therefore published following the provisions of [[#revised-rec-editorial]].
+
 	A [=candidate correction=] can be made normative
 	and be folded into the main text of the [=Recommendation=],
 	once it has satisfied all the same criteria
 	as the rest of the [=Recommendation=],
 	including review by the community to ensure
-	the technical and editorial soundness of the [=candidate amendments=].
+	its technical and editorial soundness.
 	To validate this, the [=Working Group=] must request
 	a [=Last Call for Review of Proposed Amendments=],
 	followed by an [=update request=].
@@ -4073,13 +4081,18 @@ Revising a Recommendation: Substantive Changes</h5>
 <h5 id="revised-rec-features">
 Revising a Recommendation: New Features</h5>
 
-	New features (see <a href="#correction-classes">class 4 changes</a>)
-	may be incorporated into a [=Recommendation=]
+	Tentative new features (see <a href="#correction-classes">class 4 changes</a>)
+	<em class=rfc2119>may</em> be annotated into a [=Recommendation=]
 	explicitly identified as [=allow new features|allowing new features=]
 	using [=candidate additions=].
+
+	Note: [=Candidate additions=] do not normatively modify the document;
+	they editorially indicate how one might do so.
+	They are therefore published following the provisions of [[#revised-rec-editorial]].
+
 	A [=candidate addition=] can be made normative
 	and be folded into the main text of the [=Recommendation=]
-	using the same process as for [=candidate amendments=],
+	using the same process as for [=candidate corrections=],
 	as detailed in [[#revised-rec-substantive]].
 
 	Note: This prohibition against new features unless explicitly allowed

From 077fc34072f8210ffd232faaae7c4d363f9fbdd9 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 9 May 2024 02:19:42 +0900
Subject: [PATCH 058/237] Consolidate maintenance by the Team of technical
 reports (#860)

Merge into a single section all clauses about the Team maintaining
technical reports in the absence of a chartered  group, and uniformize
the types of edits that they can make (class 1 changes, errata, and Team
corrections).

See https://github.com/w3c/w3process/issues/120

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 71 ++++++++++++++++++++++++++++++--------------------------
 1 file changed, 38 insertions(+), 33 deletions(-)

diff --git a/index.bs b/index.bs
index 69f2f717..4f278ee2 100644
--- a/index.bs
+++ b/index.bs
@@ -3143,18 +3143,6 @@ Candidate Amendments</h4>
 	except that it proposes a new feature
 	rather than an error correction.
 
-	If there is no group chartered to maintain a [=technical report=],
-	the [=Team=] <em class="rfc2119">may</em> maintain its [=errata=]
-	and associated [=candidate corrections=].
-	Such corrections <em class=rfc2119>must</em> be marked
-	as <dfn>Team correction</dfn>,
-	and do not constitute
-	a normative portion of the Recommendation,
-	as defined in the Patent Policy [[PATENT-POLICY]]
-	(i.e. they are not covered by the Patent Policy).
-	The [=Team=] <em class=rfc2119>must</em> solicit [=wide review=]
-	on [=Team corrections=] that it produces.
-
 	[=Candidate corrections=] and [=candidate additions=] are collectively known as
 	<dfn lt="candidate amendment">candidate amendments</dfn>.
 
@@ -3163,6 +3151,44 @@ Candidate Amendments</h4>
 	for the purpose of the W3C Patent Policy [[PATENT-POLICY]],
 	to be [=Working Drafts=] with those [=candidate amendments=] treated as normative.
 
+<h4 id=no-group-maintenance>
+Maintenance Without a Group</h4>
+
+	For all [[#recs-and-notes|types of technical reports]] and all [[#maturity-stages|maturity stages]],
+	if there is no [=chartered group|group=] chartered to maintain a [=technical report=],
+	the [=Team=] <em class="rfc2119">may</em> republish it
+	at the same [[#maturity-stages|maturity stage]],
+	integrating as needed:
+	<ol>
+		<li><a href="#correction-classes">class 1 changes</a>;
+		<li>inline [=errata=];
+		<li>[=candidate corrections=],
+			which <em class=rfc2119>must</em> be marked as <dfn>Team correction</dfn>;
+		<li><a href="#correction-classes">class 2 changes</a> other than inline [=errata=] and [=Team corrections=].
+	</ol>
+
+	To avoid any potential doubt or disagreement
+	about whether changes really do fall into <a href="#correction-classes">class 2</a>,
+	the [=Team=] <em class=rfc2119>should</em> be conservative,
+	limiting itself to obvious and limited fixes,
+	and <em class=rfc2119>must</em> avoid substantial rephrasing,
+	even of non-normative examples and notes.
+	If any such change is desired,
+	the [=Team=] <em class=rfc2119>must</em> mark it as a [=Team correction=].
+
+	[=Team corrections=] do not constitute
+	a normative portion of the Recommendation,
+	as defined in the Patent Policy [[PATENT-POLICY]]
+	(i.e., they are not covered by the Patent Policy).
+	For [=Candidate Recommendations=],
+	[=Proposed Recommendations=],
+	[=W3C Recommendations=],
+	[=Candidate Registries=],
+	[=W3C Registries=],
+	as well as [=W3C Statements=],
+	the [=Team=] <em class=rfc2119>must</em> solicit [=wide review=]
+	on [=Team corrections=] that it produces.
+
 <h4 id="contributor-license">
 License Grants from Non-Participants</h4>
 
@@ -4023,10 +4049,6 @@ Revising a Recommendation: Markup Changes</h5>
 	in any changes to the text of the specification.
 	(See <a href="#correction-classes">class 1 changes</a>.)
 
-	If there is no [=Working Group=] chartered to maintain a [=Recommendation=],
-	the [=Team=] <em class="rfc2119">may</em> republish the [=Recommendation=]
-	with such changes incorporated.
-
 <h5 id="revised-rec-editorial">
 Revising a Recommendation: Editorial Changes</h5>
 
@@ -4037,11 +4059,6 @@ Revising a Recommendation: Editorial Changes</h5>
 	to make this class of change without passing through earlier maturity stages.
 	(See <a href="#correction-classes">class 2 changes</a>.)
 
-	If there is no [=Working Group=] chartered to maintain a [=Recommendation=],
-	the [=Team=] <em class="rfc2119">may</em> republish the [=Recommendation=]
-	with such changes incorporated,
-	including [=errata=] and [=Team corrections=].
-
 <h5 id="revised-rec-substantive">
 Revising a Recommendation: Substantive Changes</h5>
 
@@ -4072,12 +4089,6 @@ Revising a Recommendation: Substantive Changes</h5>
 	and advance the specification from that state.
 	(See <a href="#correction-classes">class 3 changes</a>.)
 
-	Note: If there is no [=Working Group=] chartered to maintain a [=Recommendation=]
-	the [=Team=] cannot make substantive changes and republish the [=Recommendation=].
-	It can, however, informatively highlight problems and desirable changes
-	using [=errata=] and [=candidate corrections=]
-	and republish as described in [[#revised-rec-editorial|the previous section]].
-
 <h5 id="revised-rec-features">
 Revising a Recommendation: New Features</h5>
 
@@ -4438,10 +4449,6 @@ Publishing Notes</h4>
 	A [=technical report=] <em class="rfc2119">may</em> remain
 	a [=Note=] indefinitely.
 
-	If a [=Note=] produced by a [=chartered group=] is no longer in scope for any group,
-	the [=Team=] <em class=rfc2119>may</em> republish the [=Note=] with [[#correction-classes|class 1]] changes incorporated,
-	as well as with [=errata=] and [=Team corrections=] annotated.
-
 <h4 id=w3c-statement oldids=memo>
 Elevating Group Notes to W3C Statement status</h4>
 
@@ -4773,8 +4780,6 @@ Registry Data Reports</h4>
 	the [=Working Group=]
 	<em class=rfc2119>may</em> republish the [=Registry Data Report=] to incorporate
 	[=editorial changes=].
-	If there is no [=Working Group=] chartered to maintain this registry,
-	the [=Team=] <em class=rfc2119>may</em> do so instead.
 
 <h4 id=reg-ref-specifications>
 Specifications that Reference Registries</h4>

From 8b48f80e42a5624d52258cb2fb692f99b144bca0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 9 May 2024 02:28:01 +0900
Subject: [PATCH 059/237] Update changes section

---
 index.bs | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 4f278ee2..262dd78d 100644
--- a/index.bs
+++ b/index.bs
@@ -5668,7 +5668,7 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 			(See <a href="https://github.com/w3c/w3process/issues/779">Issue 779</a>)
 
 		<li>
-			Clarify the defition of a Registry (see <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
+			Clarify the definition of a Registry (see <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
 			and of Recommendation Track Documents (see <a href="https://github.com/w3c/w3process/pull/831">Pull Request 831</a>).
 
 		<li>
@@ -5689,6 +5689,12 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 			and nobody was using it.
 			(See <a href="https://github.com/w3c/w3process/issues/856">Issue 856</a>)
 
+		<li>
+			Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a>
+			the various parts of the Process
+			that described whether and how the Team can maintain technical reports
+			that no longer have a Group chartered to maintain them.
+			(See <a href="https://github.com/w3c/w3process/pull/860">Pull Request 860</a>)
 	</ul>
 
 

From a4428add08a87d533e0727cce90c91a79f4e4aaf Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 23 May 2024 01:30:19 +0900
Subject: [PATCH 060/237] Require listing chair(s) in charters

See #823

Co-authored-by: Chris Needham <chrisn@users.noreply.github.com>
---
 index.bs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/index.bs b/index.bs
index 262dd78d..d773365c 100644
--- a/index.bs
+++ b/index.bs
@@ -1759,6 +1759,9 @@ Content of a Charter</h3>
 			The <a href="#confidentiality-levels">level of confidentiality</a>
 			of the group's proceedings and deliverables.
 
+		<li>
+			The name and affiliation of the [=Chair=] or co-Chairs.
+
 		<li>
 			Meeting mechanisms and expected frequency.
 

From fc624ff6d53a46fa4eabfc4fbe040e953c445496 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 23 May 2024 01:31:28 +0900
Subject: [PATCH 061/237] Add note reminding that the first stage of REC track
 is WD (#877)

See #864
---
 index.bs | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/index.bs b/index.bs
index d773365c..4b084e3f 100644
--- a/index.bs
+++ b/index.bs
@@ -4851,6 +4851,13 @@ Switching Tracks</h3>
 	their new track’s initial maturity stage,
 	while retaining any established identity (url, shortname, etc.).
 
+	Note: The initial maturity stage of the [=Recommendation track=] is [=Working Draft=].
+	[=First Public Working Draft=] designates a specific type of [=Working Draft=]
+	and is not a separate maturity stage.
+	A document which switches to the [=Recommendation track=] is only published as a [=First Public Working Draft=]
+	if it was never previously published as such,
+	otherwise it is simply a [=Working Draft=].
+
 <h3 id="further-reading">
 Further reading</h3>
 

From 68c1bede9329d98e1a6f7c53b7910c0b9b125161 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 23 May 2024 01:51:18 +0900
Subject: [PATCH 062/237] Consolidate similar parts of REC revision (#878)

Revising a REC is a fairly complicated piece of the Process. The 4
subsections that deal with making revisions for class 1 through 4 are
comparatively simple, but they had very strong similarities between
class 1 and 2, and class 3 and 4. Consolidating the text not only makes
the whole thing shorter, it also eliminates subtle differences of
language that could leave people wondering about potential differences
where none were intended or useful.

This is a small part in addressing #700
---
 index.bs | 38 ++++++++++----------------------------
 1 file changed, 10 insertions(+), 28 deletions(-)

diff --git a/index.bs b/index.bs
index 4b084e3f..6dc3ecba 100644
--- a/index.bs
+++ b/index.bs
@@ -4042,17 +4042,7 @@ Transitioning to W3C Recommendation</h4>
 <h4 id=revising-rec oldids="rec-modify, revised-rec">
 Revising a W3C Recommendation</h4>
 
-	This section details the process for making changes to a [=Recommendation=].
-
-<h5 id="revised-rec-markup">
-Revising a Recommendation: Markup Changes</h5>
-
-	A [=Working group=] <em class="rfc2119">may</em> request republication of a [=Recommendation=]
-	to make corrections that do not result
-	in any changes to the text of the specification.
-	(See <a href="#correction-classes">class 1 changes</a>.)
-
-<h5 id="revised-rec-editorial">
+<h5 id="revised-rec-editorial" oldids="revised-rec-markup">
 Revising a Recommendation: Editorial Changes</h5>
 
 	[=Editorial changes=] to a [=Recommendation=] require no technical review of the intended changes.
@@ -4060,7 +4050,7 @@ Revising a Recommendation: Editorial Changes</h5>
 	provided there are no votes against the [=group decision|decision=] to publish,
 	<em class="rfc2119">may</em> request publication of a [=Recommendation=]
 	to make this class of change without passing through earlier maturity stages.
-	(See <a href="#correction-classes">class 2 changes</a>.)
+	(See <a href="#class-1">class 1</a> and <a href="#class-2">class 2 changes</a>.)
 
 <h5 id="revised-rec-substantive">
 Revising a Recommendation: Substantive Changes</h5>
@@ -4095,23 +4085,15 @@ Revising a Recommendation: Substantive Changes</h5>
 <h5 id="revised-rec-features">
 Revising a Recommendation: New Features</h5>
 
-	Tentative new features (see <a href="#correction-classes">class 4 changes</a>)
-	<em class=rfc2119>may</em> be annotated into a [=Recommendation=]
-	explicitly identified as [=allow new features|allowing new features=]
-	using [=candidate additions=].
-
-	Note: [=Candidate additions=] do not normatively modify the document;
-	they editorially indicate how one might do so.
-	They are therefore published following the provisions of [[#revised-rec-editorial]].
-
-	A [=candidate addition=] can be made normative
-	and be folded into the main text of the [=Recommendation=]
-	using the same process as for [=candidate corrections=],
-	as detailed in [[#revised-rec-substantive]].
+	For [=Recommendations=] explicitly identified as  [=allow new features|allowing new features=],
+	tentative new features (see <a href="#correction-classes">class 4 changes</a>)
+	<em class=rfc2119>may</em> be annotated in as [=candidate additions=],
+	and <a href="#correction-classes">class 4 changes</a> may be normatively incorporated
+	as for <a href="#correction-classes">class 3 changes</a> in [[#revised-rec-substantive]].
 
-	Note: This prohibition against new features unless explicitly allowed
-	enables third parties to depend on Recommendations having a stable feature-set,
-	as they have prior to the 2020 revision of this Process.
+	Note: Limiting the addition of new features to [=Recommendations=] that explicitly allow them
+	enables third parties to depend on a stable feature-set for [=Recommendations=] that do not advertise that ability,
+	as was the case for all [=Recommendations=] prior to the 2020 revision of this Process.
 
 	To make changes which introduce a new feature
 	to a [=Recommendation=] that does not [=allow new features=],

From fe9ef5b070b386e18376d763453ba9df063f468c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 23 May 2024 01:53:41 +0900
Subject: [PATCH 063/237] [Editorial] Rephrase what CRDs are for (#873)

By focusing on what the changes in a CDR are from rather than what
they're aimed at, we can both make the sentence simpler and avoid making
undesired implications about the impossibility to transition from CRD to PR.

This addresses #450

Co-authored-by: Dominique Hazael-Massieux <dom@w3.org>
---
 index.bs | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 6dc3ecba..14d67090 100644
--- a/index.bs
+++ b/index.bs
@@ -3349,10 +3349,8 @@ Maturity Stages on the Recommendation Track</h4>
 					<dfn export lt="Candidate Recommendation Draft | CRD">Candidate Recommendation Draft</dfn> (<abbr>CRD</abbr>)
 				<dd>
 					A Candidate Recommendation Draft
-					is published on the <a href="https://www.w3.org/TR/">W3C's Technical Reports page</a> [[TR]]
-					to integrate changes from the previous [=Candidate Recommendation Snapshot=]
-					that the Working Group intends to include
-					in a subsequent [=Candidate Recommendation Snapshot=].
+					is published
+					to solicit review of intended changes from the previous [=Candidate Recommendation Snapshot=].
 					This allows for wider review of the changes
 					and for ease of reference to the integrated specification.
 

From 6914bc0c36588921306fef35c69b7d08ba63b1ba Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 23 May 2024 02:00:42 +0900
Subject: [PATCH 064/237] Update changelog

---
 index.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.bs b/index.bs
index 14d67090..8bf09134 100644
--- a/index.bs
+++ b/index.bs
@@ -5685,6 +5685,10 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 			that described whether and how the Team can maintain technical reports
 			that no longer have a Group chartered to maintain them.
 			(See <a href="https://github.com/w3c/w3process/pull/860">Pull Request 860</a>)
+
+		<li>
+			Require Chairs to be listed in Charters.
+			(See <a href="https://github.com/w3c/w3process/issues/823">Issue 823</a>)
 	</ul>
 
 

From ca4b657cb5fa8620001695e7e7046b48d87dfd00 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 3 Jun 2024 11:46:27 +0900
Subject: [PATCH 065/237] Punctuation tweak

As suggested in https://github.com/w3c/w3process/pull/877/files#r1623157010
---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 8bf09134..b269bd88 100644
--- a/index.bs
+++ b/index.bs
@@ -4835,8 +4835,8 @@ Switching Tracks</h3>
 	[=First Public Working Draft=] designates a specific type of [=Working Draft=]
 	and is not a separate maturity stage.
 	A document which switches to the [=Recommendation track=] is only published as a [=First Public Working Draft=]
-	if it was never previously published as such,
-	otherwise it is simply a [=Working Draft=].
+	if it was never previously published as such;
+	otherwise, it is simply a [=Working Draft=].
 
 <h3 id="further-reading">
 Further reading</h3>

From 7912c023d7b495ad665c9ef90331f1c064f118cd Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 13 Jun 2024 01:09:21 +0200
Subject: [PATCH 066/237] Remove note about AC consensus assessment (#875)

Assessing the consensus of the AC in AC reviews is overseen by the Team
as a whole, not by the CEO singularly. Assessing the consensus of the AC
outside of an AC Review is not something any of our processes depend on,
so discussing who is responsible for it is unnecessary (and the phrasing
is clumsy anyway).

See #615
---
 index.bs | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/index.bs b/index.bs
index b269bd88..f3b132d4 100644
--- a/index.bs
+++ b/index.bs
@@ -2041,9 +2041,6 @@ Consensus</h4>
 	or <a href="#distributed-meeting">distributed</a>)
 	as well as through <a href=#discussion-archiving>persistent text-based discussions</a>.
 
-	Note: The CEO has the role of
-	assessing consensus within the Advisory Committee.
-
 	The following terms are used in this document
 	to describe the level of support for a decision among a set of eligible individuals:
 

From 428a9f135ef731d4b4d9be322474f729140c7c80 Mon Sep 17 00:00:00 2001
From: sideshowbarker <mike@w3.org>
Date: Mon, 17 Jun 2024 00:40:13 +0900
Subject: [PATCH 067/237] Add explainer.md

---
 explainer.md | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 explainer.md

diff --git a/explainer.md b/explainer.md
new file mode 100644
index 00000000..d3be634b
--- /dev/null
+++ b/explainer.md
@@ -0,0 +1,11 @@
+This in an explainer for the [W3C Process document](https://www.w3.org/Consortium/Process/Drafts/), with the intended audience being W3C Working Group members — and their chairs — who are trying to understand various aspects of the W3C process. This explainer is incomplete and, so far, contains only information related to publication of “living standards”.
+
+## The W3C Recommendation Track
+
+This section of the explainer so far contains only one subsection, on publication of so-called “living standards”.
+
+### Living standards
+
+For any of your deliverables which have reached CR, your group has the option to keep that deliverable at CR as a so-called “living standard” or “evergreen standard” — which you can, from then on, continuously update at any time; that is, without any intent to ever advance the document to Recommendation.
+
+In other words, that continuously-updated CR becomes the terminal state of that deliverable in the W3C publication-maturity process for web standards (which, in the Process document itself, is what’s described in the section titled [The W3C Recommendation Track](https://www.w3.org/Consortium/Process/Drafts/#rec-track)).

From b1df4f20441eb78c49b2f6751c0b7e382ba97bce Mon Sep 17 00:00:00 2001
From: sideshowbarker <mike@w3.org>
Date: Mon, 17 Jun 2024 08:33:44 +0900
Subject: [PATCH 068/237] Renamed explainer.md to faq.md

---
 explainer.md | 11 -----------
 faq.md       | 11 +++++++++++
 2 files changed, 11 insertions(+), 11 deletions(-)
 delete mode 100644 explainer.md
 create mode 100644 faq.md

diff --git a/explainer.md b/explainer.md
deleted file mode 100644
index d3be634b..00000000
--- a/explainer.md
+++ /dev/null
@@ -1,11 +0,0 @@
-This in an explainer for the [W3C Process document](https://www.w3.org/Consortium/Process/Drafts/), with the intended audience being W3C Working Group members — and their chairs — who are trying to understand various aspects of the W3C process. This explainer is incomplete and, so far, contains only information related to publication of “living standards”.
-
-## The W3C Recommendation Track
-
-This section of the explainer so far contains only one subsection, on publication of so-called “living standards”.
-
-### Living standards
-
-For any of your deliverables which have reached CR, your group has the option to keep that deliverable at CR as a so-called “living standard” or “evergreen standard” — which you can, from then on, continuously update at any time; that is, without any intent to ever advance the document to Recommendation.
-
-In other words, that continuously-updated CR becomes the terminal state of that deliverable in the W3C publication-maturity process for web standards (which, in the Process document itself, is what’s described in the section titled [The W3C Recommendation Track](https://www.w3.org/Consortium/Process/Drafts/#rec-track)).
diff --git a/faq.md b/faq.md
new file mode 100644
index 00000000..47f9b4a2
--- /dev/null
+++ b/faq.md
@@ -0,0 +1,11 @@
+This in an FAQ for the [W3C Process document](https://www.w3.org/Consortium/Process/Drafts/), with the intended audience being W3C Working Group members — and their chairs — who are trying to understand various aspects of the W3C process.
+
+## Living standards
+
+This section contains information about publication of so-called “living standards” or “evergreen standards” at the W3C.
+
+### Does the W3C process enable publication of so-called “living standards”?
+
+Yes. For any of your working-group deliverables which have reached CR, your group has the option to keep that deliverable at CR as a so-called “living standard” or “evergreen standard” — which you can, from then on, continuously update at any time; that is, without any intent to ever advance the document to Recommendation.
+
+In other words, that continuously-updated CR becomes the terminal state of that deliverable in the W3C publication-maturity process for web standards (which, in the Process document itself, is what’s described in the section titled [The W3C Recommendation Track](https://www.w3.org/Consortium/Process/Drafts/#rec-track)).

From 11ee9c2e4eec28291f8c4271a593e4b5324bd3c4 Mon Sep 17 00:00:00 2001
From: sideshowbarker <mike@w3.org>
Date: Mon, 17 Jun 2024 08:49:24 +0900
Subject: [PATCH 069/237] Shorten heading

---
 faq.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/faq.md b/faq.md
index 47f9b4a2..0d024245 100644
--- a/faq.md
+++ b/faq.md
@@ -4,7 +4,7 @@ This in an FAQ for the [W3C Process document](https://www.w3.org/Consortium/Proc
 
 This section contains information about publication of so-called “living standards” or “evergreen standards” at the W3C.
 
-### Does the W3C process enable publication of so-called “living standards”?
+### Does the W3C have living standards?
 
 Yes. For any of your working-group deliverables which have reached CR, your group has the option to keep that deliverable at CR as a so-called “living standard” or “evergreen standard” — which you can, from then on, continuously update at any time; that is, without any intent to ever advance the document to Recommendation.
 

From 5e4f2b670b6dadbfdcada6682cbea4a0e79ef2fa Mon Sep 17 00:00:00 2001
From: sideshowbarker <mike@w3.org>
Date: Mon, 17 Jun 2024 15:43:52 +0900
Subject: [PATCH 070/237] =?UTF-8?q?FAQ:=20Add=20section=20on=20the=20terms?=
 =?UTF-8?q?=20=E2=80=9CTechnical=20Reports=E2=80=9D,=20=E2=80=9CTR?=
 =?UTF-8?q?=E2=80=9D,=20and=20=E2=80=9CTR=20space=E2=80=9D?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 faq.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/faq.md b/faq.md
index 0d024245..ede6758e 100644
--- a/faq.md
+++ b/faq.md
@@ -1,5 +1,27 @@
 This in an FAQ for the [W3C Process document](https://www.w3.org/Consortium/Process/Drafts/), with the intended audience being W3C Working Group members — and their chairs — who are trying to understand various aspects of the W3C process.
 
+## Technical Reports
+
+### What is a Technical Report?
+
+Anywhere you see or hear the term _“Technical Report”_, you can substitute the term _“W3C Publication”_. So, for example, you can read the beginning of the section at https://www.w3.org/policies/process/drafts/#Reports as:
+
+> #### W3C Publications
+>
+> The W3C Publication development process is the set of steps and requirements followed by W3C Working Groups to standardize Web technology. The W3C Publication development process is designed to…
+
+And you can read the heading the section at https://www.w3.org/policies/process/drafts/#recs-and-notes as:
+
+> #### Types of W3C Publications
+
+### What is a TR?
+
+_“TR”_ is an abbreviation for _“Technical Report”_. In other words, you any time you see or hear _“TR”_, you can substitute the term _“W3C Publication”_.
+
+### What is TR space?
+
+_“TR space”_ means https://www.w3.org/TR/ — that is, it’s the area of the w3.org website under which W3C standards are published. So any time you see or hear the term _“TR space”_, you can substitute the term _“W3C publications space”_ — or even _“W3C standards space”_.
+
 ## Living standards
 
 This section contains information about publication of so-called “living standards” or “evergreen standards” at the W3C.

From bcbe64bb8eff49a511e281aa27565c373f7322ce Mon Sep 17 00:00:00 2001
From: sideshowbarker <mike@w3.org>
Date: Mon, 17 Jun 2024 16:01:56 +0900
Subject: [PATCH 071/237] =?UTF-8?q?FAQ:=20Add=20section=20about=20?=
 =?UTF-8?q?=E2=80=9CRecommendation=20Track=E2=80=9D?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 faq.md | 27 ++++++++++++++++++++++++++-
 1 file changed, 26 insertions(+), 1 deletion(-)

diff --git a/faq.md b/faq.md
index ede6758e..06194c79 100644
--- a/faq.md
+++ b/faq.md
@@ -2,6 +2,8 @@ This in an FAQ for the [W3C Process document](https://www.w3.org/Consortium/Proc
 
 ## Technical Reports
 
+This section contains clarifications about so-called “Technical Reports”.
+
 ### What is a Technical Report?
 
 Anywhere you see or hear the term _“Technical Report”_, you can substitute the term _“W3C Publication”_. So, for example, you can read the beginning of the section at https://www.w3.org/policies/process/drafts/#Reports as:
@@ -10,7 +12,7 @@ Anywhere you see or hear the term _“Technical Report”_, you can substitute t
 >
 > The W3C Publication development process is the set of steps and requirements followed by W3C Working Groups to standardize Web technology. The W3C Publication development process is designed to…
 
-And you can read the heading the section at https://www.w3.org/policies/process/drafts/#recs-and-notes as:
+And you can read the heading of the section at https://www.w3.org/policies/process/drafts/#recs-and-notes as:
 
 > #### Types of W3C Publications
 
@@ -22,6 +24,29 @@ _“TR”_ is an abbreviation for _“Technical Report”_. In other words, you
 
 _“TR space”_ means https://www.w3.org/TR/ — that is, it’s the area of the w3.org website under which W3C standards are published. So any time you see or hear the term _“TR space”_, you can substitute the term _“W3C publications space”_ — or even _“W3C standards space”_.
 
+## Recommendation Track
+
+This section contains clarifications about the so-called “Recommendation Track”.
+
+### What is the Recommendation Track?
+
+Anywhere you see or hear the term _“Recommendation Track”_, you can substitute the term _“Standards Track”_. So, for example, you can read the beginning of the section at https://www.w3.org/policies/process/drafts/#rec-track as:
+
+> #### The W3C Standards Track
+>
+> Working Groups create specifications and guidelines to complete the scope of work envisioned by a Working Group's charter. These W3C Publications undergo cycles of revision and review as they advance towards W3C Recommendation status.
+
+And you can read the beginning of the section at https://www.w3.org/policies/process/drafts/#recs-and-notes as:
+
+> #### Types of W3C Publications
+>
+> This chapter describes the formal requirements for publishing and
+> maintaining a W3C Standard, Note, or Registry Report.
+>
+> #### Standards
+>
+> Working Groups develop W3C Publications on the W3C Standards Track in order to produce normative specifications or guidelines as standards for the Web. The Standards Track process incorporates requirements for wide review, adequate implementation experience, and consensus-building.
+
 ## Living standards
 
 This section contains information about publication of so-called “living standards” or “evergreen standards” at the W3C.

From c7491cad725beedb95826257cb87dded2c808393 Mon Sep 17 00:00:00 2001
From: sideshowbarker <mike@w3.org>
Date: Mon, 17 Jun 2024 16:27:30 +0900
Subject: [PATCH 072/237] =?UTF-8?q?Add=20=E2=80=9CWhy=20not=20just=20publi?=
 =?UTF-8?q?sh=20Working=20Drafts=3F=E2=80=9D?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 faq.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/faq.md b/faq.md
index 06194c79..0c98ecac 100644
--- a/faq.md
+++ b/faq.md
@@ -56,3 +56,10 @@ This section contains information about publication of so-called “living stand
 Yes. For any of your working-group deliverables which have reached CR, your group has the option to keep that deliverable at CR as a so-called “living standard” or “evergreen standard” — which you can, from then on, continuously update at any time; that is, without any intent to ever advance the document to Recommendation.
 
 In other words, that continuously-updated CR becomes the terminal state of that deliverable in the W3C publication-maturity process for web standards (which, in the Process document itself, is what’s described in the section titled [The W3C Recommendation Track](https://www.w3.org/Consortium/Process/Drafts/#rec-track)).
+
+### Why publish Candidate Recommendations?
+
+### Why not just publish Working Drafts?
+
+If your working group wants to publish your spec as a so-called “living standard”, and you are wondering why you should transition the spec to Candidate Recommendation — rather than just publishing a Working Draft and continuously updating that Working Draft — the reason is: [to come]
+<!-- I don’t actually know the answer to this question… -->

From 831a6c3c193cfbc4e1c58f35d26a7cbec3b45a2b Mon Sep 17 00:00:00 2001
From: sideshowbarker <mike@w3.org>
Date: Mon, 17 Jun 2024 16:33:56 +0900
Subject: [PATCH 073/237] Move faq.md to
 https://github.com/w3c/process/wiki/FAQ

---
 faq.md | 65 ----------------------------------------------------------
 1 file changed, 65 deletions(-)
 delete mode 100644 faq.md

diff --git a/faq.md b/faq.md
deleted file mode 100644
index 0c98ecac..00000000
--- a/faq.md
+++ /dev/null
@@ -1,65 +0,0 @@
-This in an FAQ for the [W3C Process document](https://www.w3.org/Consortium/Process/Drafts/), with the intended audience being W3C Working Group members — and their chairs — who are trying to understand various aspects of the W3C process.
-
-## Technical Reports
-
-This section contains clarifications about so-called “Technical Reports”.
-
-### What is a Technical Report?
-
-Anywhere you see or hear the term _“Technical Report”_, you can substitute the term _“W3C Publication”_. So, for example, you can read the beginning of the section at https://www.w3.org/policies/process/drafts/#Reports as:
-
-> #### W3C Publications
->
-> The W3C Publication development process is the set of steps and requirements followed by W3C Working Groups to standardize Web technology. The W3C Publication development process is designed to…
-
-And you can read the heading of the section at https://www.w3.org/policies/process/drafts/#recs-and-notes as:
-
-> #### Types of W3C Publications
-
-### What is a TR?
-
-_“TR”_ is an abbreviation for _“Technical Report”_. In other words, you any time you see or hear _“TR”_, you can substitute the term _“W3C Publication”_.
-
-### What is TR space?
-
-_“TR space”_ means https://www.w3.org/TR/ — that is, it’s the area of the w3.org website under which W3C standards are published. So any time you see or hear the term _“TR space”_, you can substitute the term _“W3C publications space”_ — or even _“W3C standards space”_.
-
-## Recommendation Track
-
-This section contains clarifications about the so-called “Recommendation Track”.
-
-### What is the Recommendation Track?
-
-Anywhere you see or hear the term _“Recommendation Track”_, you can substitute the term _“Standards Track”_. So, for example, you can read the beginning of the section at https://www.w3.org/policies/process/drafts/#rec-track as:
-
-> #### The W3C Standards Track
->
-> Working Groups create specifications and guidelines to complete the scope of work envisioned by a Working Group's charter. These W3C Publications undergo cycles of revision and review as they advance towards W3C Recommendation status.
-
-And you can read the beginning of the section at https://www.w3.org/policies/process/drafts/#recs-and-notes as:
-
-> #### Types of W3C Publications
->
-> This chapter describes the formal requirements for publishing and
-> maintaining a W3C Standard, Note, or Registry Report.
->
-> #### Standards
->
-> Working Groups develop W3C Publications on the W3C Standards Track in order to produce normative specifications or guidelines as standards for the Web. The Standards Track process incorporates requirements for wide review, adequate implementation experience, and consensus-building.
-
-## Living standards
-
-This section contains information about publication of so-called “living standards” or “evergreen standards” at the W3C.
-
-### Does the W3C have living standards?
-
-Yes. For any of your working-group deliverables which have reached CR, your group has the option to keep that deliverable at CR as a so-called “living standard” or “evergreen standard” — which you can, from then on, continuously update at any time; that is, without any intent to ever advance the document to Recommendation.
-
-In other words, that continuously-updated CR becomes the terminal state of that deliverable in the W3C publication-maturity process for web standards (which, in the Process document itself, is what’s described in the section titled [The W3C Recommendation Track](https://www.w3.org/Consortium/Process/Drafts/#rec-track)).
-
-### Why publish Candidate Recommendations?
-
-### Why not just publish Working Drafts?
-
-If your working group wants to publish your spec as a so-called “living standard”, and you are wondering why you should transition the spec to Candidate Recommendation — rather than just publishing a Working Draft and continuously updating that Working Draft — the reason is: [to come]
-<!-- I don’t actually know the answer to this question… -->

From 50ce7b799494802b6c85482a34c3b383cfc2eb31 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 18 Jun 2024 06:11:09 +0900
Subject: [PATCH 074/237] Update URLs

---
 index.bs | 75 ++++++++++++++++++++++++++++++--------------------------
 1 file changed, 40 insertions(+), 35 deletions(-)

diff --git a/index.bs b/index.bs
index f3b132d4..11e5dc79 100644
--- a/index.bs
+++ b/index.bs
@@ -27,17 +27,17 @@
 Title: W3C Process Document
 Group: processcg
 Status: CG-DRAFT
-ED: https://www.w3.org/Consortium/Process/Drafts/
-TR: https://www.w3.org/Consortium/Process/
-Previous Version: https://www.w3.org/2023/Process-20231103/
+ED: https://www.w3.org/policies/process/drafts/
+TR: https://www.w3.org/policies/process/
+Previous Version: https://www.w3.org/policies/process/20231103/
 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/w3process
-Shortname: w3process
+Repository: w3c/process
+Shortname: process
 Abstract:
 	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.
@@ -49,13 +49,13 @@ Abstract:
 	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/2023/Process-20231103/">3 November 2023 Process</a>,
+	which is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 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/Consortium/Process/#GAProcess">Section 11 Process Changes</a>,
+	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/w3process/issues/
+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
@@ -115,7 +115,7 @@ Relation of Process Document to Patent Policy and Other Policies</h2>
 	W3C Members' attention is called to the fact
 	that provisions of the Process Document are binding on Members
 	per the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> [[MEMBER-AGREEMENT]].
-	The <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> [[!PATENT-POLICY]]
+	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.
@@ -1378,9 +1378,9 @@ Chartered Groups: Working Groups and Interest Groups</h3>
 
 			Working Groups have additional participation requirements
 			described in the W3C Patent Policy [[!PATENT-POLICY]],
-			see particularly the “<a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Obligations">Licensing Obligations of Working Group Participants</a>”
+			see particularly the “<a href="https://www.w3.org/policies/patent-policy/#sec-Obligations">Licensing Obligations of Working Group Participants</a>”
 			and the patent claim exclusion process
-			in “<a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">Exclusion From W3C RF Licensing Requirements</a>”.
+			in “<a href="https://www.w3.org/policies/patent-policy/#sec-Exclusion">Exclusion From W3C RF Licensing Requirements</a>”.
 
 
 		<dt>
@@ -3359,7 +3359,7 @@ Maturity Stages on the Recommendation Track</h4>
 					A [=Candidate Recommendation Draft=]
 					<em>does not</em> provide an exclusion opportunity;
 					instead, it is considered a [=Working Draft=]
-					for the purpose of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [[PATENT-POLICY]].
+					for the purpose of the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> [[PATENT-POLICY]].
 			</dl>
 
 			A <dfn>Rescinded Candidate Recommendation</dfn>
@@ -5605,13 +5605,13 @@ Changes</h2>
 	<em>This section is non-normative.</em>
 
 <h3 id=changes-2024 class=no-num>
-Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November 2023 Process</a></h3>
+Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></h3>
 
-	<p>This document is based on the <a href="https://www.w3.org/2023/Process-20231103/">3 November 2023 Process</a>.
-	A <a href="https://github.com/w3c/w3process/issues?q=milestone%3A%22Process+2024%22+is%3Aclosed">list of issues addressed</a>,
+	<p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
+	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%22+is%3Aclosed">list of issues addressed</a>,
 	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2F">diff from Process 2023 to this latest version</a>,
 	as well as
-	a <a href="https://github.com/w3c/w3process/compare/p2023_1...main">detailed log of all changes since then</a>
+	a <a href="https://github.com/w3c/process/compare/p2023_1...main">detailed log of all changes since then</a>
 	are available.
 
 	In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:
@@ -5619,32 +5619,32 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 	<ul>
 		<li>
 			Council dismissal vote counts must be reported.
-			(See <a href="https://github.com/w3c/w3process/issues/748">Issue 748</a>)
+			(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)
 
 		<li>
 			Exclude TAG/AB from voting on their own decisions/proposals.
-			(See <a href="https://github.com/w3c/w3process/issues/749">Issue 749</a>)
+			(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)
 
 		<li>
 			Add a requirement to make progress on external issues for update requests
-			(See <a href="https://github.com/w3c/w3process/issues/781">Issue 781</a>)
+			(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>)
 
 		<li>
 			Enable Team to replace defunct registry custodians when no-one else can.
-			(See <a href="https://github.com/w3c/w3process/issues/699">Issue 699</a>)
+			(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>)
 
 		<li>
 			Stop citing the superseded TAG charter.
-			(See <a href="https://github.com/w3c/w3process/issues/794">Issue 794</a>)
+			(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)
 
 		<li>
 			Rename “registry sections” to [=embedded registries=]
 			to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
-			(See <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
+			(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
 
 		<li>
 			Put constraints on the timing of making Formal Objections public.
-			(See <a href="https://github.com/w3c/w3process/issues/735">Issue 735</a>)
+			(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
 
 		<li>
 
@@ -5652,40 +5652,45 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 			and "Draft Registry" into "Registry Draft"
 			to be consistent with other statuses that uses the word "Draft",
 			and to make that word stand out more.
-			(See <a href="https://github.com/w3c/w3process/issues/779">Issue 779</a>)
+			(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>)
 
 		<li>
-			Clarify the definition of a Registry (see <a href="https://github.com/w3c/w3process/issues/800">Issue 800</a>)
-			and of Recommendation Track Documents (see <a href="https://github.com/w3c/w3process/pull/831">Pull Request 831</a>).
+			Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
+			and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>).
 
 		<li>
 			Clarify how the outcome of certain ballots are determined.
-			(See <a href="https://github.com/w3c/w3process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/w3process/pull/838">Issue 838</a>)
+			(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)
 
 		<li>
 			Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.
 			This change, while moderate in size, is purely editorial.
-			(See <a href="https://github.com/w3c/w3process/pull/850">Pull Request 850</a>)
+			(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>)
 
 		<li id="streamlined-update">
-			Retire “<a href="https://www.w3.org/2023/Process-20231103/#streamlined-update">Streamlined Publication Approval</a>”.
+			Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
 			This was meant to enable REC track publication with fewer/faster approval steps
 			when some stricter than usual criteria were fulfilled.
 			However, regular REC track publication have improved enough
 			that this became unnecessary,
 			and nobody was using it.
-			(See <a href="https://github.com/w3c/w3process/issues/856">Issue 856</a>)
+			(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>)
 
 		<li>
 			Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a>
 			the various parts of the Process
 			that described whether and how the Team can maintain technical reports
 			that no longer have a Group chartered to maintain them.
-			(See <a href="https://github.com/w3c/w3process/pull/860">Pull Request 860</a>)
+			(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
 
 		<li>
 			Require Chairs to be listed in Charters.
-			(See <a href="https://github.com/w3c/w3process/issues/823">Issue 823</a>)
+			(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
+
+		<li>
+			The URL of this document was changed
+			from /Consortium/Process/ to /policies/process/
+			for better integration in the W3C website architecture.
 	</ul>
 
 
@@ -5693,7 +5698,7 @@ Changes since the <a href="https://www.w3.org/2023/Process-20231103/">3 November
 Changes since earlier versions</h3>
 
 	Changes since earlier versions of the Process are detailed
-	in the <a href="https://www.w3.org/2023/Process-20231103/#changes">changes section of the previous version</a>
+	in the <a href="https://www.w3.org/policies/process/20231103/#changes">changes section of the previous version</a>
 	of the Process.
 
 <pre class=biblio>
@@ -5784,7 +5789,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"PATENT-POLICY": {
-		"href": "https://www.w3.org/Consortium/Patent-Policy/",
+		"href": "https://www.w3.org/policies/patent-policy/",
 		"title": "The W3C Patent Policy",
 		"publisher": "W3C"
 	},
@@ -5794,7 +5799,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"PATENT-POLICY-2020": {
-		"href": " https://www.w3.org/Consortium/Patent-Policy-20200915/",
+		"href": "https://www.w3.org/policies/patent-policy/20200915/",
 		"title": "The W3C 2020 Patent Policy",
 		"publisher": "W3C"
 	},

From 538646fc904e9333a180fe1f0f25859057fd9006 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 18 Jun 2024 21:42:04 +0900
Subject: [PATCH 075/237] Update URLs (follow up)

---
 CONTRIBUTING.md | 8 ++++----
 README.md       | 8 ++++----
 compile.sh      | 2 +-
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c4f4a5a5..c74c50b8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,5 +1,5 @@
 # Contributing to the W3C Process Document
-Thank-you for offering to contribute to the [W3C Process Document](https://www.w3.org/Consortium/Process/). Here we provide some details on how you can contribute. 
+Thank-you for offering to contribute to the [W3C Process Document](https://www.w3.org/policies/process/). Here we provide some details on how you can contribute. 
 
 Changes to the process document tend to fall into a few classes, and how the W3C handles these varies. Simple editorial changes may require little review, but more substantial changes will require a more substantial review and discussions by the W3C community. Please read the material below, and get involved as explained. 
 
@@ -11,7 +11,7 @@ For simple editorial changes, please feel free to raise a `pull request` or [rai
 Some changes may appear simple but may actually be more complicated than they appear. Don't worry - please continue to send your `pull request` or [raise an issue](/../../issues) and we can discuss. 
 
 ## The W3C Process Community Group
-The W3C runs a [Process Community Group](https://www.w3.org/community/w3process/), which is an open group created to manage discussions on developing the [W3C Process Document](https://www.w3.org/Consortium/Process/). Some suggestions for changes to the [W3C Process Document](https://www.w3.org/Consortium/Process/) will need to be made within the [Process Community Group](https://www.w3.org/community/w3process/), please see information below as to whether you need to take your suggestions to the group or can just raise a `pull request` or `issue`.
+The W3C runs a [Process Community Group](https://www.w3.org/community/w3process/), which is an open group created to manage discussions on developing the [W3C Process Document](https://www.w3.org/policies/process/). Some suggestions for changes to the [W3C Process Document](https://www.w3.org/policies/process/) will need to be made within the [Process Community Group](https://www.w3.org/community/w3process/), please see information below as to whether you need to take your suggestions to the group or can just raise a `pull request` or `issue`.
 
 ## Changes that Affect the Way the W3C Operates but Do Not Change the Policy
 For changes that affect the way that the W3C operates but do not change policy please do the following:
@@ -23,7 +23,7 @@ The best way to ensure your issue gets added to the [Process Community Group](ht
 
 Another way to ensure the [Process Community Group](https://www.w3.org/community/w3process/) addressed your issue is to check back on the [issues page](/../../issues) page and ask whether it has been addressed. It is more effective to join the group, but you have this option if you need it. 
 
-The [Process Community Group](https://www.w3.org/community/w3process/) will discuss your issue, and decide whether the change can be made or whether the issue needs to be brought to the [Advisory Board](https://www.w3.org/Consortium/Process/#AB) or [Advisory Committee](https://www.w3.org/Consortium/Process/#AC) for discussion; see the next section for more information on this process.
+The [Process Community Group](https://www.w3.org/community/w3process/) will discuss your issue, and decide whether the change can be made or whether the issue needs to be brought to the [Advisory Board](https://www.w3.org/policies/process/#AB) or [Advisory Committee](https://www.w3.org/policies/process/#AC) for discussion; see the next section for more information on this process.
 
 If the [Process Community Group](https://www.w3.org/community/w3process/) agrees the issue does not change the policy and agrees to make the changes detailed in your issue, you may either raise a `pull request` or wait for the Editor to make the required changes. Note: raising a `pull request` **will** be faster. See more details about `pull requests` below.
 
@@ -32,7 +32,7 @@ For changes that represent a change of policy in the W3C, the idea will need to
 
 You can raise the issue with the [Process Community Group](https://www.w3.org/community/w3process/), and you can suggest (or they will notice) that it needs policy discussion and refer it onwards. But you may prefer to initiate that discussion yourself.
 
-Getting something in front of both the [Advisory Board](https://www.w3.org/Consortium/Process/#AB) or [Advisory Committee](https://www.w3.org/Consortium/Process/#AC) can be tricky. If your organisation is a W3C member please let your Advisory Committee member know; they will then be able to email the Advisory Committee or bring the issue up at an Advisory Committee meeting. To reach the [Advisory Board](https://www.w3.org/2002/ab/) you can [raise an issue](/../../issues) on this repo (at least two AB members monitor this repo) or send an email to ab@w3.org.
+Getting something in front of both the [Advisory Board](https://www.w3.org/policies/process/#AB) or [Advisory Committee](https://www.w3.org/policies/process/#AC) can be tricky. If your organisation is a W3C member please let your Advisory Committee member know; they will then be able to email the Advisory Committee or bring the issue up at an Advisory Committee meeting. To reach the [Advisory Board](https://www.w3.org/2002/ab/) you can [raise an issue](/../../issues) on this repo (at least two AB members monitor this repo) or send an email to ab@w3.org.
 
 Gaining consensus from the [Advisory Board](https://www.w3.org/2002/ab/) or [Advisory Committee](https://www.w3.org/participate/meetings) will take some time. After consensus has been reached you may either raise a `pull request` which include the changes agreed by these committees or wait for the Editor to make the required changes. See more details about `pull requests` below.
 
diff --git a/README.md b/README.md
index a2ea3577..a33726f4 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
 # W3C Process Document repository
 
 
-This repository is for the editor's draft of the [World Wide Web Consortium Process Document](https://www.w3.org/Consortium/Process/).
+This repository is for the editor's draft of the [World Wide Web Consortium Process Document](https://www.w3.org/policies/process/).
 
 The Process document is updated most years by the W3C.
 Discussion happens in the context of the W3C Process Community Group
@@ -10,13 +10,13 @@ Discussion happens in the context of the W3C Process Community Group
 ----
 ## Branches under development
 
-[main](https://github.com/w3c/w3process/tree/main) branch (current draft of the CG):
-[Preview](https://www.w3.org/Consortium/Process/Drafts/)
+[main](https://github.com/w3c/process/tree/main) branch (current draft of the CG):
+[Preview](https://www.w3.org/policies/process/drafts/)
 
 ----
 ## Useful searches
 
-[PRs triaged into P2021](https://github.com/w3c/w3process/issues?q=is%3Aopen+-label%3A%22P2021%3A+Priority%22+milestone%3A%22Process+2021%22+) which are not priorities.
+[PRs triaged into P2021](https://github.com/w3c/process/issues?q=is%3Aopen+-label%3A%22P2021%3A+Priority%22+milestone%3A%22Process+2021%22+) which are not priorities.
 
 
 ----
diff --git a/compile.sh b/compile.sh
index a09f04d1..d10c49f4 100755
--- a/compile.sh
+++ b/compile.sh
@@ -13,7 +13,7 @@ if [ $1 ] ; then
 		--md-status-text="<details class=annoying-warning open><summary>This is not the latest Editor’s Draft of the W3C Process.</summary>\
 			<p>This is the “$1” topic branch; make sure this is indeed the one you’re looking for.\
 			If not, the current Editor’s Draft can be found at\
-			<a href='https://www.w3.org/Consortium/Process/Drafts/'>https://www.w3.org/Consortium/Process/Drafts/</a>.<br>\
+			<a href='https://www.w3.org/policies/process/drafts/'>https://www.w3.org/policies/process/drafts/</a>.<br>\
 			(The <a href=#sotd>Status of this document</a> section may have information about the purpose of this branch.)</details>"
 else
 	bikeshed --print=plain -f spec

From 0fbfa938a7cf4293362b0392fddffdafc54d071f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 11 Jul 2024 00:23:47 +0900
Subject: [PATCH 076/237] Shift most discussion of Workshops to /Guide (#876)

This consolidates the rules about Group meetings with those about Workshop and
Symposia, and delegates other discussion and description of Workshops to
/Guide.

This makes it clear that rules about minute taking or meeting recording
apply to Workshops as well as Group meetings, regroups rules about
advance notice on meetings to a single place, and shortens the Process
by focusing it on enforceable rules, while letting /Guide provide more
elaborate description and non-binding guidance.

See #419
---
 index.bs | 56 +++++++++++++-------------------------------------------
 1 file changed, 13 insertions(+), 43 deletions(-)

diff --git a/index.bs b/index.bs
index 11e5dc79..8d450fd2 100644
--- a/index.bs
+++ b/index.bs
@@ -287,7 +287,13 @@ Rights of Members</h4>
 			In <a href="#GAGeneral">Working Groups and Interest Groups</a>.
 
 		<li>
-			In <a href="#GAEvents">Workshops and Symposia</a>;
+			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>.
@@ -519,10 +525,12 @@ Individuals Representing a Member Organization</h5>
 	the number of individuals representing a W3C Member
 	(or group of <a href="#MemberRelated">related Members</a>).
 
-<h4 id="GeneralMeetings">
+<h4 id="GeneralMeetings" oldids="GAEvents, EventsS">
 Meetings</h4>
 
-	The requirements in this section apply to the official meetings of any [=W3C group=].
+	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>
 
@@ -589,6 +597,8 @@ Meeting Scheduling and Announcements</h5>
 	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>
@@ -4991,46 +5001,6 @@ Changing Confidentiality Level</h3>
 			and without attribution to the original author.
 	</ol>
 
-<h2 id="GAEvents">
-Workshops and Symposia</h2>
-
-	The Team organizes <dfn id="EventsW" export>Workshops</dfn>
-	and <dfn id="EventsS" export lt="Symposium | Symposia">Symposia</dfn>
-	to promote early involvement in the development of W3C activities
-	from Members and the public.
-
-	The goal of a Workshop 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.
-	Organizers of the first type of Workshop
-	<em class="rfc2119">may</em> solicit position papers for the Workshop program
-	and <em class="rfc2119">may</em> use those papers
-	to choose attendees and/or presenters.
-
-	The goal of a Symposium is usually
-	to educate interested parties about a particular subject.
-
-	The Call for Participation in a Workshop or Symposium
-	<em class="rfc2119">may</em> indicate participation requirements or limits,
-	and expected deliverables
-	(e.g., reports and [=minutes=]).
-	Organization of an event does not guarantee
-	further investment by W3C in a particular topic,
-	but <em class="rfc2119">may</em> lead to proposals for new activities or groups.
-
-	Workshops and Symposia generally last one to three days.
-	If a Workshop is being organized to address the pressing concerns of Members,
-	the Team <em class="rfc2119">must</em> issue the Call for Participation
-	no later than <span class="time-interval">six weeks</span>
-	prior to the Workshop's scheduled start date.
-	For other Workshops and Symposia,
-	the Team <em class="rfc2119">must</em> issue a Call for Participation
-	no later than <span class="time-interval">eight weeks</span>
-	prior to the meeting's scheduled start date.
-	This helps ensure that speakers and authors
-	have adequate time to prepare position papers and talks.
-
 <h2 id="Liaisons">
 Liaisons</h2>
 

From db2cbb7d4ddb0d51b1b88ba94574059c9a9b991b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 11 Jul 2024 00:29:47 +0900
Subject: [PATCH 077/237] Update changelog

---
 index.bs | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/index.bs b/index.bs
index 8d450fd2..2ceee742 100644
--- a/index.bs
+++ b/index.bs
@@ -5661,6 +5661,11 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 			The URL of this document was changed
 			from /Consortium/Process/ to /policies/process/
 			for better integration in the W3C website architecture.
+
+		<li>
+			Shift most of the informative discussion about Workshops to [[GUIDE]],
+			and reorganize the remaining normative requirements.
+			(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
 	</ul>
 
 

From 3fdc15aa42cbee3f464335122ed521a1b778c5fa Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 11 Jul 2024 00:33:17 +0900
Subject: [PATCH 078/237] Relax the criteria for short-circuit (#885)

A high bar for support remains needed, and any dissent remains sufficient to
defeat the short-circuit proposal, but unanimity is no longer required.

See https://github.com/w3c/process/issues/852

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index 2ceee742..207cc5df 100644
--- a/index.bs
+++ b/index.bs
@@ -2463,13 +2463,20 @@ Council Participation, Dismissal, and Renunciation</h5>
 	as they can of anyone else in the W3C community.
 
 <h5 id=council-short-circuit>
-Unanimous Short Circuit</h5>
+Short Circuit</h5>
 
 
 	The full Council process <em class=rfc2119>may</em> be short-circuited if
 	the Team recommends a resolution
-	and every potential member of a Council who is not renouncing their seat
-	votes affirmatively (no abstentions) to adopt this resolution.
+	and potential members of a Council who are not renouncing their seat
+	confirm it by a vote which results in both of the following:
+	* at least 80% of them vote affirmatively to adopt this resolution
+	* none of them vote against adopting the resolution
+
+	The request for confirmation <em class=rfc2119>must</em> be open for a period of at least two weeks,
+	or until every potential member of the Council not renouncing their seat
+	has voted,
+	whichever is shortest.
 
 	This step <em class=rfc2119>may</em> be run concurrently with [[#council-participation]]
 	and prior to choosing a [=W3C Council Chair|Chair=].

From 779ca5e277da69ea15d6d31e190ef3c4a5e180cc Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 11 Jul 2024 00:36:18 +0900
Subject: [PATCH 079/237] Update changelog

---
 index.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.bs b/index.bs
index 207cc5df..de5fb6c2 100644
--- a/index.bs
+++ b/index.bs
@@ -5673,6 +5673,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 			Shift most of the informative discussion about Workshops to [[GUIDE]],
 			and reorganize the remaining normative requirements.
 			(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
+
+		<li>
+			Make the Council's short-circuit a little more flexible.
+			(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
 	</ul>
 
 

From 5a60ea5afefb2f642a715925feab93b655b3cfa3 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 11 Jul 2024 13:43:57 +0900
Subject: [PATCH 080/237] Editorial phrasing tweaks

See https://github.com/w3c/process/pull/878/files#r1623157565
---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index de5fb6c2..2d9483c5 100644
--- a/index.bs
+++ b/index.bs
@@ -4097,11 +4097,11 @@ Revising a Recommendation: Substantive Changes</h5>
 <h5 id="revised-rec-features">
 Revising a Recommendation: New Features</h5>
 
-	For [=Recommendations=] explicitly identified as  [=allow new features|allowing new features=],
+	For [=Recommendations=] explicitly identified as [=allow new features|allowing new features=],
 	tentative new features (see <a href="#correction-classes">class 4 changes</a>)
 	<em class=rfc2119>may</em> be annotated in as [=candidate additions=],
 	and <a href="#correction-classes">class 4 changes</a> may be normatively incorporated
-	as for <a href="#correction-classes">class 3 changes</a> in [[#revised-rec-substantive]].
+	in the same fashion as <a href="#correction-classes">class 3 changes</a> in [[#revised-rec-substantive]].
 
 	Note: Limiting the addition of new features to [=Recommendations=] that explicitly allow them
 	enables third parties to depend on a stable feature-set for [=Recommendations=] that do not advertise that ability,

From 6f6b9544178c3dc9cce0eb979a1a42be42d2042e Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 24 Jul 2024 14:30:13 +0200
Subject: [PATCH 081/237] Phrasing adjustement

Closes #899
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 2d9483c5..a43387e8 100644
--- a/index.bs
+++ b/index.bs
@@ -4099,7 +4099,7 @@ Revising a Recommendation: New Features</h5>
 
 	For [=Recommendations=] explicitly identified as [=allow new features|allowing new features=],
 	tentative new features (see <a href="#correction-classes">class 4 changes</a>)
-	<em class=rfc2119>may</em> be annotated in as [=candidate additions=],
+	<em class=rfc2119>may</em> be added as [=candidate additions=] in annotations,
 	and <a href="#correction-classes">class 4 changes</a> may be normatively incorporated
 	in the same fashion as <a href="#correction-classes">class 3 changes</a> in [[#revised-rec-substantive]].
 

From b6c34297a21349ed77427bd1c089f804f09354b0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 24 Jul 2024 08:47:50 -0700
Subject: [PATCH 082/237] Introduce a formal Charter Refinement phase (#851)

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 100 +++++++++++++++++++++++++++++++++++++++++++++----------
 1 file changed, 83 insertions(+), 17 deletions(-)

diff --git a/index.bs b/index.bs
index a43387e8..7d1724ed 100644
--- a/index.bs
+++ b/index.bs
@@ -1708,22 +1708,80 @@ Team Representative in an Interest Group</h5>
 <h2 id=group-lifecyle>
 Lifecycle of Chartered Groups</h2>
 
-<h3 id="WGCharterDevelopment">
-Initiating Charter Development</h3>
-
-	W3C creates charters for [=chartered groups=]
-	based on interest from the Members and Team.
-	The Team <em class="rfc2119">must</em> notify the Advisory Committee
-	when a charter for a new Working Group or Interest Group is in development.
-	This is intended to raise awareness,
-	even if no formal proposal is yet available.
-	Advisory Committee representatives <em class="rfc2119">may</em> provide
-	feedback on the <a href="#ACCommunication">Advisory Committee discussion list</a>
-	or via other designated channels.
-
-	W3C <em class="rfc2119">may</em> begin work
-	on a Working Group or Interest Group charter
-	at any time.
+	W3C creates [=charters=] for [=chartered groups=] based on interest from the [=Members=] and [=Team=].
+	[=Charters=] are formally approved through an [=AC Review=] and [=W3C Decision=] (see [[#CharterReview]]).
+	Prior to [=AC Review=],
+	<dfn>charter drafts</dfn> go through a public [=charter refinement=] phase
+	during which the [=charter=] receives [=wide review=]
+	and the [=Chartering Facilitator=] attempts to find [=consensus=] on the charter.
+	The [=Team=] <em class=rfc2119>may</em> send notice to the [=AC=]
+	when starting development of a new charter prior to the [=charter refinement=] phase.
+
+<h3 id="charter-initiation">
+Initiating Charter Refinement</h3>
+
+	Formal [=charter refinement=] (see below) is initiated
+	by the [=Team=] sending a [=charter review notice=]
+	to the [=Advisory Committee=],
+	to the public,
+	and, in the case of rechartering, to the affected [=Group=].
+
+	This <dfn>charter review notice</dfn> must include:
+	* A short summary of the proposal.
+	* The location of the [=charter draft=], which must be public.
+	* How to participate in the discussion of this [=charter draft=] and where to file issues.
+	* The expected duration of the [=charter refinement=] phase,
+		which must not be less than 28 days,
+		and should not be more than 6 months.
+	* Who the [=Chartering Facilitator=] is.
+
+	The [=Team=] is responsible for initiating [=charter refinement=]
+	at its discretion, in consideration of discussions with the community.
+	An [=Advisory Committee representative=] <em class=rfc2119>may</em> formally request
+	that the [=Team=] initiate [=charter refinement=].
+	The Team <em class=rfc2119>may</em> deny such a request
+	if it thinks the proposal is insufficiently mature or does not align with W3C's scope and mission.
+	This rejection is a [=Team Decision=] which can be <a href="#registering-objections">Formally Objected to</a>.
+
+<h3 id="charter-development" oldids="WGCharterDevelopment">
+Charter Refinement</h3>
+
+	During <dfn>charter refinement</dfn>,
+	the W3C community further develops the [=charter draft=]
+	with the goal of achieving [=consensus=] on the proposal.
+	The <dfn>Chartering Facilitator</dfn>
+	acts as [=Chair=] for the [=charter refinement=] process.
+
+	Note: The [=Chartering Facilitator=] is not necessarily (and often is not) the [=Chair=] of the [=chartered group|group=] being chartered.
+
+	During [=charter refinement=]:
+	* All issues filed against the [=charter draft=] must be [=formally addressed=],
+		and their resolutions tracked in a disposition of comments.
+	* [=Wide review=] of the [=charter draft=] is initiated and completed.
+	* Decisions are made as [=group decisions=], where the group is made up of all individuals participating in this process,
+		(though only W3C [=Members=] and the [=Team=] can participate in any formal [[#Votes|vote]]).
+
+	The [=charter refinement=] phase concludes when there is either:
+	* A [=group decision=] to initiate [=AC Review=] of the [=charter draft=].
+	* A [=chair decision=] to abandon the proposal.
+
+	Any [=Formal Objection=] filed during the  [=charter refinement=] phase--
+	other than an objection to the choice of [=Chartering Facilitator=]
+	or to a decision to abandon the proposal--
+	is not considered [[#registering-objections|registered]]
+	until the close of the [=Advisory Committee Review=] of the charter,
+	and is registered against that [=W3C Decision=].
+
+	Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together,
+	while allowing [=Formal Objections=] to [=Chartering Facilitator=] misbehavior
+	that the [=Team=] is failing to address
+	to be processed immediately.
+
+	If the discussions have not concluded within the time frame announced in the [=charter review notice=],
+	the [=Chartering Facilitator=] must inform the AC
+	(and, in the case of rechartering, the affected [=Group=])
+	of this delay, of the status of the discussions, and of the revised expected duration of [=Charter Refinement=].
+	This report should be public.
 
 <h3 id="WGCharter">
 Content of a Charter</h3>
@@ -1899,18 +1957,26 @@ New Charters and Major Changes</h4>
 	(e.g., regarding deliverables or resource allocation)
 	and include rationale for the changes.
 
+	The Call for Review of a new or substantively modified charter
+	<em class="rfc2119">must</em> include a disposition of comments for those received during the [=charter refinement=] process,
+	highlighting any issues that were closed despite sustained objections.
+
 <h4 id="charter-minor-changes">
 Minor Changes to Active Charters</h4>
 
 	Substantive changes to a [=charter=] (including [[#charter-extension|extensions]])
 	that do not affect the way the group functions in any significant way
 	<em class=rfc2119>may</em> be approved by a [=Team Decision=],
-	in which case they do not require an [=Advisory Committee Review=].
+	in which case they do not require [=charter refinement=] nor [=Advisory Committee Review=].
 	The following are examples of such changes:
 	the addition of an in-scope deliverable,
 	a change of [=Team Contact=],
 	or a change of [=Chair=].
 
+	The [=Team=] <em class=rfc2119>may</em> nevertheless choose
+	initial [=charter refinement=] and/or [=Advisory Committee Review=]
+	when it thinks the changes would benefit from more scrutiny or explicit buy-in.
+
 	Though [=Advisory Committee Review=] is not required,
 	such changes <em class=rfc2119>must</em> still be announced
 	to the [=Advisory Committee=],

From 5f226588d33b02fb900ca87f2127f68ed6231e62 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 24 Jul 2024 17:49:26 +0200
Subject: [PATCH 083/237] Update Changelog

---
 index.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.bs b/index.bs
index 7d1724ed..177043d0 100644
--- a/index.bs
+++ b/index.bs
@@ -5743,6 +5743,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 		<li>
 			Make the Council's short-circuit a little more flexible.
 			(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
+
+		<li>
+			Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
+			(See <a href="https://github.com/w3c/process/issues/850">Issue 850</a>)
 	</ul>
 
 

From 15bcbf06fdb3b175927b71db559b1679c533ee00 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 24 Jul 2024 17:50:10 +0200
Subject: [PATCH 084/237] Fix typo in changelog

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 177043d0..29d9e8cb 100644
--- a/index.bs
+++ b/index.bs
@@ -5746,7 +5746,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 
 		<li>
 			Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
-			(See <a href="https://github.com/w3c/process/issues/850">Issue 850</a>)
+			(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>)
 	</ul>
 
 

From 93f24a8d0198ab267f0152fe886f0e5c5763c3bb Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 24 Jul 2024 08:54:20 -0700
Subject: [PATCH 085/237] Set up progressive vote threshold depending on
 participation (#901)

This mirrors the "requisite member vote" process from the W3C bylaws,
and avoids making momentous decisions based on a slim majority in vote
with low participation. Also includes a minimum quorum.

See https://www.w3.org/2024/07/15-ab-minutes.html#r02

See https://github.com/w3c/process/issues/886

Co-authored-by: Chris Needham <chrisn@users.noreply.github.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 29d9e8cb..60a5cade 100644
--- a/index.bs
+++ b/index.bs
@@ -2866,8 +2866,23 @@ Appeal by Advisory Committee Representatives</h3>
 	and “Abstain”,
 	together with Comments.
 
-	If the number of votes to reject
-	exceeds the number of votes to approve,
+	The level of support needed for an [=Advisory Committee Override=] to pass
+	depends on the level of ballot participation 
+	(including explicit “abstain” ballots) 
+	by [=Advisory Committee Representatives=]:
+	* if fewer than 5% participate,
+		the vote fails.
+	* if at least 5% but no more than 15% participate,
+		and the number of “Approve” ballots exceeds three times (3x) the number of “Reject” ballots,
+		the vote passes.
+	* if more than 15% but fewer than 20% participate,
+		and the number of “Approve” ballots exceeds twice (2x) the number of “Reject” ballots,
+		the vote passes.
+	* if 20% or more participate,
+		and the number of “Approve” ballots exceeds the number of “Reject” ballots,
+		the vote passes.
+
+	If the vote passes,
 	the decision is overturned.
 	In that case, there are the following possible next steps:
 

From c0e2edc485d09affe575a7de0766d92ede9a4e43 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 24 Jul 2024 17:57:03 +0200
Subject: [PATCH 086/237] Update Changelog

---
 index.bs | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/index.bs b/index.bs
index 60a5cade..f1fdf5de 100644
--- a/index.bs
+++ b/index.bs
@@ -5762,6 +5762,12 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 		<li>
 			Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
 			(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>)
+
+		<li>
+			Adjust AC appeal vote threshold based on participation,
+			aligning with the thresholds and super majority requirements
+			for "Requisite Member Vote" from the W3C Bylaws.
+			(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
 	</ul>
 
 

From cbffac9fa657e34bd06ff66d53e8ed85890acf7c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 30 Apr 2024 22:19:00 +0900
Subject: [PATCH 087/237] Remove the Proposed Recommendation Phase

Proposed Recommendation is only a transitional phase. Nothing stays
there: either the transition is approved and the spec goes to REC, or
it's not and it reverts to a lower maturity. The things that happen
during PR are useful, but they don't really depend on there being an
explicit phase with an explicit publication, so we can simplify things
by folding all of this into the transition from CR to REC, without a
distinct phase.

Part of https://github.com/w3c/w3process/issues/861

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
---
 index.bs | 218 +++++++++++++++++++++----------------------------------
 1 file changed, 81 insertions(+), 137 deletions(-)

diff --git a/index.bs b/index.bs
index f1fdf5de..e0ee7d17 100644
--- a/index.bs
+++ b/index.bs
@@ -729,8 +729,8 @@ Role of the Advisory Committee</h4>
 		<li>
 			<a href="#ACReview">reviewing formal proposals</a> of W3C:
 			<a href="#CharterReview">Charter Proposals</a>,
-			<a href="#RecsPR">Proposed Recommendations</a>,
-			and <a href="#GAProcess">Proposed Process Documents</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.
@@ -2785,11 +2785,16 @@ Determining the W3C Decision</h4>
 	those other conditions must also be re-fulfilled.
 
 	<div class="example">
-		For example, to make [=substantive changes=] to a [=Proposed Recommendations=],
-		the [=technical report=] could be returned to [=Candidate Recommendation=].
+		For example, if [=substantive changes=] to a [=technical report=]
+		are requested when assessing the transition from
+		[=Candidate Recommendation=] to [=Recommendation=],
+		the technical report would need to go through a new [=Update Request=]
+		and be republished as a new [=Candidate Recommendation=];
+		that new version would then need to satisfy the criteria for advancement.
 		Alternatively, the desired changes can be introduced as non-substantive amendments
 		using the process for [[#revising-rec|revising a Recommendation]].
-		However, they cannot be directly integrated between [=PR=] and [=REC=],
+		However, with the exception of the removal of at-risk features,
+		they cannot be directly integrated between [=CRS=] and [=REC=],
 		because that would fail to trigger a patent exclusion opportunity.
 	</div>
 
@@ -3327,12 +3332,11 @@ The W3C Recommendation Track</h3>
 		<li>Publication of the [=First Public Working Draft=].
 		<li>Publication of zero or more revised [=Working Drafts=].
 		<li>Publication of one or more [=Candidate Recommendations=].
-		<li>Publication of a [=Proposed Recommendation=].
 		<li>Publication as a [=W3C Recommendation=].
 	</ol>
 
 	A <dfn export lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document">W3C Recommendation Track document</dfn>
-	is any document whose current status is one of the five in the numbered list above.
+	is any document whose current status is one of the four in the numbered list above.
 
 	<div role="region" aria-label="Basic W3C Recommendation Track">
 		<pre class=include-raw>
@@ -3471,20 +3475,6 @@ Maturity Stages on the Recommendation Track</h4>
 			in the W3C Patent Policy [[!PATENT-POLICY]]
 			for implication on patent licensing obligations.
 
-		<dt>
-			<dfn export id="RecsPR" lt="W3C Proposed Recommendation | Proposed Recommendation | PR">Proposed Recommendation</dfn> (<abbr>PR</abbr>)
-		<dd>
-			A Proposed Recommendation is a document
-			that has been accepted by W3C
-			as of sufficient quality to become a [=W3C Recommendation=].
-			This phase triggers formal review by the [=Advisory Committee=],
-			who <em class="rfc2119">may</em> recommend
-			that the document be [=published=] as a [=W3C Recommendation=],
-			returned to the [=Working Group=] for further work,
-			or abandoned.
-			[=Substantive changes=] <em class="rfc2119">must not</em> be made to a [=Proposed Recommendation=]
-			except by [=publishing=] a new [=Working Draft=] or [=Candidate Recommendation=].
-
 		<dt>
 			<dfn id="RecsW3C" export lt="W3C Recommendation | Recommendation | REC">W3C Recommendation</dfn> (<abbr>REC</abbr>)
 		<dd>
@@ -3498,6 +3488,20 @@ Maturity Stages on the Recommendation Track</h4>
 			The W3C Royalty-Free IPR licenses
 			granted under the W3C Patent Policy [[PATENT-POLICY]]
 			apply to [=W3C Recommendations=].
+
+			<p id="expandable-rec">
+			After its initial publication,
+			a [=W3C Recommendation=] <em class=rfc2119>may</em> be [[#revising-rec|revised]]
+			to address [=editorial change|editorial=] or [=substantive change|substantive=] issues
+			that are discovered later.
+			However, <a href=#class-4>new features</a> can only be added
+			if the document already identifies itself
+			as intending to <dfn>allow new features</dfn>.
+			Such an allowance cannot be added
+			to a [=technical report=] previously published as a [=Recommendation=]
+			that did not allow such changes;
+			this requires a new [=technical report=], that could, for example, be similarly named but with an incremented version number.
+
 			As technology evolves,
 			a [=W3C Recommendation=] may become:
 			<dl>
@@ -3668,7 +3672,7 @@ Advancement on the Recommendation Track</h4>
 	so many requirements do not apply,
 	and verification is normally fairly straightforward.
 	For later stages,
-	especially transition to [=Candidate Recommendation|Candidate=] or [=Proposed Recommendation=],
+	especially transitions to [=Candidate Recommendation|Candidate=] or [=Recommendation=],
 	there is usually a formal review meeting
 	to verify that the requirements have been met.
 
@@ -3849,8 +3853,8 @@ Transitioning to Candidate Recommendation</h4>
 		<li>
 			<em class="rfc2119">may</em> identify features in the document as <dfn export>at risk</dfn>.
 			These features <em class="rfc2119">may</em> be removed
-			before advancement to [=Proposed Recommendation=]
-			without a requirement to publish a new [=Candidate Recommendation=].
+			before advancement to [=Recommendation=]
+			without requiring an [=Update Request=].
 	</ul>
 
 	The first Candidate Recommendation publication
@@ -3867,7 +3871,7 @@ Transitioning to Candidate Recommendation</h4>
 		<li>Return to <a href="#revising-wd">Working Draft</a></li>
 		<li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a></li>
 		<li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a></li>
-		<li><a href="#transition-pr">Proposed Recommendation</a></li>
+		<li><a href="#transition-pr">Recommendation</a></li>
 		<li><a href="#abandon-draft">Discontinued Draft</a></li>
 	</ul>
 
@@ -3897,8 +3901,8 @@ Publishing a [=Candidate Recommendation Snapshot=]</h5>
 		<li>
 			<em class="rfc2119">may</em> identify features in the document as [=at risk=].
 			These features <em class="rfc2119">may</em> be removed
-			before advancement to [=Proposed Recommendation=]
-			without a requirement to publish a new [=Candidate Recommendation=].
+			before advancement to [=Recommendation=]
+			without requiring an [=Update Request=].
 	</ul>
 
 	The [=Team=] <em class="rfc2119">must</em> announce
@@ -3972,45 +3976,44 @@ Publishing a [=Candidate Recommendation Draft=]</h5>
 		<li>Return to <a href="#revising-wd">Working Draft</a></li>
 		<li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a></li>
 		<li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a></li>
-		<li><a href="#transition-pr">Proposed Recommendation</a>,
+		<li><a href="#transition-pr">Recommendation</a>,
 		if there are no [=substantive change=] other than dropping [=at risk=] features</li>
 		<li><a href="#abandon-draft">Discontinued Draft</a></li>
 	</ul>
 
+<h4 id="transition-rec" oldids="rec-publication, rec-pr, transition-pr, RecsPR">
+Transitioning to Recommendation</h4>
 
-<h4 id=transition-pr oldids="rec-pr">
-Transitioning to Proposed Recommendation</h4>
+	When a [=Working Group=] estimates
+	that a [=Candidate Recommendation=] has fulfilled all the relevant criteria,
+	it <em class=rfc2119>may</em> [=group decision|decide=] to request advancement to [=W3C Recommendation=].
 
 	In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,
+	the Working Group:
 
 	<ul>
 		<li>
-			The status information <em class="rfc2119">must</em> specify the deadline for [=Advisory Committee review=],
-			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days
-			after the publication of the [=Proposed Recommendation=]
-			and <em class="rfc2119">should</em> be at least 10 days
-			after the end of the last Exclusion Opportunity
-			per ”Exclusion From W3C RF Licensing Requirements”
-			in the W3C Patent Policy [[!PATENT-POLICY]].
-	</ul>
+			<em class="rfc2119">must</em> show [=adequate implementation experience=]
+			except where an exception is approved by a [=Team Decision=].
 
-	A Working Group:
+			The [=Team=] <em class="rfc2119">may</em> approve a [=Candidate Recommendation=]
+			with minimal <a href="#implementation-experience">implementation experience</a>
+			where there is a compelling reason to do so.
+			In such a case, the [=Team=] <em class="rfc2119">must</em> explain the reasons for that decision,
+			and that information <em class=rfc2119>must</em> be included in the [=Call for Review=]
+			proposing advancement to [=W3C Recommendation=].
 
-	<ul>
-		<li>
-			<em class="rfc2119">must</em> show [=adequate implementation experience=]
-			except where an exception is approved by a [=Team Decision=],
 		<li>
-			<em class="rfc2119">must</em> show that the document has received [=wide review=],
+			<em class="rfc2119">must</em> show that the document has received [=wide review=].
 
 		<li>
 			<em class="rfc2119">must</em> show that all issues
 			raised during the [=Candidate Recommendation review period=]
-			have been [=formally addressed=],
+			have been [=formally addressed=].
 
 		<li>
 			<em class="rfc2119">must </em>identify any substantive issues
-			raised since the close of the [=Candidate Recommendation review period=],
+			raised since the close of the [=Candidate Recommendation review period=].
 
 		<li>
 			<em class=rfc2119>must not</em> have made any [=substantive changes=] to the document
@@ -4021,97 +4024,43 @@ Transitioning to Proposed Recommendation</h4>
 			<em class="rfc2119">may</em> have removed features
 			identified in the [=Candidate Recommendation Snapshot=] document as [=at risk=]
 			without republishing the specification as a [=Candidate Recommendation Snapshot=].
-	</ul>
-
-	The [=Team=]:
-
-	<ul>
-		<li>
-			<em class="rfc2119">must</em> announce the publication of a [=Proposed Recommendation=]
-			to the <a href="#AC">Advisory Committee</a>,
-			and <em class="rfc2119">must</em> begin an [=Advisory Committee Review=]
-			on the question of whether the specification is appropriate to [=publish=] as a [=W3C Recommendation=].
-
-		<li>
-			<em class="rfc2119">may</em> approve a [=Proposed Recommendation=]
-			with minimal <a href="#implementation-experience">implementation experience</a>
-			where there is a compelling reason to do so.
-			In such a case, the [=Team=] <em class="rfc2119">must</em> explain the reasons for that decision,
-			and that information <em class=rfc2119>must</em> be included in the [=Call for Review=]
-			proposing advancement to [=W3C Recommendation=].
-	</ul>
-
-	Since a [=W3C Recommendation=] <em class="rfc2119">must not</em> include any [=substantive changes=]
-	from the [=Proposed Recommendation=] it is based on,
-	to make any [=substantive change=] to a [=Proposed Recommendation=]
-	the [=Working Group=] <em class="rfc2119">must</em> return the specification to [=Candidate Recommendation=]
-	or [=Working Draft=].
-
-	<p id="expandable-rec">
-	A [=Proposed Recommendation=] may identify itself
-	as intending to <dfn>allow new features</dfn>
-	(<a href="#correction-classes">class 4 changes</a>)
-	after its initial publication as a [=Recommendation=],
-	as described in [[#revised-rec-features]].
-	Such an allowance cannot be added
-	to a [=technical report=] previously published as a [=Recommendation=]
-	that did not allow such changes.
-
-	Possible Next Steps:
-
-	<ul>
-		<li>
-			Return to <a href="#revising-wd">Working Draft</a>
-
-		<li>
-			Return to <a href="#transition-cr">Candidate Recommendation</a>
-
-		<li>
-			<a href="#transition-rec">Recommendation status</a>,
-			(the expected next step).
 
 		<li>
-			<a href="#abandon-draft">Discontinued Draft</a></li>
+			<em class="rfc2119">must</em> identify, in the document, where errata are tracked.
 	</ul>
 
-	[=Advisory Committee representatives=] <em class="rfc2119">may</em> initiate an [=Advisory Committee Appeal=]
-	of the decision to advance the technical report.
+	Additionally,
+	if the document has previously been published as a [=W3C Recommendation=], the [=Working Group=]
+	<em class=rfc2119>must not</em> include any <a href="#correction-classes">class 4 change</a>
+	to that publication
+	unless it was explicitly marked as [=allowing new features=],
+	and <em class=rfc2119>must not</em> include any such marking
+	if not already present.
+
+	If all the criteria above are fulfilled,
+	the [=Team=] <em class="rfc2119">must</em> begin an [=Advisory Committee Review=]
+	on the question of whether the specification is appropriate to [=publish=] as a [=W3C Recommendation=].
+	The deadline for [=Advisory Committee review=]
+	<em class="rfc2119">must</em> allow <strong>at least</strong> 28 days,
+	and <em class="rfc2119">should</em> end at least 10 days
+	after the end of the last Exclusion Opportunity
+	per ”Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy [[!PATENT-POLICY]].
 
-<h4 id="transition-rec" oldids="rec-publication">
-Transitioning to W3C Recommendation</h4>
+	If there was any [=dissent=] in Advisory Committee reviews,
+	the [=Team=] <em class="rfc2119">must</em> publish the substantive content of the dissent
+	to W3C and the general public,
+	and <em class="rfc2119">must</em> [=formally address=] the comment
+	at least 14 days before publication as a [=W3C Recommendation=].
 
 	The decision to advance a document to [=Recommendation=]
 	is a [=W3C Decision=].
-
-	In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,
-
-	<ul>
-		<li>
-			A [=Recommendation=] <em class="rfc2119">must</em> identify where errata are tracked, and
-
-		<li>
-			A [=Recommendation=] <em class="rfc2119">must not</em> include any [=substantive changes=]
-			from the [=Proposed Recommendation=]
-			on which it is based.
-
-		<li>
-			If there was any [=dissent=] in Advisory Committee reviews,
-			the [=Team=] <em class="rfc2119">must</em> publish the substantive content of the dissent
-			to W3C and the general public,
-			and <em class="rfc2119">must</em> [=formally address=] the comment
-			at least 14 days before publication as a [=W3C Recommendation=].
-
-		<li>
-			[=Advisory Committee representatives=] <em class="rfc2119">may</em> initiate
-			an [=Advisory Committee Appeal=]
-			of the [=W3C decision=]
-
-		<li>
-			The [=Team=] <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.
-	</ul>
+	The [=Team=] <em class="rfc2119">must</em> announce the publication of a [=W3C Recommendation=]
+	to the <a href="#AC">Advisory Committee</a>,
+	to other W3C groups
+	and to the public.
+	[=Advisory Committee representatives=] <em class="rfc2119">may</em> initiate an [=Advisory Committee Appeal=]
+	of the decision to advance the technical report.
 
 	Possible next steps:
 	A [=W3C Recommendation=] normally retains its status indefinitely.
@@ -4123,6 +4072,7 @@ Transitioning to W3C Recommendation</h4>
 
 		<li>
 			republished as a <a href="#transition-cr">Candidate Recommendation</a>
+			or <a href="https://www.w3.org/2023/Process-20231103/#revising-wd">Working Draft</a>
 			to be developed towards a revised [=Recommendation=], or
 
 		<li>
@@ -4787,15 +4737,9 @@ Publishing Registries</h4>
 			<dfn export>Obsolete Registry</dfn> and <dfn export>Superseded Registry</dfn>.
 
 		<li>
-			There is no equivalent to the Proposed Recommendation phase.
-			Instead,
-			an [=Advisory Committee Review=] is started
-			upon publication of each [=Candidate Registry Snapshot=].
-
-		<li>
-			Changes that add new features (i.e. [[#correction-classes|class 4 changes]]) are allowed
+			Changes that add new features (i.e., [[#correction-classes|class 4 changes]]) are allowed
 			in all [=W3C Registries=],
-			without needing the to explicitly indicate that this is allowed.
+			without needing them to explicitly indicate that this is allowed.
 	</ul>
 
 <h4 id=reg-table-update>

From 246d1905fbb5d65eaf7c376ea3b6c7cdf4f6b365 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 1 May 2024 11:50:15 +0900
Subject: [PATCH 088/237] Update REC Track diagram to remove PR

Part of https://github.com/w3c/w3process/issues/861

Addresses https://github.com/w3c/w3process/issues/775

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 basic-rec-track.svg | 52 ++++++++++++++-------------------------------
 1 file changed, 16 insertions(+), 36 deletions(-)

diff --git a/basic-rec-track.svg b/basic-rec-track.svg
index 1a074728..1aaefbf8 100644
--- a/basic-rec-track.svg
+++ b/basic-rec-track.svg
@@ -1,4 +1,4 @@
-		<svg xmlns="http://www.w3.org/2000/svg" viewBox="-5 30 630 180" width="100%">
+		<svg xmlns="http://www.w3.org/2000/svg" viewBox="-5 30 457 175" width="100%">
 			<title>Basic W3C Recommendation Track</title>
 			<!-- basic maturity states -->
 			<g role="list">
@@ -56,7 +56,7 @@
 				</g>
 			<!-- CRS -->
 				<g role="listitem">
-					<a href="#pr-1">
+					<a href="#rec-1">
 						<ellipse role="img" id="cr-1" ry="18" rx="38" cy="140" cx="260" stroke="black" fill="#fff">
 						<title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
 						</ellipse>
@@ -90,11 +90,11 @@
 								<path stroke="#000" d="M242,124C238,114 244,104 260,104 271,104 285,108 286,117" stroke-dasharray="6 2" fill="none"></path>
 							</a>
 						</g>
-					<!-- Advance to PR -->
+					<!-- Advance to REC -->
 						<g role="listitem" fill="#060">
-						<a href="#pr-1">
+						<a href="#rec-1">
 							<g role="img">
-							<title>Advance to Proposed Recommendation</title>
+							<title>Advance to Recommendation</title>
 							</g>
 							<text x="298" y="121" font-size="8">WG Decision +</text>
 							<text x="298" y="129" font-size="8">Team Approval +</text>
@@ -158,38 +158,25 @@
 						</g>
 					</g>
 				</g>
-			<!-- PR -->
+			<!-- REC -->
 				<g role="listitem">
 					<a href="#rec-1">
-						<ellipse role="img" id="pr-1" ry="18" rx="28" cy="140" cx="413" stroke="black" fill="#fff">
-						<title>Proposed Recommendation (PR) — AC Review</title>
+						<ellipse role="img" id="rec-1" ry="18" rx="28" cy="140" cx="413" stroke="black" fill="#fff" stroke-width="2">
+						<title>Recommendation</title>
 						</ellipse>
 						<text aria-hidden="true" font-size="14" font-weight="bold"
-						      y="144" x="413" text-anchor="middle">PR</text>
-						<text area-hidden="true" font-size="6" y="150" x="413" text-anchor="middle">AC Review</text>
+						      y="144" x="413" text-anchor="middle">REC</text>
 					</a>
 					<g role="list">
-					<!-- Advance to Rec -->
-						<g role="listitem" fill="#060">
-							<a href="#rec-1">
-								<g role="img">
-									<title>Advance to Recommendation</title>
-								</g>
-								<text x="300" y="138" font-size="8">
-									<tspan x="445" y="134">W3C Decision</tspan>
-								</text>
-								<path d="M441,140h100" stroke="#060"></path>
-								<polygon points="534,136 544,140 534,144"></polygon>
-							</a>
-						</g>
 					<!-- Return to CRS -->
 						<g role="listitem" fill="#900">
 							<a href="#cr-1">
 								<g role="img">
 									<title>Return to Candidate Recommendation Snapshot</title>
 								</g>
-								<text font-size="8" text-anchor="end">
-									<tspan x="385" y="160">W3C Decision</tspan>
+								<text font-size="8" text-anchor="start">
+									<tspan x="342" y="157">WG Decision</tspan>
+									<tspan x="342" y="165" font-size="6">(or Team Decision with AB+TAG Approval)</tspan>
 								</text>
 								<path d="M301,147h88" stroke-dasharray="4 4" stroke="#900"></path>
 								<polygon points="301,145 296,147 301,149"></polygon>
@@ -201,22 +188,15 @@
 								<g role="img">
 									<title>Return to Working Draft</title>
 								</g>
-								<text font-size="8" text-anchor="end">
-									<tspan x="410" y="185">W3C Decision</tspan>
+								<text font-size="8" text-anchor="start">
+									<tspan x="342" y="157">WG Decision</tspan>
+									<tspan x="342" y="165" font-size="6">(or Team Decision with AB+TAG Approval)</tspan>
 								</text>
-								<path d="M413,158v32h-316v-26" stroke-dasharray="4 4" stroke="#900" fill="none"></path>
+								<path d="M339,147v41h-242v-26" stroke-dasharray="4 4" stroke="#900" fill="none"></path>
 								<polygon points="95,164 97,159 99,164"></polygon>
 							</a>
 						</g>
 					</g>
 				</g>
-			<!-- Rec -->
-				<g role="listitem">
-					<ellipse role="img" id="rec-1" ry="18" rx="28" cy="140" cx="573" stroke="black" fill="#fff" stroke-width="2">
-						<title>Recommendation (Rec)</title>
-					</ellipse>
-					<text aria-hidden="true" font-size="16" font-weight="bold"
-					      y="144" x="573" text-anchor="middle" stroke-width=".3">REC</text>
-				</g>
 			</g>
 		</svg>

From da510fbd76cb849bb90c59a66efc757abbac303a Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 15 Aug 2024 15:35:56 +0200
Subject: [PATCH 089/237] Update Changelog

---
 index.bs | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/index.bs b/index.bs
index e0ee7d17..88ba21b2 100644
--- a/index.bs
+++ b/index.bs
@@ -5712,6 +5712,15 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 			aligning with the thresholds and super majority requirements
 			for "Requisite Member Vote" from the W3C Bylaws.
 			(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
+
+		<li>
+			Retire the Proposed Recommendation phase of the Recommendation track.
+			It was only used as a short-lived transition
+			during which various verifications and votes about CR were done.
+			These can be done on a CR
+			without having to republish it as a separate thing.
+			This simplifies the Process without changing the actual quality or consensus expectations.
+			(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)
 	</ul>
 
 

From 7fd5a10f05155bcf17dbf3f505bb986f702555e0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 15 Aug 2024 15:37:15 +0200
Subject: [PATCH 090/237] Introduce an appendix cataloging old terminology
 (#898)

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 92 ++++++++++++++++++++++++++++++++++++++++++++++++++------
 1 file changed, 83 insertions(+), 9 deletions(-)

diff --git a/index.bs b/index.bs
index 88ba21b2..711b2cd6 100644
--- a/index.bs
+++ b/index.bs
@@ -308,7 +308,7 @@ Rights of Members</h4>
 <h4 id="RelatedAndAssociatedMembers" oldids="RelatedAndConsortiumMembers">
 Member Associations and Related Members</h4>
 
-<h5 id="MemberAssoc" oldids="fdn-member-consortium, MemberConsortia">
+<h5 id="MemberAssoc" oldids="MemberConsortia">
 Membership Associations</h5>
 
 	A “<dfn lt="Member Association | Member Associations">Member Association</dfn>” means a consortium,
@@ -1901,7 +1901,7 @@ Content of a Charter</h3>
 		<li>
 			The stable URL of the Working Group charter
 			under which the Exclusion Draft was published
-			(labeled the “<dfn export id=exclusion-draft-charter oldids="other-charter">Exclusion Draft Charter</dfn>”).
+			(labeled the “<dfn export id=exclusion-draft-charter>Exclusion Draft Charter</dfn>”).
 	</ul>
 
 	All of the above data <em class=rfc2119>must</em> be identified
@@ -3358,7 +3358,7 @@ The W3C Recommendation Track</h3>
 	if it determines that the requirements for advancement
 	have not been met.
 
-<h4 id="maturity-stages" oldids="maturity-levels">
+<h4 id="maturity-stages">
 Maturity Stages on the Recommendation Track</h4>
 
 	<dl>
@@ -3821,7 +3821,7 @@ Revising a Working Draft</h4>
 		<li><a href="#abandon-draft">Discontinued Draft</a></li>
 	</ul>
 
-<h4 id="transition-cr" oldids="candidate-rec, last-call">
+<h4 id="transition-cr" oldids="candidate-rec">
 Transitioning to Candidate Recommendation</h4>
 
 	To publish a [=Candidate Recommendation=],
@@ -5058,7 +5058,7 @@ Liaisons</h2>
 	[=technical agreements=] with another organization.
 	For purposes of the W3C Process,
 	a <dfn local-lt="agreement">technical agreement</dfn> is a formal contract,
-	or a Memorandum of Understanding (<abbr id=mou>MoU</abbr>),
+	or a Memorandum of Understanding (<abbr>MoU</abbr>),
 	or a similar document,
 	between W3C and another party or parties,
 	that relates to the technical activity of the Consortium
@@ -5450,8 +5450,82 @@ Process Evolution</h2>
 	the [[COC|Code of Conduct]] in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
 	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.
 
-<h2 id="acks" class=non-normative>
-Acknowledgments</h2>
+<h2 id="old-terms" class="non-normative nonum">
+Appendix A: Retired Terminology</h2>
+
+	<em>This section is non-normative.</em>
+
+	Previous versions of this process defined and used various concepts and document statuses
+	that have since been retired or renamed.
+	For ease of reference,
+	this appendix lists the more notable ones,
+	and it links to the the definition or relevant section
+	in the most recent version of the Process that used them,
+	and gives the more recent equivalent term when there is one.
+
+	<dl>
+		<dt>
+			<dfn noexport id=rec-amended>Amended Recommendation</dfn>
+			(retired term)
+		<dd>
+			Last defined <a href="https://www.w3.org/2020/Process-20200915/#rec-amended">in section 6.2.1 of the 2020 Process</a>.
+
+		<dt>
+			<dfn noexport>Edited Recommendation</dfn>
+			(retired term)
+		<dd>
+			Last defined <a href="https://www.w3.org/2019/Process-20190301/#maturity-levels">in section 6.1.2 of the 2019 Process</a>.
+
+		<dt>
+			<dfn noexport id=last-call>Last Call</dfn>
+			(retired term)
+		<dd>
+			Last defined <a href="https://www.w3.org/2005/10/Process-20051014/tr.html#last-call">in section 7.4.2 of the 2005 Process</a>.
+
+		<dt>
+			<dfn noexport id=maturity-levels>Maturity level</dfn>
+			(renamed term)
+		<dd>
+			Last defined <a href="https://www.w3.org/2021/Process-20211102/#maturity-levels">in section 6.3.1 of the 2021 Process</a>,
+			now called [[#maturity-stages|maturity stage]].
+
+		<dt>
+			<dfn noexport id=fdn-member-consortium>Member Consortium</dfn>, plural: Member Consortia
+			(renamed term)
+		<dd>
+			Last defined <a href="https://www.w3.org/2021/Process-20211102/#fdn-member-consortium">in section 2.1.2.1 of the 2021 Process</a>,
+			now called [=Member Association=].
+
+		<dt>
+			<dfn noexport id=mou>Memorandum of Understanding</dfn>, plural: Memoranda of Understanding, abbreviation: MoU
+			(renamed term)
+		<dd>
+			Last defined <a href="https://www.w3.org/2021/Process-20211102/#mou">in section 9 of the 2021 Process</a>,
+			now called [=technical agreement=].
+
+		<dt>
+			<dfn noexport id=other-charter>Other Charter</dfn>
+			(renamed term)
+		<dd>
+			Last used <a href="https://www.w3.org/2020/Process-20200915/#other-charter">in section 5.2.6 of the 2020 Process</a>,
+			now called [=Exclusion Draft Charter=].
+
+		<dt>
+			<dfn noexport id=TeamSubmission>Team Submissions</dfn>
+			(retired term)
+		<dd>
+			Last defined <a href="https://www.w3.org/2019/Process-20190301/#TeamSubmission">in section 2.2.1 of the 2019 Process</a>.
+
+		<dt>
+			<dfn noexport id=def-W3CChair>W3C Chair</dfn>
+			(renamed term)
+		<dd>
+			Last defined <a href="https://www.w3.org/2014/Process-20140801/#def-W3CChair">in section 2.2 of the 2014 Process</a>,
+			now called [=CEO=].
+	</dl>
+
+<h2 id="acks" class="non-normative nonum">
+Appendix B: Acknowledgments</h2>
 
 	<em>This section is non-normative.</em>
 
@@ -5601,8 +5675,8 @@ Acknowledgments</h2>
 	Wendy Seltzer (W3C),
 	Yves Lafon (W3C).
 
-<h2 id="changes" class=non-normative>
-Changes</h2>
+<h2 id="changes" class="non-normative nonum">
+Appendix C: Changes</h2>
 
 	<em>This section is non-normative.</em>
 

From 78d550a0c925bb3f90392cc33ac7ca046e92298d Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 15 Aug 2024 15:40:39 +0200
Subject: [PATCH 091/237] List Proposed Recommendations in the appendix of
 retired terms

---
 index.bs | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 711b2cd6..89309aed 100644
--- a/index.bs
+++ b/index.bs
@@ -3981,7 +3981,7 @@ Publishing a [=Candidate Recommendation Draft=]</h5>
 		<li><a href="#abandon-draft">Discontinued Draft</a></li>
 	</ul>
 
-<h4 id="transition-rec" oldids="rec-publication, rec-pr, transition-pr, RecsPR">
+<h4 id="transition-rec" oldids="rec-publication, rec-pr, transition-pr">
 Transitioning to Recommendation</h4>
 
 	When a [=Working Group=] estimates
@@ -5510,6 +5510,12 @@ Appendix A: Retired Terminology</h2>
 			Last used <a href="https://www.w3.org/2020/Process-20200915/#other-charter">in section 5.2.6 of the 2020 Process</a>,
 			now called [=Exclusion Draft Charter=].
 
+		<dt>
+			<dfn noexport id=RecsPR>Proposed Recommendation</dfn>
+			(retired term)
+		<dd>
+			Last defined <a href="https://www.w3.org/policies/process/20231103/#RecsPR">in section 6.3.1 of the 2023 Process</a>.
+
 		<dt>
 			<dfn noexport id=TeamSubmission>Team Submissions</dfn>
 			(retired term)

From bcbfcdfa5c2273bf99080a47d93ef657d622c5bc Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 15 Aug 2024 15:42:19 +0200
Subject: [PATCH 092/237] Fix up terminology error

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 89309aed..6362977d 100644
--- a/index.bs
+++ b/index.bs
@@ -2871,7 +2871,7 @@ Appeal by Advisory Committee Representatives</h3>
 	and “Abstain”,
 	together with Comments.
 
-	The level of support needed for an [=Advisory Committee Override=] to pass
+	The level of support needed for an [=Advisory Committee Appeal=] to pass
 	depends on the level of ballot participation 
 	(including explicit “abstain” ballots) 
 	by [=Advisory Committee Representatives=]:

From 2f1731ec236c86e57955a0d063b69fa8a104fea0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 5 Sep 2024 12:44:43 +0900
Subject: [PATCH 093/237] Update GitHub action script

---
 .github/workflows/compile.yml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/.github/workflows/compile.yml b/.github/workflows/compile.yml
index fe2860cc..39614868 100644
--- a/.github/workflows/compile.yml
+++ b/.github/workflows/compile.yml
@@ -5,9 +5,9 @@ on: [push, pull_request]
 
 jobs:
   deploy:
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-24.04
     name: Build and deploy to gh-pages
-    if: ${{ github.repository == 'w3c/w3process' && github.event_name == 'push' }}
+    if: ${{ github.repository == 'w3c/process' && github.event_name == 'push' }}
     env:
       GITHUB_TOKEN: ${{ secrets.W3CGRUNTBOT_TOKEN }}
       GH_BRANCH: ${{ github.head_ref }}
@@ -15,10 +15,10 @@ jobs:
     steps:
       - name: Checkout the repository
         uses: actions/checkout@v2
-      - name: Setup python 3.10
+      - name: Setup python 3.12
         uses: actions/setup-python@v2
         with:
-          python-version: "3.10"
+          python-version: "3.12"
           architecture: x64
       - name: Install bikeshed
         run: |
@@ -29,16 +29,16 @@ jobs:
         run: ./deploy.sh
         shell: bash
   build:
-    runs-on: ubuntu-22.04
+    runs-on: ubuntu-24.04
     name: Check that the Process builds cleanly
-    if: ${{ github.repository != 'w3c/w3process' || github.event_name == 'pull_request' }}
+    if: ${{ github.repository != 'w3c/process' || github.event_name == 'pull_request' }}
     steps:
       - name: Checkout the repository
         uses: actions/checkout@v2
-      - name: Setup python 3.10
+      - name: Setup python 3.12
         uses: actions/setup-python@v2
         with:
-          python-version: "3.10"
+          python-version: "3.12"
           architecture: x64
       - name: Install bikeshed
         run: |

From 0fd6a938fc81699eb69b7b5b773f62d96972af49 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 5 Sep 2024 12:49:55 +0900
Subject: [PATCH 094/237] Update Github actions

---
 .github/workflows/compile.yml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/compile.yml b/.github/workflows/compile.yml
index 39614868..bba0141a 100644
--- a/.github/workflows/compile.yml
+++ b/.github/workflows/compile.yml
@@ -14,9 +14,9 @@ jobs:
       GH_EVENT_NUMBER: ${{ github.event.number }}
     steps:
       - name: Checkout the repository
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
       - name: Setup python 3.12
-        uses: actions/setup-python@v2
+        uses: actions/setup-python@v5
         with:
           python-version: "3.12"
           architecture: x64
@@ -34,9 +34,9 @@ jobs:
     if: ${{ github.repository != 'w3c/process' || github.event_name == 'pull_request' }}
     steps:
       - name: Checkout the repository
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
       - name: Setup python 3.12
-        uses: actions/setup-python@v2
+        uses: actions/setup-python@v5
         with:
           python-version: "3.12"
           architecture: x64

From 4671b580a67394cb2b21de580d534cf58f970a79 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 12 Sep 2024 00:06:47 +0900
Subject: [PATCH 095/237] Add REC maintenance to diagram (#908)

Addresses https://github.com/w3c/w3process/issues/596
---
 basic-rec-track.svg | 38 ++++++++++++++++++++++++++++++++++++--
 1 file changed, 36 insertions(+), 2 deletions(-)

diff --git a/basic-rec-track.svg b/basic-rec-track.svg
index 1aaefbf8..3dde56be 100644
--- a/basic-rec-track.svg
+++ b/basic-rec-track.svg
@@ -176,7 +176,9 @@
 								</g>
 								<text font-size="8" text-anchor="start">
 									<tspan x="342" y="157">WG Decision</tspan>
-									<tspan x="342" y="165" font-size="6">(or Team Decision with AB+TAG Approval)</tspan>
+									<tspan x="342" y="165" font-size="6">(or Team Decision</tspan>
+									<tspan x="342" y="173" font-size="6">with AB+TAG</tspan>
+									<tspan x="342" y="181" font-size="6">Approval)</tspan>
 								</text>
 								<path d="M301,147h88" stroke-dasharray="4 4" stroke="#900"></path>
 								<polygon points="301,145 296,147 301,149"></polygon>
@@ -190,12 +192,44 @@
 								</g>
 								<text font-size="8" text-anchor="start">
 									<tspan x="342" y="157">WG Decision</tspan>
-									<tspan x="342" y="165" font-size="6">(or Team Decision with AB+TAG Approval)</tspan>
+									<tspan x="342" y="165" font-size="6">(or Team Decision</tspan>
+									<tspan x="342" y="173" font-size="6">with AB+TAG</tspan>
+									<tspan x="342" y="181" font-size="6">Approval)</tspan>
 								</text>
 								<path d="M339,147v41h-242v-26" stroke-dasharray="4 4" stroke="#900" fill="none"></path>
 								<polygon points="95,164 97,159 99,164"></polygon>
 							</a>
 						</g>
+					<!-- Update REC in place, editorial -->
+						<g role="listitem">
+							<a href="#rec-1" fill="#000">
+								<g role="img">
+									<title>Publish revised Recommendation with editorial changes</title>
+								</g>
+								<text font-size="8" text-anchor="middle">
+									<tspan x="413" y="103">WG Decision</tspan>
+									<tspan x="413" y="116" font-size="6">(editorial)</tspan>
+								</text>
+								<path stroke="#000" d="M395,127C391,117 397,107 413,107 424,107 430,111 432,117" fill="none" stroke-dasharray="6 2"></path>
+								<polygon points="435,117 430,127 428,116"></polygon>
+							</a>
+						</g>
+					<!-- Update REC in place, substantive -->
+						<g role="listitem">
+							<a href="#rec-1" fill="#000">
+								<g role="img">
+									<title>Publish revised Recommendation with substantive changes</title>
+								</g>
+								<text font-size="8" text-anchor="middle">
+									<tspan x="413" y="184">WG Decision +</tspan>
+									<tspan x="413" y="192">Team Approval +</tspan>
+									<tspan x="413" y="200">AC Review</tspan>
+									<tspan x="413" y="169" font-size="6">(substantive)</tspan>
+								</text>
+								<path stroke="#000" d="M395,155C391,166 397,176 413,176 424,176 431,173 431,165" fill="none" stroke-dasharray="6 2"></path>
+								<polygon points="435,164 430,155 428,165"></polygon>
+							</a>
+						</g>
 					</g>
 				</g>
 			</g>

From 61d52c46cc65ff0d635d1904f7390355a2154515 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 12 Sep 2024 00:08:03 +0900
Subject: [PATCH 096/237] Explicitly mark figures as non-normative (#911)

See #638
---
 index.bs | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 6362977d..fe819d8d 100644
--- a/index.bs
+++ b/index.bs
@@ -3338,11 +3338,12 @@ The W3C Recommendation Track</h3>
 	A <dfn export lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document">W3C Recommendation Track document</dfn>
 	is any document whose current status is one of the four in the numbered list above.
 
-	<div role="region" aria-label="Basic W3C Recommendation Track">
+	<figure>
 		<pre class=include-raw>
 			path: basic-rec-track.svg
 		</pre>
-	</div>
+		<figcaption>Non-Normative Summary of the [=Recommendation Track=]</figcaption>
+	</figure>
 
 	This Process defines certain [=Recommendation Track=] publications as <dfn>Patent Review Drafts</dfn>.
 	Under the 2004 Patent Policy (and its 2017 update) [[!PATENT-POLICY-2004]],
@@ -4309,11 +4310,12 @@ Abandoning a W3C Recommendation</h5>
 	a [=Rescinded Recommendation=] ceases to be in effect
 	and no new licenses are granted under the Patent Policy.
 
-	<div role="region" aria-label="Retiring a W3C Recommendation">
+	<figure>
 		<pre class=include-raw>
 			path: retiring-rec.svg
 		</pre>
-	</div>
+		<figcaption>Non-Normative Summary of the Paths to Retiring a W3C Recommendation</figcaption>
+	</figure>
 
 <h5 id="deactivation">
 Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</h5>

From 0969d3e6d61e6c49b1ad84efdd0be2b898d6e765 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 12 Sep 2024 00:12:28 +0900
Subject: [PATCH 097/237] Tighten the how sustantive changes are handled post
 AC-Review (#910)

See #825

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 35 ++++++++++++++++++++++++++++++-----
 1 file changed, 30 insertions(+), 5 deletions(-)

diff --git a/index.bs b/index.bs
index fe819d8d..21093fc1 100644
--- a/index.bs
+++ b/index.bs
@@ -2772,13 +2772,31 @@ Determining the W3C Decision</h4>
 	If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>,
 	then those changes <em class=rfc2119>must</em> be announced to the [=AC=]
 	and to the [=Group=] that owns the document (if any).
-
 	Additionally, when adopting a proposal with [=substantive changes=] integrated,
 	the announcement <em class="rfc2119">must</em> include rationale
-	for the substantive changes,
-	and those changes must have the [=consensus=]
-	of the subset of the [=AC=] that voted on the proposal
-	(including anyone who explicitly abstained).
+	for the substantive changes.
+
+	[=Substantive changes=] to the proposal <em class=rfc2119>may</em> be adopted
+	only if the revised proposal has [=consensus=]
+	of the subset of the [=AC=] that voted on the initial proposal
+	(including anyone who explicitly abstained),
+	or if any [=Formal Objections=] against the revised proposal are retracted or [=overruled=]
+	and the revised proposal otherwise has sufficient support to achieve [=consensus=].
+	For clarity,
+	the [=Team=] <em class=rfc2119>should</em> seek a response from this subset of the [=AC=]
+	using the same tooling and degree of formality as it did for the [=AC Review=];
+	and as is the case during [=AC Reviews=],
+	[=dissent=] in this context <em class=rfc2119>must</em> be expressed as a [=Formal Objection=].
+
+	Any [=Formal Objection=] raised at this stage against the revised proposal
+	is handled by the same [=Council=] responsible for [=Formal Objections=] raised against the initial proposal,
+	if any.
+
+	Note: Such a [=Council=] has the ability to
+	clear either the original or the revised proposal for advancement
+	by [=overruling=] all [=Formal Objections=] against the original or revised proposal,
+	respectively.
+
 	For publications which have conditions in addition to [=AC=] approval
 	for introducing [=substantive changes=]
 	(such as [=Group=] consensus or implementation experience),
@@ -2798,6 +2816,13 @@ Determining the W3C Decision</h4>
 		because that would fail to trigger a patent exclusion opportunity.
 	</div>
 
+	For [=charters=],
+	substantive changes from the initial proposal that underwent [=AC Review=]
+	<em class=rfc2119>must not</em> include any increase to the scope.
+	If any such change is desired,
+	it <em class=rfc2119>must</em> be returned for additional work
+	and go through a complete new [=AC Review=].
+
 	This document does not specify
 	time intervals between the end of an [=Advisory Committee review=] period
 	and the [=W3C decision=].

From 0ed746a7bc4d095378704e3b80d96b008f5b3450 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 12 Sep 2024 00:15:56 +0900
Subject: [PATCH 098/237] Update changelog

---
 index.bs | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/index.bs b/index.bs
index 21093fc1..6ff89cf7 100644
--- a/index.bs
+++ b/index.bs
@@ -5828,6 +5828,12 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 			without having to republish it as a separate thing.
 			This simplifies the Process without changing the actual quality or consensus expectations.
 			(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)
+
+		<li>
+			Fine-tune the rules about
+			how changes can be incorporated into a proposal
+			following an AC Review.
+			(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
 	</ul>
 
 

From c165854d9eef69b9cee920f57631a32abc0796be Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 8 Oct 2024 11:17:42 +0900
Subject: [PATCH 099/237] Expand on examples

---
 index.bs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 6ff89cf7..e1940b47 100644
--- a/index.bs
+++ b/index.bs
@@ -2799,7 +2799,8 @@ Determining the W3C Decision</h4>
 
 	For publications which have conditions in addition to [=AC=] approval
 	for introducing [=substantive changes=]
-	(such as [=Group=] consensus or implementation experience),
+	(such as [=Group=] consensus or implementation experience
+	or going through a patent <a spec=w3c-patent-policy>Exclusion Opportunity</a>),
 	those other conditions must also be re-fulfilled.
 
 	<div class="example">

From 3fb004d2aeb8850c9abcbef6421cadb5af73c48c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 10 Oct 2024 00:06:58 +0900
Subject: [PATCH 100/237] Include link to details about the Invited Expert
 program

Among other things, the document linked to does clarify who among
Invited Experts gets access to member confidential information.

Fixes #900
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index e1940b47..54ac5654 100644
--- a/index.bs
+++ b/index.bs
@@ -4974,7 +4974,7 @@ Confidentiality Levels</h3>
 	“<dfn export id="Member-only" lt="Member-Only">Member-only</dfn>” information
 	is available to authorized parties only,
 	including representatives of Member organizations,
-	<a href="#invited-expert-wg">Invited Experts</a>,
+	<a href="#invited-expert-wg">Invited Experts</a> (as described in <a href="https://www.w3.org/invited-experts/#memaccess">https://www.w3.org/invited-experts/#memaccess</a>),
 	the Advisory Board,
 	the TAG,
 	and the Team.

From 62fea66aa728a140d8dc987c3b1ea4bfd8e2ecc7 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 10 Oct 2024 00:12:22 +0900
Subject: [PATCH 101/237] Adjust follow up steps after successful AC Appeal

Conditioned upon addressing the reasons for rejection, make the
originators of a proposal rejected via a successful AC Appeal be the
judge of whether to submit it again, instead of apparently allowing the
Team to decide disallowing resubmission.

Closes #844
---
 index.bs | 15 +++++----------
 1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/index.bs b/index.bs
index 54ac5654..3319d765 100644
--- a/index.bs
+++ b/index.bs
@@ -2915,16 +2915,11 @@ Appeal by Advisory Committee Representatives</h3>
 
 	If the vote passes,
 	the decision is overturned.
-	In that case, there are the following possible next steps:
-
-	<ol>
-		<li>
-			The proposal is rejected.
-
-		<li>
-			The proposal is returned for additional work,
-			after which the applicable decision process is re-initiated.
-	</ol>
+	Following such rejection,
+	those who had initiated the proposal may revise it
+	to address the causes of rejection
+	and follow the ordinary applicable process
+	to submit the revised proposal.
 
 <h2 id="Reports">
 W3C Technical Reports</h2>

From fb77fcabcf778f3b2a7ef7c7d715f9743b1faf03 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 8 Oct 2024 11:52:49 +0900
Subject: [PATCH 102/237] Close review loops when dropping Pull Request

Ensure the Recommendation published after AC Review corresponds
to the text submitted to AC Review and the Patent Exlusion Opportunity.

See #919
---
 index.bs | 34 ++++++++++++++++++++++------------
 1 file changed, 22 insertions(+), 12 deletions(-)

diff --git a/index.bs b/index.bs
index 3319d765..f66de8cd 100644
--- a/index.bs
+++ b/index.bs
@@ -4010,6 +4010,9 @@ Transitioning to Recommendation</h4>
 	that a [=Candidate Recommendation=] has fulfilled all the relevant criteria,
 	it <em class=rfc2119>may</em> [=group decision|decide=] to request advancement to [=W3C Recommendation=].
 
+<h5 id="transition-rec-requirements">
+Requirements for Transition</h5>
+
 	In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,
 	the Working Group:
 
@@ -4037,16 +4040,6 @@ Transitioning to Recommendation</h4>
 			<em class="rfc2119">must </em>identify any substantive issues
 			raised since the close of the [=Candidate Recommendation review period=].
 
-		<li>
-			<em class=rfc2119>must not</em> have made any [=substantive changes=] to the document
-			since the most recent [=Candidate Recommendation Snapshot=],
-			other than dropping features identified [=at risk=].
-
-		<li>
-			<em class="rfc2119">may</em> have removed features
-			identified in the [=Candidate Recommendation Snapshot=] document as [=at risk=]
-			without republishing the specification as a [=Candidate Recommendation Snapshot=].
-
 		<li>
 			<em class="rfc2119">must</em> identify, in the document, where errata are tracked.
 	</ul>
@@ -4059,16 +4052,25 @@ Transitioning to Recommendation</h4>
 	and <em class=rfc2119>must not</em> include any such marking
 	if not already present.
 
+<h5 id="initiating-rec-review">
+Initiating Review</h5>
+
 	If all the criteria above are fulfilled,
 	the [=Team=] <em class="rfc2119">must</em> begin an [=Advisory Committee Review=]
-	on the question of whether the specification is appropriate to [=publish=] as a [=W3C Recommendation=].
+	on the question of whether the identified [=Candidate Recommendation Snapshot=]
+	is appropriate to [=publish=] as a [=W3C Recommendation=].
+	If the document's most recent publication is not a [=Candidate Recommendation Snapshot=],
+	then it <em class=rfc2119>must</em> be republished as such in order to provide a basis for review.
 	The deadline for [=Advisory Committee review=]
 	<em class="rfc2119">must</em> allow <strong>at least</strong> 28 days,
-	and <em class="rfc2119">should</em> end at least 10 days
+	and <em class=rfc2119>must</em> end at least 10 days
 	after the end of the last Exclusion Opportunity
 	per ”Exclusion From W3C RF Licensing Requirements”
 	in the W3C Patent Policy [[!PATENT-POLICY]].
 
+<h5 id="rec-review-resolution">
+Resolution of Review</h5>
+
 	If there was any [=dissent=] in Advisory Committee reviews,
 	the [=Team=] <em class="rfc2119">must</em> publish the substantive content of the dissent
 	to W3C and the general public,
@@ -4084,6 +4086,14 @@ Transitioning to Recommendation</h4>
 	[=Advisory Committee representatives=] <em class="rfc2119">may</em> initiate an [=Advisory Committee Appeal=]
 	of the decision to advance the technical report.
 
+	The newly published [=Recommendation=]
+	<em class=rfc2119>must not</em> make any [=substantive changes=] to the document
+	compared to the [=Candidate Recommendation Snapshot=] submitted for AC Review,
+	other than dropping features identified [=at risk=].
+
+<h5 id="rec-next-steps">
+Next Steps from W3C Recommendation</h5>
+
 	Possible next steps:
 	A [=W3C Recommendation=] normally retains its status indefinitely.
 	However it <em class="rfc2119">may</em> be:

From 7191dab60f132ed151a1d0b6a1e91a319dbdaeb2 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 22 Oct 2024 10:51:47 +0900
Subject: [PATCH 103/237] Clarify who can issue the decision to abandon a
 charter in development

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index f66de8cd..25bf44b3 100644
--- a/index.bs
+++ b/index.bs
@@ -1763,7 +1763,7 @@ Charter Refinement</h3>
 
 	The [=charter refinement=] phase concludes when there is either:
 	* A [=group decision=] to initiate [=AC Review=] of the [=charter draft=].
-	* A [=chair decision=] to abandon the proposal.
+	* A [=chair decision=] by the [=Chartering Facilitator=] to abandon the proposal.
 
 	Any [=Formal Objection=] filed during the  [=charter refinement=] phase--
 	other than an objection to the choice of [=Chartering Facilitator=]

From 835e9ff5049568f7c41f7c5f4b0bfc3c1477490b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 22 Oct 2024 14:12:38 +0900
Subject: [PATCH 104/237] Streamline Council formation and provide safeguards
 (#925)

A major source of dissatisfaction with the current Formal Objection
handling process is the time it takes to initiate Councils. This brings
the following improvements:
* This makes it clear that the administrative steps for forming a
  council are expected to happen in parallel with the Team's effort to
  resolve and/or document the objection, which should cut the waiting
  time (and matches what the Team is moving towards anyway).
* Currently convening a Council *must* start within 90 days of FO
  registration, and *should* be complete within an extra 45 days.
  not only is this long, it means there is no actual hard end date.
  After this change, the hard deadline is 90 days.
* Previously, nothing happened if the deadlines were exceeded. This
  empowers the AB and TAG chairs to complete council formation
  once we're past the deadlines.

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 37 ++++++++++++++++++++++++++-----------
 1 file changed, 26 insertions(+), 11 deletions(-)

diff --git a/index.bs b/index.bs
index 25bf44b3..ab040e60 100644
--- a/index.bs
+++ b/index.bs
@@ -2402,6 +2402,10 @@ Investigation and Mediation by the Team</h4>
 	to make sure the problem and the various viewpoints are well understood,
 	and to the extent possible,
 	to arrive at a recommended disposition.
+
+	In parallel, the Team <em class=rfc2119>should</em> start the steps necessary
+	to <a href="#council-convention">convene</a> a Council.
+
 	If the [=Team=] can resolve the issue
 	to the satisfaction of the individual that filed the [=Formal Objection=],
 	the individual withdraws the objection and the disposition process terminates.
@@ -2409,10 +2413,10 @@ Investigation and Mediation by the Team</h4>
 	Otherwise,
 	upon concluding that consensus cannot be found,
 	and no later than 90 days after the [=Formal Objection=] being registered,
-	the [=Team=] <em class=rfc2119>must</em> initiate formation of a [=W3C Council=],
-	which should be <a href="#council-convention">convened</a> within 45 days of being initiated.
-	Concurrently, it must prepare a report for the [=Council=]
-	documenting its findings and attempts to find consensus.
+	the [=Team=] <em class=rfc2119>must</em>
+	deliver to the [=Council=] a report
+	documenting its findings and attempts to find consensus,
+	and hand over the matter to the [=W3C Council=].
 
 <h4 id=council>
 W3C Council</h4>
@@ -2563,16 +2567,27 @@ Council Chairing</h5>
 	if requested by the [=Council Team Contact=] or by the [=Chair=]
 	during the Council’s operation.
 
-<h5 id=council-deliberations>
-Council Deliberations</h5>
+<h5 id=council-convention>
+Convening the Council</h5>
 
-	<p id=council-convention>
 	Upon appointment of the [=W3C Council Chair=]
 	and delivery of the [=Team=]’s report,
-	the [=W3C Council=] is considered to be convened
-	and can start deliberations.
+	the [=W3C Council=] is considered to be <dfn>convened</dfn>
+	and can start [[#council-deliberations|deliberations]].
+
+	If a [=W3C Council=] has not yet been [=convened=] within 90 days of a Formal Objection
+	being [[#registering-objections|registered]],
+	the [=Chairs=] of the [=TAG=] and [=AB=] <em class=rfc2119>may</em> take independent action to ensure
+	that the [=dismissal=], [=renunciation=],
+	and [[#council-chairing|chair selection]] processes have been run.
+	If a report from the Team is not delivered within those 90 days,
+	the [=Council=] is considered [=convened=]
+	upon selection of the [=W3C Council Chair|Council Chair=].
+
+<h5 id=council-deliberations>
+Council Deliberations</h5>
 
-	Having reviewed the information gathered by the [=Team=],
+	Once [=convened=],
 	the Council <em class=rfc2119>may</em> conduct additional research or analysis,
 	or request additional information or interviews from anyone,
 	including the Team.
@@ -2634,7 +2649,7 @@ Council Deliberations</h5>
 	and its [=Council Team Contact=].
 
 	<p id=45-day-update>
-	If a [=W3C Council=] is unable to come to a conclusion within 45 days of being <a href="#council-convention">convened</a>,
+	If a [=W3C Council=] is unable to come to a conclusion within 45 days of being [=convened=],
 	the [=W3C Council Chair=] <em class=rfc2119>must</em> inform the [=AC=] of this delay
 	and of the status of the discussions.
 	The [=W3C Council Chair=] <em class=rfc2119>may</em> additionally make this report <a href="#confidentiality-levels">public</a>.

From d61b4c03dc208b7c75ea9aca60fc949bf1473b43 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 22 Oct 2024 14:20:06 +0900
Subject: [PATCH 105/237] Update Changelog

---
 index.bs | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/index.bs b/index.bs
index ab040e60..f9ca2981 100644
--- a/index.bs
+++ b/index.bs
@@ -5855,6 +5855,18 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 			how changes can be incorporated into a proposal
 			following an AC Review.
 			(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
+
+		<li>
+			Let the originator of a proposal decide whether to try again
+			after addressing feedback
+			following an AC Appeal.
+			(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
+
+		<li>
+			Adjust the rules guiding initiation of Councils,
+			to make the deadline strict,
+			and to provide a fallback mechanism if they are not met.
+			(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>)
 	</ul>
 
 

From 6fcd9939c516de5fecaf4ce3511ec85daab76673 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 22 Oct 2024 14:32:13 +0900
Subject: [PATCH 106/237] Reorganize changelog

---
 index.bs | 216 +++++++++++++++++++++++++++++--------------------------
 1 file changed, 115 insertions(+), 101 deletions(-)

diff --git a/index.bs b/index.bs
index f9ca2981..7bf2e763 100644
--- a/index.bs
+++ b/index.bs
@@ -5746,128 +5746,142 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 
 	In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:
 
-	<ul>
-		<li>
-			Council dismissal vote counts must be reported.
-			(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)
-
-		<li>
-			Exclude TAG/AB from voting on their own decisions/proposals.
-			(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)
-
-		<li>
-			Add a requirement to make progress on external issues for update requests
-			(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>)
+	<dl>
+		<dt>Changes to formal decision making and escalation
+		<dd>
+			<ul>
+				<li>
+					Put constraints on the timing of making Formal Objections public.
+					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
 
-		<li>
-			Enable Team to replace defunct registry custodians when no-one else can.
-			(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>)
+				<li>
+					Adjust the rules guiding initiation of Councils,
+					to make the deadline strict,
+					and to provide a fallback mechanism if they are not met.
+					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>)
 
-		<li>
-			Stop citing the superseded TAG charter.
-			(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)
+				<li>
+					Make the Council's short-circuit a little more flexible.
+					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
 
-		<li>
-			Rename “registry sections” to [=embedded registries=]
-			to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
-			(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
+				<li>
+					Exclude TAG/AB from voting on their own decisions/proposals.
+					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)
 
-		<li>
-			Put constraints on the timing of making Formal Objections public.
-			(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
+				<li>
+					Council dismissal vote counts must be reported.
+					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)
 
-		<li>
+				<li>
+					Adjust AC appeal vote threshold based on participation,
+					aligning with the thresholds and super majority requirements
+					for "Requisite Member Vote" from the W3C Bylaws.
+					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
 
-			Rename "Draft Note" into "Note Draft",
-			and "Draft Registry" into "Registry Draft"
-			to be consistent with other statuses that uses the word "Draft",
-			and to make that word stand out more.
-			(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>)
+				<li>
+					Fine-tune the rules about
+					how changes can be incorporated into a proposal
+					following an AC Review.
+					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
 
-		<li>
-			Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
-			and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>).
+				<li>
+					Let the originator of a proposal decide whether to try again
+					after addressing feedback
+					following an AC Appeal.
+					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
+			</ul>
 
-		<li>
-			Clarify how the outcome of certain ballots are determined.
-			(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)
+		<dt>Changes to technical reports and their publication
+		<dd>
+			<ul>
+				<li>
+					Retire the Proposed Recommendation phase of the Recommendation track.
+					It was only used as a short-lived transition
+					during which various verifications and votes about CR were done.
+					These can be done on a CR
+					without having to republish it as a separate thing.
+					This simplifies the Process without changing the actual quality or consensus expectations.
+					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)
+
+				<li id="streamlined-update">
+					Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
+					This was meant to enable REC track publication with fewer/faster approval steps
+					when some stricter than usual criteria were fulfilled.
+					However, regular REC track publication have improved enough
+					that this became unnecessary,
+					and nobody was using it.
+					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>)
 
-		<li>
-			Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.
-			This change, while moderate in size, is purely editorial.
-			(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>)
+				<li>
+					Add a requirement to make progress on external issues for update requests
+					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>)
 
-		<li id="streamlined-update">
-			Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
-			This was meant to enable REC track publication with fewer/faster approval steps
-			when some stricter than usual criteria were fulfilled.
-			However, regular REC track publication have improved enough
-			that this became unnecessary,
-			and nobody was using it.
-			(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>)
+				<li>
+					Enable Team to replace defunct registry custodians when no-one else can.
+					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>)
 
-		<li>
-			Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a>
-			the various parts of the Process
-			that described whether and how the Team can maintain technical reports
-			that no longer have a Group chartered to maintain them.
-			(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
+				<li>
+					Rename “registry sections” to [=embedded registries=]
+					to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
+					(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
 
-		<li>
-			Require Chairs to be listed in Charters.
-			(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
+				<li>
+					Rename "Draft Note" into "Note Draft",
+					and "Draft Registry" into "Registry Draft"
+					to be consistent with other statuses that uses the word "Draft",
+					and to make that word stand out more.
+					(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>)
 
-		<li>
-			The URL of this document was changed
-			from /Consortium/Process/ to /policies/process/
-			for better integration in the W3C website architecture.
+				<li>
+					Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
+					and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>).
 
-		<li>
-			Shift most of the informative discussion about Workshops to [[GUIDE]],
-			and reorganize the remaining normative requirements.
-			(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
+				<li>
+					Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a>
+					the various parts of the Process
+					that described whether and how the Team can maintain technical reports
+					that no longer have a Group chartered to maintain them.
+					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
+			</ul>
 
-		<li>
-			Make the Council's short-circuit a little more flexible.
-			(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
+		<dt>Changes to chartering
+		<dd>
+			<ul>
+				<li>
+					Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
+					(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>)
 
-		<li>
-			Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
-			(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>)
+				<li>
+					Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.
+					This change, while moderate in size, is purely editorial.
+					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>)
 
-		<li>
-			Adjust AC appeal vote threshold based on participation,
-			aligning with the thresholds and super majority requirements
-			for "Requisite Member Vote" from the W3C Bylaws.
-			(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
+				<li>
+					Require Chairs to be listed in Charters.
+					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
+			</ul>
 
-		<li>
-			Retire the Proposed Recommendation phase of the Recommendation track.
-			It was only used as a short-lived transition
-			during which various verifications and votes about CR were done.
-			These can be done on a CR
-			without having to republish it as a separate thing.
-			This simplifies the Process without changing the actual quality or consensus expectations.
-			(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)
+		<dt>Other changes
+		<dd>
+			<ul>
+				<li>
+					Clarify how the outcome of certain ballots are determined.
+					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)
 
-		<li>
-			Fine-tune the rules about
-			how changes can be incorporated into a proposal
-			following an AC Review.
-			(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
+				<li>
+					Stop citing the superseded TAG charter.
+					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)
 
-		<li>
-			Let the originator of a proposal decide whether to try again
-			after addressing feedback
-			following an AC Appeal.
-			(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
+				<li>
+					The URL of this document was changed
+					from /Consortium/Process/ to /policies/process/
+					for better integration in the W3C website architecture.
 
-		<li>
-			Adjust the rules guiding initiation of Councils,
-			to make the deadline strict,
-			and to provide a fallback mechanism if they are not met.
-			(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>)
-	</ul>
+				<li>
+					Shift most of the informative discussion about Workshops to [[GUIDE]],
+					and reorganize the remaining normative requirements.
+					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
+			</ul>
 
 
 <h3 id=changes-previous class=no-num oldids="changes-2023-1, changes-2023, changes-2021, changes-2020, changes-2019, changes-2018, changes-2017">

From fd42a0fce811e6ed522dbd869230199a58c8059d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tantek=20=C3=87elik?= <blog@tantek.com>
Date: Tue, 8 Oct 2024 21:14:43 -0700
Subject: [PATCH 107/237] update BYLAWS reference to latest

update BYLAWS URL to 2024 revision as approved by Consortium Members as linked from https://www.w3.org/about/corporation/
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 7bf2e763..fda5b502 100644
--- a/index.bs
+++ b/index.bs
@@ -6085,7 +6085,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"BYLAWS": {
-		"href": "https://www.w3.org/2022/10/w3c-bylaws-20221019.pdf",
+		"href": "https://www.w3.org/2024/09/25-w3c-bylaws.pdf",
 		"title": "Amended and Restated Bylaws of World Wide Web Consortium, Inc."
 	},
 	"W3C-IPR": {

From ff5a0505306788896335c859ff162cf662a4b614 Mon Sep 17 00:00:00 2001
From: Philippe Le Hegaret <plh@w3.org>
Date: Fri, 25 Oct 2024 09:45:16 -0400
Subject: [PATCH 108/237] Update group and contacts

per https://w3c.github.io/w3c.json.html
---
 w3c.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/w3c.json b/w3c.json
index 4559ff96..719d6c42 100644
--- a/w3c.json
+++ b/w3c.json
@@ -1,6 +1,6 @@
 {
-  "group": [ 7756, 50503 ]
-, "contacts":   ["jeffjaffe", "chaals", "dwsinger"]
+  "group": [ "other/ab", "cg/w3process" ]
+, "contacts":   ["plehegar", "fantasai", "frivoal"]
 , "policy": "restricted"
 , "repo-type": "process"
 }

From 1e7f9422336ff6d9db9883bc92a18704be772b8b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tantek=20=C3=87elik?= <blog@tantek.com>
Date: Thu, 31 Oct 2024 17:21:59 -0700
Subject: [PATCH 109/237] fix id attr typo lifecyle->lifecycle (#939)

Match id attribute with proper spelling in visible h2
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index fda5b502..6d02ff53 100644
--- a/index.bs
+++ b/index.bs
@@ -1705,7 +1705,7 @@ Team Representative in an Interest Group</h5>
 	When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
 	an individual is a <dfn export>Team representative in an Interest Group</dfn> when so designated by W3C management.
 
-<h2 id=group-lifecyle>
+<h2 id=group-lifecycle>
 Lifecycle of Chartered Groups</h2>
 
 	W3C creates [=charters=] for [=chartered groups=] based on interest from the [=Members=] and [=Team=].

From 5a1c43962b6f42a54b52309349ff13cec454802c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 14 Nov 2024 09:13:34 +0900
Subject: [PATCH 110/237] Simplify the section Member Submissions (#936)

Cuts down the Process part of Member Submissions to the bare minimum,
with the expectation that all the detailed requirements and guidance
will be shifted to /Guide.

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 355 ++++++++++---------------------------------------------
 1 file changed, 61 insertions(+), 294 deletions(-)

diff --git a/index.bs b/index.bs
index 6d02ff53..7cdaad11 100644
--- a/index.bs
+++ b/index.bs
@@ -874,7 +874,7 @@ Role of the Advisory Board</h5>
 	and proposing actions to resolve these issues.
 	The Advisory Board manages the <a href="#GAProcess">evolution of the Process Document</a>.
 	As part of a [=W3C Council=],
-	members of the [=Advisory Board=] hear and adjudicate on <a href="#SubmissionNo">Submission Appeals</a>
+	members of the [=Advisory Board=] hear and adjudicate on [=Submission Appeals=]
 	and [=Formal Objections=].
 
 	The [=Advisory Board=] is distinct from the [=Board of Directors=]
@@ -974,7 +974,7 @@ Role of the Technical Architecture Group</h5>
 	</ol>
 
 	As part of a [=W3C Council=],
-	the members of the [=TAG=] hear and adjudicate on <a href="#SubmissionNo">Submission Appeals</a>
+	the members of the [=TAG=] hear and adjudicate on [=Submission Appeals=]
 	and [=Formal Objections=].
 
 	The [=TAG=]'s scope is limited to technical issues about Web architecture.
@@ -1050,7 +1050,7 @@ Communications of the Technical Architecture Group</h5>
 	</ul>
 
 	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>),
+	For some TAG discussions (e.g.,  a [=Submission Appeal=]),
 	the TAG <em class="rfc2119">may</em> use a list that will be <a href="#Member-only">Member-only</a>.
 
 	The [=TAG=] <em class="rfc2119">should</em> send a summary of each of its <a href="#GeneralMeetings">meetings</a>
@@ -5147,308 +5147,80 @@ Liaisons</h2>
 	Information about <a href="https://www.w3.org/liaisons/">W3C liaisons with other organizations</a> [[LIAISON]]
 	and the guidelines W3C follows when creating a liaison is available on the Web.
 
-<h2 id="Submission">
-Member Submission Process</h2>
+<h2 id="Submission" oldids="SubmissionRights, SubmissionScope, TeamSubmissionRights, SubmissionYes, SubmissionNo">
+Member Submissions</h2>
 
-	The Member Submission process allows Members
-	to propose technology
-	or other ideas
-	for consideration by the [=Team=].
+	A <dfn id="MemberSubmission">Member Submission</dfn> is a document or set of documents
+	developed outside of W3C,
+	and submitted to W3C
+	by one or more [=Members=] (the <dfn export lt="submitter">Submitter(s)</dfn>)
+	to propose technology or other ideas.
 	After review,
 	the [=Team=] <em class="rfc2119">may</em> make the material available at the W3C website.
-	The formal process affords Members a record of their contribution
-	and gives them a mechanism for disclosing the details of the transaction with the Team
-	(including IPR claims).
-	The [=Team=] also makes review comments on the Submitted materials available for W3C Members,
-	the public,
-	and the media.
 
-	A <dfn id="MemberSubmission">Member Submission</dfn> consists of:
+	Making a [=Member Submission=] available at the W3C website
+	does not indicate endorsement, acceptance, or adoption by W3C,
+	its Team, or its Members.
+	The [=acknowledge|acknowledgment=] of a Submission request
+	does not imply that any action will be taken by W3C.
+	It merely records publicly
+	that the Submission has been made by the Submitter(s).
+	A Member Submission made available by W3C
+	is not a W3C [=technical report=] and
+	<em class="rfc2119">must not</em> be referred to as
+	an output or “work in progress” of W3C.
 
-	<ul>
-		<li>
-			One or more documents developed outside of the W3C process, and
+	The [=Member Submission=] process consists of the following steps:
 
-		<li>
-			Information about the documents,
-			provided by the Submitter.
-	</ul>
+	<dl>
+		<dt>Submission
+		<dd>
+			One of the [=Submitters=],
+			copying the [=Advisory Committee representatives=] of the other [=Submitters=] (if any),
+			sends a request to the Team to acknowledge the Submission request.
+			The [=Team=] and [=Submitter=](s) communicate to ensure that the [=Member Submission=] is complete.
+
+		<dt>Review
+		<dd>
+			The [=Team=] reviews the Submission
+			to evaluate its scope, quality, and compliance with the Submission requirements,
+			including licensing requirements:
 
-	One or more Members (called the <dfn export lt="submitter">Submitter(s)</dfn>)
-	<em class="rfc2119">may</em> participate in a Member Submission.
-	Only W3C Members <em class="rfc2119">may</em> be listed as [=Submitters=].
+			<ul>
+				<li>
+					The [=Submitter=](s)
+					and any other authors of the submitted material
+					<em class=rfc2119>must</em> agree
+					to license the Submission under the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> [[!DOC-LICENSE]].
 
-	The Submission process consists of the following steps:
+				<li>
+					The request <em class=rfc2119>must</em> satisfy the Member Submission licensing commitments
+					in [[PATENT-POLICY#sec-submissions]].
+			</ul>
 
-	<ol>
-		<li>
-			One of the [=Submitters=] sends a request to the Team to acknowledge the Submission request.
-			The Team and [=Submitter=](s) communicate to ensure that the [=Member Submission=] is complete.
+			Detailed procedures and requirements are defined by the [=Team=]
+			and documented in the “<a href="https://www.w3.org/2000/09/submission">Member submissions guidebook</a>” [[MEMBER-SUB]].
 
-		<li>
+		<dt>Decision
+		<dd>
 			After review, the [=Team=] <em class="rfc2119">must</em> either
-			acknowledge or reject the Submission request.
+			[=acknowledge=] or [=reject=] the Submission request.
 
 			<ul>
 				<li>
-					If <a href="#SubmissionYes">acknowledged</a>,
+					If <dfn>acknowledged</dfn>,
 					the Team <em class="rfc2119">must</em> make the [=Member Submission=] available
-					at the public W3C website,
-					in addition to Team comments about the [=Member Submission=].
+					at the public W3C website
+					alongside other <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a>.
+					[[SUBMISSION-LIST]]
 
-				<li>If <a href="#SubmissionNo">rejected</a>,
-					the [=Submitter=](s) <em class="rfc2119">may</em> initiate a <a href="#SubmissionNo">Submission Appeal</a>.
+				<li>
+					If <dfn>rejected</dfn>,
+					the [=Team=] <em class=rfc2119>must</em> inform the [=Advisory Committee representative=](s) of the [=Submitter=](s),
+					and <em class=rfc2119>must</em> provide rationale if requested by the [=Submitter=](s).
+					The [=Submitter=](s) <em class=rfc2119>may</em> initiate a [=Submission Appeal=].
 			</ul>
-	</ol>
-
-	<div class=note>
-		Note: To avoid confusion about the Member Submission process, please note that:
-
-		<ul>
-			<li>
-				Documents in a [=Member Submission=] are developed outside
-				of the W3C <a href="#Reports">technical report development process</a>
-				(and therefore are not included in the <a href="https://www.w3.org/TR/">index of W3C technical reports</a> [[TR]]).
-
-			<li>
-				The Submission process is <strong>not</strong> a means
-				by which Members ask for “ratification” of these documents
-				as [=W3C Recommendations=].
-
-			<li>
-				There is no requirement or guarantee
-				that technology which is part of an acknowledged Submission request
-				will receive further consideration by W3C
-				(e.g., by a W3C [=Working Group=]).
-		</ul>
-	</div>
-
-	Making a Member Submission available at the W3C website
-	does not imply endorsement by W3C,
-	including the W3C Team or Members.
-	The acknowledgment of a Submission request
-	does not imply that any action will be taken by W3C.
-	It merely records publicly
-	that the Submission request has been made by the Submitter.
-	A Member Submission made available by W3C
-	<em class="rfc2119">must not</em> be referred to as “work in progress” of W3C.
-
-	The list of <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a> [[SUBMISSION-LIST]]
-	is available at the W3C website.
-
-<h3 id="SubmissionRights">
-Submitter Rights and Obligations</h3>
-
-	When more than one Member jointly participates in a Submission request,
-	only one Member formally sends in the request.
-	That Member <em class="rfc2119">must</em> copy
-	each of the [=Advisory Committee representatives=] of the other participating Members,
-	and each of those [=Advisory Committee representatives=] <em class="rfc2119">must</em> confirm
-	(by email to the Team)
-	their participation in the Submission request.
-
-	At any time prior to acknowledgment,
-	any [=Submitter=] <em class="rfc2119">may</em> withdraw support for a Submission request
-	(described in "<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>" [[SUBMISSION-REQ]]).
-	A Submission request is “withdrawn” when no Submitter(s) support it.
-	The Team <em class="rfc2119">must not</em> make statements
-	about withdrawn Submission requests.
-
-	Prior to acknowledgment,
-	the [=Submitter=](s) <em class="rfc2119">must not</em>,
-	<strong>under any circumstances</strong>,
-	refer to a document as “submitted to the World Wide Web Consortium”
-	or “under consideration by W3C” or any similar phrase
-	either in public or Member communication.
-	The [=Submitter=](s) <em class="rfc2119">must not</em> imply
-	in public or Member communication
-	that W3C is working (with the [=Submitter=](s)) on the material in the [=Member Submission=].
-	The [=Submitter=](s) <em class="rfc2119">may</em> release the documents in the Member Submission to the public
-	prior to acknowledgment
-	(without reference to the Submission request).
-
-	After acknowledgment,
-	the [=Submitter=](s) <em class="rfc2119">must not</em>,
-	<strong>under any circumstances</strong>,
-	imply W3C investment in the Member Submission
-	until, and unless, the material has been adopted as a deliverable
-	of a W3C [=Working Group=].
-
-<h4 id="SubmissionScope">
-Scope of Member Submissions</h4>
-
-	When a technology overlaps in scope with the work of a chartered Working Group,
-	Members <em class="rfc2119">should</em> <a href="#group-participation">participate in the Working Group</a>
-	and contribute the technology to the group's process
-	rather than seek publication through the Member Submission process.
-	The [=Working Group=] <em class="rfc2119">may</em> incorporate the contributed technology into its deliverables.
-	If the Working Group does not incorporate the technology,
-	it <em class="rfc2119">should not</em> publish the contributed documents
-	as [=Working Group Notes=] since [=Working Group Notes=]
-	represent group output,
-	not input to the group.
-
-	On the other hand,
-	while W3C is in the early stages of developing a charter,
-	Members <em class="rfc2119">should</em> use the Submission process
-	to build consensus around concrete proposals for new work.
-
-	Members <em class="rfc2119">should not</em> submit materials
-	covering topics well outside the scope of <a href="https://www.w3.org/mission/">W3C's mission</a> [[MISSION]].
-
-<h4 id="SubmissionReqs">
-Information Required in a Submission Request</h4>
-
-	The [=Submitter=](s)
-	and any other authors of the submitted material
-	<em class="rfc2119">must</em> agree that,
-	if the request is acknowledged,
-	the documents in the Member Submission will be subject to the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> [[!DOC-LICENSE]]
-	and will include a reference to it.
-	The [=Submitter=](s) <em class="rfc2119">may</em> hold the copyright for the documents in a Member Submission.
-
-	The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments
-	in “Licensing Commitments in W3C Submissions”
-	in the W3C Patent Policy [[!PATENT-POLICY]].
-
-	The [=Submitter=](s) <em class="rfc2119">must</em> include the following information:
-
-	<ul>
-		<li>
-			The list of all submitting Members.
-
-		<li>
-			Position statements from all submitting Members (gathered by the Submitter).
-			All position statements <em class="rfc2119">must</em> appear in a separate document.
-
-		<li>
-			Complete electronic copies of any documents submitted for consideration
-			(e.g., a technical specification,
-			a position paper,
-			etc.)
-			If the Submission request is acknowledged,
-			these documents will be made available by W3C
-			and therefore <em class="rfc2119">must</em> satisfy the Team's
-			<a href="https://www.w3.org/pubrules/">Publication Rules</a> [[!PUBRULES]].
-			[=Submitters=] <em class="rfc2119">may</em> hold the copyright for the material contained in these documents,
-			but when made available by W3C,
-			these documents <em class="rfc2119">must</em> be subject to the provisions
-			of the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> [[!DOC-LICENSE]].
-	</ul>
-
-	The request <em class="rfc2119">must</em> also answer the following questions.
-
-	<ul>
-		<li>
-			What proprietary technology is required to implement the areas addressed by the request,
-			and what terms are associated with its use?
-			Again, many answers are possible,
-			but the specific answer will affect the [=Team's Decision=].
-
-		<li>
-			What resources, if any,
-			does the Submitter intend to make available
-			if W3C acknowledges the Submission request
-			and takes action on it?
-
-		<li>
-			What action would the Submitter like W3C to take
-			if the Submission request is acknowledged?
-
-		<li>
-			What mechanisms are there to make changes to the specification being submitted?
-			This includes, but is not limited to,
-			stating where change control will reside
-			if the request is acknowledged.
-	</ul>
-
-	For other administrative requirements related to Submission requests,
-	see “<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>” [[MEMBER-SUB]].
-
-<h3 id="TeamSubmissionRights">
-Team Rights and Obligations</h3>
-
-	Although they are not technical reports,
-	the documents in a [=Member Submission=]
-	<em class="rfc2119">must</em> fulfill the requirements established by the [=Team=],
-	including the Team's <a href="https://www.w3.org/pubrules/">Publication Rules</a> [[!PUBRULES]].
-
-	The [=Team=] sends a <dfn id="validation-notice">validation notice</dfn> to the [=Submitter=](s)
-	once the Team has reviewed a Submission request
-	and judged it complete and correct.
-
-	Prior to a <a lt="Team Decision">decision</a> to <a href="#SubmissionYes">acknowledge</a>
-	or <a href="#SubmissionNo">reject</a> the request,
-	the request is [=Team-only=],
-	and the [=Team=] <em class="rfc2119">must</em> hold it in the strictest confidentiality.
-	In particular,
-	the Team <em class="rfc2119">must not</em> comment to the media
-	about the Submission request.
-
-<h3 id="SubmissionYes">
-Acknowledgment of a Submission Request</h3>
-
-	The [=Team=] <a href="#SubmissionYes">acknowledges</a> a Submission request
-	by sending an announcement to the [=Advisory Committee=].
-	Though the announcement <em class="rfc2119">may</em> be made at any time,
-	the [=Submitter=](s) can expect an announcement between <span class="time-interval">four to six weeks</span>
-	after the [=validation notice=].
-	The [=Team=] <em class="rfc2119">must</em> keep the [=Submitter=](s) informed
-	of when an announcement is likely to be made.
-
-	Once a Submission request has been acknowledged,
-	the [=Team=] <em class="rfc2119">must</em>:
-
-	<ul>
-		<li>
-			Make the [=Member Submission=] available at the W3C website.
-
-		<li>
-			Make the Team comments about the Submission request available at the W3C website.
-	</ul>
-
-	If the [=Submitter=](s) wishes to modify
-	a document made available 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=].
-
-<h3 id="SubmissionNo">
-Rejection of a Submission Request, and Submission Appeals</h3>
-
-	The [=Team=] <em class="rfc2119">may</em> reject a Submission request
-	for a variety of reasons,
-	including any of the following:
-
-	<ul>
-		<li>
-			The ideas expressed in the request
-			overlap in scope with the work of a chartered Working Group,
-			and acknowledgment might jeopardize the progress of the group.
-
-		<li>
-			The IPR statement made by the [=Submitter=](s) is inconsistent with W3C's
-			Patent Policy [[!PATENT-POLICY]]
-			and in particular the “Licensing Commitments in W3C Submissions”,
-			<a href="https://www.w3.org/copyright/document-license-2023/">Document License</a> [[!DOC-LICENSE]],
-			or other IPR policies.
-
-		<li>
-			The ideas expressed in the request are poor,
-			might harm the Web,
-			or run counter to <a href="https://www.w3.org/mission/">W3C's mission</a> [[MISSION]].
-
-		<li>
-			The ideas expressed in the request lie well outside the scope of W3C's mission.
-	</ul>
-
-	In case of a rejection,
-	the [=Team=] <em class="rfc2119">must</em> inform the [=Advisory Committee representative=](s)
-	of the [=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.
+	</dl>
 
 	The [=Advisory Committee representative=](s) of the [=Submitters=](s)
 	<em class="rfc2119">may</em> initiate a [=Submission Appeal=].
@@ -5913,11 +5685,6 @@ Changes since earlier versions</h3>
 		"title": "The list of acknowledged Member Submissions",
 		"publisher": "W3C"
 	},
-	"SUBMISSION-REQ": {
-		"href": "https://www.w3.org/2000/09/submission",
-		"title": "Make or Withdraw a Member Submission Request (Member-only access)",
-		"publisher": "W3C"
-	},
 	"TR": {
 		"href": "https://www.w3.org/TR/",
 		"title": "The W3C technical reports index",
@@ -6050,7 +5817,7 @@ Changes since earlier versions</h3>
 	},
 	"MEMBER-SUB": {
 		"href": "https://www.w3.org/2000/09/submission",
-		"title": "How to send a Submission request",
+		"title": "Member submissions guidebook",
 		"publisher": "W3C"
 	},
 	"ELECTION-HOWTO": {

From d95d136b058c8b2404397949ee06ea6dffdc4ba5 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 14 Nov 2024 11:22:07 +0900
Subject: [PATCH 111/237] Update changelog

---
 index.bs | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/index.bs b/index.bs
index 7cdaad11..cf5ccca4 100644
--- a/index.bs
+++ b/index.bs
@@ -5653,6 +5653,14 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					Shift most of the informative discussion about Workshops to [[GUIDE]],
 					and reorganize the remaining normative requirements.
 					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
+
+				<li>
+					The section on Member Submissions was significantly shortened and simplified,
+					reducing the complexity under formal Process authority,
+					and shifting much of the material to /Guide,
+					under Team authority.
+					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a>
+					and <a href="https://github.com/w3c/process/issues/648">Pull Request 648</a>)
 			</ul>
 
 

From d2e4e21cdf6fa4d58cf997b02335bfd73a1cc816 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 14 Nov 2024 11:24:35 +0900
Subject: [PATCH 112/237] Fix wrong issue number

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index cf5ccca4..aa0fb714 100644
--- a/index.bs
+++ b/index.bs
@@ -5660,7 +5660,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					and shifting much of the material to /Guide,
 					under Team authority.
 					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a>
-					and <a href="https://github.com/w3c/process/issues/648">Pull Request 648</a>)
+					and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>)
 			</ul>
 
 

From 50cb9fbbc88baa7a41ecb6ad70e82a9a99841d33 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 28 Nov 2024 11:25:34 +0900
Subject: [PATCH 113/237] Rephrase references to "the" Membership Agreement

As there exists multiple versions of it, there isn't a singular
Membership Agreement, and the phrasing should reflect so as not to be
confusing.

See #879
---
 index.bs | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index aa0fb714..14f76131 100644
--- a/index.bs
+++ b/index.bs
@@ -114,7 +114,7 @@ Relation of Process Document to Patent Policy and Other Policies</h2>
 
 	W3C Members' attention is called to the fact
 	that provisions of the Process Document are binding on Members
-	per the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> [[MEMBER-AGREEMENT]].
+	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
@@ -231,7 +231,7 @@ Members and the Team</h2>
 Members</h3>
 
 	<dfn lt="W3C Member|Member">W3C Members</dfn> are
-	organizations subscribed according to the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> [[MEMBER-AGREEMENT]].
+	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>
@@ -279,7 +279,7 @@ Rights of Members</h4>
 			described in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [[INTRO]].
 	</ul>
 
-	Furthermore, subject to further restrictions included in the Member Agreement,
+	Furthermore, subject to further restrictions included in their Member Agreement,
 	representatives of Member organizations participate in W3C as follows:
 
 	<ul>
@@ -758,7 +758,7 @@ Participation in the Advisory Committee</h4>
 
 	When an organization joins W3C
 	(see “<a href="https://www.w3.org/membership/join/">How to Join W3C</a>” [[JOIN]]),
-	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement.
+	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of their Membership Agreement.
 	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>,
@@ -4963,7 +4963,7 @@ Public Communication</h3>
 
 		<li>
 			Legal documents,
-			including the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> [[MEMBER-AGREEMENT]]
+			including <a href="https://www.w3.org/membership/agreement/">Membership Agreements</a> [[MEMBER-AGREEMENT]]
 			and documentation of any legal commitments W3C has with other entities.
 
 		<li>
@@ -5679,7 +5679,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 		},
 	"MEMBER-AGREEMENT": {
-		"href": "https://www.w3.org/Consortium/Agreement/Member-Agreement",
+		"href": "https://www.w3.org/membership/agreement/",
 		"title": "W3C Membership Agreement",
 		"publisher": "W3C"
 	},

From 2442b54f3f1e1dec936e250430a8c757ba04ace0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 28 Nov 2024 11:52:14 +0900
Subject: [PATCH 114/237] Remove misleading comment about "typical" group
 durations

See #918
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 14f76131..28b4b0c5 100644
--- a/index.bs
+++ b/index.bs
@@ -1798,7 +1798,7 @@ Content of a Charter</h3>
 			The scope of the group's work and criteria for success.
 
 		<li>
-			The duration of the group (typically from six months to two years).
+			The duration of the proposed charter for the group.
 
 		<li>
 			The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software).

From a5204cf41ee633b6c1fe100eba96ad878860f000 Mon Sep 17 00:00:00 2001
From: Vivien Lacourba <vivien@w3.org>
Date: Sat, 14 Dec 2024 07:14:24 +0100
Subject: [PATCH 115/237] Fix links (#960)

* Fix link to Revising a Working Draft section

* Member submissions guidebook page moved from https://www.w3.org/2000/09/submission to https://www.w3.org/submissions/guide/

* Update link and title of the Conflict of Interest Policy for the W3C Team
---
 index.bs | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/index.bs b/index.bs
index 28b4b0c5..7d67654b 100644
--- a/index.bs
+++ b/index.bs
@@ -504,7 +504,7 @@ Conflict of Interest Policy</h5>
 
 	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/2000/09/06-conflictpolicy">W3C Team conflict of interest policy</a> [[!CONFLICT-POLICY]].
+	[=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>
@@ -4119,7 +4119,7 @@ Next Steps from W3C Recommendation</h5>
 
 		<li>
 			republished as a <a href="#transition-cr">Candidate Recommendation</a>
-			or <a href="https://www.w3.org/2023/Process-20231103/#revising-wd">Working Draft</a>
+			or <a href="#revising-wd">Working Draft</a>
 			to be developed towards a revised [=Recommendation=], or
 
 		<li>
@@ -5719,8 +5719,8 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"CONFLICT-POLICY": {
-		"href": "https://www.w3.org/2000/09/06-conflictpolicy",
-		"title": "Conflict of Interest Policy for W3C Team Members Engaged in Outside Professional Activities",
+		"href": "https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/",
+		"title": "Conflict of Interest Policy for the W3C Team",
 		"publisher": "W3C"
 	},
 	"TAG-HP": {
@@ -5824,7 +5824,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"MEMBER-SUB": {
-		"href": "https://www.w3.org/2000/09/submission",
+		"href": "https://www.w3.org/submissions/guide/",
 		"title": "Member submissions guidebook",
 		"publisher": "W3C"
 	},

From f06e579fd39be089ab41a93019e6b8f20340e885 Mon Sep 17 00:00:00 2001
From: Vivien Lacourba <vivien@w3.org>
Date: Mon, 16 Dec 2024 11:07:40 +0100
Subject: [PATCH 116/237] Fix links (2nd batch) (#961)

* fix another instance of: Member submissions guidebook page moved from https://www.w3.org/2000/09/submission to https://www.w3.org/submissions/guide/

* Minor editorial fix: [[SUBMISSION-LIST]] biblio reference should be placed before the '.'
---
 index.bs | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index 7d67654b..9f8ba561 100644
--- a/index.bs
+++ b/index.bs
@@ -5199,7 +5199,7 @@ Member Submissions</h2>
 			</ul>
 
 			Detailed procedures and requirements are defined by the [=Team=]
-			and documented in the “<a href="https://www.w3.org/2000/09/submission">Member submissions guidebook</a>” [[MEMBER-SUB]].
+			and documented in the “<a href="https://www.w3.org/submissions/guide/">Member submissions guidebook</a>” [[MEMBER-SUB]].
 
 		<dt>Decision
 		<dd>
@@ -5211,8 +5211,8 @@ Member Submissions</h2>
 					If <dfn>acknowledged</dfn>,
 					the Team <em class="rfc2119">must</em> make the [=Member Submission=] available
 					at the public W3C website
-					alongside other <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a>.
-					[[SUBMISSION-LIST]]
+					alongside other <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a>
+					[[SUBMISSION-LIST]].
 
 				<li>
 					If <dfn>rejected</dfn>,

From 6a8b9e8bd51bef6a2539f388b81490c59d345210 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 20 Dec 2024 16:55:44 +0900
Subject: [PATCH 117/237] Remove stray instance of Proposed Recommendation

Fixes #965
---
 index.bs | 1 -
 1 file changed, 1 deletion(-)

diff --git a/index.bs b/index.bs
index 9f8ba561..565a1933 100644
--- a/index.bs
+++ b/index.bs
@@ -3320,7 +3320,6 @@ Maintenance Without a Group</h4>
 	as defined in the Patent Policy [[PATENT-POLICY]]
 	(i.e., they are not covered by the Patent Policy).
 	For [=Candidate Recommendations=],
-	[=Proposed Recommendations=],
 	[=W3C Recommendations=],
 	[=Candidate Registries=],
 	[=W3C Registries=],

From e04b05a286b3dacee002b2e5bc7e8827476eb25b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 23 Dec 2024 11:10:27 +0900
Subject: [PATCH 118/237] Introduce Good Standing (#954)

See #935
---
 index.bs | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 565a1933..ee964814 100644
--- a/index.bs
+++ b/index.bs
@@ -377,6 +377,15 @@ Related Members</h5>
 	[=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>
 
@@ -1214,7 +1223,7 @@ Advisory Board and Technical Architecture Group Elections</h5>
 	</ul>
 
 	When there is a vote,
-	each Member
+	each Member in [=Good Standing=]
 	(or group of [=related Members=])
 	<em class="rfc2119">may</em> submit one ballot that ranks candidates in the Member's preferred order.
 	Once the deadline for votes has passed,
@@ -2864,6 +2873,8 @@ Appeal by Advisory Committee Representatives</h3>
 
 	[=Advisory Committee representatives=] <em class="rfc2119">may</em> appeal certain decisions,
 	though appeals are only expected to occur in extraordinary circumstances.
+	For the purpose of this section, only [=Advisory Committee representatives=] of
+	[=Members=] in [=Good Standing=] are counted.
 
 	When a [=W3C decision=] is made following an [=Advisory Committee review=],
 	[=Advisory Committee representatives=] <em class="rfc2119">may</em> initiate
@@ -4387,7 +4398,7 @@ Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</h5>
 			where the request was not answered within 90 days
 
 		<li>
-			5% of the members of the Advisory Committee
+			5% of [=Advisory Committee representatives=] of [=Members=] in [=Good Standing=]
 	</ul>
 
 	<p id="proposed-rescinded-rec">The [=Team=] <em class="rfc2119">must</em> then

From 5e9a0d86f61348635625a5ff7929418bf8afd14f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 23 Dec 2024 11:17:10 +0900
Subject: [PATCH 119/237] Update Changelog

---
 index.bs | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/index.bs b/index.bs
index ee964814..9324a373 100644
--- a/index.bs
+++ b/index.bs
@@ -5671,6 +5671,14 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					under Team authority.
 					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a>
 					and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>)
+
+				<li>
+					Reuse the bylaws’ notion of Good Standing,
+					and restrict TAG and AB elections
+					as well as AC Votes where a decision is made based on counting ballots
+					to Members in Good Standing.
+					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a>
+					and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>)
 			</ul>
 
 

From 624237d7948a25acad1436070c8dd2d6a373a616 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 23 Dec 2024 11:18:05 +0900
Subject: [PATCH 120/237] Require documentation of hwo FOs get resolved (#953)

See #870
---
 index.bs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/index.bs b/index.bs
index 9324a373..b8c28fb7 100644
--- a/index.bs
+++ b/index.bs
@@ -2397,6 +2397,9 @@ Registering Formal Objections</h3>
 
 	Registering a [=Formal Objection=] initiates the process of
 	[[#addressing-fo|addressing the Formal Objection]].
+	The resolution of a recorded Formal Objection--
+	whether by a Council decision, adoption of a consensus proposal, retraction of the Formal Objection, etc.--
+	must be recorded and made available at the same level of visibility as the record of the Formal Objection itself.
 
 <h3 id=addressing-fo>
 Addressing Formal Objections</h3>

From d71738c62ccd936d10170079cfe4b9bcdf026cd9 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 23 Dec 2024 11:19:40 +0900
Subject: [PATCH 121/237] Update Changelog

---
 index.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.bs b/index.bs
index b8c28fb7..7b163a06 100644
--- a/index.bs
+++ b/index.bs
@@ -5682,6 +5682,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					to Members in Good Standing.
 					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a>
 					and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>)
+
+				<li>
+					Require documentation of how Formal Objections get resolved.
+					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>)
 			</ul>
 
 

From 09dbace2627cce969764a2f1ade421f45bf00cb8 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 23 Dec 2024 11:21:30 +0900
Subject: [PATCH 122/237] Defer to /Guide for specific mailing lists to send
 review requests to (#952)

See #815
---
 index.bs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 7b163a06..8a5fd664 100644
--- a/index.bs
+++ b/index.bs
@@ -3122,7 +3122,6 @@ Wide Review</h5>
 	The objective is to ensure that the entire set of stakeholders of the Web community,
 	including the general public,
 	have had adequate notice of the progress of the [=Working Group=]
-	(for example through notices posted to <a href="https://lists.w3.org/Archives/Public/public-review-announce/">public-review-announce@w3.org</a>)
 	and were able to actually perform reviews of and provide comments on the specification.
 	A second objective is to encourage groups to request reviews
 	early enough that comments and suggested changes
@@ -3139,6 +3138,8 @@ Wide Review</h5>
 	about appropriate times and which content to review
 	and whether such reviews actually occurred.
 
+	Note: The Team documents <a href="https://www.w3.org/Guide/documentreview/">best practices for wide review</a> in the Guidebook. [[GUIDE]]
+
 	For example,
 	inviting review of new or significantly revised sections published in Working Drafts,
 	and tracking those comments

From f0df4c1a3b8faa04d4a4f3827eee77c83b9fd778 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 23 Dec 2024 11:23:28 +0900
Subject: [PATCH 123/237] Allow for some amount of leeway at the close of
 nomination periods (#950)

See #464
---
 index.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.bs b/index.bs
index 8a5fd664..0e1ccd02 100644
--- a/index.bs
+++ b/index.bs
@@ -1195,6 +1195,10 @@ Advisory Board and Technical Architecture Group Elections</h5>
 	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
 	Each nomination <em class="rfc2119">should</em> include
 	a few informative paragraphs about the nominee.
+	If an identified candidate's nomination information is only partially complete
+	as of the deadline for nominations,
+	the [=Team=] <em class=rfc2119>may</em> allow extra time for that candidate's nomination to be completed,
+	so long as it does not delay the election as a whole.
 
 	If, after the deadline for nominations, the number of nominees is:
 

From 0cbf27e91e54fe439b4539c190531cec91677ba4 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 23 Dec 2024 11:25:31 +0900
Subject: [PATCH 124/237] Update changelog

---
 index.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.bs b/index.bs
index 0e1ccd02..719177e5 100644
--- a/index.bs
+++ b/index.bs
@@ -5691,6 +5691,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 				<li>
 					Require documentation of how Formal Objections get resolved.
 					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>)
+
+				<li>
+					Clarify amount of leeway around incomplete nominations to TAG or AB elections.
+					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>)
 			</ul>
 
 

From d2100da5493c9517b9b737349f7d177ddccce985 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 19 Dec 2024 20:38:10 +0900
Subject: [PATCH 125/237] Decrease emphasis on FO to charter rejection

Team Decisions can be objected to, so it is not necessary to emphasize
that fact. Too much attention to that point could encourage
litigiousness, which would be counter productive.
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 719177e5..15c142ac 100644
--- a/index.bs
+++ b/index.bs
@@ -1754,7 +1754,7 @@ Initiating Charter Refinement</h3>
 	that the [=Team=] initiate [=charter refinement=].
 	The Team <em class=rfc2119>may</em> deny such a request
 	if it thinks the proposal is insufficiently mature or does not align with W3C's scope and mission.
-	This rejection is a [=Team Decision=] which can be <a href="#registering-objections">Formally Objected to</a>.
+	This rejection is a [=Team Decision=].
 
 <h3 id="charter-development" oldids="WGCharterDevelopment">
 Charter Refinement</h3>

From 78079bacc477bd709ab5023a850201058b3e170f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 8 Jan 2025 14:33:06 +0900
Subject: [PATCH 126/237] Simplify note

It is not helpful to highlight potential failure to perform by the Team,
when there is no concern of the Team failing to perform in this area.
---
 index.bs | 1 -
 1 file changed, 1 deletion(-)

diff --git a/index.bs b/index.bs
index 15c142ac..9707a7bb 100644
--- a/index.bs
+++ b/index.bs
@@ -1787,7 +1787,6 @@ Charter Refinement</h3>
 
 	Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together,
 	while allowing [=Formal Objections=] to [=Chartering Facilitator=] misbehavior
-	that the [=Team=] is failing to address
 	to be processed immediately.
 
 	If the discussions have not concluded within the time frame announced in the [=charter review notice=],

From 7ce45be4ddb57c8fd17680778fd0afa962c599a6 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 8 Jan 2025 14:38:12 +0900
Subject: [PATCH 127/237] Fix typo

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 9707a7bb..051b02d5 100644
--- a/index.bs
+++ b/index.bs
@@ -1986,7 +1986,7 @@ Minor Changes to Active Charters</h4>
 	or a change of [=Chair=].
 
 	The [=Team=] <em class=rfc2119>may</em> nevertheless choose
-	initial [=charter refinement=] and/or [=Advisory Committee Review=]
+	to initiate [=charter refinement=] and/or [=Advisory Committee Review=]
 	when it thinks the changes would benefit from more scrutiny or explicit buy-in.
 
 	Though [=Advisory Committee Review=] is not required,

From 808f023f39fb3e645624d098058ad510460ca176 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 9 Jan 2025 01:12:43 +0900
Subject: [PATCH 128/237] Enable the Team (as well as the Group) to push
 charters forward (#970)

See #959
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 051b02d5..2eb69a17 100644
--- a/index.bs
+++ b/index.bs
@@ -1775,7 +1775,7 @@ Charter Refinement</h3>
 		(though only W3C [=Members=] and the [=Team=] can participate in any formal [[#Votes|vote]]).
 
 	The [=charter refinement=] phase concludes when there is either:
-	* A [=group decision=] to initiate [=AC Review=] of the [=charter draft=].
+	* A [=group decision=] or [=Team Decision=] to initiate [=AC Review=] of the [=charter draft=].
 	* A [=chair decision=] by the [=Chartering Facilitator=] to abandon the proposal.
 
 	Any [=Formal Objection=] filed during the  [=charter refinement=] phase--

From b06fe4011f102953687af32c41d7db6063cd3274 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 6 Dec 2024 15:08:17 +0900
Subject: [PATCH 129/237] Be more specific about when the council composition
 is locked down

See #926
---
 index.bs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/index.bs b/index.bs
index 2eb69a17..8af32259 100644
--- a/index.bs
+++ b/index.bs
@@ -2454,6 +2454,10 @@ Council Composition</h5>
 	Membership of each [=Council=] instance is fixed at formation,
 	and is not changed by any [=AB=] or [=TAG=] elections
 	occurring before that Council has reached a conclusion.
+	Specifically, the list of potential [=Council=] members evolves
+	as terms start or end
+	so long as [=dismissal=] has not concluded,
+	but is fixed thereafter.
 	However, if participation in a [=Council=] falls so low as to hinder effective and balanced deliberations,
 	the [=W3C Council Chair=] <em class="rfc2119">should</em> dissolve the [=Council=]
 	and call for a new one to be convened.

From 7df2ef65a0a7caacb210d64e5578be75c017974f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 8 Jan 2025 15:17:05 +0900
Subject: [PATCH 130/237] Improve phrasing

---
 index.bs | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/index.bs b/index.bs
index 8af32259..2485b82f 100644
--- a/index.bs
+++ b/index.bs
@@ -2451,15 +2451,15 @@ Council Composition</h5>
 	Participation in a [=W3C Council=] <em class=rfc2119>must not</em> require attendance of [=face-to-face meetings=].
 
 	A distinct instance of the [=W3C Council=] is convened for each decision being appealed or objected to.
-	Membership of each [=Council=] instance is fixed at formation,
+	The list of potential [=Council=] members evolves
+	as [=AB=] and [=TAG=] terms start and end
+	until [=dismissal=] and [=renunciation=] are concluded,
+	at which point all remaining potential [=Council=] members become full members.
+	Thereafter, the membership of the [=Council=] is fixed,
 	and is not changed by any [=AB=] or [=TAG=] elections
-	occurring before that Council has reached a conclusion.
-	Specifically, the list of potential [=Council=] members evolves
-	as terms start or end
-	so long as [=dismissal=] has not concluded,
-	but is fixed thereafter.
-	However, if participation in a [=Council=] falls so low as to hinder effective and balanced deliberations,
-	the [=W3C Council Chair=] <em class="rfc2119">should</em> dissolve the [=Council=]
+	that occur before that Council has reached a conclusion.
+	However, if the number of active members in a [=Council=] falls so low as to hinder effective and balanced deliberations,
+	the [=Council Chair=] <em class="rfc2119">should</em> dissolve the [=Council=]
 	and call for a new one to be convened.
 
 	A [=Team=] member is assigned

From 1cb4b7376649251a8d1e30effff481eb909f1f16 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 13 Jan 2025 09:58:11 +0900
Subject: [PATCH 131/237] Add explicit Team verification of charter refinement
 (#973)

---
 index.bs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 2485b82f..d6989bf3 100644
--- a/index.bs
+++ b/index.bs
@@ -1775,7 +1775,8 @@ Charter Refinement</h3>
 		(though only W3C [=Members=] and the [=Team=] can participate in any formal [[#Votes|vote]]).
 
 	The [=charter refinement=] phase concludes when there is either:
-	* A [=group decision=] or [=Team Decision=] to initiate [=AC Review=] of the [=charter draft=].
+	* A [=group decision=] or [=Team Decision=] to initiate [=AC Review=] of the [=charter draft=],
+		subject to [=Team=] verification that the expectations of [=charter refinement=] are fulfilled.
 	* A [=chair decision=] by the [=Chartering Facilitator=] to abandon the proposal.
 
 	Any [=Formal Objection=] filed during the  [=charter refinement=] phase--

From 6e3f0deadce8990e22f867475227e5cb08be5250 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 13 Jan 2025 09:59:34 +0900
Subject: [PATCH 132/237] Chartering Facilitators are appointed by the Team,
 and can be replaced (#974)

See https://github.com/w3c/process/issues/969
---
 index.bs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/index.bs b/index.bs
index d6989bf3..33297a60 100644
--- a/index.bs
+++ b/index.bs
@@ -1763,6 +1763,7 @@ Charter Refinement</h3>
 	the W3C community further develops the [=charter draft=]
 	with the goal of achieving [=consensus=] on the proposal.
 	The <dfn>Chartering Facilitator</dfn>
+	--who is chosen (and <em class=rfc2119>may</em> be replaced) by the [=Team=]--
 	acts as [=Chair=] for the [=charter refinement=] process.
 
 	Note: The [=Chartering Facilitator=] is not necessarily (and often is not) the [=Chair=] of the [=chartered group|group=] being chartered.

From d1ae9d32131de6c69617f609ba89c92fdf537858 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 13 Jan 2025 10:02:58 +0900
Subject: [PATCH 133/237] Call out that the Team can share its views on
 proposals under AC review (#975)

---
 index.bs | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/index.bs b/index.bs
index 33297a60..569bed32 100644
--- a/index.bs
+++ b/index.bs
@@ -2731,6 +2731,8 @@ Initiating an Advisory Committee Review</h4>
 	raises attention to deadlines,
 	estimates when the decision will be available,
 	and includes other practical information.
+	The [=Team=] <em class=rfc2119>may</em> share its perspective on the proposal
+	in the [=Call for Review=].
 	Each Member organization <em class="rfc2119">may</em> send one review,
 	which <em class="rfc2119">must</em> be returned by its [=Advisory Committee representative=].
 

From 42b6585f672428a5ab113cd3ec0e834615e1c423 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 13 Jan 2025 09:56:33 +0900
Subject: [PATCH 134/237] Reorder items in list for easier flow

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 569bed32..72c4439a 100644
--- a/index.bs
+++ b/index.bs
@@ -1769,9 +1769,9 @@ Charter Refinement</h3>
 	Note: The [=Chartering Facilitator=] is not necessarily (and often is not) the [=Chair=] of the [=chartered group|group=] being chartered.
 
 	During [=charter refinement=]:
+	* [=Wide review=] of the [=charter draft=] is initiated and completed.
 	* All issues filed against the [=charter draft=] must be [=formally addressed=],
 		and their resolutions tracked in a disposition of comments.
-	* [=Wide review=] of the [=charter draft=] is initiated and completed.
 	* Decisions are made as [=group decisions=], where the group is made up of all individuals participating in this process,
 		(though only W3C [=Members=] and the [=Team=] can participate in any formal [[#Votes|vote]]).
 

From 524b216512bddbf38f7e98f67a059121c75ae15c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 16 Jan 2025 21:52:13 +0900
Subject: [PATCH 135/237] Limit the involvement of Tim Berners-Lee to the TAG
 proper (#792)

As the Council's purpose is to replace his former role as Director in
resolving Formal Objections, this removes him from being part of the
Council. This way, he does not take part in the Council's deliberations,
and is not on the critical path for Council votes or quorum questions,
notably the Council's Unanimous Short Circuit.

See #784

Co-authored-by: chaals <chaals@users.noreply.github.com>
Co-authored-by: Theresa O'Connor <hober0@gmail.com>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 72c4439a..21bc9793 100644
--- a/index.bs
+++ b/index.bs
@@ -2448,7 +2448,7 @@ Council Composition</h5>
 	Each [=W3C Council=] is composed of the following members (excepting any [[#council-participation|renounced or dismissed]]):
 	* the [=CEO=] or their chosen [=Team=] delegate
 	* the members of the [=Advisory Board=]
-	* the members of the [=Technical Architecture Group=]
+	* the elected and appointed members of the [=Technical Architecture Group=]
 
 	Participation in a [=W3C Council=] <em class=rfc2119>must not</em> require attendance of [=face-to-face meetings=].
 

From ae08c4fdb549780ef318099898986da8856b318b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 16 Jan 2025 21:55:05 +0900
Subject: [PATCH 136/237] Update changelog

---
 index.bs | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/index.bs b/index.bs
index 21bc9793..8906aac7 100644
--- a/index.bs
+++ b/index.bs
@@ -5586,6 +5586,11 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					after addressing feedback
 					following an AC Appeal.
 					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
+
+				<li>
+					Limit the involvement of Tim Berners-Lee to the TAG proper,
+					not including the Council.
+					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>)
 			</ul>
 
 		<dt>Changes to technical reports and their publication

From c662357c9b109376a579aa01a9bec1469d7dfce8 Mon Sep 17 00:00:00 2001
From: Vivien Lacourba <vivien@w3.org>
Date: Thu, 16 Jan 2025 15:09:38 +0100
Subject: [PATCH 137/237] Update links to the Guidebook following its redesign
 https://lists.w3.org/Archives/Public/spec-prod/2025JanMar/0001.html (#979)

---
 index.bs | 44 ++++++++++++++++++++++----------------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/index.bs b/index.bs
index 8906aac7..354cb03c 100644
--- a/index.bs
+++ b/index.bs
@@ -293,7 +293,7 @@ Rights of Members</h4>
 			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]])
+			(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>.
@@ -469,7 +469,7 @@ Expectations and Discipline</h5>
 	(b) the membership agreement, or
 	(c) applicable laws,
 	occur.
-	Refer to the <a href="https://www.w3.org/Guide/process/suspension">Guidelines to suspend or remove participants from groups</a>.
+	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>
@@ -915,7 +915,7 @@ Composition of the Advisory Board</h5>
 	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 <a href="https://www.w3.org/Guide/teamcontact/role.html">Team Contact</a>,
+	The team also appoints a <a href="https://www.w3.org/guide/teamcontact/role">Team Contact</a>,
 	as described in <a href="#ReqsAllGroups"></a>.
 	The CEO and Team Contact have a standing invitation
 	to all regular Advisory Board sessions.
@@ -1032,7 +1032,7 @@ Composition of the Technical Architecture Group</h5>
 	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 <a href="https://www.w3.org/Guide/teamcontact/role.html">Team Contact</a> [[TEAM-CONTACT]] for the TAG,
+	The [=Team=] also appoints a <a href="https://www.w3.org/guide/teamcontact/role">Team Contact</a> [[TEAM-CONTACT]] for the TAG,
 	as described in <a href="#ReqsAllGroups"></a>.
 
 	The terms of TAG participants last for <span class="time-interval">two years</span>.
@@ -1434,16 +1434,16 @@ Requirements for All Chartered Groups</h4>
 	(invited by the [=Team=]).
 	The requirements of this document that apply to those types of participants apply to Chairs as well.
 	
-	Note: The <a href="https://www.w3.org/Guide/chair/role.html">role of the Chair</a> [[CHAIR]] is described
-	in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> [[GUIDE]].
+	Note: The <a href="https://www.w3.org/guide/chair/role">role of the Chair</a> [[CHAIR]] is described
+	in the <a href="https://www.w3.org/guide/">Art of Consensus</a> [[GUIDE]].
 
 	Each group <em class="rfc2119">must</em> have a <dfn id="TeamContact" export>Team Contact</dfn>,
 	who acts as the interface between the [=Chair=],
 	group participants,
 	and the rest of the Team.
 	
-	Note: The <a href="https://www.w3.org/Guide/teamcontact/role.html">role of the Team Contact</a> [[TEAM-CONTACT]] 
-	is described in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> [[GUIDE]].
+	Note: The <a href="https://www.w3.org/guide/teamcontact/role">role of the Team Contact</a> [[TEAM-CONTACT]] 
+	is described in the <a href="https://www.w3.org/guide/">Art of Consensus</a> [[GUIDE]].
 				
 	The [=Chair=] and the [=Team Contact=] of a group <em class="rfc2119">should not</em> be the same individual.
 
@@ -1835,7 +1835,7 @@ Content of a Charter</h3>
 		<li>
 			Any dependencies of this group on other groups within or outside of W3C.
 			Such dependencies include interactions with
-			<a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> [[CHARTER]].
+			<a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> [[CHARTER]].
 
 		<li>
 			The <a href="#confidentiality-levels">level of confidentiality</a>
@@ -3142,14 +3142,14 @@ Wide Review</h5>
 	a reasonable opportunity to review the document,
 	who has provided comments,
 	the record of requests to and responses from reviewers,
-	especially <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">W3C Horizontal Groups</a> [[CHARTER]]
+	especially <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> [[CHARTER]]
 	and groups identified as dependencies in the charter
 	or identified as <a href="https://www.w3.org/liaisons/">liaisons</a> [[LIAISON]],
 	and seek evidence of clear communication to the general public
 	about appropriate times and which content to review
 	and whether such reviews actually occurred.
 
-	Note: The Team documents <a href="https://www.w3.org/Guide/documentreview/">best practices for wide review</a> in the Guidebook. [[GUIDE]]
+	Note: The Team documents <a href="https://www.w3.org/guide/documentreview/">best practices for wide review</a> in the Guidebook. [[GUIDE]]
 
 	For example,
 	inviting review of new or significantly revised sections published in Working Drafts,
@@ -3157,7 +3157,7 @@ Wide Review</h5>
 	and the [=Working Group=]'s responses,
 	is generally a good practice which would often be considered positive evidence of wide review.
 	[=Working Groups=]
-	<em class="rfc2119">should</em> follow the <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">W3C Horizontal Groups</a>’ review processes,
+	<em class="rfc2119">should</em> follow the <a href="https://www.w3.org/guide/documentreview/#how-to-get-horizontal-review">W3C Horizontal Groups</a>’ review processes,
 	and <em class="rfc2119">should</em> announce to other W3C Working Groups
 	as well as the general public,
 	especially those affected by this specification,
@@ -4480,7 +4480,7 @@ Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</h5>
 	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 <em class="rfc2119">should</em> link
-	to the explanation of <a href="https://www.w3.org/Guide/process/obsolete-rescinded-supserseded">Obsoleting and Rescinding W3C Specifications</a> [[OBS-RESC]] as appropriate.
+	to the explanation of <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">Obsoleting and Rescinding W3C Specifications</a> [[OBS-RESC]] as appropriate.
 
 	Once W3C has published a Rescinded Recommendation,
 	future W3C technical reports <em class="rfc2119">must not</em> include normative references
@@ -4953,8 +4953,8 @@ Switching Tracks</h3>
 <h3 id="further-reading">
 Further reading</h3>
 
-	Refer to <a href="https://www.w3.org/Guide/transitions/">"How to Organize a Recommendation Track Transition"</a> [[TRANSITION]]
-	in the <a href="https://www.w3.org/Guide/">Art of Consensus</a> [[GUIDE]]
+	Refer to <a href="https://www.w3.org/guide/transitions/">"How to Organize a Recommendation Track Transition"</a> [[TRANSITION]]
+	in the <a href="https://www.w3.org/guide/">Art of Consensus</a> [[GUIDE]]
 	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> [[REC-TIPS]].
@@ -5825,7 +5825,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"GUIDE": {
-		"href": "https://www.w3.org/Guide/",
+		"href": "https://www.w3.org/guide/",
 		"title": "The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators",
 		"publisher": "W3C"
 	},
@@ -5835,7 +5835,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"OBS-RESC": {
-		"href": "https://www.w3.org/Guide/process/obsolete-rescinded-supserseded",
+		"href": "https://www.w3.org/guide/process/obsolete-rescinded-supserseded",
 		"title": "Obsoleting and Rescinding W3C Specifications",
 		"publisher": "W3C"
 	},
@@ -5881,27 +5881,27 @@ Changes since earlier versions</h3>
 		"id": "MEM15"
 	},
 	"TEAM-CONTACT": {
-		"href": "https://www.w3.org/Guide/teamcontact/role.html",
+		"href": "https://www.w3.org/guide/teamcontact/role",
 		"title": "Role of the Team Contact",
 		"publisher": "W3C"
 	},
 	"CHAIR": {
-		"href": "https://www.w3.org/Guide/chair/role.html",
+		"href": "https://www.w3.org/guide/chair/role",
 		"title": "W3C Working/Interest Group Chair",
 		"publisher": "W3C"
 	},
 	"CHARTER": {
-		"href": "https://www.w3.org/Guide/process/charter.html",
+		"href": "https://www.w3.org/guide/process/charter",
 		"title": "How to Create a Working Group or Interest Group",
 		"publisher": "W3C"
 	},
 	"TRANSITION": {
-		"href": "https://www.w3.org/Guide/transitions/",
+		"href": "https://www.w3.org/guide/transitions/",
 		"title": "Organize a Technical Report Transition",
 		"publisher": "W3C"
 	},
 	"DECISION-APPEAL": {
-		"href": "https://www.w3.org/Guide/process/ac-appeal",
+		"href": "https://www.w3.org/guide/process/ac-appeal",
 		"title": "Appealing a W3C Decision",
 		"publisher": "W3C"
 	},

From b38a060d93e42f27b0146a1e1db0cc5a7eb21434 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 20 Jan 2025 16:53:37 +0900
Subject: [PATCH 138/237] Fix punctuation

---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 354cb03c..420df6c1 100644
--- a/index.bs
+++ b/index.bs
@@ -1762,8 +1762,8 @@ Charter Refinement</h3>
 	During <dfn>charter refinement</dfn>,
 	the W3C community further develops the [=charter draft=]
 	with the goal of achieving [=consensus=] on the proposal.
-	The <dfn>Chartering Facilitator</dfn>
-	--who is chosen (and <em class=rfc2119>may</em> be replaced) by the [=Team=]--
+	The <dfn>Chartering Facilitator</dfn>--
+	who is chosen (and <em class=rfc2119>may</em> be replaced) by the [=Team=]--
 	acts as [=Chair=] for the [=charter refinement=] process.
 
 	Note: The [=Chartering Facilitator=] is not necessarily (and often is not) the [=Chair=] of the [=chartered group|group=] being chartered.

From 4f99ea0f7162e9dabfca2e987b4ee9dfcd3830c8 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 20 Jan 2025 16:57:35 +0900
Subject: [PATCH 139/237] Remove parts of notes that have been found to be less
 than helpful

---
 index.bs | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 420df6c1..3c2a8702 100644
--- a/index.bs
+++ b/index.bs
@@ -1766,7 +1766,7 @@ Charter Refinement</h3>
 	who is chosen (and <em class=rfc2119>may</em> be replaced) by the [=Team=]--
 	acts as [=Chair=] for the [=charter refinement=] process.
 
-	Note: The [=Chartering Facilitator=] is not necessarily (and often is not) the [=Chair=] of the [=chartered group|group=] being chartered.
+	Note: The [=Chartering Facilitator=] is not necessarily the [=Chair=] of the [=chartered group|group=] being chartered.
 
 	During [=charter refinement=]:
 	* [=Wide review=] of the [=charter draft=] is initiated and completed.
@@ -1787,9 +1787,7 @@ Charter Refinement</h3>
 	until the close of the [=Advisory Committee Review=] of the charter,
 	and is registered against that [=W3C Decision=].
 
-	Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together,
-	while allowing [=Formal Objections=] to [=Chartering Facilitator=] misbehavior
-	to be processed immediately.
+	Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together.
 
 	If the discussions have not concluded within the time frame announced in the [=charter review notice=],
 	the [=Chartering Facilitator=] must inform the AC

From 781be8f413bab444a8993092b713aa9ab9c6c3e2 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 23 Jan 2025 22:06:48 +0900
Subject: [PATCH 140/237] Remove confusing statement about separate proxies and
 substitute

This just doesn't seem necessary.

Closes #373
---
 index.bs | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index 3c2a8702..85020ead 100644
--- a/index.bs
+++ b/index.bs
@@ -1504,9 +1504,6 @@ Participation in Chartered Groups</h4>
 	including for <a href="#Votes">votes</a>.
 	For the substitute to vote,
 	the participant <em class="rfc2119">must</em> inform the [=Chair=] in writing in advance.
-	As a courtesy to the group,
-	if the substitute is not well-versed in the group's discussions,
-	the regular participant <em class="rfc2119">should</em> authorize another participant to act as <a href="#proxy">proxy</a> for votes.
 
 	To allow rapid progress,
 	Working Groups are intended to be small
@@ -5705,6 +5702,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 				<li>
 					Clarify amount of leeway around incomplete nominations to TAG or AB elections.
 					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>)
+
+				<li>
+					Simplify provisions regarding subsitute representatives and proxies.
+					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
 			</ul>
 
 

From 01a6ec4a10f8d11e67d4a1fb3e5b918eca618898 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 23 Jan 2025 22:12:21 +0900
Subject: [PATCH 141/237] Extend the ability to publish Registries to IG/AB/TAG
 (#972)

See #902

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
---
 index.bs | 32 ++++++++++++++++++--------------
 1 file changed, 18 insertions(+), 14 deletions(-)

diff --git a/index.bs b/index.bs
index 85020ead..0f12d9a1 100644
--- a/index.bs
+++ b/index.bs
@@ -3018,14 +3018,14 @@ Types of Technical Reports</h3>
 
 		<dt>Registries
 		<dd>
-			[=Working Groups=] can also publish [=registries=]
+			[=Chartered groups|Chartered=] and [=elected groups=] can also publish [=registries=]
 			in order to document collections of values or other data.
 			A registry can be published either as a distinct [=registry report=],
 			or directly within a [=Recommendation Track=] document
 			as an [=embedded registry=].
 			[=registry definition|Defining a registry=] requires [=wide review=] and [=consensus=],
 			but once set up, changes to registry entries are lightweight
-			and can even be done without a [=Working Group=].
+			and can even be done without the initiating group's involvement.
 			See [[#registries]] for details.
 	</dl>
 
@@ -4705,7 +4705,7 @@ Registry Definitions</h4>
 			and which is responsible for evaluating whether such requests
 			satisfy the criteria defined in the [=registry definition=].
 
-			The [=custodian=] may be the [=Working Group=], the [=Team=], or a delegated entity.
+			The [=custodian=] may be the initiating group, the [=Team=], or a delegated entity.
 			The [=custodian=] for all [=registry tables=] in a single [=registry=]
 			<em class=rfc2119>should</em> generally be the same entity.
 
@@ -4713,7 +4713,7 @@ Registry Definitions</h4>
 			ceases to exist or to operate as a custodian
 			(e.g., the relevant group is disbanded, or 
 			the custodian is unresponsive to repeated attempts to make contact),
-			and the [=Working Group=] that owns the [=registry definition=] 
+			and the [=chartered group|chartered=] or [=elected group=] that owns the [=registry definition=]
 			is itself <a href="#GeneralTermination">closed</a> or 
 			unresponsive,
 			the [=Team=] <em class=rfc2119>should</em> propose replacing the [=custodian=],
@@ -4724,9 +4724,12 @@ Registry Definitions</h4>
 <h4 id=reg-pub>
 Publishing Registries</h4>
 
-	[=Registries=] can be published either
-	as a stand-alone [=technical report=] on the [=Registry Track=] called a <dfn>registry report</dfn>,
-	or incorporated as part of a [=Recommendation=] as an <dfn oldids="registry-section">embedded registry</dfn>.
+	A [=chartered group|chartered=] or [=elected group=] can publish a [=registry=]
+	as a stand-alone [=technical report=] on the [=Registry Track=],
+	where it is called a <dfn>registry report</dfn>.
+	[=Working Groups=] have the additional option of
+	incorporating a [=registry=] as part of a [=Recommendation=],
+	as an <dfn oldids="registry-section">embedded registry</dfn>.
 
 	The [=registry report=] or [=embedded registry=] <em class=rfc2119>must</em>:
 	<ul>
@@ -4817,22 +4820,22 @@ Updating Registry Tables</h4>
 	(i.e. [[#correction-classes|Class 5 changes]])
 	can be made by re-publishing the [=technical report=] that contains the affected table,
 	without needing to satisfy any other requirements for the publication
-	(not even Working Group consensus, unless this is required by the [=registry definition=]).
+	(not even a [=group decision=], unless this is required by the [=registry definition=]).
 	Such [=registry changes=] do not trigger new [=Advisory Committee Reviews=],
 	nor Exclusion Opportunities,
 	and do not require verification via an [=update request=],
 	even for [=technical reports=] at maturities where this would normally be expected.
 	Such publications can be made
-	even in the absence of a [=Working Group=] chartered to maintain the registry
+	even in the absence of a group chartered to maintain the registry
 	when the [=custodian=] is another entity.
 
 	Note: The custodian is only empowered to make [=registry changes=].
-	If the Working Group establishing the registry wishes
+	If the group establishing the registry wishes
 	to empower the custodian to add commentary on individual entries,
 	this needs to be part of the registry table’s definition.
 	If other changes are desired,
-	they need to be requested of the responsible Working Group--
-	or in the absence of a Working Group, of the Team.
+	they need to be requested of the group responsible for maintaining the [=registry definition=]--
+	or in the absence of such a group, of the Team.
 
 	Changes to the [=registry tables=]
 	made in accordance with [=candidate amendment|candidate=] or [=proposed amendments=] to the [=registry definition=]
@@ -4862,12 +4865,13 @@ Registry Data Reports</h4>
 	is that of the [=technical report=] holding the [=registry definition=].
 
 	Anytime a change is made to a [=registry definition=],
-	the Working Group <em class=rfc2119>must</em> update and republish
+	the group maintaining the [=registry definition=]
+	<em class=rfc2119>must</em> update and republish
 	any document holding the corresponding [=registry tables=]
 	to make it consistent with these changes.
 
 	Given a recorded [=group decision=] to do so,
-	the [=Working Group=]
+	the group maintaining the [=registry definition=]
 	<em class=rfc2119>may</em> republish the [=Registry Data Report=] to incorporate
 	[=editorial changes=].
 

From f4e0c84b1fa65f1d52ed2da4f094fac77275e63b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 23 Jan 2025 22:14:31 +0900
Subject: [PATCH 142/237] Update Change Section

---
 index.bs | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/index.bs b/index.bs
index 0f12d9a1..958adb6f 100644
--- a/index.bs
+++ b/index.bs
@@ -5643,6 +5643,11 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					that described whether and how the Team can maintain technical reports
 					that no longer have a Group chartered to maintain them.
 					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
+
+				<li>
+					Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
+					in addition to Working Groups.
+					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>)
 			</ul>
 
 		<dt>Changes to chartering

From 007923f009c3a21bf11617656926add4a543920f Mon Sep 17 00:00:00 2001
From: Vivien Lacourba <vivien@w3.org>
Date: Tue, 4 Feb 2025 10:33:38 +0100
Subject: [PATCH 143/237] Several documents merged in the guidebook as part of
 https://github.com/w3c/guide/pull/303 (#985)

https://www.w3.org/2002/05/rec-tips
  => https://www.w3.org/guide/standards-track/rec-tips

https://www.w3.org/2003/01/republishing/
  => https://www.w3.org/guide/standards-track/republishing

https://www.w3.org/2002/10/election-howto
  => https://www.w3.org/guide/process/election
---
 index.bs | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index 958adb6f..721d7730 100644
--- a/index.bs
+++ b/index.bs
@@ -1242,7 +1242,7 @@ Advisory Board and Technical Architecture Group Elections</h5>
 	the <a href="#random">verifiable random selection procedure</a> described below
 	will be used to assign the incomplete term.
 
-	Refer to <a href="https://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a> [[ELECTION-HOWTO]]
+	Refer to <a href="https://www.w3.org/guide/process/election">How to Organize an Advisory Board or TAG election</a> [[ELECTION-HOWTO]]
 	for more details.
 
 <h5 id="TAG-appointments">
@@ -4956,8 +4956,8 @@ Further reading</h3>
 	in the <a href="https://www.w3.org/guide/">Art of Consensus</a> [[GUIDE]]
 	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> [[REC-TIPS]].
-	Please see also the <a href="https://www.w3.org/2003/01/republishing/">Requirements for modification of W3C Technical Reports</a> [[REPUBLISHING]].
+	and <a href="https://www.w3.org/guide/standards-track/rec-tips">tips on getting to Recommendation faster</a> [[REC-TIPS]].
+	Please see also the <a href="https://www.w3.org/guide/standards-track/republishing">Requirements for modification of W3C Technical Reports</a> [[REPUBLISHING]].
 
 <h2 id="dissemination"> <span id="chapterDissemination"></span>
 Dissemination Policies</h2>
@@ -5783,7 +5783,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"REC-TIPS": {
-		"href": "https://www.w3.org/2002/05/rec-tips",
+		"href": "https://www.w3.org/guide/standards-track/rec-tips",
 		"title": "Tips for Getting to Recommendation Faster",
 		"publisher": "W3C"
 	},
@@ -5823,7 +5823,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"REPUBLISHING": {
-		"href": "https://www.w3.org/2003/01/republishing/",
+		"href": "https://www.w3.org/guide/standards-track/republishing",
 		"title": "In-place modification of W3C Technical Reports",
 		"publisher": "W3C"
 	},
@@ -5883,7 +5883,7 @@ Changes since earlier versions</h3>
 		"publisher": "W3C"
 	},
 	"ELECTION-HOWTO": {
-		"href": "https://www.w3.org/2002/10/election-howto",
+		"href": "https://www.w3.org/guide/process/election",
 		"title": "How to Organize an Advisory Board or TAG election",
 		"publisher": "W3C",
 		"id": "MEM15"

From a77d90ad879bbb23235429a769fc5764cd54d9ac Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 13 Feb 2025 00:45:41 +0900
Subject: [PATCH 144/237] Handle FOs, not mere dissent, after a REC's AC Review
 (#987)

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 721d7730..2f2b681b 100644
--- a/index.bs
+++ b/index.bs
@@ -4106,11 +4106,12 @@ Initiating Review</h5>
 <h5 id="rec-review-resolution">
 Resolution of Review</h5>
 
-	If there was any [=dissent=] in Advisory Committee reviews,
-	the [=Team=] <em class="rfc2119">must</em> publish the substantive content of the dissent
+	If there was any [=Formal Objection=] during the [=Advisory Committee Review=],
+	the [=Team=] <em class="rfc2119">must</em> publish the substantive content of the [=dissent=]
 	to W3C and the general public,
-	and <em class="rfc2119">must</em> [=formally address=] the comment
-	at least 14 days before publication as a [=W3C Recommendation=].
+	and the [=W3C Recommendation=] <em class="rfc2119">must not</em> be published
+	unless all [=Formal Objections=] to the document have been retracted or [=overruled=]
+	and at least 14 days have elapsed since the publication of the corresponding [=Council Report=].
 
 	The decision to advance a document to [=Recommendation=]
 	is a [=W3C Decision=].

From 9d444fc923600607d7ec0cd0d280642c4fcd24d5 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 13 Feb 2025 01:09:07 +0900
Subject: [PATCH 145/237] Require decision by both the facilitator and team to
 abandon chartering (#983)

See #982

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 2f2b681b..68073ea3 100644
--- a/index.bs
+++ b/index.bs
@@ -1772,10 +1772,10 @@ Charter Refinement</h3>
 	* Decisions are made as [=group decisions=], where the group is made up of all individuals participating in this process,
 		(though only W3C [=Members=] and the [=Team=] can participate in any formal [[#Votes|vote]]).
 
-	The [=charter refinement=] phase concludes when there is either:
+	The [=charter refinement=] phase concludes when there is either of the following:
 	* A [=group decision=] or [=Team Decision=] to initiate [=AC Review=] of the [=charter draft=],
 		subject to [=Team=] verification that the expectations of [=charter refinement=] are fulfilled.
-	* A [=chair decision=] by the [=Chartering Facilitator=] to abandon the proposal.
+	* A [=chair decision=] by the [=Chartering Facilitator=], confirmed by a [=Team Decision=], to abandon the proposal.
 
 	Any [=Formal Objection=] filed during the  [=charter refinement=] phase--
 	other than an objection to the choice of [=Chartering Facilitator=]

From 5d3f7458d8d0a141faa45d36eaa5c10ebd3d8000 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Sun, 23 Feb 2025 17:40:00 +0900
Subject: [PATCH 146/237] Fix markup mistakes

---
 index.bs | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/index.bs b/index.bs
index 68073ea3..876f670d 100644
--- a/index.bs
+++ b/index.bs
@@ -928,7 +928,7 @@ Composition of the Advisory Board</h5>
 	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.</p>
+	Regular Advisory Board terms begin on 1 July and end on 30 June.
 
 <h5 id=ab-comm>
 Communications of the Advisory Board</h5>
@@ -1306,7 +1306,7 @@ Verifiable Random Selection Procedure</h5>
 	(listed in alphabetical order by family name unless otherwise specified)
 	into a “result order”.
 
-	W3C applies this procedure as follows:</p>
+	W3C applies this procedure as follows:
 
 	<ol>
 		<li>
@@ -3255,7 +3255,7 @@ Errata Management</h4>
 	the term “<dfn lt="erratum | errata" export>erratum</dfn>”
 	(plural “errata”) refers to any error
 	that can be resolved by one or more changes in classes 1-3
-	of section [[#correction-classes]]</a>.
+	of section [[#correction-classes]].
 
 	[=Working Groups=] <em class="rfc2119">must</em> keep
 	a public record of errors
@@ -3737,7 +3737,7 @@ Advancement on the Recommendation Track</h4>
 	or [=Candidate Recommendation=]
 	will not normally be approved
 	while a [=Working Group=]'s [=charter=] is undergoing or awaiting a decision
-	on an [=Advisory Committee Review=].</p>
+	on an [=Advisory Committee Review=].
 
 <h4 id="update-reqs">
 Updating Mature Publications on the Recommendation Track</h4>
@@ -4905,7 +4905,7 @@ Specifications that Reference Registries</h4>
 		For example
 		 <span class=allow-2119>“All implementations must recognize the name <code>Basic-Method</code>,
 		and implement it as defined by section yy of IETF RFC xxxx”</span>.
-		(The Registry is nonetheless expected to contain </code>Basic-Method</code> as an entry.)
+		(The Registry is nonetheless expected to contain <code>Basic-Method</code> as an entry.)
 	</div>
 
 <h4 id=reg-pat>

From e21a91e7b48a48e1a23127d265ee4a6d187a6e6f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Sun, 23 Feb 2025 17:41:25 +0900
Subject: [PATCH 147/237] Fix Bikeshed reference

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 876f670d..5bfcb029 100644
--- a/index.bs
+++ b/index.bs
@@ -2574,7 +2574,7 @@ Short Circuit</h5>
 <h5 id=council-chairing>
 Council Chairing</h5>
 
-	The <dfn lt="W3C Council Chair">Chair</dfn> of each W3C Council is chosen by its members,
+	The <dfn lt="W3C Council Chair | Council Chair">Chair</dfn> of each W3C Council is chosen by its members,
 	by consensus if possible,
 	falling back to a vote if that fails.
 	The chair must be a member of that [=W3C Council=].

From eb8f4701f2563a5c1e6f5ceafabf79173ea16de2 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Sun, 23 Feb 2025 17:41:58 +0900
Subject: [PATCH 148/237] Delete unnecessary / unreferenced dfn

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 5bfcb029..cd83629c 100644
--- a/index.bs
+++ b/index.bs
@@ -2264,7 +2264,7 @@ Deciding by Vote</h4>
 
 	If a participant is unable to attend a vote,
 	that individual <em class="rfc2119">may</em> authorize anyone at the meeting
-	to act as a <dfn id="proxy">proxy</dfn>.
+	to act as a proxy.
 	The absent participant <em class="rfc2119">must</em> inform the Chair in writing
 	who is acting as proxy, with written instructions on the use of the proxy.
 	For a Working Group or Interest Group,

From 20b5365d2fb06db6dbb2d21d3c27b2800f8de140 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 25 Feb 2025 16:01:14 +0900
Subject: [PATCH 149/237] Use appeal vote as escalation path for rejecting
 charter refinement

This takes inspiration from parts of a proposal by @ianbjacobs.

Invoking W3C Councils is a time consuming and expensive endeavour, so we
should look at cheaper ways to address escalation against the decision
not to start charter refinement.

Since charter refinement is unlikely to be successful if not enough
members are interested, dismissing the escalation when it is supported
by fewer than 5 members seems like a cost effective filter.
When there are 5 or more, an appeals vote is a more cost effective way
to decide the question than an Council, and since this is only about the
start of charter refinement, deep discussions, such as those that a
Council would enable, don't seem necessary.
---
 index.bs | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index cd83629c..032d2aae 100644
--- a/index.bs
+++ b/index.bs
@@ -1751,7 +1751,13 @@ Initiating Charter Refinement</h3>
 	that the [=Team=] initiate [=charter refinement=].
 	The Team <em class=rfc2119>may</em> deny such a request
 	if it thinks the proposal is insufficiently mature or does not align with W3C's scope and mission.
-	This rejection is a [=Team Decision=].
+	This rejection is a [=Team Decision=],
+	and can be appealed only if 5 or more [=Members=],
+	through their [=Advisory Committee representative=],
+	formally object to the decision within X weeks of the decision being announced.
+	In this case the [=Team=] <em class=rfc2119>must</em> start an [=appeal vote=]
+	on whether to overturn the [=Team Decision=].
+	(No action is required to be taken when fewer than 5 members object.)
 
 <h3 id="charter-development" oldids="WGCharterDevelopment">
 Charter Refinement</h3>
@@ -2873,7 +2879,7 @@ Advisory Committee Votes</h3>
 
 	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 [=Advisory Committee Appeal=]
-	achieving the required support to trigger an appeal vote.
+	achieving the required support to trigger an [=appeal vote=].
 	Whenever the [=Advisory Committee=] votes,
 	each Member or group of [=related Members=] has one vote.
 
@@ -2921,7 +2927,7 @@ Appeal by Advisory Committee Representatives</h3>
 	The archive of these statements <em class="rfc2119">must</em> be [=member-only=].
 	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
+	the Team <em class="rfc2119">must</em> organize an <dfn>appeal vote</dfn>
 	asking the [=Advisory Committee=]
 	“Do you approve of the Decision?”
 	together with links to the decision and the appeal support.

From 3be73e4b953ec491431f23d6cf329a13527a7759 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 25 Feb 2025 19:35:13 +0900
Subject: [PATCH 150/237] Enable 5 members to push for resuming an abandoned
 charter refinement

This takes inspiration from parts of a proposal by @ianbjacobs.

The Council is a powerful but expensive way to resolve disagreements.

If a very limited number of members oppose abandoning a
charter-in-progress, the charter would fail AC Review anyway, and
abandoning was the right decision.

If 5 or more Members insist that abandoning the charter refinement was
the wrong decision, that is a strong indication that there is enough
interest and that the decision was premature. The charter may not quite
be ready for AC Review yet, but enough people have hope that it can
become ready that resuming discussions is the appropriate default
reaction. The facilitator remains the arbiter of how much more effort to
spend on the attempt, and of when to send the draft to the AC for
review.

Nevertheless, the Team may judge that despite pronounced member
interest, the situation is inextricable, and that no charter can be
produced that could be worth sending to the AC for review. In that case,
the Team can refer the case to the Council, hoping to gain approval for
the decision to abandon.
---
 index.bs | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index 032d2aae..b8353417 100644
--- a/index.bs
+++ b/index.bs
@@ -1783,12 +1783,18 @@ Charter Refinement</h3>
 		subject to [=Team=] verification that the expectations of [=charter refinement=] are fulfilled.
 	* A [=chair decision=] by the [=Chartering Facilitator=], confirmed by a [=Team Decision=], to abandon the proposal.
 
-	Any [=Formal Objection=] filed during the  [=charter refinement=] phase--
-	other than an objection to the choice of [=Chartering Facilitator=]
-	or to a decision to abandon the proposal--
-	is not considered [[#registering-objections|registered]]
-	until the close of the [=Advisory Committee Review=] of the charter,
-	and is registered against that [=W3C Decision=].
+	[=Formal Objections=] filed during the [=charter refinement=] phase
+	are specially handled:
+	* Objections to the choice of [=Chartering Facilitator=] are processed normally (See [[#addressing-fo]]).
+	* Objections to abandoning the proposal can be appealed only if 5 or more Members,
+		through their [=Advisory Committee representative=],
+		formally object to the decision within X weeks of the decision being announced.
+		In this case, the [=Team=] must either resume charter refinement
+		or refer the matter to the [=Council=].
+		(No action is required to be taken when fewer than 5 members object.)
+	* All other objections are considered registered
+		at the close of the [=Advisory Committee Review=] of the charter,
+		and are registered against that [=W3C Decision=].
 
 	Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together.
 

From cbc8f0919fcbdd7c3cec2c784ac96f97f547903e Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 25 Feb 2025 22:58:34 +0900
Subject: [PATCH 151/237] Phrasing / framing improvements on Chartering

Adopt (and adapt) some changes about how the phases of charter
development are introduced and described from suggestions made by
@ianbjacobs.

The intent is to give more clarity as to the goal of the various phases,
and about the role played by the Team.
---
 index.bs | 36 +++++++++++++++++++++++++-----------
 1 file changed, 25 insertions(+), 11 deletions(-)

diff --git a/index.bs b/index.bs
index b8353417..83d43cc0 100644
--- a/index.bs
+++ b/index.bs
@@ -1718,18 +1718,29 @@ Team Representative in an Interest Group</h5>
 <h2 id=group-lifecycle>
 Lifecycle of Chartered Groups</h2>
 
-	W3C creates [=charters=] for [=chartered groups=] based on interest from the [=Members=] and [=Team=].
-	[=Charters=] are formally approved through an [=AC Review=] and [=W3C Decision=] (see [[#CharterReview]]).
-	Prior to [=AC Review=],
-	<dfn>charter drafts</dfn> go through a public [=charter refinement=] phase
-	during which the [=charter=] receives [=wide review=]
-	and the [=Chartering Facilitator=] attempts to find [=consensus=] on the charter.
-	The [=Team=] <em class=rfc2119>may</em> send notice to the [=AC=]
-	when starting development of a new charter prior to the [=charter refinement=] phase.
+	W3C creates [=charters=] for [=chartered groups=] based on W3C community interest.
+	W3C fosters awareness of [=charters=],
+	improves their quality,
+	and gauges Membership support in two formal phases:
+	* A [=charter refinement|refinement=] phase helps ensure [=charters=] are mission-aligned,
+		reflect community input and [=consensus=],
+		and have been well-socialized
+		and [=wide review|widely reviewed=].
+	* [=Charters=] the are formally approved through an [=AC Review=] and [=W3C Decision=] (see [[#CharterReview]]).
 
 <h3 id="charter-initiation">
 Initiating Charter Refinement</h3>
 
+	[=Charters=] can originate in many venues,
+	including existing [=Working Group|Working=] or [=Interest Groups=],
+	Community Groups,
+	and from the [=W3C Members|Membership=].
+	Prior to the formal [=charter refinement|refinement=] phase,
+	the [=Team=] engages with those various parties
+	to help prepare [=charters=] for broader audiences.
+	The [=Team=] <em class=rfc2119>may</em> send notice to the [=AC=]
+	when starting development of a new charter prior to the [=charter refinement=] phase.
+
 	Formal [=charter refinement=] (see below) is initiated
 	by the [=Team=] sending a [=charter review notice=]
 	to the [=Advisory Committee=],
@@ -1738,7 +1749,7 @@ Initiating Charter Refinement</h3>
 
 	This <dfn>charter review notice</dfn> must include:
 	* A short summary of the proposal.
-	* The location of the [=charter draft=], which must be public.
+	* The location of the <dfn>charter draft</dfn>, which must be public.
 	* How to participate in the discussion of this [=charter draft=] and where to file issues.
 	* The expected duration of the [=charter refinement=] phase,
 		which must not be less than 28 days,
@@ -1763,11 +1774,14 @@ Initiating Charter Refinement</h3>
 Charter Refinement</h3>
 
 	During <dfn>charter refinement</dfn>,
-	the W3C community further develops the [=charter draft=]
+	the W3C community,
+	under the guidance of the [=Team=],
+	further develops the [=charter draft=]
 	with the goal of achieving [=consensus=] on the proposal.
 	The <dfn>Chartering Facilitator</dfn>--
 	who is chosen (and <em class=rfc2119>may</em> be replaced) by the [=Team=]--
-	acts as [=Chair=] for the [=charter refinement=] process.
+	acts as [=Chair=] for the [=charter refinement=] process,
+	and is responsible for seeking community consensus among those participating in the refinement process.
 
 	Note: The [=Chartering Facilitator=] is not necessarily the [=Chair=] of the [=chartered group|group=] being chartered.
 

From 20d28203906e3d809f48040140bb43b198773523 Mon Sep 17 00:00:00 2001
From: chaals <chaals@users.noreply.github.com>
Date: Thu, 27 Feb 2025 04:12:56 +0100
Subject: [PATCH 152/237] Update mission to match https://www.w3.org/mission/

Co-authored-by: Florian Rivoal <git@florian.rivoal.net>
---
 index.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 83d43cc0..2288f589 100644
--- a/index.bs
+++ b/index.bs
@@ -39,8 +39,9 @@ Level: none
 Repository: w3c/process
 Shortname: process
 Abstract:
-	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 <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.

From 73a574dbd0790766836ceb695368e044658dbf4d Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 11 Mar 2025 18:08:16 +0900
Subject: [PATCH 153/237] [editorial] Add paragraph break

---
 index.bs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/index.bs b/index.bs
index 2288f589..11804008 100644
--- a/index.bs
+++ b/index.bs
@@ -1759,6 +1759,7 @@ Initiating Charter Refinement</h3>
 
 	The [=Team=] is responsible for initiating [=charter refinement=]
 	at its discretion, in consideration of discussions with the community.
+
 	An [=Advisory Committee representative=] <em class=rfc2119>may</em> formally request
 	that the [=Team=] initiate [=charter refinement=].
 	The Team <em class=rfc2119>may</em> deny such a request

From 0d6e9c4ef502a987b9a1d60f54d4ad78f3f212e2 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 11 Mar 2025 18:10:32 +0900
Subject: [PATCH 154/237] [editorial] Minor phrasing tweak

Reads better, no change in meaning.
---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 11804008..eb1c485d 100644
--- a/index.bs
+++ b/index.bs
@@ -1765,9 +1765,9 @@ Initiating Charter Refinement</h3>
 	The Team <em class=rfc2119>may</em> deny such a request
 	if it thinks the proposal is insufficiently mature or does not align with W3C's scope and mission.
 	This rejection is a [=Team Decision=],
-	and can be appealed only if 5 or more [=Members=],
+	and can be appealed only by 5 or more [=Members=],
 	through their [=Advisory Committee representative=],
-	formally object to the decision within X weeks of the decision being announced.
+	formally objecting to the decision within X weeks of the decision being announced.
 	In this case the [=Team=] <em class=rfc2119>must</em> start an [=appeal vote=]
 	on whether to overturn the [=Team Decision=].
 	(No action is required to be taken when fewer than 5 members object.)

From b08c50564c52f25532636131a57d5990d4dfa406 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 13 Mar 2025 00:02:27 +0900
Subject: [PATCH 155/237] Give some details about DoCs in charter refinement
 (#996)

The concept of a disposition of comment is understood, but understanding
of what it needs to cover varies depending on who you ask. This sets a
minimum bar for what it needs to have.
---
 index.bs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index eb1c485d..3d542f7b 100644
--- a/index.bs
+++ b/index.bs
@@ -1790,7 +1790,8 @@ Charter Refinement</h3>
 	During [=charter refinement=]:
 	* [=Wide review=] of the [=charter draft=] is initiated and completed.
 	* All issues filed against the [=charter draft=] must be [=formally addressed=],
-		and their resolutions tracked in a disposition of comments.
+		and their resolutions tracked in a disposition of comments
+		highlighting any issues not resolved by consensus.
 	* Decisions are made as [=group decisions=], where the group is made up of all individuals participating in this process,
 		(though only W3C [=Members=] and the [=Team=] can participate in any formal [[#Votes|vote]]).
 

From 3a301fd20596f063ea064f10c3c9f5e1e3c8396e Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 13 Mar 2025 00:17:38 +0900
Subject: [PATCH 156/237] Be explicit that Team rejections must be motivated
 (#995)

More details about typical motivations can go in /Guide
---
 index.bs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 3d542f7b..e2396ffc 100644
--- a/index.bs
+++ b/index.bs
@@ -1763,7 +1763,8 @@ Initiating Charter Refinement</h3>
 	An [=Advisory Committee representative=] <em class=rfc2119>may</em> formally request
 	that the [=Team=] initiate [=charter refinement=].
 	The Team <em class=rfc2119>may</em> deny such a request
-	if it thinks the proposal is insufficiently mature or does not align with W3C's scope and mission.
+	if it thinks the proposal is insufficiently mature or does not align with W3C's scope and mission,
+	and <em class=rfc2119>must</em> reply with its rationale.
 	This rejection is a [=Team Decision=],
 	and can be appealed only by 5 or more [=Members=],
 	through their [=Advisory Committee representative=],

From cf784bdc8de8a146e59229fa5ce64310a799a6d5 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 13 Mar 2025 00:17:56 +0900
Subject: [PATCH 157/237] Pick a number of weeks (#994)

We merged earlier pull requests leaving "X weeks" as an unspecified
number. Make that 8.
---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index e2396ffc..52eabd80 100644
--- a/index.bs
+++ b/index.bs
@@ -1768,7 +1768,7 @@ Initiating Charter Refinement</h3>
 	This rejection is a [=Team Decision=],
 	and can be appealed only by 5 or more [=Members=],
 	through their [=Advisory Committee representative=],
-	formally objecting to the decision within X weeks of the decision being announced.
+	formally objecting to the decision within 8 weeks of the decision being announced.
 	In this case the [=Team=] <em class=rfc2119>must</em> start an [=appeal vote=]
 	on whether to overturn the [=Team Decision=].
 	(No action is required to be taken when fewer than 5 members object.)
@@ -1806,7 +1806,7 @@ Charter Refinement</h3>
 	* Objections to the choice of [=Chartering Facilitator=] are processed normally (See [[#addressing-fo]]).
 	* Objections to abandoning the proposal can be appealed only if 5 or more Members,
 		through their [=Advisory Committee representative=],
-		formally object to the decision within X weeks of the decision being announced.
+		formally object to the decision within 8 weeks of the decision being announced.
 		In this case, the [=Team=] must either resume charter refinement
 		or refer the matter to the [=Council=].
 		(No action is required to be taken when fewer than 5 members object.)

From c577441036153c1d2292f15994b08bbb9fc22734 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 21 Mar 2025 17:23:10 +0900
Subject: [PATCH 158/237] Improve markup/typography (#988)

See https://github.com/speced/bikeshed/issues/2948
---
 index.bs | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/index.bs b/index.bs
index 52eabd80..3ced3097 100644
--- a/index.bs
+++ b/index.bs
@@ -2035,8 +2035,8 @@ Call for Participation in a Chartered Group</h3>
 	the [=Team=] <em class="rfc2119">must</em> issue a Call for Participation to the Advisory Committee.
 	For a new group, this announcement officially creates the group.
 	The announcement <em class="rfc2119">must</em> include a reference to the <a href="#WGCharter">charter</a>,
-	the name(s) of the group's [=Chair=](s),
-	and the name(s) of the [=Team Contact=](s).
+	the name(s) of the group's [=Chair(s)=],
+	and the name(s) of the [=Team Contact(s)=].
 
 	After a Call for Participation,
 	any <a href="#member-rep">Member representatives</a>
@@ -2068,7 +2068,7 @@ Charter Extension</h3>
 	a reference to the <a href="#WGCharter">charter</a>,
 	and the Group homepage
 	(which includes at least
-	the name(s) of the group's [=Chair=](s),
+	the name(s) of the group's [=Chair(s)=],
 	the name of the [=Team Contact=],
 	and instructions for joining the group).
 
@@ -2710,7 +2710,7 @@ Council Decision Report</h5>
 		which <em class=rfc2119>should</em> address each argument raised in the Formal Objection(s).
 	* <em class=rfc2119>must</em> include any recommendation decided by the [=Council=].
 	* if the [=Formal Objection=] has been upheld, <em class=rfc2119>should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.
-	* <em class=rfc2119>must</em> include the [=Minority Opinion=](s), if any.
+	* <em class=rfc2119>must</em> include the [=Minority Opinion(s)=], if any.
 	* <em class=rfc2119>must</em> report the names of those who were [=dismissed=] or [=renounced=] their seat as well as those who were qualified to serve.
 	* <em class=rfc2119>must</em> report the names of the individuals who participated in the final decision.
 	* <em class=rfc2119>must</em> report the number of votes for/against dismissing each participant.
@@ -5233,7 +5233,7 @@ Member Submissions</h2>
 			One of the [=Submitters=],
 			copying the [=Advisory Committee representatives=] of the other [=Submitters=] (if any),
 			sends a request to the Team to acknowledge the Submission request.
-			The [=Team=] and [=Submitter=](s) communicate to ensure that the [=Member Submission=] is complete.
+			The [=Team=] and [=Submitter(s)=] communicate to ensure that the [=Member Submission=] is complete.
 
 		<dt>Review
 		<dd>
@@ -5243,7 +5243,7 @@ Member Submissions</h2>
 
 			<ul>
 				<li>
-					The [=Submitter=](s)
+					The [=Submitter(s)=]
 					and any other authors of the submitted material
 					<em class=rfc2119>must</em> agree
 					to license the Submission under the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> [[!DOC-LICENSE]].
@@ -5271,13 +5271,13 @@ Member Submissions</h2>
 
 				<li>
 					If <dfn>rejected</dfn>,
-					the [=Team=] <em class=rfc2119>must</em> inform the [=Advisory Committee representative=](s) of the [=Submitter=](s),
-					and <em class=rfc2119>must</em> provide rationale if requested by the [=Submitter=](s).
-					The [=Submitter=](s) <em class=rfc2119>may</em> initiate a [=Submission Appeal=].
+					the [=Team=] <em class=rfc2119>must</em> inform the [=Advisory Committee representative(s)=] of the [=Submitter(s)=],
+					and <em class=rfc2119>must</em> provide rationale if requested by the [=Submitter(s)=].
+					The [=Submitter(s)=] <em class=rfc2119>may</em> initiate a [=Submission Appeal=].
 			</ul>
 	</dl>
 
-	The [=Advisory Committee representative=](s) of the [=Submitters=](s)
+	The [=Advisory Committee representative(s)=] of the [=Submitter(s)=]
 	<em class="rfc2119">may</em> initiate a [=Submission Appeal=].
 	The procedure for handling <dfn>Submission Appeals</dfn> is the same as for [=Formal Objections=],
 	except that an [=AC Appeal=] is not possible

From 4599772f6a3d45ff5e45d497535163b72f9dedb9 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 12 Mar 2025 14:32:32 +0900
Subject: [PATCH 159/237] Define the role of the Facilitator without reference
 to being a chair

---
 index.bs | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 3ced3097..62cf6c4b 100644
--- a/index.bs
+++ b/index.bs
@@ -1783,8 +1783,8 @@ Charter Refinement</h3>
 	with the goal of achieving [=consensus=] on the proposal.
 	The <dfn>Chartering Facilitator</dfn>--
 	who is chosen (and <em class=rfc2119>may</em> be replaced) by the [=Team=]--
-	acts as [=Chair=] for the [=charter refinement=] process,
-	and is responsible for seeking community consensus among those participating in the refinement process.
+	is responsible for seeking community consensus among those participating in the refinement process
+	and making decisions reflecting that consensus.
 
 	Note: The [=Chartering Facilitator=] is not necessarily the [=Chair=] of the [=chartered group|group=] being chartered.
 
@@ -1793,8 +1793,6 @@ Charter Refinement</h3>
 	* All issues filed against the [=charter draft=] must be [=formally addressed=],
 		and their resolutions tracked in a disposition of comments
 		highlighting any issues not resolved by consensus.
-	* Decisions are made as [=group decisions=], where the group is made up of all individuals participating in this process,
-		(though only W3C [=Members=] and the [=Team=] can participate in any formal [[#Votes|vote]]).
 
 	The [=charter refinement=] phase concludes when there is either of the following:
 	* A [=group decision=] or [=Team Decision=] to initiate [=AC Review=] of the [=charter draft=],

From 7bcbe7acf21760c8dfa6bcd19a51e57e52b37122 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 12 Mar 2025 14:51:05 +0900
Subject: [PATCH 160/237] Make all ways to end the refinement phase be a team
 decision

---
 index.bs | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index 62cf6c4b..cc57e396 100644
--- a/index.bs
+++ b/index.bs
@@ -1783,8 +1783,8 @@ Charter Refinement</h3>
 	with the goal of achieving [=consensus=] on the proposal.
 	The <dfn>Chartering Facilitator</dfn>--
 	who is chosen (and <em class=rfc2119>may</em> be replaced) by the [=Team=]--
-	is responsible for seeking community consensus among those participating in the refinement process
-	and making decisions reflecting that consensus.
+	is responsible for seeking community [=consensus=] among those participating in the refinement process
+	and making decisions reflecting that [=consensus=].
 
 	Note: The [=Chartering Facilitator=] is not necessarily the [=Chair=] of the [=chartered group|group=] being chartered.
 
@@ -1794,10 +1794,11 @@ Charter Refinement</h3>
 		and their resolutions tracked in a disposition of comments
 		highlighting any issues not resolved by consensus.
 
-	The [=charter refinement=] phase concludes when there is either of the following:
-	* A [=group decision=] or [=Team Decision=] to initiate [=AC Review=] of the [=charter draft=],
-		subject to [=Team=] verification that the expectations of [=charter refinement=] are fulfilled.
-	* A [=chair decision=] by the [=Chartering Facilitator=], confirmed by a [=Team Decision=], to abandon the proposal.
+	The [=charter refinement=] phase concludes
+	when there is a [=Team Decision=]
+	(informed by the work of the [=Chartering Facilitator=])
+	either to initiate [=AC Review=] of the [=charter draft=],
+	or to abandon the proposal.
 
 	[=Formal Objections=] filed during the [=charter refinement=] phase
 	are specially handled:

From 3630ccd05b6e529f534d06f95f23deefdda4481b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 27 Mar 2025 01:01:54 +0900
Subject: [PATCH 161/237] Clarify what happens in the absence of consensus

---
 index.bs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/index.bs b/index.bs
index cc57e396..0c3a9722 100644
--- a/index.bs
+++ b/index.bs
@@ -1785,6 +1785,9 @@ Charter Refinement</h3>
 	who is chosen (and <em class=rfc2119>may</em> be replaced) by the [=Team=]--
 	is responsible for seeking community [=consensus=] among those participating in the refinement process
 	and making decisions reflecting that [=consensus=].
+	In cases where [=consensus=] cannot be found,
+	the [=Chartering Facilitator=] <em class=rfc2119>may</em> ask the [=Team=] to make a [=Team Decision=],
+	and <em class=rfc2119>must</em> document the rationale for the decision.
 
 	Note: The [=Chartering Facilitator=] is not necessarily the [=Chair=] of the [=chartered group|group=] being chartered.
 

From 1df443d622ab3ce5db975f052ff9a91923d7cad5 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 26 Mar 2025 13:39:55 +0900
Subject: [PATCH 162/237] Reframe the various kinds of Objection handling for
 charter refinement

---
 index.bs | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index 0c3a9722..b188469d 100644
--- a/index.bs
+++ b/index.bs
@@ -1805,16 +1805,17 @@ Charter Refinement</h3>
 
 	[=Formal Objections=] filed during the [=charter refinement=] phase
 	are specially handled:
-	* Objections to the choice of [=Chartering Facilitator=] are processed normally (See [[#addressing-fo]]).
 	* Objections to abandoning the proposal can be appealed only if 5 or more Members,
 		through their [=Advisory Committee representative=],
 		formally object to the decision within 8 weeks of the decision being announced.
 		In this case, the [=Team=] must either resume charter refinement
 		or refer the matter to the [=Council=].
 		(No action is required to be taken when fewer than 5 members object.)
-	* All other objections are considered registered
-		at the close of the [=Advisory Committee Review=] of the charter,
+	* Objections to decisions pertaining to the content of the charter,
+		as well as objections to initiating the [=AC Review=],
+		are considered registered at the close of the [=Advisory Committee Review=] of the charter,
 		and are registered against that [=W3C Decision=].
+	* Any other objections are processed normally (See [[#addressing-fo]]).
 
 	Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together.
 

From 1c9f1a79189752adb0013ba01529e0c1eae5e185 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 12 Feb 2025 15:48:55 +0900
Subject: [PATCH 163/237] Enable AB/TAG to remove one of their members by
 super-majority

See #882
---
 index.bs | 25 ++++++++++++++++++++++++-
 1 file changed, 24 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index b188469d..0bc93060 100644
--- a/index.bs
+++ b/index.bs
@@ -1323,15 +1323,38 @@ Verifiable Random Selection Procedure</h5>
 			The incomplete terms are assigned in result order.
 	</ol>
 
+<h5 id="AB-TAG-removal">
+Removing AB or TAG members</h5>
+
+	Individual participants of the [=Advisory Board=] or the [=Technical Architecture Group=]
+	can be <dfn export lt="remove|removal">removed</dfn> from those groups
+	if they are found by their peers
+	to be grossly neglecting their duties,
+	or to be acting in a way that seriously hampers the group's ability to function normally.
+
+	A chair of the [=AB=] or [=TAG=] <em class=rfc2119>must</em> hold a hearing
+	on the potential [=removal=] of a participant
+	if requested by at least three of the participants in the group.
+	After giving the individual in question
+	an opportunity to defend themselves,
+	a vote on the proposed [=removal=] is held.
+	If at least three quarters of the participants in the group,
+	excluding the individual who is the subject of such vote,
+	then vote in favor of the proposal,
+	the individual's seat on [=AB=] or [=TAG=] is [=vacated=] immediately.
+
 <h5 id="AB-TAG-vacated">
 Elected Groups Vacated Seats</h5>
 
-	An [=Advisory Board=] or [=TAG=] participant's seat is vacated when:
+	An [=Advisory Board=] or [=TAG=] participant's seat is <dfn lt="vacated|vacant">vacated</dfn> when:
 
 	<ul>
 		<li>
 			the participant resigns, or
 
+		<li>
+			the participant is [=removed=], or
+
 		<li>
 			an Advisory Board or TAG participant changes affiliations
 			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,

From 77cebe5ba66ff43ff5a1024b34512bd8c07dfaca Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 12 Mar 2025 13:28:24 +0900
Subject: [PATCH 164/237] Drop unnecessary remarks about optional communication

This sentence was kept because the notion of an advance notice was
preexisting, and we wanted to distinguish the pre-existing informal
heads up message from the official message starting the phase.

However, it may be more confusing that helpful.
---
 index.bs | 2 --
 1 file changed, 2 deletions(-)

diff --git a/index.bs b/index.bs
index 0bc93060..f35559e4 100644
--- a/index.bs
+++ b/index.bs
@@ -1762,8 +1762,6 @@ Initiating Charter Refinement</h3>
 	Prior to the formal [=charter refinement|refinement=] phase,
 	the [=Team=] engages with those various parties
 	to help prepare [=charters=] for broader audiences.
-	The [=Team=] <em class=rfc2119>may</em> send notice to the [=AC=]
-	when starting development of a new charter prior to the [=charter refinement=] phase.
 
 	Formal [=charter refinement=] (see below) is initiated
 	by the [=Team=] sending a [=charter review notice=]

From 207955b563e066f3d6724bfed0b1019240050dbd Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 27 Mar 2025 01:33:11 +0900
Subject: [PATCH 165/237] Update Changelog

---
 index.bs | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index f35559e4..e5d0d58b 100644
--- a/index.bs
+++ b/index.bs
@@ -5768,8 +5768,12 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>)
 
 				<li>
-					Simplify provisions regarding subsitute representatives and proxies.
+					Simplify provisions regarding substitute representatives and proxies.
 					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
+
+				<li>
+					Enable AB/TAG to remove one of their members by 3/4 super majority.
+					(See <a href="https://github.com/w3c/process/pull/986">Pull Request 373</a>)
 			</ul>
 
 

From 5f0a69444b0c842355a3eb474df789b10125de8a Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 28 Mar 2025 12:32:41 +0900
Subject: [PATCH 166/237] [Editorial] Punctuation / parenthetical

---
 index.bs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index e5d0d58b..1a10cf07 100644
--- a/index.bs
+++ b/index.bs
@@ -3611,7 +3611,8 @@ Maturity Stages on the Recommendation Track</h4>
 			Such an allowance cannot be added
 			to a [=technical report=] previously published as a [=Recommendation=]
 			that did not allow such changes;
-			this requires a new [=technical report=], that could, for example, be similarly named but with an incremented version number.
+			this requires a new [=technical report=]
+			(which could, for example, be similarly named but with an incremented version number).
 
 			As technology evolves,
 			a [=W3C Recommendation=] may become:

From a440df34f3c8fa7e33982bb49066119fc0f3110b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 28 Mar 2025 12:50:32 +0900
Subject: [PATCH 167/237] Fix typo

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 1a10cf07..73b9ed6e 100644
--- a/index.bs
+++ b/index.bs
@@ -1936,7 +1936,7 @@ Content of a Charter</h3>
 	in the W3C Patent Policy [[!PATENT-POLICY]].
 
 	For every Recommendation Track deliverable
-	that continues work on [=technical report=]
+	that continues work on a [=technical report=]
 	published under any other Charter (including a predecessor group of the same name),
 	for which there is at least an existing [=First Public Working Draft=]
 	the description of that deliverable in the proposed charter of the adopting Working Group

From 309bcaa7b43996c26696e74845d855880f8b697d Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Fri, 28 Mar 2025 00:12:05 -0400
Subject: [PATCH 168/237] Remove redundant 'report'

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 73b9ed6e..54e13558 100644
--- a/index.bs
+++ b/index.bs
@@ -3046,7 +3046,7 @@ Types of Technical Reports</h3>
 	This chapter describes the formal requirements
 	for [=publishing=] and maintaining a [=W3C Recommendation=],
 	[=Note=],
-	or [=Registry Report=].
+	or [=Registry=].
 
 	<dl>
 		<dt>Recommendations

From c4bf0c0ce54950bd87c79d83eba51f2a35f86935 Mon Sep 17 00:00:00 2001
From: ianbjacobs <ij@w3.org>
Date: Fri, 28 Mar 2025 14:21:04 -0500
Subject: [PATCH 169/237] (Editorial) Typo fix

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 54e13558..f7b36817 100644
--- a/index.bs
+++ b/index.bs
@@ -1750,7 +1750,7 @@ Lifecycle of Chartered Groups</h2>
 		reflect community input and [=consensus=],
 		and have been well-socialized
 		and [=wide review|widely reviewed=].
-	* [=Charters=] the are formally approved through an [=AC Review=] and [=W3C Decision=] (see [[#CharterReview]]).
+	* [=Charters=] then are formally approved through an [=AC Review=] and [=W3C Decision=] (see [[#CharterReview]]).
 
 <h3 id="charter-initiation">
 Initiating Charter Refinement</h3>

From d9955a44a606e2f261e351e2b2fbca5d1deb68b3 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 31 Mar 2025 09:06:24 +0900
Subject: [PATCH 170/237] Fix spacing

---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index f7b36817..66c2bc07 100644
--- a/index.bs
+++ b/index.bs
@@ -40,8 +40,8 @@ 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.
+	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.

From 25d1859a38c6104d3d921711d9655d37b6669f42 Mon Sep 17 00:00:00 2001
From: Basha MEGA <adambashaahmednaji@gmail.com>
Date: Fri, 28 Mar 2025 05:53:04 +0000
Subject: [PATCH 171/237] chore: replace informative with non-normative for
 consistency

---
 index.bs | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index 66c2bc07..044774b7 100644
--- a/index.bs
+++ b/index.bs
@@ -1195,7 +1195,7 @@ Advisory Board and Technical Architecture Group Elections</h5>
 	are changes of affiliation).
 	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
 	Each nomination <em class="rfc2119">should</em> include
-	a few informative paragraphs about the nominee.
+	a few non-normative paragraphs about the nominee.
 	If an identified candidate's nomination information is only partially complete
 	as of the deadline for nominations,
 	the [=Team=] <em class=rfc2119>may</em> allow extra time for that candidate's nomination to be completed,
@@ -2751,7 +2751,7 @@ Council Decision Report</h5>
 	The [=Council=] <em class=rfc2119>may</em> also issue a <dfn export>Supplemental Confidential Council Report</dfn>
 	with a more restricted <a href="#confidentiality-levels">level of confidentiality</a> than its main report
 	when it believes that additional commentary on confidential aspects of the case
-	would be informative.
+	would be non-normative.
 	However, the main [=Council Report=] <em class=rfc2119>should</em> be self-sufficient
 	and understandable without reference to Supplemental Confidential Council Reports.
 
@@ -3255,7 +3255,7 @@ Classes of Changes</h4>
 			Examples of changes in this class include
 			correcting non-normative examples
 			which clearly conflict with normative requirements,
-			clarifying informative use cases or other non-normative text,
+			clarifying non-normative use cases or other non-normative text,
 			fixing typos or grammatical errors
 			where the change does not change requirements.
 		<dd>
@@ -3337,7 +3337,7 @@ Errata Management</h4>
 <h4 id=candidate-amendments oldids=candidate-changes>
 Candidate Amendments</h4>
 
-	An [=erratum=] <em class="rfc2119">may</em> be accompanied by an informative,
+	An [=erratum=] <em class="rfc2119">may</em> be accompanied by an non-normative,
 	<dfn>candidate correction</dfn> approved by [=group decision=].
 	When annotated inline,
 	errata--
@@ -4911,7 +4911,7 @@ Registry Data Reports</h4>
 			establishing the [=registry tables=] that it contain.
 
 		<li>
-			<em class=rfc2119>May</em> contain informative introductory text, examples, and notes
+			<em class=rfc2119>May</em> contain non-normative introductory text, examples, and notes
 			about the [=registry tables=] and [=registry entries|entries=] that it contains.
 			(Changes to these parts are deemed to be [=editorial changes=]).
 	</ul>
@@ -5740,7 +5740,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					for better integration in the W3C website architecture.
 
 				<li>
-					Shift most of the informative discussion about Workshops to [[GUIDE]],
+					Shift most of the non-normative discussion about Workshops to [[GUIDE]],
 					and reorganize the remaining normative requirements.
 					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
 

From 68dc5dc0152d97d15a784eeda5c6660ad92de482 Mon Sep 17 00:00:00 2001
From: Basha MEGA <adambashaahmednaji@gmail.com>
Date: Fri, 28 Mar 2025 06:39:50 +0000
Subject: [PATCH 172/237] chore: revert some words

---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 044774b7..7dbd3fd0 100644
--- a/index.bs
+++ b/index.bs
@@ -1195,7 +1195,7 @@ Advisory Board and Technical Architecture Group Elections</h5>
 	are changes of affiliation).
 	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
 	Each nomination <em class="rfc2119">should</em> include
-	a few non-normative paragraphs about the nominee.
+	a few informative paragraphs about the nominee.
 	If an identified candidate's nomination information is only partially complete
 	as of the deadline for nominations,
 	the [=Team=] <em class=rfc2119>may</em> allow extra time for that candidate's nomination to be completed,
@@ -2751,7 +2751,7 @@ Council Decision Report</h5>
 	The [=Council=] <em class=rfc2119>may</em> also issue a <dfn export>Supplemental Confidential Council Report</dfn>
 	with a more restricted <a href="#confidentiality-levels">level of confidentiality</a> than its main report
 	when it believes that additional commentary on confidential aspects of the case
-	would be non-normative.
+	would be informative.
 	However, the main [=Council Report=] <em class=rfc2119>should</em> be self-sufficient
 	and understandable without reference to Supplemental Confidential Council Reports.
 

From 16ba1c71ba8dde6063ae017948f984e21a4e4a9b Mon Sep 17 00:00:00 2001
From: Adam Basha <110662505+Bashamega@users.noreply.github.com>
Date: Fri, 28 Mar 2025 08:41:32 +0200
Subject: [PATCH 173/237] Update index.bs

Co-authored-by: Florian Rivoal <git@florian.rivoal.net>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 7dbd3fd0..d558311d 100644
--- a/index.bs
+++ b/index.bs
@@ -3255,7 +3255,7 @@ Classes of Changes</h4>
 			Examples of changes in this class include
 			correcting non-normative examples
 			which clearly conflict with normative requirements,
-			clarifying non-normative use cases or other non-normative text,
+			clarifying various other non-normative text,
 			fixing typos or grammatical errors
 			where the change does not change requirements.
 		<dd>

From e16de99fb6d52d2355dc9570a0baa3a836773bff Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Sat, 29 Mar 2025 03:56:06 +0900
Subject: [PATCH 174/237] grammar

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index d558311d..40aae167 100644
--- a/index.bs
+++ b/index.bs
@@ -3337,7 +3337,7 @@ Errata Management</h4>
 <h4 id=candidate-amendments oldids=candidate-changes>
 Candidate Amendments</h4>
 
-	An [=erratum=] <em class="rfc2119">may</em> be accompanied by an non-normative,
+	An [=erratum=] <em class="rfc2119">may</em> be accompanied by a non-normative,
 	<dfn>candidate correction</dfn> approved by [=group decision=].
 	When annotated inline,
 	errata--

From 192c853c25c8ab443be214e21663e7d716630a1a Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 28 Mar 2025 12:33:23 +0900
Subject: [PATCH 175/237] Make cross reference more obvious

The referenced section has a bunch of rules, it would not be good if
they were overlooked.

See https://github.com/w3c/process/issues/1008
---
 index.bs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 40aae167..d60c77d1 100644
--- a/index.bs
+++ b/index.bs
@@ -3602,7 +3602,8 @@ Maturity Stages on the Recommendation Track</h4>
 
 			<p id="expandable-rec">
 			After its initial publication,
-			a [=W3C Recommendation=] <em class=rfc2119>may</em> be [[#revising-rec|revised]]
+			a [=W3C Recommendation=] <em class=rfc2119>may</em> be revised
+			(in accordance with [[#revising-rec|]])
 			to address [=editorial change|editorial=] or [=substantive change|substantive=] issues
 			that are discovered later.
 			However, <a href=#class-4>new features</a> can only be added

From 2a130d1d062faf8b1c863ce4284dc738c3280346 Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Fri, 11 Apr 2025 21:23:39 +0200
Subject: [PATCH 176/237] Fix markup error

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index d60c77d1..3486e000 100644
--- a/index.bs
+++ b/index.bs
@@ -3603,7 +3603,7 @@ Maturity Stages on the Recommendation Track</h4>
 			<p id="expandable-rec">
 			After its initial publication,
 			a [=W3C Recommendation=] <em class=rfc2119>may</em> be revised
-			(in accordance with [[#revising-rec|]])
+			(in accordance with [[#revising-rec]])
 			to address [=editorial change|editorial=] or [=substantive change|substantive=] issues
 			that are discovered later.
 			However, <a href=#class-4>new features</a> can only be added

From 6553a8015f44ed36626d5dddcef97484f703ba3b Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Fri, 11 Apr 2025 21:51:15 +0200
Subject: [PATCH 177/237] Remove 'normally' which is unnecessarily judgemental
 and unnecessary.

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 3486e000..c3607e6e 100644
--- a/index.bs
+++ b/index.bs
@@ -1330,7 +1330,7 @@ Removing AB or TAG members</h5>
 	can be <dfn export lt="remove|removal">removed</dfn> from those groups
 	if they are found by their peers
 	to be grossly neglecting their duties,
-	or to be acting in a way that seriously hampers the group's ability to function normally.
+	or to be acting in a way that seriously hampers the group's ability to function.
 
 	A chair of the [=AB=] or [=TAG=] <em class=rfc2119>must</em> hold a hearing
 	on the potential [=removal=] of a participant

From 12eef6486935a376a19fcdf99fe41393170b16a0 Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Sat, 12 Apr 2025 00:07:57 +0200
Subject: [PATCH 178/237] Notify the AC when an AB or TAG member is removed.

Addresses https://github.com/w3c/process/pull/888#discussion_r1936636248
Related to #882.
---
 index.bs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/index.bs b/index.bs
index c3607e6e..b152fa3f 100644
--- a/index.bs
+++ b/index.bs
@@ -1342,6 +1342,7 @@ Removing AB or TAG members</h5>
 	excluding the individual who is the subject of such vote,
 	then vote in favor of the proposal,
 	the individual's seat on [=AB=] or [=TAG=] is [=vacated=] immediately.
+	The group must notify the [=AC=] of such a [=removal=] within one week.
 
 <h5 id="AB-TAG-vacated">
 Elected Groups Vacated Seats</h5>

From 193b820bccd0819abfd705d05652012c49600fe1 Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Tue, 15 Apr 2025 18:43:08 -0400
Subject: [PATCH 179/237] Removal hearings are held by the group, not the
 chair.

Addresses part of #1007
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index b152fa3f..84db4bb0 100644
--- a/index.bs
+++ b/index.bs
@@ -1332,7 +1332,7 @@ Removing AB or TAG members</h5>
 	to be grossly neglecting their duties,
 	or to be acting in a way that seriously hampers the group's ability to function.
 
-	A chair of the [=AB=] or [=TAG=] <em class=rfc2119>must</em> hold a hearing
+	The [=AB=] or [=TAG=] <em class=rfc2119>must</em> hold a hearing
 	on the potential [=removal=] of a participant
 	if requested by at least three of the participants in the group.
 	After giving the individual in question

From a3bbb150d51feac83800cc7195787277ea9aa526 Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Tue, 15 Apr 2025 19:02:27 -0400
Subject: [PATCH 180/237] Removal from AB/TAG does not impact Council
 membership #1006

---
 index.bs | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/index.bs b/index.bs
index 84db4bb0..206c69df 100644
--- a/index.bs
+++ b/index.bs
@@ -1344,6 +1344,8 @@ Removing AB or TAG members</h5>
 	the individual's seat on [=AB=] or [=TAG=] is [=vacated=] immediately.
 	The group must notify the [=AC=] of such a [=removal=] within one week.
 
+	Note: Removal from the [=AB=] or [=TAG=] does not imply removal from a convened [=Council=].
+
 <h5 id="AB-TAG-vacated">
 Elected Groups Vacated Seats</h5>
 

From 3994f01830bc76b866d94303065d218539f81a5a Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Tue, 15 Apr 2025 15:07:41 -0400
Subject: [PATCH 181/237] Fix confusing wording wrt adding new features to RECs
 #1004

---
 index.bs | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 206c69df..eaf81678 100644
--- a/index.bs
+++ b/index.bs
@@ -4265,11 +4265,15 @@ Revising a Recommendation: New Features</h5>
 	enables third parties to depend on a stable feature-set for [=Recommendations=] that do not advertise that ability,
 	as was the case for all [=Recommendations=] prior to the 2020 revision of this Process.
 
-	To make changes which introduce a new feature
-	to a [=Recommendation=] that does not [=allow new features=],
-	W3C <em class="rfc2119">must</em> create a new [=technical report=],
-	following the full process of <a href="#rec-advance">advancing a technical report to Recommendation</a>
+	Note: When a [=Recommendation=] does not [=allow new features=],
+	new features can be added by creating a new [=technical report=]
+	and following the full process of advancing that [=technical report=] to [=Recommendation=]--
 	beginning with a new [=First Public Working Draft=].
+	Such [=technical reports=] could be written to represent
+	additional modules building on top of the original [=Recommendation=] of the core technology,
+	or an expanded replacement of the original [=Recommendation=] of the core technology
+	(in which case the new [=technical report=] will typically have the same name as the original,
+	with an incremented version number).
 
 <h5 id=change-review>
 Incorporating Candidate Amendments</h5>

From 02dcacbda5897f742b004194e6ae698ad959d413 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 24 Apr 2025 00:14:49 +0900
Subject: [PATCH 182/237] Create connection with the Guide on how the Team
 evaluates charters

This is similar to how we moved the Team's evaluation criteria for Member submissions to the Guide.

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index eaf81678..b02fb0b9 100644
--- a/index.bs
+++ b/index.bs
@@ -1787,7 +1787,10 @@ Initiating Charter Refinement</h3>
 	An [=Advisory Committee representative=] <em class=rfc2119>may</em> formally request
 	that the [=Team=] initiate [=charter refinement=].
 	The Team <em class=rfc2119>may</em> deny such a request
-	if it thinks the proposal is insufficiently mature or does not align with W3C's scope and mission,
+        if it thinks the proposal is insufficiently mature,
+        does not align with W3C's scope and mission,
+	or otherwise does not meet the charter assessment criteria
+	described in the Guide (see [[CHARTER inline]]),
 	and <em class=rfc2119>must</em> reply with its rationale.
 	This rejection is a [=Team Decision=],
 	and can be appealed only by 5 or more [=Members=],

From fdcbce0ab4733afcab39c82a16e452fbda1198e6 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 24 Apr 2025 00:16:13 +0900
Subject: [PATCH 183/237] Refine Expiration of Charter Refinement (#1011)

* Define extensions explicitly as decisions, which clarifies that they can be appealed if necessary.
* Clarify that failing to extend is de facto abandonment.
* Move paragraph for better cohesion.

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
---
 index.bs | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index b02fb0b9..419c0218 100644
--- a/index.bs
+++ b/index.bs
@@ -1830,6 +1830,13 @@ Charter Refinement</h3>
 	either to initiate [=AC Review=] of the [=charter draft=],
 	or to abandon the proposal.
 
+	The [=Team=] <em class=rfc2119>may</em> [=Team Decision|decide=]
+	to extend the charter refinement period
+	by sending an announcement with the same visibility as the initial [=charter refinement notice=].
+	Reaching the end of the announced period (including any announced extension)
+	with neither a decision to initiate [=AC Review=] nor an announcement of extension
+	is considered a de-facto [=Team decision=] to abandon the proposal.
+
 	[=Formal Objections=] filed during the [=charter refinement=] phase
 	are specially handled:
 	* Objections to abandoning the proposal can be appealed only if 5 or more Members,
@@ -1846,12 +1853,6 @@ Charter Refinement</h3>
 
 	Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together.
 
-	If the discussions have not concluded within the time frame announced in the [=charter review notice=],
-	the [=Chartering Facilitator=] must inform the AC
-	(and, in the case of rechartering, the affected [=Group=])
-	of this delay, of the status of the discussions, and of the revised expected duration of [=Charter Refinement=].
-	This report should be public.
-
 <h3 id="WGCharter">
 Content of a Charter</h3>
 

From 33a4a55528634ee18e3e9f45144e0d61d0fd2d8e Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Wed, 23 Apr 2025 11:16:50 -0400
Subject: [PATCH 184/237] Clarify role of the chair (#1025)

---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 419c0218..5a19b191 100644
--- a/index.bs
+++ b/index.bs
@@ -1453,11 +1453,11 @@ Requirements for All Chartered Groups</h4>
 	(even if other proceedings of the group are <a href="#Member-only">Member-only</a>).
 
 	Each group <em class="rfc2119">must</em> have a <dfn id="GeneralChairs" export>Chair</dfn> (or co-Chairs)
-	to coordinate the group's tasks.
+	to facilitate effective discussion and coordinate the group's activities.
 	The [=Team=] appoints (and re-appoints) Chairs for all groups.
 	The Chair is a <a href="#member-rep">Member representative</a>,
 	a <a href="#Team">Team representative</a>,
-	or an <a href="#invited-expert-wg">Invited Expert</a>,
+	or an <a href="#invited-expert-wg">Invited Expert</a>
 	(invited by the [=Team=]).
 	The requirements of this document that apply to those types of participants apply to Chairs as well.
 	

From 3f1e6788a224162deb356cf41e033a590208b631 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 24 Apr 2025 00:22:12 +0900
Subject: [PATCH 185/237] Clean up 3-way decision

See https://github.com/w3c/process/issues/1009 for rationale

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Philippe Le Hegaret <plh@w3.org>
---
 index.bs | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index 5a19b191..1f114afe 100644
--- a/index.bs
+++ b/index.bs
@@ -1827,8 +1827,8 @@ Charter Refinement</h3>
 	The [=charter refinement=] phase concludes
 	when there is a [=Team Decision=]
 	(informed by the work of the [=Chartering Facilitator=])
-	either to initiate [=AC Review=] of the [=charter draft=],
-	or to abandon the proposal.
+	to either complete charter refinement by initiating [=AC Review=] of the [=charter draft=],
+	or abandon the proposal.
 
 	The [=Team=] <em class=rfc2119>may</em> [=Team Decision|decide=]
 	to extend the charter refinement period
@@ -1839,11 +1839,18 @@ Charter Refinement</h3>
 
 	[=Formal Objections=] filed during the [=charter refinement=] phase
 	are specially handled:
-	* Objections to abandoning the proposal can be appealed only if 5 or more Members,
+	* Objections to abandoning the proposal or to extending the refinement period can be appealed only if 5 or more Members,
 		through their [=Advisory Committee representative=],
-		formally object to the decision within 8 weeks of the decision being announced.
-		In this case, the [=Team=] must either resume charter refinement
-		or refer the matter to the [=Council=].
+		formally object to the decision within 8 weeks of the decision.
+		In this case,
+		the [=Team=] <em class=rfc2119>must</em> do one of the following:
+		* Abide by the objectors' request, if they all agree on the
+			alternative course of action (e.g., to abandon,
+			extend, or complete charter refinement).
+		* Initiate an [=AC Review=] to formally solicit the input of
+			the community and take a W3C Decision on the subsequent
+			course of action.
+		* Convene a [=Council=] to decide the subsequent course of action.
 		(No action is required to be taken when fewer than 5 members object.)
 	* Objections to decisions pertaining to the content of the charter,
 		as well as objections to initiating the [=AC Review=],

From 2a6e153a12e0959e4785499f1402af766fb23ccc Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 24 Apr 2025 11:40:53 +0900
Subject: [PATCH 186/237] Fix spacing

---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 1f114afe..def6141d 100644
--- a/index.bs
+++ b/index.bs
@@ -1787,8 +1787,8 @@ Initiating Charter Refinement</h3>
 	An [=Advisory Committee representative=] <em class=rfc2119>may</em> formally request
 	that the [=Team=] initiate [=charter refinement=].
 	The Team <em class=rfc2119>may</em> deny such a request
-        if it thinks the proposal is insufficiently mature,
-        does not align with W3C's scope and mission,
+	if it thinks the proposal is insufficiently mature,
+	does not align with W3C's scope and mission,
 	or otherwise does not meet the charter assessment criteria
 	described in the Guide (see [[CHARTER inline]]),
 	and <em class=rfc2119>must</em> reply with its rationale.

From ecb59e375d2ecf303b6c1ab4cfb0dce30696aca9 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 24 Apr 2025 15:40:42 +0900
Subject: [PATCH 187/237] Fix terminology usage

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index def6141d..0d58f898 100644
--- a/index.bs
+++ b/index.bs
@@ -1832,7 +1832,7 @@ Charter Refinement</h3>
 
 	The [=Team=] <em class=rfc2119>may</em> [=Team Decision|decide=]
 	to extend the charter refinement period
-	by sending an announcement with the same visibility as the initial [=charter refinement notice=].
+	by sending an announcement with the same visibility as the initial [=charter review notice=].
 	Reaching the end of the announced period (including any announced extension)
 	with neither a decision to initiate [=AC Review=] nor an announcement of extension
 	is considered a de-facto [=Team decision=] to abandon the proposal.

From d3d9ab22e4a7a3a6f99c9c0ea98570f2e96525e9 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 24 Apr 2025 15:41:41 +0900
Subject: [PATCH 188/237] Markdown fix

---
 index.bs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/index.bs b/index.bs
index 0d58f898..8955cd6f 100644
--- a/index.bs
+++ b/index.bs
@@ -1851,6 +1851,7 @@ Charter Refinement</h3>
 			the community and take a W3C Decision on the subsequent
 			course of action.
 		* Convene a [=Council=] to decide the subsequent course of action.
+
 		(No action is required to be taken when fewer than 5 members object.)
 	* Objections to decisions pertaining to the content of the charter,
 		as well as objections to initiating the [=AC Review=],

From 92fd04169637bdd247d0dce9172f36d19555eb5b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 28 Apr 2025 21:53:52 +0900
Subject: [PATCH 189/237] Reorder Objection Handling cases related to charter
 refinement

This just reorders the text, with no normative difference (nor even
editorial besides the move), in order to have the main case first, and
the corner cases at the end.
---
 index.bs | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/index.bs b/index.bs
index 8955cd6f..75379fb4 100644
--- a/index.bs
+++ b/index.bs
@@ -1839,6 +1839,12 @@ Charter Refinement</h3>
 
 	[=Formal Objections=] filed during the [=charter refinement=] phase
 	are specially handled:
+	* Objections to decisions pertaining to the content of the charter,
+		as well as objections to initiating the [=AC Review=],
+		are considered registered at the close of the [=Advisory Committee Review=] of the charter,
+		and are registered against that [=W3C Decision=].
+
+		Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together.
 	* Objections to abandoning the proposal or to extending the refinement period can be appealed only if 5 or more Members,
 		through their [=Advisory Committee representative=],
 		formally object to the decision within 8 weeks of the decision.
@@ -1853,13 +1859,8 @@ Charter Refinement</h3>
 		* Convene a [=Council=] to decide the subsequent course of action.
 
 		(No action is required to be taken when fewer than 5 members object.)
-	* Objections to decisions pertaining to the content of the charter,
-		as well as objections to initiating the [=AC Review=],
-		are considered registered at the close of the [=Advisory Committee Review=] of the charter,
-		and are registered against that [=W3C Decision=].
 	* Any other objections are processed normally (See [[#addressing-fo]]).
 
-	Note: This enables all [=Formal Objections=] on the same proposed [=charter=] to be handled together.
 
 <h3 id="WGCharter">
 Content of a Charter</h3>

From 313737ef73f87b319cd9ad415f25b7af0af3e26b Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Mon, 28 Apr 2025 22:03:01 -0400
Subject: [PATCH 190/237] [editorial] Collapse some wording wrt Council
 formation. (#1022)

Co-authored-by: Florian Rivoal <git@florian.rivoal.net>
---
 index.bs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 75379fb4..0c7a026a 100644
--- a/index.bs
+++ b/index.bs
@@ -2521,13 +2521,13 @@ Council Composition</h5>
 	The list of potential [=Council=] members evolves
 	as [=AB=] and [=TAG=] terms start and end
 	until [=dismissal=] and [=renunciation=] are concluded,
-	at which point all remaining potential [=Council=] members become full members.
-	Thereafter, the membership of the [=Council=] is fixed,
-	and is not changed by any [=AB=] or [=TAG=] elections
-	that occur before that Council has reached a conclusion.
+	at which point the membership of the [=Council=] is fixed.
 	However, if the number of active members in a [=Council=] falls so low as to hinder effective and balanced deliberations,
 	the [=Council Chair=] <em class="rfc2119">should</em> dissolve the [=Council=]
 	and call for a new one to be convened.
+	
+	Note: TAG and AB elections have no effect on the Council's membership
+	once it is fixed.
 
 	A [=Team=] member is assigned
 	to act as the <dfn export>Council Team Contact</dfn>,

From 64cb8eca7271bb03499fd067b862b80b84ae780a Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 2 May 2025 11:20:03 +0900
Subject: [PATCH 191/237] Update links in README

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index a33726f4..408c7033 100644
--- a/README.md
+++ b/README.md
@@ -16,8 +16,9 @@ Discussion happens in the context of the W3C Process Community Group
 ----
 ## Useful searches
 
-[PRs triaged into P2021](https://github.com/w3c/process/issues?q=is%3Aopen+-label%3A%22P2021%3A+Priority%22+milestone%3A%22Process+2021%22+) which are not priorities.
-
+* [Issues and PRs without a milestone](https://github.com/w3c/process/issues?q=is%3Aopen%20no%3Amilestone)
+* [Issues and PR included and targetted for the next release](https://github.com/w3c/process/issues?q=is%3Aopen%20milestone%3A%22Process%202024%2F2025%22%20)
+* [Issues and PR marked as Agenda+](https://github.com/w3c/process/issues?q=%20label%3AAgenda%2B%20)
 
 ----
 ## Bikeshed

From a49d0e8a443d9e8dbbb9c849647d6768164a28e1 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 2 May 2025 11:07:28 +0900
Subject: [PATCH 192/237] Revert all changes related to AB/TAG removal/recall

This reverts commits:
193b820bccd0819abfd705d05652012c49600fe1
a3bbb150d51feac83800cc7195787277ea9aa526
12eef6486935a376a19fcdf99fe41393170b16a0
6553a8015f44ed36626d5dddcef97484f703ba3b
1c9f1a79189752adb0013ba01529e0c1eae5e185
207955b563e066f3d6724bfed0b1019240050dbd
---
 index.bs | 34 ++--------------------------------
 1 file changed, 2 insertions(+), 32 deletions(-)

diff --git a/index.bs b/index.bs
index 0c7a026a..0211c279 100644
--- a/index.bs
+++ b/index.bs
@@ -1323,41 +1323,15 @@ Verifiable Random Selection Procedure</h5>
 			The incomplete terms are assigned in result order.
 	</ol>
 
-<h5 id="AB-TAG-removal">
-Removing AB or TAG members</h5>
-
-	Individual participants of the [=Advisory Board=] or the [=Technical Architecture Group=]
-	can be <dfn export lt="remove|removal">removed</dfn> from those groups
-	if they are found by their peers
-	to be grossly neglecting their duties,
-	or to be acting in a way that seriously hampers the group's ability to function.
-
-	The [=AB=] or [=TAG=] <em class=rfc2119>must</em> hold a hearing
-	on the potential [=removal=] of a participant
-	if requested by at least three of the participants in the group.
-	After giving the individual in question
-	an opportunity to defend themselves,
-	a vote on the proposed [=removal=] is held.
-	If at least three quarters of the participants in the group,
-	excluding the individual who is the subject of such vote,
-	then vote in favor of the proposal,
-	the individual's seat on [=AB=] or [=TAG=] is [=vacated=] immediately.
-	The group must notify the [=AC=] of such a [=removal=] within one week.
-
-	Note: Removal from the [=AB=] or [=TAG=] does not imply removal from a convened [=Council=].
-
 <h5 id="AB-TAG-vacated">
 Elected Groups Vacated Seats</h5>
 
-	An [=Advisory Board=] or [=TAG=] participant's seat is <dfn lt="vacated|vacant">vacated</dfn> when:
+	An [=Advisory Board=] or [=TAG=] participant's seat is vacated when:
 
 	<ul>
 		<li>
 			the participant resigns, or
 
-		<li>
-			the participant is [=removed=], or
-
 		<li>
 			an Advisory Board or TAG participant changes affiliations
 			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
@@ -5790,12 +5764,8 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>)
 
 				<li>
-					Simplify provisions regarding substitute representatives and proxies.
+					Simplify provisions regarding subsitute representatives and proxies.
 					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
-
-				<li>
-					Enable AB/TAG to remove one of their members by 3/4 super majority.
-					(See <a href="https://github.com/w3c/process/pull/986">Pull Request 373</a>)
 			</ul>
 
 

From c9c2aa7e57e0202ed0caf0ec5b4b251407f10c77 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 2 May 2025 11:33:56 +0900
Subject: [PATCH 193/237] Fix typo

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 0211c279..4ec552fe 100644
--- a/index.bs
+++ b/index.bs
@@ -5764,7 +5764,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>)
 
 				<li>
-					Simplify provisions regarding subsitute representatives and proxies.
+					Simplify provisions regarding substitute representatives and proxies.
 					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
 			</ul>
 

From 09652c1efb702f38be6c1c82ea46d2ae9dd2a300 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 2 May 2025 11:31:23 +0900
Subject: [PATCH 194/237] Register topic branch for ab-tag-discipline

---
 README.md | 3 ++-
 deploy.sh | 3 ++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 408c7033..dd96f45c 100644
--- a/README.md
+++ b/README.md
@@ -10,8 +10,9 @@ Discussion happens in the context of the W3C Process Community Group
 ----
 ## Branches under development
 
-[main](https://github.com/w3c/process/tree/main) branch (current draft of the CG):
+* [main](https://github.com/w3c/process/tree/main) branch (current draft of the CG):
 [Preview](https://www.w3.org/policies/process/drafts/)
+* [ab-tag-discipline](https://github.com/w3c/process/tree/ab-tag-discipline) branch, where potential procedures for removal and recall of AB or TAG members are being worked out: [preview](https://www.w3.org/policies/process/drafts/ab-tag-discipline)
 
 ----
 ## Useful searches
diff --git a/deploy.sh b/deploy.sh
index 37a15610..55b5eb30 100755
--- a/deploy.sh
+++ b/deploy.sh
@@ -21,7 +21,8 @@ TOPIC_BRANCHES=(
 	"section-6-clean-up"
 	"maintenance-2020"
 	"p2021-before-reorg"
-	"p2021")
+	"p2021"
+	"ab-tag-discipline")
 
 containsElement () {
   local e match="$1"

From 2c6a66ffb86dfb4ff761c65b364613fc797232ec Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 2 May 2025 12:33:28 +0900
Subject: [PATCH 195/237] Fix URL in readme

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index dd96f45c..89943d19 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ Discussion happens in the context of the W3C Process Community Group
 
 * [main](https://github.com/w3c/process/tree/main) branch (current draft of the CG):
 [Preview](https://www.w3.org/policies/process/drafts/)
-* [ab-tag-discipline](https://github.com/w3c/process/tree/ab-tag-discipline) branch, where potential procedures for removal and recall of AB or TAG members are being worked out: [preview](https://www.w3.org/policies/process/drafts/ab-tag-discipline)
+* [ab-tag-discipline](https://github.com/w3c/process/tree/ab-tag-discipline) branch, where potential procedures for removal and recall of AB or TAG members are being worked out: [preview](https://www.w3.org/policies/process/drafts/ab-tag-discipline/)
 
 ----
 ## Useful searches

From 2691bf7d3c9157cc93afb33e82e88b2cb65d31b5 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 2 May 2025 13:11:05 +0900
Subject: [PATCH 196/237] Improve build script

Generate the correct "This Version" URL for topic branches
---
 compile.sh | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/compile.sh b/compile.sh
index d10c49f4..e2094983 100755
--- a/compile.sh
+++ b/compile.sh
@@ -14,7 +14,8 @@ if [ $1 ] ; then
 			<p>This is the “$1” topic branch; make sure this is indeed the one you’re looking for.\
 			If not, the current Editor’s Draft can be found at\
 			<a href='https://www.w3.org/policies/process/drafts/'>https://www.w3.org/policies/process/drafts/</a>.<br>\
-			(The <a href=#sotd>Status of this document</a> section may have information about the purpose of this branch.)</details>"
+			(The <a href=#sotd>Status of this document</a> section may have information about the purpose of this branch.)</details>" \
+		--md-ED="https://www.w3.org/policies/process/drafts/$1/"
 else
 	bikeshed --print=plain -f spec
 fi

From c13ed730caae8e12678841edc8d8a20a6a810a10 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 15 May 2025 00:00:45 +0900
Subject: [PATCH 197/237] Tweaks to how charter refinement concludes (#1037)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This keeps things largely as they were, but reworks the text to be more
explicit about a few things:
* The Team is actually supposed to make a decision at the end of the
  refinement phase; de-facto abandonment is a way to handle accidentally
  forgetting to do so, not a valid deliberate choice
* The Team has to announced (and give rationale) for its decisions
* If the Team (accidentally) abandons a refinement by letting it expire,
  they can still issue a (different) decision when they notice,
  without having to start a whole new refinement.

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Tantek Çelik <46418+tantek@users.noreply.github.com>
---
 index.bs | 24 +++++++++++++++---------
 1 file changed, 15 insertions(+), 9 deletions(-)

diff --git a/index.bs b/index.bs
index 4ec552fe..a494504d 100644
--- a/index.bs
+++ b/index.bs
@@ -1798,18 +1798,24 @@ Charter Refinement</h3>
 		and their resolutions tracked in a disposition of comments
 		highlighting any issues not resolved by consensus.
 
-	The [=charter refinement=] phase concludes
-	when there is a [=Team Decision=]
+	Before the end of the announced duration
+	for the [=charter refinement=] phase,
+	the [=Team=]
 	(informed by the work of the [=Chartering Facilitator=])
-	to either complete charter refinement by initiating [=AC Review=] of the [=charter draft=],
-	or abandon the proposal.
-
-	The [=Team=] <em class=rfc2119>may</em> [=Team Decision|decide=]
-	to extend the charter refinement period
-	by sending an announcement with the same visibility as the initial [=charter review notice=].
+	<em class=rfc2119>must</em> [=Team Decision|decide=] which of the following to do:
+	* Complete charter refinement by initiating [=AC Review=] of the [=charter draft=].
+	* Abandon the proposal.
+	* Extend the charter refinement period.
+
+	The [=Team=] <em class=rfc2119>must</em> announce its [=Team Decision|decision=]
+	with the same visibility as the initial [=charter review notice=],
+	and <em class=rfc2119>must</em> include a rationale
+	if they are not initiating [=AC Review=].
 	Reaching the end of the announced period (including any announced extension)
-	with neither a decision to initiate [=AC Review=] nor an announcement of extension
+	with no announced decision
 	is considered a de-facto [=Team decision=] to abandon the proposal.
+	The [=Team=] <em class=rfc2119>may</em> revise such a decision
+	by announcing an alternative decision.
 
 	[=Formal Objections=] filed during the [=charter refinement=] phase
 	are specially handled:

From 8d965518cce24fe632243d84f3ac900cc10b8c20 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 24 Apr 2025 15:39:15 +0900
Subject: [PATCH 198/237] Refine the definition/usage of the minor changes
 concept

See PSIG discussion at https://lists.w3.org/Archives/Member/member-psig/2025AprJun/0005.html and later.

As approved by PSIG in the May 12 call

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
Co-authored-by: Anna Weinberg <anna_m_weinberg@apple.com>
Co-authored-by: Jill Schmidt <jill_schmidt@apple.com>
Co-authored-by: Michael Sirtori <michael.j.sirtori@intel.com>
---
 index.bs | 31 ++++++++++++++++++++-----------
 1 file changed, 20 insertions(+), 11 deletions(-)

diff --git a/index.bs b/index.bs
index a494504d..94a9ec64 100644
--- a/index.bs
+++ b/index.bs
@@ -1999,10 +1999,10 @@ Charter Review and Approval</h3>
 New Charters and Major Changes</h4>
 
 	Any new [=charter=] (including re-chartering of existing [=chartered groups=])
-	and most substantive changes to an already-approved [=charter=]
+	and any change that is not a [=minor change=] (per [[#charter-minor-changes]]) to an already-approved [=charter=]
 	of a [=Working Group=] or [=Interest Group=]
 	<em class=rfc2119>must</em> be approved by a [=W3C Decision=] following an [=AC Review=] of that [=charter=].
-	(See [[#charter-minor-changes]] for minor changes that can be approved by a [=Team Decision=].)
+	Moditications to a [=charter=] <em class=rfc2119>should</em> have the [=consensus=] of the group.
 
 	The review period <em class=rfc2119>must</em> be at least 28 days.
 	Any [=Advisory Committee representative=] <em class=rfc2119>may</em> request an extended review period
@@ -2011,26 +2011,35 @@ New Charters and Major Changes</h4>
 	the [=Team=] <em class=rfc2119>must</em> extend the review period
 	to at least 60 days.
 
-	The Call for Review of a substantively modified charter
+	The Call for Review of a modified charter
 	<em class=rfc2119>must</em> highlight important changes
-	(e.g., regarding deliverables or resource allocation)
-	and include rationale for the changes.
+	(e.g., regarding changes in scope, deliverables, or resource allocation)
+	and <em class=rfc2119>must</em> include rationale for those changes.
 
-	The Call for Review of a new or substantively modified charter
-	<em class="rfc2119">must</em> include a disposition of comments for those received during the [=charter refinement=] process,
+	The Call for Review of a new or modified charter
+	<em class="rfc2119">must</em> include a disposition of comments received during the [=charter refinement=] process,
 	highlighting any issues that were closed despite sustained objections.
 
 <h4 id="charter-minor-changes">
 Minor Changes to Active Charters</h4>
 
-	Substantive changes to a [=charter=] (including [[#charter-extension|extensions]])
-	that do not affect the way the group functions in any significant way
+	[=Editorial changes=] or [=substantive changes=] to a [=charter=] (including [[#charter-extension|extensions]])
+	that do not affect the scope of the group's work
+	or the way the group functions in any significant way
+	are deemed <dfn>minor changes</dfn> and
 	<em class=rfc2119>may</em> be approved by a [=Team Decision=],
 	in which case they do not require [=charter refinement=] nor [=Advisory Committee Review=].
-	The following are examples of such changes:
-	the addition of an in-scope deliverable,
+	Any expansion of the scope of the [=charter=]
+	or addition of a new [=REC track=] deliverable
+	that does not fall within the scope of an existing deliverable
+	is a major, not [=minor change|minor=], change.
+	The following are examples of [=minor changes=]:
+	the renaming or restructuring (e.g. splitting or combining) of existing in-scope deliverables,
+	the addition of new [[#note-track|Note track]] deliverables that help explain the group’s work
 	a change of [=Team Contact=],
 	or a change of [=Chair=].
+	[=Minor changes=], other than a change of [=Team Contact=],
+	<em class=rfc2119>should</em> have the [=consensus=] of the group.
 
 	The [=Team=] <em class=rfc2119>may</em> nevertheless choose
 	to initiate [=charter refinement=] and/or [=Advisory Committee Review=]

From f1c2e0d8335f030bf05a0ad17affa87756199ed6 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 13 May 2025 19:34:11 +0900
Subject: [PATCH 199/237] fix typo

Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 94a9ec64..2e6e2669 100644
--- a/index.bs
+++ b/index.bs
@@ -2002,7 +2002,7 @@ New Charters and Major Changes</h4>
 	and any change that is not a [=minor change=] (per [[#charter-minor-changes]]) to an already-approved [=charter=]
 	of a [=Working Group=] or [=Interest Group=]
 	<em class=rfc2119>must</em> be approved by a [=W3C Decision=] following an [=AC Review=] of that [=charter=].
-	Moditications to a [=charter=] <em class=rfc2119>should</em> have the [=consensus=] of the group.
+	Modifications to a [=charter=] <em class=rfc2119>should</em> have the [=consensus=] of the group.
 
 	The review period <em class=rfc2119>must</em> be at least 28 days.
 	Any [=Advisory Committee representative=] <em class=rfc2119>may</em> request an extended review period

From 76b533dc50a02653461ceb42debd16012f3b3696 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 15 May 2025 00:02:32 +0900
Subject: [PATCH 200/237] Make all changes of scope major changes

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 2e6e2669..9d4b320f 100644
--- a/index.bs
+++ b/index.bs
@@ -2029,7 +2029,7 @@ Minor Changes to Active Charters</h4>
 	are deemed <dfn>minor changes</dfn> and
 	<em class=rfc2119>may</em> be approved by a [=Team Decision=],
 	in which case they do not require [=charter refinement=] nor [=Advisory Committee Review=].
-	Any expansion of the scope of the [=charter=]
+	Any change to the scope of the [=charter=]
 	or addition of a new [=REC track=] deliverable
 	that does not fall within the scope of an existing deliverable
 	is a major, not [=minor change|minor=], change.

From 850ba37cafbc410dbaf447af19b719a17b782e86 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 13 May 2025 10:41:54 +0900
Subject: [PATCH 201/237] Drop expectation to republish document when there are
 no changes

Closes #1013

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/index.bs b/index.bs
index 9d4b320f..7b75945e 100644
--- a/index.bs
+++ b/index.bs
@@ -3899,10 +3899,6 @@ Revising a Working Draft</h4>
 	to the previous published document
 	that would benefit from review beyond the Working Group.
 
-	If 6 months elapse without significant changes to a specification,
-	a Working Group <em class="rfc2119">should</em> publish a revised [=Working Draft=],
-	whose status section <em class="rfc2119">should</em> indicate reasons for the lack of change.
-
 	To publish a revision of a Working draft, a Working Group:
 
 	<ul>

From 24d728b4f36bbe8997a540d1a4af1e8eb0202c85 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 15 May 2025 00:09:26 +0900
Subject: [PATCH 202/237] Update changelog

---
 index.bs | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/index.bs b/index.bs
index 7b75945e..7ed33c59 100644
--- a/index.bs
+++ b/index.bs
@@ -5710,6 +5710,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
 					in addition to Working Groups.
 					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>)
+
+				<li>
+					Drop the requirement to publish every 6 months if nothing has changed.
+					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>)
 			</ul>
 
 		<dt>Changes to chartering
@@ -5727,6 +5731,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 				<li>
 					Require Chairs to be listed in Charters.
 					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
+
+				<li>
+					Be more specific about which types of changes to a charter must go through AC Review.
+					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>)
 			</ul>
 
 		<dt>Other changes

From bf9fd28466429cf434ab5e8a09b6892f4b92bb07 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Fri, 16 May 2025 00:12:38 +0900
Subject: [PATCH 203/237] Reorder changes section

---
 index.bs | 82 ++++++++++++++++++++++++++++----------------------------
 1 file changed, 41 insertions(+), 41 deletions(-)

diff --git a/index.bs b/index.bs
index 7ed33c59..b2c890a1 100644
--- a/index.bs
+++ b/index.bs
@@ -5608,10 +5608,6 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 		<dt>Changes to formal decision making and escalation
 		<dd>
 			<ul>
-				<li>
-					Put constraints on the timing of making Formal Objections public.
-					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
-
 				<li>
 					Adjust the rules guiding initiation of Councils,
 					to make the deadline strict,
@@ -5622,26 +5618,35 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					Make the Council's short-circuit a little more flexible.
 					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
 
-				<li>
-					Exclude TAG/AB from voting on their own decisions/proposals.
-					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)
-
-				<li>
-					Council dismissal vote counts must be reported.
-					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)
-
 				<li>
 					Adjust AC appeal vote threshold based on participation,
 					aligning with the thresholds and super majority requirements
 					for "Requisite Member Vote" from the W3C Bylaws.
 					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
 
+				<li>
+					Exclude TAG/AB from voting on their own decisions/proposals.
+					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)
+
 				<li>
 					Fine-tune the rules about
 					how changes can be incorporated into a proposal
 					following an AC Review.
 					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
 
+				<li>
+					Limit the involvement of Tim Berners-Lee to the TAG proper,
+					not including the Council.
+					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>)
+
+				<li>
+					Council dismissal vote counts must be reported.
+					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)
+
+				<li>
+					Require documentation of how Formal Objections get resolved.
+					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>)
+
 				<li>
 					Let the originator of a proposal decide whether to try again
 					after addressing feedback
@@ -5649,9 +5654,8 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
 
 				<li>
-					Limit the involvement of Tim Berners-Lee to the TAG proper,
-					not including the Council.
-					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>)
+					Put constraints on the timing of making Formal Objections public.
+					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
 			</ul>
 
 		<dt>Changes to technical reports and their publication
@@ -5675,6 +5679,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					and nobody was using it.
 					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>)
 
+				<li>
+					Drop the requirement to publish every 6 months if nothing has changed.
+					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>)
+
 				<li>
 					Add a requirement to make progress on external issues for update requests
 					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>)
@@ -5683,6 +5691,11 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					Enable Team to replace defunct registry custodians when no-one else can.
 					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>)
 
+				<li>
+					Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
+					in addition to Working Groups.
+					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>)
+
 				<li>
 					Rename “registry sections” to [=embedded registries=]
 					to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
@@ -5705,15 +5718,6 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					that described whether and how the Team can maintain technical reports
 					that no longer have a Group chartered to maintain them.
 					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
-
-				<li>
-					Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
-					in addition to Working Groups.
-					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>)
-
-				<li>
-					Drop the requirement to publish every 6 months if nothing has changed.
-					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>)
 			</ul>
 
 		<dt>Changes to chartering
@@ -5740,6 +5744,14 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 		<dt>Other changes
 		<dd>
 			<ul>
+				<li>
+					Reuse the bylaws’ notion of Good Standing,
+					and restrict TAG and AB elections
+					as well as AC Votes where a decision is made based on counting ballots
+					to Members in Good Standing.
+					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a>
+					and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>)
+
 				<li>
 					Clarify how the outcome of certain ballots are determined.
 					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)
@@ -5748,11 +5760,6 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					Stop citing the superseded TAG charter.
 					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)
 
-				<li>
-					The URL of this document was changed
-					from /Consortium/Process/ to /policies/process/
-					for better integration in the W3C website architecture.
-
 				<li>
 					Shift most of the non-normative discussion about Workshops to [[GUIDE]],
 					and reorganize the remaining normative requirements.
@@ -5766,18 +5773,6 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a>
 					and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>)
 
-				<li>
-					Reuse the bylaws’ notion of Good Standing,
-					and restrict TAG and AB elections
-					as well as AC Votes where a decision is made based on counting ballots
-					to Members in Good Standing.
-					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a>
-					and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>)
-
-				<li>
-					Require documentation of how Formal Objections get resolved.
-					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>)
-
 				<li>
 					Clarify amount of leeway around incomplete nominations to TAG or AB elections.
 					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>)
@@ -5785,6 +5780,11 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 				<li>
 					Simplify provisions regarding substitute representatives and proxies.
 					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
+
+				<li>
+					The URL of this document was changed
+					from /Consortium/Process/ to /policies/process/
+					for better integration in the W3C website architecture.
 			</ul>
 
 

From 4bd1bf1b72473b73c87739ffb5833b2008bed128 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 08:48:06 +0900
Subject: [PATCH 204/237] Update link in changelog section

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index b2c890a1..962a1ad9 100644
--- a/index.bs
+++ b/index.bs
@@ -5596,7 +5596,7 @@ Appendix C: Changes</h2>
 Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></h3>
 
 	<p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
-	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%22+is%3Aclosed">list of issues addressed</a>,
+	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
 	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2F">diff from Process 2023 to this latest version</a>,
 	as well as
 	a <a href="https://github.com/w3c/process/compare/p2023_1...main">detailed log of all changes since then</a>

From e6692641f05160748619a08757f70dfef3abbac1 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 08:58:34 +0900
Subject: [PATCH 205/237] Save snapshot of ED for wide review

---
 snapshots/2025-05.html | 6478 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 6478 insertions(+)
 create mode 100644 snapshots/2025-05.html

diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
new file mode 100644
index 00000000..676c1c19
--- /dev/null
+++ b/snapshots/2025-05.html
@@ -0,0 +1,6478 @@
+<!doctype html><html lang="en">
+ <head>
+  <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+  <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
+  <title>W3C Process Document</title>
+  <meta content="CG-DRAFT" name="w3c-status">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/cg-draft" rel="stylesheet">
+  <meta content="Bikeshed version b25686b9f, updated Fri Mar 14 14:15:20 2025 -0700" name="generator">
+  <link href="https://www.w3.org/policies/process/" rel="canonical">
+  <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
+  <meta content="4bd1bf1b72473b73c87739ffb5833b2008bed128" name="revision">
+  <meta content="dark light" name="color-scheme">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
+<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>
+<style>/* Boilerplate: style-autolinks */
+.css.css, .property.property, .descriptor.descriptor {
+    color: var(--a-normal-text);
+    font-size: inherit;
+    font-family: inherit;
+}
+.css::before, .property::before, .descriptor::before {
+    content: "‘";
+}
+.css::after, .property::after, .descriptor::after {
+    content: "’";
+}
+.property, .descriptor {
+    /* Don't wrap property and descriptor names */
+    white-space: nowrap;
+}
+.type { /* CSS value <type> */
+    font-style: italic;
+}
+pre .property::before, pre .property::after {
+    content: "";
+}
+[data-link-type="property"]::before,
+[data-link-type="propdesc"]::before,
+[data-link-type="descriptor"]::before,
+[data-link-type="value"]::before,
+[data-link-type="function"]::before,
+[data-link-type="at-rule"]::before,
+[data-link-type="selector"]::before,
+[data-link-type="maybe"]::before {
+    content: "‘";
+}
+[data-link-type="property"]::after,
+[data-link-type="propdesc"]::after,
+[data-link-type="descriptor"]::after,
+[data-link-type="value"]::after,
+[data-link-type="function"]::after,
+[data-link-type="at-rule"]::after,
+[data-link-type="selector"]::after,
+[data-link-type="maybe"]::after {
+    content: "’";
+}
+
+[data-link-type].production::before,
+[data-link-type].production::after,
+.prod [data-link-type]::before,
+.prod [data-link-type]::after {
+    content: "";
+}
+
+[data-link-type=element],
+[data-link-type=element-attr] {
+    font-family: Menlo, Consolas, "DejaVu Sans Mono", monospace;
+    font-size: .9em;
+}
+[data-link-type=element]::before { content: "<" }
+[data-link-type=element]::after  { content: ">" }
+
+[data-link-type=biblio] {
+    white-space: pre;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --selflink-text: black;
+        --selflink-bg: silver;
+        --selflink-hover-text: white;
+    }
+}
+</style>
+<style>/* Boilerplate: style-colors */
+/* Any --*-text not paired with a --*-bg is assumed to have a transparent bg */
+:root {
+    color-scheme: light dark;
+
+    --text: black;
+    --bg: white;
+
+    --unofficial-watermark: url(https://www.w3.org/StyleSheets/TR/2016/logos/UD-watermark);
+
+    --logo-bg: #1a5e9a;
+    --logo-active-bg: #c00;
+    --logo-text: white;
+
+    --tocnav-normal-text: #707070;
+    --tocnav-normal-bg: var(--bg);
+    --tocnav-hover-text: var(--tocnav-normal-text);
+    --tocnav-hover-bg: #f8f8f8;
+    --tocnav-active-text: #c00;
+    --tocnav-active-bg: var(--tocnav-normal-bg);
+
+    --tocsidebar-text: var(--text);
+    --tocsidebar-bg: #f7f8f9;
+    --tocsidebar-shadow: rgba(0,0,0,.1);
+    --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+    --toclink-text: var(--text);
+    --toclink-underline: #3980b5;
+    --toclink-visited-text: var(--toclink-text);
+    --toclink-visited-underline: #054572;
+
+    --heading-text: #005a9c;
+
+    --hr-text: var(--text);
+
+    --algo-border: #def;
+
+    --del-text: red;
+    --del-bg: transparent;
+    --ins-text: #080;
+    --ins-bg: transparent;
+
+    --a-normal-text: #034575;
+    --a-normal-underline: #bbb;
+    --a-visited-text: var(--a-normal-text);
+    --a-visited-underline: #707070;
+    --a-hover-bg: rgba(75%, 75%, 75%, .25);
+    --a-active-text: #c00;
+    --a-active-underline: #c00;
+
+    --blockquote-border: silver;
+    --blockquote-bg: transparent;
+    --blockquote-text: currentcolor;
+
+    --issue-border: #e05252;
+    --issue-bg: #fbe9e9;
+    --issue-text: var(--text);
+    --issueheading-text: #831616;
+
+    --example-border: #e0cb52;
+    --example-bg: #fcfaee;
+    --example-text: var(--text);
+    --exampleheading-text: #574b0f;
+
+    --note-border: #52e052;
+    --note-bg: #e9fbe9;
+    --note-text: var(--text);
+    --noteheading-text: hsl(120, 70%, 30%);
+    --notesummary-underline: silver;
+
+    --assertion-border: #aaa;
+    --assertion-bg: #eee;
+    --assertion-text: black;
+
+    --advisement-border: orange;
+    --advisement-bg: #fec;
+    --advisement-text: var(--text);
+    --advisementheading-text: #b35f00;
+
+    --warning-border: red;
+    --warning-bg: hsla(40,100%,50%,0.95);
+    --warning-text: var(--text);
+
+    --amendment-border: #330099;
+    --amendment-bg: #F5F0FF;
+    --amendment-text: var(--text);
+    --amendmentheading-text: #220066;
+
+    --def-border: #8ccbf2;
+    --def-bg: #def;
+    --def-text: var(--text);
+    --defrow-border: #bbd7e9;
+
+    --datacell-border: silver;
+
+    --indexinfo-text: #707070;
+
+    --indextable-hover-text: black;
+    --indextable-hover-bg: #f7f8f9;
+
+    --outdatedspec-bg: rgba(0, 0, 0, .5);
+    --outdatedspec-text: black;
+    --outdated-bg: maroon;
+    --outdated-text: white;
+    --outdated-shadow: red;
+
+    --editedrec-bg: darkorange;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --text: #ddd;
+        --bg: black;
+
+        --unofficial-watermark: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='400' height='400'%3E%3Cg fill='%23100808' transform='translate(200 200) rotate(-45) translate(-200 -200)' stroke='%23100808' stroke-width='3'%3E%3Ctext x='50%25' y='220' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EUNOFFICIAL%3C/text%3E%3Ctext x='50%25' y='305' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EDRAFT%3C/text%3E%3C/g%3E%3C/svg%3E");
+
+        --logo-bg: #1a5e9a;
+        --logo-active-bg: #c00;
+        --logo-text: white;
+
+        --tocnav-normal-text: #999;
+        --tocnav-normal-bg: var(--bg);
+        --tocnav-hover-text: var(--tocnav-normal-text);
+        --tocnav-hover-bg: #080808;
+        --tocnav-active-text: #f44;
+        --tocnav-active-bg: var(--tocnav-normal-bg);
+
+        --tocsidebar-text: var(--text);
+        --tocsidebar-bg: #080808;
+        --tocsidebar-shadow: rgba(255,255,255,.1);
+        --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+        --toclink-text: var(--text);
+        --toclink-underline: #6af;
+        --toclink-visited-text: var(--toclink-text);
+        --toclink-visited-underline: #054572;
+
+        --heading-text: #8af;
+
+        --hr-text: var(--text);
+
+        --algo-border: #456;
+
+        --del-text: #f44;
+        --del-bg: transparent;
+        --ins-text: #4a4;
+        --ins-bg: transparent;
+
+        --a-normal-text: #6af;
+        --a-normal-underline: #555;
+        --a-visited-text: var(--a-normal-text);
+        --a-visited-underline: var(--a-normal-underline);
+        --a-hover-bg: rgba(25%, 25%, 25%, .2);
+        --a-active-text: #f44;
+        --a-active-underline: var(--a-active-text);
+
+        --borderedblock-bg: rgba(255, 255, 255, .05);
+
+        --blockquote-border: silver;
+        --blockquote-bg: var(--borderedblock-bg);
+        --blockquote-text: currentcolor;
+
+        --issue-border: #e05252;
+        --issue-bg: var(--borderedblock-bg);
+        --issue-text: var(--text);
+        --issueheading-text: hsl(0deg, 70%, 70%);
+
+        --example-border: hsl(50deg, 90%, 60%);
+        --example-bg: var(--borderedblock-bg);
+        --example-text: var(--text);
+        --exampleheading-text: hsl(50deg, 70%, 70%);
+
+        --note-border: hsl(120deg, 100%, 35%);
+        --note-bg: var(--borderedblock-bg);
+        --note-text: var(--text);
+        --noteheading-text: hsl(120, 70%, 70%);
+        --notesummary-underline: silver;
+
+        --assertion-border: #444;
+        --assertion-bg: var(--borderedblock-bg);
+        --assertion-text: var(--text);
+
+        --advisement-border: orange;
+        --advisement-bg: #222218;
+        --advisement-text: var(--text);
+        --advisementheading-text: #f84;
+
+        --warning-border: red;
+        --warning-bg: hsla(40,100%,20%,0.95);
+        --warning-text: var(--text);
+
+        --amendment-border: #330099;
+        --amendment-bg: #080010;
+        --amendment-text: var(--text);
+        --amendmentheading-text: #cc00ff;
+
+        --def-border: #8ccbf2;
+        --def-bg: #080818;
+        --def-text: var(--text);
+        --defrow-border: #136;
+
+        --datacell-border: silver;
+
+        --indexinfo-text: #aaa;
+
+        --indextable-hover-text: var(--text);
+        --indextable-hover-bg: #181818;
+
+        --outdatedspec-bg: rgba(255, 255, 255, .5);
+        --outdatedspec-text: black;
+        --outdated-bg: maroon;
+        --outdated-text: white;
+        --outdated-shadow: red;
+
+        --editedrec-bg: darkorange;
+    }
+    /* In case a transparent-bg image doesn't expect to be on a dark bg,
+       which is quite common in practice... */
+    img { background: white; }
+}
+</style>
+<style>/* Boilerplate: style-counters */
+body {
+    counter-reset: example figure issue;
+}
+.issue {
+    counter-increment: issue;
+}
+.issue:not(.no-marker)::before {
+    content: "Issue " counter(issue);
+}
+
+.example {
+    counter-increment: example;
+}
+.example:not(.no-marker)::before {
+    content: "Example " counter(example);
+}
+.invalid.example:not(.no-marker)::before,
+.illegal.example:not(.no-marker)::before {
+    content: "Invalid Example" counter(example);
+}
+
+figcaption {
+    counter-increment: figure;
+}
+figcaption:not(.no-marker)::before {
+    content: "Figure " counter(figure) " ";
+}
+</style>
+<style>/* Boilerplate: style-dfn-panel */
+:root {
+    --dfnpanel-bg: #ddd;
+    --dfnpanel-text: var(--text);
+    --dfnpanel-target-bg: #ffc;
+    --dfnpanel-target-outline: orange;
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --dfnpanel-bg: #222;
+        --dfnpanel-text: var(--text);
+        --dfnpanel-target-bg: #333;
+        --dfnpanel-target-outline: silver;
+    }
+}
+.dfn-panel {
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.75em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--dfnpanel-bg);
+    color: var(--dfnpanel-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+.dfn-panel:not(.on) { display: none; }
+.dfn-panel * { margin: 0; padding: 0; text-indent: 0; }
+.dfn-panel > b { display: block; }
+.dfn-panel a { color: var(--dfnpanel-text); }
+.dfn-panel a:not(:hover) { text-decoration: none !important; border-bottom: none !important; }
+.dfn-panel a:focus {
+    outline: 5px auto Highlight;
+    outline: 5px auto -webkit-focus-ring-color;
+}
+.dfn-panel > b + b { margin-top: 0.25em; }
+.dfn-panel ul { padding: 0 0 0 1em; list-style: none; }
+.dfn-panel li a {
+    max-width: calc(300px - 1.5em - 1em);
+    overflow: hidden;
+    text-overflow: ellipsis;
+}
+
+.dfn-panel.activated {
+    display: inline-block;
+    position: fixed;
+    left: 8px;
+    bottom: 2em;
+    margin: 0 auto;
+    max-width: calc(100vw - 1.5em - .4em - .5em);
+    max-height: 30vh;
+    transition: left 1s ease-out, bottom 1s ease-out;
+}
+
+.dfn-panel .link-item:hover {
+    text-decoration: underline;
+}
+.dfn-panel .link-item .copy-icon {
+    opacity: 0;
+}
+.dfn-panel .link-item:hover .copy-icon,
+.dfn-panel .link-item .copy-icon:focus {
+    opacity: 1;
+}
+
+.dfn-panel .copy-icon {
+    display: inline-block;
+    margin-right: 0.5em;
+    width: 0.85em;
+    height: 1em;
+    border-radius: 3px;
+    background-color: #ccc;
+    cursor: pointer;
+}
+
+.dfn-panel .copy-icon .icon {
+    width: 100%;
+    height: 100%;
+    background-color: #fff;
+    display: flex;
+    justify-content: center;
+    align-items: center;
+    position: relative;
+}
+
+.dfn-panel .copy-icon .icon::before {
+    content: "";
+    position: absolute;
+    top: 0;
+    left: 0;
+    width: 100%;
+    height: 100%;
+    border: 1px solid black;
+    background-color: #ccc;
+    opacity: 0.25;
+    transform: translate(3px, -3px);
+}
+
+.dfn-panel .copy-icon:active .icon::before {
+    opacity: 1;
+}
+
+.dfn-paneled[role="button"] { cursor: help; }
+
+.highlighted {
+    animation: target-fade 3s;
+}
+
+@keyframes target-fade {
+    from {
+        background-color: var(--dfnpanel-target-bg);
+        outline: 5px solid var(--dfnpanel-target-outline);
+    }
+    to {
+        color: var(--a-normal-text);
+        background-color: transparent;
+        outline: transparent;
+    }
+}
+</style>
+<style>/* Boilerplate: style-issues */
+a[href].issue-return {
+    float: right;
+    float: inline-end;
+    color: var(--issueheading-text);
+    font-weight: bold;
+    text-decoration: none;
+}
+</style>
+<style>/* Boilerplate: style-md-lists */
+/* This is a weird hack for me not yet following the commonmark spec
+   regarding paragraph and lists. */
+[data-md] > :first-child {
+    margin-top: 0;
+}
+[data-md] > :last-child {
+    margin-bottom: 0;
+}
+</style>
+<style>/* Boilerplate: style-ref-hints */
+:root {
+    --ref-hint-bg: #ddd;
+    --ref-hint-text: var(--text);
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --ref-hint-bg: #222;
+        --ref-hint-text: var(--text);
+    }
+}
+
+.ref-hint {
+    display: inline-block;
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.5em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--ref-hint-bg);
+    color: var(--ref-hint-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+
+.ref-hint * { margin: 0; padding: 0; text-indent: 0; }
+
+.ref-hint ul { padding: 0 0 0 1em; list-style: none; }
+</style>
+<style>/* Boilerplate: style-selflinks */
+:root {
+    --selflink-text: white;
+    --selflink-bg: gray;
+    --selflink-hover-text: black;
+}
+.heading, .issue, .note, .example, li, dt {
+    position: relative;
+}
+a.self-link {
+    position: absolute;
+    top: 0;
+    left: calc(-1 * (3.5rem - 26px));
+    width: calc(3.5rem - 26px);
+    height: 2em;
+    text-align: center;
+    border: none;
+    transition: opacity .2s;
+    opacity: .5;
+}
+a.self-link:hover {
+    opacity: 1;
+}
+.heading > a.self-link {
+    font-size: 83%;
+}
+.example > a.self-link,
+.note > a.self-link,
+.issue > a.self-link {
+    /* These blocks are overflow:auto, so positioning outside
+       doesn't work. */
+    left: auto;
+    right: 0;
+}
+li > a.self-link {
+    left: calc(-1 * (3.5rem - 26px) - 2em);
+}
+dfn > a.self-link {
+    top: auto;
+    left: auto;
+    opacity: 0;
+    width: 1.5em;
+    height: 1.5em;
+    background: var(--selflink-bg);
+    color: var(--selflink-text);
+    font-style: normal;
+    transition: opacity .2s, background-color .2s, color .2s;
+}
+dfn:hover > a.self-link {
+    opacity: 1;
+}
+dfn > a.self-link:hover {
+    color: var(--selflink-hover-text);
+}
+
+a.self-link::before            { content: "¶"; }
+.heading > a.self-link::before { content: "§"; }
+dfn > a.self-link::before      { content: "#"; }
+</style>
+ <body class="h-entry">
+  <div class="head">
+   <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
+   <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types/#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2025-05-19">19 May 2025</time></p>
+   <details open>
+    <summary>More details about this document</summary>
+    <div data-fill-with="spec-metadata">
+     <dl>
+      <dt>This version:
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/snapshots/2025-05</a>
+      <dt>Editor’s Draft:
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/</a>
+      <dt>Latest published version:
+      <dd><a href="https://www.w3.org/policies/process/">https://www.w3.org/policies/process/</a>
+      <dt>Previous Versions:
+      <dd><a href="https://www.w3.org/policies/process/20231103/" rel="prev">https://www.w3.org/policies/process/20231103/</a>
+      <dt>Feedback:
+      <dd><a href="https://github.com/w3c/process/issues/">Github (preferred)</a>
+      <dd><a href="https://lists.w3.org/Archives/Public/public-w3process/">Public mailing list</a>
+      <dd><a href="https://lists.w3.org/Archives/Member/process-issues">Member-only mailing list</a>
+      <dt class="editor">Editors:
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://fantasai.inkedblade.net/contact">Elika J. Etemad / fantasai</a> (<span class="p-org org">Apple</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://florian.rivoal.net/">Florian Rivoal</a> (<span class="p-org org">Invited Expert</span>)
+      <dt class="editor">Former Editors:
+      <dd class="editor p-author h-card vcard"><span class="p-name fn">Natasha Rooney</span> (<span class="p-org org">Invited Expert</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://yandex.com">Charles McCathie Nevile</a> (<span class="p-org org">Yandex</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://www.w3.org/">Ian Jacobs</a> (<span class="p-org org">W3C</span>)
+     </dl>
+    </div>
+   </details>
+   <div data-fill-with="warning"></div>
+   <p class="copyright" data-fill-with="copyright"><a href="https://www.w3.org/policies/#copyright">Copyright</a> © 2025 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/policies/#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/policies/#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/copyright/software-license/" rel="license" title="W3C Software and Document License">permissive document license</a> rules apply. </p>
+   <hr title="Separator for header">
+  </div>
+  <div class="p-summary" data-fill-with="abstract">
+   <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></h2>
+   <p>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.</p>
+   <p>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>.</p>
+  </div>
+  <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content">Status of this document</span></h2>
+  <div data-fill-with="status">
+   <p> W3C, including all existing chartered groups,
+	follows the <a href="https://www.w3.org/policies/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
+	working within the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a> (which anyone can join).
+	This is a snaposhot of the Draft Community Group Report for the proposed next version of the W3C Process Document,
+	taken on the 19 May 2025,
+	to serve as the basis for informal and wide review.</p>
+   <p>This document,
+which is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 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.</p>
+   <p> A <a href="#changes">history of substantial changes</a> from previous versions of the Process Document is provided. </p>
+  </div>
+  <div data-fill-with="at-risk"></div>
+  <nav data-fill-with="table-of-contents" id="toc">
+   <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
+   <ol class="toc" role="directory">
+    <li><a href="#Intro"><span class="secno">1</span> <span class="content"> Introduction</span></a>
+    <li>
+     <a href="#Organization"><span class="secno">2</span> <span class="content"> Members and the Team</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Members"><span class="secno">2.1</span> <span class="content"> Members</span></a>
+       <ol class="toc">
+        <li><a href="#MemberBenefits"><span class="secno">2.1.1</span> <span class="content"> Rights of Members</span></a>
+        <li>
+         <a href="#RelatedAndAssociatedMembers"><span class="secno">2.1.2</span> <span class="content"> Member Associations and Related Members</span></a>
+         <ol class="toc">
+          <li><a href="#MemberAssoc"><span class="secno">2.1.2.1</span> <span class="content"> Membership Associations</span></a>
+          <li><a href="#MemberRelated"><span class="secno">2.1.2.2</span> <span class="content"> Related Members</span></a>
+         </ol>
+        <li><a href="#standing"><span class="secno">2.1.3</span> <span class="content"> Good Standing</span></a>
+       </ol>
+      <li><a href="#Team"><span class="secno">2.2</span> <span class="content"> The W3C Team</span></a>
+     </ol>
+    <li>
+     <a href="#groups"><span class="secno">3</span> <span class="content"> Groups and Participation</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Policies"><span class="secno">3.1</span> <span class="content"> Policies for Participation in W3C Groups</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#ParticipationCriteria"><span class="secno">3.1.1</span> <span class="content"> Individual Participation Criteria</span></a>
+         <ol class="toc">
+          <li><a href="#discipline"><span class="secno">3.1.1.1</span> <span class="content"> Expectations and Discipline</span></a>
+          <li><a href="#coi"><span class="secno">3.1.1.2</span> <span class="content"> Conflict of Interest Policy</span></a>
+          <li><a href="#member-rep"><span class="secno">3.1.1.3</span> <span class="content"> Individuals Representing a Member Organization</span></a>
+         </ol>
+        <li>
+         <a href="#GeneralMeetings"><span class="secno">3.1.2</span> <span class="content"> Meetings</span></a>
+         <ol class="toc">
+          <li><a href="#meeting-schedules"><span class="secno">3.1.2.1</span> <span class="content"> Meeting Scheduling and Announcements</span></a>
+          <li><a href="#meeting-minutes"><span class="secno">3.1.2.2</span> <span class="content"> Meeting Minutes</span></a>
+          <li><a href="#meeting-recording"><span class="secno">3.1.2.3</span> <span class="content"> Meeting Recordings and Transcripts</span></a>
+         </ol>
+        <li><a href="#tooling"><span class="secno">3.1.3</span> <span class="content"> Tooling and Archiving for Discussions and Publications</span></a>
+        <li><a href="#resignation"><span class="secno">3.1.4</span> <span class="content"> Resignation from a Group</span></a>
+       </ol>
+      <li>
+       <a href="#AC"><span class="secno">3.2</span> <span class="content"> The Advisory Committee (AC)</span></a>
+       <ol class="toc">
+        <li><a href="#ac-role"><span class="secno">3.2.1</span> <span class="content"> Role of the Advisory Committee</span></a>
+        <li><a href="#ac-participation"><span class="secno">3.2.2</span> <span class="content"> Participation in the Advisory Committee</span></a>
+        <li><a href="#ACCommunication"><span class="secno">3.2.3</span> <span class="content"> Advisory Committee Mailing Lists</span></a>
+        <li><a href="#ACMeetings"><span class="secno">3.2.4</span> <span class="content"> Advisory Committee Meetings</span></a>
+       </ol>
+      <li>
+       <a href="#elected-groups"><span class="secno">3.3</span> <span class="content"> Elected Groups: The AB and the TAG</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#AB"><span class="secno">3.3.1</span> <span class="content"> Advisory Board (AB)</span></a>
+         <ol class="toc">
+          <li><a href="#ab-role"><span class="secno">3.3.1.1</span> <span class="content"> Role of the Advisory Board</span></a>
+          <li><a href="#ABParticipation"><span class="secno">3.3.1.2</span> <span class="content"> Composition of the Advisory Board</span></a>
+          <li><a href="#ab-comm"><span class="secno">3.3.1.3</span> <span class="content"> Communications of the Advisory Board</span></a>
+          <li><a href="#ab-bod-liaison"><span class="secno">3.3.1.4</span> <span class="content"> Liaisons between the Advisory Board and the Board of Directors</span></a>
+         </ol>
+        <li>
+         <a href="#TAG"><span class="secno">3.3.2</span> <span class="content"> Technical Architecture Group (TAG)</span></a>
+         <ol class="toc">
+          <li><a href="#tag-role"><span class="secno">3.3.2.1</span> <span class="content"> Role of the Technical Architecture Group</span></a>
+          <li><a href="#tag-participation"><span class="secno">3.3.2.2</span> <span class="content"> Composition of the Technical Architecture Group</span></a>
+          <li><a href="#tag-comm"><span class="secno">3.3.2.3</span> <span class="content"> Communications of the Technical Architecture Group</span></a>
+         </ol>
+        <li>
+         <a href="#AB-TAG-participation"><span class="secno">3.3.3</span> <span class="content"> Participation in Elected Groups</span></a>
+         <ol class="toc">
+          <li><a href="#elected-expectations"><span class="secno">3.3.3.1</span> <span class="content"> Expectations for Elected Groups Participants</span></a>
+          <li><a href="#AB-TAG-constraints"><span class="secno">3.3.3.2</span> <span class="content"> Elected Groups Participation Constraints</span></a>
+          <li><a href="#AB-TAG-elections"><span class="secno">3.3.3.3</span> <span class="content"> Advisory Board and Technical Architecture Group Elections</span></a>
+          <li><a href="#TAG-appointments"><span class="secno">3.3.3.4</span> <span class="content"> Technical Architecture Group Appointments</span></a>
+          <li><a href="#random"><span class="secno">3.3.3.5</span> <span class="content"> Verifiable Random Selection Procedure</span></a>
+          <li><a href="#AB-TAG-vacated"><span class="secno">3.3.3.6</span> <span class="content"> Elected Groups Vacated Seats</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#GAGeneral"><span class="secno">3.4</span> <span class="content"> Chartered Groups: Working Groups and Interest Groups</span></a>
+       <ol class="toc">
+        <li><a href="#ReqsAllGroups"><span class="secno">3.4.1</span> <span class="content"> Requirements for All Chartered Groups</span></a>
+        <li><a href="#group-participation"><span class="secno">3.4.2</span> <span class="content"> Participation in Chartered Groups</span></a>
+        <li>
+         <a href="#chartered-group-participants"><span class="secno">3.4.3</span> <span class="content"> Types of Participants in Chartered Groups</span></a>
+         <ol class="toc">
+          <li><a href="#member-rep-wg"><span class="secno">3.4.3.1</span> <span class="content"> Member Representative in a Working Group</span></a>
+          <li><a href="#member-rep-ig"><span class="secno">3.4.3.2</span> <span class="content"> Member Representative in an Interest Group</span></a>
+          <li><a href="#invited-expert-wg"><span class="secno">3.4.3.3</span> <span class="content"> Invited Expert in a Working Group</span></a>
+          <li><a href="#invited-expert-ig"><span class="secno">3.4.3.4</span> <span class="content"> Invited Expert in an Interest Group</span></a>
+          <li><a href="#team-rep-wg"><span class="secno">3.4.3.5</span> <span class="content"> Team Representative in a Working Group</span></a>
+          <li><a href="#team-rep-ig"><span class="secno">3.4.3.6</span> <span class="content"> Team Representative in an Interest Group</span></a>
+         </ol>
+       </ol>
+     </ol>
+    <li>
+     <a href="#group-lifecycle"><span class="secno">4</span> <span class="content"> Lifecycle of Chartered Groups</span></a>
+     <ol class="toc">
+      <li><a href="#charter-initiation"><span class="secno">4.1</span> <span class="content"> Initiating Charter Refinement</span></a>
+      <li><a href="#charter-development"><span class="secno">4.2</span> <span class="content"> Charter Refinement</span></a>
+      <li><a href="#WGCharter"><span class="secno">4.3</span> <span class="content"> Content of a Charter</span></a>
+      <li>
+       <a href="#CharterReview"><span class="secno">4.4</span> <span class="content"> Charter Review and Approval</span></a>
+       <ol class="toc">
+        <li><a href="#charter-major-changes"><span class="secno">4.4.1</span> <span class="content"> New Charters and Major Changes</span></a>
+        <li><a href="#charter-minor-changes"><span class="secno">4.4.2</span> <span class="content"> Minor Changes to Active Charters</span></a>
+       </ol>
+      <li><a href="#cfp"><span class="secno">4.5</span> <span class="content"> Call for Participation in a Chartered Group</span></a>
+      <li><a href="#charter-extension"><span class="secno">4.6</span> <span class="content"> Charter Extension</span></a>
+      <li><a href="#GeneralTermination"><span class="secno">4.7</span> <span class="content"> Chartered Group Closure</span></a>
+     </ol>
+    <li>
+     <a href="#decisions"><span class="secno">5</span> <span class="content"> Decisions</span></a>
+     <ol class="toc">
+      <li><a href="#decision-types"><span class="secno">5.1</span> <span class="content"> Types of Decisions</span></a>
+      <li>
+       <a href="#consensus-building"><span class="secno">5.2</span> <span class="content"> Consensus Building</span></a>
+       <ol class="toc">
+        <li><a href="#Consensus"><span class="secno">5.2.1</span> <span class="content"> Consensus</span></a>
+        <li><a href="#managing-dissent"><span class="secno">5.2.2</span> <span class="content"> Managing Dissent</span></a>
+        <li><a href="#Votes"><span class="secno">5.2.3</span> <span class="content"> Deciding by Vote</span></a>
+       </ol>
+      <li><a href="#formal-address"><span class="secno">5.3</span> <span class="content"> Formally Addressing an Issue</span></a>
+      <li><a href="#WGChairReopen"><span class="secno">5.4</span> <span class="content"> Reopening a Decision When Presented With New Information</span></a>
+      <li><a href="#registering-objections"><span class="secno">5.5</span> <span class="content"> Registering Formal Objections</span></a>
+      <li>
+       <a href="#addressing-fo"><span class="secno">5.6</span> <span class="content"> Addressing Formal Objections</span></a>
+       <ol class="toc">
+        <li><a href="#team-fo-mediation"><span class="secno">5.6.1</span> <span class="content"> Investigation and Mediation by the Team</span></a>
+        <li>
+         <a href="#council"><span class="secno">5.6.2</span> <span class="content"> W3C Council</span></a>
+         <ol class="toc">
+          <li><a href="#council-composition"><span class="secno">5.6.2.1</span> <span class="content"> Council Composition</span></a>
+          <li><a href="#council-delegation"><span class="secno">5.6.2.2</span> <span class="content"> Extraordinary Delegation</span></a>
+          <li><a href="#council-participation"><span class="secno">5.6.2.3</span> <span class="content"> Council Participation, Dismissal, and Renunciation</span></a>
+          <li><a href="#council-short-circuit"><span class="secno">5.6.2.4</span> <span class="content"> Short Circuit</span></a>
+          <li><a href="#council-chairing"><span class="secno">5.6.2.5</span> <span class="content"> Council Chairing</span></a>
+          <li><a href="#council-convention"><span class="secno">5.6.2.6</span> <span class="content"> Convening the Council</span></a>
+          <li><a href="#council-deliberations"><span class="secno">5.6.2.7</span> <span class="content"> Council Deliberations</span></a>
+          <li><a href="#council-decision"><span class="secno">5.6.2.8</span> <span class="content"> Council Decision Report</span></a>
+          <li><a href="#council-appeals"><span class="secno">5.6.2.9</span> <span class="content"> Appealing Council Decisions</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#ACReview"><span class="secno">5.7</span> <span class="content"> Advisory Committee Reviews and W3C Decisions</span></a>
+       <ol class="toc">
+        <li><a href="#ACReviewStart"><span class="secno">5.7.1</span> <span class="content"> Initiating an Advisory Committee Review</span></a>
+        <li><a href="#ACReviewAfter"><span class="secno">5.7.2</span> <span class="content"> Determining the W3C Decision</span></a>
+       </ol>
+      <li><a href="#ACVotes"><span class="secno">5.8</span> <span class="content"> Advisory Committee Votes</span></a>
+      <li><a href="#ACAppeal"><span class="secno">5.9</span> <span class="content"> Appeal by Advisory Committee Representatives</span></a>
+     </ol>
+    <li>
+     <a href="#Reports"><span class="secno">6</span> <span class="content"> W3C Technical Reports</span></a>
+     <ol class="toc">
+      <li><a href="#recs-and-notes"><span class="secno">6.1</span> <span class="content"> Types of Technical Reports</span></a>
+      <li>
+       <a href="#general-requirements"><span class="secno">6.2</span> <span class="content"> General Requirements for Technical Reports</span></a>
+       <ol class="toc">
+        <li><a href="#publication"><span class="secno">6.2.1</span> <span class="content"> Publication of Technical Reports</span></a>
+        <li>
+         <a href="#doc-reviews"><span class="secno">6.2.2</span> <span class="content"> Reviews and Review Responsibilities</span></a>
+         <ol class="toc">
+          <li><a href="#wide-review"><span class="secno">6.2.2.1</span> <span class="content"> Wide Review</span></a>
+         </ol>
+        <li><a href="#correction-classes"><span class="secno">6.2.3</span> <span class="content"> Classes of Changes</span></a>
+        <li><a href="#errata"><span class="secno">6.2.4</span> <span class="content"> Errata Management</span></a>
+        <li><a href="#candidate-amendments"><span class="secno">6.2.5</span> <span class="content"> Candidate Amendments</span></a>
+        <li><a href="#no-group-maintenance"><span class="secno">6.2.6</span> <span class="content"> Maintenance Without a Group</span></a>
+        <li><a href="#contributor-license"><span class="secno">6.2.7</span> <span class="content"> License Grants from Non-Participants</span></a>
+       </ol>
+      <li>
+       <a href="#rec-track"><span class="secno">6.3</span> <span class="content"> The W3C Recommendation Track</span></a>
+       <ol class="toc">
+        <li><a href="#maturity-stages"><span class="secno">6.3.1</span> <span class="content"> Maturity Stages on the Recommendation Track</span></a>
+        <li><a href="#implementation-experience"><span class="secno">6.3.2</span> <span class="content"> Implementation Experience</span></a>
+        <li><a href="#transition-reqs"><span class="secno">6.3.3</span> <span class="content"> Advancement on the Recommendation Track</span></a>
+        <li><a href="#update-reqs"><span class="secno">6.3.4</span> <span class="content"> Updating Mature Publications on the Recommendation Track</span></a>
+        <li><a href="#first-wd"><span class="secno">6.3.5</span> <span class="content"> Publishing a First Public Working Draft</span></a>
+        <li><a href="#revising-wd"><span class="secno">6.3.6</span> <span class="content"> Revising a Working Draft</span></a>
+        <li><a href="#transition-cr"><span class="secno">6.3.7</span> <span class="content"> Transitioning to Candidate Recommendation</span></a>
+        <li>
+         <a href="#revising-cr"><span class="secno">6.3.8</span> <span class="content"> Revising a Candidate Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#publishing-crrs"><span class="secno">6.3.8.1</span> <span class="content"> Publishing a <span>Candidate Recommendation Snapshot</span></span></a>
+          <li><a href="#publishing-crud"><span class="secno">6.3.8.2</span> <span class="content"> Publishing a <span>Candidate Recommendation Draft</span></span></a>
+         </ol>
+        <li>
+         <a href="#transition-rec"><span class="secno">6.3.9</span> <span class="content"> Transitioning to Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#transition-rec-requirements"><span class="secno">6.3.9.1</span> <span class="content"> Requirements for Transition</span></a>
+          <li><a href="#initiating-rec-review"><span class="secno">6.3.9.2</span> <span class="content"> Initiating Review</span></a>
+          <li><a href="#rec-review-resolution"><span class="secno">6.3.9.3</span> <span class="content"> Resolution of Review</span></a>
+          <li><a href="#rec-next-steps"><span class="secno">6.3.9.4</span> <span class="content"> Next Steps from W3C Recommendation</span></a>
+         </ol>
+        <li>
+         <a href="#revising-rec"><span class="secno">6.3.10</span> <span class="content"> Revising a W3C Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#revised-rec-editorial"><span class="secno">6.3.10.1</span> <span class="content"> Revising a Recommendation: Editorial Changes</span></a>
+          <li><a href="#revised-rec-substantive"><span class="secno">6.3.10.2</span> <span class="content"> Revising a Recommendation: Substantive Changes</span></a>
+          <li><a href="#revised-rec-features"><span class="secno">6.3.10.3</span> <span class="content"> Revising a Recommendation: New Features</span></a>
+          <li><a href="#change-review"><span class="secno">6.3.10.4</span> <span class="content"> Incorporating Candidate Amendments</span></a>
+         </ol>
+        <li><a href="#rec-track-regression"><span class="secno">6.3.11</span> <span class="content"> Regression on the Recommendation Track</span></a>
+        <li>
+         <a href="#tr-end"><span class="secno">6.3.12</span> <span class="content"> Retiring Recommendation Track Documents</span></a>
+         <ol class="toc">
+          <li><a href="#abandon-draft"><span class="secno">6.3.12.1</span> <span class="content"> Abandoning an Unfinished Recommendation</span></a>
+          <li><a href="#rescind-cr"><span class="secno">6.3.12.2</span> <span class="content"> Rescinding a Candidate Recommendation</span></a>
+          <li><a href="#rec-rescind"><span class="secno">6.3.12.3</span> <span class="content"> Abandoning a W3C Recommendation</span></a>
+          <li><a href="#deactivation"><span class="secno">6.3.12.4</span> <span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#note-track"><span class="secno">6.4</span> <span class="content"> The Note Track (Notes and Statements)</span></a>
+       <ol class="toc">
+        <li><a href="#Note"><span class="secno">6.4.1</span> <span class="content"> Group Notes</span></a>
+        <li><a href="#publishing-notes"><span class="secno">6.4.2</span> <span class="content"> Publishing Notes</span></a>
+        <li><a href="#w3c-statement"><span class="secno">6.4.3</span> <span class="content"> Elevating Group Notes to W3C Statement status</span></a>
+        <li><a href="#revising-memo"><span class="secno">6.4.4</span> <span class="content"> Revising W3C Statements</span></a>
+       </ol>
+      <li>
+       <a href="#registries"><span class="secno">6.5</span> <span class="content"> The Registry Track</span></a>
+       <ol class="toc">
+        <li><a href="#reg-def"><span class="secno">6.5.1</span> <span class="content"> Registry Definitions</span></a>
+        <li><a href="#reg-pub"><span class="secno">6.5.2</span> <span class="content"> Publishing Registries</span></a>
+        <li><a href="#reg-table-update"><span class="secno">6.5.3</span> <span class="content"> Updating Registry Tables</span></a>
+        <li><a href="#reg-data-reports"><span class="secno">6.5.4</span> <span class="content"> Registry Data Reports</span></a>
+        <li><a href="#reg-ref-specifications"><span class="secno">6.5.5</span> <span class="content"> Specifications that Reference Registries</span></a>
+        <li><a href="#reg-pat"><span class="secno">6.5.6</span> <span class="content"> Registries and Patents</span></a>
+       </ol>
+      <li><a href="#switching-tracks"><span class="secno">6.6</span> <span class="content"> Switching Tracks</span></a>
+      <li><a href="#further-reading"><span class="secno">6.7</span> <span class="content"> Further reading</span></a>
+     </ol>
+    <li>
+     <a href="#dissemination"><span class="secno">7</span> <span class="content"> <span></span> Dissemination Policies</span></a>
+     <ol class="toc">
+      <li><a href="#pub-com"><span class="secno">7.1</span> <span class="content"> Public Communication</span></a>
+      <li><a href="#confidentiality-levels"><span class="secno">7.2</span> <span class="content"> Confidentiality Levels</span></a>
+      <li><a href="#confidentiality-change"><span class="secno">7.3</span> <span class="content"> Changing Confidentiality Level</span></a>
+     </ol>
+    <li><a href="#Liaisons"><span class="secno">8</span> <span class="content"> Liaisons</span></a>
+    <li><a href="#Submission"><span class="secno">9</span> <span class="content"> Member Submissions</span></a>
+    <li><a href="#GAProcess"><span class="secno">10</span> <span class="content"> Process Evolution</span></a>
+    <li><a href="#old-terms"><span class="secno"></span> <span class="content"> Appendix A: Retired Terminology</span></a>
+    <li><a href="#acks"><span class="secno"></span> <span class="content"> Appendix B: Acknowledgments</span></a>
+    <li>
+     <a href="#changes"><span class="secno"></span> <span class="content"> Appendix C: Changes</span></a>
+     <ol class="toc">
+      <li><a href="#changes-2024"><span class="secno"></span> <span class="content"> Changes since the <span>3 November 2023 Process</span></span></a>
+      <li><a href="#changes-previous"><span class="secno"></span> <span class="content"> Changes since earlier versions</span></a>
+     </ol>
+    <li>
+     <a href="#w3c-conformance"><span class="secno"></span> <span class="content">Conformance</span></a>
+     <ol class="toc">
+      <li><a href="#w3c-conventions"><span class="secno"></span> <span class="content">Document conventions</span></a>
+     </ol>
+    <li>
+     <a href="#index"><span class="secno"></span> <span class="content">Index</span></a>
+     <ol class="toc">
+      <li><a href="#index-defined-here"><span class="secno"></span> <span class="content">Terms defined by this specification</span></a>
+      <li><a href="#index-defined-elsewhere"><span class="secno"></span> <span class="content">Terms defined by reference</span></a>
+     </ol>
+    <li>
+     <a href="#references"><span class="secno"></span> <span class="content">References</span></a>
+     <ol class="toc">
+      <li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
+      <li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
+     </ol>
+   </ol>
+  </nav>
+  <main>
+   <h2 class="no-num no-toc no-ref heading settled" id="pp"><span class="content"> Relation of Process Document to Patent Policy and Other Policies</span></h2>
+   <p>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> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	The <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and other policies
+	incorporated by normative reference as a part of the Process Document
+	are equally binding.</p>
+   <p>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.</p>
+   <p>In the Process Document, the term “participant” refers to an individual, not an organization.</p>
+   <h2 class="no-num no-toc no-ref heading settled" id="terms"><span class="content"> Conformance and specialized terms</span></h2>
+   <p>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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="not-required"><em class="rfc2119">not required</em></dfn> is equivalent to the term <em class="rfc2119">may</em> as defined in RFC2119 <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a>.</p>
+   <p>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.</p>
+   <nav data-fill-with="table-of-contents"></nav>
+   <main>
+    <h2 class="heading settled" data-level="1" id="Intro"><span class="secno">1. </span><span class="content"> Introduction</span><a class="self-link" href="#Intro"></a></h2>
+    <p>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>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>. <a href="#group-participation">Participants</a> in W3C include <a href="#member-rep">representatives of its Members</a> and the <a data-link-type="dfn" href="#team" id="ref-for-team">Team</a>,
+	as well as <a href="#invited-expert-wg">Invited Experts</a> who can bring additional expertise or represent additional stakeholders. <a data-link-type="dfn" href="#team" id="ref-for-team①">Team</a> representatives both contribute to the technical work
+	and help ensure each group’s proper integration with the rest of W3C.</p>
+    <p>W3C’s technical standards, called <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C">W3C Recommendations</a>,
+	are developed by its <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG">Working Groups</a>;
+	W3C also has other types of publications,
+	all described in <a href="#Reports">§ 6 W3C Technical Reports</a>.
+	W3C has various types of groups;
+	this document describes the formation and policies
+	of its chartered <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG">Interest Groups</a>,
+	see <a href="#Policies">§ 3.1 Policies for Participation in W3C Groups</a> and <a href="#GAGeneral">§ 3.4 Chartered Groups: Working Groups and Interest Groups</a>.
+	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> <a data-link-type="biblio" href="#biblio-bg-cg" title="Community and Business Group Process">[BG-CG]</a>.</p>
+    <p>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.</p>
+    <p>Here is a general overview of how W3C initiates standardization of a Web technology:</p>
+    <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 <a data-link-type="dfn" href="#team" id="ref-for-team②">Team</a> 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>
+    <p>Further sections of this Process Document deal with topics including
+	liaisons (<a href="#Liaisons">§ 8 Liaisons</a>),
+	confidentiality (<a href="#dissemination">§ 7 Dissemination Policies</a>),
+	and formal decisions and appeals (<a href="#decisions">§ 5 Decisions</a>).</p>
+    <h2 class="heading settled" data-level="2" id="Organization"><span class="secno">2. </span><span class="content"> Members and the Team</span><a class="self-link" href="#Organization"></a></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 class="heading settled" data-level="2.1" id="Members"><span class="secno">2.1. </span><span class="content"> Members</span><a class="self-link" href="#Members"></a></h3>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Member|Member" data-noexport id="w3c-member">W3C Members</dfn> are
+	organizations subscribed according to a <a href="https://www.w3.org/membership/agreement/">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	They are represented in W3C processes as follows:</p>
+    <ol>
+     <li> One representative per Member organization participates
+			in the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee">Advisory Committee</a> 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>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>;
+	(refer to the public list of <a href="https://www.w3.org/membership/list/">current W3C Members</a> <a data-link-type="biblio" href="#biblio-member-list" title="The list of current W3C Members">[MEMBER-LIST]</a>).
+	The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure
+	that Member participation agreements remain <a href="#Team-only" id="ref-for-Team-only">Team-only</a> and that no Member receives preferential treatment within W3C. </p>
+    <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. </p>
+    <h4 class="heading settled" data-level="2.1.1" id="MemberBenefits"><span class="secno">2.1.1. </span><span class="content"> Rights of Members</span><a class="self-link" href="#MemberBenefits"></a></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> Access to <a href="#Member-only" id="ref-for-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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>. 
+    </ul>
+    <p>Furthermore, subject to further restrictions included in their 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>
+       In <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW">Workshops</a>. 
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>)</p>
+     <li> On the Team, as <a href="#fellows" id="ref-for-fellows">W3C Fellows</a>. 
+    </ul>
+    <p>The rights and benefits of W3C membership <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> are contingent upon conformance to the processes described in this document.
+	Disciplinary action for anyone participating in W3C activities is described in <a href="#discipline">§ 3.1.1.1 Expectations and Discipline</a>.</p>
+    <p>Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member website</a> <a data-link-type="biblio" href="#biblio-member-hp" title="Member website (Member-only access)">[MEMBER-HP]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.2" id="RelatedAndAssociatedMembers"><span class="secno">2.1.2. </span><span class="bs-old-id" id="RelatedAndConsortiumMembers"></span><span class="content"> Member Associations and Related Members</span><a class="self-link" href="#RelatedAndAssociatedMembers"></a></h4>
+    <h5 class="heading settled" data-level="2.1.2.1" id="MemberAssoc"><span class="secno">2.1.2.1. </span><span class="bs-old-id" id="MemberConsortia"></span><span class="content"> Membership Associations</span><a class="self-link" href="#MemberAssoc"></a></h5>
+    <p>A “<dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Member Association | Member Associations" data-noexport id="member-association">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 <a data-link-type="dfn" href="#member-association" id="ref-for-member-association">Member Association</a> merely because it has shareholders or stockholders.
+	If it is not clear whether a prospective Member qualifies as a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association①">Member Association</a>,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo">CEO</a> may reasonably make the determination.
+	For a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association②">Member Association</a>, the rights and privileges of W3C Membership
+	described in the W3C Process Document extend to the <a data-link-type="dfn" href="#member-association" id="ref-for-member-association③">Member Association</a>’s paid staff
+	and Advisory Committee representative.</p>
+    <p><a data-link-type="dfn" href="#member-association" id="ref-for-member-association④">Member Associations</a> <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>
+    <p>For <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑤">Member Associations</a> 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.</p>
+    <p>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.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="2.1.2.2" id="MemberRelated"><span class="secno">2.1.2.2. </span><span class="content"> Related Members</span><a class="self-link" href="#MemberRelated"></a></h5>
+    <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 <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Related Member" id="related-member">related</dfn> if:</p>
+    <ol>
+     <li> Either Member is a <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary">subsidiary</a> of the other, or 
+     <li> Both Members are <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary①">subsidiaries</a> of a common entity, or 
+     <li> The Members have an employment contract or consulting contract that affects W3C participation. 
+    </ol>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="subsidiary">subsidiary</dfn> is an organization of which effective control and/or majority ownership rests with another,
+	single organization.</p>
+    <p><a data-link-type="dfn" href="#related-member" id="ref-for-related-member">Related Members</a> <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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.3" id="standing"><span class="secno">2.1.3. </span><span class="content"> Good Standing</span><a class="self-link" href="#standing"></a></h4>
+    <p><a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member">Members</a> who have not lost Good Standing as defined in the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a> are considered, for the purposes of this Process,
+	to be in <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="good-standing">Good Standing</dfn>.
+	A group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member①">related Members</a> is in Good Standing if
+	at least one of them is in Good Standing.</p>
+    <h3 class="heading settled" data-level="2.2" id="Team"><span class="secno">2.2. </span><span class="bs-old-id" id="def-Director"></span><span class="content"> The W3C Team</span><a class="self-link" href="#Team"></a></h3>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team | W3C Team" id="team">Team</dfn> consists of <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="ceo">CEO</dfn>,
+	W3C paid staff,
+	unpaid interns,
+	and W3C Fellows. <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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> <a data-link-type="biblio" href="#biblio-fellows" title="W3C Fellows Program">[FELLOWS]</a>.
+	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.</p>
+    <p>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. <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision">Team Decisions</a> derive from the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo①">CEO</a>’s authority,
+	even when they are carried out by other members of the <a data-link-type="dfn" href="#team" id="ref-for-team③">Team</a>.</p>
+    <p>Oversight over the <a data-link-type="dfn" href="#team" id="ref-for-team④">Team</a>,
+	budgeting,
+	and other business decisions,
+	is provided by the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="BoD | Board | Board of Directors | W3C Board of Directors" id="bod">W3C Board of Directors</dfn>,
+	rather than managed directly by the Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf">W3C Bylaws</a> for more details
+	on the <a data-link-type="dfn" href="#bod" id="ref-for-bod">Board</a> and overall governance of W3C.</p>
+    <h2 class="heading settled" data-level="3" id="groups"><span class="secno">3. </span><span class="content"> Groups and Participation</span><a class="self-link" href="#groups"></a></h2>
+    <p>For the purposes of this Process, a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="group" data-noexport id="w3c-group">W3C Group</dfn> is one of W3C’s <a href="#wgparticipant" id="ref-for-wgparticipant">Working Groups</a>, <a href="#igparticipant" id="ref-for-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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="participant">participant</dfn> is a member of such a group.</p>
+    <h3 class="heading settled" data-level="3.1" id="Policies"><span class="secno">3.1. </span><span class="content"> Policies for Participation in W3C Groups</span><a class="self-link" href="#Policies"></a></h3>
+    <h4 class="heading settled" data-level="3.1.1" id="ParticipationCriteria"><span class="secno">3.1.1. </span><span class="content"> Individual Participation Criteria</span><a class="self-link" href="#ParticipationCriteria"></a></h4>
+    <h5 class="heading settled" data-level="3.1.1.1" id="discipline"><span class="secno">3.1.1.1. </span><span class="content"> Expectations and Discipline</span><a class="self-link" href="#discipline"></a></h5>
+    <p>There are three qualities an individual is expected to demonstrate in order to participate in W3C:</p>
+    <ol>
+     <li> Technical competence in one’s role; 
+     <li> The ability to act fairly; 
+     <li> Social competence in one’s role. 
+    </ol>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative">Advisory Committee representatives</a> who nominate individuals from their organization for participation in W3C activities
+	are responsible for assessing and attesting to the qualities of those nominees.</p>
+    <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> <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a> and the participation requirements described in
+	“Disclosure”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. </p>
+    <p>The <a data-link-type="dfn" href="#ceo" id="ref-for-ceo②">CEO</a> <em class="rfc2119">may</em> take disciplinary action,
+	including suspending or removing for cause
+	a participant in any group (including the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group">TAG</a>)
+	if serious and/or repeated violations,
+	such as failure to meet the requirements on individual behavior of
+	(a) this process
+	and in particular the Code of Conduct, or
+	(b) the membership agreement, or
+	(c) applicable laws,
+	occur.
+	Refer to the <a href="https://www.w3.org/guide/process/suspension">Guidelines to suspend or remove participants from groups</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.2" id="coi"><span class="secno">3.1.1.2. </span><span class="content"> Conflict of Interest Policy</span><a class="self-link" href="#coi"></a></h5>
+    <p>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.</p>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑤">Team</a> <em class="rfc2119">may</em> appoint a new group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs">Chair</a> 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).</p>
+    <p>The following are some scenarios where disclosure is appropriate:</p>
+    <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>
+    <p>Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the <a data-link-type="dfn" href="#team" id="ref-for-team⑥">Team</a>.</p>
+    <p><a data-link-type="dfn" href="#team" id="ref-for-team⑦">Team</a> 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> <a data-link-type="biblio" href="#biblio-conflict-policy" title="Conflict of Interest Policy for the W3C Team">[CONFLICT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.3" id="member-rep"><span class="secno">3.1.1.3. </span><span class="content"> Individuals Representing a Member Organization</span><a class="self-link" href="#member-rep"></a></h5>
+    <p>Generally, individuals representing a Member in an official capacity within W3C
+	are employees of the Member organization.
+	However, an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①">Advisory Committee representative</a> <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.</p>
+    <p>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 <a data-link-type="dfn" href="#ceo" id="ref-for-ceo③">CEO</a> <em class="rfc2119">may</em> decline
+	to allow an individual designated by an Advisory Committee representative to participate in a group.</p>
+    <p>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>).</p>
+    <h4 class="heading settled" data-level="3.1.2" id="GeneralMeetings"><span class="secno">3.1.2. </span><span class="bs-old-id" id="EventsS"></span><span class="bs-old-id" id="GAEvents"></span><span class="content"> Meetings</span><a class="self-link" href="#GeneralMeetings"></a></h4>
+    <p>The requirements in this section apply to the official meetings of any <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group">W3C group</a>,
+	as well as to official W3C meetings with open-ended participation from the Membership and/or the public,
+	such as <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW①">Workshops</a>.</p>
+    <p>W3C distinguishes two types of meetings:</p>
+    <ol>
+     <li> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 class="dfn-paneled" data-dfn-type="dfn" data-noexport 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>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①">Chair</a> <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 <a data-link-type="dfn" href="#participant" id="ref-for-participant">participant</a>.
+	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.</p>
+    <h5 class="heading settled" data-level="3.1.2.1" id="meeting-schedules"><span class="secno">3.1.2.1. </span><span class="content"> Meeting Scheduling and Announcements</span><a class="self-link" href="#meeting-schedules"></a></h5>
+    <p>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.</p>
+    <p>The following table lists <em class="rfc2119">recommendations</em> for organizing a meeting:</p>
+    <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"><a data-link-type="dfn" href="#minutes" id="ref-for-minutes">Minutes</a> available (after) 
+       <td><span class="time-interval">two weeks</span> 
+       <td><span class="time-interval">48 hours</span> 
+    </table>
+    <p><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 <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW②">Workshops</a>,
+	shorter notice is not allowed.</p>
+    <h5 class="heading settled" data-level="3.1.2.2" id="meeting-minutes"><span class="secno">3.1.2.2. </span><span class="content"> Meeting Minutes</span><a class="self-link" href="#meeting-minutes"></a></h5>
+    <p>Groups <em class="rfc2119">should</em> take and retain <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minutes">minutes</dfn> of their meetings,
+	and <em class="rfc2119">must</em> record
+	any official <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision">group decisions</a> made during the meeting discussions.
+	Details of the discussion leading to such decisions are not required,
+	provided that the rationale for the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision①">group decision</a> is nonetheless clear.</p>
+    <h5 class="heading settled" data-level="3.1.2.3" id="meeting-recording"><span class="secno">3.1.2.3. </span><span class="content"> Meeting Recordings and Transcripts</span><a class="self-link" href="#meeting-recording"></a></h5>
+    <p>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.</p>
+    <h4 class="heading settled" data-level="3.1.3" id="tooling"><span class="secno">3.1.3. </span><span class="content"> Tooling and Archiving for Discussions and Publications</span><a class="self-link" href="#tooling"></a></h4>
+    <p>For <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group①">W3C Groups</a> 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:</p>
+    <ul>
+     <li id="report-stability"><a class="self-link" href="#report-stability"></a> 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"><a class="self-link" href="#report-accessibility"></a> 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">
+      <a class="self-link" href="#discussion-archiving"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> The lack, or loss, of such archives does not by itself
+			invalidate an otherwise-valid decision.</p>
+     <li id="tool-accessibility">
+      <a class="self-link" href="#tool-accessibility"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> If a new participant joins who cannot use the tool,
+			this can require the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②">Working Group</a> to change its tooling
+			or operate some workaround.</p>
+     <li id="where-is-your-stuff"><a class="self-link" href="#where-is-your-stuff"></a> 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>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧">Team</a> is responsible for ensuring adherence to these rules
+	and for bringing any group not in compliance into compliance.</p>
+    <h4 class="heading settled" data-level="3.1.4" id="resignation"><span class="secno">3.1.4. </span><span class="content"> Resignation from a Group</span><a class="self-link" href="#resignation"></a></h4>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑨">Team</a>,
+	the Member and their representatives
+	or the Invited Expert
+	will be deemed to have resigned from the relevant group.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪">Team</a> <em class="rfc2119">must</em> record the notification.
+	See “Exclusion and Resignation from the Working Group” in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for information about obligations remaining after resignation from certain groups.</p>
+    <h3 class="heading settled" data-level="3.2" id="AC"><span class="secno">3.2. </span><span class="content"> The Advisory Committee (AC)</span><a class="self-link" href="#AC"></a></h3>
+    <h4 class="heading settled" data-level="3.2.1" id="ac-role"><span class="secno">3.2.1. </span><span class="content"> Role of the Advisory Committee</span><a class="self-link" href="#ac-role"></a></h4>
+    <p id="ReviewAppeal"> The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee|AC" id="advisory-committee">Advisory Committee</dfn> represents
+	the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member①">Members</a> of W3C at large.
+	It is responsible for: </p>
+    <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>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> of a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision">W3C decision</a> or <a data-link-type="dfn" href="#team" id="ref-for-team①①">Team</a>’s decision.</p>
+    <p>See also the additional roles of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③">Advisory Committee representatives</a> described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h4 class="heading settled" data-level="3.2.2" id="ac-participation"><span class="secno">3.2.2. </span><span class="content"> Participation in the Advisory Committee</span><a class="self-link" href="#ac-participation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①">Advisory Committee</a> is composed of one <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee representative| AC representative" id="advisory-committee-representative">representative</dfn> from each Member organization
+	(refer to the <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①②">Member-only</a> list
+	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. <a data-link-type="biblio" href="#biblio-current-ac" title="Current Advisory Committee representatives (Member-only access)">[CURRENT-AC]</a>)</p>
+    <p>When an organization joins W3C
+	(see “<a href="https://www.w3.org/membership/join/">How to Join W3C</a>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>),
+	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of their Membership Agreement.
+	The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a> 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 <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative④">Advisory Committee representative</a>,
+	and more. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑤">Advisory Committee representatives</a> <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.</p>
+    <p>The AC representative may delegate any of their rights and responsibilities
+	to an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="alternate AC representative | alternate Advisory Committee representative | alt AC rep" id="alternate-ac-representative">alternate</dfn> (except the ability to designate an alternate).</p>
+    <h4 class="heading settled" data-level="3.2.3" id="ACCommunication"><span class="secno">3.2.3. </span><span class="content"> Advisory Committee Mailing Lists</span><a class="self-link" href="#ACCommunication"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②">Team</a> <em class="rfc2119">must</em> provide two mailing lists for use by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②">Advisory Committee</a>:</p>
+    <ol>
+     <li> One for official announcements (e.g., those required by this document) from the <a data-link-type="dfn" href="#team" id="ref-for-team①③">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③">Advisory Committee</a>.
+			This list is read-only for Advisory Committee representatives. 
+     <li> One for discussion among <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑥">Advisory Committee representatives</a>.
+			Though this list is primarily for Advisory Committee representatives,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①④">Team</a> <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>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑦">Advisory Committee representative</a> <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.</p>
+    <h4 class="heading settled" data-level="3.2.4" id="ACMeetings"><span class="secno">3.2.4. </span><span class="content"> Advisory Committee Meetings</span><a class="self-link" href="#ACMeetings"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑤">Team</a> organizes a <a href="#ftf-meeting" id="ref-for-ftf-meeting">face-to-face meeting</a> for the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④">Advisory Committee</a> <span class="time-interval">twice a year</span>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⑥">Team</a> 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:</p>
+    <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>
+    </dl>
+    <p>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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑦">Team</a> <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.</p>
+    <p>More information about <a href="https://www.w3.org/events/ac/">Advisory Committee meetings</a> <a data-link-type="biblio" href="#biblio-ac-meeting" title="Advisory Committee meetings (Member-only access)">[AC-MEETING]</a> is available at the Member website.</p>
+    <h3 class="heading settled" data-level="3.3" id="elected-groups"><span class="secno">3.3. </span><span class="content"> Elected Groups: The AB and the TAG</span><a class="self-link" href="#elected-groups"></a></h3>
+    <p>The W3C Process defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="elected-group">elected groups</dfn>:
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①">Advisory Board</a> (AB) and
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①">Technical Architecture Group</a> (TAG),
+	both elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑤">Advisory Committee</a>.</p>
+    <h4 class="heading settled" data-level="3.3.1" id="AB"><span class="secno">3.3.1. </span><span class="content"> Advisory Board (AB)</span><a class="self-link" href="#AB"></a></h4>
+    <h5 class="heading settled" data-level="3.3.1.1" id="ab-role"><span class="secno">3.3.1.1. </span><span class="content"> Role of the Advisory Board</span><a class="self-link" href="#ab-role"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Board|AB" id="advisory-board">Advisory Board</dfn> 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>.
+	As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council">W3C Council</a>,
+	members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②">Advisory Board</a> hear and adjudicate on <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③">Advisory Board</a> is distinct from the <a data-link-type="dfn" href="#bod" id="ref-for-bod①">Board of Directors</a> and has no decision-making authority within W3C;
+	its role is strictly advisory.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> While the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board④">AB</a> as such does not have decision-making authority,
+	its members do when sitting as part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①">W3C Council</a>.</p>
+    <p>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> <a data-link-type="biblio" href="#biblio-ab-hp" title="The Advisory Board home page">[AB-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.1.2" id="ABParticipation"><span class="secno">3.3.1.2. </span><span class="content"> Composition of the Advisory Board</span><a class="self-link" href="#ABParticipation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑤">Advisory Board</a> 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 <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑥">AB</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⑧">Team</a> 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.</p>
+    <p>The team also appoints a <a href="https://www.w3.org/guide/teamcontact/role">Team Contact</a>,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.
+	The CEO and Team Contact have a standing invitation
+	to all regular Advisory Board sessions.</p>
+    <p>The nine to eleven <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑦">Advisory Board</a> participants are elected by the W3C <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑥">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="3.3.1.3" id="ab-comm"><span class="secno">3.3.1.3. </span><span class="content"> Communications of the Advisory Board</span><a class="self-link" href="#ab-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑨">Team</a> <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.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑧">Advisory Board</a> <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>.</p>
+    <h5 class="heading settled" data-level="3.3.1.4" id="ab-bod-liaison"><span class="secno">3.3.1.4. </span><span class="content"> Liaisons between the Advisory Board and the Board of Directors</span><a class="self-link" href="#ab-bod-liaison"></a></h5>
+    <p>To ensure good communication between the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑨">AB</a> and the <a data-link-type="dfn" href="#bod" id="ref-for-bod②">Board of Directors</a> and facilitate operational and management consistency,
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⓪">AB</a> <em class="rfc2119">may</em> appoint up to two of its participants as liaisons to the <a data-link-type="dfn" href="#bod" id="ref-for-bod③">Board</a>.
+	Such appointees are expected to attend and participate in <a data-link-type="dfn" href="#bod" id="ref-for-bod④">Board</a> meetings
+	and access <a data-link-type="dfn" href="#bod" id="ref-for-bod⑤">Board</a> materials
+	as Non-voting Observers. <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a> They do not form part of the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑥">Board</a>’s decision-making body,
+	and may be excluded from such participation
+	in accordance with applicable Board procedures.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①①">Advisory Board</a> <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.</p>
+    <h4 class="heading settled" data-level="3.3.2" id="TAG"><span class="secno">3.3.2. </span><span class="content"> Technical Architecture Group (TAG)</span><a class="self-link" href="#TAG"></a></h4>
+    <h5 class="heading settled" data-level="3.3.2.1" id="tag-role"><span class="secno">3.3.2.1. </span><span class="content"> Role of the Technical Architecture Group</span><a class="self-link" href="#tag-role"></a></h5>
+    <p>The mission of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Technical Architecture Group|TAG" id="technical-architecture-group">TAG</dfn> is stewardship of the Web architecture.
+	There are three aspects to this mission:</p>
+    <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> to help coordinate cross-technology architecture developments inside and outside W3C. 
+    </ol>
+    <p>As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②">W3C Council</a>,
+	the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②">TAG</a> hear and adjudicate on <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals①">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③">TAG</a>’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.</p>
+    <p>When the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④">TAG</a> votes to resolve an issue,
+	each TAG participant
+	(whether appointed, elected, or the Chair)
+	has one vote;
+	see also the general section on <a href="#Votes">votes</a> in this Process Document.</p>
+    <p>Details about the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑤">TAG</a> (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings)
+	are available at the <a href="https://www.w3.org/2001/tag/">TAG home page</a> <a data-link-type="biblio" href="#biblio-tag-hp" title="The TAG home page">[TAG-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.2.2" id="tag-participation"><span class="secno">3.3.2.2. </span><span class="content"> Composition of the Technical Architecture Group</span><a class="self-link" href="#tag-participation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑥">TAG</a> consists of:</p>
+    <ul>
+     <li> Tim Berners-Lee, who is a life member; 
+     <li> Three participants <a href="#TAG-appointments">appointed by the Team</a>; 
+     <li> Eight participants elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑦">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>. 
+    </ul>
+    <p>Participants in the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑦">TAG</a> choose by consensus their Chair or co-Chairs;
+	in the absence of consensus, the <a data-link-type="dfn" href="#team" id="ref-for-team②⓪">Team</a> appoints the Chair or co-Chairs of the TAG.
+	The Chair or co-Chairs <em class="rfc2119">must</em> be selected from the participants of the TAG.
+	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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②①">Team</a> also appoints a <a href="https://www.w3.org/guide/teamcontact/role">Team Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> for the TAG,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.</p>
+    <p>The terms of TAG participants last for <span class="time-interval">two years</span>.
+	Terms are staggered so that four elected terms
+	and either one or two appointed terms expire each year.
+	If an individual is appointed or elected to fill an incomplete term,
+	that individual’s term ends at the normal expiration date of that term.
+	Regular TAG terms begin on 1 February and end on 31 January.</p>
+    <h5 class="heading settled" data-level="3.3.2.3" id="tag-comm"><span class="secno">3.3.2.3. </span><span class="content"> Communications of the Technical Architecture Group</span><a class="self-link" href="#tag-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②②">Team</a> <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
+    <ul>
+     <li> a public discussion (not just input) list for issues of Web architecture.
+			The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑧">TAG</a> will conduct its public business on this list. 
+     <li> a <a href="#Member-only" id="ref-for-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. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑨">TAG</a> <em class="rfc2119">may</em> also request the creation of additional topic-specific, public mailing lists.
+	For some TAG discussions (e.g.,  a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals②">Submission Appeal</a>),
+	the TAG <em class="rfc2119">may</em> use a list that will be <a href="#Member-only" id="ref-for-Member-only①④">Member-only</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⓪">TAG</a> <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 <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①①">TAG</a> <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
+    <h4 class="heading settled" data-level="3.3.3" id="AB-TAG-participation"><span class="secno">3.3.3. </span><span class="content"> Participation in Elected Groups</span><a class="self-link" href="#AB-TAG-participation"></a></h4>
+    <h5 class="heading settled" data-level="3.3.3.1" id="elected-expectations"><span class="secno">3.3.3.1. </span><span class="content"> Expectations for Elected Groups Participants</span><a class="self-link" href="#elected-expectations"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①②">Advisory Board</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①②">TAG</a> participants have a special role within W3C:
+	they are elected by the Membership and appointed by the <a data-link-type="dfn" href="#team" id="ref-for-team②③">Team</a> with the expectation that they will use their best judgment
+	to find the best solutions for the Web,
+	not just for any particular network,
+	technology,
+	vendor,
+	or user.
+	Advisory Board and TAG participants are expected to participate regularly and fully.
+	Advisory Board and TAG participants <em class="rfc2119">should</em> attend <a href="#ACMeetings">Advisory Committee meetings</a>.</p>
+    <p>Individuals elected or appointed to the Advisory Board or TAG act in their personal capacity,
+	to serve the needs of the W3C membership as a whole,
+	and the Web community.
+	Whether they are Member representatives or Invited Experts,
+	their activities in those roles are separate and distinct from their activities on the Advisory Board or TAG.</p>
+    <p>An individual participates on the Advisory Board or TAG
+	from the moment the individual’s term begins until the seat is <a href="#AB-TAG-vacated">vacated</a> (e.g. because the term ends).
+	Although Advisory Board and TAG participants do not advocate for the commercial interests of their employers,
+	their participation does carry the responsibilities associated with Member representation,
+	Invited Expert status,
+	or Team representation
+	(as described in the section on the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>).</p>
+    <p>Participation in the TAG or AB is afforded to the specific individuals elected or appointed to those positions,
+	and a participant’s seat <em class="rfc2119">must not</em> be delegated to any other person.</p>
+    <h5 class="heading settled" data-level="3.3.3.2" id="AB-TAG-constraints"><span class="secno">3.3.3.2. </span><span class="content"> Elected Groups Participation Constraints</span><a class="self-link" href="#AB-TAG-constraints"></a></h5>
+    <p>Given the few seats available on the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①③">Advisory Board</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①③">TAG</a>,
+	and in order to ensure that the diversity of W3C Members is represented:</p>
+    <ul>
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the TAG
+			except when this is caused by a change of affiliation of an existing participant.
+			At the completion of the next regularly scheduled election for the TAG,
+			the organization <em class="rfc2119">must</em> have returned to having at most one seat. 
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation①">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the AB.
+			If, for whatever reason, these constraints are not satisfied
+			(e.g., because an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①④">AB</a> participant changes jobs),
+			one participant <em class="rfc2119">must</em> cease <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑤">AB</a> participation
+			until the situation has been resolved.
+			If after <span class="time-interval">30 days</span> the situation has not been resolved,
+			the Chair will apply
+			the <a href="#random">verifiable random selection procedure</a> described below
+			to choose one person for continued participation and declare the other seat(s) vacant. 
+     <li> An individual <em class="rfc2119">must not</em> participate on both the TAG and the AB. 
+    </ul>
+    <h5 class="heading settled" data-level="3.3.3.3" id="AB-TAG-elections"><span class="secno">3.3.3.3. </span><span class="content"> Advisory Board and Technical Architecture Group Elections</span><a class="self-link" href="#AB-TAG-elections"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑥">Advisory Board</a> and a portion of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①④">Technical Architecture Group</a> are elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑧">Advisory Committee</a>,
+	using a Single Transferable Vote system.
+	An election begins when the Team sends a Call for Nominations to the Advisory Committee.
+	Any Call for Nominations specifies the minimum and maximum number of available seats,
+	the deadline for nominations,
+	details about the specific vote tabulation system selected by the Team for the election,
+	and operational information such as how to nominate a candidate.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②④">Team</a> <em class="rfc2119">may</em> modify the tabulation system after the Call for Nominations
+	but <em class="rfc2119">must</em> stabilize it no later than the Call for Votes.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②⑤">Team</a> announces appointments
+	after the results of the election are known,
+	and before the start of the term,
+	as described in <a href="#TAG-appointments">§ 3.3.3.4 Technical Architecture Group Appointments</a>.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑤">TAG</a>,
+	the minimum and maximum number of available seats are the same:
+	the 4 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑦">AB</a>,
+	the minimum and maximum number of available seats differ:
+	The maximum number is the 5 or 6 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats;
+	the minimum number is such that when added to the occupied seats from the prior year,
+	the minimum size of the AB (9) is reached.</p>
+    <p>Each Member (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member②">related Members</a>) <em class="rfc2119">may</em> nominate one individual.
+	A nomination <em class="rfc2119">must</em> be made with the consent of the nominee.
+	In order for an individual to be nominated as a Member representative,
+	the individual <em class="rfc2119">must</em> qualify for <a href="#member-rep">Member representation</a> and the Member’s <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑧">Advisory Committee representative</a> <em class="rfc2119">must</em> include in the nomination
+	the (same) <a href="#member-rep-info">information required for a Member representative in a Working Group</a>.
+	In order for an individual to be nominated as an Invited Expert,
+	the individual <em class="rfc2119">must</em> provide
+	the (same) <a href="#inv-expert-info" id="ref-for-inv-expert-info">information required for an Invited Expert in a Working Group</a> and the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑨">Advisory Committee representative</a> <em class="rfc2119">must</em> include that information in the nomination.
+	In order for an individual to be nominated as a <a data-link-type="dfn" href="#team" id="ref-for-team②⑥">Team</a> representative,
+	the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⓪">Advisory Committee representative</a> <em class="rfc2119">must</em> first secure approval from <a data-link-type="dfn" href="#team" id="ref-for-team②⑦">Team</a> management.
+	A nominee is <em class="rfc2119">not required</em> to be an employee of a Member organization,
+	and <em class="rfc2119">may</em> be a <a href="#fellows" id="ref-for-fellows①">W3C Fellow</a>.
+	The nomination form <em class="rfc2119">must</em> ask for the nominee’s <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation②">primary affiliation</a>,
+	and this will be reported on the ballot.
+	For most nominees,
+	the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="primary-affiliation">primary affiliation</dfn> is their employer and will match their affiliation in the W3C database.
+	For contractors and invited experts,
+	this will normally be their contracting company
+	or their invited expert status;
+	in some cases
+	(e.g. where a consultant is consulting for only one organization)
+	this <em class="rfc2119">may</em> be the organization for whom the nominee is consulting.
+	A <a href="#AB-TAG-constraints">change of affiliation</a> is defined
+	such that this field would carry a different answer
+	if the nominee were to be re-nominated
+	(therefore,
+	terminating employment,
+	or accepting new employment,
+	are changes of affiliation).
+	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
+	Each nomination <em class="rfc2119">should</em> include
+	a few informative paragraphs about the nominee.
+	If an identified candidate’s nomination information is only partially complete
+	as of the deadline for nominations,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team②⑧">Team</a> <em class="rfc2119">may</em> allow extra time for that candidate’s nomination to be completed,
+	so long as it does not delay the election as a whole.</p>
+    <p>If, after the deadline for nominations, the number of nominees is:</p>
+    <ul>
+     <li> Greater than or equal to the minimum number of available seats
+			and less than or equal to the maximum number of available seats,
+			those nominees are thereby elected.
+			This situation constitutes a tie for the purpose of assigning <a href="#short-term">incomplete terms</a>.
+			Furthermore, if the number is less than the maximum number of available seats,
+			the longest terms are filled first. 
+     <li> Less than the minimum number of available seats,
+			Calls for Nominations are issued until a sufficient number of people have been nominated.
+			Those already nominated do not need to be renominated after a renewed call. 
+     <li> Greater than the maximum number of available seats,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team②⑨">Team</a> issues a Call for Votes
+			that includes the names of all candidates,
+			the (maximum) number of available seats,
+			the deadline for votes,
+			details about the vote tabulation system selected by the Team for the election,
+			and operational information. 
+    </ul>
+    <p>When there is a vote,
+	each Member in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing">Good Standing</a> (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member③">related Members</a>) <em class="rfc2119">may</em> submit one ballot that ranks candidates in the Member’s preferred order.
+	Once the deadline for votes has passed,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⓪">Team</a> announces the results to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑨">Advisory Committee</a>.
+	In case of a tie the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to fill the available seats.</p>
+    <p id="short-term">The shortest incomplete term is assigned to the elected candidate ranked lowest by the tabulation of votes,
+	the next shortest term to the next-lowest ranked elected candidate,
+	and so on.
+	In the case of a tie among those eligible for a incomplete term,
+	the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to assign the incomplete term. </p>
+    <p>Refer to <a href="https://www.w3.org/guide/process/election">How to Organize an Advisory Board or TAG election</a> <a data-link-type="biblio" href="#biblio-election-howto" title="How to Organize an Advisory Board or TAG election">[ELECTION-HOWTO]</a> for more details.</p>
+    <h5 class="heading settled" data-level="3.3.3.4" id="TAG-appointments"><span class="secno">3.3.3.4. </span><span class="content"> Technical Architecture Group Appointments</span><a class="self-link" href="#TAG-appointments"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③①">Team</a> is responsible for appointing
+	3 of the participants to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑥">Technical Architecture Group</a>.
+	This mechanism complements the election process.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③②">Team</a> <em class="rfc2119">should</em> use its appointments to support
+	a diverse and well-balanced <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑦">TAG</a>,
+	including diversity of technical background, knowledge, and skill sets.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③③">Team</a> <em class="rfc2119">should</em> actively seek
+	candidates for appointment to the TAG,
+	and <em class="rfc2119">must</em> make available to
+	the W3C community at large
+	a means to propose candidates for consideration,
+	explicitly soliciting input from at least
+	current and incoming <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑧">TAG</a> members, the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⓪">Advisory Committee</a>, and <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②">Chairs</a>.</p>
+    <p>The constraints for appointment to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑨">TAG</a> are
+	the same as for elected participants
+	(see <a href="#AB-TAG-constraints">§ 3.3.3.2 Elected Groups Participation Constraints</a> and <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a>),
+	with the additional constraint that
+	a person <em class="rfc2119">must not</em> be appointed
+	for more than two <em>consecutive</em> terms.
+	(Partial terms used to fill a vacated seat do not count towards this limit.)</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since there are no limits on elected terms,
+	this limit on appointed terms does not constrain
+	term-limited appointees
+	from running for election at any time.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③④">Team</a>’s choice of appointee(s)
+	is subject to ratification by secret ballot
+	by both the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑧">AB</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⓪">TAG</a>,
+	requiring a two-thirds approval from each.
+	In the case of regularly scheduled elections,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②①">TAG</a> participants in this ratification are
+	its members for the upcoming term.</p>
+    <p>For regularly scheduled elections,
+	selection begins once the results of the elections are known,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team③⑤">Team</a> <em class="rfc2119">should</em> announce the ratified appointment(s)
+	no later than the start of the regularly scheduled term.
+	When an appointed seat is vacated outside of a regularly scheduled election,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⑥">Team</a> <em class="rfc2119">should</em> seek to appoint a replacement
+	unless a regular Call for Nominations is scheduled within 2 months,
+	and it <em class="rfc2119">must</em> announce the ratified appointment
+	no later than the Call for Nominations of the next scheduled election.</p>
+    <h5 class="heading settled" data-level="3.3.3.5" id="random"><span class="secno">3.3.3.5. </span><span class="content"> Verifiable Random Selection Procedure</span><a class="self-link" href="#random"></a></h5>
+    <p>When it is necessary to use a verifiable random selection process
+	(e.g., in an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑨">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②②">TAG</a> election,
+	to “draw straws” in case of a tie
+	or to fill a incomplete term),
+	W3C uses the random and verifiable procedure defined in <a href="https://www.ietf.org/rfc/rfc3797.txt">RFC 3797</a> <a data-link-type="biblio" href="#biblio-rfc3797" title="Publicly Verifiable Nominations Committee (NomCom) Random Selection">[RFC3797]</a>.
+	The procedure orders an input list of names
+	(listed in alphabetical order by family name unless otherwise specified)
+	into a “result order”.</p>
+    <p>W3C applies this procedure as follows:</p>
+    <ol>
+     <li> When N people have tied for M (less than N) seats.
+			In this case, only the names of the N individuals who tied
+			are provided as input to the procedure.
+			The M seats are assigned in result order. 
+     <li> After all elected individuals have been identified,
+			when N people are eligible for M (less than N) incomplete terms.
+			In this case, only the names of those N individuals are provided as input to the procedure.
+			The incomplete terms are assigned in result order. 
+    </ol>
+    <h5 class="heading settled" data-level="3.3.3.6" id="AB-TAG-vacated"><span class="secno">3.3.3.6. </span><span class="content"> Elected Groups Vacated Seats</span><a class="self-link" href="#AB-TAG-vacated"></a></h5>
+    <p>An <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⓪">Advisory Board</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②③">TAG</a> participant’s seat is vacated when:</p>
+    <ul>
+     <li> the participant resigns, or 
+     <li> an Advisory Board or TAG participant changes affiliations
+			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
+			or 
+     <li> the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo④">CEO</a> dismisses the participant
+			for failing to meet the criteria in section <a href="#ParticipationCriteria">§ 3.1.1 Individual Participation Criteria</a>,
+			or 
+     <li> their term ends. 
+    </ul>
+    <p>If a participant changes affiliation,
+	but the <a href="#AB-TAG-constraints">participation constraints</a> are met,
+	that participant’s seat becomes vacant at the next regularly scheduled election for that group.</p>
+    <p>Vacated seats are filled according to this schedule:</p>
+    <ul>
+     <li> When an appointed <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②④">TAG</a> seat is vacated,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team③⑦">Team</a> <a href="#TAG-appointments">appoints</a> a replacement. 
+     <li>
+       When an elected seat on either the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②①">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑤">TAG</a> is vacated,
+			the seat is filled at the next regularly scheduled election for the group
+			unless the group Chair requests that W3C hold an election before then
+			(for instance, due to the group’s workload). 
+      <ul>
+       <li> The group Chair <em class="rfc2119">should not</em> request such an election
+					if the next regularly scheduled election is fewer than three months away. 
+       <li> The group Chair <em class="rfc2119">may</em> request an election,
+					and the election may begin, as soon as a current member gives notice of a resignation,
+					including a resignation effective as of a given date in the future. 
+      </ul>
+      <p>When such an election is held,
+			the minimum number of available seats is such that
+			when added to the number of continuing participants,
+			the minimum total number of elected seats is met
+			(8 for the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑥">TAG</a>, 9 for the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②②">AB</a>);
+			and the maximum number corresponds to all unoccupied seats.
+			Except for the number of available seats and the length of the terms,
+			the <a href="#AB-TAG-elections">usual rules for Advisory Board and Technical Architecture Group Elections</a> apply.</p>
+    </ul>
+    <h3 class="heading settled" data-level="3.4" id="GAGeneral"><span class="secno">3.4. </span><span class="bs-old-id" id="WG-and-IG"></span><span class="bs-old-id" id="ChapterGroups"></span><span class="content"> Chartered Groups: Working Groups and Interest Groups</span><a class="self-link" href="#GAGeneral"></a></h3>
+    <p id="GAGroups">This document defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chartered-group">chartered groups</dfn>: </p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsWG"><a href="#GroupsWG" id="ref-for-GroupsWG⑦⑥">Working Groups</a></dfn>. 
+     <dd>
+       Working Groups typically produce deliverables
+			(e.g., <a href="#rec-advance">Recommendation Track technical reports</a>,
+			software,
+			test suites,
+			and reviews of the deliverables of other groups)
+			as defined in their <a href="#WGCharter">charter</a>. 
+      <p>Working Groups have additional participation requirements
+			described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			see particularly the “<a href="https://www.w3.org/policies/patent-policy/#sec-Obligations">Licensing Obligations of Working Group Participants</a>”
+			and the patent claim exclusion process
+			in “<a href="https://www.w3.org/policies/patent-policy/#sec-Exclusion">Exclusion From W3C RF Licensing Requirements</a>”.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsIG"><a href="#GroupsIG" id="ref-for-GroupsIG①③">Interest Groups</a></dfn>. 
+     <dd>
+       The primary goal of an Interest Group
+			is to bring together people who wish to evaluate potential Web technologies and policies.
+			An Interest Group is a forum for the exchange of ideas. 
+      <p>Interest Groups do not publish <a href="#RecsW3C" id="ref-for-RecsW3C⑦④">Recommendation Track technical reports</a>;
+			but can publish <a href="#WGNote" id="ref-for-WGNote">technical reports on the Note Track</a>.</p>
+    </dl>
+    <h4 class="heading settled" data-level="3.4.1" id="ReqsAllGroups"><span class="secno">3.4.1. </span><span class="content"> Requirements for All Chartered Groups</span><a class="self-link" href="#ReqsAllGroups"></a></h4>
+    <p>Each group <em class="rfc2119">must</em> have a <a data-link-type="dfn" href="#charter" id="ref-for-charter">charter</a>.
+	Requirements for the charter depend on the group type.
+	All group charters <em class="rfc2119">must</em> be public
+	(even if other proceedings of the group are <a href="#Member-only" id="ref-for-Member-only①⑤">Member-only</a>).</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GeneralChairs">Chair</dfn> (or co-Chairs)
+	to facilitate effective discussion and coordinate the group’s activities.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③⑧">Team</a> appoints (and re-appoints) Chairs for all groups.
+	The Chair is a <a href="#member-rep">Member representative</a>,
+	a <a href="#Team">Team representative</a>,
+	or an <a href="#invited-expert-wg">Invited Expert</a> (invited by the <a data-link-type="dfn" href="#team" id="ref-for-team③⑨">Team</a>).
+	The requirements of this document that apply to those types of participants apply to Chairs as well.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/guide/chair/role">role of the Chair</a> <a data-link-type="biblio" href="#biblio-chair" title="W3C Working/Interest Group Chair">[CHAIR]</a> is described
+	in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="TeamContact">Team Contact</dfn>,
+	who acts as the interface between the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③">Chair</a>,
+	group participants,
+	and the rest of the Team.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/guide/teamcontact/role">role of the Team Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> is described in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs④">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact">Team Contact</a> of a group <em class="rfc2119">should not</em> be the same individual.</p>
+    <p>Each group <em class="rfc2119">must</em> have an archived mailing list
+	for formal group communication
+	(e.g., for meeting announcements and <a data-link-type="dfn" href="#minutes" id="ref-for-minutes①">minutes</a>,
+	documentation of decisions,
+	and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②">Formal Objections</a> to decisions).
+	It is the responsibility of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑤">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①">Team Contact</a> to ensure that new participants are subscribed to all relevant mailing lists.
+	Refer to the list of <a href="https://www.w3.org/groups/">group mailing lists</a> <a data-link-type="biblio" href="#biblio-group-mail" title="Group mailing lists">[GROUP-MAIL]</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑥">Chair</a> <em class="rfc2119">may</em> form task forces
+	(composed of group participants)
+	to carry out assignments for the group.
+	The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group’s charter.
+	A group <em class="rfc2119">should</em> document the process it uses
+	to create task forces
+	(e.g., each task force might have an informal "charter").
+	Task forces do not publish <a href="#Reports">technical reports</a>;
+	the Working Group <em class="rfc2119">may</em> choose to publish their results as part of a technical report. </p>
+    <h4 class="heading settled" data-level="3.4.2" id="group-participation"><span class="secno">3.4.2. </span><span class="content"> Participation in Chartered Groups</span><a class="self-link" href="#group-participation"></a></h4>
+    <p>There are three types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="wgparticipant">participants in a Working Group</dfn>: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
+	and <a href="#Team">Team representatives</a> (including the <a href="#TeamContact" id="ref-for-TeamContact⑧">Team Contact</a>).</p>
+    <p>There are four types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="igparticipant">participants in an Interest Group</dfn>:
+	the same three types as for Working Groups plus,
+	for an Interest Group where the only <a href="#ig-mail-only">participation requirement is mailing list subscription</a>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="public-participant-ig">public participants</dfn>.</p>
+    <p>Except where noted in this document or in a group charter,
+	all participants share the same rights and responsibilities in a group;
+	see also the <a href="#ParticipationCriteria">individual participation criteria</a>.</p>
+    <p>A participant <em class="rfc2119">may</em> represent more than one organization
+	in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①">Interest Group</a>.
+	Those organizations <em class="rfc2119">must</em> all be members of the group.</p>
+    <p>An individual <em class="rfc2119">may</em> become
+	a Working or Interest Group participant
+	at any time during the group’s existence.
+	See also relevant requirements in
+	“Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>On an exceptional basis,
+	a Working or Interest Group participant <em class="rfc2119">may</em> designate
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mtg-substitute">substitute</dfn> to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑦">Chair</a>.
+	The substitute <em class="rfc2119">may</em> act on behalf of the participant,
+	including for <a href="#Votes">votes</a>.
+	For the substitute to vote,
+	the participant <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑧">Chair</a> in writing in advance.</p>
+    <p>To allow rapid progress,
+	Working Groups are intended to be small
+	(typically fewer than 15 people)
+	and composed of experts in the area defined by the charter.
+	In principle,
+	Interest Groups have no limit on the number of participants.
+	When a Working Group grows too large to be effective,
+	W3C <em class="rfc2119">may</em> split it into an Interest Group
+	(a discussion forum)
+	and a much smaller Working Group
+	(a core group of highly dedicated participants).</p>
+    <h4 class="heading settled" data-level="3.4.3" id="chartered-group-participants"><span class="secno">3.4.3. </span><span class="content"> Types of Participants in Chartered Groups</span><a class="self-link" href="#chartered-group-participants"></a></h4>
+    <h5 class="heading settled" data-level="3.4.3.1" id="member-rep-wg"><span class="secno">3.4.3.1. </span><span class="content"> Member Representative in a Working Group</span><a class="self-link" href="#member-rep-wg"></a></h5>
+    <p>An individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-a-working-group">Member representative in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Advisory Committee representative of the Member in question
+			has designated the individual as a Working Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a Member representative in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤">Working Group</a>,
+	an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①①">Advisory Committee representative</a> <em class="rfc2119">must</em> provide the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑨">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact②">Team Contact</a> with all of the following <span id="member-rep-info">information</span>,
+	in addition to any other information required by the <a href="#cfp">Call for Participation</a> and charter
+	(including the participation requirements of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>):</p>
+    <ol>
+     <li> The name of the W3C Member the individual represents
+			and whether the individual is an employee of that Member organization; 
+     <li> A statement that the individual accepts the participation terms
+			set forth in the charter
+			(with an indication of charter date or version); 
+     <li> A statement that the Member will provide the necessary financial support for participation
+			(e.g., for travel, telephone calls, and conferences). 
+    </ol>
+    <p>A Member participates in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥">Working Group</a> from the moment the first Member representative joins the group
+	until either of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Member <a href="#resignation">resigns</a> from the Working Group;
+			this is done through the Member’s Advisory Committee representative. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.2" id="member-rep-ig"><span class="secno">3.4.3.2. </span><span class="content"> Member Representative in an Interest Group</span><a class="self-link" href="#member-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-an-interest-group">Member representative in an Interest Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①②">Advisory Committee representative</a> of the Member in question has designated the individual
+			as an Interest Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a <a data-link-type="dfn" href="#member-representative-in-an-interest-group" id="ref-for-member-representative-in-an-interest-group">Member representative in an Interest Group</a>,
+	the Advisory Committee representative <em class="rfc2119">must</em> follow the instructions
+	in the <a href="#cfp">Call for Participation</a> and charter.</p>
+    <p>Member participation in an Interest Group ceases under the same conditions as for a Working Group.</p>
+    <h5 class="heading settled" data-level="3.4.3.3" id="invited-expert-wg"><span class="secno">3.4.3.3. </span><span class="content"> Invited Expert in a Working Group</span><a class="self-link" href="#invited-expert-wg"></a></h5>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⓪">Chair</a> <em class="rfc2119">may</em> invite an individual with a particular expertise
+	to participate in a Working Group.
+	This individual <em class="rfc2119">may</em> represent an organization in the group
+	(e.g., if acting as a liaison with another organization).</p>
+    <p>An individual is an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-a-working-group">Invited Expert in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Chair has designated the individual as a group participant, 
+     <li> the Team Contact has agreed with the Chair’s choice, and 
+     <li> the individual has provided the <a href="#inv-expert-info" id="ref-for-inv-expert-info①">information required of an Invited Expert</a> to the Chair and Team Contact. 
+    </ul>
+    <p>To designate an individual as an Invited Expert in a Working Group,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①①">Chair</a> <em class="rfc2119">must</em> inform the Team Contact
+	and provide rationale for the choice.
+	When the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①②">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact③">Team Contact</a> disagree about a designation,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑤">CEO</a> determines
+	whether the individual will be invited to participate in the Working Group.</p>
+    <p>To <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="inv-expert-info">participate in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦">Working Group</a> as an Invited Expert</dfn>,
+	an individual <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> identify the organization, if any, the individual represents as a participant in this group, 
+     <li> agree to the terms of the <a href="https://www.w3.org/invited-experts/agreement-2023/">invited expert and collaborators agreement</a> <a data-link-type="biblio" href="#biblio-collaborators-agreement" title="Invited expert and collaborators agreement">[COLLABORATORS-AGREEMENT]</a>, 
+     <li> accept the participation terms set forth in the charter,
+			including the participation requirements of
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			especially in “Note on Licensing Commitments for Invited Experts”
+			and in “Disclosure”,
+			indicating a specific charter date or version, 
+     <li> disclose whether the individual is an employee of a W3C Member;
+			see the <a href="#coi">conflict of interest policy</a>, 
+     <li> provide a statement of who will provide the necessary financial support
+			for the individual’s participation
+			(e.g., for travel, telephone calls, and conferences), and 
+     <li> if the individual’s employer (including a self-employed individual)
+			or the organization the individual represents
+			is not a W3C Member,
+			indicate whether that organization intends to join W3C.
+			If the organization does not intend to join W3C,
+			indicate reasons the individual is aware of for this choice. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①③">Chair</a> <em class="rfc2119">should not</em> designate as an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group">Invited Expert in a Working Group</a> an individual who is an employee of a W3C Member.
+	The Chair <em class="rfc2119">must not</em> use Invited Expert status
+	to circumvent participation limits imposed by the <a href="#WGCharter">charter</a>.</p>
+    <p>An Invited Expert participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Chair or <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑥">CEO</a> withdraws the invitation to participate, or 
+     <li> the individual <a href="#resignation">resigns</a>. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.4" id="invited-expert-ig"><span class="secno">3.4.3.4. </span><span class="content"> Invited Expert in an Interest Group</span><a class="self-link" href="#invited-expert-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	the participation requirements for an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-an-interest-group">Invited Expert in an Interest Group</dfn> are the same as those for an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group①">Invited Expert in a Working Group</a>.</p>
+    <h5 class="heading settled" data-level="3.4.3.5" id="team-rep-wg"><span class="secno">3.4.3.5. </span><span class="content"> Team Representative in a Working Group</span><a class="self-link" href="#team-rep-wg"></a></h5>
+    <p>An individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-representative-in-a-working-group">Team representative in a Working Group</dfn> when so designated by W3C management.
+	Team representatives both contribute to the technical work
+	and help ensure the group’s proper integration with the rest of W3C.</p>
+    <p>A Team representative participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> W3C management changes Team representation by sending email to the Chair,
+			copying the group mailing list. 
+    </ul>
+    <p>The Team participates in a Working Group
+	from the moment the creation of the group is announced
+	until the group closes.</p>
+    <h5 class="heading settled" data-level="3.4.3.6" id="team-rep-ig"><span class="secno">3.4.3.6. </span><span class="content"> Team Representative in an Interest Group</span><a class="self-link" href="#team-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-representative-in-an-interest-group">Team representative in an Interest Group</dfn> when so designated by W3C management.</p>
+    <h2 class="heading settled" data-level="4" id="group-lifecycle"><span class="secno">4. </span><span class="content"> Lifecycle of Chartered Groups</span><a class="self-link" href="#group-lifecycle"></a></h2>
+    <p>W3C creates <a data-link-type="dfn" href="#charter" id="ref-for-charter①">charters</a> for <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group">chartered groups</a> based on W3C community interest.
+	W3C fosters awareness of <a data-link-type="dfn" href="#charter" id="ref-for-charter②">charters</a>,
+	improves their quality,
+	and gauges Membership support in two formal phases:</p>
+    <ul>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement">refinement</a> phase helps ensure <a data-link-type="dfn" href="#charter" id="ref-for-charter③">charters</a> are mission-aligned,
+reflect community input and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus">consensus</a>,
+and have been well-socialized
+and <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review">widely reviewed</a>.</p>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#charter" id="ref-for-charter④">Charters</a> then are formally approved through an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review">AC Review</a> and <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①">W3C Decision</a> (see <a href="#CharterReview">§ 4.4 Charter Review and Approval</a>).</p>
+    </ul>
+    <h3 class="heading settled" data-level="4.1" id="charter-initiation"><span class="secno">4.1. </span><span class="content"> Initiating Charter Refinement</span><a class="self-link" href="#charter-initiation"></a></h3>
+    <p><a data-link-type="dfn" href="#charter" id="ref-for-charter⑤">Charters</a> can originate in many venues,
+	including existing <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧">Working</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG②">Interest Groups</a>,
+	Community Groups,
+	and from the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member②">Membership</a>.
+	Prior to the formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①">refinement</a> phase,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④⓪">Team</a> engages with those various parties
+	to help prepare <a data-link-type="dfn" href="#charter" id="ref-for-charter⑥">charters</a> for broader audiences.</p>
+    <p>Formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement②">charter refinement</a> (see below) is initiated
+	by the <a data-link-type="dfn" href="#team" id="ref-for-team④①">Team</a> sending a <a data-link-type="dfn" href="#charter-review-notice" id="ref-for-charter-review-notice">charter review notice</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①①">Advisory Committee</a>,
+	to the public,
+	and, in the case of rechartering, to the affected <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group②">Group</a>.</p>
+    <p>This <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-review-notice">charter review notice</dfn> must include:</p>
+    <ul>
+     <li data-md>
+      <p>A short summary of the proposal.</p>
+     <li data-md>
+      <p>The location of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-draft">charter draft</dfn>, which must be public.</p>
+     <li data-md>
+      <p>How to participate in the discussion of this <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft">charter draft</a> and where to file issues.</p>
+     <li data-md>
+      <p>The expected duration of the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement③">charter refinement</a> phase,
+which must not be less than 28 days,
+and should not be more than 6 months.</p>
+     <li data-md>
+      <p>Who the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator">Chartering Facilitator</a> is.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④②">Team</a> is responsible for initiating <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement④">charter refinement</a> at its discretion, in consideration of discussions with the community.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①③">Advisory Committee representative</a> <em class="rfc2119">may</em> formally request
+	that the <a data-link-type="dfn" href="#team" id="ref-for-team④③">Team</a> initiate <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑤">charter refinement</a>.
+	The Team <em class="rfc2119">may</em> deny such a request
+	if it thinks the proposal is insufficiently mature,
+	does not align with W3C’s scope and mission,
+	or otherwise does not meet the charter assessment criteria
+	described in the Guide (see <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/guide/process/charter"><cite>How to Create a Working Group or Interest Group</cite></a>),
+	and <em class="rfc2119">must</em> reply with its rationale.
+	This rejection is a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①">Team Decision</a>,
+	and can be appealed only by 5 or more <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member③">Members</a>,
+	through their <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①④">Advisory Committee representative</a>,
+	formally objecting to the decision within 8 weeks of the decision being announced.
+	In this case the <a data-link-type="dfn" href="#team" id="ref-for-team④④">Team</a> <em class="rfc2119">must</em> start an <a data-link-type="dfn" href="#appeal-vote" id="ref-for-appeal-vote">appeal vote</a> on whether to overturn the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision②">Team Decision</a>.
+	(No action is required to be taken when fewer than 5 members object.)</p>
+    <h3 class="heading settled" data-level="4.2" id="charter-development"><span class="secno">4.2. </span><span class="bs-old-id" id="WGCharterDevelopment"></span><span class="content"> Charter Refinement</span><a class="self-link" href="#charter-development"></a></h3>
+    <p>During <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-refinement">charter refinement</dfn>,
+	the W3C community,
+	under the guidance of the <a data-link-type="dfn" href="#team" id="ref-for-team④⑤">Team</a>,
+	further develops the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft①">charter draft</a> with the goal of achieving <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①">consensus</a> on the proposal.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="chartering-facilitator">Chartering Facilitator</dfn>—​who is chosen (and <em class="rfc2119">may</em> be replaced) by the <a data-link-type="dfn" href="#team" id="ref-for-team④⑥">Team</a>—​is responsible for seeking community <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②">consensus</a> among those participating in the refinement process
+	and making decisions reflecting that <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus③">consensus</a>.
+	In cases where <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus④">consensus</a> cannot be found,
+	the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator①">Chartering Facilitator</a> <em class="rfc2119">may</em> ask the <a data-link-type="dfn" href="#team" id="ref-for-team④⑦">Team</a> to make a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision③">Team Decision</a>,
+	and <em class="rfc2119">must</em> document the rationale for the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator②">Chartering Facilitator</a> is not necessarily the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①④">Chair</a> of the <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group①">group</a> being chartered.</p>
+    <p>During <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑥">charter refinement</a>:</p>
+    <ul>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①">Wide review</a> of the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft②">charter draft</a> is initiated and completed.</p>
+     <li data-md>
+      <p>All issues filed against the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft③">charter draft</a> must be <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed">formally addressed</a>,
+and their resolutions tracked in a disposition of comments
+highlighting any issues not resolved by consensus.</p>
+    </ul>
+    <p>Before the end of the announced duration
+	for the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑦">charter refinement</a> phase,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④⑧">Team</a> (informed by the work of the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator③">Chartering Facilitator</a>) <em class="rfc2119">must</em> <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision④">decide</a> which of the following to do:</p>
+    <ul>
+     <li data-md>
+      <p>Complete charter refinement by initiating <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①">AC Review</a> of the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft④">charter draft</a>.</p>
+     <li data-md>
+      <p>Abandon the proposal.</p>
+     <li data-md>
+      <p>Extend the charter refinement period.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④⑨">Team</a> <em class="rfc2119">must</em> announce its <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑤">decision</a> with the same visibility as the initial <a data-link-type="dfn" href="#charter-review-notice" id="ref-for-charter-review-notice①">charter review notice</a>,
+	and <em class="rfc2119">must</em> include a rationale
+	if they are not initiating <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②">AC Review</a>.
+	Reaching the end of the announced period (including any announced extension)
+	with no announced decision
+	is considered a de-facto <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑥">Team decision</a> to abandon the proposal.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⓪">Team</a> <em class="rfc2119">may</em> revise such a decision
+	by announcing an alternative decision.</p>
+    <p><a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③">Formal Objections</a> filed during the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑧">charter refinement</a> phase
+	are specially handled:</p>
+    <ul>
+     <li data-md>
+      <p>Objections to decisions pertaining to the content of the charter,
+as well as objections to initiating the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③">AC Review</a>,
+are considered registered at the close of the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review④">Advisory Committee Review</a> of the charter,
+and are registered against that <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision②">W3C Decision</a>.</p>
+      <p class="note" role="note"><span class="marker">Note:</span> This enables all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④">Formal Objections</a> on the same proposed <a data-link-type="dfn" href="#charter" id="ref-for-charter⑦">charter</a> to be handled together.</p>
+     <li data-md>
+      <p>Objections to abandoning the proposal or to extending the refinement period can be appealed only if 5 or more Members,
+through their <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑤">Advisory Committee representative</a>,
+formally object to the decision within 8 weeks of the decision.
+In this case,
+the <a data-link-type="dfn" href="#team" id="ref-for-team⑤①">Team</a> <em class="rfc2119">must</em> do one of the following:</p>
+      <ul>
+       <li data-md>
+        <p>Abide by the objectors' request, if they all agree on the
+alternative course of action (e.g., to abandon,
+extend, or complete charter refinement).</p>
+       <li data-md>
+        <p>Initiate an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑤">AC Review</a> to formally solicit the input of
+the community and take a W3C Decision on the subsequent
+course of action.</p>
+       <li data-md>
+        <p>Convene a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③">Council</a> to decide the subsequent course of action.</p>
+      </ul>
+      <p>(No action is required to be taken when fewer than 5 members object.)</p>
+     <li data-md>
+      <p>Any other objections are processed normally (See <a href="#addressing-fo">§ 5.6 Addressing Formal Objections</a>).</p>
+    </ul>
+    <h3 class="heading settled" data-level="4.3" id="WGCharter"><span class="secno">4.3. </span><span class="content"> Content of a Charter</span><a class="self-link" href="#WGCharter"></a></h3>
+    <p>A Working Group or Interest Group <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="charter">charter</dfn> <em class="rfc2119">must</em> include all of the following information.</p>
+    <ul>
+     <li> The group’s mission
+			(e.g., develop a technology or process, review the work of other groups). 
+     <li> The scope of the group’s work and criteria for success. 
+     <li> The duration of the proposed charter for the group. 
+     <li> The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software). 
+     <li>
+       Expected milestone dates where available. 
+      <p class="note" role="note"><span class="marker">Note:</span> A charter does not need to include
+			schedules for review of other group’s deliverables.</p>
+     <li> The process for the group to approve the release of deliverables
+			(including intermediate results). 
+     <li> Any dependencies by groups within or outside of W3C on the deliverables of this group.
+			For any dependencies, the charter <em class="rfc2119">must</em> specify
+			the mechanisms for communication about the deliverables. 
+     <li> Any dependencies of this group on other groups within or outside of W3C.
+			Such dependencies include interactions with <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a>. 
+     <li> The <a href="#confidentiality-levels">level of confidentiality</a> of the group’s proceedings and deliverables. 
+     <li> The name and affiliation of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑤">Chair</a> or co-Chairs. 
+     <li> Meeting mechanisms and expected frequency. 
+     <li> If known,
+			the date of the first <a href="#ftf-meeting" id="ref-for-ftf-meeting①">face-to-face meeting</a>.
+			The date of the first face-to-face meeting of a proposed group <em class="rfc2119">must not</em> be sooner than <span class="time-interval">eight weeks</span> after the date of the proposal. 
+     <li> Communication mechanisms to be employed within the group,
+			between the group and the rest of W3C,
+			and with the general public. 
+     <li> Any voting procedures or requirements
+			other than those specified in <a href="#Votes">§ 5.2.3 Deciding by Vote</a>. 
+     <li> An estimate of the expected time commitment from participants. 
+     <li> The expected time commitment and level of involvement by the Team
+			(e.g., to track developments,
+			write and edit technical reports,
+			develop code,
+			or organize pilot experiments). 
+     <li> Intellectual property information.
+			What are the intellectual property (including patents and copyright)
+			considerations affecting the success of the Group?
+			In particular, is there any reason to believe
+			that it will be difficult to meet the Royalty-Free licensing goals
+			in “Licensing Goals for W3C Specifications”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>? 
+    </ul>
+    <p>See also the charter requirements in “Licensing Goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>For every Recommendation Track deliverable
+	that continues work on a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report">technical report</a> published under any other Charter (including a predecessor group of the same name),
+	for which there is at least an existing <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd">First Public Working Draft</a> the description of that deliverable in the proposed charter of the adopting Working Group <em class="rfc2119">must</em> provide the following information:</p>
+    <ul>
+     <li> The title,
+			stable URL,
+			and publication date of the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD">Working Draft</a> or other Recommendation-track document
+			that will serve as the basis for work on the deliverable
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="adopted-draft">Adopted Draft</dfn>”); 
+     <li> The title,
+			stable URL,
+			and publication date of the document
+			that was used as the basis for its most recent Exclusion Opportunity
+			as per
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft">Exclusion Draft</dfn>”); and 
+     <li> The stable URL of the Working Group charter
+			under which the Exclusion Draft was published
+			(labeled the “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft-charter">Exclusion Draft Charter</dfn>”). 
+    </ul>
+    <p>All of the above data <em class="rfc2119">must</em> be identified
+	in the adopting Working Group’s charter using the labels indicated.</p>
+    <p>The <a data-link-type="dfn" href="#adopted-draft" id="ref-for-adopted-draft">Adopted Draft</a> and the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft">Exclusion Draft</a> <em class="rfc2119">must</em> each be adopted in their entirety and without any modification.
+	The proposed charter <em class="rfc2119">must</em> state
+	the dates on which the Exclusion Opportunity
+	that arose on publishing the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft①">Exclusion Draft</a> began and ended.
+	As per “Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	this potentially means that exclusions can only be made immediately on joining a Working Group.</p>
+    <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding participation,
+	including specifying
+	that the <span id="ig-mail-only">only requirement for participation (by anyone) in
+	the Interest Group is subscription to the Interest Group mailing list</span>.
+	This type of Interest Group <em class="rfc2119">may</em> have <a href="#public-participant-ig" id="ref-for-public-participant-ig">public participants</a>. </p>
+    <p>A charter <em class="rfc2119">may</em> include
+	provisions other than those required by this document.
+	The charter <em class="rfc2119">should</em> highlight
+	whether additional provisions impose constraints
+	beyond those of the W3C 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>
+    <h3 class="heading settled" data-level="4.4" id="CharterReview"><span class="secno">4.4. </span><span class="content"> Charter Review and Approval</span><a class="self-link" href="#CharterReview"></a></h3>
+    <h4 class="heading settled" data-level="4.4.1" id="charter-major-changes"><span class="secno">4.4.1. </span><span class="content"> New Charters and Major Changes</span><a class="self-link" href="#charter-major-changes"></a></h4>
+    <p>Any new <a data-link-type="dfn" href="#charter" id="ref-for-charter⑧">charter</a> (including re-chartering of existing <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group②">chartered groups</a>)
+	and any change that is not a <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes">minor change</a> (per <a href="#charter-minor-changes">§ 4.4.2 Minor Changes to Active Charters</a>) to an already-approved <a data-link-type="dfn" href="#charter" id="ref-for-charter⑨">charter</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG③">Interest Group</a> <em class="rfc2119">must</em> be approved by a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision③">W3C Decision</a> following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑥">AC Review</a> of that <a data-link-type="dfn" href="#charter" id="ref-for-charter①⓪">charter</a>.
+	Modifications to a <a data-link-type="dfn" href="#charter" id="ref-for-charter①①">charter</a> <em class="rfc2119">should</em> have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑤">consensus</a> of the group.</p>
+    <p>The review period <em class="rfc2119">must</em> be at least 28 days.
+	Any <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑥">Advisory Committee representative</a> <em class="rfc2119">may</em> request an extended review period
+	in response to the Call for Review;
+	upon receipt of any such request,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤②">Team</a> <em class="rfc2119">must</em> extend the review period
+	to at least 60 days.</p>
+    <p>The Call for Review of a modified charter <em class="rfc2119">must</em> highlight important changes
+	(e.g., regarding changes in scope, deliverables, or resource allocation)
+	and <em class="rfc2119">must</em> include rationale for those changes.</p>
+    <p>The Call for Review of a new or modified charter <em class="rfc2119">must</em> include a disposition of comments received during the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑨">charter refinement</a> process,
+	highlighting any issues that were closed despite sustained objections.</p>
+    <h4 class="heading settled" data-level="4.4.2" id="charter-minor-changes"><span class="secno">4.4.2. </span><span class="content"> Minor Changes to Active Charters</span><a class="self-link" href="#charter-minor-changes"></a></h4>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change">Editorial changes</a> or <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change">substantive changes</a> to a <a data-link-type="dfn" href="#charter" id="ref-for-charter①②">charter</a> (including <a href="#charter-extension">extensions</a>)
+	that do not affect the scope of the group’s work
+	or the way the group functions in any significant way
+	are deemed <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minor-changes">minor changes</dfn> and <em class="rfc2119">may</em> be approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑦">Team Decision</a>,
+	in which case they do not require <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①⓪">charter refinement</a> nor <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑦">Advisory Committee Review</a>.
+	Any change to the scope of the <a data-link-type="dfn" href="#charter" id="ref-for-charter①③">charter</a> or addition of a new <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track">REC track</a> deliverable
+	that does not fall within the scope of an existing deliverable
+	is a major, not <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes①">minor</a>, change.
+	The following are examples of <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes②">minor changes</a>:
+	the renaming or restructuring (e.g. splitting or combining) of existing in-scope deliverables,
+	the addition of new <a href="#note-track">Note track</a> deliverables that help explain the group’s work
+	a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact④">Team Contact</a>,
+	or a change of <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑥">Chair</a>. <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes③">Minor changes</a>, other than a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑤">Team Contact</a>, <em class="rfc2119">should</em> have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑥">consensus</a> of the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤③">Team</a> <em class="rfc2119">may</em> nevertheless choose
+	to initiate <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①①">charter refinement</a> and/or <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑧">Advisory Committee Review</a> when it thinks the changes would benefit from more scrutiny or explicit buy-in.</p>
+    <p>Though <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑨">Advisory Committee Review</a> is not required,
+	such changes <em class="rfc2119">must</em> still be announced
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①②">Advisory Committee</a>,
+	and to participants in the <a href="#wgparticipant" id="ref-for-wgparticipant①">Working</a> or <a href="#igparticipant" id="ref-for-igparticipant①">Interest</a> Group,
+	and a rationale must be provided.</p>
+    <h3 class="heading settled" data-level="4.5" id="cfp"><span class="secno">4.5. </span><span class="content"> Call for Participation in a Chartered Group</span><a class="self-link" href="#cfp"></a></h3>
+    <p>Deciding whether to adopt a proposed <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⓪">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG④">Interest Group</a> <a data-link-type="dfn" href="#charter" id="ref-for-charter①④">charter</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision④">W3C Decision</a>.
+	Charters <em class="rfc2119">may</em> be amended based on review comments
+	per <a href="#ACReviewAfter">§ 5.7.2 Determining the W3C Decision</a> before the Call for Participation.</p>
+    <p>If the decision is to charter the group,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤④">Team</a> <em class="rfc2119">must</em> issue a Call for Participation to the Advisory Committee.
+	For a new group, this announcement officially creates the group.
+	The announcement <em class="rfc2119">must</em> include a reference to the <a href="#WGCharter">charter</a>,
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑦">Chair(s)</a>,
+	and the name(s) of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑥">Team Contact(s)</a>.</p>
+    <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).
+	When a group is re-chartered,
+	individuals participating in the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①①">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑤">Interest Group</a> before the new Call for Participation
+	may attend any meetings held within forty-five (45) days of the Call for Participation
+	even if they have not yet formally rejoined the group
+	(i.e., committed to the terms of the charter and patent policy).</p>
+    <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against the decision to create
+	or substantially modify
+	a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.6" id="charter-extension"><span class="secno">4.6. </span><span class="content"> Charter Extension</span><a class="self-link" href="#charter-extension"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑤">Team</a> <em class="rfc2119">may</em> decide
+	to extend a Working Group or Interest Group charter
+	with no other substantive modifications.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑥">Team</a> <em class="rfc2119">must</em> announce
+	such <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="charter extension" id="dfn-charter-extension">extensions</dfn> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①③">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate the new duration.
+	The announcement <em class="rfc2119">must</em> also include rationale for the extension,
+	a reference to the <a href="#WGCharter">charter</a>,
+	and the Group homepage
+	(which includes at least
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑧">Chair(s)</a>,
+	the name of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑦">Team Contact</a>,
+	and instructions for joining the group).</p>
+    <p>After a charter extension,
+	Advisory Committee representatives
+	and the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑨">Chair</a> 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> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑧">Team decision</a> regarding the extension of a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.7" id="GeneralTermination"><span class="secno">4.7. </span><span class="content"> Chartered Group Closure</span><a class="self-link" href="#GeneralTermination"></a></h3>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①②">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑥">Interest Group</a> charter specifies a duration for the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑦">Team</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑦">TAG</a>, or the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②③">AB</a> <em class="rfc2119">may</em> propose to close a group
+	prior to the date specified in the charter in any of the following circumstances:</p>
+    <ul>
+     <li data-md>
+      <p>There are insufficient member resources to produce chartered deliverables
+or to maintain the group,
+according to priorities established within W3C.</p>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="https://www.w3.org/policies/patent-policy/#patent-advisory-group" id="ref-for-patent-advisory-group">Patent Advisory Group</a> concluded that the work <em class="rfc2119">should</em> be terminated.</p>
+     <li data-md>
+      <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑧">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②④">AB</a> determined that continuing operation of the chartered group or its work
+would be detrimental to W3C or its mission.</p>
+     <li data-md>
+      <p>The group produced all chartered deliverables ahead of schedule.</p>
+    </ul>
+    <p>Such a proposal to close a group must be accompanied by rationale,
+	and the proposal must be confirmed by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⓪">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑤">W3C Decision</a>.</p>
+    <p>Closing a Working Group has implications
+	with respect to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h2 class="heading settled" data-level="5" id="decisions"><span class="secno">5. </span><span class="content"> Decisions</span><a class="self-link" href="#decisions"></a></h2>
+    <p>W3C attempts to resolve issues through dialog.
+	Individuals who disagree strongly with a decision <em class="rfc2119">should</em> register with the Chair any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑤">Formal Objections</a>.</p>
+    <h3 class="heading settled" data-level="5.1" id="decision-types"><span class="secno">5.1. </span><span class="content"> Types of Decisions</span><a class="self-link" href="#decision-types"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⓪">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①③">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑦">Interest Group</a> has the prerogative
+	to make certain decisions based on their own judgment.
+	Such decisions are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chair-decisions">chair decisions</dfn>.</p>
+    <p>In contrast,
+	decisions taken by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②①">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑧">Interest Group</a> on the basis of having assessed the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑦">consensus</a> of the group
+	or following a vote (see <a href="#Votes">§ 5.2.3 Deciding by Vote</a>)
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="group decision | resolution" id="group-decision">group decisions</dfn> (also known as group “resolutions”).</p>
+    <p>Decisions made by members of the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑧">Team</a> in connection with this Process,
+	based on their own individual or collective judgement,
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Team Decision | Team&apos;s Decision" data-noexport id="team-decision">Team Decisions</dfn>.</p>
+    <p>In contrast,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-w3c-decision">W3C decision</dfn> is
+	determined by the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑨">Team</a> on behalf of the W3C community
+	by <a href="#ACReviewAfter">assessing the consensus of the W3C Community</a> after an <a href="#ACReview">Advisory Committee review</a>.</p>
+    <h3 class="heading settled" data-level="5.2" id="consensus-building"><span class="secno">5.2. </span><span class="content"> Consensus Building</span><a class="self-link" href="#consensus-building"></a></h3>
+    <h4 class="heading settled" data-level="5.2.1" id="Consensus"><span class="secno">5.2.1. </span><span class="content"> Consensus</span><a class="self-link" href="#Consensus"></a></h4>
+    <p>Consensus is a core value of W3C.
+	To promote consensus,
+	the W3C process requires Chairs to ensure
+	that groups consider all legitimate views and objections,
+	and endeavor to resolve them,
+	whether these views and objections are expressed by the active participants of the group
+	or by others
+	(e.g., another W3C group,
+	a group in another organization,
+	or the general public).
+	Decisions <em class="rfc2119">may</em> be made during meetings
+	(<a href="#ftf-meeting" id="ref-for-ftf-meeting②">face-to-face</a> or <a href="#distributed-meeting" id="ref-for-distributed-meeting">distributed</a>)
+	as well as through <a href="#discussion-archiving">persistent text-based discussions</a>.</p>
+    <p>The following terms are used in this document
+	to describe the level of support for a decision among a set of eligible individuals:</p>
+    <dl>
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Consensus">Consensus</dfn>: 
+     <dd> A substantial number of individuals in the set
+			support the decision
+			and there is no sustained objection from anybody in the set.
+			Individuals in the set <em class="rfc2119">may</em> abstain.
+			Abstention is either an explicit expression of no opinion
+			or silence by an individual in the set. 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Unanimity">Unanimity</dfn>: 
+     <dd> The particular case of <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑧">consensus</a> where all individuals in the set support the decision
+			(i.e., no individual in the set abstains). 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Dissent">Dissent</dfn>: 
+     <dd> At least one individual in the set sustains an objection. 
+    </dl>
+    <p class="note" role="note"><span class="marker">Note:</span> A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑥">Formal Objection</a> always indicates a sustained objection,
+	but isn’t necessary to express it
+	(except in the context of formal <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①①">AC Reviews</a>).
+	Disagreement with a proposed decision,
+	however, does not always rise to the level of sustained objection,
+	as individuals could be willing to accept a decision
+	while expressing disagreement.</p>
+    <p>By default, the set of individuals eligible to participate in a decision is the set of group participants.
+	The Process Document does not require a quorum for decisions
+	(i.e., the minimal number of eligible participants required to be present before the Chair can call a question).
+	A charter <em class="rfc2119">may</em> include a quorum requirement for consensus decisions.</p>
+    <p>Where <a data-link-type="dfn" href="#def-Unanimity" id="ref-for-def-Unanimity">unanimity</a> is not possible,
+	a group <em class="rfc2119">should</em> strive to make <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑨">consensus</a> decisions
+	where there is significant support and few abstentions.
+	The Process Document does not require a particular percentage of eligible participants
+	to agree to a motion in order for a decision to be made.
+	To avoid decisions where there is widespread apathy,
+	(i.e., little support and many abstentions),
+	groups <em class="rfc2119">should</em> set minimum thresholds of active support before a decision can be recorded.
+	The appropriate percentage <em class="rfc2119">may</em> vary depending on the size of the group
+	and the nature of the decision.
+	A charter <em class="rfc2119">may</em> include threshold requirements for consensus decisions.
+	For instance, a charter might require a supermajority of eligible participants
+	(i.e., some established percentage above 50%)
+	to support certain types of consensus decisions.</p>
+    <div class="note" role="note">
+      Note: Chairs have substantial flexibility
+	in how they obtain and assess consensus among their groups.
+	Unless otherwise constrained by charter,
+	they can use modes including but not limited to explicit calls for consensus,
+	polls of participants,
+	“lazy consensus” in which lack of objection after sufficient notice is taken as assent;
+	they can also delegate and empower a document editor
+	to assess consensus on their behalf,
+	whether in general
+	or for specific pre-determined circumstances
+	(e.g. in non-controversial situations, for specific types of issues, etc.). 
+     <p>If questions or disagreements arise,
+	the final determination of consensus remains with the chair.</p>
+    </div>
+    <h4 class="heading settled" data-level="5.2.2" id="managing-dissent"><span class="secno">5.2.2. </span><span class="content"> Managing Dissent</span><a class="self-link" href="#managing-dissent"></a></h4>
+    <p>In some cases, even after careful consideration of all points of view,
+	a group might find itself unable to reach consensus.
+	The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②②">Chair</a> <em class="rfc2119">may</em> record a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent">dissent</a> so that the group can make progress
+	(for example, to produce a deliverable in a timely manner).
+	Dissenters cannot stop a group’s work
+	simply by saying that they cannot live with a decision.
+	When the Chair believes that the Group has duly considered
+	the legitimate concerns of dissenters as far as is possible and reasonable,
+	the group <em class="rfc2119">should</em> move on.</p>
+    <p>Groups <em class="rfc2119">should</em> favor proposals that create the weakest objections.
+	This is preferred over proposals that are supported by a large majority
+	but that cause strong objections from a few people.
+	As part of making a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent①">dissent</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②③">Chair</a> is expected to be aware of which participants work for the same
+	(or <a href="#MemberRelated">related</a>)
+	Member organizations and weigh their input accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Dissenters can escalate their sustained objection to a decision by registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑦">Formal Objection</a>.</p>
+    <h4 class="heading settled" data-level="5.2.3" id="Votes"><span class="secno">5.2.3. </span><span class="content"> Deciding by Vote</span><a class="self-link" href="#Votes"></a></h4>
+    <p>A group <em class="rfc2119">should</em> only conduct a vote to resolve a <em>substantive issue</em> after the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②④">Chair</a> has determined that all available means of <a href="#Consensus">reaching consensus</a> through technical discussion and compromise have failed,
+	and that a vote is necessary to break a deadlock.
+	In this case the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑤">Chair</a> <em class="rfc2119">must</em> record
+	(e.g., in the <a data-link-type="dfn" href="#minutes" id="ref-for-minutes②">minutes</a> of the meeting or in an archived email message):</p>
+    <ul>
+     <li> an explanation of the issue being voted on; 
+     <li> the decision to conduct a vote
+			(e.g., a simple majority vote) to resolve the issue; 
+     <li> the outcome of the vote; 
+     <li> any Formal Objections. 
+    </ul>
+    <p>In order to vote to resolve a substantive issue,
+	an individual <em class="rfc2119">must</em> be a group <a data-link-type="dfn" href="#participant" id="ref-for-participant①">participant</a>.
+	Each organization represented in the group <em class="rfc2119">must</em> have at most one vote,
+	even when the organization is represented by several participants in the group
+	(including Invited Experts).
+	For the purposes of voting:</p>
+    <ul>
+     <li> A Member or group of <a href="#MemberRelated">related Members</a> is considered a single organization. 
+     <li> The <a href="#Team">Team</a> is considered an organization. 
+    </ul>
+    <p>Unless the charter states otherwise, <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">may</em> vote.</p>
+    <p>If a participant is unable to attend a vote,
+	that individual <em class="rfc2119">may</em> authorize anyone at the meeting
+	to act as a proxy.
+	The absent participant <em class="rfc2119">must</em> inform the Chair in writing
+	who is acting as proxy, with written instructions on the use of the proxy.
+	For a Working Group or Interest Group,
+	see the related requirements regarding an individual
+	who attends a meeting as a <a href="#mtg-substitute" id="ref-for-mtg-substitute">substitute</a> for a participant.</p>
+    <p>A group <em class="rfc2119">may</em> vote for other purposes than to resolve a substantive issue.
+	For instance, the Chair often conducts a “straw poll” vote
+	as a means of determining whether there is consensus about a potential decision.</p>
+    <p>A group <em class="rfc2119">may</em> also vote to make a process decision.
+	For example,
+	it is appropriate to decide by simple majority
+	whether to hold a meeting in San Francisco or San Jose
+	(there’s not much difference geographically).
+	When simple majority votes are used to decide minor issues,
+	voters are <em class="rfc2119">not required</em> to state the reasons for votes,
+	and the group is <em class="rfc2119">not required</em> to record individual votes.</p>
+    <p>A group charter <em class="rfc2119">may</em> include formal voting procedures
+	(e.g., quorum or threshold requirements)
+	for making decisions about substantive issues.</p>
+    <h3 class="heading settled" data-level="5.3" id="formal-address"><span class="secno">5.3. </span><span class="content"> Formally Addressing an Issue</span><a class="self-link" href="#formal-address"></a></h3>
+    <p>In the context of this document,
+	a group has <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="formally-addressed">formally addressed</dfn> an issue when it has sent a public, substantive response
+	to the reviewer who raised the issue.
+	A substantive response is expected to include rationale for decisions
+	(e.g., a technical explanation, a pointer to charter scope, or a pointer to a requirements document).
+	The adequacy of a response is measured
+	against what a W3C reviewer would generally consider to be technically sound.
+	If a group believes that a reviewer’s comments result from a misunderstanding,
+	the group <em class="rfc2119">should</em> seek clarification before reaching a decision.</p>
+    <p>As a courtesy,
+	both Chairs and reviewers <em class="rfc2119">should</em> set expectations
+	for the schedule of responses and acknowledgments.
+	The group <em class="rfc2119">should</em> reply to a reviewer’s initial comments
+	in a timely manner.
+	The group <em class="rfc2119">should</em> set a time limit
+	for acknowledgment by a reviewer of the group’s substantive response;
+	a reviewer cannot block a group’s progress.
+	It is common for a reviewer to require a week or more
+	to acknowledge and comment on a substantive response.
+	The group’s responsibility to respond to reviewers
+	does not end once a reasonable amount of time has elapsed.
+	However, reviewers <em class="rfc2119">should</em> realize
+	that their comments will carry less weight
+	if not sent to the group in a timely manner.</p>
+    <p>Substantive responses <em class="rfc2119">should</em> be recorded.
+	The group <em class="rfc2119">should</em> maintain an accurate summary
+	of all substantive issues and responses to them
+	(e.g., in the form of an issues list with links to mailing list archives).</p>
+    <h3 class="heading settled" data-level="5.4" id="WGChairReopen"><span class="secno">5.4. </span><span class="content"> Reopening a Decision When Presented With New Information</span><a class="self-link" href="#WGChairReopen"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑥">Chair</a> <em class="rfc2119">may</em> reopen a decision
+	when presented with new information, including:</p>
+    <ul>
+     <li> additional technical information, 
+     <li> comments by email from participants who were unable to attend a scheduled meeting, 
+     <li> comments by email from meeting attendees
+			who chose not to speak out during a meeting
+			(e.g., so they could confer later with colleagues or for cultural reasons). 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑦">Chair</a> <em class="rfc2119">should</em> record
+	that a decision has been reopened,
+	and <em class="rfc2119">must</em> do so upon request from a group participant.</p>
+    <h3 class="heading settled" data-level="5.5" id="registering-objections"><span class="secno">5.5. </span><span class="bs-old-id" id="chair-decision-appeal"></span><span class="bs-old-id" id="wg-decision-appeal"></span><span class="bs-old-id" id="WGAppeals"></span><span class="bs-old-id" id="WGArchiveMinorityViews"></span><span class="content"> Registering Formal Objections</span><a class="self-link" href="#registering-objections"></a></h3>
+    <p>Any individual
+	(regardless of whether they are associated with a Member) <em class="rfc2119">may</em> appeal any decision made in connection with this Process
+	(except those having a different appeal process)
+	by registering a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="FormalObjection">Formal Objection</dfn> with the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⓪">Team</a>.
+	Group participants <em class="rfc2119">should</em> inform
+	their <a href="#TeamContact" id="ref-for-TeamContact⑨">Team Contact</a> as well as the group’s Chair(s).
+	The Team Contact <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑦">CEO</a> when a group participant has also raised concerns about due process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> In this document, the term <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑧">Formal Objection</a> is used to emphasize this process implication:
+	Formal Objections receive formal consideration and a formal response.
+	The word “objection” used alone has its ordinary English connotations.
+	See <a href="#consensus-building">§ 5.2 Consensus Building</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑨">Formal Objection</a> <em class="rfc2119">must</em> include a summary of
+	the issue (whether technical or procedural),
+	the decision being appealed,
+	and the rationale for the objection.
+	It <em class="rfc2119">should</em> cite technical arguments
+	and propose changes that would remove the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⓪">Formal Objection</a>;
+	these proposals <em class="rfc2119">may</em> be vague or incomplete. <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①①">Formal Objections</a> that do not provide substantive arguments
+	or rationale are unlikely to receive serious consideration.
+	Counter-arguments,
+	rationales,
+	and decisions <em class="rfc2119">should</em> also be recorded.</p>
+    <p>No later than when the <a href="#team-fo-mediation">relevant Council is initiated</a>,
+	a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①②">Formal Objection</a> against a decision regarding a publicly-available document <em class="rfc2119">must</em> be made <a href="#confidentiality-change">publicly available</a>;
+	likewise, a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①③">Formal Objection</a> against a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①">Member-visible</a> decision <em class="rfc2119">must</em> be made <a href="#confidentiality-change">available to Members</a>.
+	A Call for Review to the Advisory Committee <em class="rfc2119">must</em> identify any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①④">Formal Objections</a> related to that review.
+	This requirement is waived
+	if the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑤">Formal Objection</a> is resolved to the satisfaction of the objector
+	before its <a href="#confidentiality-change">confidentiality is changed</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑥">Formal Objections</a> against matter in a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①">technical report</a> <a href="#adv-verif-reqs">are expected to be fully addressed</a> before <a href="#rec-advance">requesting advancement</a> of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②">technical report</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑦">Formal Objection</a> filed during an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①②">Advisory Committee Review</a> is considered registered at the close of the review period.</p>
+    <p>Registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑧">Formal Objection</a> initiates the process of <a href="#addressing-fo">addressing the Formal Objection</a>.
+	The resolution of a recorded Formal Objection—​whether by a Council decision, adoption of a consensus proposal, retraction of the Formal Objection, etc.—​must be recorded and made available at the same level of visibility as the record of the Formal Objection itself.</p>
+    <h3 class="heading settled" data-level="5.6" id="addressing-fo"><span class="secno">5.6. </span><span class="content"> Addressing Formal Objections</span><a class="self-link" href="#addressing-fo"></a></h3>
+    <h4 class="heading settled" data-level="5.6.1" id="team-fo-mediation"><span class="secno">5.6.1. </span><span class="content"> Investigation and Mediation by the Team</span><a class="self-link" href="#team-fo-mediation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑥①">Team</a> considers the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑨">Formal objection</a>,
+	researches the question,
+	interviews parties,
+	and so on,
+	to make sure the problem and the various viewpoints are well understood,
+	and to the extent possible,
+	to arrive at a recommended disposition.</p>
+    <p>In parallel, the Team <em class="rfc2119">should</em> start the steps necessary
+	to <a href="#council-convention">convene</a> a Council.</p>
+    <p>If the <a data-link-type="dfn" href="#team" id="ref-for-team⑥②">Team</a> can resolve the issue
+	to the satisfaction of the individual that filed the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⓪">Formal Objection</a>,
+	the individual withdraws the objection and the disposition process terminates.</p>
+    <p>Otherwise,
+	upon concluding that consensus cannot be found,
+	and no later than 90 days after the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②①">Formal Objection</a> being registered,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑥③">Team</a> <em class="rfc2119">must</em> deliver to the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council④">Council</a> a report
+	documenting its findings and attempts to find consensus,
+	and hand over the matter to the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑤">W3C Council</a>.</p>
+    <h4 class="heading settled" data-level="5.6.2" id="council"><span class="secno">5.6.2. </span><span class="content"> W3C Council</span><a class="self-link" href="#council"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-local-lt="Council" id="w3c-council">W3C Council</dfn> is the body convened to resolve <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②②">Formal Objections</a> by combining the capabilities and perspectives of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑤">AB</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑨">TAG</a>, and the <a data-link-type="dfn" href="#team" id="ref-for-team⑥④">Team</a>,
+	and is tasked with doing so in the best interests of the Web and W3C.</p>
+    <h5 class="heading settled" data-level="5.6.2.1" id="council-composition"><span class="secno">5.6.2.1. </span><span class="content"> Council Composition</span><a class="self-link" href="#council-composition"></a></h5>
+    <p>Each <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑥">W3C Council</a> is composed of the following members (excepting any <a href="#council-participation">renounced or dismissed</a>):</p>
+    <ul>
+     <li data-md>
+      <p>the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑧">CEO</a> or their chosen <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑤">Team</a> delegate</p>
+     <li data-md>
+      <p>the members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑥">Advisory Board</a></p>
+     <li data-md>
+      <p>the elected and appointed members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⓪">Technical Architecture Group</a></p>
+    </ul>
+    <p>Participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑦">W3C Council</a> <em class="rfc2119">must not</em> require attendance of <a data-link-type="dfn" href="#ftf-meeting" id="ref-for-ftf-meeting③">face-to-face meetings</a>.</p>
+    <p>A distinct instance of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑧">W3C Council</a> is convened for each decision being appealed or objected to.
+	The list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑨">Council</a> members evolves
+	as <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑦">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③①">TAG</a> terms start and end
+	until <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed">dismissal</a> and <a data-link-type="dfn" href="#renounce" id="ref-for-renounce">renunciation</a> are concluded,
+	at which point the membership of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⓪">Council</a> is fixed.
+	However, if the number of active members in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①①">Council</a> falls so low as to hinder effective and balanced deliberations,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair">Council Chair</a> <em class="rfc2119">should</em> dissolve the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①②">Council</a> and call for a new one to be convened.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> TAG and AB elections have no effect on the Council’s membership
+	once it is fixed.</p>
+    <p>A <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑥">Team</a> member is assigned
+	to act as the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-team-contact">Council Team Contact</dfn>,
+	to support this Council
+	and to facilitate adherence to this Process.</p>
+    <h5 class="heading settled" data-level="5.6.2.2" id="council-delegation"><span class="secno">5.6.2.2. </span><span class="content"> Extraordinary Delegation</span><a class="self-link" href="#council-delegation"></a></h5>
+    <p>In extraordinary cases,
+	if they feel a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①③">Council</a> would not be the appropriate deciding body,
+	a member of the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑦">Team</a> (particularly the Legal Counsel) or
+	any potential Council member
+	may suggest that the decision for that specific Formal Objection be delegated
+	to the W3C Board of Directors,
+	to an officer of its corporation (such as the Legal Counsel),
+	or to one or more specific individuals from the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑧">Team</a>.
+	The potential Council members then <em class="rfc2119">may</em> confidentially discuss
+	and <em class="rfc2119">must</em> vote
+	whether to delegate the decision for that specific <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②③">Formal Objection</a>.
+	A decision to delegate <em class="rfc2119">must</em> be supported by a two-thirds supermajority vote
+	(i.e., at least twice as many votes in favor as against).
+	Delegation in such cases cannot be later revoked.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑨">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①④">Advisory Committee</a> when a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②④">Formal Objection</a> has been delegated,
+	and to whom it has been delegated.</p>
+    <h5 class="heading settled" data-level="5.6.2.3" id="council-participation"><span class="secno">5.6.2.3. </span><span class="content"> Council Participation, Dismissal, and Renunciation</span><a class="self-link" href="#council-participation"></a></h5>
+    <p>A potential Council member may be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="dismissed | dismiss | dismissal" data-noexport id="dismissed">dismissed</dfn> from the Council.
+	In order to apply consistent criteria,
+	the potential Council members decide collectively
+	which reasons against service
+	rise to a sufficient level for a potential member to be <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed①">dismissed</a>.
+	No-one is automatically dismissed,
+	and individual recusal is not used in the Council. <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed②">Dismissal</a> applies to an individual person in the context of a specific Council,
+	and should be used rarely in order to preserve the greatest diversity on the Council.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> A W3C Council is a deliberative body whose purpose is
+	to find the best way forward for the Web and for W3C.
+	It is not a judicial body tasked with determining right or wrong.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⓪">Team</a> <em class="rfc2119">must</em> draft a list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①④">Council</a> members,
+	with annotations of possible reasons for dismissal against each one.
+	The W3C community,
+	including members and team, and potential council members, <em class="rfc2119">must</em> be given an opportunity to contribute possible reasons to this list.
+	Affected members <em class="rfc2119">must</em> be given
+	an opportunity to respond to such comments about themselves.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦①">Team</a> may report comments verbatim
+	or may paraphrase them while preserving their intent;
+	they may also elide inappropriate comments,
+	such as any that violate applicable laws or the <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a>.</p>
+    <p>Before a Council forms,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦②">Team</a> presents the entire list of potential members
+	and collected reasons and responses
+	to the potential Council members,
+	who then consider for each potential member
+	whether that individual’s participation
+	would compromise the integrity of the Council decision,
+	and vote whether to dismiss that potential member.
+	No one is allowed to vote on their own dismissal;
+	each dismissal is enacted if there are at least as many ballots for as against.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since dismissal is individual,
+	when the decision being objected to was made by the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③②">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑧">AB</a> acting as a body,
+	the entire <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③③">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑨">AB</a> is not expected to be dismissed.</p>
+    <p>An individual <em class="rfc2119">may</em> also <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="renounce | renunciation" data-noexport id="renounce">renounce</dfn> their seat on a Council, for strong reason,
+	such as being forbidden by their employer to serve. The individual chooses the extent to which they explain
+	their renunciation.
+	Renunciation is disqualification from participation,
+	not abstention,
+	and <em class="rfc2119">should not</em> be used
+	to excuse an absence of participation.</p>
+    <p>Any person who has been <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed③">dismissed</a> or who <a data-link-type="dfn" href="#renounce" id="ref-for-renounce①">renounces</a> their seat
+	does not receive <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑤">Council</a> materials,
+	take part in its deliberations,
+	help in the determination of consensus,
+	or vote.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑥">W3C Council</a> <em class="rfc2110">may</em> still solicit and hear their testimony,
+	as they can of anyone else in the W3C community.</p>
+    <h5 class="heading settled" data-level="5.6.2.4" id="council-short-circuit"><span class="secno">5.6.2.4. </span><span class="content"> Short Circuit</span><a class="self-link" href="#council-short-circuit"></a></h5>
+    <p>The full Council process <em class="rfc2119">may</em> be short-circuited if
+	the Team recommends a resolution
+	and potential members of a Council who are not renouncing their seat
+	confirm it by a vote which results in both of the following:</p>
+    <ul>
+     <li data-md>
+      <p>at least 80% of them vote affirmatively to adopt this resolution</p>
+     <li data-md>
+      <p>none of them vote against adopting the resolution</p>
+    </ul>
+    <p>The request for confirmation <em class="rfc2119">must</em> be open for a period of at least two weeks,
+	or until every potential member of the Council not renouncing their seat
+	has voted,
+	whichever is shortest.</p>
+    <p>This step <em class="rfc2119">may</em> be run concurrently with <a href="#council-participation">§ 5.6.2.3 Council Participation, Dismissal, and Renunciation</a> and prior to choosing a <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair①">Chair</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This is intended for exceptional cases
+	that don’t seem to warrant a full Council response
+	because they are, for instance, too trivial, duplicative, etc.</p>
+    <h5 class="heading settled" data-level="5.6.2.5" id="council-chairing"><span class="secno">5.6.2.5. </span><span class="content"> Council Chairing</span><a class="self-link" href="#council-chairing"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Council Chair | Council Chair" data-noexport id="w3c-council-chair">Chair</dfn> of each W3C Council is chosen by its members,
+	by consensus if possible,
+	falling back to a vote if that fails.
+	The chair must be a member of that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑦">W3C Council</a>.
+	Chair selection happens during formation of each Council,
+	and <em class="rfc2119">must</em> be re-run
+	if requested by the <a data-link-type="dfn" href="#council-team-contact" id="ref-for-council-team-contact">Council Team Contact</a> or by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑧">Chair</a> during the Council’s operation.</p>
+    <h5 class="heading settled" data-level="5.6.2.6" id="council-convention"><span class="secno">5.6.2.6. </span><span class="content"> Convening the Council</span><a class="self-link" href="#council-convention"></a></h5>
+    <p>Upon appointment of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair②">W3C Council Chair</a> and delivery of the <a data-link-type="dfn" href="#team" id="ref-for-team⑦③">Team</a>’s report,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑧">W3C Council</a> is considered to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="convened">convened</dfn> and can start <a href="#council-deliberations">deliberations</a>.</p>
+    <p>If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑨">W3C Council</a> has not yet been <a data-link-type="dfn" href="#convened" id="ref-for-convened">convened</a> within 90 days of a Formal Objection
+	being <a href="#registering-objections">registered</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑨">Chairs</a> of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③④">TAG</a> and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⓪">AB</a> <em class="rfc2119">may</em> take independent action to ensure
+	that the <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed④">dismissal</a>, <a data-link-type="dfn" href="#renounce" id="ref-for-renounce②">renunciation</a>,
+	and <a href="#council-chairing">chair selection</a> processes have been run.
+	If a report from the Team is not delivered within those 90 days,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⓪">Council</a> is considered <a data-link-type="dfn" href="#convened" id="ref-for-convened①">convened</a> upon selection of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair③">Council Chair</a>.</p>
+    <h5 class="heading settled" data-level="5.6.2.7" id="council-deliberations"><span class="secno">5.6.2.7. </span><span class="content"> Council Deliberations</span><a class="self-link" href="#council-deliberations"></a></h5>
+    <p>Once <a data-link-type="dfn" href="#convened" id="ref-for-convened②">convened</a>,
+	the Council <em class="rfc2119">may</em> conduct additional research or analysis,
+	or request additional information or interviews from anyone,
+	including the Team.</p>
+    <p id="broker-consensus"> The Council <em class="rfc2119">may</em> further attempt to broker consensus,
+	which, if successful, disposes the formal objection. </p>
+    <p>Otherwise,
+	after sufficient deliberation,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②①">W3C Council</a> decides whether to <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="uphold | upholds | upheld | upholding" data-noexport id="uphold">uphold</dfn> or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="overrule">overrule</dfn> the objection.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②②">W3C Council</a> <em class="rfc2119">may</em> <a data-link-type="dfn" href="#overrule" id="ref-for-overrule">overrule</a> the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑤">Formal Objection</a> even if it agrees with some of the supportive arguments.</p>
+    <p id="fo-mitigations"> When <a data-link-type="dfn" href="#uphold" id="ref-for-uphold">upholding</a> an objection,
+	it <em class="rfc2199">should</em> recommend a way forward.
+	If the overturned decision has already had consequences
+	(e.g., if the objection concerns material already in a published document)
+	the Council <em class="rfc2119">should</em> suggest how these consequences might be mitigated.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦④">Team</a> is responsible for making sure that adequate mitigations are enacted in a timely fashion;
+	and the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑥">Formal Objection</a> is not considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fully-addressed">fully addressed</dfn> until then. </p>
+    <p class="note" role="note"><span class="marker">Note:</span> This does not create new powers for the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑤">Team</a>,
+	such as the ability to “unpublish” documents.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑥">Team</a>’s role is to ensure the responsible parties enact adequate mitigations,
+	by whatever means they already have at their disposal.</p>
+    <p>A Council <em class="rfc2119">may</em> form sub-groups for deliberation,
+	who may return with a recommendation,
+	but the full Council issues the final decision.
+	The decision of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②③">W3C Council</a> <em class="rfc2119">should</em> be unanimous,
+	and <em class="rfc2119">may</em> be issued under consensus.
+	However, if despite careful deliberation
+	a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②④">W3C Council</a> is unable to reach consensus,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair④">W3C Council Chair</a> may instead resort to voting.
+	In that case,
+	the decision is adopted if there are more ballots for than against;
+	in case of a tie,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑤">W3C Council Chair</a> determines the outcome.
+	However,
+	if the decision or proposal being objected to
+	originated with the TAG or AB,
+	then members of that group at the time the decision or proposal was made
+	must abstain in such a vote.
+	In case of a vote,
+	if two members of a Council who share the same affiliation cast an identical ballot,
+	then their ballots count as a one vote,
+	not two.</p>
+    <p>In the case of non-unanimous decisions,
+	members of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑤">W3C Council</a> who disagree with the decision <em class="rfc2119">may</em> write a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minority-opinion">Minority Opinion</dfn> explaining the reason for their disagreement.</p>
+    <p>The deliberations of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑥">W3C Council</a> are confidential to that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑦">W3C Council</a> and its <a data-link-type="dfn" href="#council-team-contact" id="ref-for-council-team-contact①">Council Team Contact</a>.</p>
+    <p id="45-day-update"> If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑧">W3C Council</a> is unable to come to a conclusion within 45 days of being <a data-link-type="dfn" href="#convened" id="ref-for-convened③">convened</a>,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑥">W3C Council Chair</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑤">AC</a> of this delay
+	and of the status of the discussions.
+	The <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑦">W3C Council Chair</a> <em class="rfc2119">may</em> additionally make this report <a href="#confidentiality-levels">public</a>. </p>
+    <h5 class="heading settled" data-level="5.6.2.8" id="council-decision"><span class="secno">5.6.2.8. </span><span class="content"> Council Decision Report</span><a class="self-link" href="#council-decision"></a></h5>
+    <p>A <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑨">Council</a> terminates by issuing a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-report">Council Report</dfn>,
+	which:</p>
+    <ul>
+     <li data-md>
+      <p><em class="rfc2119">must</em> state whether the Council <a data-link-type="dfn" href="#uphold" id="ref-for-uphold①">upholds</a> or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule①">overrules</a> the objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> provide a rationale supporting the decision,
+which <em class="rfc2119">should</em> address each argument raised in the Formal Objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include any recommendation decided by the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⓪">Council</a>.</p>
+     <li data-md>
+      <p>if the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑦">Formal Objection</a> has been upheld, <em class="rfc2119">should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include the <a data-link-type="dfn" href="#minority-opinion" id="ref-for-minority-opinion">Minority Opinion(s)</a>, if any.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of those who were <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed⑤">dismissed</a> or <a data-link-type="dfn" href="#renounce" id="ref-for-renounce③">renounced</a> their seat as well as those who were qualified to serve.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of the individuals who participated in the final decision.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the number of votes for/against dismissing each participant.</p>
+     <li data-md>
+      <p><em class="rfc2119">may</em> report vote totals for the Council’s decision, if a formal vote was held.</p>
+     <li data-md>
+      <p><em class="rfc2119">must not</em> attribute any position to any individual on the Council.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑦">Team</a> <em class="rfc2119">must</em> maintain a <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/about/council/">public page on the W3C website</a> indexing all completed <a data-link-type="dfn" href="#council-report" id="ref-for-council-report">Council Reports</a>.
+	If a Council decision is later overturned by an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal">AC Appeal</a>,
+	this <em class="rfc2119">must</em> also be mentioned. <a data-link-type="dfn" href="#council-report" id="ref-for-council-report①">Council Reports</a> <em class="rfc2119">must</em> be no more confidential
+	than the decision or document being objected to.</p>
+    <p>The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③①">Council</a> <em class="rfc2119">may</em> also issue a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="supplemental-confidential-council-report">Supplemental Confidential Council Report</dfn> with a more restricted <a href="#confidentiality-levels">level of confidentiality</a> than its main report
+	when it believes that additional commentary on confidential aspects of the case
+	would be informative.
+	However, the main <a data-link-type="dfn" href="#council-report" id="ref-for-council-report②">Council Report</a> <em class="rfc2119">should</em> be self-sufficient
+	and understandable without reference to Supplemental Confidential Council Reports.</p>
+    <h5 class="heading settled" data-level="5.6.2.9" id="council-appeals"><span class="secno">5.6.2.9. </span><span class="content"> Appealing Council Decisions</span><a class="self-link" href="#council-appeals"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑦">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①">Advisory Committee Appeal</a> of a Council decision issued in a <a data-link-type="dfn" href="#council-report" id="ref-for-council-report③">Council Report</a>.</p>
+    <h3 class="heading settled" data-level="5.7" id="ACReview"><span class="secno">5.7. </span><span class="content"> Advisory Committee Reviews and W3C Decisions</span><a class="self-link" href="#ACReview"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑥">Advisory Committee</a> formally confers its approval
+	on <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑤">charters</a>, <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③">technical reports</a>,
+	and other matters
+	through an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee review | AC Review" id="advisory-committee-review">Advisory Committee review</dfn> and its resulting <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑥">W3C Decision</a>.</p>
+    <h4 class="heading settled" data-level="5.7.1" id="ACReviewStart"><span class="secno">5.7.1. </span><span class="content"> Initiating an Advisory Committee Review</span><a class="self-link" href="#ACReviewStart"></a></h4>
+    <p>Each <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①③">Advisory Committee review</a> period
+	begins with a Call for Review from the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑧">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑦">Advisory Committee</a>.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="reviewform">Call for Review</dfn> describes the proposal,
+	raises attention to deadlines,
+	estimates when the decision will be available,
+	and includes other practical information.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑨">Team</a> <em class="rfc2119">may</em> share its perspective on the proposal
+	in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform">Call for Review</a>.
+	Each Member organization <em class="rfc2119">may</em> send one review,
+	which <em class="rfc2119">must</em> be returned by its <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑧">Advisory Committee representative</a>.</p>
+    <p>For clarity,
+	in the context of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①④">AC Review</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent②">dissent</a> <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑧">Formal Objection</a>.</p>
+    <p>The Team <em class="rfc2119">must</em> provide two channels for Advisory Committee review comments:</p>
+    <ol>
+     <li> an archived <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑥">Team-only</a> channel; 
+     <li> an archived <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only②">Member-only</a> channel. 
+    </ol>
+    <p>The <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform①">Call for Review</a> <em class="rfc2119">must</em> specify
+	which channel is the default for review comments on that Call.</p>
+    <p>Reviewers <em class="rfc2119">may</em> send information
+	to either or both channels.
+	A reviewer <em class="rfc2119">may</em> also share their own reviews
+	with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>,
+	and <em class="rfc2119">may</em> also make it available to the public.</p>
+    <p>A Member organization <em class="rfc2119">may</em> modify its review
+	during a review period
+	(e.g., in light of comments from other Members).</p>
+    <h4 class="heading settled" data-level="5.7.2" id="ACReviewAfter"><span class="secno">5.7.2. </span><span class="content"> Determining the W3C Decision</span><a class="self-link" href="#ACReviewAfter"></a></h4>
+    <p>After the review period,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⓪">Team</a> determines the appropriate <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑦">W3C Decision</a>,
+	which they <em class="rfc2119">must</em> announce to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑧">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate
+	the level of support for the proposal
+	(<a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⓪">consensus</a> or <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent③">dissent</a>),
+	and specifically
+	whether there were any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑨">Formal Objections</a>,
+	with attention to <a href="#confidentiality-change">changing the confidentiality level</a> of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⓪">Formal Objections</a>.</p>
+    <p>If there were <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③①">Formal Objections</a>, at least some of which were <a data-link-type="dfn" href="#uphold" id="ref-for-uphold②">upheld</a>,
+	or if there is not <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①①">consensus</a> because of insufficient support, <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑧">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to improve the proposal. 
+     <li> The proposal is rejected. 
+    </ul>
+    <p>If the proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①②">consensus</a>,
+	or if any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③②">Formal Objections</a> are retracted or overruled
+	and the proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①③">consensus</a>,
+	this <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑨">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is adopted,
+			possibly with additional changes integrated
+			in order to address the comments of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑨">AC</a> (see below). 
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to make desirable changes identified during the review
+			and to resubmit. 
+    </ul>
+    <p>If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>,
+	then those changes <em class="rfc2119">must</em> be announced to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⓪">AC</a> and to the <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group③">Group</a> that owns the document (if any).
+	Additionally, when adopting a proposal with <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①">substantive changes</a> integrated,
+	the announcement <em class="rfc2119">must</em> include rationale
+	for the substantive changes.</p>
+    <p><a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change②">Substantive changes</a> to the proposal <em class="rfc2119">may</em> be adopted
+	only if the revised proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①④">consensus</a> of the subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②①">AC</a> that voted on the initial proposal
+	(including anyone who explicitly abstained),
+	or if any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③③">Formal Objections</a> against the revised proposal are retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule②">overruled</a> and the revised proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑤">consensus</a>.
+	For clarity,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧①">Team</a> <em class="rfc2119">should</em> seek a response from this subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②②">AC</a> using the same tooling and degree of formality as it did for the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑤">AC Review</a>;
+	and as is the case during <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑥">AC Reviews</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent④">dissent</a> in this context <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③④">Formal Objection</a>.</p>
+    <p>Any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑤">Formal Objection</a> raised at this stage against the revised proposal
+	is handled by the same <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③②">Council</a> responsible for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑥">Formal Objections</a> raised against the initial proposal,
+	if any.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Such a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③③">Council</a> has the ability to
+	clear either the original or the revised proposal for advancement
+	by <a data-link-type="dfn" href="#overrule" id="ref-for-overrule③">overruling</a> all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑦">Formal Objections</a> against the original or revised proposal,
+	respectively.</p>
+    <p>For publications which have conditions in addition to <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②③">AC</a> approval
+	for introducing <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change③">substantive changes</a> (such as <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group④">Group</a> consensus or implementation experience
+	or going through a patent <a data-link-type="dfn" href="https://www.w3.org/policies/patent-policy/#exclusion-opportunity" id="ref-for-exclusion-opportunity">Exclusion Opportunity</a>),
+	those other conditions must also be re-fulfilled.</p>
+    <div class="example" id="example-2c1b534e"><a class="self-link" href="#example-2c1b534e"></a> For example, if <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change④">substantive changes</a> to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④">technical report</a> are requested when assessing the transition from <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR">Candidate Recommendation</a> to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①">Recommendation</a>,
+		the technical report would need to go through a new <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests">Update Request</a> and be republished as a new <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①">Candidate Recommendation</a>;
+		that new version would then need to satisfy the criteria for advancement.
+		Alternatively, the desired changes can be introduced as non-substantive amendments
+		using the process for <a href="#revising-rec">revising a Recommendation</a>.
+		However, with the exception of the removal of at-risk features,
+		they cannot be directly integrated between <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot">CRS</a> and <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②">REC</a>,
+		because that would fail to trigger a patent exclusion opportunity. </div>
+    <p>For <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑥">charters</a>,
+	substantive changes from the initial proposal that underwent <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑦">AC Review</a> <em class="rfc2119">must not</em> include any increase to the scope.
+	If any such change is desired,
+	it <em class="rfc2119">must</em> be returned for additional work
+	and go through a complete new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑧">AC Review</a>.</p>
+    <p>This document does not specify
+	time intervals between the end of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑨">Advisory Committee review</a> period
+	and the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⓪">W3C decision</a>.
+	This is to ensure that the Members and <a data-link-type="dfn" href="#team" id="ref-for-team⑧②">Team</a> have sufficient time to consider comments
+	gathered during the review.
+	The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②④">Advisory Committee</a> <em class="rfc2119">should not</em> expect an announcement
+	sooner than <span class="time-interval">two weeks</span> after the end of a review period.
+	If, after <span class="time-interval">three weeks</span>, the outcome has not been announced,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧③">Team</a> <em class="rfc2119">should</em> provide the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑤">Advisory Committee</a> with an update.</p>
+    <h3 class="heading settled" data-level="5.8" id="ACVotes"><span class="secno">5.8. </span><span class="content"> Advisory Committee Votes</span><a class="self-link" href="#ACVotes"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑥">Advisory Committee</a> votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>,
+	and in the event of an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal②">Advisory Committee Appeal</a> achieving the required support to trigger an <a data-link-type="dfn" href="#appeal-vote" id="ref-for-appeal-vote①">appeal vote</a>.
+	Whenever the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑦">Advisory Committee</a> votes,
+	each Member or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member④">related Members</a> has one vote.</p>
+    <h3 class="heading settled" data-level="5.9" id="ACAppeal"><span class="secno">5.9. </span><span class="content"> Appeal by Advisory Committee Representatives</span><a class="self-link" href="#ACAppeal"></a></h3>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑨">Advisory Committee representatives</a> <em class="rfc2119">may</em> appeal certain decisions,
+	though appeals are only expected to occur in extraordinary circumstances.
+	For the purpose of this section, only <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⓪">Advisory Committee representatives</a> of <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member④">Members</a> in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing①">Good Standing</a> are counted.</p>
+    <p>When a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①①">W3C decision</a> is made following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⓪">Advisory Committee review</a>, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②①">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee Appeal|AC Appeal| Appeal" id="advisory-committee-appeal">Advisory Committee Appeal</dfn>.
+	These <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①②">W3C decisions</a> include those related to group creation and modification,
+	and transitions to new maturity stages for Recommendation Track documents
+	and the Process document.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②②">Advisory Committee representatives</a> <em class="rfc2119">may</em> also initiate an appeal
+	for decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③④">W3C Council</a>, and
+	for certain decisions that do not involve an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②①">Advisory Committee review</a>.
+	These cases are identified in the sections
+	which describe the requirements for the decision
+	and include
+	additional (non-reviewed) maturity stages of Recommendation Track documents,
+	group <a data-link-type="dfn" href="#dfn-charter-extension" id="ref-for-dfn-charter-extension">charter extensions</a> and closures,
+	and <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement">technical agreements</a>.</p>
+    <p>In all cases,
+	an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal③">appeal</a> <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the decision.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②③">Advisory Committee representative</a> initiates an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal④">appeal</a> by sending a request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑧④">Team</a>,
+	and should also share this request with the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑧">Advisory Committee</a>.
+	The request should say “I appeal this Decision”
+	and identify the decision,
+	and may also include their rationale for appealing the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a> for a recommendation
+	on how to communicate an appeal request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑤">Team</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑨">AC</a>.</p>
+    <p>Within one week the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑥">Team</a> <em class="rfc2119">must</em> announce the appeal process
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⓪">Advisory Committee</a> and provide a mechanism for <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②④">Advisory Committee representatives</a> to respond with a statement of positive support for this appeal.
+	The archive of these statements <em class="rfc2119">must</em> be <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only③">member-only</a>.
+	If, within <span class="time-interval">one week</span> of the Team’s announcement,
+	5% or more of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③①">Advisory Committee</a> support the appeal request,
+	the Team <em class="rfc2119">must</em> organize an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="appeal-vote">appeal vote</dfn> asking the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③②">Advisory Committee</a> “Do you approve of the Decision?”
+	together with links to the decision and the appeal support.</p>
+    <p>The ballot <em class="rfc2119">must</em> allow for three possible responses:
+	“Approve”,
+	“Reject”,
+	and “Abstain”,
+	together with Comments.</p>
+    <p>The level of support needed for an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑤">Advisory Committee Appeal</a> to pass
+	depends on the level of ballot participation 
+	(including explicit “abstain” ballots) 
+	by <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑤">Advisory Committee Representatives</a>:</p>
+    <ul>
+     <li data-md>
+      <p>if fewer than 5% participate,
+the vote fails.</p>
+     <li data-md>
+      <p>if at least 5% but no more than 15% participate,
+and the number of “Approve” ballots exceeds three times (3x) the number of “Reject” ballots,
+the vote passes.</p>
+     <li data-md>
+      <p>if more than 15% but fewer than 20% participate,
+and the number of “Approve” ballots exceeds twice (2x) the number of “Reject” ballots,
+the vote passes.</p>
+     <li data-md>
+      <p>if 20% or more participate,
+and the number of “Approve” ballots exceeds the number of “Reject” ballots,
+the vote passes.</p>
+    </ul>
+    <p>If the vote passes,
+	the decision is overturned.
+	Following such rejection,
+	those who had initiated the proposal may revise it
+	to address the causes of rejection
+	and follow the ordinary applicable process
+	to submit the revised proposal.</p>
+    <h2 class="heading settled" data-level="6" id="Reports"><span class="secno">6. </span><span class="content"> W3C Technical Reports</span><a class="self-link" href="#Reports"></a></h2>
+    <p>The W3C technical report development process is the set of steps and requirements
+	followed by W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑤">Working Groups</a> to standardize Web technology.
+	The W3C technical report development process is designed to:</p>
+    <ul>
+     <li> support multiple specification development methodologies 
+     <li> maximize <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑥">consensus</a> about the content of stable technical reports 
+     <li> ensure high technical and editorial quality 
+     <li> promote consistency among specifications 
+     <li> facilitate royalty-free, interoperable implementations of Web Standards, and 
+     <li> earn endorsement by W3C and the broader community. 
+    </ul>
+    <p>See also “licensing goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.1" id="recs-and-notes"><span class="secno">6.1. </span><span class="content"> Types of Technical Reports</span><a class="self-link" href="#recs-and-notes"></a></h3>
+    <p>This chapter describes the formal requirements
+	for <a data-link-type="dfn" href="#publishing" id="ref-for-publishing">publishing</a> and maintaining a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③">W3C Recommendation</a>, <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑧">Note</a>,
+	or <a data-link-type="dfn" href="#registry" id="ref-for-registry">Registry</a>.</p>
+    <dl>
+     <dt>Recommendations 
+     <dd> <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑥">Working Groups</a> develop technical reports on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①">W3C Recommendation Track</a> in order to produce normative specifications or guidelines
+			as standards for the Web.
+			The <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track②">Recommendation Track</a> process incorporates requirements for <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review②">wide review</a>, <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation">adequate implementation experience</a>,
+			and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑦">consensus</a>-building,
+			and is subject to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			under which participants commit to Royalty-Free IPR licenses for implementations.
+			See <a href="#rec-track">§ 6.3 The W3C Recommendation Track</a> for details. 
+     <dt>Notes 
+     <dd> Groups can also publish documents as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①">W3C Notes</a> and <a data-link-type="dfn" href="#statement" id="ref-for-statement">W3C Statements</a>,
+			typically either to document information
+			other than technical specifications,
+			such as use cases motivating a specification
+			and best practices for its use.
+			See <a href="#note-track">§ 6.4 The Note Track (Notes and Statements)</a> for details. 
+     <dt>Registries 
+     <dd> <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group③">Chartered</a> and <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group">elected groups</a> can also publish <a data-link-type="dfn" href="#registry" id="ref-for-registry①">registries</a> in order to document collections of values or other data.
+			A registry can be published either as a distinct <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report">registry report</a>,
+			or directly within a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track③">Recommendation Track</a> document
+			as an <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry">embedded registry</a>. <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition">Defining a registry</a> requires <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review③">wide review</a> and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑧">consensus</a>,
+			but once set up, changes to registry entries are lightweight
+			and can even be done without the initiating group’s involvement.
+			See <a href="#registries">§ 6.5 The Registry Track</a> for details. 
+    </dl>
+    <p>Individual <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑦">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑨">Interest Groups</a> <em class="rfc2119">should</em> adopt additional processes
+	for developing publications,
+	so long as they do not conflict with the requirements in this chapter.</p>
+    <h3 class="heading settled" data-level="6.2" id="general-requirements"><span class="secno">6.2. </span><span class="content"> General Requirements for Technical Reports</span><a class="self-link" href="#general-requirements"></a></h3>
+    <h4 class="heading settled" data-level="6.2.1" id="publication"><span class="secno">6.2.1. </span><span class="content"> Publication of Technical Reports</span><a class="self-link" href="#publication"></a></h4>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="publish" data-noexport id="publishing">Publishing</dfn> as used in this document
+	refers to producing a version which is listed as a W3C <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="technical-report">Technical Report</dfn> on its <a href="https://www.w3.org/TR/">Technical Reports index at https://www.w3.org/TR</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a>.
+	Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public document.
+	W3C strives to make archival documents indefinitely available
+	at their original address in their original form.</p>
+    <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate its <a href="#maturity-stages">maturity stage</a>,
+	and <em class="rfc2119" id="DocumentStatus">must</em> include information about the status of the document.
+	This status information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> be unique each time a specification is <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①">published</a>, 
+     <li> <em class="rfc2119">must</em> state which <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑧">Working Group</a> developed the specification, 
+     <li> <em class="rfc2119">must</em> state how to send comments or file bugs,
+			and where these are recorded, 
+     <li> <em class="rfc2119">must</em> include expectations about next steps, 
+     <li> <em class="rfc2119">should</em> explain how the technology relates to existing international standards
+			and related work inside or outside W3C,
+			and 
+     <li> <em class="rfc2119">should</em> explain
+			or link to
+			an explanation of significant changes from the previous version. 
+    </ul>
+    <p>Every Technical Report published
+	as part of the Technical Report development process
+	is edited by one or more editors
+	appointed by a Group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③⓪">Chair</a>.
+	It is the responsibility of these editors to ensure that the decisions of the Group are
+	correctly reflected in subsequent drafts of the technical report.
+	An editor <em class="rfc2119">must</em> be a participant,
+	per <a href="#group-participation">§ 3.4.2 Participation in Chartered Groups</a> in the Group responsible for the document(s) they are editing.</p>
+    <p>The Team is <em class="rfc2119">not required</em> to publish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑤">Technical Report</a> that does not conform to the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules" title="Publication Rules">[PUBRULES]</a> (e.g., for <span id="DocumentName">naming</span>,
+	status information,
+	style,
+	and <span id="document-copyright">copyright requirements</span>).
+	These rules are subject to change by the Team from time to time.
+	The Team <em class="rfc2119">must</em> inform group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③①">Chairs</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③③">Advisory Committee</a> of any changes to these rules.</p>
+    <p>The primary language for W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑥">Technical Reports</a> is English.
+	W3C encourages the translation of its <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑦">Technical Reports</a>. <a href="https://www.w3.org/Consortium/Translation/">Information about translations of W3C technical reports</a> <a data-link-type="biblio" href="#biblio-translation" title="Translations of W3C technical reports">[TRANSLATION]</a> is available at the W3C website.</p>
+    <h4 class="heading settled" data-level="6.2.2" id="doc-reviews"><span class="secno">6.2.2. </span><span class="content"> Reviews and Review Responsibilities</span><a class="self-link" href="#doc-reviews"></a></h4>
+    <p>A document is available for review
+	from the moment it is first <a data-link-type="dfn" href="#publishing" id="ref-for-publishing②">published</a>.
+	Working Groups <em class="rfc2119">should</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed①">formally address</a> <em>any</em> substantive review comment
+	about a technical report in a timely manner.</p>
+    <p>Reviewers <em class="rfc2119">should</em> send substantive technical reviews as early as possible. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑨">Working Groups</a> are often reluctant to make <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑤">substantive changes</a> to a mature document,
+	particularly if this would cause significant compatibility problems
+	due to existing implementation. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⓪">Working Groups</a> <em class="rfc2119">should</em> record substantive
+	or interesting proposals raised by reviews
+	but not incorporated into a current specification.</p>
+    <h5 class="heading settled" data-level="6.2.2.1" id="wide-review"><span class="secno">6.2.2.1. </span><span class="content"> Wide Review</span><a class="self-link" href="#wide-review"></a></h5>
+    <p>The requirements for <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="dfn-wide-review">wide review</dfn> are not precisely defined by the W3C Process.
+	The objective is to ensure that the entire set of stakeholders of the Web community,
+	including the general public,
+	have had adequate notice of the progress of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②①">Working Group</a> and were able to actually perform reviews of and provide comments on the specification.
+	A second objective is to encourage groups to request reviews
+	early enough that comments and suggested changes
+	can still be reasonably incorporated in response to the review.
+	Before approving transitions,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑦">Team</a> will consider who has been explicitly offered
+	a reasonable opportunity to review the document,
+	who has provided comments,
+	the record of requests to and responses from reviewers,
+	especially <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a> and groups identified as dependencies in the charter
+	or identified as <a href="https://www.w3.org/liaisons/">liaisons</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a>,
+	and seek evidence of clear communication to the general public
+	about appropriate times and which content to review
+	and whether such reviews actually occurred.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The Team documents <a href="https://www.w3.org/guide/documentreview/">best practices for wide review</a> in the Guidebook. <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a></p>
+    <p>For example,
+	inviting review of new or significantly revised sections published in Working Drafts,
+	and tracking those comments
+	and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②②">Working Group</a>’s responses,
+	is generally a good practice which would often be considered positive evidence of wide review. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②③">Working Groups</a> <em class="rfc2119">should</em> follow the <a href="https://www.w3.org/guide/documentreview/#how-to-get-horizontal-review">W3C Horizontal Groups</a>’ review processes,
+	and <em class="rfc2119">should</em> announce to other W3C Working Groups
+	as well as the general public,
+	especially those affected by this specification,
+	a proposal to enter <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②">Candidate Recommendation</a> (for example in approximately 28 days).
+	By contrast a generic statement in a document
+	requesting review at any time
+	is likely not to be considered as sufficient evidence
+	that the group has solicited wide review.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②④">Working Group</a> could present evidence that wide review has been received,
+	irrespective of solicitation.
+	But it is important to note that receiving many detailed reviews
+	is not necessarily the same as wide review,
+	since they might only represent comment
+	from a small segment of the relevant stakeholder community.</p>
+    <h4 class="heading settled" data-level="6.2.3" id="correction-classes"><span class="secno">6.2.3. </span><span class="content"> Classes of Changes</span><a class="self-link" href="#correction-classes"></a></h4>
+    <p>This document distinguishes the following 5 classes of changes to a document.
+	The first two classes of change are considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="editorial change" data-noexport id="editorial-change">editorial changes</dfn>,
+	the next two <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="substantive change" data-noexport id="substantive-change">substantive changes</dfn>,
+	and the last one <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="registry change" data-noexport id="registry-change">registry changes</dfn>.</p>
+    <dl>
+     <dt id="class-1">
+      <a class="self-link" href="#class-1"></a> 
+      <ol>
+       <li data-md>
+        <p>No changes to text content</p>
+      </ol>
+     <dd> These changes include fixing broken links, style sheets, or invalid markup. 
+     <dt id="class-2">
+      <a class="self-link" href="#class-2"></a> 
+      <ol start="2">
+       <li data-md>
+        <p>Changes that do not functionally affect interpretation of the document</p>
+      </ol>
+     <dd> For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track④">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑧">technical reports</a> specifically,
+			this constitutes changes that do not affect conformance,
+			i.e. changes that reasonable implementers
+			would not interpret as changing architectural
+			or interoperability requirements
+			or their implementation.
+			Changes which resolve ambiguities in the specification
+			are considered to change (by clarification) the implementation requirements
+			and do not fall into this class. 
+     <dd> Examples of changes in this class include
+			correcting non-normative examples
+			which clearly conflict with normative requirements,
+			clarifying various other non-normative text,
+			fixing typos or grammatical errors
+			where the change does not change requirements. 
+     <dd> If there is any doubt or disagreement
+			as to whether a change functionally affects interpretation,
+			that change does not fall into this class. 
+     <dt id="class-3">
+      <a class="self-link" href="#class-3"></a> 
+      <ol start="3">
+       <li data-md>
+        <p>Other changes that do not add new features</p>
+      </ol>
+     <dd>
+       For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑤">Recommendation-track</a> documents,
+			these changes <em class="rfc2119">may</em> affect conformance to the specification.
+			A change that affects conformance is one that: 
+      <ul>
+       <li> makes conforming data, processors, or other conforming agents become non-conforming according to the new version,
+					or 
+       <li> makes non-conforming data, processors, or other agents become conforming,
+					or 
+       <li> clears up an ambiguity or under-specified part of the specification
+					in such a way that data,
+					a processor,
+					or an agent
+					whose conformance was once unclear
+					becomes clearly either conforming or non-conforming. 
+      </ul>
+     <dt id="class-4">
+      <a class="self-link" href="#class-4"></a> 
+      <ol start="4">
+       <li data-md>
+        <p>New features</p>
+      </ol>
+     <dd> Changes that add new functionality,
+			such as new elements, new APIs, new rules, etc. 
+     <dt id="class-5">
+      <a class="self-link" href="#class-5"></a> 
+      <ol start="5">
+       <li data-md>
+        <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table">registry table</a></p>
+      </ol>
+     <dd> Changes that add, remove, or alter <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry">registry entries</a> in a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①">registry table</a>. 
+    </dl>
+    <h4 class="heading settled" data-level="6.2.4" id="errata"><span class="secno">6.2.4. </span><span class="content"> Errata Management</span><a class="self-link" href="#errata"></a></h4>
+    <p>Tracking errors is an important part of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑤">Working Group</a>’s ongoing care of a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑨">technical report</a>;
+	for this reason,
+	the scope of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑥">Working Group</a> charter generally allows time
+	for work after publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④">Recommendation</a>.
+	In this Process Document,
+	the term “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="erratum | errata" id="erratum">erratum</dfn>”
+	(plural “errata”) refers to any error
+	that can be resolved by one or more changes in classes 1-3
+	of section <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑦">Working Groups</a> <em class="rfc2119">must</em> keep
+	a public record of errors
+	that are reported by readers and implementers
+	for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤">Recommendations</a>.
+	Such error reports <em class="rfc2119">should</em> be compiled
+	no less frequently than quarterly.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑧">Working Groups</a> decide how to document errata.
+	Such documentation <em class="rfc2119">must</em> identify
+	the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⓪">technical report</a> text
+	and describe the error;
+	it <em class="rfc2119">may</em> also describe some possible solution(s).
+	Readers of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①①">technical report</a> <em class="rfc2119">should</em> be able easily
+	to find and see the errata
+	that apply to that specific <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①②">technical report</a> with their associated tests.
+	Errata <em class="rfc2119">may</em> be documented
+	in a separate errata page or tracking system.
+	They <em class="rfc2119">may</em>,
+	in addition or alternatively,
+	be annotated inline
+	alongside the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①③">technical report</a> text
+	or at the start or end of the most relevant section(s).</p>
+    <h4 class="heading settled" data-level="6.2.5" id="candidate-amendments"><span class="secno">6.2.5. </span><span class="bs-old-id" id="candidate-changes"></span><span class="content"> Candidate Amendments</span><a class="self-link" href="#candidate-amendments"></a></h4>
+    <p>An <a data-link-type="dfn" href="#erratum" id="ref-for-erratum">erratum</a> <em class="rfc2119">may</em> be accompanied by a non-normative, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-correction">candidate correction</dfn> approved by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision②">group decision</a>.
+	When annotated inline,
+	errata—​including their <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction">candidate corrections</a>—​must be marked as such,
+	are treated as <a href="#correction-classes">class 2 changes</a>,
+	and are published accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Annotating changes in this way allows more mature documents
+	such as <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥">Recommendations</a> and <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR③">Candidate Recommendations</a> to be updated quickly with the Working Group’s most current thinking,
+	even when the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment">candidate amendments</a> have not yet received
+	sufficient review or implementation experience
+	to be normatively incorporated into the specification proper.</p>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-addition">candidate addition</dfn> is similar to a <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction①">candidate correction</a>,
+	except that it proposes a new feature
+	rather than an error correction.</p>
+    <p><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction②">Candidate corrections</a> and <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition">candidate additions</a> are collectively known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="candidate amendment" data-noexport id="candidate-amendment">candidate amendments</dfn>.</p>
+    <p>In addition to their actual <a href="#maturity-stages">maturity stage</a>, <a data-link-type="dfn" href="#publishing" id="ref-for-publishing③">published</a> <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑥">REC Track</a> documents with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①">candidate amendments</a> are also considered,
+	for the purpose of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	to be <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①">Working Drafts</a> with those <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment②">candidate amendments</a> treated as normative.</p>
+    <h4 class="heading settled" data-level="6.2.6" id="no-group-maintenance"><span class="secno">6.2.6. </span><span class="content"> Maintenance Without a Group</span><a class="self-link" href="#no-group-maintenance"></a></h4>
+    <p>For all <a href="#recs-and-notes">types of technical reports</a> and all <a href="#maturity-stages">maturity stages</a>,
+	if there is no <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group④">group</a> chartered to maintain a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①④">technical report</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑧">Team</a> <em class="rfc2119">may</em> republish it
+	at the same <a href="#maturity-stages">maturity stage</a>,
+	integrating as needed:</p>
+    <ol>
+     <li><a href="#correction-classes">class 1 changes</a>; 
+     <li>inline <a data-link-type="dfn" href="#erratum" id="ref-for-erratum①">errata</a>; 
+     <li><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction③">candidate corrections</a>,
+			which <em class="rfc2119">must</em> be marked as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="team-correction">Team correction</dfn>; 
+     <li><a href="#correction-classes">class 2 changes</a> other than inline <a data-link-type="dfn" href="#erratum" id="ref-for-erratum②">errata</a> and <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction">Team corrections</a>. 
+    </ol>
+    <p>To avoid any potential doubt or disagreement
+	about whether changes really do fall into <a href="#correction-classes">class 2</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑨">Team</a> <em class="rfc2119">should</em> be conservative,
+	limiting itself to obvious and limited fixes,
+	and <em class="rfc2119">must</em> avoid substantial rephrasing,
+	even of non-normative examples and notes.
+	If any such change is desired,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⓪">Team</a> <em class="rfc2119">must</em> mark it as a <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction①">Team correction</a>.</p>
+    <p><a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction②">Team corrections</a> do not constitute
+	a normative portion of the Recommendation,
+	as defined in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (i.e., they are not covered by the Patent Policy).
+	For <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR④">Candidate Recommendations</a>, <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦">W3C Recommendations</a>, <a data-link-type="dfn" href="#candidate-registry" id="ref-for-candidate-registry">Candidate Registries</a>, <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry">W3C Registries</a>,
+	as well as <a data-link-type="dfn" href="#statement" id="ref-for-statement①">W3C Statements</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨①">Team</a> <em class="rfc2119">must</em> solicit <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review④">wide review</a> on <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction③">Team corrections</a> that it produces.</p>
+    <h4 class="heading settled" data-level="6.2.7" id="contributor-license"><span class="secno">6.2.7. </span><span class="content"> License Grants from Non-Participants</span><a class="self-link" href="#contributor-license"></a></h4>
+    <p>When a party who is not already obligated under the Patent Policy
+	offers a change in class 3 or 4
+	(as described in <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>) to a technical report under this process
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨②">Team</a> <em class="rfc2119">must</em> request
+	a recorded royalty-free patent commitment;
+	for a change in class 4, the Team <em class="rfc2119">must</em> secure such commitment.
+	Such commitment <em class="rfc2119">should</em> cover,
+	at a minimum,
+	all the party’s Essential Claims both in the contribution,
+	and that become Essential Claims as a result of incorporating the contribution into the draft
+	that existed at the time of the contribution,
+	on the terms specified in the “W3C Royalty-Free (RF) Licensing Requirements” section of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.3" id="rec-track"><span class="secno">6.3. </span><span class="bs-old-id" id="rec-advance"></span><span class="content"> The W3C Recommendation Track</span><a class="self-link" href="#rec-track"></a></h3>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑨">Working Groups</a> create specifications and guidelines
+	to complete the scope of work envisioned by a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⓪">Working Group</a>’s <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑦">charter</a>.
+	These <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑤">technical reports</a> undergo cycles of revision and review
+	as they advance towards <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑧">W3C Recommendation</a> status.
+	Once review suggests the Working Group has met their requirements for a new standard,
+	including <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑤">wide review</a>,
+	a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑤">Candidate Recommendation</a> phase
+	allows the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③①">Working Group</a> to formally collect <a href="#implementation-experience">implementation experience</a> to demonstrate that the specification works in practice.
+	At the end of the process,
+	the Advisory Committee reviews the mature technical report,
+	and if there is support from its Membership,
+	W3C publishes it as a <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑤">Recommendation</a>.</p>
+    <p>In summary, the <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track" data-noexport id="w3c-recommendation-track">W3C Recommendation Track</dfn> consists of:</p>
+    <ol>
+     <li>Publication of the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd①">First Public Working Draft</a>. 
+     <li>Publication of zero or more revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD②">Working Drafts</a>. 
+     <li>Publication of one or more <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑥">Candidate Recommendations</a>. 
+     <li>Publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑨">W3C Recommendation</a>. 
+    </ol>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document" id="w3c-recommendation-track-document">W3C Recommendation Track document</dfn> is any document whose current status is one of the four in the numbered list above.</p>
+    <figure>
+     <svg viewBox="-5 30 457 175" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Basic W3C Recommendation Track</title>
+      <g role="list">
+       <g fill="#060" role="listitem">
+        <a href="#wd-1">
+         <rect fill="white" height="45" role="img" width="57" y="122">
+          <title>First Public Working Draft (FPWD) - Exclusion opportunity</title>
+         </rect>
+         <text font-size="8">
+          <tspan aria-hidden="true" x="0" y="132">First Public WD</tspan>
+          <tspan x="0" y="152">WG Decision +</tspan>
+          <tspan x="0" y="160">Team Approval</tspan>
+         </text>
+         <path d="M0,140h53" fill="none" stroke="#060"></path>
+         <polygon points="47,136 57,140 47,144"></polygon>
+        </a>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="97" cy="140" fill="#fff" id="wd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Working Draft (WD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="97" y="144">WD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Publish a new Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="97" y="100">WG Decision</tspan>
+           </text>
+           <path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114" fill="none" stroke="black" stroke-dasharray="6 2"></path>
+           <polygon points="120,114 116,124 114,113"></polygon>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Advance to Candidate Recommendation</title>
+           </g>
+           <text font-size="8" x="135" y="129">WG Decision +</text>
+           <text font-size="8" x="135" y="137">Team Approval</text>
+           <path d="M135,140h81" stroke="#060"></path>
+           <polygon points="211,136 221,140 211,144"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="260" cy="140" fill="#fff" id="cr-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="144">CRS</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="232" y="118">WG</tspan>
+            <tspan x="232" y="126">Decision</tspan>
+           </text>
+           <path d="M234,127v-34" stroke="#000"></path>
+           <polygon points="234,92 230,102 238,102"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="99">WG Decision</tspan>
+            <tspan x="290" y="107">Team Approval</tspan>
+           </text>
+           <path d="M242,124C238,114 244,104 260,104 271,104 285,108 286,117" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#rec-1">
+           <g role="img">
+            <title>Advance to Recommendation</title>
+           </g>
+           <text font-size="8" x="298" y="121">WG Decision +</text>
+           <text font-size="8" x="298" y="129">Team Approval +</text>
+           <text font-size="8" x="298" y="137">AC Review</text>
+           <path d="M298,140h77" stroke="#060"></path>
+           <polygon points="374,136 384,140 374,144"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="228" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="228" y="165">(or Team Decision with AB+TAG Approval)</tspan>
+           </text>
+           <path d="M140,147h84" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="140,145 133,147 140,149"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="260" cy="80" fill="#fff" id="crd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Draft (CRD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="84">CRD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="259" y="41">WG Decision</tspan>
+           </text>
+           <path d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="282,54 277,64 275,53"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="99">WG Decision +</tspan>
+            <tspan x="290" y="107">Team Approval</tspan>
+           </text>
+           <path d="M286,127v-34" stroke="#000"></path>
+           <polygon points="286,128 282,118 290,118"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="413" cy="140" fill="#fff" id="rec-1" role="img" rx="28" ry="18" stroke="black" stroke-width="2">
+          <title>Recommendation</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="413" y="144">REC</text>
+        </a>
+        <g role="list">
+         <g fill="#900" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Return to Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8" text-anchor="start">
+            <tspan x="342" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="342" y="165">(or Team Decision</tspan>
+            <tspan font-size="6" x="342" y="173">with AB+TAG</tspan>
+            <tspan font-size="6" x="342" y="181">Approval)</tspan>
+           </text>
+           <path d="M301,147h88" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="301,145 296,147 301,149"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="start">
+            <tspan x="342" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="342" y="165">(or Team Decision</tspan>
+            <tspan font-size="6" x="342" y="173">with AB+TAG</tspan>
+            <tspan font-size="6" x="342" y="181">Approval)</tspan>
+           </text>
+           <path d="M339,147v41h-242v-26" fill="none" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="95,164 97,159 99,164"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a fill="#000" href="#rec-1">
+           <g role="img">
+            <title>Publish revised Recommendation with editorial changes</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="413" y="103">WG Decision</tspan>
+            <tspan font-size="6" x="413" y="116">(editorial)</tspan>
+           </text>
+           <path d="M395,127C391,117 397,107 413,107 424,107 430,111 432,117" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="435,117 430,127 428,116"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a fill="#000" href="#rec-1">
+           <g role="img">
+            <title>Publish revised Recommendation with substantive changes</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="413" y="184">WG Decision +</tspan>
+            <tspan x="413" y="192">Team Approval +</tspan>
+            <tspan x="413" y="200">AC Review</tspan>
+            <tspan font-size="6" x="413" y="169">(substantive)</tspan>
+           </text>
+           <path d="M395,155C391,166 397,176 413,176 424,176 431,173 431,165" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="435,164 430,155 428,165"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+     <figcaption>Non-Normative Summary of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑦">Recommendation Track</a></figcaption>
+    </figure>
+    <p>This Process defines certain <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑧">Recommendation Track</a> publications as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="patent-review-drafts">Patent Review Drafts</dfn>.
+	Under the 2004 Patent Policy (and its 2017 update) <a data-link-type="biblio" href="#biblio-patent-policy-2004" title="The W3C 2004 Patent Policy, Updated 2017">[PATENT-POLICY-2004]</a>,
+	these correspond to “Last Call Working Draft” in the Patent Policy;
+	Starting from the 2020 Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy-2020" title="The W3C 2020 Patent Policy">[PATENT-POLICY-2020]</a>,
+	these correspond to “Patent Review Draft” in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.</p>
+    <p>As described in <a href="#transition-reqs">§ 6.3.3 Advancement on the Recommendation Track</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨③">Team</a> will decline a request to advance in maturity stage
+	and return the specification to a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③②">Working Group</a> for further work
+	if it determines that the requirements for advancement
+	have not been met.</p>
+    <h4 class="heading settled" data-level="6.3.1" id="maturity-stages"><span class="secno">6.3.1. </span><span class="content"> Maturity Stages on the Recommendation Track</span><a class="self-link" href="#maturity-stages"></a></h4>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Working Draft | Working Draft | WD" id="RecsWD">Working Draft</dfn> (<abbr>WD</abbr>) 
+     <dd>
+       A Working Draft is a document that W3C has <a data-link-type="dfn" href="#publishing" id="ref-for-publishing④">published</a> on the <a href="https://www.w3.org/TR/">W3C’s Technical Reports page</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a> for review by the community (including W3C Members), the public,
+			and other technical organizations,
+			and for simple historical reference.
+			Some, but not all, Working Drafts are meant to advance to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⓪">Recommendation</a>;
+			see the <a href="#DocumentStatus">document status section</a> of a Working Draft
+			for the group’s expectations. <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD③">Working Drafts</a> do not necessarily represent a <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑨">consensus</a> of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③③">Working Group</a> with respect to their content,
+			and do not imply any endorsement by W3C
+			or its members beyond agreement to work on a general area of technology.
+			Nevertheless the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③④">Working Group</a> decided to adopt the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD④">Working Draft</a> as the basis for their work at the time of adoption.
+			A <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑤">Working Draft</a> is suitable for gathering <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑥">wide review</a> prior to advancing to the next stage of maturity. 
+      <p>For all Working Drafts a Working Group:</p>
+      <ul>
+       <li> <em class="rfc2119">should</em> document outstanding issues,
+					and parts of the document on which the Working Group does not have consensus,
+					and 
+       <li> <em class="rfc2119">may</em> request publication of a Working Draft
+					even if its content is considered unstable
+					and does not meet all Working Group requirements. 
+      </ul>
+      <p>The first Working Draft of a technical report is called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="fpwd">First Public Working Draft</dfn> (<abbr>FPWD</abbr>),
+			and has patent implications as defined in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Candidate Recommendation | Candidate Recommendation | CR" id="RecsCR">Candidate Recommendation</dfn> (<abbr>CR</abbr>) 
+     <dd>
+       A Candidate Recommendation is a document that satisfies the technical
+			requirements of the Working Group that produced it and their dependencies,
+			and has already received wide review.
+			W3C publishes a Candidate Recommendation to 
+      <ul>
+       <li> signal to the wider community that it is time to do a final review 
+       <li> gather <a href="#implementation-experience">implementation experience</a> 
+      </ul>
+      <p class="note" role="note"><span class="marker">Note:</span> Advancing to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑦">Candidate Recommendation</a> indicates
+			that the document is considered complete and fit for purpose,
+			and that no further refinement to the text is expected
+			without additional implementation experience and testing;
+			however, additional features might be expected in a later revision.
+			A <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑧">Candidate Recommendation</a> is expected to be as well-written,
+			detailed,
+			self-consistent,
+			and technically complete
+			as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①①">Recommendation</a>,
+			and acceptable as such
+			if and when the requirements for further advancement are met.</p>
+      <p>Candidate Recommendation publications take one of two forms:</p>
+      <dl>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Snapshot | CRS" id="candidate-recommendation-snapshot">Candidate Recommendation Snapshot</dfn> (<abbr>CRS</abbr>) 
+       <dd>
+         A Candidate Recommendation Snapshot
+					corresponds to a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts">Patent Review Draft</a> as used in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+					Publishing a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts①">Patent Review Draft</a> triggers a Call for Exclusions,
+					per “Exclusion From W3C RF Licensing Requirements”
+					in the W3C Patent Policy. 
+        <p>Publication as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①">Candidate Recommendation Snapshot</a> requires verification of either a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req">Transition Request</a> (for the first <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑨">Candidate Recommendation</a> publication from another maturity stage)
+					or an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①">Update Request</a> (for subsequent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot②">Candidate Recommendation Snapshots</a>).</p>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Draft | CRD" id="candidate-recommendation-draft">Candidate Recommendation Draft</dfn> (<abbr>CRD</abbr>) 
+       <dd>
+         A Candidate Recommendation Draft
+					is published
+					to solicit review of intended changes from the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot③">Candidate Recommendation Snapshot</a>.
+					This allows for wider review of the changes
+					and for ease of reference to the integrated specification. 
+        <p>Any changes published directly into a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft">Candidate Recommendation Draft</a> should be at the same level of quality as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot④">Candidate Recommendation Snapshot</a>.
+					However, the process requirements are minimized
+					so that the Working Group can easily keep the specification up to date.</p>
+        <p>A <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft①">Candidate Recommendation Draft</a> <em>does not</em> provide an exclusion opportunity;
+					instead, it is considered a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑥">Working Draft</a> for the purpose of the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+      </dl>
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rescinded-candidate-recommendation">Rescinded Candidate Recommendation</dfn> is a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⓪">Candidate Recommendation</a> in which significant problems have been discovered
+			such that W3C cannot endorse it or continue work on it,
+			for example due to burdensome patent claims that affect implementers and cannot be resolved
+			(see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “PAG Conclusion”).
+			There is no path to restoration for a <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a>.
+			See “W3C Royalty-Free (RF) Licensing Requirements”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for implication on patent licensing obligations.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation | Recommendation | REC" id="RecsW3C">W3C Recommendation</dfn> (<abbr>REC</abbr>) 
+     <dd>
+       A W3C Recommendation is a specification
+			or set of guidelines
+			or requirements that,
+			after extensive <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②⓪">consensus</a>-building,
+			has received the endorsement of W3C and its Members.
+			W3C recommends the wide deployment
+			of its Recommendations as standards for the Web.
+			The W3C Royalty-Free IPR licenses
+			granted under the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> apply to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①②">W3C Recommendations</a>. 
+      <p id="expandable-rec"> After its initial publication,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①③">W3C Recommendation</a> <em class="rfc2119">may</em> be revised
+			(in accordance with <a href="#revising-rec">§ 6.3.10 Revising a W3C Recommendation</a>)
+			to address <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①">editorial</a> or <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑥">substantive</a> issues
+			that are discovered later.
+			However, <a href="#class-4">new features</a> can only be added
+			if the document already identifies itself
+			as intending to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="allow-new-features">allow new features</dfn>.
+			Such an allowance cannot be added
+			to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑥">technical report</a> previously published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①④">Recommendation</a> that did not allow such changes;
+			this requires a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑦">technical report</a> (which could, for example, be similarly named but with an incremented version number). </p>
+      <p>As technology evolves,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑤">W3C Recommendation</a> may become:</p>
+      <dl>
+       <dt> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsSup">Superseded Recommendation</dfn> 
+       <dd>
+         A Superseded Recommendation is a specification
+					that has been replaced by a newer version
+					that W3C recommends for new adoption.
+					An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs">Obsolete</a> or Superseded specification
+					has the same status as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑥">W3C Recommendation</a> with regards to W3C Royalty-Free IPR Licenses granted under the Patent Policy. 
+        <p class="note" role="note"><span class="marker">Note:</span> When a Technical Report which had previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑦">Recommendation</a> is again published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑧">Recommendation</a> after following the necessary steps to <a href="#revising-rec">revise</a> it,
+					the latest version replaces the previous one,
+					without the need to invoke the steps of <a href="#rec-rescind">§ 6.3.12.3 Abandoning a W3C Recommendation</a>:
+					it is the same document, updated.
+					Explicitly declaring a documented superseded, using the process documented in <a href="#rec-rescind">§ 6.3.12.3 Abandoning a W3C Recommendation</a>,
+					is intended for cases where a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑨">Recommendation</a> is superseded by a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑧">Technical Report</a> (or by a document managed outside of W3C).</p>
+       <dt> An <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsObs">Obsolete Recommendation</dfn> 
+       <dd> An Obsolete Recommendation is a specification
+					that W3C has determined lacks sufficient market relevance
+					to continue recommending it for implementation,
+					but which does not have fundamental problems
+					that would require it to be <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec">Rescinded</a>.
+					If an Obsolete specification gains sufficient market relevance,
+					W3C may decide to restore it to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⓪">Recommendation</a> status. 
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RescindedRec">Rescinded Recommendation</dfn> 
+       <dd> A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses,
+					and believes is unlikely to ever be restored to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②①">Recommendation</a> status.
+					See also “W3C Royalty-Free (RF) Licensing Requirements”
+					in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+      </dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="discontinuedREC">Discontinued Draft</dfn> 
+     <dd> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑨">technical report</a> representing the state of a Recommendation-track document
+			at the point at which work on it was discontinued.
+			See <a href="#abandon-draft">§ 6.3.12.1 Abandoning an Unfinished Recommendation</a>. 
+    </dl>
+    <p>Only sufficiently technically mature work should be advanced.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Should faster advancement to meet scheduling considerations be desired,
+	this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring
+	less stable features to other technical reports.</p>
+    <p>When publishing an updated version of an existing <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①①">Candidate Recommendation</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②②">Recommendation</a>,
+	technical reports are expected to meet the same maturity criteria as when they are first published under that status.
+	However, in the interest of replacing stale documents with improved ones in a timely manner,
+	if flaws have been discovered in the technical report after its initial publication as a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①②">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②③">REC</a> that would have been severe enough to reject that publication had they be known in time,
+	it is also permissible to publish an updated <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①③">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②④">REC</a> following the usual process,
+	even if only some of these flaws have been satisfactorily addressed.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑤">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①⓪">Interest Groups</a> <em class="rfc2119">may</em> make available <a data-link-type="dfn" href="#editors-draft" id="ref-for-editors-draft">Editor’s drafts</a>. <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Editor&apos;s Draft | Editor Draft | ED" id="editors-draft">Editor’s drafts</dfn> (<abbr>ED</abbr>) have no official standing whatsoever,
+	and do not necessarily imply consensus of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑥">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①①">Interest Group</a>,
+	nor are their contents endorsed in any way by W3C.</p>
+    <h4 class="heading settled" data-level="6.3.2" id="implementation-experience"><span class="secno">6.3.2. </span><span class="content"> Implementation Experience</span><a class="self-link" href="#implementation-experience"></a></h4>
+    <p>Implementation experience is required to show that a specification is sufficiently clear,
+	complete,
+	and relevant to market needs,
+	to ensure that independent interoperable implementations
+	of each feature of the specification will be realized.
+	While no exhaustive list of requirements is provided here,
+	when assessing that there is <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="adequate-implementation">adequate implementation experience</dfn> the <a data-link-type="dfn" href="#team" id="ref-for-team⑨④">Team</a> will consider (though not be limited to):</p>
+    <ul>
+     <li> is each feature of the current specification implemented,
+			and how is this demonstrated? 
+     <li> are there independent interoperable implementations of the current specification? 
+     <li> are there implementations created by people other than the authors of the specification? 
+     <li> are implementations publicly deployed? 
+     <li> is there implementation experience
+			at all levels of the specification’s ecosystem
+			(authoring, consuming, publishing…)? 
+     <li> are there reports of difficulties or problems with implementation? 
+    </ul>
+    <p>Planning and accomplishing a demonstration of (interoperable) implementations can be very time consuming.
+	Groups are often able to work more effectively
+	if they plan how they will demonstrate interoperable implementations
+	early in the development process;
+	for example, developing tests in concert with implementation efforts.</p>
+    <h4 class="heading settled" data-level="6.3.3" id="transition-reqs"><span class="secno">6.3.3. </span><span class="content"> Advancement on the Recommendation Track</span><a class="self-link" href="#transition-reqs"></a></h4>
+    <p>For <em>all</em> requests to advance a specification
+	to a new maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="trans-req">Transition Requests</dfn>),
+	the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request advancement. 
+     <li id="adv-verif-reqs"><a class="self-link" href="#adv-verif-reqs"></a> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑤">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑥">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑨">Team decision</a>) <em class="rfc2119">must</em> be withheld if any Process requirements are not met
+			or if there remain any unresolved Formal Objections
+			(including any <a data-link-type="dfn" href="#uphold" id="ref-for-uphold③">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑤">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed">fully addressed</a>),
+			or if the document does not adequately reflect all relevant decisions of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑥">W3C Council</a> (or its delegates).
+			If the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑦">Team</a> rejects a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req①">Transition Request</a> it <em class="rfc2119">must</em> indicate its rationale
+			to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③④">Advisory Committee</a> and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑦">Working Group</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change②">editorial changes</a> have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed②">formally address</a> all issues
+			raised about the document since the previous <a href="#maturity-stages">maturity stage</a>. 
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑧">Formal Objections</a>. 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑧">Working Group</a>’s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑨">Working Group</a>. 
+    </ul>
+    <p>For a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd②">First Public Working Draft</a> there is no “previous maturity stage”,
+	so many requirements do not apply,
+	and verification is normally fairly straightforward.
+	For later stages,
+	especially transitions to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①④">Candidate</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑤">Recommendation</a>,
+	there is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p><a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req②">Transition Requests</a> to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd③">First Public Working Draft</a> or <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑤">Candidate Recommendation</a> will not normally be approved
+	while a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⓪">Working Group</a>’s <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑧">charter</a> is undergoing or awaiting a decision
+	on an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②②">Advisory Committee Review</a>.</p>
+    <h4 class="heading settled" data-level="6.3.4" id="update-reqs"><span class="secno">6.3.4. </span><span class="content"> Updating Mature Publications on the Recommendation Track</span><a class="self-link" href="#update-reqs"></a></h4>
+    <p>Certain requests to re-publish a specification
+	within its current maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="update-requests">Update Requests</dfn>)
+	require extra verification.
+	For such <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests②">update requests</a>, the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request the update. 
+     <li> <em class="rfc2119">must</em> show that the changes have received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑦">wide review</a>. 
+     <li>
+       <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑧">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑨">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①⓪">Team decision</a>): 
+      <ul>
+       <li data-md>
+        <p><em class="rfc2119">should</em> be withheld
+if any Process requirements are not met,</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+in consideration of unresolved Formal Objections
+(including any <a data-link-type="dfn" href="#uphold" id="ref-for-uphold④">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑦">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed①">fully addressed</a>),</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+if the document does not adequately reflect
+all relevant decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑧">W3C Council</a> (or its delegates),</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+if the Team believes the Group is not making reasonable progress
+on addressing issues raised by individuals external to the Group.</p>
+      </ul>
+      <p>If the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⓪">Team</a> rejects an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests③">Update Request</a>,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④①">Working Group</a>.
+			If it waives any Process requirements,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑤">AC</a>.</p>
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑨">Formal Objections</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document of all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change③">editorial changes</a> changes have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> show that the revised specification
+			meets all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④②">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④③">Working Group</a>’s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④④">Working Group</a>. 
+    </ul>
+    <p>There is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests④">Update request</a> verification is expected to be fairly simple
+	compared to verification of a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req③">transition request</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪①">Team</a> <em class="rfc2119">must</em> announce the publication
+	of the revised specification
+	to other W3C groups and the Public.</p>
+    <h4 class="heading settled" data-level="6.3.5" id="first-wd"><span class="secno">6.3.5. </span><span class="content"> Publishing a First Public Working Draft</span><a class="self-link" href="#first-wd"></a></h4>
+    <p>To publish the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd④">First Public Working Draft</a> of a document,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑤">Working Group</a> <em class="rfc2119">must</em> meet the applicable <a href="#transition-reqs">requirements for advancement</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪②">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑤">First Public Working Draft</a> to other W3C groups and to the public.</p>
+    <h4 class="heading settled" data-level="6.3.6" id="revising-wd"><span class="secno">6.3.6. </span><span class="bs-old-id" id="revised-wd"></span><span class="content"> Revising a Working Draft</span><a class="self-link" href="#revising-wd"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑥">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑤">publish</a> a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑦">Working Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a Working draft, a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication. <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②①">Consensus</a> is not required,
+			as this is a procedural step, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑦">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑧">Working Draft</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change④">editorial changes</a> to the technical report
+			since the previous step, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups, 
+    </ul>
+    <p>Possible next steps for any Working Draft:</p>
+    <ul>
+     <li>Revised <a href="#revising-wd">Working Draft</a> 
+     <li><a href="#transition-cr">Candidate Recommendation</a> 
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.7" id="transition-cr"><span class="secno">6.3.7. </span><span class="bs-old-id" id="candidate-rec"></span><span class="content"> Transitioning to Candidate Recommendation</span><a class="self-link" href="#transition-cr"></a></h4>
+    <p>To publish a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑥">Candidate Recommendation</a>,
+	in addition to meeting the <a href="#transition-reqs">requirements for advancement</a> a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑦">Working Group</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> show that the specification
+			has met all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑧">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">must</em> document changes to dependencies during the development of the specification, 
+     <li> <em class="rfc2119">must</em> document
+			how <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation①">adequate implementation experience</a> will be demonstrated, 
+     <li> <em class="rfc2119">must</em> specify the deadline for comments,
+			delineating the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-recommendation-review-period">Candidate Recommendation review period</dfn>,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">must</em> show that the specification has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑧">wide review</a>, and 
+     <li> <em class="rfc2119">may</em> identify features in the document as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="at-risk">at risk</dfn>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑥">Recommendation</a> without requiring an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑤">Update Request</a>. 
+    </ul>
+    <p>The first Candidate Recommendation publication
+	after verification of having met the requirements for a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req④">Transition Request</a> is always a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑤">Candidate Recommendation Snapshot</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪③">Team</a> <em class="rfc2119">must</em> announce
+	the publication of the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑥">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑦">Candidate Recommendation Snapshot</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Recommendation</a>
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <p><a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑥">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 class="heading settled" data-level="6.3.8" id="revising-cr"><span class="secno">6.3.8. </span><span class="bs-old-id" id="revised-cr"></span><span class="content"> Revising a Candidate Recommendation</span><a class="self-link" href="#revising-cr"></a></h4>
+    <h5 class="heading settled" data-level="6.3.8.1" id="publishing-crrs"><span class="secno">6.3.8.1. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑧">Candidate Recommendation Snapshot</a></span><a class="self-link" href="#publishing-crrs"></a></h5>
+    <p>If there are any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑧">substantive changes</a> made to a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑦">Candidate Recommendation</a> since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑨">Candidate Recommendation Snapshot</a> other than to remove features explicitly identified as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk">at risk</a>,
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑨">Working Group</a> <em class="rfc2119">must</em> meet the requirements of an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑥">update request</a> in order to republish.</p>
+    <p>In addition the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> specify the deadline for further comments,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">may</em> identify features in the document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk①">at risk</a>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑦">Recommendation</a> without requiring an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑦">Update Request</a>. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪④">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a revised <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⓪">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>To provide timely updates and patent protection,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①①">Candidate Recommendation Snapshot</a> <em class="rfc2119">should</em> be published
+	within 24 months of the Working Group accepting
+	any proposal for a substantive change
+	(and preferably sooner).
+	To make scheduling reviews easier,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①②">Candidate Recommendation Snapshot</a> <em class="rfc2119">should not</em> be published
+	more often than approximately once every 6 months.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑨">Substantive changes</a> trigger a new Exclusion Opportunity
+	per “Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.8.2" id="publishing-crud"><span class="secno">6.3.8.2. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft②">Candidate Recommendation Draft</a></span><a class="self-link" href="#publishing-crud"></a></h5>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⓪">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑥">publish</a> an <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft③">Update Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft④">Candidate Recommendation Draft</a>,
+	a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①⓪">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①③">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑤">editorial changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①④">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> document outstanding issues,
+			and parts of the document on which the Working Group does not have consensus, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+    </ul>
+    <p class="note" role="note"><span class="marker">Note:</span> A Working Group <em>does not</em> need to
+	meet the requirements of a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑤">Candidate Recommendation Snapshot</a> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑧">update request</a> in order to publish a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑤">Candidate Recommendation Draft</a>.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑥">Candidate Recommendation Draft</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Recommendation</a>,
+		if there are no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①①">substantive change</a> other than dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk②">at risk</a> features
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.9" id="transition-rec"><span class="secno">6.3.9. </span><span class="bs-old-id" id="transition-pr"></span><span class="bs-old-id" id="rec-pr"></span><span class="bs-old-id" id="rec-publication"></span><span class="content"> Transitioning to Recommendation</span><a class="self-link" href="#transition-rec"></a></h4>
+    <p>When a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤①">Working Group</a> estimates
+	that a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑧">Candidate Recommendation</a> has fulfilled all the relevant criteria,
+	it <em class="rfc2119">may</em> <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision③">decide</a> to request advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑧">W3C Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.1" id="transition-rec-requirements"><span class="secno">6.3.9.1. </span><span class="content"> Requirements for Transition</span><a class="self-link" href="#transition-rec-requirements"></a></h5>
+    <p>In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,
+	the Working Group:</p>
+    <ul>
+     <li>
+       <em class="rfc2119">must</em> show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation②">adequate implementation experience</a> except where an exception is approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①①">Team Decision</a>. 
+      <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑤">Team</a> <em class="rfc2119">may</em> approve a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑨">Candidate Recommendation</a> with minimal <a href="#implementation-experience">implementation experience</a> where there is a compelling reason to do so.
+			In such a case, the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑥">Team</a> <em class="rfc2119">must</em> explain the reasons for that decision,
+			and that information <em class="rfc2119">must</em> be included in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform②">Call for Review</a> proposing advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑨">W3C Recommendation</a>.</p>
+     <li> <em class="rfc2119">must</em> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑨">wide review</a>. 
+     <li> <em class="rfc2119">must</em> show that all issues
+			raised during the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period">Candidate Recommendation review period</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed③">formally addressed</a>. 
+     <li> <em class="rfc2119">must </em>identify any substantive issues
+			raised since the close of the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period①">Candidate Recommendation review period</a>. 
+     <li> <em class="rfc2119">must</em> identify, in the document, where errata are tracked. 
+    </ul>
+    <p>Additionally,
+	if the document has previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⓪">W3C Recommendation</a>, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤②">Working Group</a> <em class="rfc2119">must not</em> include any <a href="#correction-classes">class 4 change</a> to that publication
+	unless it was explicitly marked as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features">allowing new features</a>,
+	and <em class="rfc2119">must not</em> include any such marking
+	if not already present.</p>
+    <h5 class="heading settled" data-level="6.3.9.2" id="initiating-rec-review"><span class="secno">6.3.9.2. </span><span class="content"> Initiating Review</span><a class="self-link" href="#initiating-rec-review"></a></h5>
+    <p>If all the criteria above are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑦">Team</a> <em class="rfc2119">must</em> begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②③">Advisory Committee Review</a> on the question of whether the identified <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑥">Candidate Recommendation Snapshot</a> is appropriate to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑦">publish</a> as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③①">W3C Recommendation</a>.
+	If the document’s most recent publication is not a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑦">Candidate Recommendation Snapshot</a>,
+	then it <em class="rfc2119">must</em> be republished as such in order to provide a basis for review.
+	The deadline for <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②④">Advisory Committee review</a> <em class="rfc2119">must</em> allow <strong>at least</strong> 28 days,
+	and <em class="rfc2119">must</em> end at least 10 days
+	after the end of the last Exclusion Opportunity
+	per ”Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.3" id="rec-review-resolution"><span class="secno">6.3.9.3. </span><span class="content"> Resolution of Review</span><a class="self-link" href="#rec-review-resolution"></a></h5>
+    <p>If there was any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④⓪">Formal Objection</a> during the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑤">Advisory Committee Review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑧">Team</a> <em class="rfc2119">must</em> publish the substantive content of the <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑤">dissent</a> to W3C and the general public,
+	and the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③②">W3C Recommendation</a> <em class="rfc2119">must not</em> be published
+	unless all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④①">Formal Objections</a> to the document have been retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule④">overruled</a> and at least 14 days have elapsed since the publication of the corresponding <a data-link-type="dfn" href="#council-report" id="ref-for-council-report④">Council Report</a>.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③③">Recommendation</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①③">W3C Decision</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑨">Team</a> <em class="rfc2119">must</em> announce the publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③④">W3C Recommendation</a> to the <a href="#AC">Advisory Committee</a>,
+	to other W3C groups
+	and to the public. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑥">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑥">Advisory Committee Appeal</a> of the decision to advance the technical report.</p>
+    <p>The newly published <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑤">Recommendation</a> <em class="rfc2119">must not</em> make any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①②">substantive changes</a> to the document
+	compared to the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑧">Candidate Recommendation Snapshot</a> submitted for AC Review,
+	other than dropping features identified <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk③">at risk</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.4" id="rec-next-steps"><span class="secno">6.3.9.4. </span><span class="content"> Next Steps from W3C Recommendation</span><a class="self-link" href="#rec-next-steps"></a></h5>
+    <p>Possible next steps:
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑥">W3C Recommendation</a> normally retains its status indefinitely.
+	However it <em class="rfc2119">may</em> be:</p>
+    <ul>
+     <li> republished as a <a href="#revising-rec">revised Recommendation</a>, or 
+     <li> republished as a <a href="#transition-cr">Candidate Recommendation</a> or <a href="#revising-wd">Working Draft</a> to be developed towards a revised <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑦">Recommendation</a>, or 
+     <li> declared <a href="#rec-rescind">superseded or obsolete</a>, or 
+     <li> <a href="#rec-rescind">rescinded</a>. 
+    </ul>
+    <h4 class="heading settled" data-level="6.3.10" id="revising-rec"><span class="secno">6.3.10. </span><span class="bs-old-id" id="revised-rec"></span><span class="bs-old-id" id="rec-modify"></span><span class="content"> Revising a W3C Recommendation</span><a class="self-link" href="#revising-rec"></a></h4>
+    <h5 class="heading settled" data-level="6.3.10.1" id="revised-rec-editorial"><span class="secno">6.3.10.1. </span><span class="bs-old-id" id="revised-rec-markup"></span><span class="content"> Revising a Recommendation: Editorial Changes</span><a class="self-link" href="#revised-rec-editorial"></a></h5>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑥">Editorial changes</a> to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑧">Recommendation</a> require no technical review of the intended changes.
+	A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤③">Working Group</a>,
+	provided there are no votes against the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision④">decision</a> to publish, <em class="rfc2119">may</em> request publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑨">Recommendation</a> to make this class of change without passing through earlier maturity stages.
+	(See <a href="#class-1">class 1</a> and <a href="#class-2">class 2 changes</a>.)</p>
+    <h5 class="heading settled" data-level="6.3.10.2" id="revised-rec-substantive"><span class="secno">6.3.10.2. </span><span class="content"> Revising a Recommendation: Substantive Changes</span><a class="self-link" href="#revised-rec-substantive"></a></h5>
+    <p>Tentative corrections (see <a href="#class-3">class 3 changes</a>) <em class="rfc2119">may</em> be annotated into a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⓪">Recommendation</a> using <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction④">candidate corrections</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑤">Candidate corrections</a> do not normatively modify the document;
+	they editorially indicate how one might do so.
+	They are therefore published following the provisions of <a href="#revised-rec-editorial">§ 6.3.10.1 Revising a Recommendation: Editorial Changes</a>.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑥">candidate correction</a> can be made normative
+	and be folded into the main text of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④①">Recommendation</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④②">Recommendation</a>,
+	including review by the community to ensure
+	its technical and editorial soundness.
+	To validate this, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤④">Working Group</a> must request
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review">Last Call for Review of Proposed Amendments</a>,
+	followed by an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑨">update request</a>.
+	See <a href="#change-review">§ 6.3.10.4 Incorporating Candidate Amendments</a>.</p>
+    <p>Alternatively,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑤">Working Group</a> <em class="rfc2119">may</em> incorporate the changes
+	and <a href="#revising-wd">publish as a Working Draft</a>—​or, if the relevant criteria are fulfilled, <a href="#transition-cr">publish as a Candidate Recommendation</a>—​and advance the specification from that state.
+	(See <a href="#correction-classes">class 3 changes</a>.)</p>
+    <h5 class="heading settled" data-level="6.3.10.3" id="revised-rec-features"><span class="secno">6.3.10.3. </span><span class="content"> Revising a Recommendation: New Features</span><a class="self-link" href="#revised-rec-features"></a></h5>
+    <p>For <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④③">Recommendations</a> explicitly identified as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features①">allowing new features</a>,
+	tentative new features (see <a href="#correction-classes">class 4 changes</a>) <em class="rfc2119">may</em> be added as <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition①">candidate additions</a> in annotations,
+	and <a href="#correction-classes">class 4 changes</a> may be normatively incorporated
+	in the same fashion as <a href="#correction-classes">class 3 changes</a> in <a href="#revised-rec-substantive">§ 6.3.10.2 Revising a Recommendation: Substantive Changes</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Limiting the addition of new features to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④④">Recommendations</a> that explicitly allow them
+	enables third parties to depend on a stable feature-set for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑤">Recommendations</a> that do not advertise that ability,
+	as was the case for all <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑥">Recommendations</a> prior to the 2020 revision of this Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> When a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑦">Recommendation</a> does not <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features②">allow new features</a>,
+	new features can be added by creating a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⓪">technical report</a> and following the full process of advancing that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②①">technical report</a> to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑧">Recommendation</a>—​beginning with a new <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑥">First Public Working Draft</a>.
+	Such <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②②">technical reports</a> could be written to represent
+	additional modules building on top of the original <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑨">Recommendation</a> of the core technology,
+	or an expanded replacement of the original <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⓪">Recommendation</a> of the core technology
+	(in which case the new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②③">technical report</a> will typically have the same name as the original,
+	with an incremented version number).</p>
+    <h5 class="heading settled" data-level="6.3.10.4" id="change-review"><span class="secno">6.3.10.4. </span><span class="content"> Incorporating Candidate Amendments</span><a class="self-link" href="#change-review"></a></h5>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-review">Last Call for Review of Proposed Amendments</dfn> verifies acceptance by the W3C community of <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment③">candidate amendments</a> by combining an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑥">AC Review</a> with a patent exclusion opportunity.</p>
+    <p>The <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review①">Last Call for Review of Proposed Amendments</a> must be announced to other W3C groups, the public, and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑦">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Identify whether this is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</dfn>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</dfn>,
+			or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</dfn>. 
+     <li> Identify the specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment④">candidate amendments</a> under review
+			as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-amendments">proposed amendments</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="proposed-corrections">proposed corrections</dfn>/<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="proposed-additions"><span class="bs-old-id" id="proposed-addition"></span>proposed additions</dfn>). 
+     <li> Specify the deadline for review comments,
+			which must not be any sooner than 60 days from the Call for Review. 
+     <li> Solicit review and, if it does not already have it, implementation experience. 
+    </ul>
+    <p>The combination of the existing <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤①">Recommendation</a> with the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments">proposed amendments</a> included in the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review②">Last Call for Review of Proposed Amendments</a> is considered a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts②">Patent Review Draft</a> for the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+	Also, the review initiated by the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review③">Last Call for Review of Proposed Amendments</a> is an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑦">Advisory Committee Review</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#last-call-for-review-of-proposed-additions" id="ref-for-last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a> and <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections-and-additions" id="ref-for-last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a> can only be issued for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤②">Recommendations</a> that <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features③">allow new features</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑥">Working Group</a> <em class="rfc2119">may</em> batch
+	multiple <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①">proposed amendments</a> into a single <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review④">Last Call for Review of Proposed Amendments</a>.
+	To facilitate review,
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑤">Last Call for Review of Proposed Amendments</a> on a given specification <em class="rfc2119">should not</em> be issued more frequently
+	than approximately once every 6 months.</p>
+    <p>At the end of the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑥">Last Call for Review of Proposed Amendments</a>,
+	the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①④">W3C Decision</a> may either be
+	to reject the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments②">proposed amendment</a>,
+	or to clear the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments③">proposed amendment</a> for advancement as is,
+	or to return the proposal to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑦">Working Group</a> with a request to <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed④">formally address</a> comments made on the changes under review.
+	If the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑧">Working Group</a> needs to amend a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments④">proposed amendment</a> in response to review feedback
+	it must issue another <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑦">Last Call for Review of Proposed Amendments</a> on the revised change
+	before it can be incorporated into the main text.</p>
+    <p>Once all comments on a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑤">proposed amendment</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑤">formally addressed</a>,
+	and after the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑨">Working Group</a> can show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation③">adequate implementation experience</a> and the fulfillment of all other requirements of Recommendation text,
+	it may incorporate the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑥">proposed amendment</a> into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤③">Recommendation</a> by issuing an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①⓪">update request</a> for publication of the updated <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤④">Recommendation</a>.</p>
+    <p>To ensure adequate review of <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑦">proposed amendment</a> combinations,
+	only <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑧">proposed amendments</a> included in the most recent <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑧">Last Call for Review of Proposed Amendments</a> can be incorporated into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑤">Recommendation</a> text.
+	(Thus if incorporation of a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑨">proposed amendment</a> is postponed,
+	it may need to be included in multiple Last Calls for Review of Proposed Amendments.)</p>
+    <h4 class="heading settled" data-level="6.3.11" id="rec-track-regression"><span class="secno">6.3.11. </span><span class="content"> Regression on the Recommendation Track</span><a class="self-link" href="#rec-track-regression"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⓪">Working Group</a> may republish a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑨">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②④">technical report</a> at a lower <a href="#maturity-stages">maturity stage</a> by fulfilling the requirements to transition to that maturity stage,
+	as described above.</p>
+    <p>Additionally,
+	with the approvals (by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑤">group decision</a>) of each of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑤">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③①">AB</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①①⓪">Team</a> <em class="rfc2119">may</em> return
+	the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑤">technical report</a> to a lower <a href="#maturity-stages">maturity stage</a> in response to <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①⓪">wide review</a> or a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④②">formal objection</a>.</p>
+    <h4 class="heading settled" data-level="6.3.12" id="tr-end"><span class="secno">6.3.12. </span><span class="content"> Retiring Recommendation Track Documents</span><a class="self-link" href="#tr-end"></a></h4>
+    <p>Work on a technical report <em class="rfc2119">may</em> cease at any time.
+	Work <em class="rfc2119 new">should</em> cease
+	if W3C or a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥①">Working Group</a> determines
+	that it cannot productively carry the work any further.</p>
+    <h5 class="heading settled" data-level="6.3.12.1" id="abandon-draft"><span class="secno">6.3.12.1. </span><span class="content"> Abandoning an Unfinished Recommendation</span><a class="self-link" href="#abandon-draft"></a></h5>
+    <p>Any <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⓪">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑥">technical report</a> no longer intended
+	to advance or to be maintained,
+	and that is not being rescinded, <em class="rfc2119">should</em> be <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑧">published</a> as a <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC">Discontinued Draft</a>,
+	with no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①③">substantive change</a> compared to the previous publication.
+	This can happen if
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥②">Working Group</a> decided
+	to abandon work on the report,
+	or as the result of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑧">AC Review</a> requiring the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥③">Working Group</a> to discontinue work on the technical report before completion.
+	If a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥④">Working Group</a> is made to <a href="#GeneralTermination">close</a>,
+	W3C <em class="rfc2119">must</em> re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑨">publish</a> any unfinished <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑦">technical report</a> on the Recommendation track as <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC①">Discontinued Draft</a>.</p>
+    <p>Such a document should include in its status section
+	an explanation of why it was discontinued.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑤">Working Group</a> <em class="rfc2119">may</em> resume work
+	on such a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑧">technical report</a> within the scope of its charter
+	at any time,
+	by re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing①⓪">publishing</a> it as a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑨">Working Draft</a>.</p>
+    <h5 class="heading settled" data-level="6.3.12.2" id="rescind-cr"><span class="secno">6.3.12.2. </span><span class="content"> Rescinding a Candidate Recommendation</span><a class="self-link" href="#rescind-cr"></a></h5>
+    <p>The process for rescinding a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②⓪">Candidate Recommendation</a> is the same as for rescinding a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑥">Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.12.3" id="rec-rescind"><span class="secno">6.3.12.3. </span><span class="content"> Abandoning a W3C Recommendation</span><a class="self-link" href="#rec-rescind"></a></h5>
+    <p>It is possible that W3C decides
+	that implementing a particular <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑦">Recommendation</a> is no longer recommended.
+	There are three designations for such specifications,
+	chosen depending on the advice W3C wishes to give about further use of the specification.</p>
+    <p>W3C <em class="rfc2119">may</em> obsolete a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑧">Recommendation</a>,
+	for example if the W3C Community decides that the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑨">Recommendation</a> no longer represents best practices,
+	or is not adopted and is not apparently likely to be adopted.
+	An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs①">Obsolete Recommendation</a> <em class="rfc2119">may</em> be restored to normal <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⓪">Recommendation</a>,
+	for example because despite marking it Obsolete the specification is later more broadly adopted.</p>
+    <p>W3C <em class="rfc2119">may</em> declare a Recommendation Superseded
+	if a newer version exists which W3C recommends for new adoption.
+	The process for declaring a Recommendation Superseded is the same as for declaring it Obsolete, below;
+	only the name and explanation change.</p>
+    <p>W3C <em class="rfc2119">may</em> rescind a Recommendation
+	if W3C believes there is no reasonable prospect of it being restored
+	for example due to burdensome patent claims that affect implementers and cannot be resolved;
+	see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “W3C Royalty-Free (RF) Licensing Requirements”
+	and “PAG Conclusion”.</p>
+    <p>W3C only rescinds, supersedes, or obsoletes entire Recommendations.
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥①">Recommendation</a> can be both superseded and obsolete.
+	To rescind, supersede, or obsolete some part of a Recommendation,
+	W3C follows the process for <a href="#revising-rec">modifying a Recommendation</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> For the purposes of the W3C Patent Policy, <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs②">Obsolete</a> or <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup">Superseded Recommendation</a> has the status of an active <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥②">Recommendation</a>,
+	although it is not advised for future implementation;
+	a <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec①">Rescinded Recommendation</a> ceases to be in effect
+	and no new licenses are granted under the Patent Policy.</p>
+    <figure>
+     <svg viewBox="0 0 300 135" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Supersede, Obsolete or Rescind a W3C Recommendation</title>
+      <g role="list">
+       <g role="listitem">
+        <ellipse cx="40" cy="50" fill="#fff" id="rec-3" role="img" rx="30" ry="20" stroke="black" stroke-width="2">
+         <title>Recommendation (Rec)</title>
+        </ellipse>
+        <text aria-hidden="true" font-size="18" stroke-width=".3" text-anchor="middle" x="40" y="55">REC</text>
+        <g role="list">
+         <g role="listitem">
+          <title>A major problem and an AC review can lead to a Recommendation being Rescinded.
+								There are no new IPR licences issued under the W3C Patent Policy,
+								and reinstating the Recommendation requires going through the full Rec-track process again.</title>
+          <path d="M40,29v-5s0,-5 5,-5h150" fill="none" stroke="black" stroke-dasharray="3 1" stroke-width="2"></path>
+          <text font-size="8" text-anchor="middle" x="105" y="16">Major problem, AC review</text>
+          <polygon points="195,16 195,22 199,19"></polygon>
+          <rect fill="#fff" height="36" id="rescinded" role="img" stroke="black" stroke-width="2" width="80" x="200" y="4"></rect>
+          <title>Rescinded Recommendation - no new IPR licenses</title>
+          <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="240" y="19">Rescinded</text>
+          <path d="M198,42l84,-40" stroke="red" stroke-width="2"></path>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="28">No new IPR licenses</text>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="37">No reinstatement path</text>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="black" stroke-dasharray="4 4"></path>
+           <title>With little uptake, following AC review a specification may become an Obsolete Recommendation</title>
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="red" stroke-dasharray="2 6" stroke-dashoffset="3"></path>
+           <polygon points="204,75 200,72 200,78"></polygon>
+           <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="42">Minimal usage, AC review</text>
+           <rect fill="#fff" height="26" id="obsolete" rx="8" stroke="black" stroke-dasharray="3 3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <title>Obsolete Recommendation</title>
+           <rect fill="none" height="26" rx="8" stroke="red" stroke-dasharray="3 3" stroke-dashoffset="3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="242" y="84">Obsolete</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <path d="M204,82h-149s-5,0 -5,-5v-5" fill="none" stroke="black" stroke-dasharray="2 3"></path>
+             <title>If there is new uptake, with AC review an Obsolete Recommendation may return to normal Recommendation status</title>
+             <polygon points="50,70 47,74 53,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="79">New uptake, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M40,71v29s0,5 5,5h140" fill="none" stroke="black"></path>
+           <polygon points="189,105 185,102 185,108"></polygon>
+           <text font-size="8" text-anchor="middle" x="115" y="102">Replaced by a new version, AC review</text>
+           <rect fill="#fff" height="30" id="superseded" role="img" rx="3" stroke="#600" stroke-width="2" width="90" x="190" y="100">
+            <title>Superseded Recommendation</title>
+           </rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="235" y="119">Superseded</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <title>A Superseded Recommendation can become a normal Recommendation with AC review</title>
+             <path d="M189,125h-154s-5,0 -5,-5v-52" fill="none" stroke="black" stroke-dasharray="1 4"></path>
+             <polygon points="30,70 27,74 33,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="110" y="122">Oops! The Web still needs this, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+     <figcaption>Non-Normative Summary of the Paths to Retiring a W3C Recommendation</figcaption>
+    </figure>
+    <h5 class="heading settled" data-level="6.3.12.4" id="deactivation"><span class="secno">6.3.12.4. </span><span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span><a class="self-link" href="#deactivation"></a></h5>
+    <p>The process of rescinding, obsoleting,
+	superseding,
+	or restoring
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥③">Recommendation</a> can be initiated
+	either by a request from the <a data-link-type="dfn" href="#team" id="ref-for-team①①①">Team</a> or via a request from any of the following:</p>
+    <ul>
+     <li> The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑥">Working Group</a> who produced,
+			or is chartered to maintain,
+			the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥④">Recommendation</a> 
+     <li> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑥">TAG</a>, if there is no such <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑦">Working Group</a> 
+     <li> Any individual who made a request to the relevant <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑧">Working Group</a> as described above,
+			or the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑦">TAG</a> if such a group does not exist, to obsolete, rescind, supersede, or restore a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑤">Recommendation</a>,
+			where the request was not answered within 90 days 
+     <li> 5% of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑦">Advisory Committee representatives</a> of <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑤">Members</a> in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing②">Good Standing</a> 
+    </ul>
+    <p id="proposed-rescinded-rec">The <a data-link-type="dfn" href="#team" id="ref-for-team①①②">Team</a> <em class="rfc2119">must</em> then
+	submit the request to the <a href="#AC">Advisory Committee</a> for review.
+	For any <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑨">Advisory Committee review</a> of a proposal to
+	rescind,
+	obsolete,
+	supersede,
+	or restore
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑥">Recommendation</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①①③">Team</a> <em class="rfc2119">must</em>: </p>
+    <ul>
+     <li> announce the proposal to all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑨">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③②">Chairs</a>,
+			and to the Public,
+			as well as to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑧">Advisory Committee</a> 
+     <li> indicate that this is a proposal to
+			Rescind,
+			Obsolete,
+			Supersede,
+			or restore,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑦">Recommendation</a> as appropriate 
+     <li> identify the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑧">Recommendation</a> by URL 
+     <li> publish a rationale for the proposal 
+     <li> identify known dependencies
+			and solicit review from all dependent <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⓪">Working Groups</a> 
+     <li> solicit public review 
+     <li> specify the deadline for review comments,
+			which <em class="rfc2119">must</em> be at least 28 days
+			after the announcement 
+    </ul>
+    <p>and <em class="rfc2119">should</em></p>
+    <ul>
+     <li> identify known implementations. 
+    </ul>
+    <p>If there was any <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑥">dissent</a> in the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⓪">Advisory Committee review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①④">Team</a> <em class="rfc2119">must</em> publish
+	the substantive content of the dissent to W3C <strong>and the public</strong>,
+	and <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑥">formally address</a> the dissent
+	at least 14 days
+	before publication as an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs③">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec②">Rescinded Recommendation</a>.</p>
+    <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑦">Advisory Committee Appeal</a> of the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑤">Team</a>’s decision.</p>
+    <p>W3C <em class="rfc2119">must</em> publish an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs④">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec③">Rescinded Recommendation</a> 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 <em class="rfc2119">should</em> link
+	to the explanation of <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">Obsoleting and Rescinding W3C Specifications</a> <a data-link-type="biblio" href="#biblio-obs-resc" title="Obsoleting and Rescinding W3C Specifications">[OBS-RESC]</a> as appropriate.</p>
+    <p>Once W3C has published a Rescinded Recommendation,
+	future W3C technical reports <em class="rfc2119">must not</em> include normative references
+	to that technical report.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> W3C strives to ensure that all Technical Reports
+	will continue to be available at their version-specific URL.</p>
+    <h3 class="heading settled" data-level="6.4" id="note-track"><span class="secno">6.4. </span><span class="content"> The Note Track (Notes and Statements)</span><a class="self-link" href="#note-track"></a></h3>
+    <h4 class="heading settled" data-level="6.4.1" id="Note"><span class="secno">6.4.1. </span><span class="content"> Group Notes</span><a class="self-link" href="#Note"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Group Note | Note | W3C Note | Working Group Note | Interest Group Note | AB Note | TAG Note" id="WGNote">Group Note</dfn> (<abbr>NOTE</abbr>)
+	is published
+	to provide a stable reference for a useful document
+	that is not intended to be a formal standard.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦①">Working Groups</a>, <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①②">Interest Groups</a>,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑧">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③②">AB</a> <em class="rfc2119">may</em> publish work as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②">Notes</a>.
+	Examples include:</p>
+    <ul>
+     <li> supporting documentation for a specification,
+			such as explanations of design principles
+			or use cases and requirements 
+     <li> non-normative guides to good practices 
+    </ul>
+    <p>Some <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote③">Notes</a> are developed through successive <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Note Draft" data-noexport id="note-draft"><span class="bs-old-id" id="draft-note"></span>Note Drafts</dfn> before publication as a full <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote④">Notes</a>,
+	while others are <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①①">published</a> directly as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑤">Note</a>.
+	There are few formal requirements to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①②">publish</a> a document as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑥">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft">Note Draft</a>,
+	and they have no standing as a recommendation of W3C
+	but are simply documents preserved for historical reference.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> does not apply any licensing requirements or commitments for <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑦">Notes</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft①">Note Drafts</a>.</p>
+    <h4 class="heading settled" data-level="6.4.2" id="publishing-notes"><span class="secno">6.4.2. </span><span class="content"> Publishing Notes</span><a class="self-link" href="#publishing-notes"></a></h4>
+    <p>In order to publish a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑧">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft②">Note Draft</a>,
+	the group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record their decision
+			to request publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑨">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft③">Note Draft</a>, and 
+     <li> <em class="rfc2119">should</em> publish documentation
+			of significant changes to the technical report
+			since any previous publication. 
+    </ul>
+    <p>Both <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⓪">Notes</a> and <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft④">Note Drafts</a> can be updated by republishing
+	as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①①">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft⑤">Note Draft</a>.
+	A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑨">technical report</a> <em class="rfc2119">may</em> remain
+	a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①②">Note</a> indefinitely.</p>
+    <h4 class="heading settled" data-level="6.4.3" id="w3c-statement"><span class="secno">6.4.3. </span><span class="bs-old-id" id="memo"></span><span class="content"> Elevating Group Notes to W3C Statement status</span><a class="self-link" href="#w3c-statement"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Statement | W3C Statement" data-noexport id="statement">W3C Statement</dfn> is a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①③">Note</a> that has been endorsed by W3C as a whole.
+	In order to elevate a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①④">Note</a> to <a data-link-type="dfn" href="#statement" id="ref-for-statement②">W3C Statement</a> status,
+	A group <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①①">wide review</a>. 
+     <li> record the group’s decision to request publication as a <a data-link-type="dfn" href="#statement" id="ref-for-statement③">W3C Statement</a>. 
+     <li> show that all issues raised against the document
+			since its first publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑤">Note</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑦">formally addressed</a>. 
+     <li> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④③">Formal Objections</a>. 
+    </ul>
+    <p>A <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑥">Note</a> specifying implementable technology <em class="rfc2119">should not</em> be elevated to <a data-link-type="dfn" href="#statement" id="ref-for-statement④">W3C Statement</a> status;
+	if it does,
+	the request to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑤">Statement</a> <em class="rfc2119">must</em> include rationale
+	for why it should be elevated,
+	and why it is not on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①①">Recommendation track</a>.</p>
+    <p>Once these conditions are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑥">Team</a> <em class="rfc2119">must</em> then
+	begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③①">Advisory Committee Review</a> on the question of
+	whether the document is appropriate to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑥">W3C Statement</a>.
+	During this review period,
+	the <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑦">Note</a> <em class="rfc2119">must not</em> be updated.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#statement" id="ref-for-statement⑦">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑤">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑧">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑧">Advisory Committee Appeal</a> of the decision.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①①⑦">Team</a> must announce the publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑧">W3C Statement</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑨">Advisory Committee</a>, other W3C groups, and the public.</p>
+    <h4 class="heading settled" data-level="6.4.4" id="revising-memo"><span class="secno">6.4.4. </span><span class="content"> Revising W3C Statements</span><a class="self-link" href="#revising-memo"></a></h4>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑥">group decision</a> to do so,
+	groups can request publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑨">W3C Statement</a> with <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑦">editorial changes</a>—​including <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑤">candidate amendment</a>—​without any additional process.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑥">candidate amendment</a> can be folded into the main text of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①⓪">W3C Statement</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①①">Statement</a>,
+	including review by the community to ensure
+	the substantive and editorial soundness of the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑦">candidate amendments</a>.
+	To validate this, the group must request
+	an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③②">Advisory Committee review</a> of the changes it wishes to incorporate.
+	The specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑧">candidate amendments</a> under review <em class="rfc2119">must</em> be identified as <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①⓪">proposed amendments</a> just as in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections" id="ref-for-last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a>.</p>
+    <p>The decision to incorporate <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①①">proposed amendments</a> into <a data-link-type="dfn" href="#statement" id="ref-for-statement①②">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑥">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑨">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑨">Advisory Committee Appeal</a> of the decision.</p>
+    <h3 class="heading settled" data-level="6.5" id="registries"><span class="secno">6.5. </span><span class="content"> The Registry Track</span><a class="self-link" href="#registries"></a></h3>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry">registry</dfn> documents a data set
+	consisting of one or more <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry table" id="registry-table">registry tables</dfn>,
+	each table representing an updatable collection
+	of logically independent, consistently-structured <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry entry" id="registry-entry">registry entries</dfn>.
+	A registry consists of:</p>
+    <ul>
+     <li>the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①">registry definition</a>, defining how the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②">registry tables</a> are structured and maintained 
+     <li>one or more <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table③">registry tables</a>, holding the data set represented by the <a data-link-type="dfn" href="#registry" id="ref-for-registry②">registry</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data">registry data</dfn>) 
+    </ul>
+    <p>The purposes of maintaining a <a data-link-type="dfn" href="#registry" id="ref-for-registry③">registry</a> can include:</p>
+    <dl>
+     <dt>non-collision 
+     <dd> Avoiding the problem
+			of two entities using the same value with different semantics. 
+     <dt>non-duplication 
+     <dd> Avoiding the problem
+			of having two or more different values in use with the same semantics. 
+     <dt>information 
+     <dd> Providing a central index
+			where anyone can find out
+			what a value means
+			and what its formal definition is
+			(and where it is). 
+     <dt>submission 
+     <dd> Ease of adding new terms,
+			including by stakeholders external to the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian">custodian</a> organization. 
+     <dt>consensus 
+     <dd> Promoting a clear consensus of the community on the terms. 
+    </dl>
+    <p>This section of the W3C Process provides a specialized process
+	facilitating the publication and maintenance of such <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table④">registry tables</a>,
+	particularly those required by or closely related to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑨">W3C Recommendations</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Not every table in a specification is a potential registry.
+	If the intent or effect is that the table enumerates
+	all the possibilities the authors of the specification expect or envisage,
+	then the table by itself is enough.
+	Similarly, if the table is managed by the Working Group
+	and only updated as part of specification update,
+	then the complexities of registry management are not needed.</p>
+    <h4 class="heading settled" data-level="6.5.1" id="reg-def"><span class="secno">6.5.1. </span><span class="content"> Registry Definitions</span><a class="self-link" href="#reg-def"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-definition">registry definition</dfn> defines what each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑤">registry table</a> is and how it is maintained.
+	It <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Define the scope and purpose of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑥">registry table</a>. 
+     <li> Define the fields of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑦">registry table</a> and their constraints
+			(e.g. values must be drawn from a defined set, or be unique,
+			or only reference publicly available resources,
+			etc.) 
+     <li>
+       Define the policy for changes to existing entries, such as 
+      <ul>
+       <li>whether entries can be deleted or deprecated 
+       <li>whether entries can be changed after being published, and what kinds of changes are allowed 
+       <li>whether previously-deleted unique identifiers can be re-used, or are reserved indefinitely 
+      </ul>
+     <li> Define the method and criteria by which changes are proposed, approved, and incorporated.
+			(For example, a <a data-link-type="dfn" href="#registry" id="ref-for-registry④">registry</a> could define
+			that changes to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry①">registry entries</a> can be proposed using a particular web form or email address,
+			that they must be accompanied by certain background information,
+			or that they do or do not need to be approved by any member of a particular Working Group.) 
+     <li>
+       Identify the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="custodian">custodian</dfn> of the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑧">registry table</a>:
+			the entity to which requests for <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change">registry changes</a> must be sent,
+			and which is responsible for evaluating whether such requests
+			satisfy the criteria defined in the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition②">registry definition</a>. 
+      <p>The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian①">custodian</a> may be the initiating group, the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑧">Team</a>, or a delegated entity.
+			The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian②">custodian</a> for all <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑨">registry tables</a> in a single <a data-link-type="dfn" href="#registry" id="ref-for-registry⑤">registry</a> <em class="rfc2119">should</em> generally be the same entity.</p>
+      <p>If the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian③">custodian</a> of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⓪">registry table</a> ceases to exist or to operate as a custodian
+			(e.g., the relevant group is disbanded, or 
+			the custodian is unresponsive to repeated attempts to make contact),
+			and the <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group⑤">chartered</a> or <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group①">elected group</a> that owns the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition③">registry definition</a> is itself <a href="#GeneralTermination">closed</a> or 
+			unresponsive,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑨">Team</a> <em class="rfc2119">should</em> propose replacing the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian④">custodian</a>,
+			which <em class="rfc2119">must</em> be confirmed
+			by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③③">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑦">W3C Decision</a>.</p>
+    </ul>
+    <h4 class="heading settled" data-level="6.5.2" id="reg-pub"><span class="secno">6.5.2. </span><span class="content"> Publishing Registries</span><a class="self-link" href="#reg-pub"></a></h4>
+    <p>A <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group⑥">chartered</a> or <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group②">elected group</a> can publish a <a data-link-type="dfn" href="#registry" id="ref-for-registry⑥">registry</a> as a stand-alone <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⓪">technical report</a> on the <a data-link-type="dfn" href="#registry-track" id="ref-for-registry-track">Registry Track</a>,
+	where it is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-report">registry report</dfn>. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦②">Working Groups</a> have the additional option of
+	incorporating a <a data-link-type="dfn" href="#registry" id="ref-for-registry⑦">registry</a> as part of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦⓪">Recommendation</a>,
+	as an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="embedded-registry"><span class="bs-old-id" id="registry-section"></span>embedded registry</dfn>.</p>
+    <p>The <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report①">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry①">embedded registry</a> <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Clearly label the <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report②">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry②">embedded registry</a>,
+			its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①①">tables</a>,
+			and its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition④">registry definitions</a> as such,
+			including a link to <a href="#registries">§ 6.5 The Registry Track</a> in this Process. 
+     <li> Include the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑤">registry definition</a> for each of its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①②">registry tables</a>. 
+     <li>
+       Provide the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data">registry data</a> by either: 
+      <ul>
+       <li> Including the entire contents of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①③">registry table</a>,
+					either inline in the report
+					(e.g. formatted as a table, or list, or other appropriate representation),
+					or in a machine-readable file published as part of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③①">technical report</a>,
+					or (preferably) both. 
+       <li> Linking to one or more standalone <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report">Registry Data Reports</a> containing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①④">registry tables</a> in human-readable form, machine-readable form,
+					or (preferably) both. 
+      </ul>
+     <li> Include, if the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑤">registry table</a> is provided in a machine-readable file,
+			a definition of the format of that file. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②⓪">Team</a> <em class="rfc2119">must</em> make available
+	a means for interested parties to be notified of any updates to a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑥">registry table</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since the Process does not impose requirements
+	on changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑦">registry table</a> other than those imposed by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑥">registry definition</a>,
+	acceptance of proposed <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change①">registry changes</a> on behalf of the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian⑤">custodian</a> and
+	publication of an updated <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report③">registry report</a> that contains
+	only <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change②">registry changes</a> since the previous publication
+	can be automated
+	if satisfaction of those rules can be automatically verified.</p>
+    <p>Rules for publication and advancement on the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-track">Registry Track</dfn> are identical to that of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①②">Recommendation Track</a> with the following exceptions:</p>
+    <ul>
+     <li> <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report④">Registry reports</a> are not subject to the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			and therefore none of their publications correspond,
+			to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑦">First Public Working Draft</a>, <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①⓪">Working Draft</a>,
+			or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts③">Patent Review Draft</a> for the purposes of the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+     <li> For the same reason,
+			there is no equivalent to <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec④">Rescinded Recommendation</a> nor to <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation①">Rescinded Candidate Recommendation</a> for <a data-link-type="dfn" href="#registry" id="ref-for-registry⑧">Registries</a>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①①">Working Draft</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-draft"><span class="bs-old-id" id="draft-registry"></span>Registry Draft</dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②①">Candidate Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry">Candidate Registry</dfn>,
+			with <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑨">Candidate Recommendation Snapshot</a> and <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑦">Candidate Recommendation Draft</a> corresponding to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-snapshot">Candidate Registry Snapshot</dfn> and <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-draft">Candidate Registry Draft</dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦①">W3C Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="w3c-registry">W3C Registry</dfn>; <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs⑤">Obsolete Recommendation</a> and <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup①">Superseded Recommendation</a> correspond to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="obsolete-registry">Obsolete Registry</dfn> and <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="superseded-registry">Superseded Registry</dfn>. 
+     <li> Changes that add new features (i.e., <a href="#correction-classes">class 4 changes</a>) are allowed
+			in all <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry①">W3C Registries</a>,
+			without needing them to explicitly indicate that this is allowed. 
+    </ul>
+    <h4 class="heading settled" data-level="6.5.3" id="reg-table-update"><span class="secno">6.5.3. </span><span class="content"> Updating Registry Tables</span><a class="self-link" href="#reg-table-update"></a></h4>
+    <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑧">registry table</a> that are in accordance with the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑦">registry definition</a>,
+	(i.e. <a href="#correction-classes">Class 5 changes</a>)
+	can be made by re-publishing the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③②">technical report</a> that contains the affected table,
+	without needing to satisfy any other requirements for the publication
+	(not even a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑦">group decision</a>, unless this is required by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑧">registry definition</a>).
+	Such <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change③">registry changes</a> do not trigger new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③④">Advisory Committee Reviews</a>,
+	nor Exclusion Opportunities,
+	and do not require verification via an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①①">update request</a>,
+	even for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③③">technical reports</a> at maturities where this would normally be expected.
+	Such publications can be made
+	even in the absence of a group chartered to maintain the registry
+	when the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian⑥">custodian</a> is another entity.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The custodian is only empowered to make <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change④">registry changes</a>.
+	If the group establishing the registry wishes
+	to empower the custodian to add commentary on individual entries,
+	this needs to be part of the registry table’s definition.
+	If other changes are desired,
+	they need to be requested of the group responsible for maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑨">registry definition</a>—​or in the absence of such a group, of the Team.</p>
+    <p>Changes to the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑨">registry tables</a> made in accordance with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑨">candidate</a> or <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①②">proposed amendments</a> to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⓪">registry definition</a> which would not be allowed by the unamended <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①①">registry definition</a> <em class="rfc2119">must</em> be identified as such.</p>
+    <h4 class="heading settled" data-level="6.5.4" id="reg-data-reports"><span class="secno">6.5.4. </span><span class="content"> Registry Data Reports</span><a class="self-link" href="#reg-data-reports"></a></h4>
+    <p>When the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data①">registry data</a> is published in a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③④">technical report</a> from its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①②">registry definition</a>,
+	that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑤">report</a> is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data-report">Registry Data Report</dfn>.
+	This <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑥">technical report</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">Must</em> link to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①③">registry definition</a> establishing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②⓪">registry tables</a> that it contain. 
+     <li> <em class="rfc2119">May</em> contain non-normative introductory text, examples, and notes
+			about the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②①">registry tables</a> and <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry②">entries</a> that it contains.
+			(Changes to these parts are deemed to be <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑧">editorial changes</a>). 
+    </ul>
+    <p><a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report①">Registry Data Reports</a> do not have maturity stages in and of themselves;
+	The maturity stage of the <a data-link-type="dfn" href="#registry" id="ref-for-registry⑨">registry</a> whose <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data②">data</a> they record
+	is that of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑦">technical report</a> holding the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①④">registry definition</a>.</p>
+    <p>Anytime a change is made to a <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑤">registry definition</a>,
+	the group maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑥">registry definition</a> <em class="rfc2119">must</em> update and republish
+	any document holding the corresponding <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②②">registry tables</a> to make it consistent with these changes.</p>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑧">group decision</a> to do so,
+	the group maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑦">registry definition</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report②">Registry Data Report</a> to incorporate <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑨">editorial changes</a>.</p>
+    <h4 class="heading settled" data-level="6.5.5" id="reg-ref-specifications"><span class="secno">6.5.5. </span><span class="content"> Specifications that Reference Registries</span><a class="self-link" href="#reg-ref-specifications"></a></h4>
+    <p>Registries document values,
+	they do not define any architectural or interoperability requirements
+	related to those values.
+	All architectural and interoperability requirements
+	pertaining to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry③">registry entries</a> <em class="rfc2119">must</em> be contained in the specifications that reference the registry,
+	and are therefore subject to the processes
+	(including approval and intellectual property provisions)
+	applicable to those referencing specifications.</p>
+    <p>If there are entries that must be implemented,
+	or any other such restrictions,
+	they <em class="rfc2119">must</em> be defined or documented
+	in the referencing specification
+	without dependency on the registry.</p>
+    <div class="example" id="example-87a6a8f6"><a class="self-link" href="#example-87a6a8f6"></a> For example, <span class="allow-2119">“All implementations must implement the <code>Basic-Method</code> as defined in the registry”</span> is not acceptable because
+		a change to the definition of the <code>Basic-Method</code> in the registry would then affect conformance.
+		Instead, the requirement has to be complete in the specification,
+		directly or by reference to another specification.
+		For example <span class="allow-2119">“All implementations must recognize the name <code>Basic-Method</code>,
+		and implement it as defined by section yy of IETF RFC xxxx”</span>.
+		(The Registry is nonetheless expected to contain <code>Basic-Method</code> as an entry.) </div>
+    <h4 class="heading settled" data-level="6.5.6" id="reg-pat"><span class="secno">6.5.6. </span><span class="content"> Registries and Patents</span><a class="self-link" href="#reg-pat"></a></h4>
+    <p>A <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report⑤">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry③">embedded registry</a> is not subject to the W3C Patent Policy,
+	and <em class="rfc2119">must not</em> define any requirements on implementations.
+	For the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (only),
+	any <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry④">embedded registry</a> in a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①③">Recommendation track</a> document
+	is not a normative portion of that specification.</p>
+    <h3 class="heading settled" data-level="6.6" id="switching-tracks"><span class="secno">6.6. </span><span class="content"> Switching Tracks</span><a class="self-link" href="#switching-tracks"></a></h3>
+    <p>Given a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑨">Group decision</a> to do so, <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦③">Working Groups</a> can republish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑧">technical report</a> on a different track than the one it is on,
+	under the following restrictions:</p>
+    <ul>
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑨">technical report</a> that is or was
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦②">W3C Recommendation</a>, <a data-link-type="dfn" href="#statement" id="ref-for-statement①③">W3C Statement</a>, or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts④">Patent Review Draft</a> cannot switch tracks. 
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④⓪">technical report</a> should not switch away from the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①④">Recommendation Track</a> without due consideration of the Patent Policy implications
+			and approval of W3C’s legal counsel
+			if the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦④">Working Group</a> envisions a likelihood of returning to it later. 
+    </ul>
+    <p><a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④①">Technical reports</a> that switch tracks start at
+	their new track’s initial maturity stage,
+	while retaining any established identity (url, shortname, etc.).</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The initial maturity stage of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⑤">Recommendation track</a> is <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①②">Working Draft</a>. <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑧">First Public Working Draft</a> designates a specific type of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①③">Working Draft</a> and is not a separate maturity stage.
+	A document which switches to the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⑥">Recommendation track</a> is only published as a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑨">First Public Working Draft</a> if it was never previously published as such;
+	otherwise, it is simply a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①④">Working Draft</a>.</p>
+    <h3 class="heading settled" data-level="6.7" id="further-reading"><span class="secno">6.7. </span><span class="content"> Further reading</span><a class="self-link" href="#further-reading"></a></h3>
+    <p>Refer to <a href="https://www.w3.org/guide/transitions/">"How to Organize a Recommendation Track Transition"</a> <a data-link-type="biblio" href="#biblio-transition" title="Organize a Technical Report Transition">[TRANSITION]</a> in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a> for practical information about preparing for the reviews
+	and announcements of the various steps,
+	and <a href="https://www.w3.org/guide/standards-track/rec-tips">tips on getting to Recommendation faster</a> <a data-link-type="biblio" href="#biblio-rec-tips" title="Tips for Getting to Recommendation Faster">[REC-TIPS]</a>.
+	Please see also the <a href="https://www.w3.org/guide/standards-track/republishing">Requirements for modification of W3C Technical Reports</a> <a data-link-type="biblio" href="#biblio-republishing" title="In-place modification of W3C Technical Reports">[REPUBLISHING]</a>.</p>
+    <h2 class="heading settled" data-level="7" id="dissemination"><span class="secno">7. </span><span class="content"> <span id="chapterDissemination"></span> Dissemination Policies</span><a class="self-link" href="#dissemination"></a></h2>
+    <h3 class="heading settled" data-level="7.1" id="pub-com"><span class="secno">7.1. </span><span class="content"> Public Communication</span><a class="self-link" href="#pub-com"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②①">Team</a> is responsible for managing communication within W3C
+	and with the general public
+	(e.g., news services, press releases, managing the website and access privileges, and managing calendars).
+	Members <em class="rfc2119">should</em> solicit review by the Team
+	prior to issuing press releases about their work within W3C.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②②">Team</a> makes every effort to ensure the persistence and availability of the following public information:</p>
+    <ul>
+     <li> <a href="#Reports">W3C technical reports</a> whose publication has been approved.
+			Per <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/policies/"><cite>W3C IPR Policies</cite></a>,
+			W3C technical reports (and software) are available free of charge to the general public. 
+     <li> A <a href="https://www.w3.org/mission/">mission statement</a> <a data-link-type="biblio" href="#biblio-mission" title="The W3C Mission statement">[MISSION]</a> that explains the purpose and mission of W3C,
+			the key benefits for Members,
+			and the organizational structure of W3C. 
+     <li> Legal documents,
+			including <a href="https://www.w3.org/membership/agreement/">Membership Agreements</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> and documentation of any legal commitments W3C has with other entities. 
+     <li> The Process Document. 
+     <li> Public results of W3C activities and <a href="#GAEvents">Workshops</a>. 
+    </ul>
+    <p>To keep the Members abreast of W3C meetings, <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW③">Workshops</a>,
+	and review deadlines,
+	the Team provides them with a regular (e.g., weekly) news service
+	and maintains a <a href="https://www.w3.org/events/">calendar</a> <a data-link-type="biblio" href="#biblio-calendar" title="Calendar of all scheduled official W3C events">[CALENDAR]</a> of official W3C events.
+	Members are encouraged to send schedule and event information to the Team for inclusion on this calendar.</p>
+    <h3 class="heading settled" data-level="7.2" id="confidentiality-levels"><span class="secno">7.2. </span><span class="content"> Confidentiality Levels</span><a class="self-link" href="#confidentiality-levels"></a></h3>
+    <p>There are three principal levels of access to W3C information
+	(on the W3C website, in W3C meetings, etc.):
+	public,
+	Member-only,
+	and Team-only.</p>
+    <p>While much information made available by W3C is public,
+	“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Member-Only" id="Member-only">Member-only</dfn>” information
+	is available to authorized parties only,
+	including representatives of Member organizations, <a href="#invited-expert-wg">Invited Experts</a> (as described in <a href="https://www.w3.org/invited-experts/#memaccess">https://www.w3.org/invited-experts/#memaccess</a>),
+	the Advisory Board,
+	the TAG,
+	and the Team.
+	For example,
+	the <a href="#WGCharter">charter</a> of some Working Groups <em class="rfc2119">may</em> specify a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only④">Member-only</a> confidentiality level for group proceedings.</p>
+    <p>“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team-Only" id="Team-only">Team-only</dfn>” information
+	is available to the Team and other authorized parties.</p>
+    <p>Those authorized to access <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑤">Member-only</a> and <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only①">Team-only</a> information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> treat the information as confidential within W3C, 
+     <li> <em class="rfc2119">must</em> use reasonable efforts to preserve that confidentiality, and 
+     <li> <em class="rfc2119">must not</em> release this information to the general public or press,
+			nor beyond the proper level of access. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②③">Team</a> <em class="rfc2119">must</em> provide mechanisms
+	to protect the confidentiality of <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑥">Member-only</a> information
+	and ensure that authorized parties have proper access to this information.
+	Documents <em class="rfc2119">should</em> clearly indicate
+	whether they require <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑦">Member-only</a> confidentiality.
+	Individuals uncertain of the confidentiality level of a piece of information <em class="rfc2119">should</em> contact the Team.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⓪">Advisory Committee representatives</a> <em class="rfc2119">may</em> authorize <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑧">Member-only</a> access to <a href="#member-rep">Member representatives</a> and other individuals employed by the Member
+	who are considered appropriate recipients.
+	For instance,
+	it is the responsibility of the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③①">Advisory Committee representative</a> and other employees
+	and official representatives of the organization
+	to ensure that Member-only news announcements
+	are distributed for internal use only within their organization.
+	Information about Member mailing lists is available
+	in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h3 class="heading settled" data-level="7.3" id="confidentiality-change"><span class="secno">7.3. </span><span class="content"> Changing Confidentiality Level</span><a class="self-link" href="#confidentiality-change"></a></h3>
+    <p>As a benefit of membership,
+	W3C provides some <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only②">Team-only</a> and <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑨">Member-only</a> channels
+	for certain types of communication.
+	For example, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③②">Advisory Committee representatives</a> can send <a href="#ACReview">reviews</a> to a <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only③">Team-only</a> channel.
+	However, for W3C processes with a significant public component,
+	such as the technical report development process,
+	it is also important for information that affects decision-making to be publicly available.
+	The Team <em class="rfc2119">may</em> need to communicate <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only④">Team-only</a> information to a Working Group or the public.
+	Similarly, a Working Group whose proceedings are <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①⓪">Member-only</a> <em class="rfc2119">must</em> make public
+	information pertinent to the technical report development process.</p>
+    <p>This document clearly indicates which information <em class="rfc2119">must</em> be available to Members or the public,
+	even though that information was initially communicated on <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑤">Team-only</a> or <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①①">Member-only</a> channels.
+	Only the <a data-link-type="dfn" href="#team" id="ref-for-team①②④">Team</a> and parties authorized by the Team
+	may change the level of confidentiality of this information.
+	When doing so:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑤">Team</a> <em class="rfc2119">must</em> use a version of the information
+			that was expressly provided by the author for the new confidentiality level.
+			In Calls for Review and other similar messages,
+			the Team <em class="rfc2119">should</em> remind recipients to provide such alternatives. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑥">Team</a> <em class="rfc2119">must not</em> attribute the version
+			for the new confidentiality level to the author without the author’s consent. 
+     <li> If the author has not conveyed to the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑦">Team</a> a version
+			that is suitable for another confidentiality level,
+			the Team <em class="rfc2119">may</em> make available a version that reasonably communicates what is required,
+			while respecting the original level of confidentiality,
+			and without attribution to the original author. 
+    </ol>
+    <h2 class="heading settled" data-level="8" id="Liaisons"><span class="secno">8. </span><span class="content"> Liaisons</span><a class="self-link" href="#Liaisons"></a></h2>
+    <p>W3C uses the term <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="liaison">liaison</dfn> 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 <a data-link-type="dfn" href="#team" id="ref-for-team①②⑧">Team</a> due to requirements for public communication;
+	patent,
+	copyright,
+	and other IPR policies;
+	confidentiality agreements;
+	and mutual membership agreements.</p>
+    <p>W3C <em class="rfc2119">may</em> negotiate <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①">technical agreements</a> with another organization.
+	For purposes of the W3C Process,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="agreement" data-noexport id="technical-agreement">technical agreement</dfn> is a formal contract,
+	or a Memorandum of Understanding (<abbr>MoU</abbr>),
+	or a similar document,
+	between W3C and another party or parties,
+	that relates to the technical activity of the Consortium
+	(e.g., its publications, groups, or liaisons).
+	It specifies rights and obligations of each party toward the others.
+	These rights and obligations <em class="rfc2119">may</em> include joint deliverables,
+	an agreed share of technical responsibilities with due coordination,
+	and/or considerations for confidentiality and specific IPR.</p>
+    <p>Non-technical agreements, including
+	those between W3C and its <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑥">Members</a> for the purposes of membership,
+	between W3C and its Partners for the purposes of partnership <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a>,
+	and other agreements related to the operation of the Consortium
+	or to the ordinary provision of services,
+	are not subject to these Process provisions.</p>
+    <p>When considering a <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement②">technical agreement</a> (i.e., before the decision whether to sign is made),
+	the Team <em class="rfc2119">should</em> provide
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④⓪">Advisory Committee</a> with a draft of the proposed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement③">agreement</a>,
+	along with an explanation of how W3C would benefit from signing this <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement④">agreement</a>,
+	for their review and discussion.
+	After addressing any comments,
+	and subject to any management or governance procedures that apply
+	(e.g., formal review of proposed contracts by legal counsel or by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑦">Board</a>),
+	if the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①②">Team decides</a> to proceed with signing the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑤">agreement</a>,
+	the Team <em class="rfc2119">must</em> announce the intent to sign,
+	and provide the final text of the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑥">agreement</a>,
+	with an explanation of signing rationale, to
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④①">Advisory Committee</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③③">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①⓪">Advisory Committee Appeal</a> of the decision to sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑦">agreement</a>.
+	If the proposal is rejected on <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①①">appeal</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑨">Team</a> <em class="rfc2119">must not</em> sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑧">agreement</a> on behalf of W3C
+	unless directed to do so by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑧">Board</a>.
+	A signed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑨">agreement</a> <em class="rfc2119">should</em> be made public.</p>
+    <p>Information about <a href="https://www.w3.org/liaisons/">W3C liaisons with other organizations</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a> and the guidelines W3C follows when creating a liaison is available on the Web.</p>
+    <h2 class="heading settled" data-level="9" id="Submission"><span class="secno">9. </span><span class="bs-old-id" id="SubmissionNo"></span><span class="bs-old-id" id="SubmissionYes"></span><span class="bs-old-id" id="TeamSubmissionRights"></span><span class="bs-old-id" id="SubmissionScope"></span><span class="bs-old-id" id="SubmissionRights"></span><span class="content"> Member Submissions</span><a class="self-link" href="#Submission"></a></h2>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="MemberSubmission">Member Submission</dfn> is a document or set of documents
+	developed outside of W3C,
+	and submitted to W3C
+	by one or more <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑦">Members</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="submitter" id="submitter">Submitter(s)</dfn>)
+	to propose technology or other ideas.
+	After review,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③⓪">Team</a> <em class="rfc2119">may</em> make the material available at the W3C website.</p>
+    <p>Making a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission">Member Submission</a> available at the W3C website
+	does not indicate endorsement, acceptance, or adoption by W3C,
+	its Team, or its Members.
+	The <a data-link-type="dfn" href="#acknowledged" id="ref-for-acknowledged">acknowledgment</a> of a Submission request
+	does not imply that any action will be taken by W3C.
+	It merely records publicly
+	that the Submission has been made by the Submitter(s).
+	A Member Submission made available by W3C
+	is not a W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④②">technical report</a> and <em class="rfc2119">must not</em> be referred to as
+	an output or “work in progress” of W3C.</p>
+    <p>The <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission①">Member Submission</a> process consists of the following steps:</p>
+    <dl>
+     <dt>Submission 
+     <dd> One of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter">Submitters</a>,
+			copying the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③④">Advisory Committee representatives</a> of the other <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①">Submitters</a> (if any),
+			sends a request to the Team to acknowledge the Submission request.
+			The <a data-link-type="dfn" href="#team" id="ref-for-team①③①">Team</a> and <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②">Submitter(s)</a> communicate to ensure that the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission②">Member Submission</a> is complete. 
+     <dt>Review 
+     <dd>
+       The <a data-link-type="dfn" href="#team" id="ref-for-team①③②">Team</a> reviews the Submission
+			to evaluate its scope, quality, and compliance with the Submission requirements,
+			including licensing requirements: 
+      <ul>
+       <li> The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter③">Submitter(s)</a> and any other authors of the submitted material <em class="rfc2119">must</em> agree
+					to license the Submission under the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a>. 
+       <li> The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments
+					in <a href="https://www.w3.org/policies/patent-policy/#sec-submissions">The W3C Patent Policy § sec-submissions</a>. 
+      </ul>
+      <p>Detailed procedures and requirements are defined by the <a data-link-type="dfn" href="#team" id="ref-for-team①③③">Team</a> and documented in the “<a href="https://www.w3.org/submissions/guide/">Member submissions guidebook</a>” <a data-link-type="biblio" href="#biblio-member-sub" title="Member submissions guidebook">[MEMBER-SUB]</a>.</p>
+     <dt>Decision 
+     <dd>
+       After review, the <a data-link-type="dfn" href="#team" id="ref-for-team①③④">Team</a> <em class="rfc2119">must</em> either <a data-link-type="dfn" href="#acknowledged" id="ref-for-acknowledged①">acknowledge</a> or <a data-link-type="dfn" href="#rejected" id="ref-for-rejected">reject</a> the Submission request. 
+      <ul>
+       <li> If <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="acknowledged">acknowledged</dfn>,
+					the Team <em class="rfc2119">must</em> make the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission③">Member Submission</a> available
+					at the public W3C website
+					alongside other <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a> <a data-link-type="biblio" href="#biblio-submission-list" title="The list of acknowledged Member Submissions">[SUBMISSION-LIST]</a>. 
+       <li> If <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rejected">rejected</dfn>,
+					the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑤">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⑤">Advisory Committee representative(s)</a> of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter④">Submitter(s)</a>,
+					and <em class="rfc2119">must</em> provide rationale if requested by the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑤">Submitter(s)</a>.
+					The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑥">Submitter(s)</a> <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals③">Submission Appeal</a>. 
+      </ul>
+    </dl>
+    <p>The <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⑥">Advisory Committee representative(s)</a> of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑦">Submitter(s)</a> <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals④">Submission Appeal</a>.
+	The procedure for handling <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="submission-appeals">Submission Appeals</dfn> is the same as for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④④">Formal Objections</a>,
+	except that an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①②">AC Appeal</a> is not possible
+	and both the Formal Objection and the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report⑤">Council Report</a> are confidential to the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑥">Team</a>, <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑨">TAG</a>, and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③③">AB</a>.</p>
+    <h2 class="heading settled" data-level="10" id="GAProcess"><span class="secno">10. </span><span class="content"> Process Evolution</span><a class="self-link" href="#GAProcess"></a></h2>
+    <p>Revision of the W3C Process and related documents (see below) undergoes similar <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②②">consensus</a>-building processes as for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④③">technical reports</a>,
+	with the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③④">Advisory Board</a>—​acting as the sponsoring <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑤">Working Group</a>.
+	The documents may be developed by the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑤">AB</a> or by another group to whom the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑥">AB</a> has delegated development.
+	Review includes
+	soliciting input from the W3C community,
+	and in particular the Team.</p>
+    <p>The documents covered by this section are:</p>
+    <ul>
+     <li data-md>
+      <p>the W3C Process (this document)</p>
+     <li data-md>
+      <p>the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a></p>
+     <li data-md>
+      <p>the W3C Code of Conduct <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a></p>
+     <li data-md>
+      <p>The W3C Document License <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a></p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑦">Advisory Board</a> initiates review as follows:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③⑦">Team</a> sends a Call for Review to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④②">Advisory Committee</a> and other W3C groups. 
+     <li> After comments have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑧">formally addressed</a> and the document possibly modified,
+			the Team seeks endorsement from the Members by initiating an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑤">Advisory Committee review</a>.
+			The review period <em class="rfc2119">must</em> last at least <span class="time-interval">28 days</span>. 
+     <li> <a href="#ACReviewAfter">After the Advisory Committee review</a>,
+			following a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑧">W3C decision</a> to adopt the document(s),
+			the Team does so
+			and sends an announcement to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④③">Advisory Committee</a>.
+			Advisory Committee representatives <em class="rfc2119">may</em> initiate
+			an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①③">Advisory Committee Appeal</a> to W3C. 
+    </ol>
+    <p class="note" role="note"><span class="marker">Note:</span> As of June 2020,
+	the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">Patent Policy</a> is developed in the <a href="https://www.w3.org/2004/pp/psig/">Patents and Standards Interest Group</a>,
+	the <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">Code of Conduct</a> in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
+	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.</p>
+    <h2 class="non-normative nonum heading settled" id="old-terms"><span class="content"> Appendix A: Retired Terminology</span><a class="self-link" href="#old-terms"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>Previous versions of this process defined and used various concepts and document statuses
+	that have since been retired or renamed.
+	For ease of reference,
+	this appendix lists the more notable ones,
+	and it links to the the definition or relevant section
+	in the most recent version of the Process that used them,
+	and gives the more recent equivalent term when there is one.</p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rec-amended">Amended Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2020/Process-20200915/#rec-amended">in section 6.2.1 of the 2020 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="edited-recommendation">Edited Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2019/Process-20190301/#maturity-levels">in section 6.1.2 of the 2019 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call">Last Call</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2005/10/Process-20051014/tr.html#last-call">in section 7.4.2 of the 2005 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="maturity-levels">Maturity level</dfn> (renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#maturity-levels">in section 6.3.1 of the 2021 Process</a>,
+			now called <a href="#maturity-stages">maturity stage</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fdn-member-consortium">Member Consortium</dfn>, plural: Member Consortia
+			(renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#fdn-member-consortium">in section 2.1.2.1 of the 2021 Process</a>,
+			now called <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑥">Member Association</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mou">Memorandum of Understanding</dfn>, plural: Memoranda of Understanding, abbreviation: MoU
+			(renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#mou">in section 9 of the 2021 Process</a>,
+			now called <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①⓪">technical agreement</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="other-charter">Other Charter</dfn> (renamed term) 
+     <dd> Last used <a href="https://www.w3.org/2020/Process-20200915/#other-charter">in section 5.2.6 of the 2020 Process</a>,
+			now called <a data-link-type="dfn" href="#exclusion-draft-charter" id="ref-for-exclusion-draft-charter">Exclusion Draft Charter</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="RecsPR">Proposed Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/policies/process/20231103/#RecsPR">in section 6.3.1 of the 2023 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="TeamSubmission">Team Submissions</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2019/Process-20190301/#TeamSubmission">in section 2.2.1 of the 2019 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-W3CChair">W3C Chair</dfn> (renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2014/Process-20140801/#def-W3CChair">in section 2.2 of the 2014 Process</a>,
+			now called <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑨">CEO</a>. 
+    </dl>
+    <h2 class="non-normative nonum heading settled" id="acks"><span class="content"> Appendix B: Acknowledgments</span><a class="self-link" href="#acks"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>The editors are grateful to the following people,
+	who as interested individuals and/or with the affiliation(s) listed,
+	have contributed to this proposal for a revised Process:
+	Brian Kardell,
+	Carine Bournez (W3C),
+	Charles McCathie Nevile (ConsenSys),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	David Singer (Apple),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Fuqiao Xue (W3C),
+	Jeff Jaffe (W3C),
+	Jeffrey Yasskin (Google),
+	Kevin Fleming (Bloomberg),
+	Léonie Watson (The Paciello Group),
+	Mark Nottingham (Cloudflare),
+	Michael Champion (Microsoft),
+	Nigel Megitt (BBC),
+	Philippe Le Hégaret (W3C),
+	Ralph Swick (W3C),
+	Samuel Weiler (W3C),
+	Sandro Hawke (W3C),
+	Shawn Lawton Henry,
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Virginia Fournier (Apple),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <p>The editors are sorry for forgetting any names,
+	and grateful to those who have listened patiently to conversations about this document
+	without feeling a need to add more.</p>
+    <p>The following individuals contributed to the development of earlier versions of the Process:
+	Alex Russell (Google),
+	Andreas Tai (Institut fuer Rundfunktechnik),
+	Andrew Betts (Fastly),
+	Ann Bassetti (The Boeing Company),
+	Anne van Kesteren,
+	Art Barstow (Nokia, unaffiliated),
+	Bede McCall (MITRE),
+	Ben Wilson,
+	Brad Hill (Facebook),
+	Brian Kardell (JQuery),
+	Carine Bournez (W3C),
+	Carl Cargill (Netscape, Sun Microsystems, Adobe),
+	Chris Lilley (W3C),
+	Chris Wilson (Google),
+	Claus von Riegen (SAP AG),
+	Coralie Mercier (W3C),
+	Cullen Jennings (Cisco),
+	Dan Appelquist (Telefonica, Samsung),
+	Dan Connolly (W3C),
+	Daniel Dardailler (W3C),
+	Daniel Glazman (Disruptive Innovations),
+	David Baron (Mozilla),
+	David Fallside (IBM),
+	David Singer (Apple),
+	David Singer (IBM),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Don Brutzman (Web3D),
+	Don Deutsch (Oracle),
+	Eduardo Gutentag (Sun Microsystems),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Florian Rivoal,
+	Fuqiao Xue (W3C),
+	Geoffrey Creighton (Microsoft),
+	Giri Mandyam (Qualcomm),
+	Gregg Kellogg,
+	Hadley Beeman,
+	Helene Workman (Apple),
+	Henri Sivonen (Mozilla),
+	Håkon Wium Lie (Opera Software),
+	Ian Hickson (Google),
+	Ian Jacobs (W3C),
+	Ivan Herman (W3C),
+	J Alan Bird (W3C),
+	Jay Kishigami 岸上順一 (NTT),
+	Jean-Charles Verdié (MStar),
+	Jean-François Abramatic (IBM, ILOG, W3C),
+	Jeff Jaffe (W3C),
+	Jim Bell (HP),
+	Jim Miller (W3C),
+	Joe Hall (CDT),
+	John Klensin (MCI),
+	Josh Soref (BlackBerry, unaffiliated),
+	Judy Brewer (W3C),
+	Judy Zhu 朱红儒 (Alibaba),
+	Kari Laihonen (Ericsson),
+	Karl Dubost (Mozilla),
+	Ken Laskey (MITRE),
+	Kevin Fleming (Bloomberg),
+	Klaus Birkenbihl (Fraunhofer Gesellschaft),
+	Larry Masinter (Adobe Systems),
+	Lauren Wood (unaffiliated),
+	Liam Quin (W3C),
+	Léonie Watson (The Paciello Group),
+	Marcos Cáceres (Mozilla),
+	Maria Courtemanche (IBM),
+	Mark Crawford (SAP),
+	Mark Nottingham,
+	Michael Champion (Microsoft),
+	Michael Geldblum (Oracle),
+	Mike West (Google),
+	Mitch Stoltz (EFF),
+	Natasha Rooney (GSMA),
+	Nigel Megitt (BBC),
+	Olle Olsson (SICS),
+	Ora Lassila (Nokia),
+	Paul Cotton (Microsoft),
+	Paul Grosso (Arbortext),
+	Peter Linss,
+	Peter Patel-Schneider,
+	Philippe Le Hégaret (W3C),
+	Qiuling Pan (Huawei),
+	Ralph Swick (W3C),
+	Renato Iannella (IPR Systems),
+	Rigo Wenning (W3C),
+	Rob Sanderson (J Paul Getty Trust),
+	Robin Berjon (W3C),
+	Sally Khudairi (W3C),
+	Sam Ruby (IBM),
+	Sam Sneddon,
+	Sandro Hawke (W3C),
+	Sangwhan Moon (Odd Concepts),
+	Scott Peterson (Google),
+	Steve Holbrook (IBM),
+	Steve Zilles (Adobe Systems)
+	Steven Pemberton (CWI),
+	TV Raman (Google),
+	Tantek Çelik (Mozilla),
+	Terence Eden (Her Majesty’s Government),
+	Thomas Reardon (Microsoft),
+	Tim Berners-Lee (W3C),
+	Tim Krauskopf (Spyglass),
+	Travis Leithead (Microsoft),
+	Virginia Fournier (Apple),
+	Virginie Galindo (Gemalto),
+	Wayne Carr (Intel),
+	Wendy Fong (Hewlett-Packard),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <h2 class="non-normative nonum heading settled" id="changes"><span class="content"> Appendix C: Changes</span><a class="self-link" href="#changes"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></span><a class="self-link" href="#changes-2024"></a></h3>
+    <p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
+	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2Fsnapshots%2F2025-05">diff from Process 2023 to this latest version</a>,
+	as well as
+	a <a href="https://github.com/w3c/process/compare/p2023_1...2025-review-draft">detailed log of all changes since then</a> are available. </p>
+    <p>In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:</p>
+    <dl>
+     <dt>Changes to formal decision making and escalation 
+     <dd>
+      <ul>
+       <li> Adjust the rules guiding initiation of Councils,
+					to make the deadline strict,
+					and to provide a fallback mechanism if they are not met.
+					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>) 
+       <li> Make the Council’s short-circuit a little more flexible.
+					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>) 
+       <li> Adjust AC appeal vote threshold based on participation,
+					aligning with the thresholds and super majority requirements
+					for "Requisite Member Vote" from the W3C Bylaws.
+					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>) 
+       <li> Exclude TAG/AB from voting on their own decisions/proposals.
+					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>) 
+       <li> Fine-tune the rules about
+					how changes can be incorporated into a proposal
+					following an AC Review.
+					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>) 
+       <li> Limit the involvement of Tim Berners-Lee to the TAG proper,
+					not including the Council.
+					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>) 
+       <li> Council dismissal vote counts must be reported.
+					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>) 
+       <li> Require documentation of how Formal Objections get resolved.
+					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>) 
+       <li> Let the originator of a proposal decide whether to try again
+					after addressing feedback
+					following an AC Appeal.
+					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>) 
+       <li> Put constraints on the timing of making Formal Objections public.
+					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>) 
+      </ul>
+     <dt>Changes to technical reports and their publication 
+     <dd>
+      <ul>
+       <li> Retire the Proposed Recommendation phase of the Recommendation track.
+					It was only used as a short-lived transition
+					during which various verifications and votes about CR were done.
+					These can be done on a CR
+					without having to republish it as a separate thing.
+					This simplifies the Process without changing the actual quality or consensus expectations.
+					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 
+       <li id="streamlined-update"><a class="self-link" href="#streamlined-update"></a> Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
+					This was meant to enable REC track publication with fewer/faster approval steps
+					when some stricter than usual criteria were fulfilled.
+					However, regular REC track publication have improved enough
+					that this became unnecessary,
+					and nobody was using it.
+					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>) 
+       <li> Drop the requirement to publish every 6 months if nothing has changed.
+					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>) 
+       <li> Add a requirement to make progress on external issues for update requests
+					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>) 
+       <li> Enable Team to replace defunct registry custodians when no-one else can.
+					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>) 
+       <li> Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
+					in addition to Working Groups.
+					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>) 
+       <li> Rename “registry sections” to <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry⑤">embedded registries</a> to avoid confusion over whether they can be split across multiple sections of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦③">Recommendation</a>.
+					(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>) 
+       <li> Rename "Draft Note" into "Note Draft",
+					and "Draft Registry" into "Registry Draft"
+					to be consistent with other statuses that uses the word "Draft",
+					and to make that word stand out more.
+					(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>) 
+       <li> Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
+					and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>). 
+       <li> Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a> the various parts of the Process
+					that described whether and how the Team can maintain technical reports
+					that no longer have a Group chartered to maintain them.
+					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>) 
+      </ul>
+     <dt>Changes to chartering 
+     <dd>
+      <ul>
+       <li> Introduce a formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①②">Charter Refinement</a> phase prior to the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑥">AC Review</a>.
+					(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>) 
+       <li> Reorganize and rephrase <a href="#CharterReview">§ 4.4 Charter Review and Approval</a> for readability and ease of understanding.
+					This change, while moderate in size, is purely editorial.
+					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>) 
+       <li> Require Chairs to be listed in Charters.
+					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>) 
+       <li> Be more specific about which types of changes to a charter must go through AC Review.
+					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>) 
+      </ul>
+     <dt>Other changes 
+     <dd>
+      <ul>
+       <li> Reuse the bylaws’ notion of Good Standing,
+					and restrict TAG and AB elections
+					as well as AC Votes where a decision is made based on counting ballots
+					to Members in Good Standing.
+					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a> and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>) 
+       <li> Clarify how the outcome of certain ballots are determined.
+					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>) 
+       <li> Stop citing the superseded TAG charter.
+					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>) 
+       <li> Shift most of the non-normative discussion about Workshops to <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>,
+					and reorganize the remaining normative requirements.
+					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>) 
+       <li> The section on Member Submissions was significantly shortened and simplified,
+					reducing the complexity under formal Process authority,
+					and shifting much of the material to /Guide,
+					under Team authority.
+					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a> and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>) 
+       <li> Clarify amount of leeway around incomplete nominations to TAG or AB elections.
+					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>) 
+       <li> Simplify provisions regarding substitute representatives and proxies.
+					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>) 
+       <li> The URL of this document was changed
+					from /Consortium/Process/ to /policies/process/
+					for better integration in the W3C website architecture. 
+      </ul>
+      <h3 class="no-num heading settled" id="changes-previous"><span class="bs-old-id" id="changes-2017"></span><span class="bs-old-id" id="changes-2018"></span><span class="bs-old-id" id="changes-2019"></span><span class="bs-old-id" id="changes-2020"></span><span class="bs-old-id" id="changes-2021"></span><span class="bs-old-id" id="changes-2023"></span><span class="bs-old-id" id="changes-2023-1"></span><span class="content"> Changes since earlier versions</span><a class="self-link" href="#changes-previous"></a></h3>
+      <p>Changes since earlier versions of the Process are detailed
+	in the <a href="https://www.w3.org/policies/process/20231103/#changes">changes section of the previous version</a> of the Process.</p>
+    </dl>
+   </main>
+   <div data-fill-with="conformance">
+    <h2 class="no-ref no-num heading settled" id="w3c-conformance"><span class="content">Conformance</span><a class="self-link" href="#w3c-conformance"></a></h2>
+    <h3 class="no-ref no-num heading settled" id="w3c-conventions"><span class="content">Document conventions</span><a class="self-link" href="#w3c-conventions"></a></h3>
+    <p>Conformance requirements are expressed
+    with a combination of descriptive assertions
+    and RFC 2119 terminology.
+    The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
+    in the normative parts of this document
+    are to be interpreted as described in RFC 2119.
+    However, for readability,
+    these words do not appear in all uppercase letters in this specification. </p>
+    <p>All of the text of this specification is normative
+    except sections explicitly marked as non-normative, examples, and notes. <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a> </p>
+    <p>Examples in this specification are introduced with the words “for example”
+    or are set apart from the normative text
+    with <code>class="example"</code>,
+    like this: </p>
+    <div class="example" id="w3c-example">
+     <a class="self-link" href="#w3c-example"></a> 
+     <p>This is an example of an informative example. </p>
+    </div>
+    <p>Informative notes begin with the word “Note”
+    and are set apart from the normative text
+    with <code>class="note"</code>,
+    like this: </p>
+    <p class="note" role="note">Note, this is an informative note.</p>
+   </div>
+   <script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script>
+  </main>
+  <h2 class="no-num no-ref heading settled" id="index"><span class="content">Index</span><a class="self-link" href="#index"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="content">Terms defined by this specification</span><a class="self-link" href="#index-defined-here"></a></h3>
+  <ul class="index">
+   <li><a href="#advisory-board">AB</a><span>, in § 3.3.1.1</span>
+   <li><a href="#WGNote">AB Note</a><span>, in § 6.4.1</span>
+   <li><a href="#advisory-committee">AC</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">AC Appeal</a><span>, in § 5.9</span>
+   <li><a href="#acknowledged">acknowledged</a><span>, in § 9</span>
+   <li><a href="#advisory-committee-representative">AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">AC Review</a><span>, in § 5.7</span>
+   <li><a href="#adequate-implementation">adequate implementation experience</a><span>, in § 6.3.2</span>
+   <li><a href="#adopted-draft">Adopted Draft</a><span>, in § 4.3</span>
+   <li><a href="#advisory-board">Advisory Board</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">Advisory Committee</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">Advisory Committee Appeal</a><span>, in § 5.9</span>
+   <li><a href="#advisory-committee-representative">Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">Advisory Committee review</a><span>, in § 5.7</span>
+   <li><a href="#technical-agreement">agreement</a><span>, in § 8</span>
+   <li><a href="#allow-new-features">allow new features</a><span>, in § 6.3.1</span>
+   <li><a href="#alternate-ac-representative">alt AC rep</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#rec-amended">Amended Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#advisory-committee-appeal">Appeal</a><span>, in § 5.9</span>
+   <li><a href="#appeal-vote">appeal vote</a><span>, in § 5.9</span>
+   <li><a href="#at-risk">at risk</a><span>, in § 6.3.7</span>
+   <li><a href="#bod">Board</a><span>, in § 2.2</span>
+   <li><a href="#bod">Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#bod">BoD</a><span>, in § 2.2</span>
+   <li><a href="#reviewform">Call for Review</a><span>, in § 5.7.1</span>
+   <li><a href="#candidate-addition">candidate addition</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-amendment">candidate amendment</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-correction">candidate correction</a><span>, in § 6.2.5</span>
+   <li><a href="#RecsCR">Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">Candidate Recommendation Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-review-period">Candidate Recommendation review period</a><span>, in § 6.3.7</span>
+   <li><a href="#candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-registry">Candidate Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-draft">Candidate Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-snapshot">Candidate Registry Snapshot</a><span>, in § 6.5.2</span>
+   <li><a href="#ceo">CEO</a><span>, in § 2.2</span>
+   <li><a href="#GeneralChairs">Chair</a><span>, in § 3.4.1</span>
+   <li><a href="#chair-decisions">chair decisions</a><span>, in § 5.1</span>
+   <li><a href="#charter">charter</a><span>, in § 4.3</span>
+   <li><a href="#charter-draft">charter draft</a><span>, in § 4.1</span>
+   <li><a href="#chartered-group">chartered groups</a><span>, in § 3.4</span>
+   <li><a href="#dfn-charter-extension">charter extension</a><span>, in § 4.6</span>
+   <li><a href="#chartering-facilitator">Chartering Facilitator</a><span>, in § 4.2</span>
+   <li><a href="#charter-refinement">charter refinement</a><span>, in § 4.2</span>
+   <li><a href="#charter-review-notice">charter review notice</a><span>, in § 4.1</span>
+   <li><a href="#def-Consensus">Consensus</a><span>, in § 5.2.1</span>
+   <li><a href="#convened">convened</a><span>, in § 5.6.2.6</span>
+   <li><a href="#w3c-council">Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#council-report">Council Report</a><span>, in § 5.6.2.8</span>
+   <li><a href="#council-team-contact">Council Team Contact</a><span>, in § 5.6.2.1</span>
+   <li><a href="#RecsCR">CR</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">CRD</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-snapshot">CRS</a><span>, in § 6.3.1</span>
+   <li><a href="#custodian">custodian</a><span>, in § 6.5.1</span>
+   <li><a href="#discontinuedREC">Discontinued Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#dismissed">dismiss</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissal</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissed</a><span>, in § 5.6.2.3</span>
+   <li><a href="#def-Dissent">Dissent</a><span>, in § 5.2.1</span>
+   <li><a href="#distributed-meeting">distributed meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#editors-draft">ED</a><span>, in § 6.3.1</span>
+   <li><a href="#edited-recommendation">Edited Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#editors-draft">Editor Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#editorial-change">editorial change</a><span>, in § 6.2.3</span>
+   <li><a href="#editors-draft">Editor's Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#elected-group">elected groups</a><span>, in § 3.3</span>
+   <li><a href="#embedded-registry">embedded registry</a><span>, in § 6.5.2</span>
+   <li><a href="#erratum">errata</a><span>, in § 6.2.4</span>
+   <li><a href="#erratum">erratum</a><span>, in § 6.2.4</span>
+   <li><a href="#exclusion-draft">Exclusion Draft</a><span>, in § 4.3</span>
+   <li><a href="#exclusion-draft-charter">Exclusion Draft Charter</a><span>, in § 4.3</span>
+   <li><a href="#ftf-meeting">face-to-face meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#fpwd">First Public Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#formally-addressed">formally addressed</a><span>, in § 5.3</span>
+   <li><a href="#FormalObjection">Formal Objection</a><span>, in § 5.5</span>
+   <li><a href="#fully-addressed">fully addressed</a><span>, in § 5.6.2.7</span>
+   <li><a href="#good-standing">Good Standing</a><span>, in § 2.1.3</span>
+   <li><a href="#w3c-group">group</a><span>, in § 3</span>
+   <li><a href="#group-decision">group decision</a><span>, in § 5.1</span>
+   <li><a href="#WGNote">Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#WGNote">Interest Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsIG">Interest Groups</a><span>, in § 3.4</span>
+   <li><a href="#invited-expert-in-an-interest-group">Invited Expert in an Interest Group</a><span>, in § 3.4.3.4</span>
+   <li><a href="#invited-expert-in-a-working-group">Invited Expert in a Working Group</a><span>, in § 3.4.3.3</span>
+   <li><a href="#last-call">Last Call</a><span>, in § Unnumbered section</span>
+   <li><a href="#last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-review">Last Call for Review of Proposed Amendments</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#liaison">liaison</a><span>, in § 8</span>
+   <li><a href="#maturity-levels">Maturity level</a><span>, in § Unnumbered section</span>
+   <li><a href="#w3c-member">Member</a><span>, in § 2.1</span>
+   <li><a href="#member-association">Member Association</a><span>, in § 2.1.2.1</span>
+   <li><a href="#member-association">Member Associations</a><span>, in § 2.1.2.1</span>
+   <li><a href="#fdn-member-consortium">Member Consortium</a><span>, in § Unnumbered section</span>
+   <li><a href="#Member-only">Member-Only</a><span>, in § 7.2</span>
+   <li><a href="#member-representative-in-an-interest-group">Member representative in an Interest Group</a><span>, in § 3.4.3.2</span>
+   <li><a href="#member-representative-in-a-working-group">Member representative in a Working Group</a><span>, in § 3.4.3.1</span>
+   <li><a href="#MemberSubmission">Member Submission</a><span>, in § 9</span>
+   <li><a href="#mou">Memorandum of Understanding</a><span>, in § Unnumbered section</span>
+   <li><a href="#minor-changes">minor changes</a><span>, in § 4.4.2</span>
+   <li><a href="#minority-opinion">Minority Opinion</a><span>, in § 5.6.2.7</span>
+   <li><a href="#minutes">minutes</a><span>, in § 3.1.2.2</span>
+   <li><a href="#WGNote">Note</a><span>, in § 6.4.1</span>
+   <li><a href="#note-draft">Note Draft</a><span>, in § 6.4.1</span>
+   <li><a href="#not-required">not required</a><span>, in § Unnumbered section</span>
+   <li><a href="#RecsObs">Obsolete Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#obsolete-registry">Obsolete Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#other-charter">Other Charter</a><span>, in § Unnumbered section</span>
+   <li><a href="#overrule">overrule</a><span>, in § 5.6.2.7</span>
+   <li><a href="#participant">participant</a><span>, in § 3</span>
+   <li><a href="#igparticipant">participants in an Interest Group</a><span>, in § 3.4.2</span>
+   <li><a href="#wgparticipant">participants in a Working Group</a><span>, in § 3.4.2</span>
+   <li><a href="#inv-expert-info">participate in a Working Group as an Invited Expert</a><span>, in § 3.4.3.3</span>
+   <li><a href="#patent-review-drafts">Patent Review Drafts</a><span>, in § 6.3</span>
+   <li><a href="#primary-affiliation">primary affiliation</a><span>, in § 3.3.3.3</span>
+   <li><a href="#proposed-additions">proposed additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#proposed-amendments">proposed amendments</a><span>, in § 6.3.10.4</span>
+   <li><a href="#proposed-corrections">proposed corrections</a><span>, in § 6.3.10.4</span>
+   <li><a href="#RecsPR">Proposed Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#public-participant-ig">public participants</a><span>, in § 3.4.2</span>
+   <li><a href="#publishing">publish</a><span>, in § 6.2.1</span>
+   <li><a href="#RecsW3C">REC</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsW3C">Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">Recommendation-track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">Recommendation Track document</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">Recommendation-track document</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">REC Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">REC Track document</a><span>, in § 6.3</span>
+   <li><a href="#registry">registry</a><span>, in § 6.5</span>
+   <li><a href="#registry-change">registry change</a><span>, in § 6.2.3</span>
+   <li><a href="#registry-data">registry data</a><span>, in § 6.5</span>
+   <li><a href="#registry-data-report">Registry Data Report</a><span>, in § 6.5.4</span>
+   <li><a href="#registry-definition">registry definition</a><span>, in § 6.5.1</span>
+   <li><a href="#registry-draft">Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-entry">registry entry</a><span>, in § 6.5</span>
+   <li><a href="#registry-report">registry report</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-table">registry table</a><span>, in § 6.5</span>
+   <li><a href="#registry-track">Registry Track</a><span>, in § 6.5.2</span>
+   <li><a href="#rejected">rejected</a><span>, in § 9</span>
+   <li><a href="#related-member">Related Member</a><span>, in § 2.1.2.2</span>
+   <li><a href="#renounce">renounce</a><span>, in § 5.6.2.3</span>
+   <li><a href="#renounce">renunciation</a><span>, in § 5.6.2.3</span>
+   <li><a href="#rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#RescindedRec">Rescinded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#group-decision">resolution</a><span>, in § 5.1</span>
+   <li><a href="#statement">Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#submission-appeals">Submission Appeals</a><span>, in § 9</span>
+   <li><a href="#submitter">submitter</a><span>, in § 9</span>
+   <li><a href="#subsidiary">subsidiary</a><span>, in § 2.1.2.2</span>
+   <li><a href="#substantive-change">substantive change</a><span>, in § 6.2.3</span>
+   <li><a href="#mtg-substitute">substitute</a><span>, in § 3.4.2</span>
+   <li><a href="#RecsSup">Superseded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#superseded-registry">Superseded Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#supplemental-confidential-council-report">Supplemental Confidential Council Report</a><span>, in § 5.6.2.8</span>
+   <li><a href="#technical-architecture-group">TAG</a><span>, in § 3.3.2.1</span>
+   <li><a href="#WGNote">TAG Note</a><span>, in § 6.4.1</span>
+   <li><a href="#team">Team</a><span>, in § 2.2</span>
+   <li><a href="#TeamContact">Team Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#team-correction">Team correction</a><span>, in § 6.2.6</span>
+   <li><a href="#team-decision">Team Decision</a><span>, in § 5.1</span>
+   <li><a href="#Team-only">Team-Only</a><span>, in § 7.2</span>
+   <li><a href="#team-representative-in-an-interest-group">Team representative in an Interest Group</a><span>, in § 3.4.3.6</span>
+   <li><a href="#team-representative-in-a-working-group">Team representative in a Working Group</a><span>, in § 3.4.3.5</span>
+   <li><a href="#team-decision">Team's Decision</a><span>, in § 5.1</span>
+   <li><a href="#TeamSubmission">Team Submissions</a><span>, in § Unnumbered section</span>
+   <li><a href="#technical-agreement">technical agreement</a><span>, in § 8</span>
+   <li><a href="#technical-architecture-group">Technical Architecture Group</a><span>, in § 3.3.2.1</span>
+   <li><a href="#technical-report">Technical Report</a><span>, in § 6.2.1</span>
+   <li><a href="#trans-req">Transition Requests</a><span>, in § 6.3.3</span>
+   <li><a href="#def-Unanimity">Unanimity</a><span>, in § 5.2.1</span>
+   <li><a href="#update-requests">Update Requests</a><span>, in § 6.3.4</span>
+   <li><a href="#uphold">upheld</a><span>, in § 5.6.2.7</span>
+   <li><a href="#uphold">uphold</a><span>, in § 5.6.2.7</span>
+   <li><a href="#uphold">upholding</a><span>, in § 5.6.2.7</span>
+   <li><a href="#uphold">upholds</a><span>, in § 5.6.2.7</span>
+   <li><a href="#bod">W3C Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#RecsCR">W3C Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#def-W3CChair">W3C Chair</a><span>, in § Unnumbered section</span>
+   <li><a href="#w3c-council">W3C Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">W3C Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#def-w3c-decision">W3C decision</a><span>, in § 5.1</span>
+   <li><a href="#fellows">W3C Fellows</a><span>, in § 2.2</span>
+   <li><a href="#w3c-group">W3C Group</a><span>, in § 3</span>
+   <li><a href="#w3c-member">W3C Member</a><span>, in § 2.1</span>
+   <li><a href="#WGNote">W3C Note</a><span>, in § 6.4.1</span>
+   <li><a href="#RecsW3C">W3C Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">W3C Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">W3C Recommendation Track document</a><span>, in § 6.3</span>
+   <li><a href="#w3c-registry">W3C Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#statement">W3C Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#team">W3C Team</a><span>, in § 2.2</span>
+   <li><a href="#RecsWD">W3C Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsWD">WD</a><span>, in § 6.3.1</span>
+   <li><a href="#dfn-wide-review">wide review</a><span>, in § 6.2.2.1</span>
+   <li><a href="#RecsWD">Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#WGNote">Working Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsWG">Working Groups</a><span>, in § 3.4</span>
+   <li><a href="#EventsW">Workshop</a><span>, in § 2.1.1</span>
+  </ul>
+  <h3 class="no-num no-ref heading settled" id="index-defined-elsewhere"><span class="content">Terms defined by reference</span><a class="self-link" href="#index-defined-elsewhere"></a></h3>
+  <ul class="index">
+   <li>
+    <a data-link-type="biblio">[W3C-PATENT-POLICY]</a> defines the following terms:
+    <ul>
+     <li><span class="dfn-paneled" id="33fd2aef">Exclusion Opportunity</span>
+     <li><span class="dfn-paneled" id="74c78a1e">Patent Advisory Group</span>
+    </ul>
+  </ul>
+  <h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
+  <dl>
+   <dt id="biblio-coc">[COC]
+   <dd><a href="https://www.w3.org/policies/code-of-conduct/"><cite>W3C Code of Conduct</cite></a>. URL: <a href="https://www.w3.org/policies/code-of-conduct/">https://www.w3.org/policies/code-of-conduct/</a>
+   <dt id="biblio-collaborators-agreement">[COLLABORATORS-AGREEMENT]
+   <dd><a href="https://www.w3.org/invited-experts/agreement-2023/"><cite>Invited expert and collaborators agreement</cite></a>. URL: <a href="https://www.w3.org/invited-experts/agreement-2023/">https://www.w3.org/invited-experts/agreement-2023/</a>
+   <dt id="biblio-conflict-policy">[CONFLICT-POLICY]
+   <dd><a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/"><cite>Conflict of Interest Policy for the W3C Team</cite></a>. URL: <a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/">https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/</a>
+   <dt id="biblio-doc-license">[DOC-LICENSE]
+   <dd><a href="https://www.w3.org/copyright/document-license-2023/"><cite>W3C Document License</cite></a>. URL: <a href="https://www.w3.org/copyright/document-license-2023/">https://www.w3.org/copyright/document-license-2023/</a>
+   <dt id="biblio-patent-policy">[PATENT-POLICY]
+   <dd><a href="https://www.w3.org/policies/patent-policy/"><cite>The W3C Patent Policy</cite></a>. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
+   <dt id="biblio-patent-policy-2004">[PATENT-POLICY-2004]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy-20170801/"><cite>The W3C 2004 Patent Policy, Updated 2017</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy-20170801/">https://www.w3.org/Consortium/Patent-Policy-20170801/</a>
+   <dt id="biblio-patent-policy-2020">[PATENT-POLICY-2020]
+   <dd><a href="https://www.w3.org/policies/patent-policy/20200915/"><cite>The W3C 2020 Patent Policy</cite></a>. URL: <a href="https://www.w3.org/policies/patent-policy/20200915/">https://www.w3.org/policies/patent-policy/20200915/</a>
+   <dt id="biblio-pubrules">[PUBRULES]
+   <dd><a href="https://www.w3.org/pubrules/"><cite>Publication Rules</cite></a>. URL: <a href="https://www.w3.org/pubrules/">https://www.w3.org/pubrules/</a>
+   <dt id="biblio-rfc2119">[RFC2119]
+   <dd>S. Bradner. <a href="https://datatracker.ietf.org/doc/html/rfc2119"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. March 1997. Best Current Practice. URL: <a href="https://datatracker.ietf.org/doc/html/rfc2119">https://datatracker.ietf.org/doc/html/rfc2119</a>
+   <dt id="biblio-rfc3797">[RFC3797]
+   <dd>D. Eastlake 3rd. <a href="https://www.rfc-editor.org/rfc/rfc3797"><cite>Publicly Verifiable Nominations Committee (NomCom) Random Selection</cite></a>. June 2004. Informational. URL: <a href="https://www.rfc-editor.org/rfc/rfc3797">https://www.rfc-editor.org/rfc/rfc3797</a>
+   <dt id="biblio-w3c-patent-policy">[W3C-PATENT-POLICY]
+   <dd>Wendy Seltzer. <a href="https://www.w3.org/policies/patent-policy/"><cite>W3C Patent Policy</cite></a>. 15 September 2020. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
+  </dl>
+  <h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
+  <dl>
+   <dt id="biblio-ab-hp">[AB-HP]
+   <dd><a href="https://www.w3.org/2002/ab/"><cite>The Advisory Board home page</cite></a>. URL: <a href="https://www.w3.org/2002/ab/">https://www.w3.org/2002/ab/</a>
+   <dt id="biblio-ac-meeting">[AC-MEETING]
+   <dd><a href="https://www.w3.org/events/ac/"><cite>Advisory Committee meetings (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/events/ac/">https://www.w3.org/events/ac/</a>
+   <dt id="biblio-bg-cg">[BG-CG]
+   <dd><a href="https://www.w3.org/community/about/process/"><cite>Community and Business Group Process</cite></a>. URL: <a href="https://www.w3.org/community/about/process/">https://www.w3.org/community/about/process/</a>
+   <dt id="biblio-bylaws">[BYLAWS]
+   <dd><a href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a>. URL: <a href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf">https://www.w3.org/2024/09/25-w3c-bylaws.pdf</a>
+   <dt id="biblio-calendar">[CALENDAR]
+   <dd><a href="https://www.w3.org/events/"><cite>Calendar of all scheduled official W3C events</cite></a>. URL: <a href="https://www.w3.org/events/">https://www.w3.org/events/</a>
+   <dt id="biblio-chair">[CHAIR]
+   <dd><a href="https://www.w3.org/guide/chair/role"><cite>W3C Working/Interest Group Chair</cite></a>. URL: <a href="https://www.w3.org/guide/chair/role">https://www.w3.org/guide/chair/role</a>
+   <dt id="biblio-charter">[CHARTER]
+   <dd><a href="https://www.w3.org/guide/process/charter"><cite>How to Create a Working Group or Interest Group</cite></a>. URL: <a href="https://www.w3.org/guide/process/charter">https://www.w3.org/guide/process/charter</a>
+   <dt id="biblio-council-report-index">[COUNCIL-REPORT-INDEX]
+   <dd><a href="https://www.w3.org/about/council/"><cite>Council Report Index</cite></a>. URL: <a href="https://www.w3.org/about/council/">https://www.w3.org/about/council/</a>
+   <dt id="biblio-current-ac">[CURRENT-AC]
+   <dd><a href="https://www.w3.org/Member/ACList"><cite>Current Advisory Committee representatives (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/ACList">https://www.w3.org/Member/ACList</a>
+   <dt id="biblio-decision-appeal">[DECISION-APPEAL]
+   <dd><a href="https://www.w3.org/guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a>. URL: <a href="https://www.w3.org/guide/process/ac-appeal">https://www.w3.org/guide/process/ac-appeal</a>
+   <dt id="biblio-election-howto">[ELECTION-HOWTO]
+   <dd><a href="https://www.w3.org/guide/process/election"><cite>How to Organize an Advisory Board or TAG election</cite></a>. URL: <a href="https://www.w3.org/guide/process/election">https://www.w3.org/guide/process/election</a>
+   <dt id="biblio-fellows">[FELLOWS]
+   <dd><a href="https://www.w3.org/careers/fellows/"><cite>W3C Fellows Program</cite></a>. URL: <a href="https://www.w3.org/careers/fellows/">https://www.w3.org/careers/fellows/</a>
+   <dt id="biblio-group-mail">[GROUP-MAIL]
+   <dd><a href="https://www.w3.org/groups/"><cite>Group mailing lists</cite></a>. URL: <a href="https://www.w3.org/groups/">https://www.w3.org/groups/</a>
+   <dt id="biblio-guide">[GUIDE]
+   <dd><a href="https://www.w3.org/guide/"><cite>The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators</cite></a>. URL: <a href="https://www.w3.org/guide/">https://www.w3.org/guide/</a>
+   <dt id="biblio-intro">[INTRO]
+   <dd><a href="https://www.w3.org/Member/Intro"><cite>Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/Intro">https://www.w3.org/Member/Intro</a>
+   <dt id="biblio-join">[JOIN]
+   <dd><a href="https://www.w3.org/membership/join/"><cite>How to Join W3C</cite></a>. URL: <a href="https://www.w3.org/membership/join/">https://www.w3.org/membership/join/</a>
+   <dt id="biblio-liaison">[LIAISON]
+   <dd><a href="https://www.w3.org/liaisons/"><cite>W3C liaisons with other organizations</cite></a>. URL: <a href="https://www.w3.org/liaisons/">https://www.w3.org/liaisons/</a>
+   <dt id="biblio-member-agreement">[MEMBER-AGREEMENT]
+   <dd><a href="https://www.w3.org/membership/agreement/"><cite>W3C Membership Agreement</cite></a>. URL: <a href="https://www.w3.org/membership/agreement/">https://www.w3.org/membership/agreement/</a>
+   <dt id="biblio-member-hp">[MEMBER-HP]
+   <dd><a href="https://www.w3.org/Member/"><cite>Member website (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/">https://www.w3.org/Member/</a>
+   <dt id="biblio-member-list">[MEMBER-LIST]
+   <dd><a href="https://www.w3.org/membership/list/"><cite>The list of current W3C Members</cite></a>. URL: <a href="https://www.w3.org/membership/list/">https://www.w3.org/membership/list/</a>
+   <dt id="biblio-member-sub">[MEMBER-SUB]
+   <dd><a href="https://www.w3.org/submissions/guide/"><cite>Member submissions guidebook</cite></a>. URL: <a href="https://www.w3.org/submissions/guide/">https://www.w3.org/submissions/guide/</a>
+   <dt id="biblio-mission">[MISSION]
+   <dd><a href="https://www.w3.org/mission/"><cite>The W3C Mission statement</cite></a>. URL: <a href="https://www.w3.org/mission/">https://www.w3.org/mission/</a>
+   <dt id="biblio-obs-resc">[OBS-RESC]
+   <dd><a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded"><cite>Obsoleting and Rescinding W3C Specifications</cite></a>. URL: <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">https://www.w3.org/guide/process/obsolete-rescinded-supserseded</a>
+   <dt id="biblio-rec-tips">[REC-TIPS]
+   <dd><a href="https://www.w3.org/guide/standards-track/rec-tips"><cite>Tips for Getting to Recommendation Faster</cite></a>. URL: <a href="https://www.w3.org/guide/standards-track/rec-tips">https://www.w3.org/guide/standards-track/rec-tips</a>
+   <dt id="biblio-republishing">[REPUBLISHING]
+   <dd><a href="https://www.w3.org/guide/standards-track/republishing"><cite>In-place modification of W3C Technical Reports</cite></a>. URL: <a href="https://www.w3.org/guide/standards-track/republishing">https://www.w3.org/guide/standards-track/republishing</a>
+   <dt id="biblio-submission-list">[SUBMISSION-LIST]
+   <dd><a href="https://www.w3.org/submissions/"><cite>The list of acknowledged Member Submissions</cite></a>. URL: <a href="https://www.w3.org/submissions/">https://www.w3.org/submissions/</a>
+   <dt id="biblio-tag-hp">[TAG-HP]
+   <dd><a href="https://www.w3.org/2001/tag/"><cite>The TAG home page</cite></a>. URL: <a href="https://www.w3.org/2001/tag/">https://www.w3.org/2001/tag/</a>
+   <dt id="biblio-team-contact">[TEAM-CONTACT]
+   <dd><a href="https://www.w3.org/guide/teamcontact/role"><cite>Role of the Team Contact</cite></a>. URL: <a href="https://www.w3.org/guide/teamcontact/role">https://www.w3.org/guide/teamcontact/role</a>
+   <dt id="biblio-tr">[TR]
+   <dd><a href="https://www.w3.org/TR/"><cite>The W3C technical reports index</cite></a>. URL: <a href="https://www.w3.org/TR/">https://www.w3.org/TR/</a>
+   <dt id="biblio-transition">[TRANSITION]
+   <dd><a href="https://www.w3.org/guide/transitions/"><cite>Organize a Technical Report Transition</cite></a>. URL: <a href="https://www.w3.org/guide/transitions/">https://www.w3.org/guide/transitions/</a>
+   <dt id="biblio-translation">[TRANSLATION]
+   <dd><a href="https://www.w3.org/Consortium/Translation/"><cite>Translations of W3C technical reports</cite></a>. URL: <a href="https://www.w3.org/Consortium/Translation/">https://www.w3.org/Consortium/Translation/</a>
+   <dt id="biblio-w3c-ipr">[W3C-IPR]
+   <dd><a href="https://www.w3.org/policies/"><cite>W3C IPR Policies</cite></a>. URL: <a href="https://www.w3.org/policies/">https://www.w3.org/policies/</a>
+  </dl>
+<script>/* Boilerplate: script-dom-helper */
+"use strict";
+function query(sel) { return document.querySelector(sel); }
+
+function queryAll(sel) { return [...document.querySelectorAll(sel)]; }
+
+function iter(obj) {
+	if(!obj) return [];
+	var it = obj[Symbol.iterator];
+	if(it) return it;
+	return Object.entries(obj);
+}
+
+function mk(tagname, attrs, ...children) {
+	const el = document.createElement(tagname);
+	for(const [k,v] of iter(attrs)) {
+		if(k.slice(0,3) == "_on") {
+			const eventName = k.slice(3);
+			el.addEventListener(eventName, v);
+		} else if(k[0] == "_") {
+			// property, not attribute
+			el[k.slice(1)] = v;
+		} else {
+			if(v === false || v == null) {
+        continue;
+      } else if(v === true) {
+        el.setAttribute(k, "");
+        continue;
+      } else {
+  			el.setAttribute(k, v);
+      }
+		}
+	}
+	append(el, children);
+	return el;
+}
+
+/* Create shortcuts for every known HTML element */
+[
+  "a",
+  "abbr",
+  "acronym",
+  "address",
+  "applet",
+  "area",
+  "article",
+  "aside",
+  "audio",
+  "b",
+  "base",
+  "basefont",
+  "bdo",
+  "big",
+  "blockquote",
+  "body",
+  "br",
+  "button",
+  "canvas",
+  "caption",
+  "center",
+  "cite",
+  "code",
+  "col",
+  "colgroup",
+  "datalist",
+  "dd",
+  "del",
+  "details",
+  "dfn",
+  "dialog",
+  "div",
+  "dl",
+  "dt",
+  "em",
+  "embed",
+  "fieldset",
+  "figcaption",
+  "figure",
+  "font",
+  "footer",
+  "form",
+  "frame",
+  "frameset",
+  "head",
+  "header",
+  "h1",
+  "h2",
+  "h3",
+  "h4",
+  "h5",
+  "h6",
+  "hr",
+  "html",
+  "i",
+  "iframe",
+  "img",
+  "input",
+  "ins",
+  "kbd",
+  "label",
+  "legend",
+  "li",
+  "link",
+  "main",
+  "map",
+  "mark",
+  "meta",
+  "meter",
+  "nav",
+  "nobr",
+  "noscript",
+  "object",
+  "ol",
+  "optgroup",
+  "option",
+  "output",
+  "p",
+  "param",
+  "pre",
+  "progress",
+  "q",
+  "s",
+  "samp",
+  "script",
+  "section",
+  "select",
+  "small",
+  "source",
+  "span",
+  "strike",
+  "strong",
+  "style",
+  "sub",
+  "summary",
+  "sup",
+  "table",
+  "tbody",
+  "td",
+  "template",
+  "textarea",
+  "tfoot",
+  "th",
+  "thead",
+  "time",
+  "title",
+  "tr",
+  "u",
+  "ul",
+  "var",
+  "video",
+  "wbr",
+  "xmp",
+].forEach(tagname=>{
+	mk[tagname] = (...args) => mk(tagname, ...args);
+});
+
+function* nodesFromChildList(children) {
+	for(const child of children.flat(Infinity)) {
+		if(child instanceof Node) {
+			yield child;
+		} else {
+			yield new Text(child);
+		}
+	}
+}
+function append(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		if(el instanceof Node) el.appendChild(child);
+		else el.push(child);
+	}
+	return el;
+}
+
+function insertAfter(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		el.parentNode.insertBefore(child, el.nextSibling);
+	}
+	return el;
+}
+
+function clearContents(el) {
+	el.innerHTML = "";
+	return el;
+}
+
+function parseHTML(markup) {
+	if(markup.toLowerCase().trim().indexOf('<!doctype') === 0) {
+		const doc = document.implementation.createHTMLDocument("");
+		doc.documentElement.innerHTML = markup;
+		return doc;
+	} else {
+		const el = mk.template({});
+		el.innerHTML = markup;
+		return el.content;
+	}
+}</script>
+<script>/* Boilerplate: script-dfn-panel */
+"use strict";
+{
+let dfnPanelData = {
+"33fd2aef": {"dfnID":"33fd2aef","dfnText":"Exclusion Opportunity","external":true,"refSections":[{"refs":[{"id":"ref-for-exclusion-opportunity"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
+"74c78a1e": {"dfnID":"74c78a1e","dfnText":"Patent Advisory Group","external":true,"refSections":[{"refs":[{"id":"ref-for-patent-advisory-group"}],"title":"4.7. \nChartered Group Closure"}],"url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
+"EventsW": {"dfnID":"EventsW","dfnText":"Workshop","external":false,"refSections":[{"refs":[{"id":"ref-for-EventsW"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-EventsW\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-EventsW\u2461"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-EventsW\u2462"}],"title":"7.1. \nPublic Communication"}],"url":"#EventsW"},
+"FormalObjection": {"dfnID":"FormalObjection","dfnText":"Formal Objection","external":false,"refSections":[{"refs":[{"id":"ref-for-FormalObjection"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-FormalObjection\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-FormalObjection\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-FormalObjection\u2462"},{"id":"ref-for-FormalObjection\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-FormalObjection\u2464"}],"title":"5. \nDecisions"},{"refs":[{"id":"ref-for-FormalObjection\u2465"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-FormalObjection\u2466"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-FormalObjection\u2467"},{"id":"ref-for-FormalObjection\u2468"},{"id":"ref-for-FormalObjection\u2460\u24ea"},{"id":"ref-for-FormalObjection\u2460\u2460"},{"id":"ref-for-FormalObjection\u2460\u2461"},{"id":"ref-for-FormalObjection\u2460\u2462"},{"id":"ref-for-FormalObjection\u2460\u2463"},{"id":"ref-for-FormalObjection\u2460\u2464"},{"id":"ref-for-FormalObjection\u2460\u2465"},{"id":"ref-for-FormalObjection\u2460\u2466"},{"id":"ref-for-FormalObjection\u2460\u2467"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-FormalObjection\u2460\u2468"},{"id":"ref-for-FormalObjection\u2461\u24ea"},{"id":"ref-for-FormalObjection\u2461\u2460"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2461"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2462"},{"id":"ref-for-FormalObjection\u2461\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2464"},{"id":"ref-for-FormalObjection\u2461\u2465"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2466"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2468"},{"id":"ref-for-FormalObjection\u2462\u24ea"},{"id":"ref-for-FormalObjection\u2462\u2460"},{"id":"ref-for-FormalObjection\u2462\u2461"},{"id":"ref-for-FormalObjection\u2462\u2462"},{"id":"ref-for-FormalObjection\u2462\u2463"},{"id":"ref-for-FormalObjection\u2462\u2464"},{"id":"ref-for-FormalObjection\u2462\u2465"},{"id":"ref-for-FormalObjection\u2462\u2466"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2468"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u24ea"},{"id":"ref-for-FormalObjection\u2463\u2460"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2461"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2462"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2463"}],"title":"9. \nMember Submissions"}],"url":"#FormalObjection"},
+"GeneralChairs": {"dfnID":"GeneralChairs","dfnText":"Chair","external":false,"refSections":[{"refs":[{"id":"ref-for-GeneralChairs"}],"title":"3.1.1.2. \nConflict of Interest Policy"},{"refs":[{"id":"ref-for-GeneralChairs\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-GeneralChairs\u2461"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-GeneralChairs\u2462"},{"id":"ref-for-GeneralChairs\u2463"},{"id":"ref-for-GeneralChairs\u2464"},{"id":"ref-for-GeneralChairs\u2465"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-GeneralChairs\u2466"},{"id":"ref-for-GeneralChairs\u2467"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GeneralChairs\u2468"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u24ea"},{"id":"ref-for-GeneralChairs\u2460\u2460"},{"id":"ref-for-GeneralChairs\u2460\u2461"},{"id":"ref-for-GeneralChairs\u2460\u2462"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2464"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2465"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2466"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2467"},{"id":"ref-for-GeneralChairs\u2460\u2468"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u24ea"},{"id":"ref-for-GeneralChairs\u2461\u2460"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2461"},{"id":"ref-for-GeneralChairs\u2461\u2462"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2463"},{"id":"ref-for-GeneralChairs\u2461\u2464"}],"title":"5.2.3. \nDeciding by Vote"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2465"},{"id":"ref-for-GeneralChairs\u2461\u2466"}],"title":"5.4. \nReopening a Decision When Presented With New Information"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2467"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2468"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-GeneralChairs\u2462\u24ea"},{"id":"ref-for-GeneralChairs\u2462\u2460"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-GeneralChairs\u2462\u2461"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#GeneralChairs"},
+"GroupsIG": {"dfnID":"GroupsIG","dfnText":"Interest Groups","external":false,"refSections":[{"refs":[{"id":"ref-for-GroupsIG"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-GroupsIG"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-GroupsIG\u2460"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GroupsIG\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-GroupsIG\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-GroupsIG\u2463"},{"id":"ref-for-GroupsIG\u2464"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GroupsIG\u2465"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-GroupsIG\u2466"},{"id":"ref-for-GroupsIG\u2467"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GroupsIG\u2468"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-GroupsIG\u2460\u24ea"},{"id":"ref-for-GroupsIG\u2460\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsIG\u2460\u2461"}],"title":"6.4.1. \nGroup Notes"}],"url":"#GroupsIG"},
+"GroupsWG": {"dfnID":"GroupsWG","dfnText":"Working Groups","external":false,"refSections":[{"refs":[{"id":"ref-for-GroupsWG"},{"id":"ref-for-GroupsWG\u2460"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-GroupsWG\u2461"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-GroupsWG\u2462"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-GroupsWG"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-GroupsWG\u2463"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GroupsWG\u2464"},{"id":"ref-for-GroupsWG\u2465"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-GroupsWG\u2466"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-GroupsWG\u2467"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-GroupsWG\u2468"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u24ea"},{"id":"ref-for-GroupsWG\u2460\u2460"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2461"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2462"},{"id":"ref-for-GroupsWG\u2460\u2463"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2464"}],"title":"6. \nW3C Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2465"},{"id":"ref-for-GroupsWG\u2460\u2466"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2467"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2468"},{"id":"ref-for-GroupsWG\u2461\u24ea"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2460"},{"id":"ref-for-GroupsWG\u2461\u2461"},{"id":"ref-for-GroupsWG\u2461\u2462"},{"id":"ref-for-GroupsWG\u2461\u2463"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2464"},{"id":"ref-for-GroupsWG\u2461\u2465"},{"id":"ref-for-GroupsWG\u2461\u2466"},{"id":"ref-for-GroupsWG\u2461\u2467"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2468"},{"id":"ref-for-GroupsWG\u2462\u24ea"},{"id":"ref-for-GroupsWG\u2462\u2460"},{"id":"ref-for-GroupsWG\u2462\u2461"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2462\u2462"},{"id":"ref-for-GroupsWG\u2462\u2463"},{"id":"ref-for-GroupsWG\u2462\u2464"},{"id":"ref-for-GroupsWG\u2462\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2462\u2466"},{"id":"ref-for-GroupsWG\u2462\u2467"},{"id":"ref-for-GroupsWG\u2462\u2468"},{"id":"ref-for-GroupsWG\u2463\u24ea"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2460"},{"id":"ref-for-GroupsWG\u2463\u2461"},{"id":"ref-for-GroupsWG\u2463\u2462"},{"id":"ref-for-GroupsWG\u2463\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2464"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2465"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2466"},{"id":"ref-for-GroupsWG\u2463\u2467"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2468"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u24ea"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2460"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2462"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2463"},{"id":"ref-for-GroupsWG\u2464\u2464"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2465"},{"id":"ref-for-GroupsWG\u2464\u2466"},{"id":"ref-for-GroupsWG\u2464\u2467"},{"id":"ref-for-GroupsWG\u2464\u2468"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u24ea"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2460"}],"title":"6.3.12. \nRetiring Recommendation Track Documents"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2461"},{"id":"ref-for-GroupsWG\u2465\u2462"},{"id":"ref-for-GroupsWG\u2465\u2463"},{"id":"ref-for-GroupsWG\u2465\u2464"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2465"},{"id":"ref-for-GroupsWG\u2465\u2466"},{"id":"ref-for-GroupsWG\u2465\u2467"},{"id":"ref-for-GroupsWG\u2465\u2468"},{"id":"ref-for-GroupsWG\u2466\u24ea"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2460"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2462"},{"id":"ref-for-GroupsWG\u2466\u2463"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2464"}],"title":"10. \nProcess Evolution"}],"url":"#GroupsWG"},
+"Member-only": {"dfnID":"Member-only","dfnText":"Member-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Member-only"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-Member-only"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-Member-only"},{"id":"ref-for-Member-only"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-Member-only"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-Member-only\u2460"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-Member-only\u2461"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Member-only\u2462"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-Member-only\u2463"},{"id":"ref-for-Member-only\u2464"},{"id":"ref-for-Member-only\u2465"},{"id":"ref-for-Member-only\u2466"},{"id":"ref-for-Member-only\u2467"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Member-only\u2468"},{"id":"ref-for-Member-only\u2460\u24ea"},{"id":"ref-for-Member-only\u2460\u2460"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Member-only"},
+"MemberSubmission": {"dfnID":"MemberSubmission","dfnText":"Member Submission","external":false,"refSections":[{"refs":[{"id":"ref-for-MemberSubmission"},{"id":"ref-for-MemberSubmission\u2460"},{"id":"ref-for-MemberSubmission\u2461"},{"id":"ref-for-MemberSubmission\u2462"}],"title":"9. \nMember Submissions"}],"url":"#MemberSubmission"},
+"RecsCR": {"dfnID":"RecsCR","dfnText":"Candidate Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsCR"},{"id":"ref-for-RecsCR\u2460"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-RecsCR\u2461"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-RecsCR\u2462"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsCR\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-RecsCR\u2464"},{"id":"ref-for-RecsCR\u2465"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2466"},{"id":"ref-for-RecsCR\u2467"},{"id":"ref-for-RecsCR\u2468"},{"id":"ref-for-RecsCR\u2460\u24ea"},{"id":"ref-for-RecsCR\u2460\u2460"},{"id":"ref-for-RecsCR\u2460\u2461"},{"id":"ref-for-RecsCR\u2460\u2462"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2463"},{"id":"ref-for-RecsCR\u2460\u2464"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2467"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2468"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-RecsCR\u2461\u24ea"}],"title":"6.3.12.2. \nRescinding a Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2461\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsCR"},
+"RecsObs": {"dfnID":"RecsObs","dfnText":"Obsolete Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsObs"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsObs\u2460"},{"id":"ref-for-RecsObs\u2461"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsObs\u2462"},{"id":"ref-for-RecsObs\u2463"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RecsObs\u2464"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsObs"},
+"RecsPR": {"dfnID":"RecsPR","dfnText":"Proposed Recommendation","external":false,"refSections":[],"url":"#RecsPR"},
+"RecsSup": {"dfnID":"RecsSup","dfnText":"Superseded Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsSup"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsSup\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsSup"},
+"RecsW3C": {"dfnID":"RecsW3C","dfnText":"W3C Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsW3C"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-RecsW3C"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-RecsW3C\u2460"},{"id":"ref-for-RecsW3C\u2461"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-RecsW3C\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-RecsW3C\u2463"},{"id":"ref-for-RecsW3C\u2464"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-RecsW3C\u2465"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsW3C\u2466"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-RecsW3C\u2467"},{"id":"ref-for-RecsW3C"},{"id":"ref-for-RecsW3C\u2468"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2460\u24ea"},{"id":"ref-for-RecsW3C\u2460\u2460"},{"id":"ref-for-RecsW3C\u2460\u2461"},{"id":"ref-for-RecsW3C\u2460\u2462"},{"id":"ref-for-RecsW3C\u2460\u2463"},{"id":"ref-for-RecsW3C\u2460\u2464"},{"id":"ref-for-RecsW3C\u2460\u2465"},{"id":"ref-for-RecsW3C\u2460\u2466"},{"id":"ref-for-RecsW3C\u2460\u2467"},{"id":"ref-for-RecsW3C\u2460\u2468"},{"id":"ref-for-RecsW3C\u2461\u24ea"},{"id":"ref-for-RecsW3C\u2461\u2460"},{"id":"ref-for-RecsW3C\u2461\u2461"},{"id":"ref-for-RecsW3C\u2461\u2462"},{"id":"ref-for-RecsW3C\u2461\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2464"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2467"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2468"},{"id":"ref-for-RecsW3C\u2462\u24ea"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2460"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2461"},{"id":"ref-for-RecsW3C\u2462\u2462"},{"id":"ref-for-RecsW3C\u2462\u2463"},{"id":"ref-for-RecsW3C\u2462\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2465"},{"id":"ref-for-RecsW3C\u2462\u2466"}],"title":"6.3.9.4. \nNext Steps from W3C Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2467"},{"id":"ref-for-RecsW3C\u2462\u2468"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-RecsW3C\u2463\u24ea"},{"id":"ref-for-RecsW3C\u2463\u2460"},{"id":"ref-for-RecsW3C\u2463\u2461"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-RecsW3C\u2463\u2462"},{"id":"ref-for-RecsW3C\u2463\u2463"},{"id":"ref-for-RecsW3C\u2463\u2464"},{"id":"ref-for-RecsW3C\u2463\u2465"},{"id":"ref-for-RecsW3C\u2463\u2466"},{"id":"ref-for-RecsW3C\u2463\u2467"},{"id":"ref-for-RecsW3C\u2463\u2468"},{"id":"ref-for-RecsW3C\u2464\u24ea"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2460"},{"id":"ref-for-RecsW3C\u2464\u2461"},{"id":"ref-for-RecsW3C\u2464\u2462"},{"id":"ref-for-RecsW3C\u2464\u2463"},{"id":"ref-for-RecsW3C\u2464\u2464"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2465"}],"title":"6.3.12.2. \nRescinding a Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2466"},{"id":"ref-for-RecsW3C\u2464\u2467"},{"id":"ref-for-RecsW3C\u2464\u2468"},{"id":"ref-for-RecsW3C\u2465\u24ea"},{"id":"ref-for-RecsW3C\u2465\u2460"},{"id":"ref-for-RecsW3C\u2465\u2461"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2465\u2462"},{"id":"ref-for-RecsW3C\u2465\u2463"},{"id":"ref-for-RecsW3C\u2465\u2464"},{"id":"ref-for-RecsW3C\u2465\u2465"},{"id":"ref-for-RecsW3C\u2465\u2466"},{"id":"ref-for-RecsW3C\u2465\u2467"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2465\u2468"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u24ea"},{"id":"ref-for-RecsW3C\u2466\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2461"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2462"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#RecsW3C"},
+"RecsWD": {"dfnID":"RecsWD","dfnText":"Working Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsWD"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-RecsWD\u2460"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsWD\u2461"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsWD\u2462"},{"id":"ref-for-RecsWD\u2463"},{"id":"ref-for-RecsWD\u2464"},{"id":"ref-for-RecsWD\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsWD\u2466"},{"id":"ref-for-RecsWD\u2467"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-RecsWD\u2468"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-RecsWD\u2460\u24ea"},{"id":"ref-for-RecsWD\u2460\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-RecsWD\u2460\u2461"},{"id":"ref-for-RecsWD\u2460\u2462"},{"id":"ref-for-RecsWD\u2460\u2463"}],"title":"6.6. \nSwitching Tracks"}],"url":"#RecsWD"},
+"RescindedRec": {"dfnID":"RescindedRec","dfnText":"Rescinded Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RescindedRec"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RescindedRec\u2460"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RescindedRec\u2461"},{"id":"ref-for-RescindedRec\u2462"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RescindedRec\u2463"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RescindedRec"},
+"Team-only": {"dfnID":"Team-only","dfnText":"Team-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Team-only"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-Team-only"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Team-only\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Team-only\u2461"},{"id":"ref-for-Team-only\u2462"},{"id":"ref-for-Team-only\u2463"},{"id":"ref-for-Team-only\u2464"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Team-only"},
+"TeamContact": {"dfnID":"TeamContact","dfnText":"Team Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-TeamContact"},{"id":"ref-for-TeamContact\u2460"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2461"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2462"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2463"},{"id":"ref-for-TeamContact\u2464"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-TeamContact\u2465"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-TeamContact\u2466"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-TeamContact"}],"title":"5.5. \nRegistering Formal Objections"}],"url":"#TeamContact"},
+"TeamSubmission": {"dfnID":"TeamSubmission","dfnText":"Team Submissions","external":false,"refSections":[],"url":"#TeamSubmission"},
+"WGNote": {"dfnID":"WGNote","dfnText":"Group Note","external":false,"refSections":[{"refs":[{"id":"ref-for-WGNote"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-WGNote"},{"id":"ref-for-WGNote\u2460"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-WGNote\u2461"},{"id":"ref-for-WGNote\u2462"},{"id":"ref-for-WGNote\u2463"},{"id":"ref-for-WGNote\u2464"},{"id":"ref-for-WGNote\u2465"},{"id":"ref-for-WGNote\u2466"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-WGNote\u2467"},{"id":"ref-for-WGNote\u2468"},{"id":"ref-for-WGNote\u2460\u24ea"},{"id":"ref-for-WGNote\u2460\u2460"},{"id":"ref-for-WGNote\u2460\u2461"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-WGNote\u2460\u2462"},{"id":"ref-for-WGNote\u2460\u2463"},{"id":"ref-for-WGNote\u2460\u2464"},{"id":"ref-for-WGNote\u2460\u2465"},{"id":"ref-for-WGNote\u2460\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#WGNote"},
+"acknowledged": {"dfnID":"acknowledged","dfnText":"acknowledged","external":false,"refSections":[{"refs":[{"id":"ref-for-acknowledged"},{"id":"ref-for-acknowledged\u2460"}],"title":"9. \nMember Submissions"}],"url":"#acknowledged"},
+"adequate-implementation": {"dfnID":"adequate-implementation","dfnText":"adequate implementation experience","external":false,"refSections":[{"refs":[{"id":"ref-for-adequate-implementation"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-adequate-implementation\u2460"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-adequate-implementation\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-adequate-implementation\u2462"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#adequate-implementation"},
+"adopted-draft": {"dfnID":"adopted-draft","dfnText":"Adopted Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-adopted-draft"}],"title":"4.3. \nContent of a Charter"}],"url":"#adopted-draft"},
+"advisory-board": {"dfnID":"advisory-board","dfnText":"Advisory Board","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-board"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-advisory-board\u2460"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-advisory-board\u2461"},{"id":"ref-for-advisory-board\u2462"},{"id":"ref-for-advisory-board\u2463"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2464"},{"id":"ref-for-advisory-board\u2465"},{"id":"ref-for-advisory-board\u2466"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2467"}],"title":"3.3.1.3. \nCommunications of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2468"},{"id":"ref-for-advisory-board\u2460\u24ea"},{"id":"ref-for-advisory-board\u2460\u2460"}],"title":"3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2461"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2462"},{"id":"ref-for-advisory-board\u2460\u2463"},{"id":"ref-for-advisory-board\u2460\u2464"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2465"},{"id":"ref-for-advisory-board\u2460\u2466"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2467"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2468"}],"title":"3.3.3.5. \nVerifiable Random Selection Procedure"},{"refs":[{"id":"ref-for-advisory-board\u2461\u24ea"},{"id":"ref-for-advisory-board\u2461\u2460"},{"id":"ref-for-advisory-board\u2461\u2461"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2462"},{"id":"ref-for-advisory-board\u2461\u2463"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2464"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2465"},{"id":"ref-for-advisory-board\u2461\u2466"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2467"},{"id":"ref-for-advisory-board\u2461\u2468"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-advisory-board\u2462\u24ea"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2460"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2461"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2462"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2463"},{"id":"ref-for-advisory-board\u2462\u2464"},{"id":"ref-for-advisory-board\u2462\u2465"},{"id":"ref-for-advisory-board\u2462\u2466"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-board"},
+"advisory-committee": {"dfnID":"advisory-committee","dfnText":"Advisory Committee","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-advisory-committee\u2460"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee\u2461"},{"id":"ref-for-advisory-committee\u2462"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-advisory-committee\u2463"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-advisory-committee\u2464"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-advisory-committee\u2465"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-committee\u2466"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-advisory-committee\u2467"},{"id":"ref-for-advisory-committee\u2468"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u24ea"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2460"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2461"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2462"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2464"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2465"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2466"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2467"},{"id":"ref-for-advisory-committee\u2460\u2468"},{"id":"ref-for-advisory-committee\u2461\u24ea"},{"id":"ref-for-advisory-committee\u2461\u2460"},{"id":"ref-for-advisory-committee\u2461\u2461"},{"id":"ref-for-advisory-committee\u2461\u2462"},{"id":"ref-for-advisory-committee\u2461\u2463"},{"id":"ref-for-advisory-committee\u2461\u2464"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-advisory-committee\u2461\u2465"},{"id":"ref-for-advisory-committee\u2461\u2466"}],"title":"5.8. \nAdvisory Committee Votes"},{"refs":[{"id":"ref-for-advisory-committee\u2461\u2467"},{"id":"ref-for-advisory-committee\u2461\u2468"},{"id":"ref-for-advisory-committee\u2462\u24ea"},{"id":"ref-for-advisory-committee\u2462\u2460"},{"id":"ref-for-advisory-committee\u2462\u2461"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2462"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2463"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2464"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2466"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2467"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2468"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee\u2463\u24ea"},{"id":"ref-for-advisory-committee\u2463\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee\u2463\u2461"},{"id":"ref-for-advisory-committee\u2463\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-committee"},
+"advisory-committee-appeal": {"dfnID":"advisory-committee-appeal","dfnText":"Advisory Committee Appeal","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-appeal"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2461"}],"title":"5.8. \nAdvisory Committee Votes"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2462"},{"id":"ref-for-advisory-committee-appeal\u2463"},{"id":"ref-for-advisory-committee-appeal\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2468"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u24ea"},{"id":"ref-for-advisory-committee-appeal\u2460\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u2461"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-committee-appeal"},
+"advisory-committee-representative": {"dfnID":"advisory-committee-representative","dfnText":"representative","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-representative"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460"}],"title":"3.1.1.3. \nIndividuals Representing a Member Organization"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461"},{"id":"ref-for-advisory-committee-representative\u2462"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2463"},{"id":"ref-for-advisory-committee-representative\u2464"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2465"},{"id":"ref-for-advisory-committee-representative\u2466"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2467"},{"id":"ref-for-advisory-committee-representative\u2468"},{"id":"ref-for-advisory-committee-representative\u2460\u24ea"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2460"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2461"}],"title":"3.4.3.2. \nMember Representative in an Interest Group"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2462"},{"id":"ref-for-advisory-committee-representative\u2460\u2463"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2464"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2465"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2466"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2468"},{"id":"ref-for-advisory-committee-representative\u2461\u24ea"},{"id":"ref-for-advisory-committee-representative\u2461\u2460"},{"id":"ref-for-advisory-committee-representative\u2461\u2461"},{"id":"ref-for-advisory-committee-representative\u2461\u2462"},{"id":"ref-for-advisory-committee-representative\u2461\u2463"},{"id":"ref-for-advisory-committee-representative\u2461\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2468"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u24ea"},{"id":"ref-for-advisory-committee-representative\u2462\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2461"}],"title":"7.3. \nChanging Confidentiality Level"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2462"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2463"},{"id":"ref-for-advisory-committee-representative\u2462\u2464"},{"id":"ref-for-advisory-committee-representative\u2462\u2465"}],"title":"9. \nMember Submissions"}],"url":"#advisory-committee-representative"},
+"advisory-committee-review": {"dfnID":"advisory-committee-review","dfnText":"Advisory Committee review","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-review"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460"},{"id":"ref-for-advisory-committee-review\u2461"},{"id":"ref-for-advisory-committee-review\u2462"},{"id":"ref-for-advisory-committee-review\u2463"},{"id":"ref-for-advisory-committee-review\u2464"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-review\u2465"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-advisory-committee-review\u2466"},{"id":"ref-for-advisory-committee-review\u2467"},{"id":"ref-for-advisory-committee-review\u2468"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u24ea"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2460"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2461"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2462"},{"id":"ref-for-advisory-committee-review\u2460\u2463"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2464"},{"id":"ref-for-advisory-committee-review\u2460\u2465"},{"id":"ref-for-advisory-committee-review\u2460\u2466"},{"id":"ref-for-advisory-committee-review\u2460\u2467"},{"id":"ref-for-advisory-committee-review\u2460\u2468"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u24ea"},{"id":"ref-for-advisory-committee-review\u2461\u2460"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2462"},{"id":"ref-for-advisory-committee-review\u2461\u2463"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2465"},{"id":"ref-for-advisory-committee-review\u2461\u2466"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2467"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2468"},{"id":"ref-for-advisory-committee-review\u2462\u24ea"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2461"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2462"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2463"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2464"}],"title":"10. \nProcess Evolution"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2465"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#advisory-committee-review"},
+"allow-new-features": {"dfnID":"allow-new-features","dfnText":"allow new features","external":false,"refSections":[{"refs":[{"id":"ref-for-allow-new-features"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-allow-new-features\u2460"},{"id":"ref-for-allow-new-features\u2461"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-allow-new-features\u2462"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#allow-new-features"},
+"alternate-ac-representative": {"dfnID":"alternate-ac-representative","dfnText":"alternate","external":false,"refSections":[],"url":"#alternate-ac-representative"},
+"appeal-vote": {"dfnID":"appeal-vote","dfnText":"appeal vote","external":false,"refSections":[{"refs":[{"id":"ref-for-appeal-vote"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-appeal-vote\u2460"}],"title":"5.8. \nAdvisory Committee Votes"}],"url":"#appeal-vote"},
+"at-risk": {"dfnID":"at-risk","dfnText":"at risk","external":false,"refSections":[{"refs":[{"id":"ref-for-at-risk"},{"id":"ref-for-at-risk\u2460"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-at-risk\u2461"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-at-risk\u2462"}],"title":"6.3.9.3. \nResolution of Review"}],"url":"#at-risk"},
+"bod": {"dfnID":"bod","dfnText":"W3C Board of Directors","external":false,"refSections":[{"refs":[{"id":"ref-for-bod"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-bod\u2460"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-bod\u2461"},{"id":"ref-for-bod\u2462"},{"id":"ref-for-bod\u2463"},{"id":"ref-for-bod\u2464"},{"id":"ref-for-bod\u2465"}],"title":"3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"},{"refs":[{"id":"ref-for-bod\u2466"},{"id":"ref-for-bod\u2467"}],"title":"8. \nLiaisons"}],"url":"#bod"},
+"candidate-addition": {"dfnID":"candidate-addition","dfnText":"candidate addition","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-addition"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-addition\u2460"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"}],"url":"#candidate-addition"},
+"candidate-amendment": {"dfnID":"candidate-amendment","dfnText":"candidate amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-amendment"},{"id":"ref-for-candidate-amendment\u2460"},{"id":"ref-for-candidate-amendment\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-amendment\u2462"},{"id":"ref-for-candidate-amendment\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-candidate-amendment\u2464"},{"id":"ref-for-candidate-amendment\u2465"},{"id":"ref-for-candidate-amendment\u2466"},{"id":"ref-for-candidate-amendment\u2467"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-candidate-amendment\u2468"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#candidate-amendment"},
+"candidate-correction": {"dfnID":"candidate-correction","dfnText":"candidate correction","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-correction"},{"id":"ref-for-candidate-correction\u2460"},{"id":"ref-for-candidate-correction\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-correction\u2462"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-candidate-correction\u2463"},{"id":"ref-for-candidate-correction\u2464"},{"id":"ref-for-candidate-correction\u2465"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"}],"url":"#candidate-correction"},
+"candidate-recommendation-draft": {"dfnID":"candidate-recommendation-draft","dfnText":"Candidate Recommendation Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-draft"},{"id":"ref-for-candidate-recommendation-draft\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2461"},{"id":"ref-for-candidate-recommendation-draft\u2462"},{"id":"ref-for-candidate-recommendation-draft\u2463"},{"id":"ref-for-candidate-recommendation-draft\u2464"},{"id":"ref-for-candidate-recommendation-draft\u2465"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2466"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#candidate-recommendation-draft"},
+"candidate-recommendation-review-period": {"dfnID":"candidate-recommendation-review-period","dfnText":"Candidate Recommendation review period","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-review-period"},{"id":"ref-for-candidate-recommendation-review-period\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"}],"url":"#candidate-recommendation-review-period"},
+"candidate-recommendation-snapshot": {"dfnID":"candidate-recommendation-snapshot","dfnText":"Candidate Recommendation Snapshot","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-snapshot"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460"},{"id":"ref-for-candidate-recommendation-snapshot\u2461"},{"id":"ref-for-candidate-recommendation-snapshot\u2462"},{"id":"ref-for-candidate-recommendation-snapshot\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2464"},{"id":"ref-for-candidate-recommendation-snapshot\u2465"},{"id":"ref-for-candidate-recommendation-snapshot\u2466"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2467"},{"id":"ref-for-candidate-recommendation-snapshot\u2468"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u24ea"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2460"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2461"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2462"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2463"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2464"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2465"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2466"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2467"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2468"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#candidate-recommendation-snapshot"},
+"candidate-registry": {"dfnID":"candidate-registry","dfnText":"Candidate Registry","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-registry"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#candidate-registry"},
+"candidate-registry-draft": {"dfnID":"candidate-registry-draft","dfnText":"Candidate Registry Draft","external":false,"refSections":[],"url":"#candidate-registry-draft"},
+"candidate-registry-snapshot": {"dfnID":"candidate-registry-snapshot","dfnText":"Candidate Registry Snapshot","external":false,"refSections":[],"url":"#candidate-registry-snapshot"},
+"ceo": {"dfnID":"ceo","dfnText":"CEO","external":false,"refSections":[{"refs":[{"id":"ref-for-ceo"}],"title":"2.1.2.1. \nMembership Associations"},{"refs":[{"id":"ref-for-ceo\u2460"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-ceo\u2461"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-ceo\u2462"}],"title":"3.1.1.3. \nIndividuals Representing a Member Organization"},{"refs":[{"id":"ref-for-ceo\u2463"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-ceo\u2464"},{"id":"ref-for-ceo\u2465"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-ceo\u2466"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-ceo\u2467"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-ceo\u2468"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#ceo"},
+"chair-decisions": {"dfnID":"chair-decisions","dfnText":"chair decisions","external":false,"refSections":[],"url":"#chair-decisions"},
+"charter": {"dfnID":"charter","dfnText":"charter","external":false,"refSections":[{"refs":[{"id":"ref-for-charter"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-charter\u2460"},{"id":"ref-for-charter\u2461"},{"id":"ref-for-charter\u2462"},{"id":"ref-for-charter\u2463"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-charter\u2464"},{"id":"ref-for-charter\u2465"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter\u2466"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-charter\u2467"},{"id":"ref-for-charter\u2468"},{"id":"ref-for-charter\u2460\u24ea"},{"id":"ref-for-charter\u2460\u2460"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-charter\u2460\u2461"},{"id":"ref-for-charter\u2460\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-charter\u2460\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-charter\u2460\u2464"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-charter\u2460\u2465"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-charter\u2460\u2466"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-charter\u2460\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"}],"url":"#charter"},
+"charter-draft": {"dfnID":"charter-draft","dfnText":"charter draft","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-draft"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-draft\u2460"},{"id":"ref-for-charter-draft\u2461"},{"id":"ref-for-charter-draft\u2462"},{"id":"ref-for-charter-draft\u2463"}],"title":"4.2. \nCharter Refinement"}],"url":"#charter-draft"},
+"charter-refinement": {"dfnID":"charter-refinement","dfnText":"charter refinement","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-refinement"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-charter-refinement\u2460"},{"id":"ref-for-charter-refinement\u2461"},{"id":"ref-for-charter-refinement\u2462"},{"id":"ref-for-charter-refinement\u2463"},{"id":"ref-for-charter-refinement\u2464"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-refinement\u2465"},{"id":"ref-for-charter-refinement\u2466"},{"id":"ref-for-charter-refinement\u2467"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-charter-refinement\u2468"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-charter-refinement\u2460\u24ea"},{"id":"ref-for-charter-refinement\u2460\u2460"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-charter-refinement\u2460\u2461"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#charter-refinement"},
+"charter-review-notice": {"dfnID":"charter-review-notice","dfnText":"charter review notice","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-review-notice"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-review-notice\u2460"}],"title":"4.2. \nCharter Refinement"}],"url":"#charter-review-notice"},
+"chartered-group": {"dfnID":"chartered-group","dfnText":"chartered groups","external":false,"refSections":[{"refs":[{"id":"ref-for-chartered-group"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-chartered-group\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-chartered-group\u2461"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-chartered-group\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-chartered-group\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-chartered-group\u2464"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-chartered-group\u2465"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#chartered-group"},
+"chartering-facilitator": {"dfnID":"chartering-facilitator","dfnText":"Chartering Facilitator","external":false,"refSections":[{"refs":[{"id":"ref-for-chartering-facilitator"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-chartering-facilitator\u2460"},{"id":"ref-for-chartering-facilitator\u2461"},{"id":"ref-for-chartering-facilitator\u2462"}],"title":"4.2. \nCharter Refinement"}],"url":"#chartering-facilitator"},
+"convened": {"dfnID":"convened","dfnText":"convened","external":false,"refSections":[{"refs":[{"id":"ref-for-convened"},{"id":"ref-for-convened\u2460"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-convened\u2461"},{"id":"ref-for-convened\u2462"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#convened"},
+"council-report": {"dfnID":"council-report","dfnText":"Council Report","external":false,"refSections":[{"refs":[{"id":"ref-for-council-report"},{"id":"ref-for-council-report\u2460"},{"id":"ref-for-council-report\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-council-report\u2462"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-council-report\u2463"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-council-report\u2464"}],"title":"9. \nMember Submissions"}],"url":"#council-report"},
+"council-team-contact": {"dfnID":"council-team-contact","dfnText":"Council Team Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-council-team-contact"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-council-team-contact\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#council-team-contact"},
+"custodian": {"dfnID":"custodian","dfnText":"custodian","external":false,"refSections":[{"refs":[{"id":"ref-for-custodian"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-custodian\u2460"},{"id":"ref-for-custodian\u2461"},{"id":"ref-for-custodian\u2462"},{"id":"ref-for-custodian\u2463"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-custodian\u2464"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-custodian\u2465"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#custodian"},
+"def-Consensus": {"dfnID":"def-Consensus","dfnText":"Consensus","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Consensus"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-def-Consensus\u2460"},{"id":"ref-for-def-Consensus\u2461"},{"id":"ref-for-def-Consensus\u2462"},{"id":"ref-for-def-Consensus\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-def-Consensus\u2464"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-def-Consensus\u2465"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-def-Consensus\u2466"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-def-Consensus\u2467"},{"id":"ref-for-def-Consensus\u2468"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u24ea"},{"id":"ref-for-def-Consensus\u2460\u2460"},{"id":"ref-for-def-Consensus\u2460\u2461"},{"id":"ref-for-def-Consensus\u2460\u2462"},{"id":"ref-for-def-Consensus\u2460\u2463"},{"id":"ref-for-def-Consensus\u2460\u2464"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2465"}],"title":"6. \nW3C Technical Reports"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2466"},{"id":"ref-for-def-Consensus\u2460\u2467"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2468"},{"id":"ref-for-def-Consensus\u2461\u24ea"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-def-Consensus\u2461\u2460"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-def-Consensus\u2461\u2461"}],"title":"10. \nProcess Evolution"}],"url":"#def-Consensus"},
+"def-Dissent": {"dfnID":"def-Dissent","dfnText":"Dissent","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Dissent"},{"id":"ref-for-def-Dissent\u2460"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-def-Dissent\u2461"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-def-Dissent\u2462"},{"id":"ref-for-def-Dissent\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-Dissent\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-def-Dissent\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#def-Dissent"},
+"def-Unanimity": {"dfnID":"def-Unanimity","dfnText":"Unanimity","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Unanimity"}],"title":"5.2.1. \nConsensus"}],"url":"#def-Unanimity"},
+"def-W3CChair": {"dfnID":"def-W3CChair","dfnText":"W3C Chair","external":false,"refSections":[],"url":"#def-W3CChair"},
+"def-w3c-decision": {"dfnID":"def-w3c-decision","dfnText":"W3C decision","external":false,"refSections":[{"refs":[{"id":"ref-for-def-w3c-decision"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-def-w3c-decision\u2461"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-def-w3c-decision\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-def-w3c-decision\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-def-w3c-decision\u2464"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-def-w3c-decision\u2465"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-def-w3c-decision\u2466"},{"id":"ref-for-def-w3c-decision\u2467"},{"id":"ref-for-def-w3c-decision\u2468"},{"id":"ref-for-def-w3c-decision\u2460\u24ea"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2460"},{"id":"ref-for-def-w3c-decision\u2460\u2461"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2462"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2464"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2465"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2466"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#def-w3c-decision"},
+"dfn-charter-extension": {"dfnID":"dfn-charter-extension","dfnText":"extensions","external":false,"refSections":[{"refs":[{"id":"ref-for-dfn-charter-extension"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"}],"url":"#dfn-charter-extension"},
+"dfn-wide-review": {"dfnID":"dfn-wide-review","dfnText":"wide review","external":false,"refSections":[{"refs":[{"id":"ref-for-dfn-wide-review"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-dfn-wide-review\u2461"},{"id":"ref-for-dfn-wide-review\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-dfn-wide-review\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-dfn-wide-review\u2464"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2466"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2467"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-dfn-wide-review\u2468"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460\u24ea"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#dfn-wide-review"},
+"discontinuedREC": {"dfnID":"discontinuedREC","dfnText":"Discontinued Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-discontinuedREC"},{"id":"ref-for-discontinuedREC\u2460"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"}],"url":"#discontinuedREC"},
+"dismissed": {"dfnID":"dismissed","dfnText":"dismissed","external":false,"refSections":[{"refs":[{"id":"ref-for-dismissed"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-dismissed\u2460"},{"id":"ref-for-dismissed\u2461"},{"id":"ref-for-dismissed\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-dismissed\u2463"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-dismissed\u2464"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#dismissed"},
+"distributed-meeting": {"dfnID":"distributed-meeting","dfnText":"distributed meeting","external":false,"refSections":[{"refs":[{"id":"ref-for-distributed-meeting"}],"title":"5.2.1. \nConsensus"}],"url":"#distributed-meeting"},
+"edited-recommendation": {"dfnID":"edited-recommendation","dfnText":"Edited Recommendation","external":false,"refSections":[],"url":"#edited-recommendation"},
+"editorial-change": {"dfnID":"editorial-change","dfnText":"editorial changes","external":false,"refSections":[{"refs":[{"id":"ref-for-editorial-change"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-editorial-change\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2462"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2463"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-editorial-change\u2464"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-editorial-change\u2465"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-editorial-change\u2466"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-editorial-change\u2467"},{"id":"ref-for-editorial-change\u2468"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#editorial-change"},
+"editors-draft": {"dfnID":"editors-draft","dfnText":"Editor\u2019s drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-editors-draft"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"}],"url":"#editors-draft"},
+"elected-group": {"dfnID":"elected-group","dfnText":"elected groups","external":false,"refSections":[{"refs":[{"id":"ref-for-elected-group"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-elected-group\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-elected-group\u2461"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#elected-group"},
+"embedded-registry": {"dfnID":"embedded-registry","dfnText":"embedded registry","external":false,"refSections":[{"refs":[{"id":"ref-for-embedded-registry"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-embedded-registry\u2460"},{"id":"ref-for-embedded-registry\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-embedded-registry\u2462"},{"id":"ref-for-embedded-registry\u2463"}],"title":"6.5.6. \nRegistries and Patents"},{"refs":[{"id":"ref-for-embedded-registry\u2464"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#embedded-registry"},
+"erratum": {"dfnID":"erratum","dfnText":"erratum","external":false,"refSections":[{"refs":[{"id":"ref-for-erratum"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-erratum\u2460"},{"id":"ref-for-erratum\u2461"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#erratum"},
+"exclusion-draft": {"dfnID":"exclusion-draft","dfnText":"Exclusion Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-exclusion-draft"},{"id":"ref-for-exclusion-draft\u2460"}],"title":"4.3. \nContent of a Charter"}],"url":"#exclusion-draft"},
+"exclusion-draft-charter": {"dfnID":"exclusion-draft-charter","dfnText":"Exclusion Draft Charter","external":false,"refSections":[{"refs":[{"id":"ref-for-exclusion-draft-charter"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#exclusion-draft-charter"},
+"fdn-member-consortium": {"dfnID":"fdn-member-consortium","dfnText":"Member Consortium","external":false,"refSections":[],"url":"#fdn-member-consortium"},
+"fellows": {"dfnID":"fellows","dfnText":"W3C Fellows","external":false,"refSections":[{"refs":[{"id":"ref-for-fellows"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-fellows"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}],"url":"#fellows"},
+"formally-addressed": {"dfnID":"formally-addressed","dfnText":"formally addressed","external":false,"refSections":[{"refs":[{"id":"ref-for-formally-addressed"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-formally-addressed\u2460"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-formally-addressed\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-formally-addressed\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-formally-addressed\u2463"},{"id":"ref-for-formally-addressed\u2464"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-formally-addressed\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-formally-addressed\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-formally-addressed\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#formally-addressed"},
+"fpwd": {"dfnID":"fpwd","dfnText":"First Public Working Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-fpwd"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-fpwd\u2460"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-fpwd\u2461"},{"id":"ref-for-fpwd\u2462"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-fpwd\u2463"},{"id":"ref-for-fpwd\u2464"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-fpwd\u2465"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-fpwd\u2466"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-fpwd\u2467"},{"id":"ref-for-fpwd\u2468"}],"title":"6.6. \nSwitching Tracks"}],"url":"#fpwd"},
+"ftf-meeting": {"dfnID":"ftf-meeting","dfnText":"face-to-face meeting","external":false,"refSections":[{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"5.6.2.1. \nCouncil Composition"}],"url":"#ftf-meeting"},
+"fully-addressed": {"dfnID":"fully-addressed","dfnText":"fully addressed","external":false,"refSections":[{"refs":[{"id":"ref-for-fully-addressed"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-fully-addressed\u2460"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#fully-addressed"},
+"good-standing": {"dfnID":"good-standing","dfnText":"Good Standing","external":false,"refSections":[{"refs":[{"id":"ref-for-good-standing"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-good-standing\u2460"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-good-standing\u2461"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#good-standing"},
+"group-decision": {"dfnID":"group-decision","dfnText":"group decisions","external":false,"refSections":[{"refs":[{"id":"ref-for-group-decision"},{"id":"ref-for-group-decision\u2460"}],"title":"3.1.2.2. \nMeeting Minutes"},{"refs":[{"id":"ref-for-group-decision\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-group-decision\u2462"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-group-decision\u2463"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-group-decision\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-group-decision\u2465"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-group-decision\u2466"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-group-decision\u2467"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-group-decision\u2468"}],"title":"6.6. \nSwitching Tracks"}],"url":"#group-decision"},
+"igparticipant": {"dfnID":"igparticipant","dfnText":"participants in an Interest Group","external":false,"refSections":[{"refs":[{"id":"ref-for-igparticipant"}],"title":"3. \nGroups and Participation"},{"refs":[{"id":"ref-for-igparticipant"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#igparticipant"},
+"inv-expert-info": {"dfnID":"inv-expert-info","dfnText":"participate in a Working Group as an Invited Expert","external":false,"refSections":[{"refs":[{"id":"ref-for-inv-expert-info"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-inv-expert-info"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"}],"url":"#inv-expert-info"},
+"invited-expert-in-a-working-group": {"dfnID":"invited-expert-in-a-working-group","dfnText":"Invited Expert in a Working Group","external":false,"refSections":[{"refs":[{"id":"ref-for-invited-expert-in-a-working-group"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-invited-expert-in-a-working-group\u2460"}],"title":"3.4.3.4. \nInvited Expert in an Interest Group"}],"url":"#invited-expert-in-a-working-group"},
+"invited-expert-in-an-interest-group": {"dfnID":"invited-expert-in-an-interest-group","dfnText":"Invited Expert in an Interest Group","external":false,"refSections":[],"url":"#invited-expert-in-an-interest-group"},
+"last-call": {"dfnID":"last-call","dfnText":"Last Call","external":false,"refSections":[],"url":"#last-call"},
+"last-call-for-review-of-proposed-additions": {"dfnID":"last-call-for-review-of-proposed-additions","dfnText":"Last Call for Review of Proposed Additions","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-additions"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-for-review-of-proposed-additions"},
+"last-call-for-review-of-proposed-corrections": {"dfnID":"last-call-for-review-of-proposed-corrections","dfnText":"Last Call for Review of Proposed Corrections","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-corrections"}],"title":"6.4.4. \nRevising W3C Statements"}],"url":"#last-call-for-review-of-proposed-corrections"},
+"last-call-for-review-of-proposed-corrections-and-additions": {"dfnID":"last-call-for-review-of-proposed-corrections-and-additions","dfnText":"Last Call for Review of Proposed Corrections and Additions","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-corrections-and-additions"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-for-review-of-proposed-corrections-and-additions"},
+"last-call-review": {"dfnID":"last-call-review","dfnText":"Last Call for Review of Proposed Amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-review"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-last-call-review\u2460"},{"id":"ref-for-last-call-review\u2461"},{"id":"ref-for-last-call-review\u2462"},{"id":"ref-for-last-call-review\u2463"},{"id":"ref-for-last-call-review\u2464"},{"id":"ref-for-last-call-review\u2465"},{"id":"ref-for-last-call-review\u2466"},{"id":"ref-for-last-call-review\u2467"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-review"},
+"liaison": {"dfnID":"liaison","dfnText":"liaison","external":false,"refSections":[],"url":"#liaison"},
+"maturity-levels": {"dfnID":"maturity-levels","dfnText":"Maturity level","external":false,"refSections":[],"url":"#maturity-levels"},
+"member-association": {"dfnID":"member-association","dfnText":"Member Association","external":false,"refSections":[{"refs":[{"id":"ref-for-member-association"},{"id":"ref-for-member-association\u2460"},{"id":"ref-for-member-association\u2461"},{"id":"ref-for-member-association\u2462"},{"id":"ref-for-member-association\u2463"},{"id":"ref-for-member-association\u2464"}],"title":"2.1.2.1. \nMembership Associations"},{"refs":[{"id":"ref-for-member-association\u2465"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#member-association"},
+"member-representative-in-a-working-group": {"dfnID":"member-representative-in-a-working-group","dfnText":"Member representative in a Working Group","external":false,"refSections":[],"url":"#member-representative-in-a-working-group"},
+"member-representative-in-an-interest-group": {"dfnID":"member-representative-in-an-interest-group","dfnText":"Member representative in an Interest Group","external":false,"refSections":[{"refs":[{"id":"ref-for-member-representative-in-an-interest-group"}],"title":"3.4.3.2. \nMember Representative in an Interest Group"}],"url":"#member-representative-in-an-interest-group"},
+"minor-changes": {"dfnID":"minor-changes","dfnText":"minor changes","external":false,"refSections":[{"refs":[{"id":"ref-for-minor-changes"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-minor-changes\u2460"},{"id":"ref-for-minor-changes\u2461"},{"id":"ref-for-minor-changes\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#minor-changes"},
+"minority-opinion": {"dfnID":"minority-opinion","dfnText":"Minority Opinion","external":false,"refSections":[{"refs":[{"id":"ref-for-minority-opinion"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#minority-opinion"},
+"minutes": {"dfnID":"minutes","dfnText":"minutes","external":false,"refSections":[{"refs":[{"id":"ref-for-minutes"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-minutes\u2460"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-minutes\u2461"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#minutes"},
+"mou": {"dfnID":"mou","dfnText":"Memorandum of Understanding","external":false,"refSections":[],"url":"#mou"},
+"mtg-substitute": {"dfnID":"mtg-substitute","dfnText":"substitute","external":false,"refSections":[{"refs":[{"id":"ref-for-mtg-substitute"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#mtg-substitute"},
+"not-required": {"dfnID":"not-required","dfnText":"not required","external":false,"refSections":[],"url":"#not-required"},
+"note-draft": {"dfnID":"note-draft","dfnText":"Note Drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-note-draft"},{"id":"ref-for-note-draft\u2460"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-note-draft\u2461"},{"id":"ref-for-note-draft\u2462"},{"id":"ref-for-note-draft\u2463"},{"id":"ref-for-note-draft\u2464"}],"title":"6.4.2. \nPublishing Notes"}],"url":"#note-draft"},
+"obsolete-registry": {"dfnID":"obsolete-registry","dfnText":"Obsolete Registry","external":false,"refSections":[],"url":"#obsolete-registry"},
+"other-charter": {"dfnID":"other-charter","dfnText":"Other Charter","external":false,"refSections":[],"url":"#other-charter"},
+"overrule": {"dfnID":"overrule","dfnText":"overrule","external":false,"refSections":[{"refs":[{"id":"ref-for-overrule"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-overrule\u2460"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-overrule\u2461"},{"id":"ref-for-overrule\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-overrule\u2463"}],"title":"6.3.9.3. \nResolution of Review"}],"url":"#overrule"},
+"participant": {"dfnID":"participant","dfnText":"participant","external":false,"refSections":[{"refs":[{"id":"ref-for-participant"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-participant\u2460"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#participant"},
+"patent-review-drafts": {"dfnID":"patent-review-drafts","dfnText":"Patent Review Drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-patent-review-drafts"},{"id":"ref-for-patent-review-drafts\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-patent-review-drafts\u2461"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-patent-review-drafts\u2462"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-patent-review-drafts\u2463"}],"title":"6.6. \nSwitching Tracks"}],"url":"#patent-review-drafts"},
+"primary-affiliation": {"dfnID":"primary-affiliation","dfnText":"primary affiliation","external":false,"refSections":[{"refs":[{"id":"ref-for-primary-affiliation"},{"id":"ref-for-primary-affiliation\u2460"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-primary-affiliation\u2461"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}],"url":"#primary-affiliation"},
+"proposed-additions": {"dfnID":"proposed-additions","dfnText":"proposed additions","external":false,"refSections":[],"url":"#proposed-additions"},
+"proposed-amendments": {"dfnID":"proposed-amendments","dfnText":"proposed amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-proposed-amendments"},{"id":"ref-for-proposed-amendments\u2460"},{"id":"ref-for-proposed-amendments\u2461"},{"id":"ref-for-proposed-amendments\u2462"},{"id":"ref-for-proposed-amendments\u2463"},{"id":"ref-for-proposed-amendments\u2464"},{"id":"ref-for-proposed-amendments\u2465"},{"id":"ref-for-proposed-amendments\u2466"},{"id":"ref-for-proposed-amendments\u2467"},{"id":"ref-for-proposed-amendments\u2468"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-proposed-amendments\u2460\u24ea"},{"id":"ref-for-proposed-amendments\u2460\u2460"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-proposed-amendments\u2460\u2461"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#proposed-amendments"},
+"proposed-corrections": {"dfnID":"proposed-corrections","dfnText":"proposed corrections","external":false,"refSections":[],"url":"#proposed-corrections"},
+"public-participant-ig": {"dfnID":"public-participant-ig","dfnText":"public participants","external":false,"refSections":[{"refs":[{"id":"ref-for-public-participant-ig"}],"title":"4.3. \nContent of a Charter"}],"url":"#public-participant-ig"},
+"publishing": {"dfnID":"publishing","dfnText":"Publishing","external":false,"refSections":[{"refs":[{"id":"ref-for-publishing"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-publishing\u2460"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-publishing\u2461"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-publishing\u2462"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-publishing\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-publishing\u2464"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-publishing\u2465"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-publishing\u2466"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-publishing\u2467"},{"id":"ref-for-publishing\u2468"},{"id":"ref-for-publishing\u2460\u24ea"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-publishing\u2460\u2460"},{"id":"ref-for-publishing\u2460\u2461"}],"title":"6.4.1. \nGroup Notes"}],"url":"#publishing"},
+"rec-amended": {"dfnID":"rec-amended","dfnText":"Amended Recommendation","external":false,"refSections":[],"url":"#rec-amended"},
+"registry": {"dfnID":"registry","dfnText":"registry","external":false,"refSections":[{"refs":[{"id":"ref-for-registry"},{"id":"ref-for-registry\u2460"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry\u2461"},{"id":"ref-for-registry\u2462"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry\u2463"},{"id":"ref-for-registry\u2464"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry\u2465"},{"id":"ref-for-registry\u2466"},{"id":"ref-for-registry\u2467"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry\u2468"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry"},
+"registry-change": {"dfnID":"registry-change","dfnText":"registry changes","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-change"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-change\u2460"},{"id":"ref-for-registry-change\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-change\u2462"},{"id":"ref-for-registry-change\u2463"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#registry-change"},
+"registry-data": {"dfnID":"registry-data","dfnText":"registry data","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-data"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-data\u2460"},{"id":"ref-for-registry-data\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-data"},
+"registry-data-report": {"dfnID":"registry-data-report","dfnText":"Registry Data Report","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-data-report"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-data-report\u2460"},{"id":"ref-for-registry-data-report\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-data-report"},
+"registry-definition": {"dfnID":"registry-definition","dfnText":"registry definition","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-definition"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry-definition\u2460"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry-definition\u2461"},{"id":"ref-for-registry-definition\u2462"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-definition\u2463"},{"id":"ref-for-registry-definition\u2464"},{"id":"ref-for-registry-definition\u2465"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-definition\u2466"},{"id":"ref-for-registry-definition\u2467"},{"id":"ref-for-registry-definition\u2468"},{"id":"ref-for-registry-definition\u2460\u24ea"},{"id":"ref-for-registry-definition\u2460\u2460"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-registry-definition\u2460\u2461"},{"id":"ref-for-registry-definition\u2460\u2462"},{"id":"ref-for-registry-definition\u2460\u2463"},{"id":"ref-for-registry-definition\u2460\u2464"},{"id":"ref-for-registry-definition\u2460\u2465"},{"id":"ref-for-registry-definition\u2460\u2466"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-definition"},
+"registry-draft": {"dfnID":"registry-draft","dfnText":"Registry Draft","external":false,"refSections":[],"url":"#registry-draft"},
+"registry-entry": {"dfnID":"registry-entry","dfnText":"registry entries","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-entry"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-registry-entry\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-entry\u2461"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-registry-entry\u2462"}],"title":"6.5.5. \nSpecifications that Reference Registries"}],"url":"#registry-entry"},
+"registry-report": {"dfnID":"registry-report","dfnText":"registry report","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-report"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry-report\u2460"},{"id":"ref-for-registry-report\u2461"},{"id":"ref-for-registry-report\u2462"},{"id":"ref-for-registry-report\u2463"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-report\u2464"}],"title":"6.5.6. \nRegistries and Patents"}],"url":"#registry-report"},
+"registry-table": {"dfnID":"registry-table","dfnText":"registry tables","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-table"},{"id":"ref-for-registry-table\u2460"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-registry-table\u2461"},{"id":"ref-for-registry-table\u2462"},{"id":"ref-for-registry-table\u2463"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry-table\u2464"},{"id":"ref-for-registry-table\u2465"},{"id":"ref-for-registry-table\u2466"},{"id":"ref-for-registry-table\u2467"},{"id":"ref-for-registry-table\u2468"},{"id":"ref-for-registry-table\u2460\u24ea"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-table\u2460\u2460"},{"id":"ref-for-registry-table\u2460\u2461"},{"id":"ref-for-registry-table\u2460\u2462"},{"id":"ref-for-registry-table\u2460\u2463"},{"id":"ref-for-registry-table\u2460\u2464"},{"id":"ref-for-registry-table\u2460\u2465"},{"id":"ref-for-registry-table\u2460\u2466"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-table\u2460\u2467"},{"id":"ref-for-registry-table\u2460\u2468"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-registry-table\u2461\u24ea"},{"id":"ref-for-registry-table\u2461\u2460"},{"id":"ref-for-registry-table\u2461\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-table"},
+"registry-track": {"dfnID":"registry-track","dfnText":"Registry Track","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-track"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#registry-track"},
+"rejected": {"dfnID":"rejected","dfnText":"rejected","external":false,"refSections":[{"refs":[{"id":"ref-for-rejected"}],"title":"9. \nMember Submissions"}],"url":"#rejected"},
+"related-member": {"dfnID":"related-member","dfnText":"related","external":false,"refSections":[{"refs":[{"id":"ref-for-related-member"}],"title":"2.1.2.2. \nRelated Members"},{"refs":[{"id":"ref-for-related-member\u2460"}],"title":"2.1.3. \nGood Standing"},{"refs":[{"id":"ref-for-related-member\u2461"},{"id":"ref-for-related-member\u2462"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-related-member\u2463"}],"title":"5.8. \nAdvisory Committee Votes"}],"url":"#related-member"},
+"renounce": {"dfnID":"renounce","dfnText":"renounce","external":false,"refSections":[{"refs":[{"id":"ref-for-renounce"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-renounce\u2460"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-renounce\u2461"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-renounce\u2462"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#renounce"},
+"rescinded-candidate-recommendation": {"dfnID":"rescinded-candidate-recommendation","dfnText":"Rescinded Candidate Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-rescinded-candidate-recommendation"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-rescinded-candidate-recommendation\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#rescinded-candidate-recommendation"},
+"reviewform": {"dfnID":"reviewform","dfnText":"Call for Review","external":false,"refSections":[{"refs":[{"id":"ref-for-reviewform"},{"id":"ref-for-reviewform\u2460"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-reviewform\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"}],"url":"#reviewform"},
+"statement": {"dfnID":"statement","dfnText":"W3C Statement","external":false,"refSections":[{"refs":[{"id":"ref-for-statement"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-statement\u2460"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-statement\u2461"},{"id":"ref-for-statement\u2462"},{"id":"ref-for-statement\u2463"},{"id":"ref-for-statement\u2464"},{"id":"ref-for-statement\u2465"},{"id":"ref-for-statement\u2466"},{"id":"ref-for-statement\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-statement\u2468"},{"id":"ref-for-statement\u2460\u24ea"},{"id":"ref-for-statement\u2460\u2460"},{"id":"ref-for-statement\u2460\u2461"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-statement\u2460\u2462"}],"title":"6.6. \nSwitching Tracks"}],"url":"#statement"},
+"submission-appeals": {"dfnID":"submission-appeals","dfnText":"Submission Appeals","external":false,"refSections":[{"refs":[{"id":"ref-for-submission-appeals"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-submission-appeals\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-submission-appeals\u2461"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-submission-appeals\u2462"},{"id":"ref-for-submission-appeals\u2463"}],"title":"9. \nMember Submissions"}],"url":"#submission-appeals"},
+"submitter": {"dfnID":"submitter","dfnText":"Submitter(s)","external":false,"refSections":[{"refs":[{"id":"ref-for-submitter"},{"id":"ref-for-submitter\u2460"},{"id":"ref-for-submitter\u2461"},{"id":"ref-for-submitter\u2462"},{"id":"ref-for-submitter\u2463"},{"id":"ref-for-submitter\u2464"},{"id":"ref-for-submitter\u2465"},{"id":"ref-for-submitter\u2466"}],"title":"9. \nMember Submissions"}],"url":"#submitter"},
+"subsidiary": {"dfnID":"subsidiary","dfnText":"subsidiary","external":false,"refSections":[{"refs":[{"id":"ref-for-subsidiary"},{"id":"ref-for-subsidiary\u2460"}],"title":"2.1.2.2. \nRelated Members"}],"url":"#subsidiary"},
+"substantive-change": {"dfnID":"substantive-change","dfnText":"substantive changes","external":false,"refSections":[{"refs":[{"id":"ref-for-substantive-change"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-substantive-change\u2460"},{"id":"ref-for-substantive-change\u2461"},{"id":"ref-for-substantive-change\u2462"},{"id":"ref-for-substantive-change\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-substantive-change\u2464"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-substantive-change\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-substantive-change\u2466"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-substantive-change\u2467"},{"id":"ref-for-substantive-change\u2468"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-substantive-change\u2460\u24ea"},{"id":"ref-for-substantive-change\u2460\u2460"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2461"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2462"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"}],"url":"#substantive-change"},
+"superseded-registry": {"dfnID":"superseded-registry","dfnText":"Superseded Registry","external":false,"refSections":[],"url":"#superseded-registry"},
+"supplemental-confidential-council-report": {"dfnID":"supplemental-confidential-council-report","dfnText":"Supplemental Confidential Council Report","external":false,"refSections":[],"url":"#supplemental-confidential-council-report"},
+"team": {"dfnID":"team","dfnText":"Team","external":false,"refSections":[{"refs":[{"id":"ref-for-team"},{"id":"ref-for-team\u2460"},{"id":"ref-for-team\u2461"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-team\u2462"},{"id":"ref-for-team\u2463"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-team\u2464"},{"id":"ref-for-team\u2465"},{"id":"ref-for-team\u2466"}],"title":"3.1.1.2. \nConflict of Interest Policy"},{"refs":[{"id":"ref-for-team\u2467"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-team\u2468"},{"id":"ref-for-team\u2460\u24ea"}],"title":"3.1.4. \nResignation from a Group"},{"refs":[{"id":"ref-for-team\u2460\u2460"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-team\u2460\u2461"},{"id":"ref-for-team\u2460\u2462"},{"id":"ref-for-team\u2460\u2463"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-team\u2460\u2464"},{"id":"ref-for-team\u2460\u2465"},{"id":"ref-for-team\u2460\u2466"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-team\u2460\u2467"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-team\u2460\u2468"}],"title":"3.3.1.3. \nCommunications of the Advisory Board"},{"refs":[{"id":"ref-for-team\u2461\u24ea"},{"id":"ref-for-team\u2461\u2460"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-team\u2461\u2461"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-team\u2461\u2462"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-team\u2461\u2463"},{"id":"ref-for-team\u2461\u2464"},{"id":"ref-for-team\u2461\u2465"},{"id":"ref-for-team\u2461\u2466"},{"id":"ref-for-team\u2461\u2467"},{"id":"ref-for-team\u2461\u2468"},{"id":"ref-for-team\u2462\u24ea"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-team\u2462\u2460"},{"id":"ref-for-team\u2462\u2461"},{"id":"ref-for-team\u2462\u2462"},{"id":"ref-for-team\u2462\u2463"},{"id":"ref-for-team\u2462\u2464"},{"id":"ref-for-team\u2462\u2465"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-team\u2462\u2466"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-team\u2462\u2467"},{"id":"ref-for-team\u2462\u2468"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-team\u2463\u24ea"},{"id":"ref-for-team\u2463\u2460"},{"id":"ref-for-team\u2463\u2461"},{"id":"ref-for-team\u2463\u2462"},{"id":"ref-for-team\u2463\u2463"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-team\u2463\u2464"},{"id":"ref-for-team\u2463\u2465"},{"id":"ref-for-team\u2463\u2466"},{"id":"ref-for-team\u2463\u2467"},{"id":"ref-for-team\u2463\u2468"},{"id":"ref-for-team\u2464\u24ea"},{"id":"ref-for-team\u2464\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-team\u2464\u2461"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-team\u2464\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-team\u2464\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-team\u2464\u2464"},{"id":"ref-for-team\u2464\u2465"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-team\u2464\u2466"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-team\u2464\u2467"},{"id":"ref-for-team\u2464\u2468"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-team\u2465\u24ea"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-team\u2465\u2460"},{"id":"ref-for-team\u2465\u2461"},{"id":"ref-for-team\u2465\u2462"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-team\u2465\u2463"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-team\u2465\u2464"},{"id":"ref-for-team\u2465\u2465"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-team\u2465\u2466"},{"id":"ref-for-team\u2465\u2467"},{"id":"ref-for-team\u2465\u2468"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-team\u2466\u24ea"},{"id":"ref-for-team\u2466\u2460"},{"id":"ref-for-team\u2466\u2461"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-team\u2466\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-team\u2466\u2463"},{"id":"ref-for-team\u2466\u2464"},{"id":"ref-for-team\u2466\u2465"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-team\u2466\u2466"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-team\u2466\u2467"},{"id":"ref-for-team\u2466\u2468"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-team\u2467\u24ea"},{"id":"ref-for-team\u2467\u2460"},{"id":"ref-for-team\u2467\u2461"},{"id":"ref-for-team\u2467\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-team\u2467\u2463"},{"id":"ref-for-team\u2467\u2464"},{"id":"ref-for-team\u2467\u2465"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-team\u2467\u2466"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-team\u2467\u2467"},{"id":"ref-for-team\u2467\u2468"},{"id":"ref-for-team\u2468\u24ea"},{"id":"ref-for-team\u2468\u2460"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-team\u2468\u2461"}],"title":"6.2.7. \nLicense Grants from Non-Participants"},{"refs":[{"id":"ref-for-team\u2468\u2462"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-team\u2468\u2463"}],"title":"6.3.2. \nImplementation Experience"},{"refs":[{"id":"ref-for-team\u2468\u2464"},{"id":"ref-for-team\u2468\u2465"},{"id":"ref-for-team\u2468\u2466"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2468\u2467"},{"id":"ref-for-team\u2468\u2468"},{"id":"ref-for-team\u2460\u24ea\u24ea"},{"id":"ref-for-team\u2460\u24ea\u2460"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2461"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2462"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2463"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2464"},{"id":"ref-for-team\u2460\u24ea\u2465"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2466"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2467"},{"id":"ref-for-team\u2460\u24ea\u2468"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-team\u2460\u2460\u24ea"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2460"},{"id":"ref-for-team\u2460\u2460\u2461"},{"id":"ref-for-team\u2460\u2460\u2462"},{"id":"ref-for-team\u2460\u2460\u2463"},{"id":"ref-for-team\u2460\u2460\u2464"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2465"},{"id":"ref-for-team\u2460\u2460\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2467"},{"id":"ref-for-team\u2460\u2460\u2468"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-team\u2460\u2461\u24ea"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2460"},{"id":"ref-for-team\u2460\u2461\u2461"}],"title":"7.1. \nPublic Communication"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2462"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2463"},{"id":"ref-for-team\u2460\u2461\u2464"},{"id":"ref-for-team\u2460\u2461\u2465"},{"id":"ref-for-team\u2460\u2461\u2466"}],"title":"7.3. \nChanging Confidentiality Level"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2467"},{"id":"ref-for-team\u2460\u2461\u2468"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-team\u2460\u2462\u24ea"},{"id":"ref-for-team\u2460\u2462\u2460"},{"id":"ref-for-team\u2460\u2462\u2461"},{"id":"ref-for-team\u2460\u2462\u2462"},{"id":"ref-for-team\u2460\u2462\u2463"},{"id":"ref-for-team\u2460\u2462\u2464"},{"id":"ref-for-team\u2460\u2462\u2465"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-team\u2460\u2462\u2466"}],"title":"10. \nProcess Evolution"}],"url":"#team"},
+"team-correction": {"dfnID":"team-correction","dfnText":"Team correction","external":false,"refSections":[{"refs":[{"id":"ref-for-team-correction"},{"id":"ref-for-team-correction\u2460"},{"id":"ref-for-team-correction\u2461"},{"id":"ref-for-team-correction\u2462"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#team-correction"},
+"team-decision": {"dfnID":"team-decision","dfnText":"Team Decisions","external":false,"refSections":[{"refs":[{"id":"ref-for-team-decision"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-team-decision\u2460"},{"id":"ref-for-team-decision\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-team-decision\u2462"},{"id":"ref-for-team-decision\u2463"},{"id":"ref-for-team-decision\u2464"},{"id":"ref-for-team-decision\u2465"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-team-decision\u2466"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-team-decision\u2467"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-team-decision\u2468"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-team-decision\u2460\u24ea"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-team-decision\u2460\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-team-decision\u2460\u2461"}],"title":"8. \nLiaisons"}],"url":"#team-decision"},
+"team-representative-in-a-working-group": {"dfnID":"team-representative-in-a-working-group","dfnText":"Team representative in a Working Group","external":false,"refSections":[],"url":"#team-representative-in-a-working-group"},
+"team-representative-in-an-interest-group": {"dfnID":"team-representative-in-an-interest-group","dfnText":"Team representative in an Interest Group","external":false,"refSections":[],"url":"#team-representative-in-an-interest-group"},
+"technical-agreement": {"dfnID":"technical-agreement","dfnText":"technical agreement","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-agreement"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-technical-agreement\u2460"},{"id":"ref-for-technical-agreement\u2461"},{"id":"ref-for-technical-agreement\u2462"},{"id":"ref-for-technical-agreement\u2463"},{"id":"ref-for-technical-agreement\u2464"},{"id":"ref-for-technical-agreement\u2465"},{"id":"ref-for-technical-agreement\u2466"},{"id":"ref-for-technical-agreement\u2467"},{"id":"ref-for-technical-agreement\u2468"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-technical-agreement\u2460\u24ea"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#technical-agreement"},
+"technical-architecture-group": {"dfnID":"technical-architecture-group","dfnText":"TAG","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-architecture-group"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461"},{"id":"ref-for-technical-architecture-group\u2462"},{"id":"ref-for-technical-architecture-group\u2463"},{"id":"ref-for-technical-architecture-group\u2464"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2465"},{"id":"ref-for-technical-architecture-group\u2466"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2467"},{"id":"ref-for-technical-architecture-group\u2468"},{"id":"ref-for-technical-architecture-group\u2460\u24ea"},{"id":"ref-for-technical-architecture-group\u2460\u2460"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2461"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2462"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2463"},{"id":"ref-for-technical-architecture-group\u2460\u2464"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2465"},{"id":"ref-for-technical-architecture-group\u2460\u2466"},{"id":"ref-for-technical-architecture-group\u2460\u2467"},{"id":"ref-for-technical-architecture-group\u2460\u2468"},{"id":"ref-for-technical-architecture-group\u2461\u24ea"},{"id":"ref-for-technical-architecture-group\u2461\u2460"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2461"}],"title":"3.3.3.5. \nVerifiable Random Selection Procedure"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2462"},{"id":"ref-for-technical-architecture-group\u2461\u2463"},{"id":"ref-for-technical-architecture-group\u2461\u2464"},{"id":"ref-for-technical-architecture-group\u2461\u2465"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2466"},{"id":"ref-for-technical-architecture-group\u2461\u2467"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2468"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u24ea"},{"id":"ref-for-technical-architecture-group\u2462\u2460"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2461"},{"id":"ref-for-technical-architecture-group\u2462\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2463"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2465"},{"id":"ref-for-technical-architecture-group\u2462\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2467"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2468"}],"title":"9. \nMember Submissions"}],"url":"#technical-architecture-group"},
+"technical-report": {"dfnID":"technical-report","dfnText":"Technical Report","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-report"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-technical-report\u2460"},{"id":"ref-for-technical-report\u2461"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-technical-report\u2462"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-technical-report\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-technical-report\u2464"},{"id":"ref-for-technical-report\u2465"},{"id":"ref-for-technical-report\u2466"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-technical-report\u2467"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-technical-report\u2468"},{"id":"ref-for-technical-report\u2460\u24ea"},{"id":"ref-for-technical-report\u2460\u2460"},{"id":"ref-for-technical-report\u2460\u2461"},{"id":"ref-for-technical-report\u2460\u2462"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-technical-report\u2460\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-technical-report\u2460\u2464"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2460\u2465"},{"id":"ref-for-technical-report\u2460\u2466"},{"id":"ref-for-technical-report\u2460\u2467"},{"id":"ref-for-technical-report\u2460\u2468"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2461\u24ea"},{"id":"ref-for-technical-report\u2461\u2460"},{"id":"ref-for-technical-report\u2461\u2461"},{"id":"ref-for-technical-report\u2461\u2462"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-technical-report\u2461\u2463"},{"id":"ref-for-technical-report\u2461\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2461\u2465"},{"id":"ref-for-technical-report\u2461\u2466"},{"id":"ref-for-technical-report\u2461\u2467"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-technical-report\u2461\u2468"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-technical-report\u2462\u24ea"},{"id":"ref-for-technical-report\u2462\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-technical-report\u2462\u2461"},{"id":"ref-for-technical-report\u2462\u2462"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-technical-report\u2462\u2463"},{"id":"ref-for-technical-report\u2462\u2464"},{"id":"ref-for-technical-report\u2462\u2465"},{"id":"ref-for-technical-report\u2462\u2466"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-technical-report\u2462\u2467"},{"id":"ref-for-technical-report\u2462\u2468"},{"id":"ref-for-technical-report\u2463\u24ea"},{"id":"ref-for-technical-report\u2463\u2460"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-technical-report\u2463\u2461"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-technical-report\u2463\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#technical-report"},
+"trans-req": {"dfnID":"trans-req","dfnText":"Transition Requests","external":false,"refSections":[{"refs":[{"id":"ref-for-trans-req"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2460"},{"id":"ref-for-trans-req\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2462"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2463"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"}],"url":"#trans-req"},
+"update-requests": {"dfnID":"update-requests","dfnText":"Update Requests","external":false,"refSections":[{"refs":[{"id":"ref-for-update-requests"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-update-requests\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-update-requests\u2461"},{"id":"ref-for-update-requests\u2462"},{"id":"ref-for-update-requests\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-update-requests\u2464"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-update-requests\u2465"},{"id":"ref-for-update-requests\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-update-requests\u2467"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-update-requests\u2468"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-update-requests\u2460\u24ea"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-update-requests\u2460\u2460"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#update-requests"},
+"uphold": {"dfnID":"uphold","dfnText":"uphold","external":false,"refSections":[{"refs":[{"id":"ref-for-uphold"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-uphold\u2460"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-uphold\u2461"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-uphold\u2462"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-uphold\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#uphold"},
+"w3c-council": {"dfnID":"w3c-council","dfnText":"W3C Council","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-council"},{"id":"ref-for-w3c-council\u2460"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-w3c-council\u2461"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-w3c-council\u2462"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-w3c-council\u2463"},{"id":"ref-for-w3c-council\u2464"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-w3c-council\u2465"},{"id":"ref-for-w3c-council\u2466"},{"id":"ref-for-w3c-council\u2467"},{"id":"ref-for-w3c-council\u2468"},{"id":"ref-for-w3c-council\u2460\u24ea"},{"id":"ref-for-w3c-council\u2460\u2460"},{"id":"ref-for-w3c-council\u2460\u2461"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2462"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2463"},{"id":"ref-for-w3c-council\u2460\u2464"},{"id":"ref-for-w3c-council\u2460\u2465"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2466"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2467"},{"id":"ref-for-w3c-council\u2460\u2468"},{"id":"ref-for-w3c-council\u2461\u24ea"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-w3c-council\u2461\u2460"},{"id":"ref-for-w3c-council\u2461\u2461"},{"id":"ref-for-w3c-council\u2461\u2462"},{"id":"ref-for-w3c-council\u2461\u2463"},{"id":"ref-for-w3c-council\u2461\u2464"},{"id":"ref-for-w3c-council\u2461\u2465"},{"id":"ref-for-w3c-council\u2461\u2466"},{"id":"ref-for-w3c-council\u2461\u2467"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-w3c-council\u2461\u2468"},{"id":"ref-for-w3c-council\u2462\u24ea"},{"id":"ref-for-w3c-council\u2462\u2460"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2461"},{"id":"ref-for-w3c-council\u2462\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2463"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2464"},{"id":"ref-for-w3c-council\u2462\u2465"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2466"},{"id":"ref-for-w3c-council\u2462\u2467"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#w3c-council"},
+"w3c-council-chair": {"dfnID":"w3c-council-chair","dfnText":"Chair","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-council-chair"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-w3c-council-chair\u2460"}],"title":"5.6.2.4. \nShort Circuit"},{"refs":[{"id":"ref-for-w3c-council-chair\u2461"},{"id":"ref-for-w3c-council-chair\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-w3c-council-chair\u2463"},{"id":"ref-for-w3c-council-chair\u2464"},{"id":"ref-for-w3c-council-chair\u2465"},{"id":"ref-for-w3c-council-chair\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#w3c-council-chair"},
+"w3c-group": {"dfnID":"w3c-group","dfnText":"W3C Group","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-group"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-w3c-group\u2460"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-w3c-group\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-w3c-group\u2462"},{"id":"ref-for-w3c-group\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"#w3c-group"},
+"w3c-member": {"dfnID":"w3c-member","dfnText":"W3C Members","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-member"}],"title":"2.1.3. \nGood Standing"},{"refs":[{"id":"ref-for-w3c-member\u2460"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-w3c-member\u2461"},{"id":"ref-for-w3c-member\u2462"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-w3c-member\u2463"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-w3c-member\u2464"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-w3c-member\u2465"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-w3c-member\u2466"}],"title":"9. \nMember Submissions"}],"url":"#w3c-member"},
+"w3c-recommendation-track": {"dfnID":"w3c-recommendation-track","dfnText":"W3C Recommendation Track","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-recommendation-track"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460"},{"id":"ref-for-w3c-recommendation-track\u2461"},{"id":"ref-for-w3c-recommendation-track\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2463"},{"id":"ref-for-w3c-recommendation-track\u2464"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2465"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2466"},{"id":"ref-for-w3c-recommendation-track\u2467"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2468"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u24ea"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2462"}],"title":"6.5.6. \nRegistries and Patents"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2463"},{"id":"ref-for-w3c-recommendation-track\u2460\u2464"},{"id":"ref-for-w3c-recommendation-track\u2460\u2465"}],"title":"6.6. \nSwitching Tracks"}],"url":"#w3c-recommendation-track"},
+"w3c-recommendation-track-document": {"dfnID":"w3c-recommendation-track-document","dfnText":"W3C Recommendation Track document","external":false,"refSections":[],"url":"#w3c-recommendation-track-document"},
+"w3c-registry": {"dfnID":"w3c-registry","dfnText":"W3C Registry","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-registry"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-w3c-registry\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#w3c-registry"},
+"wgparticipant": {"dfnID":"wgparticipant","dfnText":"participants in a Working Group","external":false,"refSections":[{"refs":[{"id":"ref-for-wgparticipant"}],"title":"3. \nGroups and Participation"},{"refs":[{"id":"ref-for-wgparticipant"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#wgparticipant"},
+};
+
+document.addEventListener("DOMContentLoaded", ()=>{
+    genAllDfnPanels();
+
+    document.body.addEventListener("click", (e) => {
+        // If not handled already, just hide all dfn panels.
+        hideAllDfnPanels();
+    });
+});
+
+window.addEventListener("resize", () => {
+    // Pin any visible dfn panel
+    queryAll(".dfn-panel.on, .dfn-panel.activated").forEach(el=>positionDfnPanel(el));
+});
+
+function genAllDfnPanels() {
+    for(const panelData of Object.values(dfnPanelData)) {
+        const dfnID = panelData.dfnID;
+        const dfn = document.getElementById(dfnID);
+        if(!dfn) {
+            console.log(`Can't find dfn#${dfnID}.`, panelData);
+            continue;
+        }
+        dfn.panelData = panelData;
+        insertDfnPopupAction(dfn);
+    }
+}
+
+function genDfnPanel(dfn, { dfnID, url, dfnText, refSections, external }) {
+    const dfnPanel = mk.aside({
+        class: "dfn-panel on",
+        id: `infopanel-for-${dfnID}`,
+        "data-for": dfnID,
+        "aria-labelled-by":`infopaneltitle-for-${dfnID}`,
+        },
+        mk.span({id:`infopaneltitle-for-${dfnID}`, style:"display:none"},
+            `Info about the '${dfnText}' ${external?"external":""} reference.`),
+        mk.a({href:url, class:"dfn-link"}, url),
+        refSections.length == 0 ? [] :
+            mk.b({}, "Referenced in:"),
+            mk.ul({},
+                ...refSections.map(section=>
+                    mk.li({},
+                        ...section.refs.map((ref, refI)=>
+                            [
+                                mk.a({ href: `#${ref.id}` },
+                                    (refI == 0) ? section.title : `(${refI + 1})`
+                                ),
+                                " ",
+                            ]
+                        ),
+                    ),
+                ),
+            ),
+        genLinkingSyntaxes(dfn),
+    );
+
+    dfnPanel.addEventListener('click', (event) => {
+        if (event.target.nodeName == 'A') {
+            scrollToTargetAndHighlight(event);
+            pinDfnPanel(dfnPanel);
+        }
+        event.stopPropagation();
+        refocusOnTarget(event);
+    });
+    dfnPanel.addEventListener('keydown', (event) => {
+        if(event.keyCode == 27) { // Escape key
+            hideDfnPanel({dfnPanel});
+            event.stopPropagation();
+            event.preventDefault();
+        }
+    });
+
+    dfnPanel.dfn = dfn;
+    dfn.dfnPanel = dfnPanel;
+    return dfnPanel;
+}
+
+
+
+function hideAllDfnPanels() {
+    // Delete the currently-active dfn panel.
+    queryAll(".dfn-panel").forEach(dfnPanel=>hideDfnPanel({dfnPanel}));
+}
+
+function showDfnPanel(dfn) {
+    hideAllDfnPanels(); // Only display one at a time.
+
+    dfn.setAttribute("aria-expanded", "true");
+
+    const dfnPanel = genDfnPanel(dfn, dfn.panelData);
+
+    // Give the dfn a unique tabindex, and then
+    // give all the tabbable panel bits successive indexes.
+    let tabIndex = 100;
+    dfn.tabIndex = tabIndex++;
+    const tabbable = dfnPanel.querySelectorAll(":is(a, button)");
+    for (const el of tabbable) {
+        el.tabIndex = tabIndex++;
+    }
+
+    append(document.body, dfnPanel);
+    positionDfnPanel(dfnPanel);
+}
+
+function positionDfnPanel(dfnPanel) {
+    const dfn = dfnPanel.dfn;
+    const dfnPos = getBounds(dfn);
+    dfnPanel.style.top = dfnPos.bottom + "px";
+    dfnPanel.style.left = dfnPos.left + "px";
+
+    const panelPos = dfnPanel.getBoundingClientRect();
+    const panelMargin = 8;
+    const maxRight = document.body.parentNode.clientWidth - panelMargin;
+    if (panelPos.right > maxRight) {
+        const overflowAmount = panelPos.right - maxRight;
+        const newLeft = Math.max(panelMargin, dfnPos.left - overflowAmount);
+        dfnPanel.style.left = newLeft + "px";
+    }
+}
+
+function pinDfnPanel(dfnPanel) {
+    // Switch it to "activated" state, which pins it.
+    dfnPanel.classList.add("activated");
+    dfnPanel.style.position = "fixed";
+    dfnPanel.style.left = null;
+    dfnPanel.style.top = null;
+}
+
+function hideDfnPanel({dfn, dfnPanel}) {
+    if(!dfnPanel) dfnPanel = dfn.dfnPanel;
+    if(!dfn) dfn = dfnPanel.dfn;
+    dfn.dfnPanel = undefined;
+    dfnPanel.dfn = undefined;
+    dfn.setAttribute("aria-expanded", "false");
+    dfn.tabIndex = undefined;
+    dfnPanel.remove()
+}
+
+function toggleDfnPanel(dfn) {
+    if(dfn.dfnPanel) {
+        hideDfnPanel(dfn);
+    } else {
+        showDfnPanel(dfn);
+    }
+}
+
+function insertDfnPopupAction(dfn) {
+    dfn.setAttribute('role', 'button');
+    dfn.setAttribute('aria-expanded', 'false')
+    dfn.tabIndex = 0;
+    dfn.classList.add('has-dfn-panel');
+    dfn.addEventListener('click', (event) => {
+        toggleDfnPanel(dfn);
+        event.stopPropagation();
+    });
+    dfn.addEventListener('keypress', (event) => {
+        const kc = event.keyCode;
+        // 32->Space, 13->Enter
+        if(kc == 32 || kc == 13) {
+            toggleDfnPanel(dfn);
+            event.stopPropagation();
+            event.preventDefault();
+        }
+    });
+}
+
+function refocusOnTarget(event) {
+    const target = event.target;
+    setTimeout(() => {
+        // Refocus on the event.target element.
+        // This is needed after browser scrolls to the destination.
+        target.focus();
+    });
+}
+
+// TODO: shared util
+// Returns the root-level absolute position {left and top} of element.
+function getBounds(el, relativeTo=document.body) {
+    const relativeRect = relativeTo.getBoundingClientRect();
+    const elRect = el.getBoundingClientRect();
+    const top = elRect.top - relativeRect.top;
+    const left = elRect.left - relativeRect.left;
+    return {
+        top,
+        left,
+        bottom: top + elRect.height,
+        right: left + elRect.width,
+    }
+}
+
+function scrollToTargetAndHighlight(event) {
+    let hash = event.target.hash;
+    if (hash) {
+        hash = decodeURIComponent(hash.substring(1));
+        const dest = document.getElementById(hash);
+        if (dest) {
+            dest.classList.add('highlighted');
+            setTimeout(() => dest.classList.remove('highlighted'), 1000);
+        }
+    }
+}
+
+// Functions, divided by link type, that wrap an autolink's
+// contents with the appropriate outer syntax.
+// Alternately, a string naming another type they format
+// the same as.
+function needsFor(type) {
+    switch(type) {
+        case "descriptor":
+        case "value":
+        case "element-attr":
+        case "attr-value":
+        case "element-state":
+        case "method":
+        case "constructor":
+        case "argument":
+        case "attribute":
+        case "const":
+        case "dict-member":
+        case "event":
+        case "enum-value":
+        case "stringifier":
+        case "serializer":
+        case "iterator":
+        case "maplike":
+        case "setlike":
+        case "state":
+        case "mode":
+        case "context":
+        case "facet": return true;
+
+        default: return false;
+    }
+}
+function refusesFor(type) {
+    switch(type) {
+        case "property":
+        case "element":
+        case "interface":
+        case "namespace":
+        case "callback":
+        case "dictionary":
+        case "enum":
+        case "exception":
+        case "typedef":
+        case "http-header":
+        case "permission": return true;
+
+        default: return false;
+    }
+}
+function linkFormatterFromType(type) {
+    switch(type) {
+        case 'scheme':
+        case 'permission':
+        case 'dfn': return (text) => `[=${text}=]`;
+
+        case 'abstract-op': return (text) => `[\$${text}\$]`;
+
+        case 'function':
+        case 'at-rule':
+        case 'selector':
+        case 'value': return (text) => `''${text}''`;
+
+        case 'http-header': return (text) => `[:${text}:]`;
+
+        case 'interface':
+        case 'constructor':
+        case 'method':
+        case 'argument':
+        case 'attribute':
+        case 'callback':
+        case 'dictionary':
+        case 'dict-member':
+        case 'enum':
+        case 'enum-value':
+        case 'exception':
+        case 'const':
+        case 'typedef':
+        case 'stringifier':
+        case 'serializer':
+        case 'iterator':
+        case 'maplike':
+        case 'setlike':
+        case 'extended-attribute':
+        case 'event':
+        case 'idl': return (text) => `{{${text}}}`;
+
+        case 'element-state':
+        case 'element-attr':
+        case 'attr-value':
+        case 'element': return (element) => `<{${element}}>`;
+
+        case 'grammar': return (text) => `${text} (within a <pre class=prod>)`;
+
+        case 'type': return (text)=> `<<${text}>>`;
+
+        case 'descriptor':
+        case 'property': return (text) => `'${text}'`;
+
+        default: return;
+    };
+};
+
+function genLinkingSyntaxes(dfn) {
+    if(dfn.tagName != "DFN") return;
+
+    const type = dfn.getAttribute('data-dfn-type');
+    if(!type) {
+        console.log(`<dfn> doesn't have a data-dfn-type:`, dfn);
+        return [];
+    }
+
+    // Return a function that wraps link text based on the type
+    const linkFormatter = linkFormatterFromType(type);
+    if(!linkFormatter) {
+        console.log(`<dfn> has an unknown data-dfn-type:`, dfn);
+        return [];
+    }
+
+    let ltAlts;
+    if(dfn.hasAttribute('data-lt')) {
+        ltAlts = dfn.getAttribute('data-lt')
+            .split("|")
+            .map(x=>x.trim());
+    } else {
+        ltAlts = [dfn.textContent.trim()];
+    }
+    if(type == "type") {
+        // lt of "<foo>", but "foo" is the interior;
+        // <<foo/bar>> is how you write it with a for,
+        // not <foo/<bar>> or whatever.
+        for(var i = 0; i < ltAlts.length; i++) {
+            const lt = ltAlts[i];
+            const match = /<(.*)>/.exec(lt);
+            if(match) { ltAlts[i] = match[1]; }
+        }
+    }
+
+    let forAlts;
+    if(dfn.hasAttribute('data-dfn-for')) {
+        forAlts = dfn.getAttribute('data-dfn-for')
+            .split(",")
+            .map(x=>x.trim());
+    } else {
+        forAlts = [''];
+    }
+
+    let linkingSyntaxes = [];
+    if(!needsFor(type)) {
+        for(const lt of ltAlts) {
+            linkingSyntaxes.push(linkFormatter(lt));
+        }
+    }
+    if(!refusesFor(type)) {
+        for(const f of forAlts) {
+            linkingSyntaxes.push(linkFormatter(`${f}/${ltAlts[0]}`))
+        }
+    }
+    return [
+        mk.b({}, 'Possible linking syntaxes:'),
+        mk.ul({},
+            ...linkingSyntaxes.map(link => {
+                const copyLink = async () =>
+                    await navigator.clipboard.writeText(link);
+                return mk.li({},
+                    mk.div({ class: 'link-item' },
+                        mk.button({
+                            class: 'copy-icon', title: 'Copy',
+                            type: 'button',
+                            _onclick: copyLink,
+                            tabindex: 0,
+                        }, mk.span({ class: 'icon' }) ),
+                        mk.span({}, link)
+                    )
+                );
+            })
+        )
+    ];
+}
+}
+</script>
+<script>/* Boilerplate: script-ref-hints */
+"use strict";
+{
+let refsData = {
+"#EventsW": {"displayText":"workshop","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"workshop","type":"dfn","url":"#EventsW"},
+"#FormalObjection": {"displayText":"formal objection","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"formal objection","type":"dfn","url":"#FormalObjection"},
+"#GeneralChairs": {"displayText":"chair","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chair","type":"dfn","url":"#GeneralChairs"},
+"#GroupsIG": {"displayText":"interest groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"interest groups","type":"dfn","url":"#GroupsIG"},
+"#GroupsWG": {"displayText":"working groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"working groups","type":"dfn","url":"#GroupsWG"},
+"#Member-only": {"displayText":"member-only","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member-only","type":"dfn","url":"#Member-only"},
+"#MemberSubmission": {"displayText":"member submission","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member submission","type":"dfn","url":"#MemberSubmission"},
+"#RecsCR": {"displayText":"candidate recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation","type":"dfn","url":"#RecsCR"},
+"#RecsObs": {"displayText":"obsolete recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"obsolete recommendation","type":"dfn","url":"#RecsObs"},
+"#RecsSup": {"displayText":"superseded recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"superseded recommendation","type":"dfn","url":"#RecsSup"},
+"#RecsW3C": {"displayText":"w3c recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c recommendation","type":"dfn","url":"#RecsW3C"},
+"#RecsWD": {"displayText":"working draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"working draft","type":"dfn","url":"#RecsWD"},
+"#RescindedRec": {"displayText":"rescinded recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rescinded recommendation","type":"dfn","url":"#RescindedRec"},
+"#Team-only": {"displayText":"team-only","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team-only","type":"dfn","url":"#Team-only"},
+"#TeamContact": {"displayText":"team contact","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team contact","type":"dfn","url":"#TeamContact"},
+"#WGNote": {"displayText":"note","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"note","type":"dfn","url":"#WGNote"},
+"#acknowledged": {"displayText":"acknowledged","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"acknowledged","type":"dfn","url":"#acknowledged"},
+"#adequate-implementation": {"displayText":"adequate implementation experience","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"adequate implementation experience","type":"dfn","url":"#adequate-implementation"},
+"#adopted-draft": {"displayText":"adopted draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"adopted draft","type":"dfn","url":"#adopted-draft"},
+"#advisory-board": {"displayText":"ab","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ab","type":"dfn","url":"#advisory-board"},
+"#advisory-committee": {"displayText":"advisory committee","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"advisory committee","type":"dfn","url":"#advisory-committee"},
+"#advisory-committee-appeal": {"displayText":"ac appeal","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ac appeal","type":"dfn","url":"#advisory-committee-appeal"},
+"#advisory-committee-representative": {"displayText":"advisory committee representative","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"advisory committee representative","type":"dfn","url":"#advisory-committee-representative"},
+"#advisory-committee-review": {"displayText":"ac review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ac review","type":"dfn","url":"#advisory-committee-review"},
+"#allow-new-features": {"displayText":"allow new features","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"allow new features","type":"dfn","url":"#allow-new-features"},
+"#appeal-vote": {"displayText":"appeal vote","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"appeal vote","type":"dfn","url":"#appeal-vote"},
+"#at-risk": {"displayText":"at risk","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"at risk","type":"dfn","url":"#at-risk"},
+"#bod": {"displayText":"board","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"board","type":"dfn","url":"#bod"},
+"#candidate-addition": {"displayText":"candidate addition","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate addition","type":"dfn","url":"#candidate-addition"},
+"#candidate-amendment": {"displayText":"candidate amendment","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate amendment","type":"dfn","url":"#candidate-amendment"},
+"#candidate-correction": {"displayText":"candidate correction","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate correction","type":"dfn","url":"#candidate-correction"},
+"#candidate-recommendation-draft": {"displayText":"candidate recommendation draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation draft","type":"dfn","url":"#candidate-recommendation-draft"},
+"#candidate-recommendation-review-period": {"displayText":"candidate recommendation review period","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation review period","type":"dfn","url":"#candidate-recommendation-review-period"},
+"#candidate-recommendation-snapshot": {"displayText":"crs","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"crs","type":"dfn","url":"#candidate-recommendation-snapshot"},
+"#candidate-registry": {"displayText":"candidate registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate registry","type":"dfn","url":"#candidate-registry"},
+"#ceo": {"displayText":"ceo","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ceo","type":"dfn","url":"#ceo"},
+"#charter": {"displayText":"charter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter","type":"dfn","url":"#charter"},
+"#charter-draft": {"displayText":"charter draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter draft","type":"dfn","url":"#charter-draft"},
+"#charter-refinement": {"displayText":"charter refinement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter refinement","type":"dfn","url":"#charter-refinement"},
+"#charter-review-notice": {"displayText":"charter review notice","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter review notice","type":"dfn","url":"#charter-review-notice"},
+"#chartered-group": {"displayText":"chartered groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chartered groups","type":"dfn","url":"#chartered-group"},
+"#chartering-facilitator": {"displayText":"chartering facilitator","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chartering facilitator","type":"dfn","url":"#chartering-facilitator"},
+"#convened": {"displayText":"convened","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"convened","type":"dfn","url":"#convened"},
+"#council-report": {"displayText":"council report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council report","type":"dfn","url":"#council-report"},
+"#council-team-contact": {"displayText":"council team contact","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council team contact","type":"dfn","url":"#council-team-contact"},
+"#custodian": {"displayText":"custodian","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"custodian","type":"dfn","url":"#custodian"},
+"#def-Consensus": {"displayText":"consensus","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"consensus","type":"dfn","url":"#def-Consensus"},
+"#def-Dissent": {"displayText":"dissent","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"dissent","type":"dfn","url":"#def-Dissent"},
+"#def-Unanimity": {"displayText":"unanimity","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"unanimity","type":"dfn","url":"#def-Unanimity"},
+"#def-w3c-decision": {"displayText":"w3c decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c decision","type":"dfn","url":"#def-w3c-decision"},
+"#dfn-charter-extension": {"displayText":"charter extension","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter extension","type":"dfn","url":"#dfn-charter-extension"},
+"#dfn-wide-review": {"displayText":"wide review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"wide review","type":"dfn","url":"#dfn-wide-review"},
+"#discontinuedREC": {"displayText":"discontinued draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"discontinued draft","type":"dfn","url":"#discontinuedREC"},
+"#dismissed": {"displayText":"dismissal","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"dismissal","type":"dfn","url":"#dismissed"},
+"#editorial-change": {"displayText":"editorial change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"editorial change","type":"dfn","url":"#editorial-change"},
+"#editors-draft": {"displayText":"editor's draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"editor's draft","type":"dfn","url":"#editors-draft"},
+"#elected-group": {"displayText":"elected groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"elected groups","type":"dfn","url":"#elected-group"},
+"#embedded-registry": {"displayText":"embedded registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"embedded registry","type":"dfn","url":"#embedded-registry"},
+"#erratum": {"displayText":"erratum","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"erratum","type":"dfn","url":"#erratum"},
+"#exclusion-draft": {"displayText":"exclusion draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"exclusion draft","type":"dfn","url":"#exclusion-draft"},
+"#exclusion-draft-charter": {"displayText":"exclusion draft charter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"exclusion draft charter","type":"dfn","url":"#exclusion-draft-charter"},
+"#formally-addressed": {"displayText":"formally addressed","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"formally addressed","type":"dfn","url":"#formally-addressed"},
+"#fpwd": {"displayText":"first public working draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"first public working draft","type":"dfn","url":"#fpwd"},
+"#ftf-meeting": {"displayText":"face-to-face meeting","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"face-to-face meeting","type":"dfn","url":"#ftf-meeting"},
+"#fully-addressed": {"displayText":"fully addressed","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"fully addressed","type":"dfn","url":"#fully-addressed"},
+"#good-standing": {"displayText":"good standing","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"good standing","type":"dfn","url":"#good-standing"},
+"#group-decision": {"displayText":"group decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"group decision","type":"dfn","url":"#group-decision"},
+"#invited-expert-in-a-working-group": {"displayText":"invited expert in a working group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"invited expert in a working group","type":"dfn","url":"#invited-expert-in-a-working-group"},
+"#last-call-for-review-of-proposed-additions": {"displayText":"last call for review of proposed additions","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed additions","type":"dfn","url":"#last-call-for-review-of-proposed-additions"},
+"#last-call-for-review-of-proposed-corrections": {"displayText":"last call for review of proposed corrections","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed corrections","type":"dfn","url":"#last-call-for-review-of-proposed-corrections"},
+"#last-call-for-review-of-proposed-corrections-and-additions": {"displayText":"last call for review of proposed corrections and additions","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed corrections and additions","type":"dfn","url":"#last-call-for-review-of-proposed-corrections-and-additions"},
+"#last-call-review": {"displayText":"last call for review of proposed amendments","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed amendments","type":"dfn","url":"#last-call-review"},
+"#member-association": {"displayText":"member association","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member association","type":"dfn","url":"#member-association"},
+"#member-representative-in-an-interest-group": {"displayText":"member representative in an interest group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member representative in an interest group","type":"dfn","url":"#member-representative-in-an-interest-group"},
+"#minor-changes": {"displayText":"minor changes","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minor changes","type":"dfn","url":"#minor-changes"},
+"#minority-opinion": {"displayText":"minority opinion","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minority opinion","type":"dfn","url":"#minority-opinion"},
+"#minutes": {"displayText":"minutes","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minutes","type":"dfn","url":"#minutes"},
+"#note-draft": {"displayText":"note draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"note draft","type":"dfn","url":"#note-draft"},
+"#overrule": {"displayText":"overrule","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"overrule","type":"dfn","url":"#overrule"},
+"#participant": {"displayText":"participant","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"participant","type":"dfn","url":"#participant"},
+"#patent-review-drafts": {"displayText":"patent review drafts","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"patent review drafts","type":"dfn","url":"#patent-review-drafts"},
+"#primary-affiliation": {"displayText":"primary affiliation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"primary affiliation","type":"dfn","url":"#primary-affiliation"},
+"#proposed-amendments": {"displayText":"proposed amendments","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"proposed amendments","type":"dfn","url":"#proposed-amendments"},
+"#publishing": {"displayText":"publish","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"publish","type":"dfn","url":"#publishing"},
+"#registry": {"displayText":"registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry","type":"dfn","url":"#registry"},
+"#registry-change": {"displayText":"registry change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry change","type":"dfn","url":"#registry-change"},
+"#registry-data": {"displayText":"registry data","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry data","type":"dfn","url":"#registry-data"},
+"#registry-data-report": {"displayText":"registry data report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry data report","type":"dfn","url":"#registry-data-report"},
+"#registry-definition": {"displayText":"registry definition","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry definition","type":"dfn","url":"#registry-definition"},
+"#registry-entry": {"displayText":"registry entry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry entry","type":"dfn","url":"#registry-entry"},
+"#registry-report": {"displayText":"registry report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry report","type":"dfn","url":"#registry-report"},
+"#registry-table": {"displayText":"registry table","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry table","type":"dfn","url":"#registry-table"},
+"#registry-track": {"displayText":"registry track","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry track","type":"dfn","url":"#registry-track"},
+"#rejected": {"displayText":"rejected","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rejected","type":"dfn","url":"#rejected"},
+"#related-member": {"displayText":"related member","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"related member","type":"dfn","url":"#related-member"},
+"#renounce": {"displayText":"renunciation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"renunciation","type":"dfn","url":"#renounce"},
+"#rescinded-candidate-recommendation": {"displayText":"rescinded candidate recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rescinded candidate recommendation","type":"dfn","url":"#rescinded-candidate-recommendation"},
+"#reviewform": {"displayText":"call for review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"call for review","type":"dfn","url":"#reviewform"},
+"#statement": {"displayText":"w3c statement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c statement","type":"dfn","url":"#statement"},
+"#submission-appeals": {"displayText":"submission appeals","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"submission appeals","type":"dfn","url":"#submission-appeals"},
+"#submitter": {"displayText":"submitter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"submitter","type":"dfn","url":"#submitter"},
+"#subsidiary": {"displayText":"subsidiary","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"subsidiary","type":"dfn","url":"#subsidiary"},
+"#substantive-change": {"displayText":"substantive change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"substantive change","type":"dfn","url":"#substantive-change"},
+"#team": {"displayText":"team","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team","type":"dfn","url":"#team"},
+"#team-correction": {"displayText":"team correction","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team correction","type":"dfn","url":"#team-correction"},
+"#team-decision": {"displayText":"team decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team decision","type":"dfn","url":"#team-decision"},
+"#technical-agreement": {"displayText":"technical agreement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"technical agreement","type":"dfn","url":"#technical-agreement"},
+"#technical-architecture-group": {"displayText":"tag","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"tag","type":"dfn","url":"#technical-architecture-group"},
+"#technical-report": {"displayText":"technical report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"technical report","type":"dfn","url":"#technical-report"},
+"#trans-req": {"displayText":"transition requests","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"transition requests","type":"dfn","url":"#trans-req"},
+"#update-requests": {"displayText":"update requests","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"update requests","type":"dfn","url":"#update-requests"},
+"#uphold": {"displayText":"upholding","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"upholding","type":"dfn","url":"#uphold"},
+"#w3c-council": {"displayText":"w3c council","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c council","type":"dfn","url":"#w3c-council"},
+"#w3c-council-chair": {"displayText":"council chair","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council chair","type":"dfn","url":"#w3c-council-chair"},
+"#w3c-group": {"displayText":"w3c group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c group","type":"dfn","url":"#w3c-group"},
+"#w3c-member": {"displayText":"member","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member","type":"dfn","url":"#w3c-member"},
+"#w3c-recommendation-track": {"displayText":"rec track","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rec track","type":"dfn","url":"#w3c-recommendation-track"},
+"#w3c-registry": {"displayText":"w3c registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c registry","type":"dfn","url":"#w3c-registry"},
+"https://www.w3.org/policies/patent-policy/#exclusion-opportunity": {"displayText":"Exclusion Opportunity","export":false,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"exclusion opportunity","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
+"https://www.w3.org/policies/patent-policy/#patent-advisory-group": {"displayText":"Patent Advisory Group","export":true,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"patent advisory group","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
+};
+
+function mkRefHint(link, ref) {
+    const linkText = link.textContent;
+    let dfnTextElements = '';
+    if (ref.displayText.toLowerCase() != linkText.toLowerCase()) {
+        // Give the original term if it's being displayed in a different way.
+        // But allow casing differences, they're insignificant.
+        dfnTextElements =
+            mk.li({},
+                mk.b({}, "Term: "),
+                mk.span({}, ref.displayText)
+            );
+    }
+    const forList = ref.for_;
+    let forListElements;
+    if(forList.length == 0) {
+        forListElements = [];
+    } else if(forList.length == 1) {
+        forListElements = mk.li({},
+            mk.b({}, "For: "),
+            mk.span({}, forList[0]),
+        );
+    } else {
+        forListElements = mk.li({},
+            mk.b({}, "For: "),
+            mk.ul({},
+                ...forList.map(forItem =>
+                    mk.li({},
+                        mk.span({}, forItem)
+                    ),
+                ),
+            ),
+        );
+    }
+    const url = ref.url;
+    const safeUrl = encodeURIComponent(url);
+    const hintPanel = mk.aside({
+        class: "ref-hint",
+        id: `ref-hint-for-${safeUrl}`,
+        "data-for": url,
+        "aria-labelled-by": `ref-hint-for-${safeUrl}`,
+    },
+        mk.ul({},
+            dfnTextElements,
+            mk.li({},
+                mk.b({}, "URL: "),
+                mk.a({ href: url, class: "ref" }, url),
+            ),
+            mk.li({},
+                mk.b({}, "Type: "),
+                mk.span({}, `${ref.type}`),
+            ),
+            mk.li({},
+                mk.b({}, "Spec: "),
+                mk.span({}, `${ref.spec ? ref.spec : ''}`),
+            ),
+            forListElements
+        ),
+    );
+    hintPanel.forLink = link;
+    setupRefHintEventListeners(link, hintPanel);
+    return hintPanel;
+}
+
+function hideAllRefHints() {
+    queryAll(".ref-hint").forEach(el=>hideRefHint(el));
+}
+
+function hideRefHint(refHint) {
+    const link = refHint.forLink;
+    link.setAttribute("aria-expanded", "false");
+    if(refHint.teardownEventListeners) {
+        refHint.teardownEventListeners();
+    }
+    refHint.remove();
+}
+
+function showRefHint(link) {
+    if(link.classList.contains("dfn-link")) return;
+    const url = link.getAttribute("href");
+    const refHintKey = link.getAttribute("data-refhint-key");
+    let key = url;
+    if(refHintKey) {
+        key = refHintKey + "_" + url;
+    }
+    const ref = refsData[key];
+    if(!ref) return;
+
+    hideAllRefHints(); // Only display one at this time.
+
+    const refHint = mkRefHint(link, ref);
+    append(document.body, refHint);
+    link.setAttribute("aria-expanded", "true");
+    positionRefHint(refHint);
+}
+
+function setupRefHintEventListeners(link, refHint) {
+    if (refHint.teardownEventListeners) return;
+    // Add event handlers to hide the refHint after the user moves away
+    // from both the link and refHint, if not hovering either within one second.
+    let timeout = null;
+    const startHidingRefHint = (event) => {
+        if (timeout) {
+            clearTimeout(timeout);
+        }
+        timeout = setTimeout(() => {
+            hideRefHint(refHint);
+        }, 1000);
+    }
+    const resetHidingRefHint = (event) => {
+        if (timeout) clearTimeout(timeout);
+        timeout = null;
+    };
+    link.addEventListener("mouseleave", startHidingRefHint);
+    link.addEventListener("mouseenter", resetHidingRefHint);
+    link.addEventListener("blur", startHidingRefHint);
+    link.addEventListener("focus", resetHidingRefHint);
+    refHint.addEventListener("mouseleave", startHidingRefHint);
+    refHint.addEventListener("mouseenter", resetHidingRefHint);
+    refHint.addEventListener("blur", startHidingRefHint);
+    refHint.addEventListener("focus", resetHidingRefHint);
+
+    refHint.teardownEventListeners = () => {
+        // remove event listeners
+        resetHidingRefHint();
+        link.removeEventListener("mouseleave", startHidingRefHint);
+        link.removeEventListener("mouseenter", resetHidingRefHint);
+        link.removeEventListener("blur", startHidingRefHint);
+        link.removeEventListener("focus", resetHidingRefHint);
+        refHint.removeEventListener("mouseleave", startHidingRefHint);
+        refHint.removeEventListener("mouseenter", resetHidingRefHint);
+        refHint.removeEventListener("blur", startHidingRefHint);
+        refHint.removeEventListener("focus", resetHidingRefHint);
+    };
+}
+
+function positionRefHint(refHint) {
+    const link = refHint.forLink;
+    const linkPos = getBounds(link);
+    refHint.style.top = linkPos.bottom + "px";
+    refHint.style.left = linkPos.left + "px";
+
+    const panelPos = refHint.getBoundingClientRect();
+    const panelMargin = 8;
+    const maxRight = document.body.parentNode.clientWidth - panelMargin;
+    if (panelPos.right > maxRight) {
+        const overflowAmount = panelPos.right - maxRight;
+        const newLeft = Math.max(panelMargin, linkPos.left - overflowAmount);
+        refHint.style.left = newLeft + "px";
+    }
+}
+
+// TODO: shared util
+// Returns the root-level absolute position {left and top} of element.
+function getBounds(el, relativeTo=document.body) {
+    const relativeRect = relativeTo.getBoundingClientRect();
+    const elRect = el.getBoundingClientRect();
+    const top = elRect.top - relativeRect.top;
+    const left = elRect.left - relativeRect.left;
+    return {
+        top,
+        left,
+        bottom: top + elRect.height,
+        right: left + elRect.width,
+    }
+}
+
+function showRefHintListener(e) {
+    // If the target isn't in a link (or is a link),
+    // just ignore it.
+    let link = e.target.closest("a");
+    if(!link) return;
+
+    // If the target is in a ref-hint panel
+    // (aka a link in the already-open one),
+    // also just ignore it.
+    if(link.closest(".ref-hint")) return;
+
+    // Otherwise, show the panel for the link.
+    showRefHint(link);
+}
+
+function hideAllHintsListener(e) {
+    // If the click is inside a ref-hint panel, ignore it.
+    if(e.target.closest(".ref-hint")) return;
+    // Otherwise, close all the current panels.
+    hideAllRefHints();
+}
+
+document.addEventListener("DOMContentLoaded", () => {
+    document.body.addEventListener("mousedown", showRefHintListener);
+    document.body.addEventListener("focus", showRefHintListener);
+
+    document.body.addEventListener("click", hideAllHintsListener);
+});
+
+window.addEventListener("resize", () => {
+    // Hide any open ref hint.
+    hideAllRefHints();
+});
+}
+</script>

From 8da8de548cb3b12a0767b566e29e4a65c4c57e73 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 09:05:55 +0900
Subject: [PATCH 206/237] Fix link

---
 snapshots/2025-05.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
index 676c1c19..28769472 100644
--- a/snapshots/2025-05.html
+++ b/snapshots/2025-05.html
@@ -619,7 +619,7 @@ <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
     <div data-fill-with="spec-metadata">
      <dl>
       <dt>This version:
-      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/snapshots/2025-05</a>
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/snapshots/2025-05">https://www.w3.org/policies/process/drafts/snapshots/2025-05</a>
       <dt>Editor’s Draft:
       <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/</a>
       <dt>Latest published version:

From 1b5d916edd0219d0f479fa4156a121bf1ab135ff Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 09:10:34 +0900
Subject: [PATCH 207/237] Fix link

---
 index.bs               | 2 +-
 snapshots/2025-05.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 962a1ad9..a8713c32 100644
--- a/index.bs
+++ b/index.bs
@@ -5597,7 +5597,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 
 	<p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
 	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
-	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2F">diff from Process 2023 to this latest version</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2F">diff from Process 2023 to this latest version</a>,
 	as well as
 	a <a href="https://github.com/w3c/process/compare/p2023_1...main">detailed log of all changes since then</a>
 	are available.
diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
index 28769472..5b7f5f91 100644
--- a/snapshots/2025-05.html
+++ b/snapshots/2025-05.html
@@ -4949,7 +4949,7 @@ <h2 class="non-normative nonum heading settled" id="changes"><span class="conten
     <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></span><a class="self-link" href="#changes-2024"></a></h3>
     <p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
 	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
-	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2FConsortium%2FProcess%2FDrafts%2Fsnapshots%2F2025-05">diff from Process 2023 to this latest version</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2Fsnapshots%2F2025-05">diff from Process 2023 to this latest version</a>,
 	as well as
 	a <a href="https://github.com/w3c/process/compare/p2023_1...2025-review-draft">detailed log of all changes since then</a> are available. </p>
     <p>In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:</p>

From 89f6f58dd67fac11ce022f049f3edac1787472fc Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 11:43:19 +0900
Subject: [PATCH 208/237] Tweak changes section

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs               | 156 +++++++++++++++++++++--------------------
 snapshots/2025-05.html | 104 ++++++++++++++-------------
 2 files changed, 131 insertions(+), 129 deletions(-)

diff --git a/index.bs b/index.bs
index a8713c32..d7d1cffd 100644
--- a/index.bs
+++ b/index.bs
@@ -5605,69 +5605,18 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 	In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:
 
 	<dl>
-		<dt>Changes to formal decision making and escalation
-		<dd>
-			<ul>
-				<li>
-					Adjust the rules guiding initiation of Councils,
-					to make the deadline strict,
-					and to provide a fallback mechanism if they are not met.
-					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>)
-
-				<li>
-					Make the Council's short-circuit a little more flexible.
-					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
-
-				<li>
-					Adjust AC appeal vote threshold based on participation,
-					aligning with the thresholds and super majority requirements
-					for "Requisite Member Vote" from the W3C Bylaws.
-					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
-
-				<li>
-					Exclude TAG/AB from voting on their own decisions/proposals.
-					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)
-
-				<li>
-					Fine-tune the rules about
-					how changes can be incorporated into a proposal
-					following an AC Review.
-					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
-
-				<li>
-					Limit the involvement of Tim Berners-Lee to the TAG proper,
-					not including the Council.
-					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>)
-
-				<li>
-					Council dismissal vote counts must be reported.
-					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)
-
-				<li>
-					Require documentation of how Formal Objections get resolved.
-					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>)
-
-				<li>
-					Let the originator of a proposal decide whether to try again
-					after addressing feedback
-					following an AC Appeal.
-					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
-
-				<li>
-					Put constraints on the timing of making Formal Objections public.
-					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
-			</ul>
-
 		<dt>Changes to technical reports and their publication
 		<dd>
 			<ul>
 				<li>
+					<strong>
 					Retire the Proposed Recommendation phase of the Recommendation track.
 					It was only used as a short-lived transition
 					during which various verifications and votes about CR were done.
 					These can be done on a CR
 					without having to republish it as a separate thing.
 					This simplifies the Process without changing the actual quality or consensus expectations.
+					</strong>
 					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)
 
 				<li id="streamlined-update">
@@ -5679,14 +5628,14 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					and nobody was using it.
 					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>)
 
-				<li>
-					Drop the requirement to publish every 6 months if nothing has changed.
-					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>)
-
 				<li>
 					Add a requirement to make progress on external issues for update requests
 					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>)
 
+				<li>
+					Drop the requirement to publish every 6 months if nothing has changed.
+					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>)
+
 				<li>
 					Enable Team to replace defunct registry custodians when no-one else can.
 					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>)
@@ -5724,21 +5673,80 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 		<dd>
 			<ul>
 				<li>
+					<strong>
 					Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
+					</strong>
 					(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>)
 
+				<li>
+					Be more specific about which types of changes to a charter must go through AC Review.
+					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>)
+
+				<li>
+					Require Chairs to be listed in Charters.
+					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
+
 				<li>
 					Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.
 					This change, while moderate in size, is purely editorial.
 					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>)
+			</ul>
 
+		<dt>Changes to formal decision making and escalation
+		<dd>
+			<ul>
 				<li>
-					Require Chairs to be listed in Charters.
-					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
+					Adjust the rules guiding initiation of Councils,
+					to make the deadline strict,
+					and to provide a fallback mechanism if they are not met.
+					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>)
 
 				<li>
-					Be more specific about which types of changes to a charter must go through AC Review.
-					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>)
+					Make the Council's short-circuit a little more flexible.
+					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
+
+				<li>
+					Exclude TAG/AB Members from voting on TAG/AB proposals in Councils.
+					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)
+
+				<li>
+					Limit the involvement of Tim Berners-Lee to the TAG proper,
+					not including the Council.
+					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>)
+
+				<li>
+					Council dismissal vote counts must be reported.
+					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)
+
+				<li>
+					Require documentation of how Formal Objections get resolved.
+					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>)
+
+				<li>
+					Put constraints on the timing of making Formal Objections public.
+					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
+
+				<li>
+					Fine-tune the rules about
+					how changes can be incorporated into a proposal
+					following an AC Review.
+					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
+
+				<li>
+					Adjust AC appeal vote threshold based on participation,
+					aligning with the thresholds and super majority requirements
+					for "Requisite Member Vote" from the W3C Bylaws.
+					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
+
+				<li>
+					Let the originator of a proposal decide whether to try again
+					after addressing feedback
+					following an AC Appeal.
+					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
+
+				<li>
+					Simplify provisions regarding substitute representatives and proxies.
+					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
 			</ul>
 
 		<dt>Other changes
@@ -5752,19 +5760,6 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a>
 					and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>)
 
-				<li>
-					Clarify how the outcome of certain ballots are determined.
-					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)
-
-				<li>
-					Stop citing the superseded TAG charter.
-					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)
-
-				<li>
-					Shift most of the non-normative discussion about Workshops to [[GUIDE]],
-					and reorganize the remaining normative requirements.
-					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
-
 				<li>
 					The section on Member Submissions was significantly shortened and simplified,
 					reducing the complexity under formal Process authority,
@@ -5773,13 +5768,22 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a>
 					and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>)
 
+				<li>
+					Clarify how the outcome of certain ballots are determined.
+					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)
+
+				<li>
+					Stop citing the superseded TAG charter.
+					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)
+
 				<li>
 					Clarify amount of leeway around incomplete nominations to TAG or AB elections.
 					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>)
 
 				<li>
-					Simplify provisions regarding substitute representatives and proxies.
-					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
+					Shift most of the non-normative discussion about Workshops to [[GUIDE]],
+					and reorganize the remaining normative requirements.
+					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
 
 				<li>
 					The URL of this document was changed
diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
index 5b7f5f91..5e3a57d4 100644
--- a/snapshots/2025-05.html
+++ b/snapshots/2025-05.html
@@ -4954,49 +4954,15 @@ <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Chan
 	a <a href="https://github.com/w3c/process/compare/p2023_1...2025-review-draft">detailed log of all changes since then</a> are available. </p>
     <p>In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:</p>
     <dl>
-     <dt>Changes to formal decision making and escalation 
-     <dd>
-      <ul>
-       <li> Adjust the rules guiding initiation of Councils,
-					to make the deadline strict,
-					and to provide a fallback mechanism if they are not met.
-					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>) 
-       <li> Make the Council’s short-circuit a little more flexible.
-					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>) 
-       <li> Adjust AC appeal vote threshold based on participation,
-					aligning with the thresholds and super majority requirements
-					for "Requisite Member Vote" from the W3C Bylaws.
-					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>) 
-       <li> Exclude TAG/AB from voting on their own decisions/proposals.
-					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>) 
-       <li> Fine-tune the rules about
-					how changes can be incorporated into a proposal
-					following an AC Review.
-					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>) 
-       <li> Limit the involvement of Tim Berners-Lee to the TAG proper,
-					not including the Council.
-					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>) 
-       <li> Council dismissal vote counts must be reported.
-					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>) 
-       <li> Require documentation of how Formal Objections get resolved.
-					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>) 
-       <li> Let the originator of a proposal decide whether to try again
-					after addressing feedback
-					following an AC Appeal.
-					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>) 
-       <li> Put constraints on the timing of making Formal Objections public.
-					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>) 
-      </ul>
      <dt>Changes to technical reports and their publication 
      <dd>
       <ul>
-       <li> Retire the Proposed Recommendation phase of the Recommendation track.
+       <li> <strong> Retire the Proposed Recommendation phase of the Recommendation track.
 					It was only used as a short-lived transition
 					during which various verifications and votes about CR were done.
 					These can be done on a CR
 					without having to republish it as a separate thing.
-					This simplifies the Process without changing the actual quality or consensus expectations.
-					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 
+					This simplifies the Process without changing the actual quality or consensus expectations. </strong> (See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 
        <li id="streamlined-update"><a class="self-link" href="#streamlined-update"></a> Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
 					This was meant to enable REC track publication with fewer/faster approval steps
 					when some stricter than usual criteria were fulfilled.
@@ -5004,10 +4970,10 @@ <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Chan
 					that this became unnecessary,
 					and nobody was using it.
 					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>) 
-       <li> Drop the requirement to publish every 6 months if nothing has changed.
-					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>) 
        <li> Add a requirement to make progress on external issues for update requests
 					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>) 
+       <li> Drop the requirement to publish every 6 months if nothing has changed.
+					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>) 
        <li> Enable Team to replace defunct registry custodians when no-one else can.
 					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>) 
        <li> Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
@@ -5030,15 +4996,49 @@ <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Chan
      <dt>Changes to chartering 
      <dd>
       <ul>
-       <li> Introduce a formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①②">Charter Refinement</a> phase prior to the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑥">AC Review</a>.
-					(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>) 
+       <li> <strong> Introduce a formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①②">Charter Refinement</a> phase prior to the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑥">AC Review</a>. </strong> (See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>) 
+       <li> Be more specific about which types of changes to a charter must go through AC Review.
+					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>) 
+       <li> Require Chairs to be listed in Charters.
+					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>) 
        <li> Reorganize and rephrase <a href="#CharterReview">§ 4.4 Charter Review and Approval</a> for readability and ease of understanding.
 					This change, while moderate in size, is purely editorial.
 					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>) 
-       <li> Require Chairs to be listed in Charters.
-					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>) 
-       <li> Be more specific about which types of changes to a charter must go through AC Review.
-					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>) 
+      </ul>
+     <dt>Changes to formal decision making and escalation 
+     <dd>
+      <ul>
+       <li> Adjust the rules guiding initiation of Councils,
+					to make the deadline strict,
+					and to provide a fallback mechanism if they are not met.
+					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>) 
+       <li> Make the Council’s short-circuit a little more flexible.
+					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>) 
+       <li> Exclude TAG/AB Members from voting on TAG/AB proposals in Councils.
+					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>) 
+       <li> Limit the involvement of Tim Berners-Lee to the TAG proper,
+					not including the Council.
+					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>) 
+       <li> Council dismissal vote counts must be reported.
+					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>) 
+       <li> Require documentation of how Formal Objections get resolved.
+					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>) 
+       <li> Put constraints on the timing of making Formal Objections public.
+					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>) 
+       <li> Fine-tune the rules about
+					how changes can be incorporated into a proposal
+					following an AC Review.
+					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>) 
+       <li> Adjust AC appeal vote threshold based on participation,
+					aligning with the thresholds and super majority requirements
+					for "Requisite Member Vote" from the W3C Bylaws.
+					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>) 
+       <li> Let the originator of a proposal decide whether to try again
+					after addressing feedback
+					following an AC Appeal.
+					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>) 
+       <li> Simplify provisions regarding substitute representatives and proxies.
+					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>) 
       </ul>
      <dt>Other changes 
      <dd>
@@ -5048,22 +5048,20 @@ <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Chan
 					as well as AC Votes where a decision is made based on counting ballots
 					to Members in Good Standing.
 					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a> and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>) 
-       <li> Clarify how the outcome of certain ballots are determined.
-					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>) 
-       <li> Stop citing the superseded TAG charter.
-					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>) 
-       <li> Shift most of the non-normative discussion about Workshops to <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>,
-					and reorganize the remaining normative requirements.
-					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>) 
        <li> The section on Member Submissions was significantly shortened and simplified,
 					reducing the complexity under formal Process authority,
 					and shifting much of the material to /Guide,
 					under Team authority.
 					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a> and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>) 
+       <li> Clarify how the outcome of certain ballots are determined.
+					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>) 
+       <li> Stop citing the superseded TAG charter.
+					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>) 
        <li> Clarify amount of leeway around incomplete nominations to TAG or AB elections.
 					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>) 
-       <li> Simplify provisions regarding substitute representatives and proxies.
-					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>) 
+       <li> Shift most of the non-normative discussion about Workshops to <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>,
+					and reorganize the remaining normative requirements.
+					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>) 
        <li> The URL of this document was changed
 					from /Consortium/Process/ to /policies/process/
 					for better integration in the W3C website architecture. 

From 73bea72c87369a02dd2fc594a78ccf33d331aeb8 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 12:35:19 +0900
Subject: [PATCH 209/237] Tweak changelog

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs               | 10 +++++-----
 snapshots/2025-05.html | 14 +++++++-------
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/index.bs b/index.bs
index d7d1cffd..0bbc204e 100644
--- a/index.bs
+++ b/index.bs
@@ -5605,7 +5605,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 	In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:
 
 	<dl>
-		<dt>Changes to technical reports and their publication
+		<dt id=changes-2025-tr>Changes to technical reports and their publication
 		<dd>
 			<ul>
 				<li>
@@ -5613,10 +5613,10 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					Retire the Proposed Recommendation phase of the Recommendation track.
 					It was only used as a short-lived transition
 					during which various verifications and votes about CR were done.
+					</strong>
 					These can be done on a CR
 					without having to republish it as a separate thing.
 					This simplifies the Process without changing the actual quality or consensus expectations.
-					</strong>
 					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)
 
 				<li id="streamlined-update">
@@ -5669,7 +5669,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
 			</ul>
 
-		<dt>Changes to chartering
+		<dt id=changes-2025-charter>Changes to chartering
 		<dd>
 			<ul>
 				<li>
@@ -5692,7 +5692,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>)
 			</ul>
 
-		<dt>Changes to formal decision making and escalation
+		<dt id=changes-2025-decisions>Changes to formal decision making and escalation
 		<dd>
 			<ul>
 				<li>
@@ -5749,7 +5749,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
 			</ul>
 
-		<dt>Other changes
+		<dt id=changes-other>Other changes
 		<dd>
 			<ul>
 				<li>
diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
index 5e3a57d4..bcb27fd5 100644
--- a/snapshots/2025-05.html
+++ b/snapshots/2025-05.html
@@ -4954,15 +4954,15 @@ <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Chan
 	a <a href="https://github.com/w3c/process/compare/p2023_1...2025-review-draft">detailed log of all changes since then</a> are available. </p>
     <p>In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:</p>
     <dl>
-     <dt>Changes to technical reports and their publication 
+     <dt id="changes-2025-tr"><a class="self-link" href="#changes-2025-tr"></a>Changes to technical reports and their publication 
      <dd>
       <ul>
        <li> <strong> Retire the Proposed Recommendation phase of the Recommendation track.
 					It was only used as a short-lived transition
-					during which various verifications and votes about CR were done.
-					These can be done on a CR
+					during which various verifications and votes about CR were done. </strong> These can be done on a CR
 					without having to republish it as a separate thing.
-					This simplifies the Process without changing the actual quality or consensus expectations. </strong> (See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 
+					This simplifies the Process without changing the actual quality or consensus expectations.
+					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 
        <li id="streamlined-update"><a class="self-link" href="#streamlined-update"></a> Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
 					This was meant to enable REC track publication with fewer/faster approval steps
 					when some stricter than usual criteria were fulfilled.
@@ -4993,7 +4993,7 @@ <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Chan
 					that no longer have a Group chartered to maintain them.
 					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>) 
       </ul>
-     <dt>Changes to chartering 
+     <dt id="changes-2025-charter"><a class="self-link" href="#changes-2025-charter"></a>Changes to chartering 
      <dd>
       <ul>
        <li> <strong> Introduce a formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①②">Charter Refinement</a> phase prior to the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑥">AC Review</a>. </strong> (See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>) 
@@ -5005,7 +5005,7 @@ <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Chan
 					This change, while moderate in size, is purely editorial.
 					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>) 
       </ul>
-     <dt>Changes to formal decision making and escalation 
+     <dt id="changes-2025-decisions"><a class="self-link" href="#changes-2025-decisions"></a>Changes to formal decision making and escalation 
      <dd>
       <ul>
        <li> Adjust the rules guiding initiation of Councils,
@@ -5040,7 +5040,7 @@ <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Chan
        <li> Simplify provisions regarding substitute representatives and proxies.
 					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>) 
       </ul>
-     <dt>Other changes 
+     <dt id="changes-other"><a class="self-link" href="#changes-other"></a>Other changes 
      <dd>
       <ul>
        <li> Reuse the bylaws’ notion of Good Standing,

From 8b35a3143c8d55b9c5cc2c6fc11a0beb8c01fbb6 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 12:36:28 +0900
Subject: [PATCH 210/237] Update Acknowledgements

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs               | 55 ++++++++++++++++++++++++------------------
 snapshots/2025-05.html | 55 ++++++++++++++++++++++++------------------
 2 files changed, 62 insertions(+), 48 deletions(-)

diff --git a/index.bs b/index.bs
index 0bbc204e..4a5994dc 100644
--- a/index.bs
+++ b/index.bs
@@ -5444,33 +5444,34 @@ Appendix B: Acknowledgments</h2>
 	The editors are grateful to the following people,
 	who as interested individuals and/or with the affiliation(s) listed,
 	have contributed to this proposal for a revised Process:
-	Brian Kardell,
-	Carine Bournez (W3C),
-	Charles McCathie Nevile (ConsenSys),
+	Adam Basha,
+	Anna Weinberg (Apple)
+	Charles McCathie Nevile,
+	Chris Lilley (W3C),
 	Chris Needham (BBC),
 	Chris Wilson (Google),
-	David Singer (Apple),
-	Delfí Ramírez,
-	Dominique Hazaël-Massieux (W3C),
-	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
-	Fuqiao Xue (W3C),
-	Jeff Jaffe (W3C),
+	Coralie Mercier (W3C),
+	David W. Singer (Apple),
+	Denis Ah-Kang (W3C),
+	Dominique Hazael-Massieux (W3C),
+	Ian Jacobs (W3C),
 	Jeffrey Yasskin (Google),
-	Kevin Fleming (Bloomberg),
-	Léonie Watson (The Paciello Group),
-	Mark Nottingham (Cloudflare),
-	Michael Champion (Microsoft),
+	Jill Schmidt (Apple),
+	Marcos Cáceres (Apple),
+	Mark Nottingham,
+	Martin Thomson (Mozilla),
+	Michael Champion,
+	Michael Sirtori (Intel),
+	Mike Smith (W3C),
+	Nick Doty (Center for Democracy and Technology),
 	Nigel Megitt (BBC),
 	Philippe Le Hégaret (W3C),
-	Ralph Swick (W3C),
-	Samuel Weiler (W3C),
-	Sandro Hawke (W3C),
-	Shawn Lawton Henry,
+	Sam Sneddon (Apple),
+	Shawn Lawton Henry (W3C),
 	Tantek Çelik (Mozilla),
 	Ted Thibodeau Jr (OpenLink Software),
-	Virginia Fournier (Apple),
-	Wendy Seltzer (W3C),
-	Yves Lafon (W3C).
+	Theresa O'Connor (Apple),
+	Vivien Lacourba (W3C).
 
 	The editors are sorry for forgetting any names,
 	and grateful to those who have listened patiently to conversations about this document
@@ -5486,10 +5487,12 @@ Appendix B: Acknowledgments</h2>
 	Bede McCall (MITRE),
 	Ben Wilson,
 	Brad Hill (Facebook),
-	Brian Kardell (JQuery),
+	Brian Kardell (JQuery, Igalia),
 	Carine Bournez (W3C),
 	Carl Cargill (Netscape, Sun Microsystems, Adobe),
+	Charles McCathie Nevile (ConsenSys),
 	Chris Lilley (W3C),
+	Chris Needham (BBC),
 	Chris Wilson (Google),
 	Claus von Riegen (SAP AG),
 	Coralie Mercier (W3C),
@@ -5500,7 +5503,7 @@ Appendix B: Acknowledgments</h2>
 	Daniel Glazman (Disruptive Innovations),
 	David Baron (Mozilla),
 	David Fallside (IBM),
-	David Singer (Apple),
+	David W. Singer (Apple),
 	David Singer (IBM),
 	Delfí Ramírez,
 	Dominique Hazaël-Massieux (W3C),
@@ -5514,9 +5517,9 @@ Appendix B: Acknowledgments</h2>
 	Giri Mandyam (Qualcomm),
 	Gregg Kellogg,
 	Hadley Beeman,
+	Håkon Wium Lie (Opera Software),
 	Helene Workman (Apple),
 	Henri Sivonen (Mozilla),
-	Håkon Wium Lie (Opera Software),
 	Ian Hickson (Google),
 	Ian Jacobs (W3C),
 	Ivan Herman (W3C),
@@ -5525,6 +5528,7 @@ Appendix B: Acknowledgments</h2>
 	Jean-Charles Verdié (MStar),
 	Jean-François Abramatic (IBM, ILOG, W3C),
 	Jeff Jaffe (W3C),
+	Jeffrey Yasskin (Google),
 	Jim Bell (HP),
 	Jim Miller (W3C),
 	Joe Hall (CDT),
@@ -5539,8 +5543,8 @@ Appendix B: Acknowledgments</h2>
 	Klaus Birkenbihl (Fraunhofer Gesellschaft),
 	Larry Masinter (Adobe Systems),
 	Lauren Wood (unaffiliated),
-	Liam Quin (W3C),
 	Léonie Watson (The Paciello Group),
+	Liam Quin (W3C),
 	Marcos Cáceres (Mozilla),
 	Maria Courtemanche (IBM),
 	Mark Crawford (SAP),
@@ -5567,14 +5571,17 @@ Appendix B: Acknowledgments</h2>
 	Sally Khudairi (W3C),
 	Sam Ruby (IBM),
 	Sam Sneddon,
+	Samuel Weiler (W3C),
 	Sandro Hawke (W3C),
 	Sangwhan Moon (Odd Concepts),
 	Scott Peterson (Google),
+	Shawn Lawton Henry,
 	Steve Holbrook (IBM),
 	Steve Zilles (Adobe Systems)
 	Steven Pemberton (CWI),
 	TV Raman (Google),
 	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
 	Terence Eden (Her Majesty's Government),
 	Thomas Reardon (Microsoft),
 	Tim Berners-Lee (W3C),
diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
index bcb27fd5..a242c316 100644
--- a/snapshots/2025-05.html
+++ b/snapshots/2025-05.html
@@ -4804,33 +4804,34 @@ <h2 class="non-normative nonum heading settled" id="acks"><span class="content">
     <p>The editors are grateful to the following people,
 	who as interested individuals and/or with the affiliation(s) listed,
 	have contributed to this proposal for a revised Process:
-	Brian Kardell,
-	Carine Bournez (W3C),
-	Charles McCathie Nevile (ConsenSys),
+	Adam Basha,
+	Anna Weinberg (Apple)
+	Charles McCathie Nevile,
+	Chris Lilley (W3C),
 	Chris Needham (BBC),
 	Chris Wilson (Google),
-	David Singer (Apple),
-	Delfí Ramírez,
-	Dominique Hazaël-Massieux (W3C),
-	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
-	Fuqiao Xue (W3C),
-	Jeff Jaffe (W3C),
+	Coralie Mercier (W3C),
+	David W. Singer (Apple),
+	Denis Ah-Kang (W3C),
+	Dominique Hazael-Massieux (W3C),
+	Ian Jacobs (W3C),
 	Jeffrey Yasskin (Google),
-	Kevin Fleming (Bloomberg),
-	Léonie Watson (The Paciello Group),
-	Mark Nottingham (Cloudflare),
-	Michael Champion (Microsoft),
+	Jill Schmidt (Apple),
+	Marcos Cáceres (Apple),
+	Mark Nottingham,
+	Martin Thomson (Mozilla),
+	Michael Champion,
+	Michael Sirtori (Intel),
+	Mike Smith (W3C),
+	Nick Doty (Center for Democracy and Technology),
 	Nigel Megitt (BBC),
 	Philippe Le Hégaret (W3C),
-	Ralph Swick (W3C),
-	Samuel Weiler (W3C),
-	Sandro Hawke (W3C),
-	Shawn Lawton Henry,
+	Sam Sneddon (Apple),
+	Shawn Lawton Henry (W3C),
 	Tantek Çelik (Mozilla),
 	Ted Thibodeau Jr (OpenLink Software),
-	Virginia Fournier (Apple),
-	Wendy Seltzer (W3C),
-	Yves Lafon (W3C).</p>
+	Theresa O’Connor (Apple),
+	Vivien Lacourba (W3C).</p>
     <p>The editors are sorry for forgetting any names,
 	and grateful to those who have listened patiently to conversations about this document
 	without feeling a need to add more.</p>
@@ -4844,10 +4845,12 @@ <h2 class="non-normative nonum heading settled" id="acks"><span class="content">
 	Bede McCall (MITRE),
 	Ben Wilson,
 	Brad Hill (Facebook),
-	Brian Kardell (JQuery),
+	Brian Kardell (JQuery, Igalia),
 	Carine Bournez (W3C),
 	Carl Cargill (Netscape, Sun Microsystems, Adobe),
+	Charles McCathie Nevile (ConsenSys),
 	Chris Lilley (W3C),
+	Chris Needham (BBC),
 	Chris Wilson (Google),
 	Claus von Riegen (SAP AG),
 	Coralie Mercier (W3C),
@@ -4858,7 +4861,7 @@ <h2 class="non-normative nonum heading settled" id="acks"><span class="content">
 	Daniel Glazman (Disruptive Innovations),
 	David Baron (Mozilla),
 	David Fallside (IBM),
-	David Singer (Apple),
+	David W. Singer (Apple),
 	David Singer (IBM),
 	Delfí Ramírez,
 	Dominique Hazaël-Massieux (W3C),
@@ -4872,9 +4875,9 @@ <h2 class="non-normative nonum heading settled" id="acks"><span class="content">
 	Giri Mandyam (Qualcomm),
 	Gregg Kellogg,
 	Hadley Beeman,
+	Håkon Wium Lie (Opera Software),
 	Helene Workman (Apple),
 	Henri Sivonen (Mozilla),
-	Håkon Wium Lie (Opera Software),
 	Ian Hickson (Google),
 	Ian Jacobs (W3C),
 	Ivan Herman (W3C),
@@ -4883,6 +4886,7 @@ <h2 class="non-normative nonum heading settled" id="acks"><span class="content">
 	Jean-Charles Verdié (MStar),
 	Jean-François Abramatic (IBM, ILOG, W3C),
 	Jeff Jaffe (W3C),
+	Jeffrey Yasskin (Google),
 	Jim Bell (HP),
 	Jim Miller (W3C),
 	Joe Hall (CDT),
@@ -4897,8 +4901,8 @@ <h2 class="non-normative nonum heading settled" id="acks"><span class="content">
 	Klaus Birkenbihl (Fraunhofer Gesellschaft),
 	Larry Masinter (Adobe Systems),
 	Lauren Wood (unaffiliated),
-	Liam Quin (W3C),
 	Léonie Watson (The Paciello Group),
+	Liam Quin (W3C),
 	Marcos Cáceres (Mozilla),
 	Maria Courtemanche (IBM),
 	Mark Crawford (SAP),
@@ -4925,14 +4929,17 @@ <h2 class="non-normative nonum heading settled" id="acks"><span class="content">
 	Sally Khudairi (W3C),
 	Sam Ruby (IBM),
 	Sam Sneddon,
+	Samuel Weiler (W3C),
 	Sandro Hawke (W3C),
 	Sangwhan Moon (Odd Concepts),
 	Scott Peterson (Google),
+	Shawn Lawton Henry,
 	Steve Holbrook (IBM),
 	Steve Zilles (Adobe Systems)
 	Steven Pemberton (CWI),
 	TV Raman (Google),
 	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
 	Terence Eden (Her Majesty’s Government),
 	Thomas Reardon (Microsoft),
 	Tim Berners-Lee (W3C),

From f5cb3b23070eab943ca1770f66df87755ab0ba4c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 12:52:34 +0900
Subject: [PATCH 211/237] Fix section id

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs               | 2 +-
 snapshots/2025-05.html | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index 4a5994dc..f35046cd 100644
--- a/index.bs
+++ b/index.bs
@@ -5599,7 +5599,7 @@ Appendix C: Changes</h2>
 
 	<em>This section is non-normative.</em>
 
-<h3 id=changes-2024 class=no-num>
+<h3 id=changes-2025 class=no-num>
 Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></h3>
 
 	<p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
index a242c316..2eded394 100644
--- a/snapshots/2025-05.html
+++ b/snapshots/2025-05.html
@@ -925,7 +925,7 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
     <li>
      <a href="#changes"><span class="secno"></span> <span class="content"> Appendix C: Changes</span></a>
      <ol class="toc">
-      <li><a href="#changes-2024"><span class="secno"></span> <span class="content"> Changes since the <span>3 November 2023 Process</span></span></a>
+      <li><a href="#changes-2025"><span class="secno"></span> <span class="content"> Changes since the <span>3 November 2023 Process</span></span></a>
       <li><a href="#changes-previous"><span class="secno"></span> <span class="content"> Changes since earlier versions</span></a>
      </ol>
     <li>
@@ -4953,7 +4953,7 @@ <h2 class="non-normative nonum heading settled" id="acks"><span class="content">
 	Yves Lafon (W3C).</p>
     <h2 class="non-normative nonum heading settled" id="changes"><span class="content"> Appendix C: Changes</span><a class="self-link" href="#changes"></a></h2>
     <p><em>This section is non-normative.</em></p>
-    <h3 class="no-num heading settled" id="changes-2024"><span class="content"> Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></span><a class="self-link" href="#changes-2024"></a></h3>
+    <h3 class="no-num heading settled" id="changes-2025"><span class="content"> Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></span><a class="self-link" href="#changes-2025"></a></h3>
     <p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
 	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
 	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2Fsnapshots%2F2025-05">diff from Process 2023 to this latest version</a>,

From 430df75827b25a76ce91cbdd2f3851810781c6d8 Mon Sep 17 00:00:00 2001
From: Jeffrey Yasskin <jyasskin@google.com>
Date: Tue, 3 Jun 2025 06:33:04 -0700
Subject: [PATCH 212/237] Remove a stray emdash.

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index f35046cd..94a78860 100644
--- a/index.bs
+++ b/index.bs
@@ -5318,7 +5318,7 @@ Member Submissions</h2>
 Process Evolution</h2>
 
 	Revision of the W3C Process and related documents (see below) undergoes similar [=consensus=]-building processes as for [=technical reports=],
-	with the [=Advisory Board=]--
+	with the [=Advisory Board=]
 	acting as the sponsoring [=Working Group=].
 	The documents may be developed by the [=AB=] or by another group to whom the [=AB=] has delegated development.
 	Review includes

From 4cbc515d645708a9e279c2a33497c6dd8d14062f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Mon, 19 May 2025 12:59:03 +0900
Subject: [PATCH 213/237] Add comment to help with maintenance

---
 index.bs | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/index.bs b/index.bs
index 94a78860..0b981110 100644
--- a/index.bs
+++ b/index.bs
@@ -5473,6 +5473,15 @@ Appendix B: Acknowledgments</h2>
 	Theresa O'Connor (Apple),
 	Vivien Lacourba (W3C).
 
+	<!--
+		* After publication merge the list above in the one below,
+		  and start it anew
+		* the following command can be helpful to find contributors since a particular version
+		(in this example, starting from the p2023_1 tag):
+
+		git log  p2023_1.. | grep -i author | sed "s/^[^:]*: //" | sed "s/ <.*>//" | sort -u
+	-->
+
 	The editors are sorry for forgetting any names,
 	and grateful to those who have listened patiently to conversations about this document
 	without feeling a need to add more.

From 3e23937f568bce8dca713bd3b936cf887c071cfc Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 10 Jun 2025 13:23:53 +0900
Subject: [PATCH 214/237] Drop legacy aliases for Group Note from the
 definition

These names were only provided as a bikeshed convenience, but it is
unlikely that it is being used, and defining them gives them exposure in
the "terms defined by this specification" index. Giving exposure to
legacy terms is unnecessary and confusing, so removing.

Addresses #1064

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs               | 4 ++--
 snapshots/2025-05.html | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/index.bs b/index.bs
index 0b981110..1a5850d3 100644
--- a/index.bs
+++ b/index.bs
@@ -4553,7 +4553,7 @@ The Note Track (Notes and Statements)</h3>
 <h4 id="Note">
 Group Notes</h4>
 
-	A <dfn export id="WGNote" lt="Group Note | Note | W3C Note | Working Group Note | Interest Group Note | AB Note | TAG Note">Group Note</dfn> (<abbr>NOTE</abbr>)
+	A <dfn export id="WGNote" lt="Group Note | Note">Group Note</dfn> (<abbr>NOTE</abbr>)
 	is published
 	to provide a stable reference for a useful document
 	that is not intended to be a formal standard.
@@ -5627,9 +5627,9 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 				<li>
 					<strong>
 					Retire the Proposed Recommendation phase of the Recommendation track.
+					</strong>
 					It was only used as a short-lived transition
 					during which various verifications and votes about CR were done.
-					</strong>
 					These can be done on a CR
 					without having to republish it as a separate thing.
 					This simplifies the Process without changing the actual quality or consensus expectations.
diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
index 2eded394..1773a6c5 100644
--- a/snapshots/2025-05.html
+++ b/snapshots/2025-05.html
@@ -4964,9 +4964,9 @@ <h3 class="no-num heading settled" id="changes-2025"><span class="content"> Chan
      <dt id="changes-2025-tr"><a class="self-link" href="#changes-2025-tr"></a>Changes to technical reports and their publication 
      <dd>
       <ul>
-       <li> <strong> Retire the Proposed Recommendation phase of the Recommendation track.
-					It was only used as a short-lived transition
-					during which various verifications and votes about CR were done. </strong> These can be done on a CR
+       <li> <strong> Retire the Proposed Recommendation phase of the Recommendation track. </strong> It was only used as a short-lived transition
+					during which various verifications and votes about CR were done.
+					These can be done on a CR
 					without having to republish it as a separate thing.
 					This simplifies the Process without changing the actual quality or consensus expectations.
 					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 

From 7405e1ae3783dc4cbbba8f4c9f9b7658c6661d81 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 10 Jun 2025 13:50:56 +0900
Subject: [PATCH 215/237] Rename "Team Conact" into "Staff Contact"

See issue #1066

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 45 +++++++++++++++++++++++----------------------
 1 file changed, 23 insertions(+), 22 deletions(-)

diff --git a/index.bs b/index.bs
index 1a5850d3..ff18ec94 100644
--- a/index.bs
+++ b/index.bs
@@ -916,9 +916,9 @@ Composition of the Advisory Board</h5>
 	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 <a href="https://www.w3.org/guide/teamcontact/role">Team Contact</a>,
+	The team also appoints a [=Staff Contact=],
 	as described in <a href="#ReqsAllGroups"></a>.
-	The CEO and Team Contact have a standing invitation
+	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=]
@@ -1033,7 +1033,7 @@ Composition of the Technical Architecture Group</h5>
 	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 <a href="https://www.w3.org/guide/teamcontact/role">Team Contact</a> [[TEAM-CONTACT]] for the TAG,
+	The [=Team=] also appoints a <a href="https://www.w3.org/guide/teamcontact/role">Staff Contact</a> [[TEAM-CONTACT]] for the TAG,
 	as described in <a href="#ReqsAllGroups"></a>.
 
 	The terms of TAG participants last for <span class="time-interval">two years</span>.
@@ -1438,22 +1438,23 @@ Requirements for All Chartered Groups</h4>
 	Note: The <a href="https://www.w3.org/guide/chair/role">role of the Chair</a> [[CHAIR]] is described
 	in the <a href="https://www.w3.org/guide/">Art of Consensus</a> [[GUIDE]].
 
-	Each group <em class="rfc2119">must</em> have a <dfn id="TeamContact" export>Team Contact</dfn>,
+	Each group <em class="rfc2119">must</em> have a <dfn id="TeamContact" export>Staff Contact</dfn>
+	(also known as <dfn export>Team Contact</dfn>),
 	who acts as the interface between the [=Chair=],
 	group participants,
 	and the rest of the Team.
 	
-	Note: The <a href="https://www.w3.org/guide/teamcontact/role">role of the Team Contact</a> [[TEAM-CONTACT]] 
+	Note: The <a href="https://www.w3.org/guide/teamcontact/role">role of the Staff Contact</a> [[TEAM-CONTACT]]
 	is described in the <a href="https://www.w3.org/guide/">Art of Consensus</a> [[GUIDE]].
 				
-	The [=Chair=] and the [=Team Contact=] of a group <em class="rfc2119">should not</em> be the same individual.
+	The [=Chair=] and the [=Staff Contact=] of a group <em class="rfc2119">should not</em> be the same individual.
 
 	Each group <em class="rfc2119">must</em> have an archived mailing list
 	for formal group communication
 	(e.g., for meeting announcements and [=minutes=],
 	documentation of decisions,
 	and [=Formal Objections=] to decisions).
-	It is the responsibility of the [=Chair=] and [=Team Contact=]
+	It is the responsibility of the [=Chair=] and [=Staff Contact=]
 	to ensure that new participants are subscribed to all relevant mailing lists.
 	Refer to the list of <a href="https://www.w3.org/groups/">group mailing lists</a> [[GROUP-MAIL]].
 
@@ -1474,7 +1475,7 @@ Participation in Chartered Groups</h4>
 	<a href="#member-rep">Member representatives</a>,
 	<a href="#invited-expert-wg">Invited Experts</a>,
 	and <a href="#Team">Team representatives</a>
-	(including the <a href="#TeamContact">Team Contact</a>).
+	(including the [=Staff Contact=]).
 
 	There are four types of individual <dfn id="igparticipant">participants in an Interest Group</dfn>:
 	the same three types as for Working Groups plus,
@@ -1537,7 +1538,7 @@ Member Representative in a Working Group</h5>
 	</ul>
 
 	To designate an individual as a Member representative in a [=Working Group=],
-	an [=Advisory Committee representative=] <em class="rfc2119">must</em> provide the [=Chair=] and [=Team Contact=]
+	an [=Advisory Committee representative=] <em class="rfc2119">must</em> provide the [=Chair=] and [=Staff Contact=]
 	with all of the following <span id=member-rep-info>information</span>,
 	in addition to any other information required by the <a href="#cfp">Call for Participation</a>
 	and charter
@@ -1607,17 +1608,17 @@ Invited Expert in a Working Group</h5>
 			the Chair has designated the individual as a group participant,
 
 		<li>
-			the Team Contact has agreed with the Chair's choice, and
+			the Staff Contact has agreed with the Chair's choice, and
 
 		<li>
 			the individual has provided the <a href="#inv-expert-info">information required of an Invited Expert</a>
-			to the Chair and Team Contact.
+			to the Chair and Staff Contact.
 	</ul>
 
 	To designate an individual as an Invited Expert in a Working Group,
-	the [=Chair=] <em class="rfc2119">must</em> inform the Team Contact
+	the [=Chair=] <em class="rfc2119">must</em> inform the Staff Contact
 	and provide rationale for the choice.
-	When the [=Chair=] and the [=Team Contact=] disagree about a designation,
+	When the [=Chair=] and the [=Staff Contact=] disagree about a designation,
 	the [=CEO=] determines
 	whether the individual will be invited to participate in the Working Group.
 
@@ -2036,9 +2037,9 @@ Minor Changes to Active Charters</h4>
 	The following are examples of [=minor changes=]:
 	the renaming or restructuring (e.g. splitting or combining) of existing in-scope deliverables,
 	the addition of new [[#note-track|Note track]] deliverables that help explain the group’s work
-	a change of [=Team Contact=],
+	a change of [=Staff Contact=],
 	or a change of [=Chair=].
-	[=Minor changes=], other than a change of [=Team Contact=],
+	[=Minor changes=], other than a change of [=Staff Contact=],
 	<em class=rfc2119>should</em> have the [=consensus=] of the group.
 
 	The [=Team=] <em class=rfc2119>may</em> nevertheless choose
@@ -2065,7 +2066,7 @@ Call for Participation in a Chartered Group</h3>
 	For a new group, this announcement officially creates the group.
 	The announcement <em class="rfc2119">must</em> include a reference to the <a href="#WGCharter">charter</a>,
 	the name(s) of the group's [=Chair(s)=],
-	and the name(s) of the [=Team Contact(s)=].
+	and the name(s) of the [=Staff Contact(s)=].
 
 	After a Call for Participation,
 	any <a href="#member-rep">Member representatives</a>
@@ -2098,7 +2099,7 @@ Charter Extension</h3>
 	and the Group homepage
 	(which includes at least
 	the name(s) of the group's [=Chair(s)=],
-	the name of the [=Team Contact=],
+	the name of the [=Staff Contact=],
 	and instructions for joining the group).
 
 	After a charter extension,
@@ -2412,8 +2413,8 @@ Registering Formal Objections</h3>
 	(except those having a different appeal process)
 	by registering a <dfn id="FormalObjection">Formal Objection</dfn> with the [=Team=].
 	Group participants <em class="rfc2119">should</em> inform
-	their <a href="#TeamContact">Team Contact</a> as well as the group's Chair(s).
-	The Team Contact <em class="rfc2119">must</em> inform the [=CEO=]
+	their [=Staff Contact=] as well as the group's Chair(s).
+	The Staff Contact <em class="rfc2119">must</em> inform the [=CEO=]
 	when a group participant has also raised concerns about due process.
 
 	Note: In this document, the term [=Formal Objection=] is used to emphasize this process implication:
@@ -2519,7 +2520,7 @@ Council Composition</h5>
 	once it is fixed.
 
 	A [=Team=] member is assigned
-	to act as the <dfn export>Council Team Contact</dfn>,
+	to act as the <dfn export oldids="council-team-contact">Council Staff Contact</dfn>,
 	to support this Council
 	and to facilitate adherence to this Process.
 
@@ -2639,7 +2640,7 @@ Council Chairing</h5>
 	The chair must be a member of that [=W3C Council=].
 	Chair selection happens during formation of each Council,
 	and <em class=rfc2119>must</em> be re-run
-	if requested by the [=Council Team Contact=] or by the [=Chair=]
+	if requested by the [=Council Staff Contact=] or by the [=Chair=]
 	during the Council’s operation.
 
 <h5 id=council-convention>
@@ -2721,7 +2722,7 @@ Council Deliberations</h5>
 	explaining the reason for their disagreement.
 
 	The deliberations of a [=W3C Council=] are confidential to that [=W3C Council=]
-	and its [=Council Team Contact=].
+	and its [=Council Staff Contact=].
 
 	<p id=45-day-update>
 	If a [=W3C Council=] is unable to come to a conclusion within 45 days of being [=convened=],

From fa781ed72d31f04943d0fda51f1a4267ecb27a9f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 13 May 2025 12:16:48 +0900
Subject: [PATCH 216/237] Clarify timing of Council being convened

It is already implied that the Council is only convened after dismissal
and renunciation because the chair is picked by members of the council,
not potential members, but this is not super clear from this paragraph
so make it obvious.

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index ff18ec94..bc65b8d8 100644
--- a/index.bs
+++ b/index.bs
@@ -2646,8 +2646,9 @@ Council Chairing</h5>
 <h5 id=council-convention>
 Convening the Council</h5>
 
-	Upon appointment of the [=W3C Council Chair=]
-	and delivery of the [=Team=]’s report,
+	Once [=dismissal=], [=renunciation=], and
+	appointment of the [=W3C Council Chair=] have concluded,
+	and the [=Team=]’s report has been delivered,
 	the [=W3C Council=] is considered to be <dfn>convened</dfn>
 	and can start [[#council-deliberations|deliberations]].
 

From d9baeaad8876c7822383488ad3fedd6c4a822a87 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 13 May 2025 19:35:55 +0900
Subject: [PATCH 217/237] improve phrasing

Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index bc65b8d8..bb5d6b1d 100644
--- a/index.bs
+++ b/index.bs
@@ -2646,7 +2646,7 @@ Council Chairing</h5>
 <h5 id=council-convention>
 Convening the Council</h5>
 
-	Once [=dismissal=], [=renunciation=], and
+	When [=dismissal=], [=renunciation=], and
 	appointment of the [=W3C Council Chair=] have concluded,
 	and the [=Team=]’s report has been delivered,
 	the [=W3C Council=] is considered to be <dfn>convened</dfn>

From 2f8ed5ba04491c0ab28d32c0b63b2d64a2779cb5 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 13 May 2025 12:07:29 +0900
Subject: [PATCH 218/237] Clarify council text in case of multiple objections
 to a single decision

Even though the logic already was that the Council processes all
objections to a single decision together, parts of the original text
were written as if there was only a single objection, and were awkward
or in case of several.

This rephrasing makes the text coherent.

See #1041

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/index.bs b/index.bs
index bb5d6b1d..7bf251d7 100644
--- a/index.bs
+++ b/index.bs
@@ -2672,17 +2672,17 @@ Council Deliberations</h5>
 	<p id=broker-consensus>
 	The Council <em class=rfc2119>may</em>
 	further attempt to broker consensus,
-	which, if successful, disposes the formal objection.
+	which, if successful, disposes that formal objection.
 
 	Otherwise,
 	after sufficient deliberation,
 	the [=W3C Council=] decides whether to
-	<dfn lt="uphold | upholds | upheld | upholding">uphold</dfn> or <dfn>overrule</dfn> the objection.
-	The [=W3C Council=] <em class=rfc2119>may</em> [=overrule=] the [=Formal Objection=]
-	even if it agrees with some of the supportive arguments.
+	<dfn>confirm</dfn> or <dfn>overturn</dfn> the decision being objected to.
+	The [=W3C Council=] <em class=rfc2119>may</em> [=confirm=] the decision
+	even if it agrees with some of the arguments of a [=Formal Objection=].
 
 	<p id=fo-mitigations>
-	When [=upholding=] an objection,
+	When [=overturning=] an decision,
 	it <em class=rfc2199>should</em> recommend a way forward.
 	If the overturned decision has already had consequences
 	(e.g., if the objection concerns material already in a published document)
@@ -2718,7 +2718,7 @@ Council Deliberations</h5>
 	not two.
 
 	In the case of non-unanimous decisions,
-	members of a [=W3C Council=] who disagree with the decision
+	members of a [=W3C Council=] who disagree with the Council's decision
 	<em class=rfc2119>may</em> write a <dfn>Minority Opinion</dfn>
 	explaining the reason for their disagreement.
 
@@ -2736,14 +2736,14 @@ Council Decision Report</h5>
 
 	A [=Council=] terminates by issuing a <dfn export>Council Report</dfn>,
 	which:
-	* <em class=rfc2119>must</em> state whether the Council [=upholds=] or [=overrules=] the objection(s).
-	* <em class=rfc2119>must</em> provide a rationale supporting the decision,
+	* <em class=rfc2119>must</em> state whether the Council [=confirms=] or [=overturns=] the decision being objected to.
+	* <em class=rfc2119>must</em> provide a rationale supporting its conclusion,
 		which <em class=rfc2119>should</em> address each argument raised in the Formal Objection(s).
 	* <em class=rfc2119>must</em> include any recommendation decided by the [=Council=].
-	* if the [=Formal Objection=] has been upheld, <em class=rfc2119>should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.
+	* if the decision has been overturned, <em class=rfc2119>should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.
 	* <em class=rfc2119>must</em> include the [=Minority Opinion(s)=], if any.
 	* <em class=rfc2119>must</em> report the names of those who were [=dismissed=] or [=renounced=] their seat as well as those who were qualified to serve.
-	* <em class=rfc2119>must</em> report the names of the individuals who participated in the final decision.
+	* <em class=rfc2119>must</em> report the names of the individuals who participated in the final Council decision.
 	* <em class=rfc2119>must</em> report the number of votes for/against dismissing each participant.
 	* <em class=rfc2119>may</em> report vote totals for the Council’s decision, if a formal vote was held.
 	* <em class=rfc2119>must not</em> attribute any position to any individual on the Council.

From 648bcf3df441635d91ceeafd66a5f22317c7449b Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 14 May 2025 16:48:07 +0900
Subject: [PATCH 219/237] Fix typo

Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 7bf251d7..25e4d13e 100644
--- a/index.bs
+++ b/index.bs
@@ -2682,7 +2682,7 @@ Council Deliberations</h5>
 	even if it agrees with some of the arguments of a [=Formal Objection=].
 
 	<p id=fo-mitigations>
-	When [=overturning=] an decision,
+	When [=overturning=] a decision,
 	it <em class=rfc2199>should</em> recommend a way forward.
 	If the overturned decision has already had consequences
 	(e.g., if the objection concerns material already in a published document)

From 46ced6ca53f7c5f0ff38e72f53eaf08730e381f0 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 14 May 2025 16:49:53 +0900
Subject: [PATCH 220/237] Phrasing improvement

Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
---
 index.bs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 25e4d13e..583f3020 100644
--- a/index.bs
+++ b/index.bs
@@ -2671,8 +2671,8 @@ Council Deliberations</h5>
 
 	<p id=broker-consensus>
 	The Council <em class=rfc2119>may</em>
-	further attempt to broker consensus,
-	which, if successful, disposes that formal objection.
+	further attempt to broker consensus on one or more of the formal objections,
+	which, if successful, would allow them to be resolved.
 
 	Otherwise,
 	after sufficient deliberation,

From 92fc9f913cecdd4b47bff5b4fa71f3c5909996fc Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 10 Jun 2025 13:58:48 +0900
Subject: [PATCH 221/237] clarify phrasing

Co-authored-by: chaals <chaals@users.noreply.github.com>
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 583f3020..d53b8534 100644
--- a/index.bs
+++ b/index.bs
@@ -2679,7 +2679,7 @@ Council Deliberations</h5>
 	the [=W3C Council=] decides whether to
 	<dfn>confirm</dfn> or <dfn>overturn</dfn> the decision being objected to.
 	The [=W3C Council=] <em class=rfc2119>may</em> [=confirm=] the decision
-	even if it agrees with some of the arguments of a [=Formal Objection=].
+	even if it agrees with some of the arguments made as part of a [=Formal Objection=].
 
 	<p id=fo-mitigations>
 	When [=overturning=] a decision,

From 3da7bc6f26f617f2eeec5fe5ff66ac024b7b9839 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 12 Jun 2025 00:07:09 +0900
Subject: [PATCH 222/237] Add emphasis on the need to consider each argument

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/index.bs b/index.bs
index d53b8534..a6960844 100644
--- a/index.bs
+++ b/index.bs
@@ -2676,6 +2676,7 @@ Council Deliberations</h5>
 
 	Otherwise,
 	after sufficient deliberation,
+	and with due consideration of each argument in the applicable [=Formal Objections=],
 	the [=W3C Council=] decides whether to
 	<dfn>confirm</dfn> or <dfn>overturn</dfn> the decision being objected to.
 	The [=W3C Council=] <em class=rfc2119>may</em> [=confirm=] the decision

From 4652c692dc637a3e7696b51ce2458b78634a8317 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 12 Jun 2025 00:09:58 +0900
Subject: [PATCH 223/237] Use "uphold" rather than "confirm" when the Council
 lets a decision stand

---
 index.bs | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index a6960844..26605cc9 100644
--- a/index.bs
+++ b/index.bs
@@ -2678,8 +2678,8 @@ Council Deliberations</h5>
 	after sufficient deliberation,
 	and with due consideration of each argument in the applicable [=Formal Objections=],
 	the [=W3C Council=] decides whether to
-	<dfn>confirm</dfn> or <dfn>overturn</dfn> the decision being objected to.
-	The [=W3C Council=] <em class=rfc2119>may</em> [=confirm=] the decision
+	<dfn>uphold</dfn> or <dfn>overturn</dfn> the decision being objected to.
+	The [=W3C Council=] <em class=rfc2119>may</em> [=uphold=] the decision
 	even if it agrees with some of the arguments made as part of a [=Formal Objection=].
 
 	<p id=fo-mitigations>
@@ -2737,7 +2737,7 @@ Council Decision Report</h5>
 
 	A [=Council=] terminates by issuing a <dfn export>Council Report</dfn>,
 	which:
-	* <em class=rfc2119>must</em> state whether the Council [=confirms=] or [=overturns=] the decision being objected to.
+	* <em class=rfc2119>must</em> state whether the Council [=upholds=] or [=overturns=] the decision being objected to.
 	* <em class=rfc2119>must</em> provide a rationale supporting its conclusion,
 		which <em class=rfc2119>should</em> address each argument raised in the Formal Objection(s).
 	* <em class=rfc2119>must</em> include any recommendation decided by the [=Council=].

From e58ed8866f821f059871ff1fff3b6bbd220b6f09 Mon Sep 17 00:00:00 2001
From: fantasai <fantasai.bugs@inkedblade.net>
Date: Wed, 11 Jun 2025 11:14:58 -0400
Subject: [PATCH 224/237] Explain the reasons for the Council confidentiality
 requirements (#1069)

Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/index.bs b/index.bs
index 26605cc9..b959f7b2 100644
--- a/index.bs
+++ b/index.bs
@@ -2726,6 +2726,12 @@ Council Deliberations</h5>
 	The deliberations of a [=W3C Council=] are confidential to that [=W3C Council=]
 	and its [=Council Staff Contact=].
 
+	Note: This confidentiality requirement is put in place so that
+	the Council can receive sensitive information in confidence
+	and to enable Council members to speak freely in their individual expert capacity
+	without pressure or fear of retaliation
+	by those involved in the dispute, business relations, their employer, etc.
+
 	<p id=45-day-update>
 	If a [=W3C Council=] is unable to come to a conclusion within 45 days of being [=convened=],
 	the [=W3C Council Chair=] <em class=rfc2119>must</em> inform the [=AC=] of this delay

From d46aa222872e5479b779eed30734eefa52353b17 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 18 Jun 2025 23:56:54 +0900
Subject: [PATCH 225/237] Correct council text pertaining to multiple
 objections / decisions (#1072)

This is a follow up to https://github.com/w3c/process/pull/1045

The earlier commits established terminology to discuss Councils in terms
of the decisions they may or may not overturn, and made the Council
section of the Process clearer. However, in the process of doing that,
it broke some of the ways other sections refered to this.

This closes the loop, and makes everything coherent.


Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
Co-authored-by: Nigel Megitt <nigel.megitt@bbc.co.uk>
---
 index.bs | 33 +++++++++++++++++++++------------
 1 file changed, 21 insertions(+), 12 deletions(-)

diff --git a/index.bs b/index.bs
index b959f7b2..e0ecc73d 100644
--- a/index.bs
+++ b/index.bs
@@ -2678,18 +2678,25 @@ Council Deliberations</h5>
 	after sufficient deliberation,
 	and with due consideration of each argument in the applicable [=Formal Objections=],
 	the [=W3C Council=] decides whether to
-	<dfn>uphold</dfn> or <dfn>overturn</dfn> the decision being objected to.
-	The [=W3C Council=] <em class=rfc2119>may</em> [=uphold=] the decision
+	<dfn>affirm</dfn> or <dfn>overturn</dfn> the decision being objected to.
+	The [=W3C Council=] <em class=rfc2119>may</em> [=affirm=] the decision
 	even if it agrees with some of the arguments made as part of a [=Formal Objection=].
+	When a decision is [=affirmed=],
+	all Formal Objections against it are said to be <dfn lt="overrule">overruled</dfn>.
+	Conversely,
+	aspects of Formal Objections that are found by the Council
+	to justify [=overturning=] a decision
+	are said to be <dfn>upheld</dfn>.
 
 	<p id=fo-mitigations>
 	When [=overturning=] a decision,
 	it <em class=rfc2199>should</em> recommend a way forward.
 	If the overturned decision has already had consequences
+	pertaining to [=upheld=] aspects of the Formal Objection(s)
 	(e.g., if the objection concerns material already in a published document)
 	the Council <em class=rfc2119>should</em> suggest how these consequences might be mitigated.
 	The [=Team=] is responsible for making sure that adequate mitigations are enacted in a timely fashion;
-	and the [=Formal Objection=] is not considered <dfn>fully addressed</dfn> until then.
+	and the [=upheld=] aspects of the [=Formal Objection(s)=] (as identified in the [=Council Report=]) are not considered <dfn>fully addressed</dfn> until then.
 
 	Note: This does not create new powers for the [=Team=],
 	such as the ability to “unpublish” documents.
@@ -2743,11 +2750,13 @@ Council Decision Report</h5>
 
 	A [=Council=] terminates by issuing a <dfn export>Council Report</dfn>,
 	which:
-	* <em class=rfc2119>must</em> state whether the Council [=upholds=] or [=overturns=] the decision being objected to.
+	* <em class=rfc2119>must</em> state whether the Council [=affirms=] or [=overturns=] the decision being objected to.
 	* <em class=rfc2119>must</em> provide a rationale supporting its conclusion,
 		which <em class=rfc2119>should</em> address each argument raised in the Formal Objection(s).
 	* <em class=rfc2119>must</em> include any recommendation decided by the [=Council=].
-	* if the decision has been overturned, <em class=rfc2119>should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.
+	* if the decision has been [=overturned=],
+		<em class=rfc2119>must</em> identify which aspects of the Formal Objection(s) are being [=upheld=], and
+		<em class=rfc2119>should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.
 	* <em class=rfc2119>must</em> include the [=Minority Opinion(s)=], if any.
 	* <em class=rfc2119>must</em> report the names of those who were [=dismissed=] or [=renounced=] their seat as well as those who were qualified to serve.
 	* <em class=rfc2119>must</em> report the names of the individuals who participated in the final Council decision.
@@ -2853,7 +2862,7 @@ Determining the W3C Decision</h4>
 	</ul>
 
 	If the proposal has [=consensus=],
-	or if any [=Formal Objections=] are retracted or overruled
+	or if all [=Formal Objections=] are retracted or [=overruled=]
 	and the proposal otherwise has sufficient support to achieve [=consensus=],
 	this [=W3C Decision=] <em class=rfc2119>must</em> be one of:
 
@@ -2881,7 +2890,7 @@ Determining the W3C Decision</h4>
 	only if the revised proposal has [=consensus=]
 	of the subset of the [=AC=] that voted on the initial proposal
 	(including anyone who explicitly abstained),
-	or if any [=Formal Objections=] against the revised proposal are retracted or [=overruled=]
+	or if all [=Formal Objections=] against the revised proposal are retracted or [=overruled=]
 	and the revised proposal otherwise has sufficient support to achieve [=consensus=].
 	For clarity,
 	the [=Team=] <em class=rfc2119>should</em> seek a response from this subset of the [=AC=]
@@ -2893,9 +2902,9 @@ Determining the W3C Decision</h4>
 	is handled by the same [=Council=] responsible for [=Formal Objections=] raised against the initial proposal,
 	if any.
 
-	Note: Such a [=Council=] has the ability to
-	clear either the original or the revised proposal for advancement
-	by [=overruling=] all [=Formal Objections=] against the original or revised proposal,
+	Such a [=Council=] has the ability to [=affirm=]
+	either the original or the revised proposal for advancement,
+	thereby [=overruling=] all [=Formal Objections=] against the original or revised proposal,
 	respectively.
 
 	For publications which have conditions in addition to [=AC=] approval
@@ -3758,7 +3767,7 @@ Advancement on the Recommendation Track</h4>
 			[=Team=] verification (a [=Team decision=])
 			<em class=rfc2119>must</em> be withheld if any Process requirements are not met
 			or if there remain any unresolved Formal Objections
-			(including any [=upheld=] by a [=Council=] but not yet [=fully addressed=]),
+			(including any aspect [=upheld=] by a [=Council=] but not yet [=fully addressed=]),
 			or if the document does not adequately reflect all relevant decisions of the [=W3C Council=] (or its delegates).
 			If the [=Team=] rejects a [=Transition Request=]
 			it <em class=rfc2119>must</em> indicate its rationale
@@ -3832,7 +3841,7 @@ Updating Mature Publications on the Recommendation Track</h4>
 				if any Process requirements are not met,
 			* <em class=rfc2119>may</em> be withheld
 				in consideration of unresolved Formal Objections
-				(including any [=upheld=] by a [=Council=] but not yet [=fully addressed=]),
+				(including any aspect [=upheld=] by a [=Council=] but not yet [=fully addressed=]),
 			* <em class=rfc2119>may</em> be withheld
 				if the document does not adequately reflect
 				all relevant decisions of a [=W3C Council=] (or its delegates),

From b077baa3b38881c4e04f5819e36bc6148ca24872 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 18 Jun 2025 23:58:15 +0900
Subject: [PATCH 226/237] Allow transition to REC from CRD in certain cases
 (#1070)

See #1063


Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/index.bs b/index.bs
index e0ecc73d..2893638f 100644
--- a/index.bs
+++ b/index.bs
@@ -3632,6 +3632,7 @@ Maturity Stages on the Recommendation Track</h4>
 			However, <a href=#class-4>new features</a> can only be added
 			if the document already identifies itself
 			as intending to <dfn>allow new features</dfn>.
+			Adding or removing this allowance is a [=substantive change=].
 			Such an allowance cannot be added
 			to a [=technical report=] previously published as a [=Recommendation=]
 			that did not allow such changes;
@@ -4162,15 +4163,25 @@ Requirements for Transition</h5>
 	and <em class=rfc2119>must not</em> include any such marking
 	if not already present.
 
+	If the document's most recent publication is a [=Candidate Recommendation Draft=],
+	the [=Team=] <em class=rfc2119>must</em> verify
+	that it contains no changes since the previous [=Candidate Recommendation Snapshot=] other than:
+	* [=editorial changes=],
+	* the addition or removal of a statement as to whether the document will [=allow new features=]
+		after its publication as a [=Recommendation=].
+	* dropping [=at risk=] features
+
+	Otherwise, the [=Working Group=] <em class=rfc2119>must</em> republish it
+	as a [=Candidate Recommendation Snapshot=]
+	prior to initiating the review.
+
 <h5 id="initiating-rec-review">
 Initiating Review</h5>
 
 	If all the criteria above are fulfilled,
 	the [=Team=] <em class="rfc2119">must</em> begin an [=Advisory Committee Review=]
-	on the question of whether the identified [=Candidate Recommendation Snapshot=]
+	on the question of whether the identified [=Candidate Recommendation=]
 	is appropriate to [=publish=] as a [=W3C Recommendation=].
-	If the document's most recent publication is not a [=Candidate Recommendation Snapshot=],
-	then it <em class=rfc2119>must</em> be republished as such in order to provide a basis for review.
 	The deadline for [=Advisory Committee review=]
 	<em class="rfc2119">must</em> allow <strong>at least</strong> 28 days,
 	and <em class=rfc2119>must</em> end at least 10 days

From dbac47731fcf85ea9e87ce05a017294f9012b03e Mon Sep 17 00:00:00 2001
From: plehegar <plh@w3.org>
Date: Mon, 23 Jun 2025 16:31:19 -0400
Subject: [PATCH 227/237] Snapshot

---
 snapshots/2025-06.html | 6526 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 6526 insertions(+)
 create mode 100644 snapshots/2025-06.html

diff --git a/snapshots/2025-06.html b/snapshots/2025-06.html
new file mode 100644
index 00000000..67dcedc3
--- /dev/null
+++ b/snapshots/2025-06.html
@@ -0,0 +1,6526 @@
+<!doctype html><html lang="en">
+ <head>
+  <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+  <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
+  <title>W3C Process Document</title>
+  <meta content="CG-DRAFT" name="w3c-status">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/cg-draft" rel="stylesheet">
+  <meta content="Bikeshed version b25686b9f, updated Fri Mar 14 14:15:20 2025 -0700" name="generator">
+  <link href="https://www.w3.org/policies/process/" rel="canonical">
+  <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
+  <meta content="b077baa3b38881c4e04f5819e36bc6148ca24872" name="revision">
+  <meta content="dark light" name="color-scheme">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
+<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>
+<style>/* Boilerplate: style-autolinks */
+.css.css, .property.property, .descriptor.descriptor {
+    color: var(--a-normal-text);
+    font-size: inherit;
+    font-family: inherit;
+}
+.css::before, .property::before, .descriptor::before {
+    content: "‘";
+}
+.css::after, .property::after, .descriptor::after {
+    content: "’";
+}
+.property, .descriptor {
+    /* Don't wrap property and descriptor names */
+    white-space: nowrap;
+}
+.type { /* CSS value <type> */
+    font-style: italic;
+}
+pre .property::before, pre .property::after {
+    content: "";
+}
+[data-link-type="property"]::before,
+[data-link-type="propdesc"]::before,
+[data-link-type="descriptor"]::before,
+[data-link-type="value"]::before,
+[data-link-type="function"]::before,
+[data-link-type="at-rule"]::before,
+[data-link-type="selector"]::before,
+[data-link-type="maybe"]::before {
+    content: "‘";
+}
+[data-link-type="property"]::after,
+[data-link-type="propdesc"]::after,
+[data-link-type="descriptor"]::after,
+[data-link-type="value"]::after,
+[data-link-type="function"]::after,
+[data-link-type="at-rule"]::after,
+[data-link-type="selector"]::after,
+[data-link-type="maybe"]::after {
+    content: "’";
+}
+
+[data-link-type].production::before,
+[data-link-type].production::after,
+.prod [data-link-type]::before,
+.prod [data-link-type]::after {
+    content: "";
+}
+
+[data-link-type=element],
+[data-link-type=element-attr] {
+    font-family: Menlo, Consolas, "DejaVu Sans Mono", monospace;
+    font-size: .9em;
+}
+[data-link-type=element]::before { content: "<" }
+[data-link-type=element]::after  { content: ">" }
+
+[data-link-type=biblio] {
+    white-space: pre;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --selflink-text: black;
+        --selflink-bg: silver;
+        --selflink-hover-text: white;
+    }
+}
+</style>
+<style>/* Boilerplate: style-colors */
+/* Any --*-text not paired with a --*-bg is assumed to have a transparent bg */
+:root {
+    color-scheme: light dark;
+
+    --text: black;
+    --bg: white;
+
+    --unofficial-watermark: url(https://www.w3.org/StyleSheets/TR/2016/logos/UD-watermark);
+
+    --logo-bg: #1a5e9a;
+    --logo-active-bg: #c00;
+    --logo-text: white;
+
+    --tocnav-normal-text: #707070;
+    --tocnav-normal-bg: var(--bg);
+    --tocnav-hover-text: var(--tocnav-normal-text);
+    --tocnav-hover-bg: #f8f8f8;
+    --tocnav-active-text: #c00;
+    --tocnav-active-bg: var(--tocnav-normal-bg);
+
+    --tocsidebar-text: var(--text);
+    --tocsidebar-bg: #f7f8f9;
+    --tocsidebar-shadow: rgba(0,0,0,.1);
+    --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+    --toclink-text: var(--text);
+    --toclink-underline: #3980b5;
+    --toclink-visited-text: var(--toclink-text);
+    --toclink-visited-underline: #054572;
+
+    --heading-text: #005a9c;
+
+    --hr-text: var(--text);
+
+    --algo-border: #def;
+
+    --del-text: red;
+    --del-bg: transparent;
+    --ins-text: #080;
+    --ins-bg: transparent;
+
+    --a-normal-text: #034575;
+    --a-normal-underline: #bbb;
+    --a-visited-text: var(--a-normal-text);
+    --a-visited-underline: #707070;
+    --a-hover-bg: rgba(75%, 75%, 75%, .25);
+    --a-active-text: #c00;
+    --a-active-underline: #c00;
+
+    --blockquote-border: silver;
+    --blockquote-bg: transparent;
+    --blockquote-text: currentcolor;
+
+    --issue-border: #e05252;
+    --issue-bg: #fbe9e9;
+    --issue-text: var(--text);
+    --issueheading-text: #831616;
+
+    --example-border: #e0cb52;
+    --example-bg: #fcfaee;
+    --example-text: var(--text);
+    --exampleheading-text: #574b0f;
+
+    --note-border: #52e052;
+    --note-bg: #e9fbe9;
+    --note-text: var(--text);
+    --noteheading-text: hsl(120, 70%, 30%);
+    --notesummary-underline: silver;
+
+    --assertion-border: #aaa;
+    --assertion-bg: #eee;
+    --assertion-text: black;
+
+    --advisement-border: orange;
+    --advisement-bg: #fec;
+    --advisement-text: var(--text);
+    --advisementheading-text: #b35f00;
+
+    --warning-border: red;
+    --warning-bg: hsla(40,100%,50%,0.95);
+    --warning-text: var(--text);
+
+    --amendment-border: #330099;
+    --amendment-bg: #F5F0FF;
+    --amendment-text: var(--text);
+    --amendmentheading-text: #220066;
+
+    --def-border: #8ccbf2;
+    --def-bg: #def;
+    --def-text: var(--text);
+    --defrow-border: #bbd7e9;
+
+    --datacell-border: silver;
+
+    --indexinfo-text: #707070;
+
+    --indextable-hover-text: black;
+    --indextable-hover-bg: #f7f8f9;
+
+    --outdatedspec-bg: rgba(0, 0, 0, .5);
+    --outdatedspec-text: black;
+    --outdated-bg: maroon;
+    --outdated-text: white;
+    --outdated-shadow: red;
+
+    --editedrec-bg: darkorange;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --text: #ddd;
+        --bg: black;
+
+        --unofficial-watermark: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='400' height='400'%3E%3Cg fill='%23100808' transform='translate(200 200) rotate(-45) translate(-200 -200)' stroke='%23100808' stroke-width='3'%3E%3Ctext x='50%25' y='220' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EUNOFFICIAL%3C/text%3E%3Ctext x='50%25' y='305' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EDRAFT%3C/text%3E%3C/g%3E%3C/svg%3E");
+
+        --logo-bg: #1a5e9a;
+        --logo-active-bg: #c00;
+        --logo-text: white;
+
+        --tocnav-normal-text: #999;
+        --tocnav-normal-bg: var(--bg);
+        --tocnav-hover-text: var(--tocnav-normal-text);
+        --tocnav-hover-bg: #080808;
+        --tocnav-active-text: #f44;
+        --tocnav-active-bg: var(--tocnav-normal-bg);
+
+        --tocsidebar-text: var(--text);
+        --tocsidebar-bg: #080808;
+        --tocsidebar-shadow: rgba(255,255,255,.1);
+        --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+        --toclink-text: var(--text);
+        --toclink-underline: #6af;
+        --toclink-visited-text: var(--toclink-text);
+        --toclink-visited-underline: #054572;
+
+        --heading-text: #8af;
+
+        --hr-text: var(--text);
+
+        --algo-border: #456;
+
+        --del-text: #f44;
+        --del-bg: transparent;
+        --ins-text: #4a4;
+        --ins-bg: transparent;
+
+        --a-normal-text: #6af;
+        --a-normal-underline: #555;
+        --a-visited-text: var(--a-normal-text);
+        --a-visited-underline: var(--a-normal-underline);
+        --a-hover-bg: rgba(25%, 25%, 25%, .2);
+        --a-active-text: #f44;
+        --a-active-underline: var(--a-active-text);
+
+        --borderedblock-bg: rgba(255, 255, 255, .05);
+
+        --blockquote-border: silver;
+        --blockquote-bg: var(--borderedblock-bg);
+        --blockquote-text: currentcolor;
+
+        --issue-border: #e05252;
+        --issue-bg: var(--borderedblock-bg);
+        --issue-text: var(--text);
+        --issueheading-text: hsl(0deg, 70%, 70%);
+
+        --example-border: hsl(50deg, 90%, 60%);
+        --example-bg: var(--borderedblock-bg);
+        --example-text: var(--text);
+        --exampleheading-text: hsl(50deg, 70%, 70%);
+
+        --note-border: hsl(120deg, 100%, 35%);
+        --note-bg: var(--borderedblock-bg);
+        --note-text: var(--text);
+        --noteheading-text: hsl(120, 70%, 70%);
+        --notesummary-underline: silver;
+
+        --assertion-border: #444;
+        --assertion-bg: var(--borderedblock-bg);
+        --assertion-text: var(--text);
+
+        --advisement-border: orange;
+        --advisement-bg: #222218;
+        --advisement-text: var(--text);
+        --advisementheading-text: #f84;
+
+        --warning-border: red;
+        --warning-bg: hsla(40,100%,20%,0.95);
+        --warning-text: var(--text);
+
+        --amendment-border: #330099;
+        --amendment-bg: #080010;
+        --amendment-text: var(--text);
+        --amendmentheading-text: #cc00ff;
+
+        --def-border: #8ccbf2;
+        --def-bg: #080818;
+        --def-text: var(--text);
+        --defrow-border: #136;
+
+        --datacell-border: silver;
+
+        --indexinfo-text: #aaa;
+
+        --indextable-hover-text: var(--text);
+        --indextable-hover-bg: #181818;
+
+        --outdatedspec-bg: rgba(255, 255, 255, .5);
+        --outdatedspec-text: black;
+        --outdated-bg: maroon;
+        --outdated-text: white;
+        --outdated-shadow: red;
+
+        --editedrec-bg: darkorange;
+    }
+    /* In case a transparent-bg image doesn't expect to be on a dark bg,
+       which is quite common in practice... */
+    img { background: white; }
+}
+</style>
+<style>/* Boilerplate: style-counters */
+body {
+    counter-reset: example figure issue;
+}
+.issue {
+    counter-increment: issue;
+}
+.issue:not(.no-marker)::before {
+    content: "Issue " counter(issue);
+}
+
+.example {
+    counter-increment: example;
+}
+.example:not(.no-marker)::before {
+    content: "Example " counter(example);
+}
+.invalid.example:not(.no-marker)::before,
+.illegal.example:not(.no-marker)::before {
+    content: "Invalid Example" counter(example);
+}
+
+figcaption {
+    counter-increment: figure;
+}
+figcaption:not(.no-marker)::before {
+    content: "Figure " counter(figure) " ";
+}
+</style>
+<style>/* Boilerplate: style-dfn-panel */
+:root {
+    --dfnpanel-bg: #ddd;
+    --dfnpanel-text: var(--text);
+    --dfnpanel-target-bg: #ffc;
+    --dfnpanel-target-outline: orange;
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --dfnpanel-bg: #222;
+        --dfnpanel-text: var(--text);
+        --dfnpanel-target-bg: #333;
+        --dfnpanel-target-outline: silver;
+    }
+}
+.dfn-panel {
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.75em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--dfnpanel-bg);
+    color: var(--dfnpanel-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+.dfn-panel:not(.on) { display: none; }
+.dfn-panel * { margin: 0; padding: 0; text-indent: 0; }
+.dfn-panel > b { display: block; }
+.dfn-panel a { color: var(--dfnpanel-text); }
+.dfn-panel a:not(:hover) { text-decoration: none !important; border-bottom: none !important; }
+.dfn-panel a:focus {
+    outline: 5px auto Highlight;
+    outline: 5px auto -webkit-focus-ring-color;
+}
+.dfn-panel > b + b { margin-top: 0.25em; }
+.dfn-panel ul { padding: 0 0 0 1em; list-style: none; }
+.dfn-panel li a {
+    max-width: calc(300px - 1.5em - 1em);
+    overflow: hidden;
+    text-overflow: ellipsis;
+}
+
+.dfn-panel.activated {
+    display: inline-block;
+    position: fixed;
+    left: 8px;
+    bottom: 2em;
+    margin: 0 auto;
+    max-width: calc(100vw - 1.5em - .4em - .5em);
+    max-height: 30vh;
+    transition: left 1s ease-out, bottom 1s ease-out;
+}
+
+.dfn-panel .link-item:hover {
+    text-decoration: underline;
+}
+.dfn-panel .link-item .copy-icon {
+    opacity: 0;
+}
+.dfn-panel .link-item:hover .copy-icon,
+.dfn-panel .link-item .copy-icon:focus {
+    opacity: 1;
+}
+
+.dfn-panel .copy-icon {
+    display: inline-block;
+    margin-right: 0.5em;
+    width: 0.85em;
+    height: 1em;
+    border-radius: 3px;
+    background-color: #ccc;
+    cursor: pointer;
+}
+
+.dfn-panel .copy-icon .icon {
+    width: 100%;
+    height: 100%;
+    background-color: #fff;
+    display: flex;
+    justify-content: center;
+    align-items: center;
+    position: relative;
+}
+
+.dfn-panel .copy-icon .icon::before {
+    content: "";
+    position: absolute;
+    top: 0;
+    left: 0;
+    width: 100%;
+    height: 100%;
+    border: 1px solid black;
+    background-color: #ccc;
+    opacity: 0.25;
+    transform: translate(3px, -3px);
+}
+
+.dfn-panel .copy-icon:active .icon::before {
+    opacity: 1;
+}
+
+.dfn-paneled[role="button"] { cursor: help; }
+
+.highlighted {
+    animation: target-fade 3s;
+}
+
+@keyframes target-fade {
+    from {
+        background-color: var(--dfnpanel-target-bg);
+        outline: 5px solid var(--dfnpanel-target-outline);
+    }
+    to {
+        color: var(--a-normal-text);
+        background-color: transparent;
+        outline: transparent;
+    }
+}
+</style>
+<style>/* Boilerplate: style-issues */
+a[href].issue-return {
+    float: right;
+    float: inline-end;
+    color: var(--issueheading-text);
+    font-weight: bold;
+    text-decoration: none;
+}
+</style>
+<style>/* Boilerplate: style-md-lists */
+/* This is a weird hack for me not yet following the commonmark spec
+   regarding paragraph and lists. */
+[data-md] > :first-child {
+    margin-top: 0;
+}
+[data-md] > :last-child {
+    margin-bottom: 0;
+}
+</style>
+<style>/* Boilerplate: style-ref-hints */
+:root {
+    --ref-hint-bg: #ddd;
+    --ref-hint-text: var(--text);
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --ref-hint-bg: #222;
+        --ref-hint-text: var(--text);
+    }
+}
+
+.ref-hint {
+    display: inline-block;
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.5em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--ref-hint-bg);
+    color: var(--ref-hint-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+
+.ref-hint * { margin: 0; padding: 0; text-indent: 0; }
+
+.ref-hint ul { padding: 0 0 0 1em; list-style: none; }
+</style>
+<style>/* Boilerplate: style-selflinks */
+:root {
+    --selflink-text: white;
+    --selflink-bg: gray;
+    --selflink-hover-text: black;
+}
+.heading, .issue, .note, .example, li, dt {
+    position: relative;
+}
+a.self-link {
+    position: absolute;
+    top: 0;
+    left: calc(-1 * (3.5rem - 26px));
+    width: calc(3.5rem - 26px);
+    height: 2em;
+    text-align: center;
+    border: none;
+    transition: opacity .2s;
+    opacity: .5;
+}
+a.self-link:hover {
+    opacity: 1;
+}
+.heading > a.self-link {
+    font-size: 83%;
+}
+.example > a.self-link,
+.note > a.self-link,
+.issue > a.self-link {
+    /* These blocks are overflow:auto, so positioning outside
+       doesn't work. */
+    left: auto;
+    right: 0;
+}
+li > a.self-link {
+    left: calc(-1 * (3.5rem - 26px) - 2em);
+}
+dfn > a.self-link {
+    top: auto;
+    left: auto;
+    opacity: 0;
+    width: 1.5em;
+    height: 1.5em;
+    background: var(--selflink-bg);
+    color: var(--selflink-text);
+    font-style: normal;
+    transition: opacity .2s, background-color .2s, color .2s;
+}
+dfn:hover > a.self-link {
+    opacity: 1;
+}
+dfn > a.self-link:hover {
+    color: var(--selflink-hover-text);
+}
+
+a.self-link::before            { content: "¶"; }
+.heading > a.self-link::before { content: "§"; }
+dfn > a.self-link::before      { content: "#"; }
+</style>
+ <body class="h-entry">
+  <div class="head">
+   <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
+   <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types/#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2025-06-23">23 June 2025</time></p>
+   <details open>
+    <summary>More details about this document</summary>
+    <div data-fill-with="spec-metadata">
+     <dl>
+      <dt>This version:
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/</a>
+      <dt>Latest published version:
+      <dd><a href="https://www.w3.org/policies/process/">https://www.w3.org/policies/process/</a>
+      <dt>Previous Versions:
+      <dd><a href="https://www.w3.org/policies/process/20231103/" rel="prev">https://www.w3.org/policies/process/20231103/</a>
+      <dt>Feedback:
+      <dd><a href="https://github.com/w3c/process/issues/">Github (preferred)</a>
+      <dd><a href="https://lists.w3.org/Archives/Public/public-w3process/">Public mailing list</a>
+      <dd><a href="https://lists.w3.org/Archives/Member/process-issues">Member-only mailing list</a>
+      <dt class="editor">Editors:
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://fantasai.inkedblade.net/contact">Elika J. Etemad / fantasai</a> (<span class="p-org org">Apple</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://florian.rivoal.net/">Florian Rivoal</a> (<span class="p-org org">Invited Expert</span>)
+      <dt class="editor">Former Editors:
+      <dd class="editor p-author h-card vcard"><span class="p-name fn">Natasha Rooney</span> (<span class="p-org org">Invited Expert</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://yandex.com">Charles McCathie Nevile</a> (<span class="p-org org">Yandex</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://www.w3.org/">Ian Jacobs</a> (<span class="p-org org">W3C</span>)
+     </dl>
+    </div>
+   </details>
+   <div data-fill-with="warning"></div>
+   <p class="copyright" data-fill-with="copyright"><a href="https://www.w3.org/policies/#copyright">Copyright</a> © 2025 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/policies/#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/policies/#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/copyright/software-license/" rel="license" title="W3C Software and Document License">permissive document license</a> rules apply. </p>
+   <hr title="Separator for header">
+  </div>
+  <div class="p-summary" data-fill-with="abstract">
+   <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></h2>
+   <p>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.</p>
+   <p>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>.</p>
+  </div>
+  <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content">Status of this document</span></h2>
+  <div data-fill-with="status">
+   <p> W3C, including all existing chartered groups,
+	follows the <a href="https://www.w3.org/policies/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
+	working within the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a> (which anyone can join).
+	This is the 23 June 2025 Draft Community Group Report for the proposed next version of the W3C Process Document. </p>
+   <p>This document,
+which is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>,
+is offered for W3C Advisory Committee Review of the proposal to adopt this
+as the new operative Process document
+per <a href="https://www.w3.org/Consortium/Process/#GAProcess">Section 11 Process Changes</a>.</p>
+   <p> A <a href="#changes">history of substantial changes</a> from previous versions of the Process Document is provided. </p>
+  </div>
+  <div data-fill-with="at-risk"></div>
+  <nav data-fill-with="table-of-contents" id="toc">
+   <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
+   <ol class="toc" role="directory">
+    <li><a href="#Intro"><span class="secno">1</span> <span class="content"> Introduction</span></a>
+    <li>
+     <a href="#Organization"><span class="secno">2</span> <span class="content"> Members and the Team</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Members"><span class="secno">2.1</span> <span class="content"> Members</span></a>
+       <ol class="toc">
+        <li><a href="#MemberBenefits"><span class="secno">2.1.1</span> <span class="content"> Rights of Members</span></a>
+        <li>
+         <a href="#RelatedAndAssociatedMembers"><span class="secno">2.1.2</span> <span class="content"> Member Associations and Related Members</span></a>
+         <ol class="toc">
+          <li><a href="#MemberAssoc"><span class="secno">2.1.2.1</span> <span class="content"> Membership Associations</span></a>
+          <li><a href="#MemberRelated"><span class="secno">2.1.2.2</span> <span class="content"> Related Members</span></a>
+         </ol>
+        <li><a href="#standing"><span class="secno">2.1.3</span> <span class="content"> Good Standing</span></a>
+       </ol>
+      <li><a href="#Team"><span class="secno">2.2</span> <span class="content"> The W3C Team</span></a>
+     </ol>
+    <li>
+     <a href="#groups"><span class="secno">3</span> <span class="content"> Groups and Participation</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Policies"><span class="secno">3.1</span> <span class="content"> Policies for Participation in W3C Groups</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#ParticipationCriteria"><span class="secno">3.1.1</span> <span class="content"> Individual Participation Criteria</span></a>
+         <ol class="toc">
+          <li><a href="#discipline"><span class="secno">3.1.1.1</span> <span class="content"> Expectations and Discipline</span></a>
+          <li><a href="#coi"><span class="secno">3.1.1.2</span> <span class="content"> Conflict of Interest Policy</span></a>
+          <li><a href="#member-rep"><span class="secno">3.1.1.3</span> <span class="content"> Individuals Representing a Member Organization</span></a>
+         </ol>
+        <li>
+         <a href="#GeneralMeetings"><span class="secno">3.1.2</span> <span class="content"> Meetings</span></a>
+         <ol class="toc">
+          <li><a href="#meeting-schedules"><span class="secno">3.1.2.1</span> <span class="content"> Meeting Scheduling and Announcements</span></a>
+          <li><a href="#meeting-minutes"><span class="secno">3.1.2.2</span> <span class="content"> Meeting Minutes</span></a>
+          <li><a href="#meeting-recording"><span class="secno">3.1.2.3</span> <span class="content"> Meeting Recordings and Transcripts</span></a>
+         </ol>
+        <li><a href="#tooling"><span class="secno">3.1.3</span> <span class="content"> Tooling and Archiving for Discussions and Publications</span></a>
+        <li><a href="#resignation"><span class="secno">3.1.4</span> <span class="content"> Resignation from a Group</span></a>
+       </ol>
+      <li>
+       <a href="#AC"><span class="secno">3.2</span> <span class="content"> The Advisory Committee (AC)</span></a>
+       <ol class="toc">
+        <li><a href="#ac-role"><span class="secno">3.2.1</span> <span class="content"> Role of the Advisory Committee</span></a>
+        <li><a href="#ac-participation"><span class="secno">3.2.2</span> <span class="content"> Participation in the Advisory Committee</span></a>
+        <li><a href="#ACCommunication"><span class="secno">3.2.3</span> <span class="content"> Advisory Committee Mailing Lists</span></a>
+        <li><a href="#ACMeetings"><span class="secno">3.2.4</span> <span class="content"> Advisory Committee Meetings</span></a>
+       </ol>
+      <li>
+       <a href="#elected-groups"><span class="secno">3.3</span> <span class="content"> Elected Groups: The AB and the TAG</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#AB"><span class="secno">3.3.1</span> <span class="content"> Advisory Board (AB)</span></a>
+         <ol class="toc">
+          <li><a href="#ab-role"><span class="secno">3.3.1.1</span> <span class="content"> Role of the Advisory Board</span></a>
+          <li><a href="#ABParticipation"><span class="secno">3.3.1.2</span> <span class="content"> Composition of the Advisory Board</span></a>
+          <li><a href="#ab-comm"><span class="secno">3.3.1.3</span> <span class="content"> Communications of the Advisory Board</span></a>
+          <li><a href="#ab-bod-liaison"><span class="secno">3.3.1.4</span> <span class="content"> Liaisons between the Advisory Board and the Board of Directors</span></a>
+         </ol>
+        <li>
+         <a href="#TAG"><span class="secno">3.3.2</span> <span class="content"> Technical Architecture Group (TAG)</span></a>
+         <ol class="toc">
+          <li><a href="#tag-role"><span class="secno">3.3.2.1</span> <span class="content"> Role of the Technical Architecture Group</span></a>
+          <li><a href="#tag-participation"><span class="secno">3.3.2.2</span> <span class="content"> Composition of the Technical Architecture Group</span></a>
+          <li><a href="#tag-comm"><span class="secno">3.3.2.3</span> <span class="content"> Communications of the Technical Architecture Group</span></a>
+         </ol>
+        <li>
+         <a href="#AB-TAG-participation"><span class="secno">3.3.3</span> <span class="content"> Participation in Elected Groups</span></a>
+         <ol class="toc">
+          <li><a href="#elected-expectations"><span class="secno">3.3.3.1</span> <span class="content"> Expectations for Elected Groups Participants</span></a>
+          <li><a href="#AB-TAG-constraints"><span class="secno">3.3.3.2</span> <span class="content"> Elected Groups Participation Constraints</span></a>
+          <li><a href="#AB-TAG-elections"><span class="secno">3.3.3.3</span> <span class="content"> Advisory Board and Technical Architecture Group Elections</span></a>
+          <li><a href="#TAG-appointments"><span class="secno">3.3.3.4</span> <span class="content"> Technical Architecture Group Appointments</span></a>
+          <li><a href="#random"><span class="secno">3.3.3.5</span> <span class="content"> Verifiable Random Selection Procedure</span></a>
+          <li><a href="#AB-TAG-vacated"><span class="secno">3.3.3.6</span> <span class="content"> Elected Groups Vacated Seats</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#GAGeneral"><span class="secno">3.4</span> <span class="content"> Chartered Groups: Working Groups and Interest Groups</span></a>
+       <ol class="toc">
+        <li><a href="#ReqsAllGroups"><span class="secno">3.4.1</span> <span class="content"> Requirements for All Chartered Groups</span></a>
+        <li><a href="#group-participation"><span class="secno">3.4.2</span> <span class="content"> Participation in Chartered Groups</span></a>
+        <li>
+         <a href="#chartered-group-participants"><span class="secno">3.4.3</span> <span class="content"> Types of Participants in Chartered Groups</span></a>
+         <ol class="toc">
+          <li><a href="#member-rep-wg"><span class="secno">3.4.3.1</span> <span class="content"> Member Representative in a Working Group</span></a>
+          <li><a href="#member-rep-ig"><span class="secno">3.4.3.2</span> <span class="content"> Member Representative in an Interest Group</span></a>
+          <li><a href="#invited-expert-wg"><span class="secno">3.4.3.3</span> <span class="content"> Invited Expert in a Working Group</span></a>
+          <li><a href="#invited-expert-ig"><span class="secno">3.4.3.4</span> <span class="content"> Invited Expert in an Interest Group</span></a>
+          <li><a href="#team-rep-wg"><span class="secno">3.4.3.5</span> <span class="content"> Team Representative in a Working Group</span></a>
+          <li><a href="#team-rep-ig"><span class="secno">3.4.3.6</span> <span class="content"> Team Representative in an Interest Group</span></a>
+         </ol>
+       </ol>
+     </ol>
+    <li>
+     <a href="#group-lifecycle"><span class="secno">4</span> <span class="content"> Lifecycle of Chartered Groups</span></a>
+     <ol class="toc">
+      <li><a href="#charter-initiation"><span class="secno">4.1</span> <span class="content"> Initiating Charter Refinement</span></a>
+      <li><a href="#charter-development"><span class="secno">4.2</span> <span class="content"> Charter Refinement</span></a>
+      <li><a href="#WGCharter"><span class="secno">4.3</span> <span class="content"> Content of a Charter</span></a>
+      <li>
+       <a href="#CharterReview"><span class="secno">4.4</span> <span class="content"> Charter Review and Approval</span></a>
+       <ol class="toc">
+        <li><a href="#charter-major-changes"><span class="secno">4.4.1</span> <span class="content"> New Charters and Major Changes</span></a>
+        <li><a href="#charter-minor-changes"><span class="secno">4.4.2</span> <span class="content"> Minor Changes to Active Charters</span></a>
+       </ol>
+      <li><a href="#cfp"><span class="secno">4.5</span> <span class="content"> Call for Participation in a Chartered Group</span></a>
+      <li><a href="#charter-extension"><span class="secno">4.6</span> <span class="content"> Charter Extension</span></a>
+      <li><a href="#GeneralTermination"><span class="secno">4.7</span> <span class="content"> Chartered Group Closure</span></a>
+     </ol>
+    <li>
+     <a href="#decisions"><span class="secno">5</span> <span class="content"> Decisions</span></a>
+     <ol class="toc">
+      <li><a href="#decision-types"><span class="secno">5.1</span> <span class="content"> Types of Decisions</span></a>
+      <li>
+       <a href="#consensus-building"><span class="secno">5.2</span> <span class="content"> Consensus Building</span></a>
+       <ol class="toc">
+        <li><a href="#Consensus"><span class="secno">5.2.1</span> <span class="content"> Consensus</span></a>
+        <li><a href="#managing-dissent"><span class="secno">5.2.2</span> <span class="content"> Managing Dissent</span></a>
+        <li><a href="#Votes"><span class="secno">5.2.3</span> <span class="content"> Deciding by Vote</span></a>
+       </ol>
+      <li><a href="#formal-address"><span class="secno">5.3</span> <span class="content"> Formally Addressing an Issue</span></a>
+      <li><a href="#WGChairReopen"><span class="secno">5.4</span> <span class="content"> Reopening a Decision When Presented With New Information</span></a>
+      <li><a href="#registering-objections"><span class="secno">5.5</span> <span class="content"> Registering Formal Objections</span></a>
+      <li>
+       <a href="#addressing-fo"><span class="secno">5.6</span> <span class="content"> Addressing Formal Objections</span></a>
+       <ol class="toc">
+        <li><a href="#team-fo-mediation"><span class="secno">5.6.1</span> <span class="content"> Investigation and Mediation by the Team</span></a>
+        <li>
+         <a href="#council"><span class="secno">5.6.2</span> <span class="content"> W3C Council</span></a>
+         <ol class="toc">
+          <li><a href="#council-composition"><span class="secno">5.6.2.1</span> <span class="content"> Council Composition</span></a>
+          <li><a href="#council-delegation"><span class="secno">5.6.2.2</span> <span class="content"> Extraordinary Delegation</span></a>
+          <li><a href="#council-participation"><span class="secno">5.6.2.3</span> <span class="content"> Council Participation, Dismissal, and Renunciation</span></a>
+          <li><a href="#council-short-circuit"><span class="secno">5.6.2.4</span> <span class="content"> Short Circuit</span></a>
+          <li><a href="#council-chairing"><span class="secno">5.6.2.5</span> <span class="content"> Council Chairing</span></a>
+          <li><a href="#council-convention"><span class="secno">5.6.2.6</span> <span class="content"> Convening the Council</span></a>
+          <li><a href="#council-deliberations"><span class="secno">5.6.2.7</span> <span class="content"> Council Deliberations</span></a>
+          <li><a href="#council-decision"><span class="secno">5.6.2.8</span> <span class="content"> Council Decision Report</span></a>
+          <li><a href="#council-appeals"><span class="secno">5.6.2.9</span> <span class="content"> Appealing Council Decisions</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#ACReview"><span class="secno">5.7</span> <span class="content"> Advisory Committee Reviews and W3C Decisions</span></a>
+       <ol class="toc">
+        <li><a href="#ACReviewStart"><span class="secno">5.7.1</span> <span class="content"> Initiating an Advisory Committee Review</span></a>
+        <li><a href="#ACReviewAfter"><span class="secno">5.7.2</span> <span class="content"> Determining the W3C Decision</span></a>
+       </ol>
+      <li><a href="#ACVotes"><span class="secno">5.8</span> <span class="content"> Advisory Committee Votes</span></a>
+      <li><a href="#ACAppeal"><span class="secno">5.9</span> <span class="content"> Appeal by Advisory Committee Representatives</span></a>
+     </ol>
+    <li>
+     <a href="#Reports"><span class="secno">6</span> <span class="content"> W3C Technical Reports</span></a>
+     <ol class="toc">
+      <li><a href="#recs-and-notes"><span class="secno">6.1</span> <span class="content"> Types of Technical Reports</span></a>
+      <li>
+       <a href="#general-requirements"><span class="secno">6.2</span> <span class="content"> General Requirements for Technical Reports</span></a>
+       <ol class="toc">
+        <li><a href="#publication"><span class="secno">6.2.1</span> <span class="content"> Publication of Technical Reports</span></a>
+        <li>
+         <a href="#doc-reviews"><span class="secno">6.2.2</span> <span class="content"> Reviews and Review Responsibilities</span></a>
+         <ol class="toc">
+          <li><a href="#wide-review"><span class="secno">6.2.2.1</span> <span class="content"> Wide Review</span></a>
+         </ol>
+        <li><a href="#correction-classes"><span class="secno">6.2.3</span> <span class="content"> Classes of Changes</span></a>
+        <li><a href="#errata"><span class="secno">6.2.4</span> <span class="content"> Errata Management</span></a>
+        <li><a href="#candidate-amendments"><span class="secno">6.2.5</span> <span class="content"> Candidate Amendments</span></a>
+        <li><a href="#no-group-maintenance"><span class="secno">6.2.6</span> <span class="content"> Maintenance Without a Group</span></a>
+        <li><a href="#contributor-license"><span class="secno">6.2.7</span> <span class="content"> License Grants from Non-Participants</span></a>
+       </ol>
+      <li>
+       <a href="#rec-track"><span class="secno">6.3</span> <span class="content"> The W3C Recommendation Track</span></a>
+       <ol class="toc">
+        <li><a href="#maturity-stages"><span class="secno">6.3.1</span> <span class="content"> Maturity Stages on the Recommendation Track</span></a>
+        <li><a href="#implementation-experience"><span class="secno">6.3.2</span> <span class="content"> Implementation Experience</span></a>
+        <li><a href="#transition-reqs"><span class="secno">6.3.3</span> <span class="content"> Advancement on the Recommendation Track</span></a>
+        <li><a href="#update-reqs"><span class="secno">6.3.4</span> <span class="content"> Updating Mature Publications on the Recommendation Track</span></a>
+        <li><a href="#first-wd"><span class="secno">6.3.5</span> <span class="content"> Publishing a First Public Working Draft</span></a>
+        <li><a href="#revising-wd"><span class="secno">6.3.6</span> <span class="content"> Revising a Working Draft</span></a>
+        <li><a href="#transition-cr"><span class="secno">6.3.7</span> <span class="content"> Transitioning to Candidate Recommendation</span></a>
+        <li>
+         <a href="#revising-cr"><span class="secno">6.3.8</span> <span class="content"> Revising a Candidate Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#publishing-crrs"><span class="secno">6.3.8.1</span> <span class="content"> Publishing a <span>Candidate Recommendation Snapshot</span></span></a>
+          <li><a href="#publishing-crud"><span class="secno">6.3.8.2</span> <span class="content"> Publishing a <span>Candidate Recommendation Draft</span></span></a>
+         </ol>
+        <li>
+         <a href="#transition-rec"><span class="secno">6.3.9</span> <span class="content"> Transitioning to Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#transition-rec-requirements"><span class="secno">6.3.9.1</span> <span class="content"> Requirements for Transition</span></a>
+          <li><a href="#initiating-rec-review"><span class="secno">6.3.9.2</span> <span class="content"> Initiating Review</span></a>
+          <li><a href="#rec-review-resolution"><span class="secno">6.3.9.3</span> <span class="content"> Resolution of Review</span></a>
+          <li><a href="#rec-next-steps"><span class="secno">6.3.9.4</span> <span class="content"> Next Steps from W3C Recommendation</span></a>
+         </ol>
+        <li>
+         <a href="#revising-rec"><span class="secno">6.3.10</span> <span class="content"> Revising a W3C Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#revised-rec-editorial"><span class="secno">6.3.10.1</span> <span class="content"> Revising a Recommendation: Editorial Changes</span></a>
+          <li><a href="#revised-rec-substantive"><span class="secno">6.3.10.2</span> <span class="content"> Revising a Recommendation: Substantive Changes</span></a>
+          <li><a href="#revised-rec-features"><span class="secno">6.3.10.3</span> <span class="content"> Revising a Recommendation: New Features</span></a>
+          <li><a href="#change-review"><span class="secno">6.3.10.4</span> <span class="content"> Incorporating Candidate Amendments</span></a>
+         </ol>
+        <li><a href="#rec-track-regression"><span class="secno">6.3.11</span> <span class="content"> Regression on the Recommendation Track</span></a>
+        <li>
+         <a href="#tr-end"><span class="secno">6.3.12</span> <span class="content"> Retiring Recommendation Track Documents</span></a>
+         <ol class="toc">
+          <li><a href="#abandon-draft"><span class="secno">6.3.12.1</span> <span class="content"> Abandoning an Unfinished Recommendation</span></a>
+          <li><a href="#rescind-cr"><span class="secno">6.3.12.2</span> <span class="content"> Rescinding a Candidate Recommendation</span></a>
+          <li><a href="#rec-rescind"><span class="secno">6.3.12.3</span> <span class="content"> Abandoning a W3C Recommendation</span></a>
+          <li><a href="#deactivation"><span class="secno">6.3.12.4</span> <span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#note-track"><span class="secno">6.4</span> <span class="content"> The Note Track (Notes and Statements)</span></a>
+       <ol class="toc">
+        <li><a href="#Note"><span class="secno">6.4.1</span> <span class="content"> Group Notes</span></a>
+        <li><a href="#publishing-notes"><span class="secno">6.4.2</span> <span class="content"> Publishing Notes</span></a>
+        <li><a href="#w3c-statement"><span class="secno">6.4.3</span> <span class="content"> Elevating Group Notes to W3C Statement status</span></a>
+        <li><a href="#revising-memo"><span class="secno">6.4.4</span> <span class="content"> Revising W3C Statements</span></a>
+       </ol>
+      <li>
+       <a href="#registries"><span class="secno">6.5</span> <span class="content"> The Registry Track</span></a>
+       <ol class="toc">
+        <li><a href="#reg-def"><span class="secno">6.5.1</span> <span class="content"> Registry Definitions</span></a>
+        <li><a href="#reg-pub"><span class="secno">6.5.2</span> <span class="content"> Publishing Registries</span></a>
+        <li><a href="#reg-table-update"><span class="secno">6.5.3</span> <span class="content"> Updating Registry Tables</span></a>
+        <li><a href="#reg-data-reports"><span class="secno">6.5.4</span> <span class="content"> Registry Data Reports</span></a>
+        <li><a href="#reg-ref-specifications"><span class="secno">6.5.5</span> <span class="content"> Specifications that Reference Registries</span></a>
+        <li><a href="#reg-pat"><span class="secno">6.5.6</span> <span class="content"> Registries and Patents</span></a>
+       </ol>
+      <li><a href="#switching-tracks"><span class="secno">6.6</span> <span class="content"> Switching Tracks</span></a>
+      <li><a href="#further-reading"><span class="secno">6.7</span> <span class="content"> Further reading</span></a>
+     </ol>
+    <li>
+     <a href="#dissemination"><span class="secno">7</span> <span class="content"> <span></span> Dissemination Policies</span></a>
+     <ol class="toc">
+      <li><a href="#pub-com"><span class="secno">7.1</span> <span class="content"> Public Communication</span></a>
+      <li><a href="#confidentiality-levels"><span class="secno">7.2</span> <span class="content"> Confidentiality Levels</span></a>
+      <li><a href="#confidentiality-change"><span class="secno">7.3</span> <span class="content"> Changing Confidentiality Level</span></a>
+     </ol>
+    <li><a href="#Liaisons"><span class="secno">8</span> <span class="content"> Liaisons</span></a>
+    <li><a href="#Submission"><span class="secno">9</span> <span class="content"> Member Submissions</span></a>
+    <li><a href="#GAProcess"><span class="secno">10</span> <span class="content"> Process Evolution</span></a>
+    <li><a href="#old-terms"><span class="secno"></span> <span class="content"> Appendix A: Retired Terminology</span></a>
+    <li><a href="#acks"><span class="secno"></span> <span class="content"> Appendix B: Acknowledgments</span></a>
+    <li>
+     <a href="#changes"><span class="secno"></span> <span class="content"> Appendix C: Changes</span></a>
+     <ol class="toc">
+      <li><a href="#changes-2025"><span class="secno"></span> <span class="content"> Changes since the <span>3 November 2023 Process</span></span></a>
+      <li><a href="#changes-previous"><span class="secno"></span> <span class="content"> Changes since earlier versions</span></a>
+     </ol>
+    <li>
+     <a href="#w3c-conformance"><span class="secno"></span> <span class="content">Conformance</span></a>
+     <ol class="toc">
+      <li><a href="#w3c-conventions"><span class="secno"></span> <span class="content">Document conventions</span></a>
+     </ol>
+    <li>
+     <a href="#index"><span class="secno"></span> <span class="content">Index</span></a>
+     <ol class="toc">
+      <li><a href="#index-defined-here"><span class="secno"></span> <span class="content">Terms defined by this specification</span></a>
+      <li><a href="#index-defined-elsewhere"><span class="secno"></span> <span class="content">Terms defined by reference</span></a>
+     </ol>
+    <li>
+     <a href="#references"><span class="secno"></span> <span class="content">References</span></a>
+     <ol class="toc">
+      <li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
+      <li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
+     </ol>
+   </ol>
+  </nav>
+  <main>
+   <h2 class="no-num no-toc no-ref heading settled" id="pp"><span class="content"> Relation of Process Document to Patent Policy and Other Policies</span></h2>
+   <p>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> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	The <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and other policies
+	incorporated by normative reference as a part of the Process Document
+	are equally binding.</p>
+   <p>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.</p>
+   <p>In the Process Document, the term “participant” refers to an individual, not an organization.</p>
+   <h2 class="no-num no-toc no-ref heading settled" id="terms"><span class="content"> Conformance and specialized terms</span></h2>
+   <p>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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="not-required"><em class="rfc2119">not required</em></dfn> is equivalent to the term <em class="rfc2119">may</em> as defined in RFC2119 <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a>.</p>
+   <p>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.</p>
+   <nav data-fill-with="table-of-contents"></nav>
+   <main>
+    <h2 class="heading settled" data-level="1" id="Intro"><span class="secno">1. </span><span class="content"> Introduction</span><a class="self-link" href="#Intro"></a></h2>
+    <p>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>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>. <a href="#group-participation">Participants</a> in W3C include <a href="#member-rep">representatives of its Members</a> and the <a data-link-type="dfn" href="#team" id="ref-for-team">Team</a>,
+	as well as <a href="#invited-expert-wg">Invited Experts</a> who can bring additional expertise or represent additional stakeholders. <a data-link-type="dfn" href="#team" id="ref-for-team①">Team</a> representatives both contribute to the technical work
+	and help ensure each group’s proper integration with the rest of W3C.</p>
+    <p>W3C’s technical standards, called <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C">W3C Recommendations</a>,
+	are developed by its <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG">Working Groups</a>;
+	W3C also has other types of publications,
+	all described in <a href="#Reports">§ 6 W3C Technical Reports</a>.
+	W3C has various types of groups;
+	this document describes the formation and policies
+	of its chartered <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG">Interest Groups</a>,
+	see <a href="#Policies">§ 3.1 Policies for Participation in W3C Groups</a> and <a href="#GAGeneral">§ 3.4 Chartered Groups: Working Groups and Interest Groups</a>.
+	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> <a data-link-type="biblio" href="#biblio-bg-cg" title="Community and Business Group Process">[BG-CG]</a>.</p>
+    <p>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.</p>
+    <p>Here is a general overview of how W3C initiates standardization of a Web technology:</p>
+    <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 <a data-link-type="dfn" href="#team" id="ref-for-team②">Team</a> 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>
+    <p>Further sections of this Process Document deal with topics including
+	liaisons (<a href="#Liaisons">§ 8 Liaisons</a>),
+	confidentiality (<a href="#dissemination">§ 7 Dissemination Policies</a>),
+	and formal decisions and appeals (<a href="#decisions">§ 5 Decisions</a>).</p>
+    <h2 class="heading settled" data-level="2" id="Organization"><span class="secno">2. </span><span class="content"> Members and the Team</span><a class="self-link" href="#Organization"></a></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 class="heading settled" data-level="2.1" id="Members"><span class="secno">2.1. </span><span class="content"> Members</span><a class="self-link" href="#Members"></a></h3>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Member|Member" data-noexport id="w3c-member">W3C Members</dfn> are
+	organizations subscribed according to a <a href="https://www.w3.org/membership/agreement/">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	They are represented in W3C processes as follows:</p>
+    <ol>
+     <li> One representative per Member organization participates
+			in the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee">Advisory Committee</a> 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>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>;
+	(refer to the public list of <a href="https://www.w3.org/membership/list/">current W3C Members</a> <a data-link-type="biblio" href="#biblio-member-list" title="The list of current W3C Members">[MEMBER-LIST]</a>).
+	The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure
+	that Member participation agreements remain <a href="#Team-only" id="ref-for-Team-only">Team-only</a> and that no Member receives preferential treatment within W3C. </p>
+    <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. </p>
+    <h4 class="heading settled" data-level="2.1.1" id="MemberBenefits"><span class="secno">2.1.1. </span><span class="content"> Rights of Members</span><a class="self-link" href="#MemberBenefits"></a></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> Access to <a href="#Member-only" id="ref-for-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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>. 
+    </ul>
+    <p>Furthermore, subject to further restrictions included in their 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>
+       In <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW">Workshops</a>. 
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>)</p>
+     <li> On the Team, as <a href="#fellows" id="ref-for-fellows">W3C Fellows</a>. 
+    </ul>
+    <p>The rights and benefits of W3C membership <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> are contingent upon conformance to the processes described in this document.
+	Disciplinary action for anyone participating in W3C activities is described in <a href="#discipline">§ 3.1.1.1 Expectations and Discipline</a>.</p>
+    <p>Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member website</a> <a data-link-type="biblio" href="#biblio-member-hp" title="Member website (Member-only access)">[MEMBER-HP]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.2" id="RelatedAndAssociatedMembers"><span class="secno">2.1.2. </span><span class="bs-old-id" id="RelatedAndConsortiumMembers"></span><span class="content"> Member Associations and Related Members</span><a class="self-link" href="#RelatedAndAssociatedMembers"></a></h4>
+    <h5 class="heading settled" data-level="2.1.2.1" id="MemberAssoc"><span class="secno">2.1.2.1. </span><span class="bs-old-id" id="MemberConsortia"></span><span class="content"> Membership Associations</span><a class="self-link" href="#MemberAssoc"></a></h5>
+    <p>A “<dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Member Association | Member Associations" data-noexport id="member-association">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 <a data-link-type="dfn" href="#member-association" id="ref-for-member-association">Member Association</a> merely because it has shareholders or stockholders.
+	If it is not clear whether a prospective Member qualifies as a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association①">Member Association</a>,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo">CEO</a> may reasonably make the determination.
+	For a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association②">Member Association</a>, the rights and privileges of W3C Membership
+	described in the W3C Process Document extend to the <a data-link-type="dfn" href="#member-association" id="ref-for-member-association③">Member Association</a>’s paid staff
+	and Advisory Committee representative.</p>
+    <p><a data-link-type="dfn" href="#member-association" id="ref-for-member-association④">Member Associations</a> <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>
+    <p>For <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑤">Member Associations</a> 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.</p>
+    <p>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.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="2.1.2.2" id="MemberRelated"><span class="secno">2.1.2.2. </span><span class="content"> Related Members</span><a class="self-link" href="#MemberRelated"></a></h5>
+    <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 <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Related Member" id="related-member">related</dfn> if:</p>
+    <ol>
+     <li> Either Member is a <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary">subsidiary</a> of the other, or 
+     <li> Both Members are <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary①">subsidiaries</a> of a common entity, or 
+     <li> The Members have an employment contract or consulting contract that affects W3C participation. 
+    </ol>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="subsidiary">subsidiary</dfn> is an organization of which effective control and/or majority ownership rests with another,
+	single organization.</p>
+    <p><a data-link-type="dfn" href="#related-member" id="ref-for-related-member">Related Members</a> <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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.3" id="standing"><span class="secno">2.1.3. </span><span class="content"> Good Standing</span><a class="self-link" href="#standing"></a></h4>
+    <p><a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member">Members</a> who have not lost Good Standing as defined in the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a> are considered, for the purposes of this Process,
+	to be in <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="good-standing">Good Standing</dfn>.
+	A group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member①">related Members</a> is in Good Standing if
+	at least one of them is in Good Standing.</p>
+    <h3 class="heading settled" data-level="2.2" id="Team"><span class="secno">2.2. </span><span class="bs-old-id" id="def-Director"></span><span class="content"> The W3C Team</span><a class="self-link" href="#Team"></a></h3>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team | W3C Team" id="team">Team</dfn> consists of <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="ceo">CEO</dfn>,
+	W3C paid staff,
+	unpaid interns,
+	and W3C Fellows. <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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> <a data-link-type="biblio" href="#biblio-fellows" title="W3C Fellows Program">[FELLOWS]</a>.
+	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.</p>
+    <p>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. <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision">Team Decisions</a> derive from the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo①">CEO</a>’s authority,
+	even when they are carried out by other members of the <a data-link-type="dfn" href="#team" id="ref-for-team③">Team</a>.</p>
+    <p>Oversight over the <a data-link-type="dfn" href="#team" id="ref-for-team④">Team</a>,
+	budgeting,
+	and other business decisions,
+	is provided by the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="BoD | Board | Board of Directors | W3C Board of Directors" id="bod">W3C Board of Directors</dfn>,
+	rather than managed directly by the Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf">W3C Bylaws</a> for more details
+	on the <a data-link-type="dfn" href="#bod" id="ref-for-bod">Board</a> and overall governance of W3C.</p>
+    <h2 class="heading settled" data-level="3" id="groups"><span class="secno">3. </span><span class="content"> Groups and Participation</span><a class="self-link" href="#groups"></a></h2>
+    <p>For the purposes of this Process, a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="group" data-noexport id="w3c-group">W3C Group</dfn> is one of W3C’s <a href="#wgparticipant" id="ref-for-wgparticipant">Working Groups</a>, <a href="#igparticipant" id="ref-for-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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="participant">participant</dfn> is a member of such a group.</p>
+    <h3 class="heading settled" data-level="3.1" id="Policies"><span class="secno">3.1. </span><span class="content"> Policies for Participation in W3C Groups</span><a class="self-link" href="#Policies"></a></h3>
+    <h4 class="heading settled" data-level="3.1.1" id="ParticipationCriteria"><span class="secno">3.1.1. </span><span class="content"> Individual Participation Criteria</span><a class="self-link" href="#ParticipationCriteria"></a></h4>
+    <h5 class="heading settled" data-level="3.1.1.1" id="discipline"><span class="secno">3.1.1.1. </span><span class="content"> Expectations and Discipline</span><a class="self-link" href="#discipline"></a></h5>
+    <p>There are three qualities an individual is expected to demonstrate in order to participate in W3C:</p>
+    <ol>
+     <li> Technical competence in one’s role; 
+     <li> The ability to act fairly; 
+     <li> Social competence in one’s role. 
+    </ol>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative">Advisory Committee representatives</a> who nominate individuals from their organization for participation in W3C activities
+	are responsible for assessing and attesting to the qualities of those nominees.</p>
+    <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> <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a> and the participation requirements described in
+	“Disclosure”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. </p>
+    <p>The <a data-link-type="dfn" href="#ceo" id="ref-for-ceo②">CEO</a> <em class="rfc2119">may</em> take disciplinary action,
+	including suspending or removing for cause
+	a participant in any group (including the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group">TAG</a>)
+	if serious and/or repeated violations,
+	such as failure to meet the requirements on individual behavior of
+	(a) this process
+	and in particular the Code of Conduct, or
+	(b) the membership agreement, or
+	(c) applicable laws,
+	occur.
+	Refer to the <a href="https://www.w3.org/guide/process/suspension">Guidelines to suspend or remove participants from groups</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.2" id="coi"><span class="secno">3.1.1.2. </span><span class="content"> Conflict of Interest Policy</span><a class="self-link" href="#coi"></a></h5>
+    <p>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.</p>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑤">Team</a> <em class="rfc2119">may</em> appoint a new group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs">Chair</a> 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).</p>
+    <p>The following are some scenarios where disclosure is appropriate:</p>
+    <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>
+    <p>Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the <a data-link-type="dfn" href="#team" id="ref-for-team⑥">Team</a>.</p>
+    <p><a data-link-type="dfn" href="#team" id="ref-for-team⑦">Team</a> 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> <a data-link-type="biblio" href="#biblio-conflict-policy" title="Conflict of Interest Policy for the W3C Team">[CONFLICT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.3" id="member-rep"><span class="secno">3.1.1.3. </span><span class="content"> Individuals Representing a Member Organization</span><a class="self-link" href="#member-rep"></a></h5>
+    <p>Generally, individuals representing a Member in an official capacity within W3C
+	are employees of the Member organization.
+	However, an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①">Advisory Committee representative</a> <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.</p>
+    <p>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 <a data-link-type="dfn" href="#ceo" id="ref-for-ceo③">CEO</a> <em class="rfc2119">may</em> decline
+	to allow an individual designated by an Advisory Committee representative to participate in a group.</p>
+    <p>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>).</p>
+    <h4 class="heading settled" data-level="3.1.2" id="GeneralMeetings"><span class="secno">3.1.2. </span><span class="bs-old-id" id="EventsS"></span><span class="bs-old-id" id="GAEvents"></span><span class="content"> Meetings</span><a class="self-link" href="#GeneralMeetings"></a></h4>
+    <p>The requirements in this section apply to the official meetings of any <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group">W3C group</a>,
+	as well as to official W3C meetings with open-ended participation from the Membership and/or the public,
+	such as <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW①">Workshops</a>.</p>
+    <p>W3C distinguishes two types of meetings:</p>
+    <ol>
+     <li> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 class="dfn-paneled" data-dfn-type="dfn" data-noexport 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>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①">Chair</a> <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 <a data-link-type="dfn" href="#participant" id="ref-for-participant">participant</a>.
+	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.</p>
+    <h5 class="heading settled" data-level="3.1.2.1" id="meeting-schedules"><span class="secno">3.1.2.1. </span><span class="content"> Meeting Scheduling and Announcements</span><a class="self-link" href="#meeting-schedules"></a></h5>
+    <p>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.</p>
+    <p>The following table lists <em class="rfc2119">recommendations</em> for organizing a meeting:</p>
+    <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"><a data-link-type="dfn" href="#minutes" id="ref-for-minutes">Minutes</a> available (after) 
+       <td><span class="time-interval">two weeks</span> 
+       <td><span class="time-interval">48 hours</span> 
+    </table>
+    <p><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 <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW②">Workshops</a>,
+	shorter notice is not allowed.</p>
+    <h5 class="heading settled" data-level="3.1.2.2" id="meeting-minutes"><span class="secno">3.1.2.2. </span><span class="content"> Meeting Minutes</span><a class="self-link" href="#meeting-minutes"></a></h5>
+    <p>Groups <em class="rfc2119">should</em> take and retain <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minutes">minutes</dfn> of their meetings,
+	and <em class="rfc2119">must</em> record
+	any official <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision">group decisions</a> made during the meeting discussions.
+	Details of the discussion leading to such decisions are not required,
+	provided that the rationale for the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision①">group decision</a> is nonetheless clear.</p>
+    <h5 class="heading settled" data-level="3.1.2.3" id="meeting-recording"><span class="secno">3.1.2.3. </span><span class="content"> Meeting Recordings and Transcripts</span><a class="self-link" href="#meeting-recording"></a></h5>
+    <p>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.</p>
+    <h4 class="heading settled" data-level="3.1.3" id="tooling"><span class="secno">3.1.3. </span><span class="content"> Tooling and Archiving for Discussions and Publications</span><a class="self-link" href="#tooling"></a></h4>
+    <p>For <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group①">W3C Groups</a> 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:</p>
+    <ul>
+     <li id="report-stability"><a class="self-link" href="#report-stability"></a> 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"><a class="self-link" href="#report-accessibility"></a> 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">
+      <a class="self-link" href="#discussion-archiving"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> The lack, or loss, of such archives does not by itself
+			invalidate an otherwise-valid decision.</p>
+     <li id="tool-accessibility">
+      <a class="self-link" href="#tool-accessibility"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> If a new participant joins who cannot use the tool,
+			this can require the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②">Working Group</a> to change its tooling
+			or operate some workaround.</p>
+     <li id="where-is-your-stuff"><a class="self-link" href="#where-is-your-stuff"></a> 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>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧">Team</a> is responsible for ensuring adherence to these rules
+	and for bringing any group not in compliance into compliance.</p>
+    <h4 class="heading settled" data-level="3.1.4" id="resignation"><span class="secno">3.1.4. </span><span class="content"> Resignation from a Group</span><a class="self-link" href="#resignation"></a></h4>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑨">Team</a>,
+	the Member and their representatives
+	or the Invited Expert
+	will be deemed to have resigned from the relevant group.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪">Team</a> <em class="rfc2119">must</em> record the notification.
+	See “Exclusion and Resignation from the Working Group” in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for information about obligations remaining after resignation from certain groups.</p>
+    <h3 class="heading settled" data-level="3.2" id="AC"><span class="secno">3.2. </span><span class="content"> The Advisory Committee (AC)</span><a class="self-link" href="#AC"></a></h3>
+    <h4 class="heading settled" data-level="3.2.1" id="ac-role"><span class="secno">3.2.1. </span><span class="content"> Role of the Advisory Committee</span><a class="self-link" href="#ac-role"></a></h4>
+    <p id="ReviewAppeal"> The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee|AC" id="advisory-committee">Advisory Committee</dfn> represents
+	the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member①">Members</a> of W3C at large.
+	It is responsible for: </p>
+    <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>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> of a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision">W3C decision</a> or <a data-link-type="dfn" href="#team" id="ref-for-team①①">Team</a>’s decision.</p>
+    <p>See also the additional roles of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③">Advisory Committee representatives</a> described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h4 class="heading settled" data-level="3.2.2" id="ac-participation"><span class="secno">3.2.2. </span><span class="content"> Participation in the Advisory Committee</span><a class="self-link" href="#ac-participation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①">Advisory Committee</a> is composed of one <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee representative| AC representative" id="advisory-committee-representative">representative</dfn> from each Member organization
+	(refer to the <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①②">Member-only</a> list
+	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. <a data-link-type="biblio" href="#biblio-current-ac" title="Current Advisory Committee representatives (Member-only access)">[CURRENT-AC]</a>)</p>
+    <p>When an organization joins W3C
+	(see “<a href="https://www.w3.org/membership/join/">How to Join W3C</a>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>),
+	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of their Membership Agreement.
+	The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a> 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 <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative④">Advisory Committee representative</a>,
+	and more. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑤">Advisory Committee representatives</a> <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.</p>
+    <p>The AC representative may delegate any of their rights and responsibilities
+	to an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="alternate AC representative | alternate Advisory Committee representative | alt AC rep" id="alternate-ac-representative">alternate</dfn> (except the ability to designate an alternate).</p>
+    <h4 class="heading settled" data-level="3.2.3" id="ACCommunication"><span class="secno">3.2.3. </span><span class="content"> Advisory Committee Mailing Lists</span><a class="self-link" href="#ACCommunication"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②">Team</a> <em class="rfc2119">must</em> provide two mailing lists for use by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②">Advisory Committee</a>:</p>
+    <ol>
+     <li> One for official announcements (e.g., those required by this document) from the <a data-link-type="dfn" href="#team" id="ref-for-team①③">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③">Advisory Committee</a>.
+			This list is read-only for Advisory Committee representatives. 
+     <li> One for discussion among <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑥">Advisory Committee representatives</a>.
+			Though this list is primarily for Advisory Committee representatives,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①④">Team</a> <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>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑦">Advisory Committee representative</a> <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.</p>
+    <h4 class="heading settled" data-level="3.2.4" id="ACMeetings"><span class="secno">3.2.4. </span><span class="content"> Advisory Committee Meetings</span><a class="self-link" href="#ACMeetings"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑤">Team</a> organizes a <a href="#ftf-meeting" id="ref-for-ftf-meeting">face-to-face meeting</a> for the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④">Advisory Committee</a> <span class="time-interval">twice a year</span>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⑥">Team</a> 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:</p>
+    <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>
+    </dl>
+    <p>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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑦">Team</a> <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.</p>
+    <p>More information about <a href="https://www.w3.org/events/ac/">Advisory Committee meetings</a> <a data-link-type="biblio" href="#biblio-ac-meeting" title="Advisory Committee meetings (Member-only access)">[AC-MEETING]</a> is available at the Member website.</p>
+    <h3 class="heading settled" data-level="3.3" id="elected-groups"><span class="secno">3.3. </span><span class="content"> Elected Groups: The AB and the TAG</span><a class="self-link" href="#elected-groups"></a></h3>
+    <p>The W3C Process defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="elected-group">elected groups</dfn>:
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①">Advisory Board</a> (AB) and
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①">Technical Architecture Group</a> (TAG),
+	both elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑤">Advisory Committee</a>.</p>
+    <h4 class="heading settled" data-level="3.3.1" id="AB"><span class="secno">3.3.1. </span><span class="content"> Advisory Board (AB)</span><a class="self-link" href="#AB"></a></h4>
+    <h5 class="heading settled" data-level="3.3.1.1" id="ab-role"><span class="secno">3.3.1.1. </span><span class="content"> Role of the Advisory Board</span><a class="self-link" href="#ab-role"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Board|AB" id="advisory-board">Advisory Board</dfn> 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>.
+	As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council">W3C Council</a>,
+	members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②">Advisory Board</a> hear and adjudicate on <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③">Advisory Board</a> is distinct from the <a data-link-type="dfn" href="#bod" id="ref-for-bod①">Board of Directors</a> and has no decision-making authority within W3C;
+	its role is strictly advisory.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> While the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board④">AB</a> as such does not have decision-making authority,
+	its members do when sitting as part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①">W3C Council</a>.</p>
+    <p>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> <a data-link-type="biblio" href="#biblio-ab-hp" title="The Advisory Board home page">[AB-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.1.2" id="ABParticipation"><span class="secno">3.3.1.2. </span><span class="content"> Composition of the Advisory Board</span><a class="self-link" href="#ABParticipation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑤">Advisory Board</a> 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 <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑥">AB</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⑧">Team</a> 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.</p>
+    <p>The team also appoints a <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact">Staff Contact</a>,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.
+	The CEO and Staff Contact have a standing invitation
+	to all regular Advisory Board sessions.</p>
+    <p>The nine to eleven <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑦">Advisory Board</a> participants are elected by the W3C <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑥">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="3.3.1.3" id="ab-comm"><span class="secno">3.3.1.3. </span><span class="content"> Communications of the Advisory Board</span><a class="self-link" href="#ab-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑨">Team</a> <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.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑧">Advisory Board</a> <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>.</p>
+    <h5 class="heading settled" data-level="3.3.1.4" id="ab-bod-liaison"><span class="secno">3.3.1.4. </span><span class="content"> Liaisons between the Advisory Board and the Board of Directors</span><a class="self-link" href="#ab-bod-liaison"></a></h5>
+    <p>To ensure good communication between the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑨">AB</a> and the <a data-link-type="dfn" href="#bod" id="ref-for-bod②">Board of Directors</a> and facilitate operational and management consistency,
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⓪">AB</a> <em class="rfc2119">may</em> appoint up to two of its participants as liaisons to the <a data-link-type="dfn" href="#bod" id="ref-for-bod③">Board</a>.
+	Such appointees are expected to attend and participate in <a data-link-type="dfn" href="#bod" id="ref-for-bod④">Board</a> meetings
+	and access <a data-link-type="dfn" href="#bod" id="ref-for-bod⑤">Board</a> materials
+	as Non-voting Observers. <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a> They do not form part of the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑥">Board</a>’s decision-making body,
+	and may be excluded from such participation
+	in accordance with applicable Board procedures.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①①">Advisory Board</a> <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.</p>
+    <h4 class="heading settled" data-level="3.3.2" id="TAG"><span class="secno">3.3.2. </span><span class="content"> Technical Architecture Group (TAG)</span><a class="self-link" href="#TAG"></a></h4>
+    <h5 class="heading settled" data-level="3.3.2.1" id="tag-role"><span class="secno">3.3.2.1. </span><span class="content"> Role of the Technical Architecture Group</span><a class="self-link" href="#tag-role"></a></h5>
+    <p>The mission of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Technical Architecture Group|TAG" id="technical-architecture-group">TAG</dfn> is stewardship of the Web architecture.
+	There are three aspects to this mission:</p>
+    <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> to help coordinate cross-technology architecture developments inside and outside W3C. 
+    </ol>
+    <p>As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②">W3C Council</a>,
+	the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②">TAG</a> hear and adjudicate on <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals①">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③">TAG</a>’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.</p>
+    <p>When the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④">TAG</a> votes to resolve an issue,
+	each TAG participant
+	(whether appointed, elected, or the Chair)
+	has one vote;
+	see also the general section on <a href="#Votes">votes</a> in this Process Document.</p>
+    <p>Details about the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑤">TAG</a> (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings)
+	are available at the <a href="https://www.w3.org/2001/tag/">TAG home page</a> <a data-link-type="biblio" href="#biblio-tag-hp" title="The TAG home page">[TAG-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.2.2" id="tag-participation"><span class="secno">3.3.2.2. </span><span class="content"> Composition of the Technical Architecture Group</span><a class="self-link" href="#tag-participation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑥">TAG</a> consists of:</p>
+    <ul>
+     <li> Tim Berners-Lee, who is a life member; 
+     <li> Three participants <a href="#TAG-appointments">appointed by the Team</a>; 
+     <li> Eight participants elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑦">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>. 
+    </ul>
+    <p>Participants in the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑦">TAG</a> choose by consensus their Chair or co-Chairs;
+	in the absence of consensus, the <a data-link-type="dfn" href="#team" id="ref-for-team②⓪">Team</a> appoints the Chair or co-Chairs of the TAG.
+	The Chair or co-Chairs <em class="rfc2119">must</em> be selected from the participants of the TAG.
+	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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②①">Team</a> also appoints a <a href="https://www.w3.org/guide/teamcontact/role">Staff Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> for the TAG,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.</p>
+    <p>The terms of TAG participants last for <span class="time-interval">two years</span>.
+	Terms are staggered so that four elected terms
+	and either one or two appointed terms expire each year.
+	If an individual is appointed or elected to fill an incomplete term,
+	that individual’s term ends at the normal expiration date of that term.
+	Regular TAG terms begin on 1 February and end on 31 January.</p>
+    <h5 class="heading settled" data-level="3.3.2.3" id="tag-comm"><span class="secno">3.3.2.3. </span><span class="content"> Communications of the Technical Architecture Group</span><a class="self-link" href="#tag-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②②">Team</a> <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
+    <ul>
+     <li> a public discussion (not just input) list for issues of Web architecture.
+			The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑧">TAG</a> will conduct its public business on this list. 
+     <li> a <a href="#Member-only" id="ref-for-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. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑨">TAG</a> <em class="rfc2119">may</em> also request the creation of additional topic-specific, public mailing lists.
+	For some TAG discussions (e.g.,  a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals②">Submission Appeal</a>),
+	the TAG <em class="rfc2119">may</em> use a list that will be <a href="#Member-only" id="ref-for-Member-only①④">Member-only</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⓪">TAG</a> <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 <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①①">TAG</a> <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
+    <h4 class="heading settled" data-level="3.3.3" id="AB-TAG-participation"><span class="secno">3.3.3. </span><span class="content"> Participation in Elected Groups</span><a class="self-link" href="#AB-TAG-participation"></a></h4>
+    <h5 class="heading settled" data-level="3.3.3.1" id="elected-expectations"><span class="secno">3.3.3.1. </span><span class="content"> Expectations for Elected Groups Participants</span><a class="self-link" href="#elected-expectations"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①②">Advisory Board</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①②">TAG</a> participants have a special role within W3C:
+	they are elected by the Membership and appointed by the <a data-link-type="dfn" href="#team" id="ref-for-team②③">Team</a> with the expectation that they will use their best judgment
+	to find the best solutions for the Web,
+	not just for any particular network,
+	technology,
+	vendor,
+	or user.
+	Advisory Board and TAG participants are expected to participate regularly and fully.
+	Advisory Board and TAG participants <em class="rfc2119">should</em> attend <a href="#ACMeetings">Advisory Committee meetings</a>.</p>
+    <p>Individuals elected or appointed to the Advisory Board or TAG act in their personal capacity,
+	to serve the needs of the W3C membership as a whole,
+	and the Web community.
+	Whether they are Member representatives or Invited Experts,
+	their activities in those roles are separate and distinct from their activities on the Advisory Board or TAG.</p>
+    <p>An individual participates on the Advisory Board or TAG
+	from the moment the individual’s term begins until the seat is <a href="#AB-TAG-vacated">vacated</a> (e.g. because the term ends).
+	Although Advisory Board and TAG participants do not advocate for the commercial interests of their employers,
+	their participation does carry the responsibilities associated with Member representation,
+	Invited Expert status,
+	or Team representation
+	(as described in the section on the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>).</p>
+    <p>Participation in the TAG or AB is afforded to the specific individuals elected or appointed to those positions,
+	and a participant’s seat <em class="rfc2119">must not</em> be delegated to any other person.</p>
+    <h5 class="heading settled" data-level="3.3.3.2" id="AB-TAG-constraints"><span class="secno">3.3.3.2. </span><span class="content"> Elected Groups Participation Constraints</span><a class="self-link" href="#AB-TAG-constraints"></a></h5>
+    <p>Given the few seats available on the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①③">Advisory Board</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①③">TAG</a>,
+	and in order to ensure that the diversity of W3C Members is represented:</p>
+    <ul>
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the TAG
+			except when this is caused by a change of affiliation of an existing participant.
+			At the completion of the next regularly scheduled election for the TAG,
+			the organization <em class="rfc2119">must</em> have returned to having at most one seat. 
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation①">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the AB.
+			If, for whatever reason, these constraints are not satisfied
+			(e.g., because an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①④">AB</a> participant changes jobs),
+			one participant <em class="rfc2119">must</em> cease <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑤">AB</a> participation
+			until the situation has been resolved.
+			If after <span class="time-interval">30 days</span> the situation has not been resolved,
+			the Chair will apply
+			the <a href="#random">verifiable random selection procedure</a> described below
+			to choose one person for continued participation and declare the other seat(s) vacant. 
+     <li> An individual <em class="rfc2119">must not</em> participate on both the TAG and the AB. 
+    </ul>
+    <h5 class="heading settled" data-level="3.3.3.3" id="AB-TAG-elections"><span class="secno">3.3.3.3. </span><span class="content"> Advisory Board and Technical Architecture Group Elections</span><a class="self-link" href="#AB-TAG-elections"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑥">Advisory Board</a> and a portion of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①④">Technical Architecture Group</a> are elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑧">Advisory Committee</a>,
+	using a Single Transferable Vote system.
+	An election begins when the Team sends a Call for Nominations to the Advisory Committee.
+	Any Call for Nominations specifies the minimum and maximum number of available seats,
+	the deadline for nominations,
+	details about the specific vote tabulation system selected by the Team for the election,
+	and operational information such as how to nominate a candidate.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②④">Team</a> <em class="rfc2119">may</em> modify the tabulation system after the Call for Nominations
+	but <em class="rfc2119">must</em> stabilize it no later than the Call for Votes.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②⑤">Team</a> announces appointments
+	after the results of the election are known,
+	and before the start of the term,
+	as described in <a href="#TAG-appointments">§ 3.3.3.4 Technical Architecture Group Appointments</a>.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑤">TAG</a>,
+	the minimum and maximum number of available seats are the same:
+	the 4 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑦">AB</a>,
+	the minimum and maximum number of available seats differ:
+	The maximum number is the 5 or 6 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats;
+	the minimum number is such that when added to the occupied seats from the prior year,
+	the minimum size of the AB (9) is reached.</p>
+    <p>Each Member (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member②">related Members</a>) <em class="rfc2119">may</em> nominate one individual.
+	A nomination <em class="rfc2119">must</em> be made with the consent of the nominee.
+	In order for an individual to be nominated as a Member representative,
+	the individual <em class="rfc2119">must</em> qualify for <a href="#member-rep">Member representation</a> and the Member’s <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑧">Advisory Committee representative</a> <em class="rfc2119">must</em> include in the nomination
+	the (same) <a href="#member-rep-info">information required for a Member representative in a Working Group</a>.
+	In order for an individual to be nominated as an Invited Expert,
+	the individual <em class="rfc2119">must</em> provide
+	the (same) <a href="#inv-expert-info" id="ref-for-inv-expert-info">information required for an Invited Expert in a Working Group</a> and the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑨">Advisory Committee representative</a> <em class="rfc2119">must</em> include that information in the nomination.
+	In order for an individual to be nominated as a <a data-link-type="dfn" href="#team" id="ref-for-team②⑥">Team</a> representative,
+	the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⓪">Advisory Committee representative</a> <em class="rfc2119">must</em> first secure approval from <a data-link-type="dfn" href="#team" id="ref-for-team②⑦">Team</a> management.
+	A nominee is <em class="rfc2119">not required</em> to be an employee of a Member organization,
+	and <em class="rfc2119">may</em> be a <a href="#fellows" id="ref-for-fellows①">W3C Fellow</a>.
+	The nomination form <em class="rfc2119">must</em> ask for the nominee’s <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation②">primary affiliation</a>,
+	and this will be reported on the ballot.
+	For most nominees,
+	the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="primary-affiliation">primary affiliation</dfn> is their employer and will match their affiliation in the W3C database.
+	For contractors and invited experts,
+	this will normally be their contracting company
+	or their invited expert status;
+	in some cases
+	(e.g. where a consultant is consulting for only one organization)
+	this <em class="rfc2119">may</em> be the organization for whom the nominee is consulting.
+	A <a href="#AB-TAG-constraints">change of affiliation</a> is defined
+	such that this field would carry a different answer
+	if the nominee were to be re-nominated
+	(therefore,
+	terminating employment,
+	or accepting new employment,
+	are changes of affiliation).
+	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
+	Each nomination <em class="rfc2119">should</em> include
+	a few informative paragraphs about the nominee.
+	If an identified candidate’s nomination information is only partially complete
+	as of the deadline for nominations,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team②⑧">Team</a> <em class="rfc2119">may</em> allow extra time for that candidate’s nomination to be completed,
+	so long as it does not delay the election as a whole.</p>
+    <p>If, after the deadline for nominations, the number of nominees is:</p>
+    <ul>
+     <li> Greater than or equal to the minimum number of available seats
+			and less than or equal to the maximum number of available seats,
+			those nominees are thereby elected.
+			This situation constitutes a tie for the purpose of assigning <a href="#short-term">incomplete terms</a>.
+			Furthermore, if the number is less than the maximum number of available seats,
+			the longest terms are filled first. 
+     <li> Less than the minimum number of available seats,
+			Calls for Nominations are issued until a sufficient number of people have been nominated.
+			Those already nominated do not need to be renominated after a renewed call. 
+     <li> Greater than the maximum number of available seats,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team②⑨">Team</a> issues a Call for Votes
+			that includes the names of all candidates,
+			the (maximum) number of available seats,
+			the deadline for votes,
+			details about the vote tabulation system selected by the Team for the election,
+			and operational information. 
+    </ul>
+    <p>When there is a vote,
+	each Member in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing">Good Standing</a> (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member③">related Members</a>) <em class="rfc2119">may</em> submit one ballot that ranks candidates in the Member’s preferred order.
+	Once the deadline for votes has passed,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⓪">Team</a> announces the results to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑨">Advisory Committee</a>.
+	In case of a tie the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to fill the available seats.</p>
+    <p id="short-term">The shortest incomplete term is assigned to the elected candidate ranked lowest by the tabulation of votes,
+	the next shortest term to the next-lowest ranked elected candidate,
+	and so on.
+	In the case of a tie among those eligible for a incomplete term,
+	the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to assign the incomplete term. </p>
+    <p>Refer to <a href="https://www.w3.org/guide/process/election">How to Organize an Advisory Board or TAG election</a> <a data-link-type="biblio" href="#biblio-election-howto" title="How to Organize an Advisory Board or TAG election">[ELECTION-HOWTO]</a> for more details.</p>
+    <h5 class="heading settled" data-level="3.3.3.4" id="TAG-appointments"><span class="secno">3.3.3.4. </span><span class="content"> Technical Architecture Group Appointments</span><a class="self-link" href="#TAG-appointments"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③①">Team</a> is responsible for appointing
+	3 of the participants to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑥">Technical Architecture Group</a>.
+	This mechanism complements the election process.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③②">Team</a> <em class="rfc2119">should</em> use its appointments to support
+	a diverse and well-balanced <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑦">TAG</a>,
+	including diversity of technical background, knowledge, and skill sets.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③③">Team</a> <em class="rfc2119">should</em> actively seek
+	candidates for appointment to the TAG,
+	and <em class="rfc2119">must</em> make available to
+	the W3C community at large
+	a means to propose candidates for consideration,
+	explicitly soliciting input from at least
+	current and incoming <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑧">TAG</a> members, the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⓪">Advisory Committee</a>, and <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②">Chairs</a>.</p>
+    <p>The constraints for appointment to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑨">TAG</a> are
+	the same as for elected participants
+	(see <a href="#AB-TAG-constraints">§ 3.3.3.2 Elected Groups Participation Constraints</a> and <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a>),
+	with the additional constraint that
+	a person <em class="rfc2119">must not</em> be appointed
+	for more than two <em>consecutive</em> terms.
+	(Partial terms used to fill a vacated seat do not count towards this limit.)</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since there are no limits on elected terms,
+	this limit on appointed terms does not constrain
+	term-limited appointees
+	from running for election at any time.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③④">Team</a>’s choice of appointee(s)
+	is subject to ratification by secret ballot
+	by both the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑧">AB</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⓪">TAG</a>,
+	requiring a two-thirds approval from each.
+	In the case of regularly scheduled elections,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②①">TAG</a> participants in this ratification are
+	its members for the upcoming term.</p>
+    <p>For regularly scheduled elections,
+	selection begins once the results of the elections are known,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team③⑤">Team</a> <em class="rfc2119">should</em> announce the ratified appointment(s)
+	no later than the start of the regularly scheduled term.
+	When an appointed seat is vacated outside of a regularly scheduled election,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⑥">Team</a> <em class="rfc2119">should</em> seek to appoint a replacement
+	unless a regular Call for Nominations is scheduled within 2 months,
+	and it <em class="rfc2119">must</em> announce the ratified appointment
+	no later than the Call for Nominations of the next scheduled election.</p>
+    <h5 class="heading settled" data-level="3.3.3.5" id="random"><span class="secno">3.3.3.5. </span><span class="content"> Verifiable Random Selection Procedure</span><a class="self-link" href="#random"></a></h5>
+    <p>When it is necessary to use a verifiable random selection process
+	(e.g., in an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑨">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②②">TAG</a> election,
+	to “draw straws” in case of a tie
+	or to fill a incomplete term),
+	W3C uses the random and verifiable procedure defined in <a href="https://www.ietf.org/rfc/rfc3797.txt">RFC 3797</a> <a data-link-type="biblio" href="#biblio-rfc3797" title="Publicly Verifiable Nominations Committee (NomCom) Random Selection">[RFC3797]</a>.
+	The procedure orders an input list of names
+	(listed in alphabetical order by family name unless otherwise specified)
+	into a “result order”.</p>
+    <p>W3C applies this procedure as follows:</p>
+    <ol>
+     <li> When N people have tied for M (less than N) seats.
+			In this case, only the names of the N individuals who tied
+			are provided as input to the procedure.
+			The M seats are assigned in result order. 
+     <li> After all elected individuals have been identified,
+			when N people are eligible for M (less than N) incomplete terms.
+			In this case, only the names of those N individuals are provided as input to the procedure.
+			The incomplete terms are assigned in result order. 
+    </ol>
+    <h5 class="heading settled" data-level="3.3.3.6" id="AB-TAG-vacated"><span class="secno">3.3.3.6. </span><span class="content"> Elected Groups Vacated Seats</span><a class="self-link" href="#AB-TAG-vacated"></a></h5>
+    <p>An <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⓪">Advisory Board</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②③">TAG</a> participant’s seat is vacated when:</p>
+    <ul>
+     <li> the participant resigns, or 
+     <li> an Advisory Board or TAG participant changes affiliations
+			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
+			or 
+     <li> the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo④">CEO</a> dismisses the participant
+			for failing to meet the criteria in section <a href="#ParticipationCriteria">§ 3.1.1 Individual Participation Criteria</a>,
+			or 
+     <li> their term ends. 
+    </ul>
+    <p>If a participant changes affiliation,
+	but the <a href="#AB-TAG-constraints">participation constraints</a> are met,
+	that participant’s seat becomes vacant at the next regularly scheduled election for that group.</p>
+    <p>Vacated seats are filled according to this schedule:</p>
+    <ul>
+     <li> When an appointed <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②④">TAG</a> seat is vacated,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team③⑦">Team</a> <a href="#TAG-appointments">appoints</a> a replacement. 
+     <li>
+       When an elected seat on either the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②①">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑤">TAG</a> is vacated,
+			the seat is filled at the next regularly scheduled election for the group
+			unless the group Chair requests that W3C hold an election before then
+			(for instance, due to the group’s workload). 
+      <ul>
+       <li> The group Chair <em class="rfc2119">should not</em> request such an election
+					if the next regularly scheduled election is fewer than three months away. 
+       <li> The group Chair <em class="rfc2119">may</em> request an election,
+					and the election may begin, as soon as a current member gives notice of a resignation,
+					including a resignation effective as of a given date in the future. 
+      </ul>
+      <p>When such an election is held,
+			the minimum number of available seats is such that
+			when added to the number of continuing participants,
+			the minimum total number of elected seats is met
+			(8 for the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑥">TAG</a>, 9 for the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②②">AB</a>);
+			and the maximum number corresponds to all unoccupied seats.
+			Except for the number of available seats and the length of the terms,
+			the <a href="#AB-TAG-elections">usual rules for Advisory Board and Technical Architecture Group Elections</a> apply.</p>
+    </ul>
+    <h3 class="heading settled" data-level="3.4" id="GAGeneral"><span class="secno">3.4. </span><span class="bs-old-id" id="WG-and-IG"></span><span class="bs-old-id" id="ChapterGroups"></span><span class="content"> Chartered Groups: Working Groups and Interest Groups</span><a class="self-link" href="#GAGeneral"></a></h3>
+    <p id="GAGroups">This document defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chartered-group">chartered groups</dfn>: </p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsWG"><a href="#GroupsWG" id="ref-for-GroupsWG⑦⑦">Working Groups</a></dfn>. 
+     <dd>
+       Working Groups typically produce deliverables
+			(e.g., <a href="#rec-advance">Recommendation Track technical reports</a>,
+			software,
+			test suites,
+			and reviews of the deliverables of other groups)
+			as defined in their <a href="#WGCharter">charter</a>. 
+      <p>Working Groups have additional participation requirements
+			described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			see particularly the “<a href="https://www.w3.org/policies/patent-policy/#sec-Obligations">Licensing Obligations of Working Group Participants</a>”
+			and the patent claim exclusion process
+			in “<a href="https://www.w3.org/policies/patent-policy/#sec-Exclusion">Exclusion From W3C RF Licensing Requirements</a>”.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsIG"><a href="#GroupsIG" id="ref-for-GroupsIG①③">Interest Groups</a></dfn>. 
+     <dd>
+       The primary goal of an Interest Group
+			is to bring together people who wish to evaluate potential Web technologies and policies.
+			An Interest Group is a forum for the exchange of ideas. 
+      <p>Interest Groups do not publish <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑤">Recommendation Track technical reports</a>;
+			but can publish <a href="#WGNote" id="ref-for-WGNote">technical reports on the Note Track</a>.</p>
+    </dl>
+    <h4 class="heading settled" data-level="3.4.1" id="ReqsAllGroups"><span class="secno">3.4.1. </span><span class="content"> Requirements for All Chartered Groups</span><a class="self-link" href="#ReqsAllGroups"></a></h4>
+    <p>Each group <em class="rfc2119">must</em> have a <a data-link-type="dfn" href="#charter" id="ref-for-charter">charter</a>.
+	Requirements for the charter depend on the group type.
+	All group charters <em class="rfc2119">must</em> be public
+	(even if other proceedings of the group are <a href="#Member-only" id="ref-for-Member-only①⑤">Member-only</a>).</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GeneralChairs">Chair</dfn> (or co-Chairs)
+	to facilitate effective discussion and coordinate the group’s activities.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③⑧">Team</a> appoints (and re-appoints) Chairs for all groups.
+	The Chair is a <a href="#member-rep">Member representative</a>,
+	a <a href="#Team">Team representative</a>,
+	or an <a href="#invited-expert-wg">Invited Expert</a> (invited by the <a data-link-type="dfn" href="#team" id="ref-for-team③⑨">Team</a>).
+	The requirements of this document that apply to those types of participants apply to Chairs as well.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/guide/chair/role">role of the Chair</a> <a data-link-type="biblio" href="#biblio-chair" title="W3C Working/Interest Group Chair">[CHAIR]</a> is described
+	in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="TeamContact">Staff Contact</dfn> (also known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-contact">Team Contact</dfn>),
+	who acts as the interface between the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③">Chair</a>,
+	group participants,
+	and the rest of the Team.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/guide/teamcontact/role">role of the Staff Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> is described in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs④">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①">Staff Contact</a> of a group <em class="rfc2119">should not</em> be the same individual.</p>
+    <p>Each group <em class="rfc2119">must</em> have an archived mailing list
+	for formal group communication
+	(e.g., for meeting announcements and <a data-link-type="dfn" href="#minutes" id="ref-for-minutes①">minutes</a>,
+	documentation of decisions,
+	and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②">Formal Objections</a> to decisions).
+	It is the responsibility of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑤">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact②">Staff Contact</a> to ensure that new participants are subscribed to all relevant mailing lists.
+	Refer to the list of <a href="https://www.w3.org/groups/">group mailing lists</a> <a data-link-type="biblio" href="#biblio-group-mail" title="Group mailing lists">[GROUP-MAIL]</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑥">Chair</a> <em class="rfc2119">may</em> form task forces
+	(composed of group participants)
+	to carry out assignments for the group.
+	The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group’s charter.
+	A group <em class="rfc2119">should</em> document the process it uses
+	to create task forces
+	(e.g., each task force might have an informal "charter").
+	Task forces do not publish <a href="#Reports">technical reports</a>;
+	the Working Group <em class="rfc2119">may</em> choose to publish their results as part of a technical report. </p>
+    <h4 class="heading settled" data-level="3.4.2" id="group-participation"><span class="secno">3.4.2. </span><span class="content"> Participation in Chartered Groups</span><a class="self-link" href="#group-participation"></a></h4>
+    <p>There are three types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="wgparticipant">participants in a Working Group</dfn>: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
+	and <a href="#Team">Team representatives</a> (including the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact③">Staff Contact</a>).</p>
+    <p>There are four types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="igparticipant">participants in an Interest Group</dfn>:
+	the same three types as for Working Groups plus,
+	for an Interest Group where the only <a href="#ig-mail-only">participation requirement is mailing list subscription</a>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="public-participant-ig">public participants</dfn>.</p>
+    <p>Except where noted in this document or in a group charter,
+	all participants share the same rights and responsibilities in a group;
+	see also the <a href="#ParticipationCriteria">individual participation criteria</a>.</p>
+    <p>A participant <em class="rfc2119">may</em> represent more than one organization
+	in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①">Interest Group</a>.
+	Those organizations <em class="rfc2119">must</em> all be members of the group.</p>
+    <p>An individual <em class="rfc2119">may</em> become
+	a Working or Interest Group participant
+	at any time during the group’s existence.
+	See also relevant requirements in
+	“Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>On an exceptional basis,
+	a Working or Interest Group participant <em class="rfc2119">may</em> designate
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mtg-substitute">substitute</dfn> to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑦">Chair</a>.
+	The substitute <em class="rfc2119">may</em> act on behalf of the participant,
+	including for <a href="#Votes">votes</a>.
+	For the substitute to vote,
+	the participant <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑧">Chair</a> in writing in advance.</p>
+    <p>To allow rapid progress,
+	Working Groups are intended to be small
+	(typically fewer than 15 people)
+	and composed of experts in the area defined by the charter.
+	In principle,
+	Interest Groups have no limit on the number of participants.
+	When a Working Group grows too large to be effective,
+	W3C <em class="rfc2119">may</em> split it into an Interest Group
+	(a discussion forum)
+	and a much smaller Working Group
+	(a core group of highly dedicated participants).</p>
+    <h4 class="heading settled" data-level="3.4.3" id="chartered-group-participants"><span class="secno">3.4.3. </span><span class="content"> Types of Participants in Chartered Groups</span><a class="self-link" href="#chartered-group-participants"></a></h4>
+    <h5 class="heading settled" data-level="3.4.3.1" id="member-rep-wg"><span class="secno">3.4.3.1. </span><span class="content"> Member Representative in a Working Group</span><a class="self-link" href="#member-rep-wg"></a></h5>
+    <p>An individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-a-working-group">Member representative in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Advisory Committee representative of the Member in question
+			has designated the individual as a Working Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a Member representative in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤">Working Group</a>,
+	an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①①">Advisory Committee representative</a> <em class="rfc2119">must</em> provide the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑨">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact④">Staff Contact</a> with all of the following <span id="member-rep-info">information</span>,
+	in addition to any other information required by the <a href="#cfp">Call for Participation</a> and charter
+	(including the participation requirements of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>):</p>
+    <ol>
+     <li> The name of the W3C Member the individual represents
+			and whether the individual is an employee of that Member organization; 
+     <li> A statement that the individual accepts the participation terms
+			set forth in the charter
+			(with an indication of charter date or version); 
+     <li> A statement that the Member will provide the necessary financial support for participation
+			(e.g., for travel, telephone calls, and conferences). 
+    </ol>
+    <p>A Member participates in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥">Working Group</a> from the moment the first Member representative joins the group
+	until either of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Member <a href="#resignation">resigns</a> from the Working Group;
+			this is done through the Member’s Advisory Committee representative. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.2" id="member-rep-ig"><span class="secno">3.4.3.2. </span><span class="content"> Member Representative in an Interest Group</span><a class="self-link" href="#member-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-an-interest-group">Member representative in an Interest Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①②">Advisory Committee representative</a> of the Member in question has designated the individual
+			as an Interest Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a <a data-link-type="dfn" href="#member-representative-in-an-interest-group" id="ref-for-member-representative-in-an-interest-group">Member representative in an Interest Group</a>,
+	the Advisory Committee representative <em class="rfc2119">must</em> follow the instructions
+	in the <a href="#cfp">Call for Participation</a> and charter.</p>
+    <p>Member participation in an Interest Group ceases under the same conditions as for a Working Group.</p>
+    <h5 class="heading settled" data-level="3.4.3.3" id="invited-expert-wg"><span class="secno">3.4.3.3. </span><span class="content"> Invited Expert in a Working Group</span><a class="self-link" href="#invited-expert-wg"></a></h5>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⓪">Chair</a> <em class="rfc2119">may</em> invite an individual with a particular expertise
+	to participate in a Working Group.
+	This individual <em class="rfc2119">may</em> represent an organization in the group
+	(e.g., if acting as a liaison with another organization).</p>
+    <p>An individual is an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-a-working-group">Invited Expert in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Chair has designated the individual as a group participant, 
+     <li> the Staff Contact has agreed with the Chair’s choice, and 
+     <li> the individual has provided the <a href="#inv-expert-info" id="ref-for-inv-expert-info①">information required of an Invited Expert</a> to the Chair and Staff Contact. 
+    </ul>
+    <p>To designate an individual as an Invited Expert in a Working Group,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①①">Chair</a> <em class="rfc2119">must</em> inform the Staff Contact
+	and provide rationale for the choice.
+	When the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①②">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑤">Staff Contact</a> disagree about a designation,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑤">CEO</a> determines
+	whether the individual will be invited to participate in the Working Group.</p>
+    <p>To <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="inv-expert-info">participate in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦">Working Group</a> as an Invited Expert</dfn>,
+	an individual <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> identify the organization, if any, the individual represents as a participant in this group, 
+     <li> agree to the terms of the <a href="https://www.w3.org/invited-experts/agreement-2023/">invited expert and collaborators agreement</a> <a data-link-type="biblio" href="#biblio-collaborators-agreement" title="Invited expert and collaborators agreement">[COLLABORATORS-AGREEMENT]</a>, 
+     <li> accept the participation terms set forth in the charter,
+			including the participation requirements of
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			especially in “Note on Licensing Commitments for Invited Experts”
+			and in “Disclosure”,
+			indicating a specific charter date or version, 
+     <li> disclose whether the individual is an employee of a W3C Member;
+			see the <a href="#coi">conflict of interest policy</a>, 
+     <li> provide a statement of who will provide the necessary financial support
+			for the individual’s participation
+			(e.g., for travel, telephone calls, and conferences), and 
+     <li> if the individual’s employer (including a self-employed individual)
+			or the organization the individual represents
+			is not a W3C Member,
+			indicate whether that organization intends to join W3C.
+			If the organization does not intend to join W3C,
+			indicate reasons the individual is aware of for this choice. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①③">Chair</a> <em class="rfc2119">should not</em> designate as an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group">Invited Expert in a Working Group</a> an individual who is an employee of a W3C Member.
+	The Chair <em class="rfc2119">must not</em> use Invited Expert status
+	to circumvent participation limits imposed by the <a href="#WGCharter">charter</a>.</p>
+    <p>An Invited Expert participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Chair or <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑥">CEO</a> withdraws the invitation to participate, or 
+     <li> the individual <a href="#resignation">resigns</a>. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.4" id="invited-expert-ig"><span class="secno">3.4.3.4. </span><span class="content"> Invited Expert in an Interest Group</span><a class="self-link" href="#invited-expert-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	the participation requirements for an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-an-interest-group">Invited Expert in an Interest Group</dfn> are the same as those for an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group①">Invited Expert in a Working Group</a>.</p>
+    <h5 class="heading settled" data-level="3.4.3.5" id="team-rep-wg"><span class="secno">3.4.3.5. </span><span class="content"> Team Representative in a Working Group</span><a class="self-link" href="#team-rep-wg"></a></h5>
+    <p>An individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-representative-in-a-working-group">Team representative in a Working Group</dfn> when so designated by W3C management.
+	Team representatives both contribute to the technical work
+	and help ensure the group’s proper integration with the rest of W3C.</p>
+    <p>A Team representative participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> W3C management changes Team representation by sending email to the Chair,
+			copying the group mailing list. 
+    </ul>
+    <p>The Team participates in a Working Group
+	from the moment the creation of the group is announced
+	until the group closes.</p>
+    <h5 class="heading settled" data-level="3.4.3.6" id="team-rep-ig"><span class="secno">3.4.3.6. </span><span class="content"> Team Representative in an Interest Group</span><a class="self-link" href="#team-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-representative-in-an-interest-group">Team representative in an Interest Group</dfn> when so designated by W3C management.</p>
+    <h2 class="heading settled" data-level="4" id="group-lifecycle"><span class="secno">4. </span><span class="content"> Lifecycle of Chartered Groups</span><a class="self-link" href="#group-lifecycle"></a></h2>
+    <p>W3C creates <a data-link-type="dfn" href="#charter" id="ref-for-charter①">charters</a> for <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group">chartered groups</a> based on W3C community interest.
+	W3C fosters awareness of <a data-link-type="dfn" href="#charter" id="ref-for-charter②">charters</a>,
+	improves their quality,
+	and gauges Membership support in two formal phases:</p>
+    <ul>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement">refinement</a> phase helps ensure <a data-link-type="dfn" href="#charter" id="ref-for-charter③">charters</a> are mission-aligned,
+reflect community input and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus">consensus</a>,
+and have been well-socialized
+and <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review">widely reviewed</a>.</p>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#charter" id="ref-for-charter④">Charters</a> then are formally approved through an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review">AC Review</a> and <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①">W3C Decision</a> (see <a href="#CharterReview">§ 4.4 Charter Review and Approval</a>).</p>
+    </ul>
+    <h3 class="heading settled" data-level="4.1" id="charter-initiation"><span class="secno">4.1. </span><span class="content"> Initiating Charter Refinement</span><a class="self-link" href="#charter-initiation"></a></h3>
+    <p><a data-link-type="dfn" href="#charter" id="ref-for-charter⑤">Charters</a> can originate in many venues,
+	including existing <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧">Working</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG②">Interest Groups</a>,
+	Community Groups,
+	and from the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member②">Membership</a>.
+	Prior to the formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①">refinement</a> phase,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④⓪">Team</a> engages with those various parties
+	to help prepare <a data-link-type="dfn" href="#charter" id="ref-for-charter⑥">charters</a> for broader audiences.</p>
+    <p>Formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement②">charter refinement</a> (see below) is initiated
+	by the <a data-link-type="dfn" href="#team" id="ref-for-team④①">Team</a> sending a <a data-link-type="dfn" href="#charter-review-notice" id="ref-for-charter-review-notice">charter review notice</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①①">Advisory Committee</a>,
+	to the public,
+	and, in the case of rechartering, to the affected <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group②">Group</a>.</p>
+    <p>This <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-review-notice">charter review notice</dfn> must include:</p>
+    <ul>
+     <li data-md>
+      <p>A short summary of the proposal.</p>
+     <li data-md>
+      <p>The location of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-draft">charter draft</dfn>, which must be public.</p>
+     <li data-md>
+      <p>How to participate in the discussion of this <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft">charter draft</a> and where to file issues.</p>
+     <li data-md>
+      <p>The expected duration of the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement③">charter refinement</a> phase,
+which must not be less than 28 days,
+and should not be more than 6 months.</p>
+     <li data-md>
+      <p>Who the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator">Chartering Facilitator</a> is.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④②">Team</a> is responsible for initiating <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement④">charter refinement</a> at its discretion, in consideration of discussions with the community.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①③">Advisory Committee representative</a> <em class="rfc2119">may</em> formally request
+	that the <a data-link-type="dfn" href="#team" id="ref-for-team④③">Team</a> initiate <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑤">charter refinement</a>.
+	The Team <em class="rfc2119">may</em> deny such a request
+	if it thinks the proposal is insufficiently mature,
+	does not align with W3C’s scope and mission,
+	or otherwise does not meet the charter assessment criteria
+	described in the Guide (see <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/guide/process/charter"><cite>How to Create a Working Group or Interest Group</cite></a>),
+	and <em class="rfc2119">must</em> reply with its rationale.
+	This rejection is a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①">Team Decision</a>,
+	and can be appealed only by 5 or more <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member③">Members</a>,
+	through their <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①④">Advisory Committee representative</a>,
+	formally objecting to the decision within 8 weeks of the decision being announced.
+	In this case the <a data-link-type="dfn" href="#team" id="ref-for-team④④">Team</a> <em class="rfc2119">must</em> start an <a data-link-type="dfn" href="#appeal-vote" id="ref-for-appeal-vote">appeal vote</a> on whether to overturn the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision②">Team Decision</a>.
+	(No action is required to be taken when fewer than 5 members object.)</p>
+    <h3 class="heading settled" data-level="4.2" id="charter-development"><span class="secno">4.2. </span><span class="bs-old-id" id="WGCharterDevelopment"></span><span class="content"> Charter Refinement</span><a class="self-link" href="#charter-development"></a></h3>
+    <p>During <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-refinement">charter refinement</dfn>,
+	the W3C community,
+	under the guidance of the <a data-link-type="dfn" href="#team" id="ref-for-team④⑤">Team</a>,
+	further develops the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft①">charter draft</a> with the goal of achieving <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①">consensus</a> on the proposal.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="chartering-facilitator">Chartering Facilitator</dfn>—​who is chosen (and <em class="rfc2119">may</em> be replaced) by the <a data-link-type="dfn" href="#team" id="ref-for-team④⑥">Team</a>—​is responsible for seeking community <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②">consensus</a> among those participating in the refinement process
+	and making decisions reflecting that <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus③">consensus</a>.
+	In cases where <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus④">consensus</a> cannot be found,
+	the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator①">Chartering Facilitator</a> <em class="rfc2119">may</em> ask the <a data-link-type="dfn" href="#team" id="ref-for-team④⑦">Team</a> to make a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision③">Team Decision</a>,
+	and <em class="rfc2119">must</em> document the rationale for the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator②">Chartering Facilitator</a> is not necessarily the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①④">Chair</a> of the <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group①">group</a> being chartered.</p>
+    <p>During <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑥">charter refinement</a>:</p>
+    <ul>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①">Wide review</a> of the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft②">charter draft</a> is initiated and completed.</p>
+     <li data-md>
+      <p>All issues filed against the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft③">charter draft</a> must be <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed">formally addressed</a>,
+and their resolutions tracked in a disposition of comments
+highlighting any issues not resolved by consensus.</p>
+    </ul>
+    <p>Before the end of the announced duration
+	for the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑦">charter refinement</a> phase,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④⑧">Team</a> (informed by the work of the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator③">Chartering Facilitator</a>) <em class="rfc2119">must</em> <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision④">decide</a> which of the following to do:</p>
+    <ul>
+     <li data-md>
+      <p>Complete charter refinement by initiating <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①">AC Review</a> of the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft④">charter draft</a>.</p>
+     <li data-md>
+      <p>Abandon the proposal.</p>
+     <li data-md>
+      <p>Extend the charter refinement period.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④⑨">Team</a> <em class="rfc2119">must</em> announce its <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑤">decision</a> with the same visibility as the initial <a data-link-type="dfn" href="#charter-review-notice" id="ref-for-charter-review-notice①">charter review notice</a>,
+	and <em class="rfc2119">must</em> include a rationale
+	if they are not initiating <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②">AC Review</a>.
+	Reaching the end of the announced period (including any announced extension)
+	with no announced decision
+	is considered a de-facto <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑥">Team decision</a> to abandon the proposal.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⓪">Team</a> <em class="rfc2119">may</em> revise such a decision
+	by announcing an alternative decision.</p>
+    <p><a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③">Formal Objections</a> filed during the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑧">charter refinement</a> phase
+	are specially handled:</p>
+    <ul>
+     <li data-md>
+      <p>Objections to decisions pertaining to the content of the charter,
+as well as objections to initiating the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③">AC Review</a>,
+are considered registered at the close of the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review④">Advisory Committee Review</a> of the charter,
+and are registered against that <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision②">W3C Decision</a>.</p>
+      <p class="note" role="note"><span class="marker">Note:</span> This enables all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④">Formal Objections</a> on the same proposed <a data-link-type="dfn" href="#charter" id="ref-for-charter⑦">charter</a> to be handled together.</p>
+     <li data-md>
+      <p>Objections to abandoning the proposal or to extending the refinement period can be appealed only if 5 or more Members,
+through their <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑤">Advisory Committee representative</a>,
+formally object to the decision within 8 weeks of the decision.
+In this case,
+the <a data-link-type="dfn" href="#team" id="ref-for-team⑤①">Team</a> <em class="rfc2119">must</em> do one of the following:</p>
+      <ul>
+       <li data-md>
+        <p>Abide by the objectors' request, if they all agree on the
+alternative course of action (e.g., to abandon,
+extend, or complete charter refinement).</p>
+       <li data-md>
+        <p>Initiate an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑤">AC Review</a> to formally solicit the input of
+the community and take a W3C Decision on the subsequent
+course of action.</p>
+       <li data-md>
+        <p>Convene a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③">Council</a> to decide the subsequent course of action.</p>
+      </ul>
+      <p>(No action is required to be taken when fewer than 5 members object.)</p>
+     <li data-md>
+      <p>Any other objections are processed normally (See <a href="#addressing-fo">§ 5.6 Addressing Formal Objections</a>).</p>
+    </ul>
+    <h3 class="heading settled" data-level="4.3" id="WGCharter"><span class="secno">4.3. </span><span class="content"> Content of a Charter</span><a class="self-link" href="#WGCharter"></a></h3>
+    <p>A Working Group or Interest Group <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="charter">charter</dfn> <em class="rfc2119">must</em> include all of the following information.</p>
+    <ul>
+     <li> The group’s mission
+			(e.g., develop a technology or process, review the work of other groups). 
+     <li> The scope of the group’s work and criteria for success. 
+     <li> The duration of the proposed charter for the group. 
+     <li> The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software). 
+     <li>
+       Expected milestone dates where available. 
+      <p class="note" role="note"><span class="marker">Note:</span> A charter does not need to include
+			schedules for review of other group’s deliverables.</p>
+     <li> The process for the group to approve the release of deliverables
+			(including intermediate results). 
+     <li> Any dependencies by groups within or outside of W3C on the deliverables of this group.
+			For any dependencies, the charter <em class="rfc2119">must</em> specify
+			the mechanisms for communication about the deliverables. 
+     <li> Any dependencies of this group on other groups within or outside of W3C.
+			Such dependencies include interactions with <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a>. 
+     <li> The <a href="#confidentiality-levels">level of confidentiality</a> of the group’s proceedings and deliverables. 
+     <li> The name and affiliation of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑤">Chair</a> or co-Chairs. 
+     <li> Meeting mechanisms and expected frequency. 
+     <li> If known,
+			the date of the first <a href="#ftf-meeting" id="ref-for-ftf-meeting①">face-to-face meeting</a>.
+			The date of the first face-to-face meeting of a proposed group <em class="rfc2119">must not</em> be sooner than <span class="time-interval">eight weeks</span> after the date of the proposal. 
+     <li> Communication mechanisms to be employed within the group,
+			between the group and the rest of W3C,
+			and with the general public. 
+     <li> Any voting procedures or requirements
+			other than those specified in <a href="#Votes">§ 5.2.3 Deciding by Vote</a>. 
+     <li> An estimate of the expected time commitment from participants. 
+     <li> The expected time commitment and level of involvement by the Team
+			(e.g., to track developments,
+			write and edit technical reports,
+			develop code,
+			or organize pilot experiments). 
+     <li> Intellectual property information.
+			What are the intellectual property (including patents and copyright)
+			considerations affecting the success of the Group?
+			In particular, is there any reason to believe
+			that it will be difficult to meet the Royalty-Free licensing goals
+			in “Licensing Goals for W3C Specifications”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>? 
+    </ul>
+    <p>See also the charter requirements in “Licensing Goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>For every Recommendation Track deliverable
+	that continues work on a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report">technical report</a> published under any other Charter (including a predecessor group of the same name),
+	for which there is at least an existing <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd">First Public Working Draft</a> the description of that deliverable in the proposed charter of the adopting Working Group <em class="rfc2119">must</em> provide the following information:</p>
+    <ul>
+     <li> The title,
+			stable URL,
+			and publication date of the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD">Working Draft</a> or other Recommendation-track document
+			that will serve as the basis for work on the deliverable
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="adopted-draft">Adopted Draft</dfn>”); 
+     <li> The title,
+			stable URL,
+			and publication date of the document
+			that was used as the basis for its most recent Exclusion Opportunity
+			as per
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft">Exclusion Draft</dfn>”); and 
+     <li> The stable URL of the Working Group charter
+			under which the Exclusion Draft was published
+			(labeled the “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft-charter">Exclusion Draft Charter</dfn>”). 
+    </ul>
+    <p>All of the above data <em class="rfc2119">must</em> be identified
+	in the adopting Working Group’s charter using the labels indicated.</p>
+    <p>The <a data-link-type="dfn" href="#adopted-draft" id="ref-for-adopted-draft">Adopted Draft</a> and the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft">Exclusion Draft</a> <em class="rfc2119">must</em> each be adopted in their entirety and without any modification.
+	The proposed charter <em class="rfc2119">must</em> state
+	the dates on which the Exclusion Opportunity
+	that arose on publishing the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft①">Exclusion Draft</a> began and ended.
+	As per “Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	this potentially means that exclusions can only be made immediately on joining a Working Group.</p>
+    <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding participation,
+	including specifying
+	that the <span id="ig-mail-only">only requirement for participation (by anyone) in
+	the Interest Group is subscription to the Interest Group mailing list</span>.
+	This type of Interest Group <em class="rfc2119">may</em> have <a href="#public-participant-ig" id="ref-for-public-participant-ig">public participants</a>. </p>
+    <p>A charter <em class="rfc2119">may</em> include
+	provisions other than those required by this document.
+	The charter <em class="rfc2119">should</em> highlight
+	whether additional provisions impose constraints
+	beyond those of the W3C 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>
+    <h3 class="heading settled" data-level="4.4" id="CharterReview"><span class="secno">4.4. </span><span class="content"> Charter Review and Approval</span><a class="self-link" href="#CharterReview"></a></h3>
+    <h4 class="heading settled" data-level="4.4.1" id="charter-major-changes"><span class="secno">4.4.1. </span><span class="content"> New Charters and Major Changes</span><a class="self-link" href="#charter-major-changes"></a></h4>
+    <p>Any new <a data-link-type="dfn" href="#charter" id="ref-for-charter⑧">charter</a> (including re-chartering of existing <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group②">chartered groups</a>)
+	and any change that is not a <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes">minor change</a> (per <a href="#charter-minor-changes">§ 4.4.2 Minor Changes to Active Charters</a>) to an already-approved <a data-link-type="dfn" href="#charter" id="ref-for-charter⑨">charter</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG③">Interest Group</a> <em class="rfc2119">must</em> be approved by a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision③">W3C Decision</a> following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑥">AC Review</a> of that <a data-link-type="dfn" href="#charter" id="ref-for-charter①⓪">charter</a>.
+	Modifications to a <a data-link-type="dfn" href="#charter" id="ref-for-charter①①">charter</a> <em class="rfc2119">should</em> have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑤">consensus</a> of the group.</p>
+    <p>The review period <em class="rfc2119">must</em> be at least 28 days.
+	Any <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑥">Advisory Committee representative</a> <em class="rfc2119">may</em> request an extended review period
+	in response to the Call for Review;
+	upon receipt of any such request,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤②">Team</a> <em class="rfc2119">must</em> extend the review period
+	to at least 60 days.</p>
+    <p>The Call for Review of a modified charter <em class="rfc2119">must</em> highlight important changes
+	(e.g., regarding changes in scope, deliverables, or resource allocation)
+	and <em class="rfc2119">must</em> include rationale for those changes.</p>
+    <p>The Call for Review of a new or modified charter <em class="rfc2119">must</em> include a disposition of comments received during the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑨">charter refinement</a> process,
+	highlighting any issues that were closed despite sustained objections.</p>
+    <h4 class="heading settled" data-level="4.4.2" id="charter-minor-changes"><span class="secno">4.4.2. </span><span class="content"> Minor Changes to Active Charters</span><a class="self-link" href="#charter-minor-changes"></a></h4>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change">Editorial changes</a> or <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change">substantive changes</a> to a <a data-link-type="dfn" href="#charter" id="ref-for-charter①②">charter</a> (including <a href="#charter-extension">extensions</a>)
+	that do not affect the scope of the group’s work
+	or the way the group functions in any significant way
+	are deemed <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minor-changes">minor changes</dfn> and <em class="rfc2119">may</em> be approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑦">Team Decision</a>,
+	in which case they do not require <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①⓪">charter refinement</a> nor <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑦">Advisory Committee Review</a>.
+	Any change to the scope of the <a data-link-type="dfn" href="#charter" id="ref-for-charter①③">charter</a> or addition of a new <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track">REC track</a> deliverable
+	that does not fall within the scope of an existing deliverable
+	is a major, not <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes①">minor</a>, change.
+	The following are examples of <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes②">minor changes</a>:
+	the renaming or restructuring (e.g. splitting or combining) of existing in-scope deliverables,
+	the addition of new <a href="#note-track">Note track</a> deliverables that help explain the group’s work
+	a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑥">Staff Contact</a>,
+	or a change of <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑥">Chair</a>. <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes③">Minor changes</a>, other than a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑦">Staff Contact</a>, <em class="rfc2119">should</em> have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑥">consensus</a> of the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤③">Team</a> <em class="rfc2119">may</em> nevertheless choose
+	to initiate <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①①">charter refinement</a> and/or <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑧">Advisory Committee Review</a> when it thinks the changes would benefit from more scrutiny or explicit buy-in.</p>
+    <p>Though <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑨">Advisory Committee Review</a> is not required,
+	such changes <em class="rfc2119">must</em> still be announced
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①②">Advisory Committee</a>,
+	and to participants in the <a href="#wgparticipant" id="ref-for-wgparticipant①">Working</a> or <a href="#igparticipant" id="ref-for-igparticipant①">Interest</a> Group,
+	and a rationale must be provided.</p>
+    <h3 class="heading settled" data-level="4.5" id="cfp"><span class="secno">4.5. </span><span class="content"> Call for Participation in a Chartered Group</span><a class="self-link" href="#cfp"></a></h3>
+    <p>Deciding whether to adopt a proposed <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⓪">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG④">Interest Group</a> <a data-link-type="dfn" href="#charter" id="ref-for-charter①④">charter</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision④">W3C Decision</a>.
+	Charters <em class="rfc2119">may</em> be amended based on review comments
+	per <a href="#ACReviewAfter">§ 5.7.2 Determining the W3C Decision</a> before the Call for Participation.</p>
+    <p>If the decision is to charter the group,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤④">Team</a> <em class="rfc2119">must</em> issue a Call for Participation to the Advisory Committee.
+	For a new group, this announcement officially creates the group.
+	The announcement <em class="rfc2119">must</em> include a reference to the <a href="#WGCharter">charter</a>,
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑦">Chair(s)</a>,
+	and the name(s) of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑧">Staff Contact(s)</a>.</p>
+    <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).
+	When a group is re-chartered,
+	individuals participating in the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①①">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑤">Interest Group</a> before the new Call for Participation
+	may attend any meetings held within forty-five (45) days of the Call for Participation
+	even if they have not yet formally rejoined the group
+	(i.e., committed to the terms of the charter and patent policy).</p>
+    <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against the decision to create
+	or substantially modify
+	a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.6" id="charter-extension"><span class="secno">4.6. </span><span class="content"> Charter Extension</span><a class="self-link" href="#charter-extension"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑤">Team</a> <em class="rfc2119">may</em> decide
+	to extend a Working Group or Interest Group charter
+	with no other substantive modifications.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑥">Team</a> <em class="rfc2119">must</em> announce
+	such <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="charter extension" id="dfn-charter-extension">extensions</dfn> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①③">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate the new duration.
+	The announcement <em class="rfc2119">must</em> also include rationale for the extension,
+	a reference to the <a href="#WGCharter">charter</a>,
+	and the Group homepage
+	(which includes at least
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑧">Chair(s)</a>,
+	the name of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑨">Staff Contact</a>,
+	and instructions for joining the group).</p>
+    <p>After a charter extension,
+	Advisory Committee representatives
+	and the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑨">Chair</a> 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> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑧">Team decision</a> regarding the extension of a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.7" id="GeneralTermination"><span class="secno">4.7. </span><span class="content"> Chartered Group Closure</span><a class="self-link" href="#GeneralTermination"></a></h3>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①②">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑥">Interest Group</a> charter specifies a duration for the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑦">Team</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑦">TAG</a>, or the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②③">AB</a> <em class="rfc2119">may</em> propose to close a group
+	prior to the date specified in the charter in any of the following circumstances:</p>
+    <ul>
+     <li data-md>
+      <p>There are insufficient member resources to produce chartered deliverables
+or to maintain the group,
+according to priorities established within W3C.</p>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="https://www.w3.org/policies/patent-policy/#patent-advisory-group" id="ref-for-patent-advisory-group">Patent Advisory Group</a> concluded that the work <em class="rfc2119">should</em> be terminated.</p>
+     <li data-md>
+      <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑧">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②④">AB</a> determined that continuing operation of the chartered group or its work
+would be detrimental to W3C or its mission.</p>
+     <li data-md>
+      <p>The group produced all chartered deliverables ahead of schedule.</p>
+    </ul>
+    <p>Such a proposal to close a group must be accompanied by rationale,
+	and the proposal must be confirmed by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⓪">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑤">W3C Decision</a>.</p>
+    <p>Closing a Working Group has implications
+	with respect to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h2 class="heading settled" data-level="5" id="decisions"><span class="secno">5. </span><span class="content"> Decisions</span><a class="self-link" href="#decisions"></a></h2>
+    <p>W3C attempts to resolve issues through dialog.
+	Individuals who disagree strongly with a decision <em class="rfc2119">should</em> register with the Chair any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑤">Formal Objections</a>.</p>
+    <h3 class="heading settled" data-level="5.1" id="decision-types"><span class="secno">5.1. </span><span class="content"> Types of Decisions</span><a class="self-link" href="#decision-types"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⓪">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①③">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑦">Interest Group</a> has the prerogative
+	to make certain decisions based on their own judgment.
+	Such decisions are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chair-decisions">chair decisions</dfn>.</p>
+    <p>In contrast,
+	decisions taken by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②①">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑧">Interest Group</a> on the basis of having assessed the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑦">consensus</a> of the group
+	or following a vote (see <a href="#Votes">§ 5.2.3 Deciding by Vote</a>)
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="group decision | resolution" id="group-decision">group decisions</dfn> (also known as group “resolutions”).</p>
+    <p>Decisions made by members of the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑧">Team</a> in connection with this Process,
+	based on their own individual or collective judgement,
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Team Decision | Team&apos;s Decision" data-noexport id="team-decision">Team Decisions</dfn>.</p>
+    <p>In contrast,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-w3c-decision">W3C decision</dfn> is
+	determined by the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑨">Team</a> on behalf of the W3C community
+	by <a href="#ACReviewAfter">assessing the consensus of the W3C Community</a> after an <a href="#ACReview">Advisory Committee review</a>.</p>
+    <h3 class="heading settled" data-level="5.2" id="consensus-building"><span class="secno">5.2. </span><span class="content"> Consensus Building</span><a class="self-link" href="#consensus-building"></a></h3>
+    <h4 class="heading settled" data-level="5.2.1" id="Consensus"><span class="secno">5.2.1. </span><span class="content"> Consensus</span><a class="self-link" href="#Consensus"></a></h4>
+    <p>Consensus is a core value of W3C.
+	To promote consensus,
+	the W3C process requires Chairs to ensure
+	that groups consider all legitimate views and objections,
+	and endeavor to resolve them,
+	whether these views and objections are expressed by the active participants of the group
+	or by others
+	(e.g., another W3C group,
+	a group in another organization,
+	or the general public).
+	Decisions <em class="rfc2119">may</em> be made during meetings
+	(<a href="#ftf-meeting" id="ref-for-ftf-meeting②">face-to-face</a> or <a href="#distributed-meeting" id="ref-for-distributed-meeting">distributed</a>)
+	as well as through <a href="#discussion-archiving">persistent text-based discussions</a>.</p>
+    <p>The following terms are used in this document
+	to describe the level of support for a decision among a set of eligible individuals:</p>
+    <dl>
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Consensus">Consensus</dfn>: 
+     <dd> A substantial number of individuals in the set
+			support the decision
+			and there is no sustained objection from anybody in the set.
+			Individuals in the set <em class="rfc2119">may</em> abstain.
+			Abstention is either an explicit expression of no opinion
+			or silence by an individual in the set. 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Unanimity">Unanimity</dfn>: 
+     <dd> The particular case of <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑧">consensus</a> where all individuals in the set support the decision
+			(i.e., no individual in the set abstains). 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Dissent">Dissent</dfn>: 
+     <dd> At least one individual in the set sustains an objection. 
+    </dl>
+    <p class="note" role="note"><span class="marker">Note:</span> A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑥">Formal Objection</a> always indicates a sustained objection,
+	but isn’t necessary to express it
+	(except in the context of formal <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①①">AC Reviews</a>).
+	Disagreement with a proposed decision,
+	however, does not always rise to the level of sustained objection,
+	as individuals could be willing to accept a decision
+	while expressing disagreement.</p>
+    <p>By default, the set of individuals eligible to participate in a decision is the set of group participants.
+	The Process Document does not require a quorum for decisions
+	(i.e., the minimal number of eligible participants required to be present before the Chair can call a question).
+	A charter <em class="rfc2119">may</em> include a quorum requirement for consensus decisions.</p>
+    <p>Where <a data-link-type="dfn" href="#def-Unanimity" id="ref-for-def-Unanimity">unanimity</a> is not possible,
+	a group <em class="rfc2119">should</em> strive to make <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑨">consensus</a> decisions
+	where there is significant support and few abstentions.
+	The Process Document does not require a particular percentage of eligible participants
+	to agree to a motion in order for a decision to be made.
+	To avoid decisions where there is widespread apathy,
+	(i.e., little support and many abstentions),
+	groups <em class="rfc2119">should</em> set minimum thresholds of active support before a decision can be recorded.
+	The appropriate percentage <em class="rfc2119">may</em> vary depending on the size of the group
+	and the nature of the decision.
+	A charter <em class="rfc2119">may</em> include threshold requirements for consensus decisions.
+	For instance, a charter might require a supermajority of eligible participants
+	(i.e., some established percentage above 50%)
+	to support certain types of consensus decisions.</p>
+    <div class="note" role="note">
+      Note: Chairs have substantial flexibility
+	in how they obtain and assess consensus among their groups.
+	Unless otherwise constrained by charter,
+	they can use modes including but not limited to explicit calls for consensus,
+	polls of participants,
+	“lazy consensus” in which lack of objection after sufficient notice is taken as assent;
+	they can also delegate and empower a document editor
+	to assess consensus on their behalf,
+	whether in general
+	or for specific pre-determined circumstances
+	(e.g. in non-controversial situations, for specific types of issues, etc.). 
+     <p>If questions or disagreements arise,
+	the final determination of consensus remains with the chair.</p>
+    </div>
+    <h4 class="heading settled" data-level="5.2.2" id="managing-dissent"><span class="secno">5.2.2. </span><span class="content"> Managing Dissent</span><a class="self-link" href="#managing-dissent"></a></h4>
+    <p>In some cases, even after careful consideration of all points of view,
+	a group might find itself unable to reach consensus.
+	The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②②">Chair</a> <em class="rfc2119">may</em> record a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent">dissent</a> so that the group can make progress
+	(for example, to produce a deliverable in a timely manner).
+	Dissenters cannot stop a group’s work
+	simply by saying that they cannot live with a decision.
+	When the Chair believes that the Group has duly considered
+	the legitimate concerns of dissenters as far as is possible and reasonable,
+	the group <em class="rfc2119">should</em> move on.</p>
+    <p>Groups <em class="rfc2119">should</em> favor proposals that create the weakest objections.
+	This is preferred over proposals that are supported by a large majority
+	but that cause strong objections from a few people.
+	As part of making a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent①">dissent</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②③">Chair</a> is expected to be aware of which participants work for the same
+	(or <a href="#MemberRelated">related</a>)
+	Member organizations and weigh their input accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Dissenters can escalate their sustained objection to a decision by registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑦">Formal Objection</a>.</p>
+    <h4 class="heading settled" data-level="5.2.3" id="Votes"><span class="secno">5.2.3. </span><span class="content"> Deciding by Vote</span><a class="self-link" href="#Votes"></a></h4>
+    <p>A group <em class="rfc2119">should</em> only conduct a vote to resolve a <em>substantive issue</em> after the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②④">Chair</a> has determined that all available means of <a href="#Consensus">reaching consensus</a> through technical discussion and compromise have failed,
+	and that a vote is necessary to break a deadlock.
+	In this case the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑤">Chair</a> <em class="rfc2119">must</em> record
+	(e.g., in the <a data-link-type="dfn" href="#minutes" id="ref-for-minutes②">minutes</a> of the meeting or in an archived email message):</p>
+    <ul>
+     <li> an explanation of the issue being voted on; 
+     <li> the decision to conduct a vote
+			(e.g., a simple majority vote) to resolve the issue; 
+     <li> the outcome of the vote; 
+     <li> any Formal Objections. 
+    </ul>
+    <p>In order to vote to resolve a substantive issue,
+	an individual <em class="rfc2119">must</em> be a group <a data-link-type="dfn" href="#participant" id="ref-for-participant①">participant</a>.
+	Each organization represented in the group <em class="rfc2119">must</em> have at most one vote,
+	even when the organization is represented by several participants in the group
+	(including Invited Experts).
+	For the purposes of voting:</p>
+    <ul>
+     <li> A Member or group of <a href="#MemberRelated">related Members</a> is considered a single organization. 
+     <li> The <a href="#Team">Team</a> is considered an organization. 
+    </ul>
+    <p>Unless the charter states otherwise, <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">may</em> vote.</p>
+    <p>If a participant is unable to attend a vote,
+	that individual <em class="rfc2119">may</em> authorize anyone at the meeting
+	to act as a proxy.
+	The absent participant <em class="rfc2119">must</em> inform the Chair in writing
+	who is acting as proxy, with written instructions on the use of the proxy.
+	For a Working Group or Interest Group,
+	see the related requirements regarding an individual
+	who attends a meeting as a <a href="#mtg-substitute" id="ref-for-mtg-substitute">substitute</a> for a participant.</p>
+    <p>A group <em class="rfc2119">may</em> vote for other purposes than to resolve a substantive issue.
+	For instance, the Chair often conducts a “straw poll” vote
+	as a means of determining whether there is consensus about a potential decision.</p>
+    <p>A group <em class="rfc2119">may</em> also vote to make a process decision.
+	For example,
+	it is appropriate to decide by simple majority
+	whether to hold a meeting in San Francisco or San Jose
+	(there’s not much difference geographically).
+	When simple majority votes are used to decide minor issues,
+	voters are <em class="rfc2119">not required</em> to state the reasons for votes,
+	and the group is <em class="rfc2119">not required</em> to record individual votes.</p>
+    <p>A group charter <em class="rfc2119">may</em> include formal voting procedures
+	(e.g., quorum or threshold requirements)
+	for making decisions about substantive issues.</p>
+    <h3 class="heading settled" data-level="5.3" id="formal-address"><span class="secno">5.3. </span><span class="content"> Formally Addressing an Issue</span><a class="self-link" href="#formal-address"></a></h3>
+    <p>In the context of this document,
+	a group has <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="formally-addressed">formally addressed</dfn> an issue when it has sent a public, substantive response
+	to the reviewer who raised the issue.
+	A substantive response is expected to include rationale for decisions
+	(e.g., a technical explanation, a pointer to charter scope, or a pointer to a requirements document).
+	The adequacy of a response is measured
+	against what a W3C reviewer would generally consider to be technically sound.
+	If a group believes that a reviewer’s comments result from a misunderstanding,
+	the group <em class="rfc2119">should</em> seek clarification before reaching a decision.</p>
+    <p>As a courtesy,
+	both Chairs and reviewers <em class="rfc2119">should</em> set expectations
+	for the schedule of responses and acknowledgments.
+	The group <em class="rfc2119">should</em> reply to a reviewer’s initial comments
+	in a timely manner.
+	The group <em class="rfc2119">should</em> set a time limit
+	for acknowledgment by a reviewer of the group’s substantive response;
+	a reviewer cannot block a group’s progress.
+	It is common for a reviewer to require a week or more
+	to acknowledge and comment on a substantive response.
+	The group’s responsibility to respond to reviewers
+	does not end once a reasonable amount of time has elapsed.
+	However, reviewers <em class="rfc2119">should</em> realize
+	that their comments will carry less weight
+	if not sent to the group in a timely manner.</p>
+    <p>Substantive responses <em class="rfc2119">should</em> be recorded.
+	The group <em class="rfc2119">should</em> maintain an accurate summary
+	of all substantive issues and responses to them
+	(e.g., in the form of an issues list with links to mailing list archives).</p>
+    <h3 class="heading settled" data-level="5.4" id="WGChairReopen"><span class="secno">5.4. </span><span class="content"> Reopening a Decision When Presented With New Information</span><a class="self-link" href="#WGChairReopen"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑥">Chair</a> <em class="rfc2119">may</em> reopen a decision
+	when presented with new information, including:</p>
+    <ul>
+     <li> additional technical information, 
+     <li> comments by email from participants who were unable to attend a scheduled meeting, 
+     <li> comments by email from meeting attendees
+			who chose not to speak out during a meeting
+			(e.g., so they could confer later with colleagues or for cultural reasons). 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑦">Chair</a> <em class="rfc2119">should</em> record
+	that a decision has been reopened,
+	and <em class="rfc2119">must</em> do so upon request from a group participant.</p>
+    <h3 class="heading settled" data-level="5.5" id="registering-objections"><span class="secno">5.5. </span><span class="bs-old-id" id="chair-decision-appeal"></span><span class="bs-old-id" id="wg-decision-appeal"></span><span class="bs-old-id" id="WGAppeals"></span><span class="bs-old-id" id="WGArchiveMinorityViews"></span><span class="content"> Registering Formal Objections</span><a class="self-link" href="#registering-objections"></a></h3>
+    <p>Any individual
+	(regardless of whether they are associated with a Member) <em class="rfc2119">may</em> appeal any decision made in connection with this Process
+	(except those having a different appeal process)
+	by registering a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="FormalObjection">Formal Objection</dfn> with the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⓪">Team</a>.
+	Group participants <em class="rfc2119">should</em> inform
+	their <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①⓪">Staff Contact</a> as well as the group’s Chair(s).
+	The Staff Contact <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑦">CEO</a> when a group participant has also raised concerns about due process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> In this document, the term <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑧">Formal Objection</a> is used to emphasize this process implication:
+	Formal Objections receive formal consideration and a formal response.
+	The word “objection” used alone has its ordinary English connotations.
+	See <a href="#consensus-building">§ 5.2 Consensus Building</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑨">Formal Objection</a> <em class="rfc2119">must</em> include a summary of
+	the issue (whether technical or procedural),
+	the decision being appealed,
+	and the rationale for the objection.
+	It <em class="rfc2119">should</em> cite technical arguments
+	and propose changes that would remove the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⓪">Formal Objection</a>;
+	these proposals <em class="rfc2119">may</em> be vague or incomplete. <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①①">Formal Objections</a> that do not provide substantive arguments
+	or rationale are unlikely to receive serious consideration.
+	Counter-arguments,
+	rationales,
+	and decisions <em class="rfc2119">should</em> also be recorded.</p>
+    <p>No later than when the <a href="#team-fo-mediation">relevant Council is initiated</a>,
+	a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①②">Formal Objection</a> against a decision regarding a publicly-available document <em class="rfc2119">must</em> be made <a href="#confidentiality-change">publicly available</a>;
+	likewise, a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①③">Formal Objection</a> against a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①">Member-visible</a> decision <em class="rfc2119">must</em> be made <a href="#confidentiality-change">available to Members</a>.
+	A Call for Review to the Advisory Committee <em class="rfc2119">must</em> identify any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①④">Formal Objections</a> related to that review.
+	This requirement is waived
+	if the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑤">Formal Objection</a> is resolved to the satisfaction of the objector
+	before its <a href="#confidentiality-change">confidentiality is changed</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑥">Formal Objections</a> against matter in a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①">technical report</a> <a href="#adv-verif-reqs">are expected to be fully addressed</a> before <a href="#rec-advance">requesting advancement</a> of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②">technical report</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑦">Formal Objection</a> filed during an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①②">Advisory Committee Review</a> is considered registered at the close of the review period.</p>
+    <p>Registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑧">Formal Objection</a> initiates the process of <a href="#addressing-fo">addressing the Formal Objection</a>.
+	The resolution of a recorded Formal Objection—​whether by a Council decision, adoption of a consensus proposal, retraction of the Formal Objection, etc.—​must be recorded and made available at the same level of visibility as the record of the Formal Objection itself.</p>
+    <h3 class="heading settled" data-level="5.6" id="addressing-fo"><span class="secno">5.6. </span><span class="content"> Addressing Formal Objections</span><a class="self-link" href="#addressing-fo"></a></h3>
+    <h4 class="heading settled" data-level="5.6.1" id="team-fo-mediation"><span class="secno">5.6.1. </span><span class="content"> Investigation and Mediation by the Team</span><a class="self-link" href="#team-fo-mediation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑥①">Team</a> considers the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑨">Formal objection</a>,
+	researches the question,
+	interviews parties,
+	and so on,
+	to make sure the problem and the various viewpoints are well understood,
+	and to the extent possible,
+	to arrive at a recommended disposition.</p>
+    <p>In parallel, the Team <em class="rfc2119">should</em> start the steps necessary
+	to <a href="#council-convention">convene</a> a Council.</p>
+    <p>If the <a data-link-type="dfn" href="#team" id="ref-for-team⑥②">Team</a> can resolve the issue
+	to the satisfaction of the individual that filed the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⓪">Formal Objection</a>,
+	the individual withdraws the objection and the disposition process terminates.</p>
+    <p>Otherwise,
+	upon concluding that consensus cannot be found,
+	and no later than 90 days after the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②①">Formal Objection</a> being registered,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑥③">Team</a> <em class="rfc2119">must</em> deliver to the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council④">Council</a> a report
+	documenting its findings and attempts to find consensus,
+	and hand over the matter to the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑤">W3C Council</a>.</p>
+    <h4 class="heading settled" data-level="5.6.2" id="council"><span class="secno">5.6.2. </span><span class="content"> W3C Council</span><a class="self-link" href="#council"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-local-lt="Council" id="w3c-council">W3C Council</dfn> is the body convened to resolve <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②②">Formal Objections</a> by combining the capabilities and perspectives of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑤">AB</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑨">TAG</a>, and the <a data-link-type="dfn" href="#team" id="ref-for-team⑥④">Team</a>,
+	and is tasked with doing so in the best interests of the Web and W3C.</p>
+    <h5 class="heading settled" data-level="5.6.2.1" id="council-composition"><span class="secno">5.6.2.1. </span><span class="content"> Council Composition</span><a class="self-link" href="#council-composition"></a></h5>
+    <p>Each <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑥">W3C Council</a> is composed of the following members (excepting any <a href="#council-participation">renounced or dismissed</a>):</p>
+    <ul>
+     <li data-md>
+      <p>the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑧">CEO</a> or their chosen <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑤">Team</a> delegate</p>
+     <li data-md>
+      <p>the members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑥">Advisory Board</a></p>
+     <li data-md>
+      <p>the elected and appointed members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⓪">Technical Architecture Group</a></p>
+    </ul>
+    <p>Participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑦">W3C Council</a> <em class="rfc2119">must not</em> require attendance of <a data-link-type="dfn" href="#ftf-meeting" id="ref-for-ftf-meeting③">face-to-face meetings</a>.</p>
+    <p>A distinct instance of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑧">W3C Council</a> is convened for each decision being appealed or objected to.
+	The list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑨">Council</a> members evolves
+	as <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑦">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③①">TAG</a> terms start and end
+	until <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed">dismissal</a> and <a data-link-type="dfn" href="#renounce" id="ref-for-renounce">renunciation</a> are concluded,
+	at which point the membership of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⓪">Council</a> is fixed.
+	However, if the number of active members in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①①">Council</a> falls so low as to hinder effective and balanced deliberations,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair">Council Chair</a> <em class="rfc2119">should</em> dissolve the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①②">Council</a> and call for a new one to be convened.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> TAG and AB elections have no effect on the Council’s membership
+	once it is fixed.</p>
+    <p>A <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑥">Team</a> member is assigned
+	to act as the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-staff-contact"><span class="bs-old-id" id="council-team-contact"></span>Council Staff Contact</dfn>,
+	to support this Council
+	and to facilitate adherence to this Process.</p>
+    <h5 class="heading settled" data-level="5.6.2.2" id="council-delegation"><span class="secno">5.6.2.2. </span><span class="content"> Extraordinary Delegation</span><a class="self-link" href="#council-delegation"></a></h5>
+    <p>In extraordinary cases,
+	if they feel a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①③">Council</a> would not be the appropriate deciding body,
+	a member of the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑦">Team</a> (particularly the Legal Counsel) or
+	any potential Council member
+	may suggest that the decision for that specific Formal Objection be delegated
+	to the W3C Board of Directors,
+	to an officer of its corporation (such as the Legal Counsel),
+	or to one or more specific individuals from the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑧">Team</a>.
+	The potential Council members then <em class="rfc2119">may</em> confidentially discuss
+	and <em class="rfc2119">must</em> vote
+	whether to delegate the decision for that specific <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②③">Formal Objection</a>.
+	A decision to delegate <em class="rfc2119">must</em> be supported by a two-thirds supermajority vote
+	(i.e., at least twice as many votes in favor as against).
+	Delegation in such cases cannot be later revoked.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑨">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①④">Advisory Committee</a> when a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②④">Formal Objection</a> has been delegated,
+	and to whom it has been delegated.</p>
+    <h5 class="heading settled" data-level="5.6.2.3" id="council-participation"><span class="secno">5.6.2.3. </span><span class="content"> Council Participation, Dismissal, and Renunciation</span><a class="self-link" href="#council-participation"></a></h5>
+    <p>A potential Council member may be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="dismissed | dismiss | dismissal" data-noexport id="dismissed">dismissed</dfn> from the Council.
+	In order to apply consistent criteria,
+	the potential Council members decide collectively
+	which reasons against service
+	rise to a sufficient level for a potential member to be <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed①">dismissed</a>.
+	No-one is automatically dismissed,
+	and individual recusal is not used in the Council. <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed②">Dismissal</a> applies to an individual person in the context of a specific Council,
+	and should be used rarely in order to preserve the greatest diversity on the Council.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> A W3C Council is a deliberative body whose purpose is
+	to find the best way forward for the Web and for W3C.
+	It is not a judicial body tasked with determining right or wrong.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⓪">Team</a> <em class="rfc2119">must</em> draft a list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①④">Council</a> members,
+	with annotations of possible reasons for dismissal against each one.
+	The W3C community,
+	including members and team, and potential council members, <em class="rfc2119">must</em> be given an opportunity to contribute possible reasons to this list.
+	Affected members <em class="rfc2119">must</em> be given
+	an opportunity to respond to such comments about themselves.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦①">Team</a> may report comments verbatim
+	or may paraphrase them while preserving their intent;
+	they may also elide inappropriate comments,
+	such as any that violate applicable laws or the <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a>.</p>
+    <p>Before a Council forms,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦②">Team</a> presents the entire list of potential members
+	and collected reasons and responses
+	to the potential Council members,
+	who then consider for each potential member
+	whether that individual’s participation
+	would compromise the integrity of the Council decision,
+	and vote whether to dismiss that potential member.
+	No one is allowed to vote on their own dismissal;
+	each dismissal is enacted if there are at least as many ballots for as against.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since dismissal is individual,
+	when the decision being objected to was made by the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③②">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑧">AB</a> acting as a body,
+	the entire <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③③">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑨">AB</a> is not expected to be dismissed.</p>
+    <p>An individual <em class="rfc2119">may</em> also <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="renounce | renunciation" data-noexport id="renounce">renounce</dfn> their seat on a Council, for strong reason,
+	such as being forbidden by their employer to serve. The individual chooses the extent to which they explain
+	their renunciation.
+	Renunciation is disqualification from participation,
+	not abstention,
+	and <em class="rfc2119">should not</em> be used
+	to excuse an absence of participation.</p>
+    <p>Any person who has been <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed③">dismissed</a> or who <a data-link-type="dfn" href="#renounce" id="ref-for-renounce①">renounces</a> their seat
+	does not receive <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑤">Council</a> materials,
+	take part in its deliberations,
+	help in the determination of consensus,
+	or vote.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑥">W3C Council</a> <em class="rfc2110">may</em> still solicit and hear their testimony,
+	as they can of anyone else in the W3C community.</p>
+    <h5 class="heading settled" data-level="5.6.2.4" id="council-short-circuit"><span class="secno">5.6.2.4. </span><span class="content"> Short Circuit</span><a class="self-link" href="#council-short-circuit"></a></h5>
+    <p>The full Council process <em class="rfc2119">may</em> be short-circuited if
+	the Team recommends a resolution
+	and potential members of a Council who are not renouncing their seat
+	confirm it by a vote which results in both of the following:</p>
+    <ul>
+     <li data-md>
+      <p>at least 80% of them vote affirmatively to adopt this resolution</p>
+     <li data-md>
+      <p>none of them vote against adopting the resolution</p>
+    </ul>
+    <p>The request for confirmation <em class="rfc2119">must</em> be open for a period of at least two weeks,
+	or until every potential member of the Council not renouncing their seat
+	has voted,
+	whichever is shortest.</p>
+    <p>This step <em class="rfc2119">may</em> be run concurrently with <a href="#council-participation">§ 5.6.2.3 Council Participation, Dismissal, and Renunciation</a> and prior to choosing a <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair①">Chair</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This is intended for exceptional cases
+	that don’t seem to warrant a full Council response
+	because they are, for instance, too trivial, duplicative, etc.</p>
+    <h5 class="heading settled" data-level="5.6.2.5" id="council-chairing"><span class="secno">5.6.2.5. </span><span class="content"> Council Chairing</span><a class="self-link" href="#council-chairing"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Council Chair | Council Chair" data-noexport id="w3c-council-chair">Chair</dfn> of each W3C Council is chosen by its members,
+	by consensus if possible,
+	falling back to a vote if that fails.
+	The chair must be a member of that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑦">W3C Council</a>.
+	Chair selection happens during formation of each Council,
+	and <em class="rfc2119">must</em> be re-run
+	if requested by the <a data-link-type="dfn" href="#council-staff-contact" id="ref-for-council-staff-contact">Council Staff Contact</a> or by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑧">Chair</a> during the Council’s operation.</p>
+    <h5 class="heading settled" data-level="5.6.2.6" id="council-convention"><span class="secno">5.6.2.6. </span><span class="content"> Convening the Council</span><a class="self-link" href="#council-convention"></a></h5>
+    <p>When <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed④">dismissal</a>, <a data-link-type="dfn" href="#renounce" id="ref-for-renounce②">renunciation</a>, and
+	appointment of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair②">W3C Council Chair</a> have concluded,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team⑦③">Team</a>’s report has been delivered,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑧">W3C Council</a> is considered to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="convened">convened</dfn> and can start <a href="#council-deliberations">deliberations</a>.</p>
+    <p>If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑨">W3C Council</a> has not yet been <a data-link-type="dfn" href="#convened" id="ref-for-convened">convened</a> within 90 days of a Formal Objection
+	being <a href="#registering-objections">registered</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑨">Chairs</a> of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③④">TAG</a> and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⓪">AB</a> <em class="rfc2119">may</em> take independent action to ensure
+	that the <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed⑤">dismissal</a>, <a data-link-type="dfn" href="#renounce" id="ref-for-renounce③">renunciation</a>,
+	and <a href="#council-chairing">chair selection</a> processes have been run.
+	If a report from the Team is not delivered within those 90 days,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⓪">Council</a> is considered <a data-link-type="dfn" href="#convened" id="ref-for-convened①">convened</a> upon selection of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair③">Council Chair</a>.</p>
+    <h5 class="heading settled" data-level="5.6.2.7" id="council-deliberations"><span class="secno">5.6.2.7. </span><span class="content"> Council Deliberations</span><a class="self-link" href="#council-deliberations"></a></h5>
+    <p>Once <a data-link-type="dfn" href="#convened" id="ref-for-convened②">convened</a>,
+	the Council <em class="rfc2119">may</em> conduct additional research or analysis,
+	or request additional information or interviews from anyone,
+	including the Team.</p>
+    <p id="broker-consensus"> The Council <em class="rfc2119">may</em> further attempt to broker consensus on one or more of the formal objections,
+	which, if successful, would allow them to be resolved. </p>
+    <p>Otherwise,
+	after sufficient deliberation,
+	and with due consideration of each argument in the applicable <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑤">Formal Objections</a>,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②①">W3C Council</a> decides whether to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="affirm">affirm</dfn> or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="overturn">overturn</dfn> the decision being objected to.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②②">W3C Council</a> <em class="rfc2119">may</em> <a data-link-type="dfn" href="#affirm" id="ref-for-affirm">affirm</a> the decision
+	even if it agrees with some of the arguments made as part of a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑥">Formal Objection</a>.
+	When a decision is <a data-link-type="dfn" href="#affirm" id="ref-for-affirm①">affirmed</a>,
+	all Formal Objections against it are said to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="overrule" data-noexport id="overrule">overruled</dfn>.
+	Conversely,
+	aspects of Formal Objections that are found by the Council
+	to justify <a data-link-type="dfn" href="#overturn" id="ref-for-overturn">overturning</a> a decision
+	are said to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="upheld">upheld</dfn>.</p>
+    <p id="fo-mitigations"> When <a data-link-type="dfn" href="#overturn" id="ref-for-overturn①">overturning</a> a decision,
+	it <em class="rfc2199">should</em> recommend a way forward.
+	If the overturned decision has already had consequences
+	pertaining to <a data-link-type="dfn" href="#upheld" id="ref-for-upheld">upheld</a> aspects of the Formal Objection(s)
+	(e.g., if the objection concerns material already in a published document)
+	the Council <em class="rfc2119">should</em> suggest how these consequences might be mitigated.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦④">Team</a> is responsible for making sure that adequate mitigations are enacted in a timely fashion;
+	and the <a data-link-type="dfn" href="#upheld" id="ref-for-upheld①">upheld</a> aspects of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑦">Formal Objection(s)</a> (as identified in the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report">Council Report</a>) are not considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fully-addressed">fully addressed</dfn> until then. </p>
+    <p class="note" role="note"><span class="marker">Note:</span> This does not create new powers for the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑤">Team</a>,
+	such as the ability to “unpublish” documents.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑥">Team</a>’s role is to ensure the responsible parties enact adequate mitigations,
+	by whatever means they already have at their disposal.</p>
+    <p>A Council <em class="rfc2119">may</em> form sub-groups for deliberation,
+	who may return with a recommendation,
+	but the full Council issues the final decision.
+	The decision of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②③">W3C Council</a> <em class="rfc2119">should</em> be unanimous,
+	and <em class="rfc2119">may</em> be issued under consensus.
+	However, if despite careful deliberation
+	a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②④">W3C Council</a> is unable to reach consensus,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair④">W3C Council Chair</a> may instead resort to voting.
+	In that case,
+	the decision is adopted if there are more ballots for than against;
+	in case of a tie,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑤">W3C Council Chair</a> determines the outcome.
+	However,
+	if the decision or proposal being objected to
+	originated with the TAG or AB,
+	then members of that group at the time the decision or proposal was made
+	must abstain in such a vote.
+	In case of a vote,
+	if two members of a Council who share the same affiliation cast an identical ballot,
+	then their ballots count as a one vote,
+	not two.</p>
+    <p>In the case of non-unanimous decisions,
+	members of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑤">W3C Council</a> who disagree with the Council’s decision <em class="rfc2119">may</em> write a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minority-opinion">Minority Opinion</dfn> explaining the reason for their disagreement.</p>
+    <p>The deliberations of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑥">W3C Council</a> are confidential to that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑦">W3C Council</a> and its <a data-link-type="dfn" href="#council-staff-contact" id="ref-for-council-staff-contact①">Council Staff Contact</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This confidentiality requirement is put in place so that
+	the Council can receive sensitive information in confidence
+	and to enable Council members to speak freely in their individual expert capacity
+	without pressure or fear of retaliation
+	by those involved in the dispute, business relations, their employer, etc.</p>
+    <p id="45-day-update"> If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑧">W3C Council</a> is unable to come to a conclusion within 45 days of being <a data-link-type="dfn" href="#convened" id="ref-for-convened③">convened</a>,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑥">W3C Council Chair</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑤">AC</a> of this delay
+	and of the status of the discussions.
+	The <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑦">W3C Council Chair</a> <em class="rfc2119">may</em> additionally make this report <a href="#confidentiality-levels">public</a>. </p>
+    <h5 class="heading settled" data-level="5.6.2.8" id="council-decision"><span class="secno">5.6.2.8. </span><span class="content"> Council Decision Report</span><a class="self-link" href="#council-decision"></a></h5>
+    <p>A <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑨">Council</a> terminates by issuing a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-report">Council Report</dfn>,
+	which:</p>
+    <ul>
+     <li data-md>
+      <p><em class="rfc2119">must</em> state whether the Council <a data-link-type="dfn" href="#affirm" id="ref-for-affirm②">affirms</a> or <a data-link-type="dfn" href="#overturn" id="ref-for-overturn②">overturns</a> the decision being objected to.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> provide a rationale supporting its conclusion,
+which <em class="rfc2119">should</em> address each argument raised in the Formal Objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include any recommendation decided by the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⓪">Council</a>.</p>
+     <li data-md>
+      <p>if the decision has been <a data-link-type="dfn" href="#overturn" id="ref-for-overturn③">overturned</a>, <em class="rfc2119">must</em> identify which aspects of the Formal Objection(s) are being <a data-link-type="dfn" href="#upheld" id="ref-for-upheld②">upheld</a>, and <em class="rfc2119">should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include the <a data-link-type="dfn" href="#minority-opinion" id="ref-for-minority-opinion">Minority Opinion(s)</a>, if any.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of those who were <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed⑥">dismissed</a> or <a data-link-type="dfn" href="#renounce" id="ref-for-renounce④">renounced</a> their seat as well as those who were qualified to serve.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of the individuals who participated in the final Council decision.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the number of votes for/against dismissing each participant.</p>
+     <li data-md>
+      <p><em class="rfc2119">may</em> report vote totals for the Council’s decision, if a formal vote was held.</p>
+     <li data-md>
+      <p><em class="rfc2119">must not</em> attribute any position to any individual on the Council.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑦">Team</a> <em class="rfc2119">must</em> maintain a <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/about/council/">public page on the W3C website</a> indexing all completed <a data-link-type="dfn" href="#council-report" id="ref-for-council-report①">Council Reports</a>.
+	If a Council decision is later overturned by an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal">AC Appeal</a>,
+	this <em class="rfc2119">must</em> also be mentioned. <a data-link-type="dfn" href="#council-report" id="ref-for-council-report②">Council Reports</a> <em class="rfc2119">must</em> be no more confidential
+	than the decision or document being objected to.</p>
+    <p>The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③①">Council</a> <em class="rfc2119">may</em> also issue a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="supplemental-confidential-council-report">Supplemental Confidential Council Report</dfn> with a more restricted <a href="#confidentiality-levels">level of confidentiality</a> than its main report
+	when it believes that additional commentary on confidential aspects of the case
+	would be informative.
+	However, the main <a data-link-type="dfn" href="#council-report" id="ref-for-council-report③">Council Report</a> <em class="rfc2119">should</em> be self-sufficient
+	and understandable without reference to Supplemental Confidential Council Reports.</p>
+    <h5 class="heading settled" data-level="5.6.2.9" id="council-appeals"><span class="secno">5.6.2.9. </span><span class="content"> Appealing Council Decisions</span><a class="self-link" href="#council-appeals"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑦">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①">Advisory Committee Appeal</a> of a Council decision issued in a <a data-link-type="dfn" href="#council-report" id="ref-for-council-report④">Council Report</a>.</p>
+    <h3 class="heading settled" data-level="5.7" id="ACReview"><span class="secno">5.7. </span><span class="content"> Advisory Committee Reviews and W3C Decisions</span><a class="self-link" href="#ACReview"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑥">Advisory Committee</a> formally confers its approval
+	on <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑤">charters</a>, <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③">technical reports</a>,
+	and other matters
+	through an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee review | AC Review" id="advisory-committee-review">Advisory Committee review</dfn> and its resulting <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑥">W3C Decision</a>.</p>
+    <h4 class="heading settled" data-level="5.7.1" id="ACReviewStart"><span class="secno">5.7.1. </span><span class="content"> Initiating an Advisory Committee Review</span><a class="self-link" href="#ACReviewStart"></a></h4>
+    <p>Each <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①③">Advisory Committee review</a> period
+	begins with a Call for Review from the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑧">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑦">Advisory Committee</a>.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="reviewform">Call for Review</dfn> describes the proposal,
+	raises attention to deadlines,
+	estimates when the decision will be available,
+	and includes other practical information.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑨">Team</a> <em class="rfc2119">may</em> share its perspective on the proposal
+	in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform">Call for Review</a>.
+	Each Member organization <em class="rfc2119">may</em> send one review,
+	which <em class="rfc2119">must</em> be returned by its <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑧">Advisory Committee representative</a>.</p>
+    <p>For clarity,
+	in the context of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①④">AC Review</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent②">dissent</a> <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑧">Formal Objection</a>.</p>
+    <p>The Team <em class="rfc2119">must</em> provide two channels for Advisory Committee review comments:</p>
+    <ol>
+     <li> an archived <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑥">Team-only</a> channel; 
+     <li> an archived <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only②">Member-only</a> channel. 
+    </ol>
+    <p>The <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform①">Call for Review</a> <em class="rfc2119">must</em> specify
+	which channel is the default for review comments on that Call.</p>
+    <p>Reviewers <em class="rfc2119">may</em> send information
+	to either or both channels.
+	A reviewer <em class="rfc2119">may</em> also share their own reviews
+	with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>,
+	and <em class="rfc2119">may</em> also make it available to the public.</p>
+    <p>A Member organization <em class="rfc2119">may</em> modify its review
+	during a review period
+	(e.g., in light of comments from other Members).</p>
+    <h4 class="heading settled" data-level="5.7.2" id="ACReviewAfter"><span class="secno">5.7.2. </span><span class="content"> Determining the W3C Decision</span><a class="self-link" href="#ACReviewAfter"></a></h4>
+    <p>After the review period,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⓪">Team</a> determines the appropriate <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑦">W3C Decision</a>,
+	which they <em class="rfc2119">must</em> announce to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑧">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate
+	the level of support for the proposal
+	(<a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⓪">consensus</a> or <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent③">dissent</a>),
+	and specifically
+	whether there were any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑨">Formal Objections</a>,
+	with attention to <a href="#confidentiality-change">changing the confidentiality level</a> of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⓪">Formal Objections</a>.</p>
+    <p>If there were <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③①">Formal Objections</a>, at least some of which were <a data-link-type="dfn" href="#upheld" id="ref-for-upheld③">upheld</a>,
+	or if there is not <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①①">consensus</a> because of insufficient support, <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑧">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to improve the proposal. 
+     <li> The proposal is rejected. 
+    </ul>
+    <p>If the proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①②">consensus</a>,
+	or if all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③②">Formal Objections</a> are retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule">overruled</a> and the proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①③">consensus</a>,
+	this <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑨">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is adopted,
+			possibly with additional changes integrated
+			in order to address the comments of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑨">AC</a> (see below). 
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to make desirable changes identified during the review
+			and to resubmit. 
+    </ul>
+    <p>If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>,
+	then those changes <em class="rfc2119">must</em> be announced to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⓪">AC</a> and to the <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group③">Group</a> that owns the document (if any).
+	Additionally, when adopting a proposal with <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①">substantive changes</a> integrated,
+	the announcement <em class="rfc2119">must</em> include rationale
+	for the substantive changes.</p>
+    <p><a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change②">Substantive changes</a> to the proposal <em class="rfc2119">may</em> be adopted
+	only if the revised proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①④">consensus</a> of the subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②①">AC</a> that voted on the initial proposal
+	(including anyone who explicitly abstained),
+	or if all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③③">Formal Objections</a> against the revised proposal are retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule①">overruled</a> and the revised proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑤">consensus</a>.
+	For clarity,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧①">Team</a> <em class="rfc2119">should</em> seek a response from this subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②②">AC</a> using the same tooling and degree of formality as it did for the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑤">AC Review</a>;
+	and as is the case during <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑥">AC Reviews</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent④">dissent</a> in this context <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③④">Formal Objection</a>.</p>
+    <p>Any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑤">Formal Objection</a> raised at this stage against the revised proposal
+	is handled by the same <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③②">Council</a> responsible for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑥">Formal Objections</a> raised against the initial proposal,
+	if any.</p>
+    <p>Such a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③③">Council</a> has the ability to <a data-link-type="dfn" href="#affirm" id="ref-for-affirm③">affirm</a> either the original or the revised proposal for advancement,
+	thereby <a data-link-type="dfn" href="#overrule" id="ref-for-overrule②">overruling</a> all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑦">Formal Objections</a> against the original or revised proposal,
+	respectively.</p>
+    <p>For publications which have conditions in addition to <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②③">AC</a> approval
+	for introducing <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change③">substantive changes</a> (such as <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group④">Group</a> consensus or implementation experience
+	or going through a patent <a data-link-type="dfn" href="https://www.w3.org/policies/patent-policy/#exclusion-opportunity" id="ref-for-exclusion-opportunity">Exclusion Opportunity</a>),
+	those other conditions must also be re-fulfilled.</p>
+    <div class="example" id="example-2c1b534e"><a class="self-link" href="#example-2c1b534e"></a> For example, if <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change④">substantive changes</a> to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④">technical report</a> are requested when assessing the transition from <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR">Candidate Recommendation</a> to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①">Recommendation</a>,
+		the technical report would need to go through a new <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests">Update Request</a> and be republished as a new <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①">Candidate Recommendation</a>;
+		that new version would then need to satisfy the criteria for advancement.
+		Alternatively, the desired changes can be introduced as non-substantive amendments
+		using the process for <a href="#revising-rec">revising a Recommendation</a>.
+		However, with the exception of the removal of at-risk features,
+		they cannot be directly integrated between <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot">CRS</a> and <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②">REC</a>,
+		because that would fail to trigger a patent exclusion opportunity. </div>
+    <p>For <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑥">charters</a>,
+	substantive changes from the initial proposal that underwent <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑦">AC Review</a> <em class="rfc2119">must not</em> include any increase to the scope.
+	If any such change is desired,
+	it <em class="rfc2119">must</em> be returned for additional work
+	and go through a complete new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑧">AC Review</a>.</p>
+    <p>This document does not specify
+	time intervals between the end of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑨">Advisory Committee review</a> period
+	and the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⓪">W3C decision</a>.
+	This is to ensure that the Members and <a data-link-type="dfn" href="#team" id="ref-for-team⑧②">Team</a> have sufficient time to consider comments
+	gathered during the review.
+	The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②④">Advisory Committee</a> <em class="rfc2119">should not</em> expect an announcement
+	sooner than <span class="time-interval">two weeks</span> after the end of a review period.
+	If, after <span class="time-interval">three weeks</span>, the outcome has not been announced,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧③">Team</a> <em class="rfc2119">should</em> provide the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑤">Advisory Committee</a> with an update.</p>
+    <h3 class="heading settled" data-level="5.8" id="ACVotes"><span class="secno">5.8. </span><span class="content"> Advisory Committee Votes</span><a class="self-link" href="#ACVotes"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑥">Advisory Committee</a> votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>,
+	and in the event of an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal②">Advisory Committee Appeal</a> achieving the required support to trigger an <a data-link-type="dfn" href="#appeal-vote" id="ref-for-appeal-vote①">appeal vote</a>.
+	Whenever the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑦">Advisory Committee</a> votes,
+	each Member or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member④">related Members</a> has one vote.</p>
+    <h3 class="heading settled" data-level="5.9" id="ACAppeal"><span class="secno">5.9. </span><span class="content"> Appeal by Advisory Committee Representatives</span><a class="self-link" href="#ACAppeal"></a></h3>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑨">Advisory Committee representatives</a> <em class="rfc2119">may</em> appeal certain decisions,
+	though appeals are only expected to occur in extraordinary circumstances.
+	For the purpose of this section, only <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⓪">Advisory Committee representatives</a> of <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member④">Members</a> in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing①">Good Standing</a> are counted.</p>
+    <p>When a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①①">W3C decision</a> is made following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⓪">Advisory Committee review</a>, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②①">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee Appeal|AC Appeal| Appeal" id="advisory-committee-appeal">Advisory Committee Appeal</dfn>.
+	These <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①②">W3C decisions</a> include those related to group creation and modification,
+	and transitions to new maturity stages for Recommendation Track documents
+	and the Process document.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②②">Advisory Committee representatives</a> <em class="rfc2119">may</em> also initiate an appeal
+	for decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③④">W3C Council</a>, and
+	for certain decisions that do not involve an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②①">Advisory Committee review</a>.
+	These cases are identified in the sections
+	which describe the requirements for the decision
+	and include
+	additional (non-reviewed) maturity stages of Recommendation Track documents,
+	group <a data-link-type="dfn" href="#dfn-charter-extension" id="ref-for-dfn-charter-extension">charter extensions</a> and closures,
+	and <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement">technical agreements</a>.</p>
+    <p>In all cases,
+	an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal③">appeal</a> <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the decision.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②③">Advisory Committee representative</a> initiates an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal④">appeal</a> by sending a request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑧④">Team</a>,
+	and should also share this request with the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑧">Advisory Committee</a>.
+	The request should say “I appeal this Decision”
+	and identify the decision,
+	and may also include their rationale for appealing the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a> for a recommendation
+	on how to communicate an appeal request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑤">Team</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑨">AC</a>.</p>
+    <p>Within one week the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑥">Team</a> <em class="rfc2119">must</em> announce the appeal process
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⓪">Advisory Committee</a> and provide a mechanism for <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②④">Advisory Committee representatives</a> to respond with a statement of positive support for this appeal.
+	The archive of these statements <em class="rfc2119">must</em> be <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only③">member-only</a>.
+	If, within <span class="time-interval">one week</span> of the Team’s announcement,
+	5% or more of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③①">Advisory Committee</a> support the appeal request,
+	the Team <em class="rfc2119">must</em> organize an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="appeal-vote">appeal vote</dfn> asking the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③②">Advisory Committee</a> “Do you approve of the Decision?”
+	together with links to the decision and the appeal support.</p>
+    <p>The ballot <em class="rfc2119">must</em> allow for three possible responses:
+	“Approve”,
+	“Reject”,
+	and “Abstain”,
+	together with Comments.</p>
+    <p>The level of support needed for an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑤">Advisory Committee Appeal</a> to pass
+	depends on the level of ballot participation 
+	(including explicit “abstain” ballots) 
+	by <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑤">Advisory Committee Representatives</a>:</p>
+    <ul>
+     <li data-md>
+      <p>if fewer than 5% participate,
+the vote fails.</p>
+     <li data-md>
+      <p>if at least 5% but no more than 15% participate,
+and the number of “Approve” ballots exceeds three times (3x) the number of “Reject” ballots,
+the vote passes.</p>
+     <li data-md>
+      <p>if more than 15% but fewer than 20% participate,
+and the number of “Approve” ballots exceeds twice (2x) the number of “Reject” ballots,
+the vote passes.</p>
+     <li data-md>
+      <p>if 20% or more participate,
+and the number of “Approve” ballots exceeds the number of “Reject” ballots,
+the vote passes.</p>
+    </ul>
+    <p>If the vote passes,
+	the decision is overturned.
+	Following such rejection,
+	those who had initiated the proposal may revise it
+	to address the causes of rejection
+	and follow the ordinary applicable process
+	to submit the revised proposal.</p>
+    <h2 class="heading settled" data-level="6" id="Reports"><span class="secno">6. </span><span class="content"> W3C Technical Reports</span><a class="self-link" href="#Reports"></a></h2>
+    <p>The W3C technical report development process is the set of steps and requirements
+	followed by W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑤">Working Groups</a> to standardize Web technology.
+	The W3C technical report development process is designed to:</p>
+    <ul>
+     <li> support multiple specification development methodologies 
+     <li> maximize <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑥">consensus</a> about the content of stable technical reports 
+     <li> ensure high technical and editorial quality 
+     <li> promote consistency among specifications 
+     <li> facilitate royalty-free, interoperable implementations of Web Standards, and 
+     <li> earn endorsement by W3C and the broader community. 
+    </ul>
+    <p>See also “licensing goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.1" id="recs-and-notes"><span class="secno">6.1. </span><span class="content"> Types of Technical Reports</span><a class="self-link" href="#recs-and-notes"></a></h3>
+    <p>This chapter describes the formal requirements
+	for <a data-link-type="dfn" href="#publishing" id="ref-for-publishing">publishing</a> and maintaining a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③">W3C Recommendation</a>, <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑧">Note</a>,
+	or <a data-link-type="dfn" href="#registry" id="ref-for-registry">Registry</a>.</p>
+    <dl>
+     <dt>Recommendations 
+     <dd> <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑥">Working Groups</a> develop technical reports on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①">W3C Recommendation Track</a> in order to produce normative specifications or guidelines
+			as standards for the Web.
+			The <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track②">Recommendation Track</a> process incorporates requirements for <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review②">wide review</a>, <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation">adequate implementation experience</a>,
+			and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑦">consensus</a>-building,
+			and is subject to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			under which participants commit to Royalty-Free IPR licenses for implementations.
+			See <a href="#rec-track">§ 6.3 The W3C Recommendation Track</a> for details. 
+     <dt>Notes 
+     <dd> Groups can also publish documents as <a data-link-type="dfn" href="https://www.w3.org/policies/process/#WGNote" id="ref-for-WGNote①">W3C Notes</a> and <a data-link-type="dfn" href="#statement" id="ref-for-statement">W3C Statements</a>,
+			typically either to document information
+			other than technical specifications,
+			such as use cases motivating a specification
+			and best practices for its use.
+			See <a href="#note-track">§ 6.4 The Note Track (Notes and Statements)</a> for details. 
+     <dt>Registries 
+     <dd> <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group③">Chartered</a> and <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group">elected groups</a> can also publish <a data-link-type="dfn" href="#registry" id="ref-for-registry①">registries</a> in order to document collections of values or other data.
+			A registry can be published either as a distinct <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report">registry report</a>,
+			or directly within a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track③">Recommendation Track</a> document
+			as an <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry">embedded registry</a>. <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition">Defining a registry</a> requires <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review③">wide review</a> and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑧">consensus</a>,
+			but once set up, changes to registry entries are lightweight
+			and can even be done without the initiating group’s involvement.
+			See <a href="#registries">§ 6.5 The Registry Track</a> for details. 
+    </dl>
+    <p>Individual <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑦">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑨">Interest Groups</a> <em class="rfc2119">should</em> adopt additional processes
+	for developing publications,
+	so long as they do not conflict with the requirements in this chapter.</p>
+    <h3 class="heading settled" data-level="6.2" id="general-requirements"><span class="secno">6.2. </span><span class="content"> General Requirements for Technical Reports</span><a class="self-link" href="#general-requirements"></a></h3>
+    <h4 class="heading settled" data-level="6.2.1" id="publication"><span class="secno">6.2.1. </span><span class="content"> Publication of Technical Reports</span><a class="self-link" href="#publication"></a></h4>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="publish" data-noexport id="publishing">Publishing</dfn> as used in this document
+	refers to producing a version which is listed as a W3C <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="technical-report">Technical Report</dfn> on its <a href="https://www.w3.org/TR/">Technical Reports index at https://www.w3.org/TR</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a>.
+	Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public document.
+	W3C strives to make archival documents indefinitely available
+	at their original address in their original form.</p>
+    <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate its <a href="#maturity-stages">maturity stage</a>,
+	and <em class="rfc2119" id="DocumentStatus">must</em> include information about the status of the document.
+	This status information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> be unique each time a specification is <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①">published</a>, 
+     <li> <em class="rfc2119">must</em> state which <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑧">Working Group</a> developed the specification, 
+     <li> <em class="rfc2119">must</em> state how to send comments or file bugs,
+			and where these are recorded, 
+     <li> <em class="rfc2119">must</em> include expectations about next steps, 
+     <li> <em class="rfc2119">should</em> explain how the technology relates to existing international standards
+			and related work inside or outside W3C,
+			and 
+     <li> <em class="rfc2119">should</em> explain
+			or link to
+			an explanation of significant changes from the previous version. 
+    </ul>
+    <p>Every Technical Report published
+	as part of the Technical Report development process
+	is edited by one or more editors
+	appointed by a Group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③⓪">Chair</a>.
+	It is the responsibility of these editors to ensure that the decisions of the Group are
+	correctly reflected in subsequent drafts of the technical report.
+	An editor <em class="rfc2119">must</em> be a participant,
+	per <a href="#group-participation">§ 3.4.2 Participation in Chartered Groups</a> in the Group responsible for the document(s) they are editing.</p>
+    <p>The Team is <em class="rfc2119">not required</em> to publish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑤">Technical Report</a> that does not conform to the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules" title="Publication Rules">[PUBRULES]</a> (e.g., for <span id="DocumentName">naming</span>,
+	status information,
+	style,
+	and <span id="document-copyright">copyright requirements</span>).
+	These rules are subject to change by the Team from time to time.
+	The Team <em class="rfc2119">must</em> inform group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③①">Chairs</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③③">Advisory Committee</a> of any changes to these rules.</p>
+    <p>The primary language for W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑥">Technical Reports</a> is English.
+	W3C encourages the translation of its <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑦">Technical Reports</a>. <a href="https://www.w3.org/Consortium/Translation/">Information about translations of W3C technical reports</a> <a data-link-type="biblio" href="#biblio-translation" title="Translations of W3C technical reports">[TRANSLATION]</a> is available at the W3C website.</p>
+    <h4 class="heading settled" data-level="6.2.2" id="doc-reviews"><span class="secno">6.2.2. </span><span class="content"> Reviews and Review Responsibilities</span><a class="self-link" href="#doc-reviews"></a></h4>
+    <p>A document is available for review
+	from the moment it is first <a data-link-type="dfn" href="#publishing" id="ref-for-publishing②">published</a>.
+	Working Groups <em class="rfc2119">should</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed①">formally address</a> <em>any</em> substantive review comment
+	about a technical report in a timely manner.</p>
+    <p>Reviewers <em class="rfc2119">should</em> send substantive technical reviews as early as possible. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑨">Working Groups</a> are often reluctant to make <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑤">substantive changes</a> to a mature document,
+	particularly if this would cause significant compatibility problems
+	due to existing implementation. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⓪">Working Groups</a> <em class="rfc2119">should</em> record substantive
+	or interesting proposals raised by reviews
+	but not incorporated into a current specification.</p>
+    <h5 class="heading settled" data-level="6.2.2.1" id="wide-review"><span class="secno">6.2.2.1. </span><span class="content"> Wide Review</span><a class="self-link" href="#wide-review"></a></h5>
+    <p>The requirements for <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="dfn-wide-review">wide review</dfn> are not precisely defined by the W3C Process.
+	The objective is to ensure that the entire set of stakeholders of the Web community,
+	including the general public,
+	have had adequate notice of the progress of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②①">Working Group</a> and were able to actually perform reviews of and provide comments on the specification.
+	A second objective is to encourage groups to request reviews
+	early enough that comments and suggested changes
+	can still be reasonably incorporated in response to the review.
+	Before approving transitions,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑦">Team</a> will consider who has been explicitly offered
+	a reasonable opportunity to review the document,
+	who has provided comments,
+	the record of requests to and responses from reviewers,
+	especially <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a> and groups identified as dependencies in the charter
+	or identified as <a href="https://www.w3.org/liaisons/">liaisons</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a>,
+	and seek evidence of clear communication to the general public
+	about appropriate times and which content to review
+	and whether such reviews actually occurred.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The Team documents <a href="https://www.w3.org/guide/documentreview/">best practices for wide review</a> in the Guidebook. <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a></p>
+    <p>For example,
+	inviting review of new or significantly revised sections published in Working Drafts,
+	and tracking those comments
+	and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②②">Working Group</a>’s responses,
+	is generally a good practice which would often be considered positive evidence of wide review. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②③">Working Groups</a> <em class="rfc2119">should</em> follow the <a href="https://www.w3.org/guide/documentreview/#how-to-get-horizontal-review">W3C Horizontal Groups</a>’ review processes,
+	and <em class="rfc2119">should</em> announce to other W3C Working Groups
+	as well as the general public,
+	especially those affected by this specification,
+	a proposal to enter <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②">Candidate Recommendation</a> (for example in approximately 28 days).
+	By contrast a generic statement in a document
+	requesting review at any time
+	is likely not to be considered as sufficient evidence
+	that the group has solicited wide review.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②④">Working Group</a> could present evidence that wide review has been received,
+	irrespective of solicitation.
+	But it is important to note that receiving many detailed reviews
+	is not necessarily the same as wide review,
+	since they might only represent comment
+	from a small segment of the relevant stakeholder community.</p>
+    <h4 class="heading settled" data-level="6.2.3" id="correction-classes"><span class="secno">6.2.3. </span><span class="content"> Classes of Changes</span><a class="self-link" href="#correction-classes"></a></h4>
+    <p>This document distinguishes the following 5 classes of changes to a document.
+	The first two classes of change are considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="editorial change" data-noexport id="editorial-change">editorial changes</dfn>,
+	the next two <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="substantive change" data-noexport id="substantive-change">substantive changes</dfn>,
+	and the last one <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="registry change" data-noexport id="registry-change">registry changes</dfn>.</p>
+    <dl>
+     <dt id="class-1">
+      <a class="self-link" href="#class-1"></a> 
+      <ol>
+       <li data-md>
+        <p>No changes to text content</p>
+      </ol>
+     <dd> These changes include fixing broken links, style sheets, or invalid markup. 
+     <dt id="class-2">
+      <a class="self-link" href="#class-2"></a> 
+      <ol start="2">
+       <li data-md>
+        <p>Changes that do not functionally affect interpretation of the document</p>
+      </ol>
+     <dd> For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track④">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑧">technical reports</a> specifically,
+			this constitutes changes that do not affect conformance,
+			i.e. changes that reasonable implementers
+			would not interpret as changing architectural
+			or interoperability requirements
+			or their implementation.
+			Changes which resolve ambiguities in the specification
+			are considered to change (by clarification) the implementation requirements
+			and do not fall into this class. 
+     <dd> Examples of changes in this class include
+			correcting non-normative examples
+			which clearly conflict with normative requirements,
+			clarifying various other non-normative text,
+			fixing typos or grammatical errors
+			where the change does not change requirements. 
+     <dd> If there is any doubt or disagreement
+			as to whether a change functionally affects interpretation,
+			that change does not fall into this class. 
+     <dt id="class-3">
+      <a class="self-link" href="#class-3"></a> 
+      <ol start="3">
+       <li data-md>
+        <p>Other changes that do not add new features</p>
+      </ol>
+     <dd>
+       For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑤">Recommendation-track</a> documents,
+			these changes <em class="rfc2119">may</em> affect conformance to the specification.
+			A change that affects conformance is one that: 
+      <ul>
+       <li> makes conforming data, processors, or other conforming agents become non-conforming according to the new version,
+					or 
+       <li> makes non-conforming data, processors, or other agents become conforming,
+					or 
+       <li> clears up an ambiguity or under-specified part of the specification
+					in such a way that data,
+					a processor,
+					or an agent
+					whose conformance was once unclear
+					becomes clearly either conforming or non-conforming. 
+      </ul>
+     <dt id="class-4">
+      <a class="self-link" href="#class-4"></a> 
+      <ol start="4">
+       <li data-md>
+        <p>New features</p>
+      </ol>
+     <dd> Changes that add new functionality,
+			such as new elements, new APIs, new rules, etc. 
+     <dt id="class-5">
+      <a class="self-link" href="#class-5"></a> 
+      <ol start="5">
+       <li data-md>
+        <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table">registry table</a></p>
+      </ol>
+     <dd> Changes that add, remove, or alter <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry">registry entries</a> in a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①">registry table</a>. 
+    </dl>
+    <h4 class="heading settled" data-level="6.2.4" id="errata"><span class="secno">6.2.4. </span><span class="content"> Errata Management</span><a class="self-link" href="#errata"></a></h4>
+    <p>Tracking errors is an important part of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑤">Working Group</a>’s ongoing care of a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑨">technical report</a>;
+	for this reason,
+	the scope of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑥">Working Group</a> charter generally allows time
+	for work after publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④">Recommendation</a>.
+	In this Process Document,
+	the term “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="erratum | errata" id="erratum">erratum</dfn>”
+	(plural “errata”) refers to any error
+	that can be resolved by one or more changes in classes 1-3
+	of section <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑦">Working Groups</a> <em class="rfc2119">must</em> keep
+	a public record of errors
+	that are reported by readers and implementers
+	for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤">Recommendations</a>.
+	Such error reports <em class="rfc2119">should</em> be compiled
+	no less frequently than quarterly.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑧">Working Groups</a> decide how to document errata.
+	Such documentation <em class="rfc2119">must</em> identify
+	the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⓪">technical report</a> text
+	and describe the error;
+	it <em class="rfc2119">may</em> also describe some possible solution(s).
+	Readers of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①①">technical report</a> <em class="rfc2119">should</em> be able easily
+	to find and see the errata
+	that apply to that specific <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①②">technical report</a> with their associated tests.
+	Errata <em class="rfc2119">may</em> be documented
+	in a separate errata page or tracking system.
+	They <em class="rfc2119">may</em>,
+	in addition or alternatively,
+	be annotated inline
+	alongside the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①③">technical report</a> text
+	or at the start or end of the most relevant section(s).</p>
+    <h4 class="heading settled" data-level="6.2.5" id="candidate-amendments"><span class="secno">6.2.5. </span><span class="bs-old-id" id="candidate-changes"></span><span class="content"> Candidate Amendments</span><a class="self-link" href="#candidate-amendments"></a></h4>
+    <p>An <a data-link-type="dfn" href="#erratum" id="ref-for-erratum">erratum</a> <em class="rfc2119">may</em> be accompanied by a non-normative, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-correction">candidate correction</dfn> approved by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision②">group decision</a>.
+	When annotated inline,
+	errata—​including their <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction">candidate corrections</a>—​must be marked as such,
+	are treated as <a href="#correction-classes">class 2 changes</a>,
+	and are published accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Annotating changes in this way allows more mature documents
+	such as <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥">Recommendations</a> and <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR③">Candidate Recommendations</a> to be updated quickly with the Working Group’s most current thinking,
+	even when the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment">candidate amendments</a> have not yet received
+	sufficient review or implementation experience
+	to be normatively incorporated into the specification proper.</p>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-addition">candidate addition</dfn> is similar to a <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction①">candidate correction</a>,
+	except that it proposes a new feature
+	rather than an error correction.</p>
+    <p><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction②">Candidate corrections</a> and <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition">candidate additions</a> are collectively known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="candidate amendment" data-noexport id="candidate-amendment">candidate amendments</dfn>.</p>
+    <p>In addition to their actual <a href="#maturity-stages">maturity stage</a>, <a data-link-type="dfn" href="#publishing" id="ref-for-publishing③">published</a> <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑥">REC Track</a> documents with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①">candidate amendments</a> are also considered,
+	for the purpose of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	to be <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①">Working Drafts</a> with those <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment②">candidate amendments</a> treated as normative.</p>
+    <h4 class="heading settled" data-level="6.2.6" id="no-group-maintenance"><span class="secno">6.2.6. </span><span class="content"> Maintenance Without a Group</span><a class="self-link" href="#no-group-maintenance"></a></h4>
+    <p>For all <a href="#recs-and-notes">types of technical reports</a> and all <a href="#maturity-stages">maturity stages</a>,
+	if there is no <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group④">group</a> chartered to maintain a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①④">technical report</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑧">Team</a> <em class="rfc2119">may</em> republish it
+	at the same <a href="#maturity-stages">maturity stage</a>,
+	integrating as needed:</p>
+    <ol>
+     <li><a href="#correction-classes">class 1 changes</a>; 
+     <li>inline <a data-link-type="dfn" href="#erratum" id="ref-for-erratum①">errata</a>; 
+     <li><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction③">candidate corrections</a>,
+			which <em class="rfc2119">must</em> be marked as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="team-correction">Team correction</dfn>; 
+     <li><a href="#correction-classes">class 2 changes</a> other than inline <a data-link-type="dfn" href="#erratum" id="ref-for-erratum②">errata</a> and <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction">Team corrections</a>. 
+    </ol>
+    <p>To avoid any potential doubt or disagreement
+	about whether changes really do fall into <a href="#correction-classes">class 2</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑨">Team</a> <em class="rfc2119">should</em> be conservative,
+	limiting itself to obvious and limited fixes,
+	and <em class="rfc2119">must</em> avoid substantial rephrasing,
+	even of non-normative examples and notes.
+	If any such change is desired,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⓪">Team</a> <em class="rfc2119">must</em> mark it as a <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction①">Team correction</a>.</p>
+    <p><a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction②">Team corrections</a> do not constitute
+	a normative portion of the Recommendation,
+	as defined in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (i.e., they are not covered by the Patent Policy).
+	For <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR④">Candidate Recommendations</a>, <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦">W3C Recommendations</a>, <a data-link-type="dfn" href="#candidate-registry" id="ref-for-candidate-registry">Candidate Registries</a>, <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry">W3C Registries</a>,
+	as well as <a data-link-type="dfn" href="#statement" id="ref-for-statement①">W3C Statements</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨①">Team</a> <em class="rfc2119">must</em> solicit <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review④">wide review</a> on <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction③">Team corrections</a> that it produces.</p>
+    <h4 class="heading settled" data-level="6.2.7" id="contributor-license"><span class="secno">6.2.7. </span><span class="content"> License Grants from Non-Participants</span><a class="self-link" href="#contributor-license"></a></h4>
+    <p>When a party who is not already obligated under the Patent Policy
+	offers a change in class 3 or 4
+	(as described in <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>) to a technical report under this process
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨②">Team</a> <em class="rfc2119">must</em> request
+	a recorded royalty-free patent commitment;
+	for a change in class 4, the Team <em class="rfc2119">must</em> secure such commitment.
+	Such commitment <em class="rfc2119">should</em> cover,
+	at a minimum,
+	all the party’s Essential Claims both in the contribution,
+	and that become Essential Claims as a result of incorporating the contribution into the draft
+	that existed at the time of the contribution,
+	on the terms specified in the “W3C Royalty-Free (RF) Licensing Requirements” section of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.3" id="rec-track"><span class="secno">6.3. </span><span class="bs-old-id" id="rec-advance"></span><span class="content"> The W3C Recommendation Track</span><a class="self-link" href="#rec-track"></a></h3>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑨">Working Groups</a> create specifications and guidelines
+	to complete the scope of work envisioned by a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⓪">Working Group</a>’s <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑦">charter</a>.
+	These <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑤">technical reports</a> undergo cycles of revision and review
+	as they advance towards <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑧">W3C Recommendation</a> status.
+	Once review suggests the Working Group has met their requirements for a new standard,
+	including <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑤">wide review</a>,
+	a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑤">Candidate Recommendation</a> phase
+	allows the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③①">Working Group</a> to formally collect <a href="#implementation-experience">implementation experience</a> to demonstrate that the specification works in practice.
+	At the end of the process,
+	the Advisory Committee reviews the mature technical report,
+	and if there is support from its Membership,
+	W3C publishes it as a <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑥">Recommendation</a>.</p>
+    <p>In summary, the <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track" data-noexport id="w3c-recommendation-track">W3C Recommendation Track</dfn> consists of:</p>
+    <ol>
+     <li>Publication of the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd①">First Public Working Draft</a>. 
+     <li>Publication of zero or more revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD②">Working Drafts</a>. 
+     <li>Publication of one or more <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑥">Candidate Recommendations</a>. 
+     <li>Publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑨">W3C Recommendation</a>. 
+    </ol>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document" id="w3c-recommendation-track-document">W3C Recommendation Track document</dfn> is any document whose current status is one of the four in the numbered list above.</p>
+    <figure>
+     <svg viewBox="-5 30 457 175" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Basic W3C Recommendation Track</title>
+      <g role="list">
+       <g fill="#060" role="listitem">
+        <a href="#wd-1">
+         <rect fill="white" height="45" role="img" width="57" y="122">
+          <title>First Public Working Draft (FPWD) - Exclusion opportunity</title>
+         </rect>
+         <text font-size="8">
+          <tspan aria-hidden="true" x="0" y="132">First Public WD</tspan>
+          <tspan x="0" y="152">WG Decision +</tspan>
+          <tspan x="0" y="160">Team Approval</tspan>
+         </text>
+         <path d="M0,140h53" fill="none" stroke="#060"></path>
+         <polygon points="47,136 57,140 47,144"></polygon>
+        </a>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="97" cy="140" fill="#fff" id="wd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Working Draft (WD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="97" y="144">WD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Publish a new Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="97" y="100">WG Decision</tspan>
+           </text>
+           <path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114" fill="none" stroke="black" stroke-dasharray="6 2"></path>
+           <polygon points="120,114 116,124 114,113"></polygon>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Advance to Candidate Recommendation</title>
+           </g>
+           <text font-size="8" x="135" y="129">WG Decision +</text>
+           <text font-size="8" x="135" y="137">Team Approval</text>
+           <path d="M135,140h81" stroke="#060"></path>
+           <polygon points="211,136 221,140 211,144"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="260" cy="140" fill="#fff" id="cr-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="144">CRS</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="232" y="118">WG</tspan>
+            <tspan x="232" y="126">Decision</tspan>
+           </text>
+           <path d="M234,127v-34" stroke="#000"></path>
+           <polygon points="234,92 230,102 238,102"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="99">WG Decision</tspan>
+            <tspan x="290" y="107">Team Approval</tspan>
+           </text>
+           <path d="M242,124C238,114 244,104 260,104 271,104 285,108 286,117" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#rec-1">
+           <g role="img">
+            <title>Advance to Recommendation</title>
+           </g>
+           <text font-size="8" x="298" y="121">WG Decision +</text>
+           <text font-size="8" x="298" y="129">Team Approval +</text>
+           <text font-size="8" x="298" y="137">AC Review</text>
+           <path d="M298,140h77" stroke="#060"></path>
+           <polygon points="374,136 384,140 374,144"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="228" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="228" y="165">(or Team Decision with AB+TAG Approval)</tspan>
+           </text>
+           <path d="M140,147h84" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="140,145 133,147 140,149"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="260" cy="80" fill="#fff" id="crd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Draft (CRD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="84">CRD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="259" y="41">WG Decision</tspan>
+           </text>
+           <path d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="282,54 277,64 275,53"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="99">WG Decision +</tspan>
+            <tspan x="290" y="107">Team Approval</tspan>
+           </text>
+           <path d="M286,127v-34" stroke="#000"></path>
+           <polygon points="286,128 282,118 290,118"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="413" cy="140" fill="#fff" id="rec-1" role="img" rx="28" ry="18" stroke="black" stroke-width="2">
+          <title>Recommendation</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="413" y="144">REC</text>
+        </a>
+        <g role="list">
+         <g fill="#900" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Return to Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8" text-anchor="start">
+            <tspan x="342" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="342" y="165">(or Team Decision</tspan>
+            <tspan font-size="6" x="342" y="173">with AB+TAG</tspan>
+            <tspan font-size="6" x="342" y="181">Approval)</tspan>
+           </text>
+           <path d="M301,147h88" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="301,145 296,147 301,149"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="start">
+            <tspan x="342" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="342" y="165">(or Team Decision</tspan>
+            <tspan font-size="6" x="342" y="173">with AB+TAG</tspan>
+            <tspan font-size="6" x="342" y="181">Approval)</tspan>
+           </text>
+           <path d="M339,147v41h-242v-26" fill="none" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="95,164 97,159 99,164"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a fill="#000" href="#rec-1">
+           <g role="img">
+            <title>Publish revised Recommendation with editorial changes</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="413" y="103">WG Decision</tspan>
+            <tspan font-size="6" x="413" y="116">(editorial)</tspan>
+           </text>
+           <path d="M395,127C391,117 397,107 413,107 424,107 430,111 432,117" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="435,117 430,127 428,116"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a fill="#000" href="#rec-1">
+           <g role="img">
+            <title>Publish revised Recommendation with substantive changes</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="413" y="184">WG Decision +</tspan>
+            <tspan x="413" y="192">Team Approval +</tspan>
+            <tspan x="413" y="200">AC Review</tspan>
+            <tspan font-size="6" x="413" y="169">(substantive)</tspan>
+           </text>
+           <path d="M395,155C391,166 397,176 413,176 424,176 431,173 431,165" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="435,164 430,155 428,165"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+     <figcaption>Non-Normative Summary of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑦">Recommendation Track</a></figcaption>
+    </figure>
+    <p>This Process defines certain <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑧">Recommendation Track</a> publications as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="patent-review-drafts">Patent Review Drafts</dfn>.
+	Under the 2004 Patent Policy (and its 2017 update) <a data-link-type="biblio" href="#biblio-patent-policy-2004" title="The W3C 2004 Patent Policy, Updated 2017">[PATENT-POLICY-2004]</a>,
+	these correspond to “Last Call Working Draft” in the Patent Policy;
+	Starting from the 2020 Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy-2020" title="The W3C 2020 Patent Policy">[PATENT-POLICY-2020]</a>,
+	these correspond to “Patent Review Draft” in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.</p>
+    <p>As described in <a href="#transition-reqs">§ 6.3.3 Advancement on the Recommendation Track</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨③">Team</a> will decline a request to advance in maturity stage
+	and return the specification to a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③②">Working Group</a> for further work
+	if it determines that the requirements for advancement
+	have not been met.</p>
+    <h4 class="heading settled" data-level="6.3.1" id="maturity-stages"><span class="secno">6.3.1. </span><span class="content"> Maturity Stages on the Recommendation Track</span><a class="self-link" href="#maturity-stages"></a></h4>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Working Draft | Working Draft | WD" id="RecsWD">Working Draft</dfn> (<abbr>WD</abbr>) 
+     <dd>
+       A Working Draft is a document that W3C has <a data-link-type="dfn" href="#publishing" id="ref-for-publishing④">published</a> on the <a href="https://www.w3.org/TR/">W3C’s Technical Reports page</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a> for review by the community (including W3C Members), the public,
+			and other technical organizations,
+			and for simple historical reference.
+			Some, but not all, Working Drafts are meant to advance to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⓪">Recommendation</a>;
+			see the <a href="#DocumentStatus">document status section</a> of a Working Draft
+			for the group’s expectations. <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD③">Working Drafts</a> do not necessarily represent a <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑨">consensus</a> of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③③">Working Group</a> with respect to their content,
+			and do not imply any endorsement by W3C
+			or its members beyond agreement to work on a general area of technology.
+			Nevertheless the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③④">Working Group</a> decided to adopt the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD④">Working Draft</a> as the basis for their work at the time of adoption.
+			A <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑤">Working Draft</a> is suitable for gathering <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑥">wide review</a> prior to advancing to the next stage of maturity. 
+      <p>For all Working Drafts a Working Group:</p>
+      <ul>
+       <li> <em class="rfc2119">should</em> document outstanding issues,
+					and parts of the document on which the Working Group does not have consensus,
+					and 
+       <li> <em class="rfc2119">may</em> request publication of a Working Draft
+					even if its content is considered unstable
+					and does not meet all Working Group requirements. 
+      </ul>
+      <p>The first Working Draft of a technical report is called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="fpwd">First Public Working Draft</dfn> (<abbr>FPWD</abbr>),
+			and has patent implications as defined in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Candidate Recommendation | Candidate Recommendation | CR" id="RecsCR">Candidate Recommendation</dfn> (<abbr>CR</abbr>) 
+     <dd>
+       A Candidate Recommendation is a document that satisfies the technical
+			requirements of the Working Group that produced it and their dependencies,
+			and has already received wide review.
+			W3C publishes a Candidate Recommendation to 
+      <ul>
+       <li> signal to the wider community that it is time to do a final review 
+       <li> gather <a href="#implementation-experience">implementation experience</a> 
+      </ul>
+      <p class="note" role="note"><span class="marker">Note:</span> Advancing to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑦">Candidate Recommendation</a> indicates
+			that the document is considered complete and fit for purpose,
+			and that no further refinement to the text is expected
+			without additional implementation experience and testing;
+			however, additional features might be expected in a later revision.
+			A <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑧">Candidate Recommendation</a> is expected to be as well-written,
+			detailed,
+			self-consistent,
+			and technically complete
+			as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①①">Recommendation</a>,
+			and acceptable as such
+			if and when the requirements for further advancement are met.</p>
+      <p>Candidate Recommendation publications take one of two forms:</p>
+      <dl>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Snapshot | CRS" id="candidate-recommendation-snapshot">Candidate Recommendation Snapshot</dfn> (<abbr>CRS</abbr>) 
+       <dd>
+         A Candidate Recommendation Snapshot
+					corresponds to a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts">Patent Review Draft</a> as used in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+					Publishing a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts①">Patent Review Draft</a> triggers a Call for Exclusions,
+					per “Exclusion From W3C RF Licensing Requirements”
+					in the W3C Patent Policy. 
+        <p>Publication as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①">Candidate Recommendation Snapshot</a> requires verification of either a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req">Transition Request</a> (for the first <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑨">Candidate Recommendation</a> publication from another maturity stage)
+					or an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①">Update Request</a> (for subsequent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot②">Candidate Recommendation Snapshots</a>).</p>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Draft | CRD" id="candidate-recommendation-draft">Candidate Recommendation Draft</dfn> (<abbr>CRD</abbr>) 
+       <dd>
+         A Candidate Recommendation Draft
+					is published
+					to solicit review of intended changes from the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot③">Candidate Recommendation Snapshot</a>.
+					This allows for wider review of the changes
+					and for ease of reference to the integrated specification. 
+        <p>Any changes published directly into a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft">Candidate Recommendation Draft</a> should be at the same level of quality as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot④">Candidate Recommendation Snapshot</a>.
+					However, the process requirements are minimized
+					so that the Working Group can easily keep the specification up to date.</p>
+        <p>A <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft①">Candidate Recommendation Draft</a> <em>does not</em> provide an exclusion opportunity;
+					instead, it is considered a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑥">Working Draft</a> for the purpose of the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+      </dl>
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rescinded-candidate-recommendation">Rescinded Candidate Recommendation</dfn> is a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⓪">Candidate Recommendation</a> in which significant problems have been discovered
+			such that W3C cannot endorse it or continue work on it,
+			for example due to burdensome patent claims that affect implementers and cannot be resolved
+			(see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “PAG Conclusion”).
+			There is no path to restoration for a <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a>.
+			See “W3C Royalty-Free (RF) Licensing Requirements”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for implication on patent licensing obligations.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation | Recommendation | REC" id="RecsW3C">W3C Recommendation</dfn> (<abbr>REC</abbr>) 
+     <dd>
+       A W3C Recommendation is a specification
+			or set of guidelines
+			or requirements that,
+			after extensive <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②⓪">consensus</a>-building,
+			has received the endorsement of W3C and its Members.
+			W3C recommends the wide deployment
+			of its Recommendations as standards for the Web.
+			The W3C Royalty-Free IPR licenses
+			granted under the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> apply to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①②">W3C Recommendations</a>. 
+      <p id="expandable-rec"> After its initial publication,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①③">W3C Recommendation</a> <em class="rfc2119">may</em> be revised
+			(in accordance with <a href="#revising-rec">§ 6.3.10 Revising a W3C Recommendation</a>)
+			to address <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①">editorial</a> or <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑥">substantive</a> issues
+			that are discovered later.
+			However, <a href="#class-4">new features</a> can only be added
+			if the document already identifies itself
+			as intending to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="allow-new-features">allow new features</dfn>.
+			Adding or removing this allowance is a <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑦">substantive change</a>.
+			Such an allowance cannot be added
+			to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑥">technical report</a> previously published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①④">Recommendation</a> that did not allow such changes;
+			this requires a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑦">technical report</a> (which could, for example, be similarly named but with an incremented version number). </p>
+      <p>As technology evolves,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑤">W3C Recommendation</a> may become:</p>
+      <dl>
+       <dt> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsSup">Superseded Recommendation</dfn> 
+       <dd>
+         A Superseded Recommendation is a specification
+					that has been replaced by a newer version
+					that W3C recommends for new adoption.
+					An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs">Obsolete</a> or Superseded specification
+					has the same status as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑥">W3C Recommendation</a> with regards to W3C Royalty-Free IPR Licenses granted under the Patent Policy. 
+        <p class="note" role="note"><span class="marker">Note:</span> When a Technical Report which had previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑦">Recommendation</a> is again published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑧">Recommendation</a> after following the necessary steps to <a href="#revising-rec">revise</a> it,
+					the latest version replaces the previous one,
+					without the need to invoke the steps of <a href="#rec-rescind">§ 6.3.12.3 Abandoning a W3C Recommendation</a>:
+					it is the same document, updated.
+					Explicitly declaring a documented superseded, using the process documented in <a href="#rec-rescind">§ 6.3.12.3 Abandoning a W3C Recommendation</a>,
+					is intended for cases where a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑨">Recommendation</a> is superseded by a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑧">Technical Report</a> (or by a document managed outside of W3C).</p>
+       <dt> An <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsObs">Obsolete Recommendation</dfn> 
+       <dd> An Obsolete Recommendation is a specification
+					that W3C has determined lacks sufficient market relevance
+					to continue recommending it for implementation,
+					but which does not have fundamental problems
+					that would require it to be <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec">Rescinded</a>.
+					If an Obsolete specification gains sufficient market relevance,
+					W3C may decide to restore it to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⓪">Recommendation</a> status. 
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RescindedRec">Rescinded Recommendation</dfn> 
+       <dd> A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses,
+					and believes is unlikely to ever be restored to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②①">Recommendation</a> status.
+					See also “W3C Royalty-Free (RF) Licensing Requirements”
+					in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+      </dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="discontinuedREC">Discontinued Draft</dfn> 
+     <dd> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑨">technical report</a> representing the state of a Recommendation-track document
+			at the point at which work on it was discontinued.
+			See <a href="#abandon-draft">§ 6.3.12.1 Abandoning an Unfinished Recommendation</a>. 
+    </dl>
+    <p>Only sufficiently technically mature work should be advanced.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Should faster advancement to meet scheduling considerations be desired,
+	this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring
+	less stable features to other technical reports.</p>
+    <p>When publishing an updated version of an existing <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①①">Candidate Recommendation</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②②">Recommendation</a>,
+	technical reports are expected to meet the same maturity criteria as when they are first published under that status.
+	However, in the interest of replacing stale documents with improved ones in a timely manner,
+	if flaws have been discovered in the technical report after its initial publication as a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①②">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②③">REC</a> that would have been severe enough to reject that publication had they be known in time,
+	it is also permissible to publish an updated <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①③">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②④">REC</a> following the usual process,
+	even if only some of these flaws have been satisfactorily addressed.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑤">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①⓪">Interest Groups</a> <em class="rfc2119">may</em> make available <a data-link-type="dfn" href="#editors-draft" id="ref-for-editors-draft">Editor’s drafts</a>. <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Editor&apos;s Draft | Editor Draft | ED" id="editors-draft">Editor’s drafts</dfn> (<abbr>ED</abbr>) have no official standing whatsoever,
+	and do not necessarily imply consensus of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑥">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①①">Interest Group</a>,
+	nor are their contents endorsed in any way by W3C.</p>
+    <h4 class="heading settled" data-level="6.3.2" id="implementation-experience"><span class="secno">6.3.2. </span><span class="content"> Implementation Experience</span><a class="self-link" href="#implementation-experience"></a></h4>
+    <p>Implementation experience is required to show that a specification is sufficiently clear,
+	complete,
+	and relevant to market needs,
+	to ensure that independent interoperable implementations
+	of each feature of the specification will be realized.
+	While no exhaustive list of requirements is provided here,
+	when assessing that there is <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="adequate-implementation">adequate implementation experience</dfn> the <a data-link-type="dfn" href="#team" id="ref-for-team⑨④">Team</a> will consider (though not be limited to):</p>
+    <ul>
+     <li> is each feature of the current specification implemented,
+			and how is this demonstrated? 
+     <li> are there independent interoperable implementations of the current specification? 
+     <li> are there implementations created by people other than the authors of the specification? 
+     <li> are implementations publicly deployed? 
+     <li> is there implementation experience
+			at all levels of the specification’s ecosystem
+			(authoring, consuming, publishing…)? 
+     <li> are there reports of difficulties or problems with implementation? 
+    </ul>
+    <p>Planning and accomplishing a demonstration of (interoperable) implementations can be very time consuming.
+	Groups are often able to work more effectively
+	if they plan how they will demonstrate interoperable implementations
+	early in the development process;
+	for example, developing tests in concert with implementation efforts.</p>
+    <h4 class="heading settled" data-level="6.3.3" id="transition-reqs"><span class="secno">6.3.3. </span><span class="content"> Advancement on the Recommendation Track</span><a class="self-link" href="#transition-reqs"></a></h4>
+    <p>For <em>all</em> requests to advance a specification
+	to a new maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="trans-req">Transition Requests</dfn>),
+	the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request advancement. 
+     <li id="adv-verif-reqs"><a class="self-link" href="#adv-verif-reqs"></a> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑤">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑥">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑨">Team decision</a>) <em class="rfc2119">must</em> be withheld if any Process requirements are not met
+			or if there remain any unresolved Formal Objections
+			(including any aspect <a data-link-type="dfn" href="#upheld" id="ref-for-upheld④">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑤">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed">fully addressed</a>),
+			or if the document does not adequately reflect all relevant decisions of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑥">W3C Council</a> (or its delegates).
+			If the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑦">Team</a> rejects a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req①">Transition Request</a> it <em class="rfc2119">must</em> indicate its rationale
+			to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③④">Advisory Committee</a> and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑦">Working Group</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change②">editorial changes</a> have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed②">formally address</a> all issues
+			raised about the document since the previous <a href="#maturity-stages">maturity stage</a>. 
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑧">Formal Objections</a>. 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑧">Working Group</a>’s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑨">Working Group</a>. 
+    </ul>
+    <p>For a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd②">First Public Working Draft</a> there is no “previous maturity stage”,
+	so many requirements do not apply,
+	and verification is normally fairly straightforward.
+	For later stages,
+	especially transitions to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①④">Candidate</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑤">Recommendation</a>,
+	there is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p><a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req②">Transition Requests</a> to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd③">First Public Working Draft</a> or <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑤">Candidate Recommendation</a> will not normally be approved
+	while a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⓪">Working Group</a>’s <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑧">charter</a> is undergoing or awaiting a decision
+	on an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②②">Advisory Committee Review</a>.</p>
+    <h4 class="heading settled" data-level="6.3.4" id="update-reqs"><span class="secno">6.3.4. </span><span class="content"> Updating Mature Publications on the Recommendation Track</span><a class="self-link" href="#update-reqs"></a></h4>
+    <p>Certain requests to re-publish a specification
+	within its current maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="update-requests">Update Requests</dfn>)
+	require extra verification.
+	For such <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests②">update requests</a>, the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request the update. 
+     <li> <em class="rfc2119">must</em> show that the changes have received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑦">wide review</a>. 
+     <li>
+       <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑧">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑨">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①⓪">Team decision</a>): 
+      <ul>
+       <li data-md>
+        <p><em class="rfc2119">should</em> be withheld
+if any Process requirements are not met,</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+in consideration of unresolved Formal Objections
+(including any aspect <a data-link-type="dfn" href="#upheld" id="ref-for-upheld⑤">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑦">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed①">fully addressed</a>),</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+if the document does not adequately reflect
+all relevant decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑧">W3C Council</a> (or its delegates),</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+if the Team believes the Group is not making reasonable progress
+on addressing issues raised by individuals external to the Group.</p>
+      </ul>
+      <p>If the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⓪">Team</a> rejects an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests③">Update Request</a>,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④①">Working Group</a>.
+			If it waives any Process requirements,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑤">AC</a>.</p>
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑨">Formal Objections</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document of all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change③">editorial changes</a> changes have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> show that the revised specification
+			meets all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④②">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④③">Working Group</a>’s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④④">Working Group</a>. 
+    </ul>
+    <p>There is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests④">Update request</a> verification is expected to be fairly simple
+	compared to verification of a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req③">transition request</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪①">Team</a> <em class="rfc2119">must</em> announce the publication
+	of the revised specification
+	to other W3C groups and the Public.</p>
+    <h4 class="heading settled" data-level="6.3.5" id="first-wd"><span class="secno">6.3.5. </span><span class="content"> Publishing a First Public Working Draft</span><a class="self-link" href="#first-wd"></a></h4>
+    <p>To publish the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd④">First Public Working Draft</a> of a document,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑤">Working Group</a> <em class="rfc2119">must</em> meet the applicable <a href="#transition-reqs">requirements for advancement</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪②">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑤">First Public Working Draft</a> to other W3C groups and to the public.</p>
+    <h4 class="heading settled" data-level="6.3.6" id="revising-wd"><span class="secno">6.3.6. </span><span class="bs-old-id" id="revised-wd"></span><span class="content"> Revising a Working Draft</span><a class="self-link" href="#revising-wd"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑥">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑤">publish</a> a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑦">Working Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a Working draft, a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication. <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②①">Consensus</a> is not required,
+			as this is a procedural step, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑧">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑧">Working Draft</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change④">editorial changes</a> to the technical report
+			since the previous step, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups, 
+    </ul>
+    <p>Possible next steps for any Working Draft:</p>
+    <ul>
+     <li>Revised <a href="#revising-wd">Working Draft</a> 
+     <li><a href="#transition-cr">Candidate Recommendation</a> 
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.7" id="transition-cr"><span class="secno">6.3.7. </span><span class="bs-old-id" id="candidate-rec"></span><span class="content"> Transitioning to Candidate Recommendation</span><a class="self-link" href="#transition-cr"></a></h4>
+    <p>To publish a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑥">Candidate Recommendation</a>,
+	in addition to meeting the <a href="#transition-reqs">requirements for advancement</a> a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑦">Working Group</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> show that the specification
+			has met all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑧">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">must</em> document changes to dependencies during the development of the specification, 
+     <li> <em class="rfc2119">must</em> document
+			how <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation①">adequate implementation experience</a> will be demonstrated, 
+     <li> <em class="rfc2119">must</em> specify the deadline for comments,
+			delineating the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-recommendation-review-period">Candidate Recommendation review period</dfn>,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">must</em> show that the specification has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑧">wide review</a>, and 
+     <li> <em class="rfc2119">may</em> identify features in the document as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="at-risk">at risk</dfn>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑥">Recommendation</a> without requiring an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑤">Update Request</a>. 
+    </ul>
+    <p>The first Candidate Recommendation publication
+	after verification of having met the requirements for a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req④">Transition Request</a> is always a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑤">Candidate Recommendation Snapshot</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪③">Team</a> <em class="rfc2119">must</em> announce
+	the publication of the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑥">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑦">Candidate Recommendation Snapshot</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Recommendation</a>
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <p><a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑥">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 class="heading settled" data-level="6.3.8" id="revising-cr"><span class="secno">6.3.8. </span><span class="bs-old-id" id="revised-cr"></span><span class="content"> Revising a Candidate Recommendation</span><a class="self-link" href="#revising-cr"></a></h4>
+    <h5 class="heading settled" data-level="6.3.8.1" id="publishing-crrs"><span class="secno">6.3.8.1. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑧">Candidate Recommendation Snapshot</a></span><a class="self-link" href="#publishing-crrs"></a></h5>
+    <p>If there are any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑨">substantive changes</a> made to a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑦">Candidate Recommendation</a> since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑨">Candidate Recommendation Snapshot</a> other than to remove features explicitly identified as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk">at risk</a>,
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑨">Working Group</a> <em class="rfc2119">must</em> meet the requirements of an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑥">update request</a> in order to republish.</p>
+    <p>In addition the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> specify the deadline for further comments,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">may</em> identify features in the document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk①">at risk</a>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑦">Recommendation</a> without requiring an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑦">Update Request</a>. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪④">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a revised <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⓪">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>To provide timely updates and patent protection,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①①">Candidate Recommendation Snapshot</a> <em class="rfc2119">should</em> be published
+	within 24 months of the Working Group accepting
+	any proposal for a substantive change
+	(and preferably sooner).
+	To make scheduling reviews easier,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①②">Candidate Recommendation Snapshot</a> <em class="rfc2119">should not</em> be published
+	more often than approximately once every 6 months.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①⓪">Substantive changes</a> trigger a new Exclusion Opportunity
+	per “Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.8.2" id="publishing-crud"><span class="secno">6.3.8.2. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft②">Candidate Recommendation Draft</a></span><a class="self-link" href="#publishing-crud"></a></h5>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⓪">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑥">publish</a> an <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft③">Update Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft④">Candidate Recommendation Draft</a>,
+	a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①①">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①③">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑤">editorial changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①④">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> document outstanding issues,
+			and parts of the document on which the Working Group does not have consensus, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+    </ul>
+    <p class="note" role="note"><span class="marker">Note:</span> A Working Group <em>does not</em> need to
+	meet the requirements of a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑤">Candidate Recommendation Snapshot</a> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑧">update request</a> in order to publish a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑤">Candidate Recommendation Draft</a>.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑥">Candidate Recommendation Draft</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Recommendation</a>,
+		if there are no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①②">substantive change</a> other than dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk②">at risk</a> features
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.9" id="transition-rec"><span class="secno">6.3.9. </span><span class="bs-old-id" id="transition-pr"></span><span class="bs-old-id" id="rec-pr"></span><span class="bs-old-id" id="rec-publication"></span><span class="content"> Transitioning to Recommendation</span><a class="self-link" href="#transition-rec"></a></h4>
+    <p>When a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤①">Working Group</a> estimates
+	that a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑧">Candidate Recommendation</a> has fulfilled all the relevant criteria,
+	it <em class="rfc2119">may</em> <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision③">decide</a> to request advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑧">W3C Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.1" id="transition-rec-requirements"><span class="secno">6.3.9.1. </span><span class="content"> Requirements for Transition</span><a class="self-link" href="#transition-rec-requirements"></a></h5>
+    <p>In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,
+	the Working Group:</p>
+    <ul>
+     <li>
+       <em class="rfc2119">must</em> show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation②">adequate implementation experience</a> except where an exception is approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①①">Team Decision</a>. 
+      <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑤">Team</a> <em class="rfc2119">may</em> approve a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑨">Candidate Recommendation</a> with minimal <a href="#implementation-experience">implementation experience</a> where there is a compelling reason to do so.
+			In such a case, the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑥">Team</a> <em class="rfc2119">must</em> explain the reasons for that decision,
+			and that information <em class="rfc2119">must</em> be included in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform②">Call for Review</a> proposing advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑨">W3C Recommendation</a>.</p>
+     <li> <em class="rfc2119">must</em> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑨">wide review</a>. 
+     <li> <em class="rfc2119">must</em> show that all issues
+			raised during the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period">Candidate Recommendation review period</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed③">formally addressed</a>. 
+     <li> <em class="rfc2119">must </em>identify any substantive issues
+			raised since the close of the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period①">Candidate Recommendation review period</a>. 
+     <li> <em class="rfc2119">must</em> identify, in the document, where errata are tracked. 
+    </ul>
+    <p>Additionally,
+	if the document has previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⓪">W3C Recommendation</a>, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤②">Working Group</a> <em class="rfc2119">must not</em> include any <a href="#correction-classes">class 4 change</a> to that publication
+	unless it was explicitly marked as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features">allowing new features</a>,
+	and <em class="rfc2119">must not</em> include any such marking
+	if not already present.</p>
+    <p>If the document’s most recent publication is a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑦">Candidate Recommendation Draft</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑦">Team</a> <em class="rfc2119">must</em> verify
+	that it contains no changes since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑥">Candidate Recommendation Snapshot</a> other than:</p>
+    <ul>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑥">editorial changes</a>,</p>
+     <li data-md>
+      <p>the addition or removal of a statement as to whether the document will <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features①">allow new features</a> after its publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③①">Recommendation</a>.</p>
+     <li data-md>
+      <p>dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk③">at risk</a> features</p>
+    </ul>
+    <p>Otherwise, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤③">Working Group</a> <em class="rfc2119">must</em> republish it
+	as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑦">Candidate Recommendation Snapshot</a> prior to initiating the review.</p>
+    <h5 class="heading settled" data-level="6.3.9.2" id="initiating-rec-review"><span class="secno">6.3.9.2. </span><span class="content"> Initiating Review</span><a class="self-link" href="#initiating-rec-review"></a></h5>
+    <p>If all the criteria above are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑧">Team</a> <em class="rfc2119">must</em> begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②③">Advisory Committee Review</a> on the question of whether the identified <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②⓪">Candidate Recommendation</a> is appropriate to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑦">publish</a> as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③②">W3C Recommendation</a>.
+	The deadline for <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②④">Advisory Committee review</a> <em class="rfc2119">must</em> allow <strong>at least</strong> 28 days,
+	and <em class="rfc2119">must</em> end at least 10 days
+	after the end of the last Exclusion Opportunity
+	per ”Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.3" id="rec-review-resolution"><span class="secno">6.3.9.3. </span><span class="content"> Resolution of Review</span><a class="self-link" href="#rec-review-resolution"></a></h5>
+    <p>If there was any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④⓪">Formal Objection</a> during the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑤">Advisory Committee Review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑨">Team</a> <em class="rfc2119">must</em> publish the substantive content of the <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑤">dissent</a> to W3C and the general public,
+	and the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③③">W3C Recommendation</a> <em class="rfc2119">must not</em> be published
+	unless all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④①">Formal Objections</a> to the document have been retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule③">overruled</a> and at least 14 days have elapsed since the publication of the corresponding <a data-link-type="dfn" href="#council-report" id="ref-for-council-report⑤">Council Report</a>.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③④">Recommendation</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①③">W3C Decision</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①①⓪">Team</a> <em class="rfc2119">must</em> announce the publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑤">W3C Recommendation</a> to the <a href="#AC">Advisory Committee</a>,
+	to other W3C groups
+	and to the public. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑥">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑥">Advisory Committee Appeal</a> of the decision to advance the technical report.</p>
+    <p>The newly published <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑥">Recommendation</a> <em class="rfc2119">must not</em> make any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①③">substantive changes</a> to the document
+	compared to the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑧">Candidate Recommendation Snapshot</a> submitted for AC Review,
+	other than dropping features identified <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk④">at risk</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.4" id="rec-next-steps"><span class="secno">6.3.9.4. </span><span class="content"> Next Steps from W3C Recommendation</span><a class="self-link" href="#rec-next-steps"></a></h5>
+    <p>Possible next steps:
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑦">W3C Recommendation</a> normally retains its status indefinitely.
+	However it <em class="rfc2119">may</em> be:</p>
+    <ul>
+     <li> republished as a <a href="#revising-rec">revised Recommendation</a>, or 
+     <li> republished as a <a href="#transition-cr">Candidate Recommendation</a> or <a href="#revising-wd">Working Draft</a> to be developed towards a revised <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑧">Recommendation</a>, or 
+     <li> declared <a href="#rec-rescind">superseded or obsolete</a>, or 
+     <li> <a href="#rec-rescind">rescinded</a>. 
+    </ul>
+    <h4 class="heading settled" data-level="6.3.10" id="revising-rec"><span class="secno">6.3.10. </span><span class="bs-old-id" id="revised-rec"></span><span class="bs-old-id" id="rec-modify"></span><span class="content"> Revising a W3C Recommendation</span><a class="self-link" href="#revising-rec"></a></h4>
+    <h5 class="heading settled" data-level="6.3.10.1" id="revised-rec-editorial"><span class="secno">6.3.10.1. </span><span class="bs-old-id" id="revised-rec-markup"></span><span class="content"> Revising a Recommendation: Editorial Changes</span><a class="self-link" href="#revised-rec-editorial"></a></h5>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑦">Editorial changes</a> to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑨">Recommendation</a> require no technical review of the intended changes.
+	A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤④">Working Group</a>,
+	provided there are no votes against the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision④">decision</a> to publish, <em class="rfc2119">may</em> request publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⓪">Recommendation</a> to make this class of change without passing through earlier maturity stages.
+	(See <a href="#class-1">class 1</a> and <a href="#class-2">class 2 changes</a>.)</p>
+    <h5 class="heading settled" data-level="6.3.10.2" id="revised-rec-substantive"><span class="secno">6.3.10.2. </span><span class="content"> Revising a Recommendation: Substantive Changes</span><a class="self-link" href="#revised-rec-substantive"></a></h5>
+    <p>Tentative corrections (see <a href="#class-3">class 3 changes</a>) <em class="rfc2119">may</em> be annotated into a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④①">Recommendation</a> using <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction④">candidate corrections</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑤">Candidate corrections</a> do not normatively modify the document;
+	they editorially indicate how one might do so.
+	They are therefore published following the provisions of <a href="#revised-rec-editorial">§ 6.3.10.1 Revising a Recommendation: Editorial Changes</a>.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑥">candidate correction</a> can be made normative
+	and be folded into the main text of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④②">Recommendation</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④③">Recommendation</a>,
+	including review by the community to ensure
+	its technical and editorial soundness.
+	To validate this, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑤">Working Group</a> must request
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review">Last Call for Review of Proposed Amendments</a>,
+	followed by an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑨">update request</a>.
+	See <a href="#change-review">§ 6.3.10.4 Incorporating Candidate Amendments</a>.</p>
+    <p>Alternatively,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑥">Working Group</a> <em class="rfc2119">may</em> incorporate the changes
+	and <a href="#revising-wd">publish as a Working Draft</a>—​or, if the relevant criteria are fulfilled, <a href="#transition-cr">publish as a Candidate Recommendation</a>—​and advance the specification from that state.
+	(See <a href="#correction-classes">class 3 changes</a>.)</p>
+    <h5 class="heading settled" data-level="6.3.10.3" id="revised-rec-features"><span class="secno">6.3.10.3. </span><span class="content"> Revising a Recommendation: New Features</span><a class="self-link" href="#revised-rec-features"></a></h5>
+    <p>For <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④④">Recommendations</a> explicitly identified as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features②">allowing new features</a>,
+	tentative new features (see <a href="#correction-classes">class 4 changes</a>) <em class="rfc2119">may</em> be added as <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition①">candidate additions</a> in annotations,
+	and <a href="#correction-classes">class 4 changes</a> may be normatively incorporated
+	in the same fashion as <a href="#correction-classes">class 3 changes</a> in <a href="#revised-rec-substantive">§ 6.3.10.2 Revising a Recommendation: Substantive Changes</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Limiting the addition of new features to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑤">Recommendations</a> that explicitly allow them
+	enables third parties to depend on a stable feature-set for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑥">Recommendations</a> that do not advertise that ability,
+	as was the case for all <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑦">Recommendations</a> prior to the 2020 revision of this Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> When a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑧">Recommendation</a> does not <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features③">allow new features</a>,
+	new features can be added by creating a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⓪">technical report</a> and following the full process of advancing that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②①">technical report</a> to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑨">Recommendation</a>—​beginning with a new <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑥">First Public Working Draft</a>.
+	Such <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②②">technical reports</a> could be written to represent
+	additional modules building on top of the original <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⓪">Recommendation</a> of the core technology,
+	or an expanded replacement of the original <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤①">Recommendation</a> of the core technology
+	(in which case the new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②③">technical report</a> will typically have the same name as the original,
+	with an incremented version number).</p>
+    <h5 class="heading settled" data-level="6.3.10.4" id="change-review"><span class="secno">6.3.10.4. </span><span class="content"> Incorporating Candidate Amendments</span><a class="self-link" href="#change-review"></a></h5>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-review">Last Call for Review of Proposed Amendments</dfn> verifies acceptance by the W3C community of <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment③">candidate amendments</a> by combining an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑥">AC Review</a> with a patent exclusion opportunity.</p>
+    <p>The <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review①">Last Call for Review of Proposed Amendments</a> must be announced to other W3C groups, the public, and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑦">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Identify whether this is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</dfn>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</dfn>,
+			or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</dfn>. 
+     <li> Identify the specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment④">candidate amendments</a> under review
+			as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-amendments">proposed amendments</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="proposed-corrections">proposed corrections</dfn>/<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="proposed-additions"><span class="bs-old-id" id="proposed-addition"></span>proposed additions</dfn>). 
+     <li> Specify the deadline for review comments,
+			which must not be any sooner than 60 days from the Call for Review. 
+     <li> Solicit review and, if it does not already have it, implementation experience. 
+    </ul>
+    <p>The combination of the existing <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤②">Recommendation</a> with the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments">proposed amendments</a> included in the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review②">Last Call for Review of Proposed Amendments</a> is considered a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts②">Patent Review Draft</a> for the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+	Also, the review initiated by the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review③">Last Call for Review of Proposed Amendments</a> is an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑦">Advisory Committee Review</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#last-call-for-review-of-proposed-additions" id="ref-for-last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a> and <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections-and-additions" id="ref-for-last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a> can only be issued for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤③">Recommendations</a> that <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features④">allow new features</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑦">Working Group</a> <em class="rfc2119">may</em> batch
+	multiple <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①">proposed amendments</a> into a single <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review④">Last Call for Review of Proposed Amendments</a>.
+	To facilitate review,
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑤">Last Call for Review of Proposed Amendments</a> on a given specification <em class="rfc2119">should not</em> be issued more frequently
+	than approximately once every 6 months.</p>
+    <p>At the end of the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑥">Last Call for Review of Proposed Amendments</a>,
+	the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①④">W3C Decision</a> may either be
+	to reject the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments②">proposed amendment</a>,
+	or to clear the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments③">proposed amendment</a> for advancement as is,
+	or to return the proposal to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑧">Working Group</a> with a request to <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed④">formally address</a> comments made on the changes under review.
+	If the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑨">Working Group</a> needs to amend a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments④">proposed amendment</a> in response to review feedback
+	it must issue another <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑦">Last Call for Review of Proposed Amendments</a> on the revised change
+	before it can be incorporated into the main text.</p>
+    <p>Once all comments on a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑤">proposed amendment</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑤">formally addressed</a>,
+	and after the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⓪">Working Group</a> can show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation③">adequate implementation experience</a> and the fulfillment of all other requirements of Recommendation text,
+	it may incorporate the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑥">proposed amendment</a> into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤④">Recommendation</a> by issuing an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①⓪">update request</a> for publication of the updated <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑤">Recommendation</a>.</p>
+    <p>To ensure adequate review of <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑦">proposed amendment</a> combinations,
+	only <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑧">proposed amendments</a> included in the most recent <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑧">Last Call for Review of Proposed Amendments</a> can be incorporated into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑥">Recommendation</a> text.
+	(Thus if incorporation of a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑨">proposed amendment</a> is postponed,
+	it may need to be included in multiple Last Calls for Review of Proposed Amendments.)</p>
+    <h4 class="heading settled" data-level="6.3.11" id="rec-track-regression"><span class="secno">6.3.11. </span><span class="content"> Regression on the Recommendation Track</span><a class="self-link" href="#rec-track-regression"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥①">Working Group</a> may republish a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑨">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②④">technical report</a> at a lower <a href="#maturity-stages">maturity stage</a> by fulfilling the requirements to transition to that maturity stage,
+	as described above.</p>
+    <p>Additionally,
+	with the approvals (by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑤">group decision</a>) of each of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑤">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③①">AB</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①①①">Team</a> <em class="rfc2119">may</em> return
+	the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑤">technical report</a> to a lower <a href="#maturity-stages">maturity stage</a> in response to <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①⓪">wide review</a> or a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④②">formal objection</a>.</p>
+    <h4 class="heading settled" data-level="6.3.12" id="tr-end"><span class="secno">6.3.12. </span><span class="content"> Retiring Recommendation Track Documents</span><a class="self-link" href="#tr-end"></a></h4>
+    <p>Work on a technical report <em class="rfc2119">may</em> cease at any time.
+	Work <em class="rfc2119 new">should</em> cease
+	if W3C or a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥②">Working Group</a> determines
+	that it cannot productively carry the work any further.</p>
+    <h5 class="heading settled" data-level="6.3.12.1" id="abandon-draft"><span class="secno">6.3.12.1. </span><span class="content"> Abandoning an Unfinished Recommendation</span><a class="self-link" href="#abandon-draft"></a></h5>
+    <p>Any <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⓪">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑥">technical report</a> no longer intended
+	to advance or to be maintained,
+	and that is not being rescinded, <em class="rfc2119">should</em> be <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑧">published</a> as a <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC">Discontinued Draft</a>,
+	with no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①④">substantive change</a> compared to the previous publication.
+	This can happen if
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥③">Working Group</a> decided
+	to abandon work on the report,
+	or as the result of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑧">AC Review</a> requiring the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥④">Working Group</a> to discontinue work on the technical report before completion.
+	If a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑤">Working Group</a> is made to <a href="#GeneralTermination">close</a>,
+	W3C <em class="rfc2119">must</em> re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑨">publish</a> any unfinished <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑦">technical report</a> on the Recommendation track as <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC①">Discontinued Draft</a>.</p>
+    <p>Such a document should include in its status section
+	an explanation of why it was discontinued.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑥">Working Group</a> <em class="rfc2119">may</em> resume work
+	on such a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑧">technical report</a> within the scope of its charter
+	at any time,
+	by re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing①⓪">publishing</a> it as a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑨">Working Draft</a>.</p>
+    <h5 class="heading settled" data-level="6.3.12.2" id="rescind-cr"><span class="secno">6.3.12.2. </span><span class="content"> Rescinding a Candidate Recommendation</span><a class="self-link" href="#rescind-cr"></a></h5>
+    <p>The process for rescinding a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②①">Candidate Recommendation</a> is the same as for rescinding a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑦">Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.12.3" id="rec-rescind"><span class="secno">6.3.12.3. </span><span class="content"> Abandoning a W3C Recommendation</span><a class="self-link" href="#rec-rescind"></a></h5>
+    <p>It is possible that W3C decides
+	that implementing a particular <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑧">Recommendation</a> is no longer recommended.
+	There are three designations for such specifications,
+	chosen depending on the advice W3C wishes to give about further use of the specification.</p>
+    <p>W3C <em class="rfc2119">may</em> obsolete a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑨">Recommendation</a>,
+	for example if the W3C Community decides that the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⓪">Recommendation</a> no longer represents best practices,
+	or is not adopted and is not apparently likely to be adopted.
+	An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs①">Obsolete Recommendation</a> <em class="rfc2119">may</em> be restored to normal <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥①">Recommendation</a>,
+	for example because despite marking it Obsolete the specification is later more broadly adopted.</p>
+    <p>W3C <em class="rfc2119">may</em> declare a Recommendation Superseded
+	if a newer version exists which W3C recommends for new adoption.
+	The process for declaring a Recommendation Superseded is the same as for declaring it Obsolete, below;
+	only the name and explanation change.</p>
+    <p>W3C <em class="rfc2119">may</em> rescind a Recommendation
+	if W3C believes there is no reasonable prospect of it being restored
+	for example due to burdensome patent claims that affect implementers and cannot be resolved;
+	see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “W3C Royalty-Free (RF) Licensing Requirements”
+	and “PAG Conclusion”.</p>
+    <p>W3C only rescinds, supersedes, or obsoletes entire Recommendations.
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥②">Recommendation</a> can be both superseded and obsolete.
+	To rescind, supersede, or obsolete some part of a Recommendation,
+	W3C follows the process for <a href="#revising-rec">modifying a Recommendation</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> For the purposes of the W3C Patent Policy, <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs②">Obsolete</a> or <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup">Superseded Recommendation</a> has the status of an active <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥③">Recommendation</a>,
+	although it is not advised for future implementation;
+	a <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec①">Rescinded Recommendation</a> ceases to be in effect
+	and no new licenses are granted under the Patent Policy.</p>
+    <figure>
+     <svg viewBox="0 0 300 135" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Supersede, Obsolete or Rescind a W3C Recommendation</title>
+      <g role="list">
+       <g role="listitem">
+        <ellipse cx="40" cy="50" fill="#fff" id="rec-3" role="img" rx="30" ry="20" stroke="black" stroke-width="2">
+         <title>Recommendation (Rec)</title>
+        </ellipse>
+        <text aria-hidden="true" font-size="18" stroke-width=".3" text-anchor="middle" x="40" y="55">REC</text>
+        <g role="list">
+         <g role="listitem">
+          <title>A major problem and an AC review can lead to a Recommendation being Rescinded.
+								There are no new IPR licences issued under the W3C Patent Policy,
+								and reinstating the Recommendation requires going through the full Rec-track process again.</title>
+          <path d="M40,29v-5s0,-5 5,-5h150" fill="none" stroke="black" stroke-dasharray="3 1" stroke-width="2"></path>
+          <text font-size="8" text-anchor="middle" x="105" y="16">Major problem, AC review</text>
+          <polygon points="195,16 195,22 199,19"></polygon>
+          <rect fill="#fff" height="36" id="rescinded" role="img" stroke="black" stroke-width="2" width="80" x="200" y="4"></rect>
+          <title>Rescinded Recommendation - no new IPR licenses</title>
+          <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="240" y="19">Rescinded</text>
+          <path d="M198,42l84,-40" stroke="red" stroke-width="2"></path>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="28">No new IPR licenses</text>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="37">No reinstatement path</text>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="black" stroke-dasharray="4 4"></path>
+           <title>With little uptake, following AC review a specification may become an Obsolete Recommendation</title>
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="red" stroke-dasharray="2 6" stroke-dashoffset="3"></path>
+           <polygon points="204,75 200,72 200,78"></polygon>
+           <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="42">Minimal usage, AC review</text>
+           <rect fill="#fff" height="26" id="obsolete" rx="8" stroke="black" stroke-dasharray="3 3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <title>Obsolete Recommendation</title>
+           <rect fill="none" height="26" rx="8" stroke="red" stroke-dasharray="3 3" stroke-dashoffset="3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="242" y="84">Obsolete</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <path d="M204,82h-149s-5,0 -5,-5v-5" fill="none" stroke="black" stroke-dasharray="2 3"></path>
+             <title>If there is new uptake, with AC review an Obsolete Recommendation may return to normal Recommendation status</title>
+             <polygon points="50,70 47,74 53,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="79">New uptake, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M40,71v29s0,5 5,5h140" fill="none" stroke="black"></path>
+           <polygon points="189,105 185,102 185,108"></polygon>
+           <text font-size="8" text-anchor="middle" x="115" y="102">Replaced by a new version, AC review</text>
+           <rect fill="#fff" height="30" id="superseded" role="img" rx="3" stroke="#600" stroke-width="2" width="90" x="190" y="100">
+            <title>Superseded Recommendation</title>
+           </rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="235" y="119">Superseded</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <title>A Superseded Recommendation can become a normal Recommendation with AC review</title>
+             <path d="M189,125h-154s-5,0 -5,-5v-52" fill="none" stroke="black" stroke-dasharray="1 4"></path>
+             <polygon points="30,70 27,74 33,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="110" y="122">Oops! The Web still needs this, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+     <figcaption>Non-Normative Summary of the Paths to Retiring a W3C Recommendation</figcaption>
+    </figure>
+    <h5 class="heading settled" data-level="6.3.12.4" id="deactivation"><span class="secno">6.3.12.4. </span><span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span><a class="self-link" href="#deactivation"></a></h5>
+    <p>The process of rescinding, obsoleting,
+	superseding,
+	or restoring
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥④">Recommendation</a> can be initiated
+	either by a request from the <a data-link-type="dfn" href="#team" id="ref-for-team①①②">Team</a> or via a request from any of the following:</p>
+    <ul>
+     <li> The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑦">Working Group</a> who produced,
+			or is chartered to maintain,
+			the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑤">Recommendation</a> 
+     <li> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑥">TAG</a>, if there is no such <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑧">Working Group</a> 
+     <li> Any individual who made a request to the relevant <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑨">Working Group</a> as described above,
+			or the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑦">TAG</a> if such a group does not exist, to obsolete, rescind, supersede, or restore a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑥">Recommendation</a>,
+			where the request was not answered within 90 days 
+     <li> 5% of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑦">Advisory Committee representatives</a> of <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑤">Members</a> in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing②">Good Standing</a> 
+    </ul>
+    <p id="proposed-rescinded-rec">The <a data-link-type="dfn" href="#team" id="ref-for-team①①③">Team</a> <em class="rfc2119">must</em> then
+	submit the request to the <a href="#AC">Advisory Committee</a> for review.
+	For any <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑨">Advisory Committee review</a> of a proposal to
+	rescind,
+	obsolete,
+	supersede,
+	or restore
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑦">Recommendation</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①①④">Team</a> <em class="rfc2119">must</em>: </p>
+    <ul>
+     <li> announce the proposal to all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⓪">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③②">Chairs</a>,
+			and to the Public,
+			as well as to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑧">Advisory Committee</a> 
+     <li> indicate that this is a proposal to
+			Rescind,
+			Obsolete,
+			Supersede,
+			or restore,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑧">Recommendation</a> as appropriate 
+     <li> identify the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑨">Recommendation</a> by URL 
+     <li> publish a rationale for the proposal 
+     <li> identify known dependencies
+			and solicit review from all dependent <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦①">Working Groups</a> 
+     <li> solicit public review 
+     <li> specify the deadline for review comments,
+			which <em class="rfc2119">must</em> be at least 28 days
+			after the announcement 
+    </ul>
+    <p>and <em class="rfc2119">should</em></p>
+    <ul>
+     <li> identify known implementations. 
+    </ul>
+    <p>If there was any <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑥">dissent</a> in the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⓪">Advisory Committee review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑤">Team</a> <em class="rfc2119">must</em> publish
+	the substantive content of the dissent to W3C <strong>and the public</strong>,
+	and <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑥">formally address</a> the dissent
+	at least 14 days
+	before publication as an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs③">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec②">Rescinded Recommendation</a>.</p>
+    <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑦">Advisory Committee Appeal</a> of the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑥">Team</a>’s decision.</p>
+    <p>W3C <em class="rfc2119">must</em> publish an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs④">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec③">Rescinded Recommendation</a> 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 <em class="rfc2119">should</em> link
+	to the explanation of <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">Obsoleting and Rescinding W3C Specifications</a> <a data-link-type="biblio" href="#biblio-obs-resc" title="Obsoleting and Rescinding W3C Specifications">[OBS-RESC]</a> as appropriate.</p>
+    <p>Once W3C has published a Rescinded Recommendation,
+	future W3C technical reports <em class="rfc2119">must not</em> include normative references
+	to that technical report.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> W3C strives to ensure that all Technical Reports
+	will continue to be available at their version-specific URL.</p>
+    <h3 class="heading settled" data-level="6.4" id="note-track"><span class="secno">6.4. </span><span class="content"> The Note Track (Notes and Statements)</span><a class="self-link" href="#note-track"></a></h3>
+    <h4 class="heading settled" data-level="6.4.1" id="Note"><span class="secno">6.4.1. </span><span class="content"> Group Notes</span><a class="self-link" href="#Note"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Group Note | Note" id="WGNote">Group Note</dfn> (<abbr>NOTE</abbr>)
+	is published
+	to provide a stable reference for a useful document
+	that is not intended to be a formal standard.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦②">Working Groups</a>, <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①②">Interest Groups</a>,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑧">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③②">AB</a> <em class="rfc2119">may</em> publish work as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②">Notes</a>.
+	Examples include:</p>
+    <ul>
+     <li> supporting documentation for a specification,
+			such as explanations of design principles
+			or use cases and requirements 
+     <li> non-normative guides to good practices 
+    </ul>
+    <p>Some <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote③">Notes</a> are developed through successive <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Note Draft" data-noexport id="note-draft"><span class="bs-old-id" id="draft-note"></span>Note Drafts</dfn> before publication as a full <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote④">Notes</a>,
+	while others are <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①①">published</a> directly as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑤">Note</a>.
+	There are few formal requirements to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①②">publish</a> a document as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑥">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft">Note Draft</a>,
+	and they have no standing as a recommendation of W3C
+	but are simply documents preserved for historical reference.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> does not apply any licensing requirements or commitments for <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑦">Notes</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft①">Note Drafts</a>.</p>
+    <h4 class="heading settled" data-level="6.4.2" id="publishing-notes"><span class="secno">6.4.2. </span><span class="content"> Publishing Notes</span><a class="self-link" href="#publishing-notes"></a></h4>
+    <p>In order to publish a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑧">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft②">Note Draft</a>,
+	the group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record their decision
+			to request publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑨">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft③">Note Draft</a>, and 
+     <li> <em class="rfc2119">should</em> publish documentation
+			of significant changes to the technical report
+			since any previous publication. 
+    </ul>
+    <p>Both <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⓪">Notes</a> and <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft④">Note Drafts</a> can be updated by republishing
+	as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①①">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft⑤">Note Draft</a>.
+	A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑨">technical report</a> <em class="rfc2119">may</em> remain
+	a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①②">Note</a> indefinitely.</p>
+    <h4 class="heading settled" data-level="6.4.3" id="w3c-statement"><span class="secno">6.4.3. </span><span class="bs-old-id" id="memo"></span><span class="content"> Elevating Group Notes to W3C Statement status</span><a class="self-link" href="#w3c-statement"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Statement | W3C Statement" data-noexport id="statement">W3C Statement</dfn> is a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①③">Note</a> that has been endorsed by W3C as a whole.
+	In order to elevate a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①④">Note</a> to <a data-link-type="dfn" href="#statement" id="ref-for-statement②">W3C Statement</a> status,
+	A group <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①①">wide review</a>. 
+     <li> record the group’s decision to request publication as a <a data-link-type="dfn" href="#statement" id="ref-for-statement③">W3C Statement</a>. 
+     <li> show that all issues raised against the document
+			since its first publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑤">Note</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑦">formally addressed</a>. 
+     <li> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④③">Formal Objections</a>. 
+    </ul>
+    <p>A <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑥">Note</a> specifying implementable technology <em class="rfc2119">should not</em> be elevated to <a data-link-type="dfn" href="#statement" id="ref-for-statement④">W3C Statement</a> status;
+	if it does,
+	the request to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑤">Statement</a> <em class="rfc2119">must</em> include rationale
+	for why it should be elevated,
+	and why it is not on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①①">Recommendation track</a>.</p>
+    <p>Once these conditions are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑦">Team</a> <em class="rfc2119">must</em> then
+	begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③①">Advisory Committee Review</a> on the question of
+	whether the document is appropriate to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑥">W3C Statement</a>.
+	During this review period,
+	the <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑦">Note</a> <em class="rfc2119">must not</em> be updated.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#statement" id="ref-for-statement⑦">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑤">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑧">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑧">Advisory Committee Appeal</a> of the decision.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①①⑧">Team</a> must announce the publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑧">W3C Statement</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑨">Advisory Committee</a>, other W3C groups, and the public.</p>
+    <h4 class="heading settled" data-level="6.4.4" id="revising-memo"><span class="secno">6.4.4. </span><span class="content"> Revising W3C Statements</span><a class="self-link" href="#revising-memo"></a></h4>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑥">group decision</a> to do so,
+	groups can request publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑨">W3C Statement</a> with <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑧">editorial changes</a>—​including <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑤">candidate amendment</a>—​without any additional process.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑥">candidate amendment</a> can be folded into the main text of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①⓪">W3C Statement</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①①">Statement</a>,
+	including review by the community to ensure
+	the substantive and editorial soundness of the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑦">candidate amendments</a>.
+	To validate this, the group must request
+	an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③②">Advisory Committee review</a> of the changes it wishes to incorporate.
+	The specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑧">candidate amendments</a> under review <em class="rfc2119">must</em> be identified as <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①⓪">proposed amendments</a> just as in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections" id="ref-for-last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a>.</p>
+    <p>The decision to incorporate <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①①">proposed amendments</a> into <a data-link-type="dfn" href="#statement" id="ref-for-statement①②">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑥">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑨">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑨">Advisory Committee Appeal</a> of the decision.</p>
+    <h3 class="heading settled" data-level="6.5" id="registries"><span class="secno">6.5. </span><span class="content"> The Registry Track</span><a class="self-link" href="#registries"></a></h3>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry">registry</dfn> documents a data set
+	consisting of one or more <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry table" id="registry-table">registry tables</dfn>,
+	each table representing an updatable collection
+	of logically independent, consistently-structured <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry entry" id="registry-entry">registry entries</dfn>.
+	A registry consists of:</p>
+    <ul>
+     <li>the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①">registry definition</a>, defining how the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②">registry tables</a> are structured and maintained 
+     <li>one or more <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table③">registry tables</a>, holding the data set represented by the <a data-link-type="dfn" href="#registry" id="ref-for-registry②">registry</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data">registry data</dfn>) 
+    </ul>
+    <p>The purposes of maintaining a <a data-link-type="dfn" href="#registry" id="ref-for-registry③">registry</a> can include:</p>
+    <dl>
+     <dt>non-collision 
+     <dd> Avoiding the problem
+			of two entities using the same value with different semantics. 
+     <dt>non-duplication 
+     <dd> Avoiding the problem
+			of having two or more different values in use with the same semantics. 
+     <dt>information 
+     <dd> Providing a central index
+			where anyone can find out
+			what a value means
+			and what its formal definition is
+			(and where it is). 
+     <dt>submission 
+     <dd> Ease of adding new terms,
+			including by stakeholders external to the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian">custodian</a> organization. 
+     <dt>consensus 
+     <dd> Promoting a clear consensus of the community on the terms. 
+    </dl>
+    <p>This section of the W3C Process provides a specialized process
+	facilitating the publication and maintenance of such <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table④">registry tables</a>,
+	particularly those required by or closely related to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦⓪">W3C Recommendations</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Not every table in a specification is a potential registry.
+	If the intent or effect is that the table enumerates
+	all the possibilities the authors of the specification expect or envisage,
+	then the table by itself is enough.
+	Similarly, if the table is managed by the Working Group
+	and only updated as part of specification update,
+	then the complexities of registry management are not needed.</p>
+    <h4 class="heading settled" data-level="6.5.1" id="reg-def"><span class="secno">6.5.1. </span><span class="content"> Registry Definitions</span><a class="self-link" href="#reg-def"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-definition">registry definition</dfn> defines what each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑤">registry table</a> is and how it is maintained.
+	It <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Define the scope and purpose of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑥">registry table</a>. 
+     <li> Define the fields of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑦">registry table</a> and their constraints
+			(e.g. values must be drawn from a defined set, or be unique,
+			or only reference publicly available resources,
+			etc.) 
+     <li>
+       Define the policy for changes to existing entries, such as 
+      <ul>
+       <li>whether entries can be deleted or deprecated 
+       <li>whether entries can be changed after being published, and what kinds of changes are allowed 
+       <li>whether previously-deleted unique identifiers can be re-used, or are reserved indefinitely 
+      </ul>
+     <li> Define the method and criteria by which changes are proposed, approved, and incorporated.
+			(For example, a <a data-link-type="dfn" href="#registry" id="ref-for-registry④">registry</a> could define
+			that changes to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry①">registry entries</a> can be proposed using a particular web form or email address,
+			that they must be accompanied by certain background information,
+			or that they do or do not need to be approved by any member of a particular Working Group.) 
+     <li>
+       Identify the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="custodian">custodian</dfn> of the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑧">registry table</a>:
+			the entity to which requests for <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change">registry changes</a> must be sent,
+			and which is responsible for evaluating whether such requests
+			satisfy the criteria defined in the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition②">registry definition</a>. 
+      <p>The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian①">custodian</a> may be the initiating group, the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑨">Team</a>, or a delegated entity.
+			The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian②">custodian</a> for all <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑨">registry tables</a> in a single <a data-link-type="dfn" href="#registry" id="ref-for-registry⑤">registry</a> <em class="rfc2119">should</em> generally be the same entity.</p>
+      <p>If the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian③">custodian</a> of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⓪">registry table</a> ceases to exist or to operate as a custodian
+			(e.g., the relevant group is disbanded, or 
+			the custodian is unresponsive to repeated attempts to make contact),
+			and the <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group⑤">chartered</a> or <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group①">elected group</a> that owns the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition③">registry definition</a> is itself <a href="#GeneralTermination">closed</a> or 
+			unresponsive,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①②⓪">Team</a> <em class="rfc2119">should</em> propose replacing the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian④">custodian</a>,
+			which <em class="rfc2119">must</em> be confirmed
+			by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③③">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑦">W3C Decision</a>.</p>
+    </ul>
+    <h4 class="heading settled" data-level="6.5.2" id="reg-pub"><span class="secno">6.5.2. </span><span class="content"> Publishing Registries</span><a class="self-link" href="#reg-pub"></a></h4>
+    <p>A <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group⑥">chartered</a> or <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group②">elected group</a> can publish a <a data-link-type="dfn" href="#registry" id="ref-for-registry⑥">registry</a> as a stand-alone <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⓪">technical report</a> on the <a data-link-type="dfn" href="#registry-track" id="ref-for-registry-track">Registry Track</a>,
+	where it is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-report">registry report</dfn>. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦③">Working Groups</a> have the additional option of
+	incorporating a <a data-link-type="dfn" href="#registry" id="ref-for-registry⑦">registry</a> as part of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦①">Recommendation</a>,
+	as an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="embedded-registry"><span class="bs-old-id" id="registry-section"></span>embedded registry</dfn>.</p>
+    <p>The <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report①">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry①">embedded registry</a> <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Clearly label the <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report②">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry②">embedded registry</a>,
+			its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①①">tables</a>,
+			and its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition④">registry definitions</a> as such,
+			including a link to <a href="#registries">§ 6.5 The Registry Track</a> in this Process. 
+     <li> Include the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑤">registry definition</a> for each of its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①②">registry tables</a>. 
+     <li>
+       Provide the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data">registry data</a> by either: 
+      <ul>
+       <li> Including the entire contents of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①③">registry table</a>,
+					either inline in the report
+					(e.g. formatted as a table, or list, or other appropriate representation),
+					or in a machine-readable file published as part of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③①">technical report</a>,
+					or (preferably) both. 
+       <li> Linking to one or more standalone <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report">Registry Data Reports</a> containing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①④">registry tables</a> in human-readable form, machine-readable form,
+					or (preferably) both. 
+      </ul>
+     <li> Include, if the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑤">registry table</a> is provided in a machine-readable file,
+			a definition of the format of that file. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②①">Team</a> <em class="rfc2119">must</em> make available
+	a means for interested parties to be notified of any updates to a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑥">registry table</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since the Process does not impose requirements
+	on changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑦">registry table</a> other than those imposed by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑥">registry definition</a>,
+	acceptance of proposed <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change①">registry changes</a> on behalf of the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian⑤">custodian</a> and
+	publication of an updated <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report③">registry report</a> that contains
+	only <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change②">registry changes</a> since the previous publication
+	can be automated
+	if satisfaction of those rules can be automatically verified.</p>
+    <p>Rules for publication and advancement on the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-track">Registry Track</dfn> are identical to that of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①②">Recommendation Track</a> with the following exceptions:</p>
+    <ul>
+     <li> <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report④">Registry reports</a> are not subject to the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			and therefore none of their publications correspond,
+			to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑦">First Public Working Draft</a>, <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①⓪">Working Draft</a>,
+			or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts③">Patent Review Draft</a> for the purposes of the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+     <li> For the same reason,
+			there is no equivalent to <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec④">Rescinded Recommendation</a> nor to <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation①">Rescinded Candidate Recommendation</a> for <a data-link-type="dfn" href="#registry" id="ref-for-registry⑧">Registries</a>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①①">Working Draft</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-draft"><span class="bs-old-id" id="draft-registry"></span>Registry Draft</dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②②">Candidate Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry">Candidate Registry</dfn>,
+			with <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑨">Candidate Recommendation Snapshot</a> and <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑧">Candidate Recommendation Draft</a> corresponding to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-snapshot">Candidate Registry Snapshot</dfn> and <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-draft">Candidate Registry Draft</dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦②">W3C Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="w3c-registry">W3C Registry</dfn>; <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs⑤">Obsolete Recommendation</a> and <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup①">Superseded Recommendation</a> correspond to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="obsolete-registry">Obsolete Registry</dfn> and <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="superseded-registry">Superseded Registry</dfn>. 
+     <li> Changes that add new features (i.e., <a href="#correction-classes">class 4 changes</a>) are allowed
+			in all <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry①">W3C Registries</a>,
+			without needing them to explicitly indicate that this is allowed. 
+    </ul>
+    <h4 class="heading settled" data-level="6.5.3" id="reg-table-update"><span class="secno">6.5.3. </span><span class="content"> Updating Registry Tables</span><a class="self-link" href="#reg-table-update"></a></h4>
+    <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑧">registry table</a> that are in accordance with the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑦">registry definition</a>,
+	(i.e. <a href="#correction-classes">Class 5 changes</a>)
+	can be made by re-publishing the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③②">technical report</a> that contains the affected table,
+	without needing to satisfy any other requirements for the publication
+	(not even a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑦">group decision</a>, unless this is required by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑧">registry definition</a>).
+	Such <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change③">registry changes</a> do not trigger new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③④">Advisory Committee Reviews</a>,
+	nor Exclusion Opportunities,
+	and do not require verification via an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①①">update request</a>,
+	even for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③③">technical reports</a> at maturities where this would normally be expected.
+	Such publications can be made
+	even in the absence of a group chartered to maintain the registry
+	when the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian⑥">custodian</a> is another entity.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The custodian is only empowered to make <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change④">registry changes</a>.
+	If the group establishing the registry wishes
+	to empower the custodian to add commentary on individual entries,
+	this needs to be part of the registry table’s definition.
+	If other changes are desired,
+	they need to be requested of the group responsible for maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑨">registry definition</a>—​or in the absence of such a group, of the Team.</p>
+    <p>Changes to the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑨">registry tables</a> made in accordance with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑨">candidate</a> or <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①②">proposed amendments</a> to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⓪">registry definition</a> which would not be allowed by the unamended <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①①">registry definition</a> <em class="rfc2119">must</em> be identified as such.</p>
+    <h4 class="heading settled" data-level="6.5.4" id="reg-data-reports"><span class="secno">6.5.4. </span><span class="content"> Registry Data Reports</span><a class="self-link" href="#reg-data-reports"></a></h4>
+    <p>When the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data①">registry data</a> is published in a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③④">technical report</a> from its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①②">registry definition</a>,
+	that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑤">report</a> is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data-report">Registry Data Report</dfn>.
+	This <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑥">technical report</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">Must</em> link to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①③">registry definition</a> establishing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②⓪">registry tables</a> that it contain. 
+     <li> <em class="rfc2119">May</em> contain non-normative introductory text, examples, and notes
+			about the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②①">registry tables</a> and <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry②">entries</a> that it contains.
+			(Changes to these parts are deemed to be <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑨">editorial changes</a>). 
+    </ul>
+    <p><a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report①">Registry Data Reports</a> do not have maturity stages in and of themselves;
+	The maturity stage of the <a data-link-type="dfn" href="#registry" id="ref-for-registry⑨">registry</a> whose <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data②">data</a> they record
+	is that of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑦">technical report</a> holding the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①④">registry definition</a>.</p>
+    <p>Anytime a change is made to a <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑤">registry definition</a>,
+	the group maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑥">registry definition</a> <em class="rfc2119">must</em> update and republish
+	any document holding the corresponding <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②②">registry tables</a> to make it consistent with these changes.</p>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑧">group decision</a> to do so,
+	the group maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑦">registry definition</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report②">Registry Data Report</a> to incorporate <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①⓪">editorial changes</a>.</p>
+    <h4 class="heading settled" data-level="6.5.5" id="reg-ref-specifications"><span class="secno">6.5.5. </span><span class="content"> Specifications that Reference Registries</span><a class="self-link" href="#reg-ref-specifications"></a></h4>
+    <p>Registries document values,
+	they do not define any architectural or interoperability requirements
+	related to those values.
+	All architectural and interoperability requirements
+	pertaining to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry③">registry entries</a> <em class="rfc2119">must</em> be contained in the specifications that reference the registry,
+	and are therefore subject to the processes
+	(including approval and intellectual property provisions)
+	applicable to those referencing specifications.</p>
+    <p>If there are entries that must be implemented,
+	or any other such restrictions,
+	they <em class="rfc2119">must</em> be defined or documented
+	in the referencing specification
+	without dependency on the registry.</p>
+    <div class="example" id="example-87a6a8f6"><a class="self-link" href="#example-87a6a8f6"></a> For example, <span class="allow-2119">“All implementations must implement the <code>Basic-Method</code> as defined in the registry”</span> is not acceptable because
+		a change to the definition of the <code>Basic-Method</code> in the registry would then affect conformance.
+		Instead, the requirement has to be complete in the specification,
+		directly or by reference to another specification.
+		For example <span class="allow-2119">“All implementations must recognize the name <code>Basic-Method</code>,
+		and implement it as defined by section yy of IETF RFC xxxx”</span>.
+		(The Registry is nonetheless expected to contain <code>Basic-Method</code> as an entry.) </div>
+    <h4 class="heading settled" data-level="6.5.6" id="reg-pat"><span class="secno">6.5.6. </span><span class="content"> Registries and Patents</span><a class="self-link" href="#reg-pat"></a></h4>
+    <p>A <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report⑤">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry③">embedded registry</a> is not subject to the W3C Patent Policy,
+	and <em class="rfc2119">must not</em> define any requirements on implementations.
+	For the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (only),
+	any <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry④">embedded registry</a> in a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①③">Recommendation track</a> document
+	is not a normative portion of that specification.</p>
+    <h3 class="heading settled" data-level="6.6" id="switching-tracks"><span class="secno">6.6. </span><span class="content"> Switching Tracks</span><a class="self-link" href="#switching-tracks"></a></h3>
+    <p>Given a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑨">Group decision</a> to do so, <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦④">Working Groups</a> can republish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑧">technical report</a> on a different track than the one it is on,
+	under the following restrictions:</p>
+    <ul>
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑨">technical report</a> that is or was
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦③">W3C Recommendation</a>, <a data-link-type="dfn" href="#statement" id="ref-for-statement①③">W3C Statement</a>, or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts④">Patent Review Draft</a> cannot switch tracks. 
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④⓪">technical report</a> should not switch away from the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①④">Recommendation Track</a> without due consideration of the Patent Policy implications
+			and approval of W3C’s legal counsel
+			if the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑤">Working Group</a> envisions a likelihood of returning to it later. 
+    </ul>
+    <p><a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④①">Technical reports</a> that switch tracks start at
+	their new track’s initial maturity stage,
+	while retaining any established identity (url, shortname, etc.).</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The initial maturity stage of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⑤">Recommendation track</a> is <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①②">Working Draft</a>. <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑧">First Public Working Draft</a> designates a specific type of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①③">Working Draft</a> and is not a separate maturity stage.
+	A document which switches to the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⑥">Recommendation track</a> is only published as a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑨">First Public Working Draft</a> if it was never previously published as such;
+	otherwise, it is simply a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①④">Working Draft</a>.</p>
+    <h3 class="heading settled" data-level="6.7" id="further-reading"><span class="secno">6.7. </span><span class="content"> Further reading</span><a class="self-link" href="#further-reading"></a></h3>
+    <p>Refer to <a href="https://www.w3.org/guide/transitions/">"How to Organize a Recommendation Track Transition"</a> <a data-link-type="biblio" href="#biblio-transition" title="Organize a Technical Report Transition">[TRANSITION]</a> in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a> for practical information about preparing for the reviews
+	and announcements of the various steps,
+	and <a href="https://www.w3.org/guide/standards-track/rec-tips">tips on getting to Recommendation faster</a> <a data-link-type="biblio" href="#biblio-rec-tips" title="Tips for Getting to Recommendation Faster">[REC-TIPS]</a>.
+	Please see also the <a href="https://www.w3.org/guide/standards-track/republishing">Requirements for modification of W3C Technical Reports</a> <a data-link-type="biblio" href="#biblio-republishing" title="In-place modification of W3C Technical Reports">[REPUBLISHING]</a>.</p>
+    <h2 class="heading settled" data-level="7" id="dissemination"><span class="secno">7. </span><span class="content"> <span id="chapterDissemination"></span> Dissemination Policies</span><a class="self-link" href="#dissemination"></a></h2>
+    <h3 class="heading settled" data-level="7.1" id="pub-com"><span class="secno">7.1. </span><span class="content"> Public Communication</span><a class="self-link" href="#pub-com"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②②">Team</a> is responsible for managing communication within W3C
+	and with the general public
+	(e.g., news services, press releases, managing the website and access privileges, and managing calendars).
+	Members <em class="rfc2119">should</em> solicit review by the Team
+	prior to issuing press releases about their work within W3C.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②③">Team</a> makes every effort to ensure the persistence and availability of the following public information:</p>
+    <ul>
+     <li> <a href="#Reports">W3C technical reports</a> whose publication has been approved.
+			Per <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/policies/"><cite>W3C IPR Policies</cite></a>,
+			W3C technical reports (and software) are available free of charge to the general public. 
+     <li> A <a href="https://www.w3.org/mission/">mission statement</a> <a data-link-type="biblio" href="#biblio-mission" title="The W3C Mission statement">[MISSION]</a> that explains the purpose and mission of W3C,
+			the key benefits for Members,
+			and the organizational structure of W3C. 
+     <li> Legal documents,
+			including <a href="https://www.w3.org/membership/agreement/">Membership Agreements</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> and documentation of any legal commitments W3C has with other entities. 
+     <li> The Process Document. 
+     <li> Public results of W3C activities and <a href="#GAEvents">Workshops</a>. 
+    </ul>
+    <p>To keep the Members abreast of W3C meetings, <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW③">Workshops</a>,
+	and review deadlines,
+	the Team provides them with a regular (e.g., weekly) news service
+	and maintains a <a href="https://www.w3.org/events/">calendar</a> <a data-link-type="biblio" href="#biblio-calendar" title="Calendar of all scheduled official W3C events">[CALENDAR]</a> of official W3C events.
+	Members are encouraged to send schedule and event information to the Team for inclusion on this calendar.</p>
+    <h3 class="heading settled" data-level="7.2" id="confidentiality-levels"><span class="secno">7.2. </span><span class="content"> Confidentiality Levels</span><a class="self-link" href="#confidentiality-levels"></a></h3>
+    <p>There are three principal levels of access to W3C information
+	(on the W3C website, in W3C meetings, etc.):
+	public,
+	Member-only,
+	and Team-only.</p>
+    <p>While much information made available by W3C is public,
+	“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Member-Only" id="Member-only">Member-only</dfn>” information
+	is available to authorized parties only,
+	including representatives of Member organizations, <a href="#invited-expert-wg">Invited Experts</a> (as described in <a href="https://www.w3.org/invited-experts/#memaccess">https://www.w3.org/invited-experts/#memaccess</a>),
+	the Advisory Board,
+	the TAG,
+	and the Team.
+	For example,
+	the <a href="#WGCharter">charter</a> of some Working Groups <em class="rfc2119">may</em> specify a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only④">Member-only</a> confidentiality level for group proceedings.</p>
+    <p>“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team-Only" id="Team-only">Team-only</dfn>” information
+	is available to the Team and other authorized parties.</p>
+    <p>Those authorized to access <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑤">Member-only</a> and <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only①">Team-only</a> information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> treat the information as confidential within W3C, 
+     <li> <em class="rfc2119">must</em> use reasonable efforts to preserve that confidentiality, and 
+     <li> <em class="rfc2119">must not</em> release this information to the general public or press,
+			nor beyond the proper level of access. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②④">Team</a> <em class="rfc2119">must</em> provide mechanisms
+	to protect the confidentiality of <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑥">Member-only</a> information
+	and ensure that authorized parties have proper access to this information.
+	Documents <em class="rfc2119">should</em> clearly indicate
+	whether they require <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑦">Member-only</a> confidentiality.
+	Individuals uncertain of the confidentiality level of a piece of information <em class="rfc2119">should</em> contact the Team.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⓪">Advisory Committee representatives</a> <em class="rfc2119">may</em> authorize <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑧">Member-only</a> access to <a href="#member-rep">Member representatives</a> and other individuals employed by the Member
+	who are considered appropriate recipients.
+	For instance,
+	it is the responsibility of the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③①">Advisory Committee representative</a> and other employees
+	and official representatives of the organization
+	to ensure that Member-only news announcements
+	are distributed for internal use only within their organization.
+	Information about Member mailing lists is available
+	in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h3 class="heading settled" data-level="7.3" id="confidentiality-change"><span class="secno">7.3. </span><span class="content"> Changing Confidentiality Level</span><a class="self-link" href="#confidentiality-change"></a></h3>
+    <p>As a benefit of membership,
+	W3C provides some <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only②">Team-only</a> and <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑨">Member-only</a> channels
+	for certain types of communication.
+	For example, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③②">Advisory Committee representatives</a> can send <a href="#ACReview">reviews</a> to a <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only③">Team-only</a> channel.
+	However, for W3C processes with a significant public component,
+	such as the technical report development process,
+	it is also important for information that affects decision-making to be publicly available.
+	The Team <em class="rfc2119">may</em> need to communicate <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only④">Team-only</a> information to a Working Group or the public.
+	Similarly, a Working Group whose proceedings are <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①⓪">Member-only</a> <em class="rfc2119">must</em> make public
+	information pertinent to the technical report development process.</p>
+    <p>This document clearly indicates which information <em class="rfc2119">must</em> be available to Members or the public,
+	even though that information was initially communicated on <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑤">Team-only</a> or <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①①">Member-only</a> channels.
+	Only the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑤">Team</a> and parties authorized by the Team
+	may change the level of confidentiality of this information.
+	When doing so:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑥">Team</a> <em class="rfc2119">must</em> use a version of the information
+			that was expressly provided by the author for the new confidentiality level.
+			In Calls for Review and other similar messages,
+			the Team <em class="rfc2119">should</em> remind recipients to provide such alternatives. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑦">Team</a> <em class="rfc2119">must not</em> attribute the version
+			for the new confidentiality level to the author without the author’s consent. 
+     <li> If the author has not conveyed to the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑧">Team</a> a version
+			that is suitable for another confidentiality level,
+			the Team <em class="rfc2119">may</em> make available a version that reasonably communicates what is required,
+			while respecting the original level of confidentiality,
+			and without attribution to the original author. 
+    </ol>
+    <h2 class="heading settled" data-level="8" id="Liaisons"><span class="secno">8. </span><span class="content"> Liaisons</span><a class="self-link" href="#Liaisons"></a></h2>
+    <p>W3C uses the term <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="liaison">liaison</dfn> 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 <a data-link-type="dfn" href="#team" id="ref-for-team①②⑨">Team</a> due to requirements for public communication;
+	patent,
+	copyright,
+	and other IPR policies;
+	confidentiality agreements;
+	and mutual membership agreements.</p>
+    <p>W3C <em class="rfc2119">may</em> negotiate <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①">technical agreements</a> with another organization.
+	For purposes of the W3C Process,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="agreement" data-noexport id="technical-agreement">technical agreement</dfn> is a formal contract,
+	or a Memorandum of Understanding (<abbr>MoU</abbr>),
+	or a similar document,
+	between W3C and another party or parties,
+	that relates to the technical activity of the Consortium
+	(e.g., its publications, groups, or liaisons).
+	It specifies rights and obligations of each party toward the others.
+	These rights and obligations <em class="rfc2119">may</em> include joint deliverables,
+	an agreed share of technical responsibilities with due coordination,
+	and/or considerations for confidentiality and specific IPR.</p>
+    <p>Non-technical agreements, including
+	those between W3C and its <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑥">Members</a> for the purposes of membership,
+	between W3C and its Partners for the purposes of partnership <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a>,
+	and other agreements related to the operation of the Consortium
+	or to the ordinary provision of services,
+	are not subject to these Process provisions.</p>
+    <p>When considering a <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement②">technical agreement</a> (i.e., before the decision whether to sign is made),
+	the Team <em class="rfc2119">should</em> provide
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④⓪">Advisory Committee</a> with a draft of the proposed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement③">agreement</a>,
+	along with an explanation of how W3C would benefit from signing this <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement④">agreement</a>,
+	for their review and discussion.
+	After addressing any comments,
+	and subject to any management or governance procedures that apply
+	(e.g., formal review of proposed contracts by legal counsel or by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑦">Board</a>),
+	if the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①②">Team decides</a> to proceed with signing the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑤">agreement</a>,
+	the Team <em class="rfc2119">must</em> announce the intent to sign,
+	and provide the final text of the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑥">agreement</a>,
+	with an explanation of signing rationale, to
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④①">Advisory Committee</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③③">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①⓪">Advisory Committee Appeal</a> of the decision to sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑦">agreement</a>.
+	If the proposal is rejected on <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①①">appeal</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③⓪">Team</a> <em class="rfc2119">must not</em> sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑧">agreement</a> on behalf of W3C
+	unless directed to do so by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑧">Board</a>.
+	A signed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑨">agreement</a> <em class="rfc2119">should</em> be made public.</p>
+    <p>Information about <a href="https://www.w3.org/liaisons/">W3C liaisons with other organizations</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a> and the guidelines W3C follows when creating a liaison is available on the Web.</p>
+    <h2 class="heading settled" data-level="9" id="Submission"><span class="secno">9. </span><span class="bs-old-id" id="SubmissionNo"></span><span class="bs-old-id" id="SubmissionYes"></span><span class="bs-old-id" id="TeamSubmissionRights"></span><span class="bs-old-id" id="SubmissionScope"></span><span class="bs-old-id" id="SubmissionRights"></span><span class="content"> Member Submissions</span><a class="self-link" href="#Submission"></a></h2>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="MemberSubmission">Member Submission</dfn> is a document or set of documents
+	developed outside of W3C,
+	and submitted to W3C
+	by one or more <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑦">Members</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="submitter" id="submitter">Submitter(s)</dfn>)
+	to propose technology or other ideas.
+	After review,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③①">Team</a> <em class="rfc2119">may</em> make the material available at the W3C website.</p>
+    <p>Making a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission">Member Submission</a> available at the W3C website
+	does not indicate endorsement, acceptance, or adoption by W3C,
+	its Team, or its Members.
+	The <a data-link-type="dfn" href="#acknowledged" id="ref-for-acknowledged">acknowledgment</a> of a Submission request
+	does not imply that any action will be taken by W3C.
+	It merely records publicly
+	that the Submission has been made by the Submitter(s).
+	A Member Submission made available by W3C
+	is not a W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④②">technical report</a> and <em class="rfc2119">must not</em> be referred to as
+	an output or “work in progress” of W3C.</p>
+    <p>The <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission①">Member Submission</a> process consists of the following steps:</p>
+    <dl>
+     <dt>Submission 
+     <dd> One of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter">Submitters</a>,
+			copying the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③④">Advisory Committee representatives</a> of the other <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①">Submitters</a> (if any),
+			sends a request to the Team to acknowledge the Submission request.
+			The <a data-link-type="dfn" href="#team" id="ref-for-team①③②">Team</a> and <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②">Submitter(s)</a> communicate to ensure that the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission②">Member Submission</a> is complete. 
+     <dt>Review 
+     <dd>
+       The <a data-link-type="dfn" href="#team" id="ref-for-team①③③">Team</a> reviews the Submission
+			to evaluate its scope, quality, and compliance with the Submission requirements,
+			including licensing requirements: 
+      <ul>
+       <li> The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter③">Submitter(s)</a> and any other authors of the submitted material <em class="rfc2119">must</em> agree
+					to license the Submission under the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a>. 
+       <li> The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments
+					in <a href="https://www.w3.org/policies/patent-policy/#sec-submissions">The W3C Patent Policy § sec-submissions</a>. 
+      </ul>
+      <p>Detailed procedures and requirements are defined by the <a data-link-type="dfn" href="#team" id="ref-for-team①③④">Team</a> and documented in the “<a href="https://www.w3.org/submissions/guide/">Member submissions guidebook</a>” <a data-link-type="biblio" href="#biblio-member-sub" title="Member submissions guidebook">[MEMBER-SUB]</a>.</p>
+     <dt>Decision 
+     <dd>
+       After review, the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑤">Team</a> <em class="rfc2119">must</em> either <a data-link-type="dfn" href="#acknowledged" id="ref-for-acknowledged①">acknowledge</a> or <a data-link-type="dfn" href="#rejected" id="ref-for-rejected">reject</a> the Submission request. 
+      <ul>
+       <li> If <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="acknowledged">acknowledged</dfn>,
+					the Team <em class="rfc2119">must</em> make the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission③">Member Submission</a> available
+					at the public W3C website
+					alongside other <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a> <a data-link-type="biblio" href="#biblio-submission-list" title="The list of acknowledged Member Submissions">[SUBMISSION-LIST]</a>. 
+       <li> If <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rejected">rejected</dfn>,
+					the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑥">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⑤">Advisory Committee representative(s)</a> of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter④">Submitter(s)</a>,
+					and <em class="rfc2119">must</em> provide rationale if requested by the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑤">Submitter(s)</a>.
+					The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑥">Submitter(s)</a> <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals③">Submission Appeal</a>. 
+      </ul>
+    </dl>
+    <p>The <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⑥">Advisory Committee representative(s)</a> of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑦">Submitter(s)</a> <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals④">Submission Appeal</a>.
+	The procedure for handling <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="submission-appeals">Submission Appeals</dfn> is the same as for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④④">Formal Objections</a>,
+	except that an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①②">AC Appeal</a> is not possible
+	and both the Formal Objection and the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report⑥">Council Report</a> are confidential to the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑦">Team</a>, <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑨">TAG</a>, and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③③">AB</a>.</p>
+    <h2 class="heading settled" data-level="10" id="GAProcess"><span class="secno">10. </span><span class="content"> Process Evolution</span><a class="self-link" href="#GAProcess"></a></h2>
+    <p>Revision of the W3C Process and related documents (see below) undergoes similar <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②②">consensus</a>-building processes as for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④③">technical reports</a>,
+	with the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③④">Advisory Board</a> acting as the sponsoring <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑥">Working Group</a>.
+	The documents may be developed by the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑤">AB</a> or by another group to whom the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑥">AB</a> has delegated development.
+	Review includes
+	soliciting input from the W3C community,
+	and in particular the Team.</p>
+    <p>The documents covered by this section are:</p>
+    <ul>
+     <li data-md>
+      <p>the W3C Process (this document)</p>
+     <li data-md>
+      <p>the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a></p>
+     <li data-md>
+      <p>the W3C Code of Conduct <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a></p>
+     <li data-md>
+      <p>The W3C Document License <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a></p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑦">Advisory Board</a> initiates review as follows:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③⑧">Team</a> sends a Call for Review to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④②">Advisory Committee</a> and other W3C groups. 
+     <li> After comments have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑧">formally addressed</a> and the document possibly modified,
+			the Team seeks endorsement from the Members by initiating an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑤">Advisory Committee review</a>.
+			The review period <em class="rfc2119">must</em> last at least <span class="time-interval">28 days</span>. 
+     <li> <a href="#ACReviewAfter">After the Advisory Committee review</a>,
+			following a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑧">W3C decision</a> to adopt the document(s),
+			the Team does so
+			and sends an announcement to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④③">Advisory Committee</a>.
+			Advisory Committee representatives <em class="rfc2119">may</em> initiate
+			an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①③">Advisory Committee Appeal</a> to W3C. 
+    </ol>
+    <p class="note" role="note"><span class="marker">Note:</span> As of June 2020,
+	the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">Patent Policy</a> is developed in the <a href="https://www.w3.org/2004/pp/psig/">Patents and Standards Interest Group</a>,
+	the <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">Code of Conduct</a> in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
+	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.</p>
+    <h2 class="non-normative nonum heading settled" id="old-terms"><span class="content"> Appendix A: Retired Terminology</span><a class="self-link" href="#old-terms"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>Previous versions of this process defined and used various concepts and document statuses
+	that have since been retired or renamed.
+	For ease of reference,
+	this appendix lists the more notable ones,
+	and it links to the the definition or relevant section
+	in the most recent version of the Process that used them,
+	and gives the more recent equivalent term when there is one.</p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rec-amended">Amended Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2020/Process-20200915/#rec-amended">in section 6.2.1 of the 2020 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="edited-recommendation">Edited Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2019/Process-20190301/#maturity-levels">in section 6.1.2 of the 2019 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call">Last Call</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2005/10/Process-20051014/tr.html#last-call">in section 7.4.2 of the 2005 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="maturity-levels">Maturity level</dfn> (renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#maturity-levels">in section 6.3.1 of the 2021 Process</a>,
+			now called <a href="#maturity-stages">maturity stage</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fdn-member-consortium">Member Consortium</dfn>, plural: Member Consortia
+			(renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#fdn-member-consortium">in section 2.1.2.1 of the 2021 Process</a>,
+			now called <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑥">Member Association</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mou">Memorandum of Understanding</dfn>, plural: Memoranda of Understanding, abbreviation: MoU
+			(renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#mou">in section 9 of the 2021 Process</a>,
+			now called <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①⓪">technical agreement</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="other-charter">Other Charter</dfn> (renamed term) 
+     <dd> Last used <a href="https://www.w3.org/2020/Process-20200915/#other-charter">in section 5.2.6 of the 2020 Process</a>,
+			now called <a data-link-type="dfn" href="#exclusion-draft-charter" id="ref-for-exclusion-draft-charter">Exclusion Draft Charter</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="RecsPR">Proposed Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/policies/process/20231103/#RecsPR">in section 6.3.1 of the 2023 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="TeamSubmission">Team Submissions</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2019/Process-20190301/#TeamSubmission">in section 2.2.1 of the 2019 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-W3CChair">W3C Chair</dfn> (renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2014/Process-20140801/#def-W3CChair">in section 2.2 of the 2014 Process</a>,
+			now called <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑨">CEO</a>. 
+    </dl>
+    <h2 class="non-normative nonum heading settled" id="acks"><span class="content"> Appendix B: Acknowledgments</span><a class="self-link" href="#acks"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>The editors are grateful to the following people,
+	who as interested individuals and/or with the affiliation(s) listed,
+	have contributed to this proposal for a revised Process:
+	Adam Basha,
+	Anna Weinberg (Apple)
+	Charles McCathie Nevile,
+	Chris Lilley (W3C),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	Coralie Mercier (W3C),
+	David W. Singer (Apple),
+	Denis Ah-Kang (W3C),
+	Dominique Hazael-Massieux (W3C),
+	Ian Jacobs (W3C),
+	Jeffrey Yasskin (Google),
+	Jill Schmidt (Apple),
+	Marcos Cáceres (Apple),
+	Mark Nottingham,
+	Martin Thomson (Mozilla),
+	Michael Champion,
+	Michael Sirtori (Intel),
+	Mike Smith (W3C),
+	Nick Doty (Center for Democracy and Technology),
+	Nigel Megitt (BBC),
+	Philippe Le Hégaret (W3C),
+	Sam Sneddon (Apple),
+	Shawn Lawton Henry (W3C),
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Theresa O’Connor (Apple),
+	Vivien Lacourba (W3C).</p>
+    <p>The editors are sorry for forgetting any names,
+	and grateful to those who have listened patiently to conversations about this document
+	without feeling a need to add more.</p>
+    <p>The following individuals contributed to the development of earlier versions of the Process:
+	Alex Russell (Google),
+	Andreas Tai (Institut fuer Rundfunktechnik),
+	Andrew Betts (Fastly),
+	Ann Bassetti (The Boeing Company),
+	Anne van Kesteren,
+	Art Barstow (Nokia, unaffiliated),
+	Bede McCall (MITRE),
+	Ben Wilson,
+	Brad Hill (Facebook),
+	Brian Kardell (JQuery, Igalia),
+	Carine Bournez (W3C),
+	Carl Cargill (Netscape, Sun Microsystems, Adobe),
+	Charles McCathie Nevile (ConsenSys),
+	Chris Lilley (W3C),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	Claus von Riegen (SAP AG),
+	Coralie Mercier (W3C),
+	Cullen Jennings (Cisco),
+	Dan Appelquist (Telefonica, Samsung),
+	Dan Connolly (W3C),
+	Daniel Dardailler (W3C),
+	Daniel Glazman (Disruptive Innovations),
+	David Baron (Mozilla),
+	David Fallside (IBM),
+	David W. Singer (Apple),
+	David Singer (IBM),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Don Brutzman (Web3D),
+	Don Deutsch (Oracle),
+	Eduardo Gutentag (Sun Microsystems),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Florian Rivoal,
+	Fuqiao Xue (W3C),
+	Geoffrey Creighton (Microsoft),
+	Giri Mandyam (Qualcomm),
+	Gregg Kellogg,
+	Hadley Beeman,
+	Håkon Wium Lie (Opera Software),
+	Helene Workman (Apple),
+	Henri Sivonen (Mozilla),
+	Ian Hickson (Google),
+	Ian Jacobs (W3C),
+	Ivan Herman (W3C),
+	J Alan Bird (W3C),
+	Jay Kishigami 岸上順一 (NTT),
+	Jean-Charles Verdié (MStar),
+	Jean-François Abramatic (IBM, ILOG, W3C),
+	Jeff Jaffe (W3C),
+	Jeffrey Yasskin (Google),
+	Jim Bell (HP),
+	Jim Miller (W3C),
+	Joe Hall (CDT),
+	John Klensin (MCI),
+	Josh Soref (BlackBerry, unaffiliated),
+	Judy Brewer (W3C),
+	Judy Zhu 朱红儒 (Alibaba),
+	Kari Laihonen (Ericsson),
+	Karl Dubost (Mozilla),
+	Ken Laskey (MITRE),
+	Kevin Fleming (Bloomberg),
+	Klaus Birkenbihl (Fraunhofer Gesellschaft),
+	Larry Masinter (Adobe Systems),
+	Lauren Wood (unaffiliated),
+	Léonie Watson (The Paciello Group),
+	Liam Quin (W3C),
+	Marcos Cáceres (Mozilla),
+	Maria Courtemanche (IBM),
+	Mark Crawford (SAP),
+	Mark Nottingham,
+	Michael Champion (Microsoft),
+	Michael Geldblum (Oracle),
+	Mike West (Google),
+	Mitch Stoltz (EFF),
+	Natasha Rooney (GSMA),
+	Nigel Megitt (BBC),
+	Olle Olsson (SICS),
+	Ora Lassila (Nokia),
+	Paul Cotton (Microsoft),
+	Paul Grosso (Arbortext),
+	Peter Linss,
+	Peter Patel-Schneider,
+	Philippe Le Hégaret (W3C),
+	Qiuling Pan (Huawei),
+	Ralph Swick (W3C),
+	Renato Iannella (IPR Systems),
+	Rigo Wenning (W3C),
+	Rob Sanderson (J Paul Getty Trust),
+	Robin Berjon (W3C),
+	Sally Khudairi (W3C),
+	Sam Ruby (IBM),
+	Sam Sneddon,
+	Samuel Weiler (W3C),
+	Sandro Hawke (W3C),
+	Sangwhan Moon (Odd Concepts),
+	Scott Peterson (Google),
+	Shawn Lawton Henry,
+	Steve Holbrook (IBM),
+	Steve Zilles (Adobe Systems)
+	Steven Pemberton (CWI),
+	TV Raman (Google),
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Terence Eden (Her Majesty’s Government),
+	Thomas Reardon (Microsoft),
+	Tim Berners-Lee (W3C),
+	Tim Krauskopf (Spyglass),
+	Travis Leithead (Microsoft),
+	Virginia Fournier (Apple),
+	Virginie Galindo (Gemalto),
+	Wayne Carr (Intel),
+	Wendy Fong (Hewlett-Packard),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <h2 class="non-normative nonum heading settled" id="changes"><span class="content"> Appendix C: Changes</span><a class="self-link" href="#changes"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <h3 class="no-num heading settled" id="changes-2025"><span class="content"> Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></span><a class="self-link" href="#changes-2025"></a></h3>
+    <p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
+	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2F">diff from Process 2023 to this latest version</a>,
+	as well as
+	a <a href="https://github.com/w3c/process/compare/p2023_1...main">detailed log of all changes since then</a> are available. </p>
+    <p>In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:</p>
+    <dl>
+     <dt id="changes-2025-tr"><a class="self-link" href="#changes-2025-tr"></a>Changes to technical reports and their publication 
+     <dd>
+      <ul>
+       <li> <strong> Retire the Proposed Recommendation phase of the Recommendation track. </strong> It was only used as a short-lived transition
+					during which various verifications and votes about CR were done.
+					These can be done on a CR
+					without having to republish it as a separate thing.
+					This simplifies the Process without changing the actual quality or consensus expectations.
+					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 
+       <li id="streamlined-update"><a class="self-link" href="#streamlined-update"></a> Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
+					This was meant to enable REC track publication with fewer/faster approval steps
+					when some stricter than usual criteria were fulfilled.
+					However, regular REC track publication have improved enough
+					that this became unnecessary,
+					and nobody was using it.
+					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>) 
+       <li> Add a requirement to make progress on external issues for update requests
+					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>) 
+       <li> Drop the requirement to publish every 6 months if nothing has changed.
+					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>) 
+       <li> Enable Team to replace defunct registry custodians when no-one else can.
+					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>) 
+       <li> Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
+					in addition to Working Groups.
+					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>) 
+       <li> Rename “registry sections” to <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry⑤">embedded registries</a> to avoid confusion over whether they can be split across multiple sections of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦④">Recommendation</a>.
+					(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>) 
+       <li> Rename "Draft Note" into "Note Draft",
+					and "Draft Registry" into "Registry Draft"
+					to be consistent with other statuses that uses the word "Draft",
+					and to make that word stand out more.
+					(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>) 
+       <li> Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
+					and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>). 
+       <li> Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a> the various parts of the Process
+					that described whether and how the Team can maintain technical reports
+					that no longer have a Group chartered to maintain them.
+					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>) 
+      </ul>
+     <dt id="changes-2025-charter"><a class="self-link" href="#changes-2025-charter"></a>Changes to chartering 
+     <dd>
+      <ul>
+       <li> <strong> Introduce a formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①②">Charter Refinement</a> phase prior to the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑥">AC Review</a>. </strong> (See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>) 
+       <li> Be more specific about which types of changes to a charter must go through AC Review.
+					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>) 
+       <li> Require Chairs to be listed in Charters.
+					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>) 
+       <li> Reorganize and rephrase <a href="#CharterReview">§ 4.4 Charter Review and Approval</a> for readability and ease of understanding.
+					This change, while moderate in size, is purely editorial.
+					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>) 
+      </ul>
+     <dt id="changes-2025-decisions"><a class="self-link" href="#changes-2025-decisions"></a>Changes to formal decision making and escalation 
+     <dd>
+      <ul>
+       <li> Adjust the rules guiding initiation of Councils,
+					to make the deadline strict,
+					and to provide a fallback mechanism if they are not met.
+					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>) 
+       <li> Make the Council’s short-circuit a little more flexible.
+					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>) 
+       <li> Exclude TAG/AB Members from voting on TAG/AB proposals in Councils.
+					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>) 
+       <li> Limit the involvement of Tim Berners-Lee to the TAG proper,
+					not including the Council.
+					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>) 
+       <li> Council dismissal vote counts must be reported.
+					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>) 
+       <li> Require documentation of how Formal Objections get resolved.
+					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>) 
+       <li> Put constraints on the timing of making Formal Objections public.
+					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>) 
+       <li> Fine-tune the rules about
+					how changes can be incorporated into a proposal
+					following an AC Review.
+					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>) 
+       <li> Adjust AC appeal vote threshold based on participation,
+					aligning with the thresholds and super majority requirements
+					for "Requisite Member Vote" from the W3C Bylaws.
+					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>) 
+       <li> Let the originator of a proposal decide whether to try again
+					after addressing feedback
+					following an AC Appeal.
+					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>) 
+       <li> Simplify provisions regarding substitute representatives and proxies.
+					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>) 
+      </ul>
+     <dt id="changes-other"><a class="self-link" href="#changes-other"></a>Other changes 
+     <dd>
+      <ul>
+       <li> Reuse the bylaws’ notion of Good Standing,
+					and restrict TAG and AB elections
+					as well as AC Votes where a decision is made based on counting ballots
+					to Members in Good Standing.
+					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a> and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>) 
+       <li> The section on Member Submissions was significantly shortened and simplified,
+					reducing the complexity under formal Process authority,
+					and shifting much of the material to /Guide,
+					under Team authority.
+					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a> and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>) 
+       <li> Clarify how the outcome of certain ballots are determined.
+					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>) 
+       <li> Stop citing the superseded TAG charter.
+					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>) 
+       <li> Clarify amount of leeway around incomplete nominations to TAG or AB elections.
+					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>) 
+       <li> Shift most of the non-normative discussion about Workshops to <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>,
+					and reorganize the remaining normative requirements.
+					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>) 
+       <li> The URL of this document was changed
+					from /Consortium/Process/ to /policies/process/
+					for better integration in the W3C website architecture. 
+      </ul>
+      <h3 class="no-num heading settled" id="changes-previous"><span class="bs-old-id" id="changes-2017"></span><span class="bs-old-id" id="changes-2018"></span><span class="bs-old-id" id="changes-2019"></span><span class="bs-old-id" id="changes-2020"></span><span class="bs-old-id" id="changes-2021"></span><span class="bs-old-id" id="changes-2023"></span><span class="bs-old-id" id="changes-2023-1"></span><span class="content"> Changes since earlier versions</span><a class="self-link" href="#changes-previous"></a></h3>
+      <p>Changes since earlier versions of the Process are detailed
+	in the <a href="https://www.w3.org/policies/process/20231103/#changes">changes section of the previous version</a> of the Process.</p>
+    </dl>
+   </main>
+   <div data-fill-with="conformance">
+    <h2 class="no-ref no-num heading settled" id="w3c-conformance"><span class="content">Conformance</span><a class="self-link" href="#w3c-conformance"></a></h2>
+    <h3 class="no-ref no-num heading settled" id="w3c-conventions"><span class="content">Document conventions</span><a class="self-link" href="#w3c-conventions"></a></h3>
+    <p>Conformance requirements are expressed
+
+    with a combination of descriptive assertions
+
+    and RFC 2119 terminology.
+
+    The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
+
+    in the normative parts of this document
+
+    are to be interpreted as described in RFC 2119.
+
+    However, for readability,
+
+    these words do not appear in all uppercase letters in this specification. </p>
+    <p>All of the text of this specification is normative
+
+    except sections explicitly marked as non-normative, examples, and notes. <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a> </p>
+    <p>Examples in this specification are introduced with the words “for example”
+
+    or are set apart from the normative text
+
+    with <code>class="example"</code>,
+
+    like this: </p>
+    <div class="example" id="w3c-example">
+     <a class="self-link" href="#w3c-example"></a> 
+     <p>This is an example of an informative example. </p>
+    </div>
+    <p>Informative notes begin with the word “Note”
+
+    and are set apart from the normative text
+
+    with <code>class="note"</code>,
+
+    like this: </p>
+    <p class="note" role="note">Note, this is an informative note.</p>
+   </div>
+   <script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script>
+  </main>
+  <h2 class="no-num no-ref heading settled" id="index"><span class="content">Index</span><a class="self-link" href="#index"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="content">Terms defined by this specification</span><a class="self-link" href="#index-defined-here"></a></h3>
+  <ul class="index">
+   <li><a href="#advisory-board">AB</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">AC</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">AC Appeal</a><span>, in § 5.9</span>
+   <li><a href="#acknowledged">acknowledged</a><span>, in § 9</span>
+   <li><a href="#advisory-committee-representative">AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">AC Review</a><span>, in § 5.7</span>
+   <li><a href="#adequate-implementation">adequate implementation experience</a><span>, in § 6.3.2</span>
+   <li><a href="#adopted-draft">Adopted Draft</a><span>, in § 4.3</span>
+   <li><a href="#advisory-board">Advisory Board</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">Advisory Committee</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">Advisory Committee Appeal</a><span>, in § 5.9</span>
+   <li><a href="#advisory-committee-representative">Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">Advisory Committee review</a><span>, in § 5.7</span>
+   <li><a href="#affirm">affirm</a><span>, in § 5.6.2.7</span>
+   <li><a href="#technical-agreement">agreement</a><span>, in § 8</span>
+   <li><a href="#allow-new-features">allow new features</a><span>, in § 6.3.1</span>
+   <li><a href="#alternate-ac-representative">alt AC rep</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#rec-amended">Amended Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#advisory-committee-appeal">Appeal</a><span>, in § 5.9</span>
+   <li><a href="#appeal-vote">appeal vote</a><span>, in § 5.9</span>
+   <li><a href="#at-risk">at risk</a><span>, in § 6.3.7</span>
+   <li><a href="#bod">Board</a><span>, in § 2.2</span>
+   <li><a href="#bod">Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#bod">BoD</a><span>, in § 2.2</span>
+   <li><a href="#reviewform">Call for Review</a><span>, in § 5.7.1</span>
+   <li><a href="#candidate-addition">candidate addition</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-amendment">candidate amendment</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-correction">candidate correction</a><span>, in § 6.2.5</span>
+   <li><a href="#RecsCR">Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">Candidate Recommendation Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-review-period">Candidate Recommendation review period</a><span>, in § 6.3.7</span>
+   <li><a href="#candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-registry">Candidate Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-draft">Candidate Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-snapshot">Candidate Registry Snapshot</a><span>, in § 6.5.2</span>
+   <li><a href="#ceo">CEO</a><span>, in § 2.2</span>
+   <li><a href="#GeneralChairs">Chair</a><span>, in § 3.4.1</span>
+   <li><a href="#chair-decisions">chair decisions</a><span>, in § 5.1</span>
+   <li><a href="#charter">charter</a><span>, in § 4.3</span>
+   <li><a href="#charter-draft">charter draft</a><span>, in § 4.1</span>
+   <li><a href="#chartered-group">chartered groups</a><span>, in § 3.4</span>
+   <li><a href="#dfn-charter-extension">charter extension</a><span>, in § 4.6</span>
+   <li><a href="#chartering-facilitator">Chartering Facilitator</a><span>, in § 4.2</span>
+   <li><a href="#charter-refinement">charter refinement</a><span>, in § 4.2</span>
+   <li><a href="#charter-review-notice">charter review notice</a><span>, in § 4.1</span>
+   <li><a href="#def-Consensus">Consensus</a><span>, in § 5.2.1</span>
+   <li><a href="#convened">convened</a><span>, in § 5.6.2.6</span>
+   <li><a href="#w3c-council">Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#council-report">Council Report</a><span>, in § 5.6.2.8</span>
+   <li><a href="#council-staff-contact">Council Staff Contact</a><span>, in § 5.6.2.1</span>
+   <li><a href="#RecsCR">CR</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">CRD</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-snapshot">CRS</a><span>, in § 6.3.1</span>
+   <li><a href="#custodian">custodian</a><span>, in § 6.5.1</span>
+   <li><a href="#discontinuedREC">Discontinued Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#dismissed">dismiss</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissal</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissed</a><span>, in § 5.6.2.3</span>
+   <li><a href="#def-Dissent">Dissent</a><span>, in § 5.2.1</span>
+   <li><a href="#distributed-meeting">distributed meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#editors-draft">ED</a><span>, in § 6.3.1</span>
+   <li><a href="#edited-recommendation">Edited Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#editors-draft">Editor Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#editorial-change">editorial change</a><span>, in § 6.2.3</span>
+   <li><a href="#editors-draft">Editor's Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#elected-group">elected groups</a><span>, in § 3.3</span>
+   <li><a href="#embedded-registry">embedded registry</a><span>, in § 6.5.2</span>
+   <li><a href="#erratum">errata</a><span>, in § 6.2.4</span>
+   <li><a href="#erratum">erratum</a><span>, in § 6.2.4</span>
+   <li><a href="#exclusion-draft">Exclusion Draft</a><span>, in § 4.3</span>
+   <li><a href="#exclusion-draft-charter">Exclusion Draft Charter</a><span>, in § 4.3</span>
+   <li><a href="#ftf-meeting">face-to-face meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#fpwd">First Public Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#formally-addressed">formally addressed</a><span>, in § 5.3</span>
+   <li><a href="#FormalObjection">Formal Objection</a><span>, in § 5.5</span>
+   <li><a href="#fully-addressed">fully addressed</a><span>, in § 5.6.2.7</span>
+   <li><a href="#good-standing">Good Standing</a><span>, in § 2.1.3</span>
+   <li><a href="#w3c-group">group</a><span>, in § 3</span>
+   <li><a href="#group-decision">group decision</a><span>, in § 5.1</span>
+   <li><a href="#WGNote">Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsIG">Interest Groups</a><span>, in § 3.4</span>
+   <li><a href="#invited-expert-in-an-interest-group">Invited Expert in an Interest Group</a><span>, in § 3.4.3.4</span>
+   <li><a href="#invited-expert-in-a-working-group">Invited Expert in a Working Group</a><span>, in § 3.4.3.3</span>
+   <li><a href="#last-call">Last Call</a><span>, in § Unnumbered section</span>
+   <li><a href="#last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-review">Last Call for Review of Proposed Amendments</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#liaison">liaison</a><span>, in § 8</span>
+   <li><a href="#maturity-levels">Maturity level</a><span>, in § Unnumbered section</span>
+   <li><a href="#w3c-member">Member</a><span>, in § 2.1</span>
+   <li><a href="#member-association">Member Association</a><span>, in § 2.1.2.1</span>
+   <li><a href="#member-association">Member Associations</a><span>, in § 2.1.2.1</span>
+   <li><a href="#fdn-member-consortium">Member Consortium</a><span>, in § Unnumbered section</span>
+   <li><a href="#Member-only">Member-Only</a><span>, in § 7.2</span>
+   <li><a href="#member-representative-in-an-interest-group">Member representative in an Interest Group</a><span>, in § 3.4.3.2</span>
+   <li><a href="#member-representative-in-a-working-group">Member representative in a Working Group</a><span>, in § 3.4.3.1</span>
+   <li><a href="#MemberSubmission">Member Submission</a><span>, in § 9</span>
+   <li><a href="#mou">Memorandum of Understanding</a><span>, in § Unnumbered section</span>
+   <li><a href="#minor-changes">minor changes</a><span>, in § 4.4.2</span>
+   <li><a href="#minority-opinion">Minority Opinion</a><span>, in § 5.6.2.7</span>
+   <li><a href="#minutes">minutes</a><span>, in § 3.1.2.2</span>
+   <li><a href="#WGNote">Note</a><span>, in § 6.4.1</span>
+   <li><a href="#note-draft">Note Draft</a><span>, in § 6.4.1</span>
+   <li><a href="#not-required">not required</a><span>, in § Unnumbered section</span>
+   <li><a href="#RecsObs">Obsolete Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#obsolete-registry">Obsolete Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#other-charter">Other Charter</a><span>, in § Unnumbered section</span>
+   <li><a href="#overrule">overrule</a><span>, in § 5.6.2.7</span>
+   <li><a href="#overturn">overturn</a><span>, in § 5.6.2.7</span>
+   <li><a href="#participant">participant</a><span>, in § 3</span>
+   <li><a href="#igparticipant">participants in an Interest Group</a><span>, in § 3.4.2</span>
+   <li><a href="#wgparticipant">participants in a Working Group</a><span>, in § 3.4.2</span>
+   <li><a href="#inv-expert-info">participate in a Working Group as an Invited Expert</a><span>, in § 3.4.3.3</span>
+   <li><a href="#patent-review-drafts">Patent Review Drafts</a><span>, in § 6.3</span>
+   <li><a href="#primary-affiliation">primary affiliation</a><span>, in § 3.3.3.3</span>
+   <li><a href="#proposed-additions">proposed additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#proposed-amendments">proposed amendments</a><span>, in § 6.3.10.4</span>
+   <li><a href="#proposed-corrections">proposed corrections</a><span>, in § 6.3.10.4</span>
+   <li><a href="#RecsPR">Proposed Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#public-participant-ig">public participants</a><span>, in § 3.4.2</span>
+   <li><a href="#publishing">publish</a><span>, in § 6.2.1</span>
+   <li><a href="#RecsW3C">REC</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsW3C">Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">Recommendation-track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">Recommendation Track document</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">Recommendation-track document</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">REC Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">REC Track document</a><span>, in § 6.3</span>
+   <li><a href="#registry">registry</a><span>, in § 6.5</span>
+   <li><a href="#registry-change">registry change</a><span>, in § 6.2.3</span>
+   <li><a href="#registry-data">registry data</a><span>, in § 6.5</span>
+   <li><a href="#registry-data-report">Registry Data Report</a><span>, in § 6.5.4</span>
+   <li><a href="#registry-definition">registry definition</a><span>, in § 6.5.1</span>
+   <li><a href="#registry-draft">Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-entry">registry entry</a><span>, in § 6.5</span>
+   <li><a href="#registry-report">registry report</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-table">registry table</a><span>, in § 6.5</span>
+   <li><a href="#registry-track">Registry Track</a><span>, in § 6.5.2</span>
+   <li><a href="#rejected">rejected</a><span>, in § 9</span>
+   <li><a href="#related-member">Related Member</a><span>, in § 2.1.2.2</span>
+   <li><a href="#renounce">renounce</a><span>, in § 5.6.2.3</span>
+   <li><a href="#renounce">renunciation</a><span>, in § 5.6.2.3</span>
+   <li><a href="#rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#RescindedRec">Rescinded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#group-decision">resolution</a><span>, in § 5.1</span>
+   <li><a href="#TeamContact">Staff Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#statement">Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#submission-appeals">Submission Appeals</a><span>, in § 9</span>
+   <li><a href="#submitter">submitter</a><span>, in § 9</span>
+   <li><a href="#subsidiary">subsidiary</a><span>, in § 2.1.2.2</span>
+   <li><a href="#substantive-change">substantive change</a><span>, in § 6.2.3</span>
+   <li><a href="#mtg-substitute">substitute</a><span>, in § 3.4.2</span>
+   <li><a href="#RecsSup">Superseded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#superseded-registry">Superseded Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#supplemental-confidential-council-report">Supplemental Confidential Council Report</a><span>, in § 5.6.2.8</span>
+   <li><a href="#technical-architecture-group">TAG</a><span>, in § 3.3.2.1</span>
+   <li><a href="#team">Team</a><span>, in § 2.2</span>
+   <li><a href="#team-contact">Team Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#team-correction">Team correction</a><span>, in § 6.2.6</span>
+   <li><a href="#team-decision">Team Decision</a><span>, in § 5.1</span>
+   <li><a href="#Team-only">Team-Only</a><span>, in § 7.2</span>
+   <li><a href="#team-representative-in-an-interest-group">Team representative in an Interest Group</a><span>, in § 3.4.3.6</span>
+   <li><a href="#team-representative-in-a-working-group">Team representative in a Working Group</a><span>, in § 3.4.3.5</span>
+   <li><a href="#team-decision">Team's Decision</a><span>, in § 5.1</span>
+   <li><a href="#TeamSubmission">Team Submissions</a><span>, in § Unnumbered section</span>
+   <li><a href="#technical-agreement">technical agreement</a><span>, in § 8</span>
+   <li><a href="#technical-architecture-group">Technical Architecture Group</a><span>, in § 3.3.2.1</span>
+   <li><a href="#technical-report">Technical Report</a><span>, in § 6.2.1</span>
+   <li><a href="#trans-req">Transition Requests</a><span>, in § 6.3.3</span>
+   <li><a href="#def-Unanimity">Unanimity</a><span>, in § 5.2.1</span>
+   <li><a href="#update-requests">Update Requests</a><span>, in § 6.3.4</span>
+   <li><a href="#upheld">upheld</a><span>, in § 5.6.2.7</span>
+   <li><a href="#bod">W3C Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#RecsCR">W3C Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#def-W3CChair">W3C Chair</a><span>, in § Unnumbered section</span>
+   <li><a href="#w3c-council">W3C Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">W3C Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#def-w3c-decision">W3C decision</a><span>, in § 5.1</span>
+   <li><a href="#fellows">W3C Fellows</a><span>, in § 2.2</span>
+   <li><a href="#w3c-group">W3C Group</a><span>, in § 3</span>
+   <li><a href="#w3c-member">W3C Member</a><span>, in § 2.1</span>
+   <li><a href="#RecsW3C">W3C Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">W3C Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">W3C Recommendation Track document</a><span>, in § 6.3</span>
+   <li><a href="#w3c-registry">W3C Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#statement">W3C Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#team">W3C Team</a><span>, in § 2.2</span>
+   <li><a href="#RecsWD">W3C Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsWD">WD</a><span>, in § 6.3.1</span>
+   <li><a href="#dfn-wide-review">wide review</a><span>, in § 6.2.2.1</span>
+   <li><a href="#RecsWD">Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#GroupsWG">Working Groups</a><span>, in § 3.4</span>
+   <li><a href="#EventsW">Workshop</a><span>, in § 2.1.1</span>
+  </ul>
+  <h3 class="no-num no-ref heading settled" id="index-defined-elsewhere"><span class="content">Terms defined by reference</span><a class="self-link" href="#index-defined-elsewhere"></a></h3>
+  <ul class="index">
+   <li>
+    <a data-link-type="biblio">[W3C-PATENT-POLICY]</a> defines the following terms:
+    <ul>
+     <li><span class="dfn-paneled" id="33fd2aef">Exclusion Opportunity</span>
+     <li><span class="dfn-paneled" id="74c78a1e">Patent Advisory Group</span>
+    </ul>
+   <li>
+    <a data-link-type="biblio">[W3C-PROCESS]</a> defines the following terms:
+    <ul>
+     <li><span class="dfn-paneled" id="3a585f2f">W3C Note</span>
+    </ul>
+  </ul>
+  <h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
+  <dl>
+   <dt id="biblio-coc">[COC]
+   <dd><a href="https://www.w3.org/policies/code-of-conduct/"><cite>W3C Code of Conduct</cite></a>. URL: <a href="https://www.w3.org/policies/code-of-conduct/">https://www.w3.org/policies/code-of-conduct/</a>
+   <dt id="biblio-collaborators-agreement">[COLLABORATORS-AGREEMENT]
+   <dd><a href="https://www.w3.org/invited-experts/agreement-2023/"><cite>Invited expert and collaborators agreement</cite></a>. URL: <a href="https://www.w3.org/invited-experts/agreement-2023/">https://www.w3.org/invited-experts/agreement-2023/</a>
+   <dt id="biblio-conflict-policy">[CONFLICT-POLICY]
+   <dd><a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/"><cite>Conflict of Interest Policy for the W3C Team</cite></a>. URL: <a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/">https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/</a>
+   <dt id="biblio-doc-license">[DOC-LICENSE]
+   <dd><a href="https://www.w3.org/copyright/document-license-2023/"><cite>W3C Document License</cite></a>. URL: <a href="https://www.w3.org/copyright/document-license-2023/">https://www.w3.org/copyright/document-license-2023/</a>
+   <dt id="biblio-patent-policy">[PATENT-POLICY]
+   <dd><a href="https://www.w3.org/policies/patent-policy/"><cite>The W3C Patent Policy</cite></a>. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
+   <dt id="biblio-patent-policy-2004">[PATENT-POLICY-2004]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy-20170801/"><cite>The W3C 2004 Patent Policy, Updated 2017</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy-20170801/">https://www.w3.org/Consortium/Patent-Policy-20170801/</a>
+   <dt id="biblio-patent-policy-2020">[PATENT-POLICY-2020]
+   <dd><a href="https://www.w3.org/policies/patent-policy/20200915/"><cite>The W3C 2020 Patent Policy</cite></a>. URL: <a href="https://www.w3.org/policies/patent-policy/20200915/">https://www.w3.org/policies/patent-policy/20200915/</a>
+   <dt id="biblio-pubrules">[PUBRULES]
+   <dd><a href="https://www.w3.org/pubrules/"><cite>Publication Rules</cite></a>. URL: <a href="https://www.w3.org/pubrules/">https://www.w3.org/pubrules/</a>
+   <dt id="biblio-rfc2119">[RFC2119]
+   <dd>S. Bradner. <a href="https://datatracker.ietf.org/doc/html/rfc2119"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. March 1997. Best Current Practice. URL: <a href="https://datatracker.ietf.org/doc/html/rfc2119">https://datatracker.ietf.org/doc/html/rfc2119</a>
+   <dt id="biblio-rfc3797">[RFC3797]
+   <dd>D. Eastlake 3rd. <a href="https://www.rfc-editor.org/rfc/rfc3797"><cite>Publicly Verifiable Nominations Committee (NomCom) Random Selection</cite></a>. June 2004. Informational. URL: <a href="https://www.rfc-editor.org/rfc/rfc3797">https://www.rfc-editor.org/rfc/rfc3797</a>
+   <dt id="biblio-w3c-patent-policy">[W3C-PATENT-POLICY]
+   <dd>Wendy Seltzer. <a href="https://www.w3.org/policies/patent-policy/"><cite>W3C Patent Policy</cite></a>. 15 September 2020. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
+   <dt id="biblio-w3c-process">[W3C-PROCESS]
+   <dd>Elika J. Etemad (fantasai); Florian Rivoal. <a href="https://www.w3.org/policies/process/"><cite>W3C Process Document</cite></a>. 3 November 2023. URL: <a href="https://www.w3.org/policies/process/">https://www.w3.org/policies/process/</a>
+  </dl>
+  <h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
+  <dl>
+   <dt id="biblio-ab-hp">[AB-HP]
+   <dd><a href="https://www.w3.org/2002/ab/"><cite>The Advisory Board home page</cite></a>. URL: <a href="https://www.w3.org/2002/ab/">https://www.w3.org/2002/ab/</a>
+   <dt id="biblio-ac-meeting">[AC-MEETING]
+   <dd><a href="https://www.w3.org/events/ac/"><cite>Advisory Committee meetings (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/events/ac/">https://www.w3.org/events/ac/</a>
+   <dt id="biblio-bg-cg">[BG-CG]
+   <dd><a href="https://www.w3.org/community/about/process/"><cite>Community and Business Group Process</cite></a>. URL: <a href="https://www.w3.org/community/about/process/">https://www.w3.org/community/about/process/</a>
+   <dt id="biblio-bylaws">[BYLAWS]
+   <dd><a href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a>. URL: <a href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf">https://www.w3.org/2024/09/25-w3c-bylaws.pdf</a>
+   <dt id="biblio-calendar">[CALENDAR]
+   <dd><a href="https://www.w3.org/events/"><cite>Calendar of all scheduled official W3C events</cite></a>. URL: <a href="https://www.w3.org/events/">https://www.w3.org/events/</a>
+   <dt id="biblio-chair">[CHAIR]
+   <dd><a href="https://www.w3.org/guide/chair/role"><cite>W3C Working/Interest Group Chair</cite></a>. URL: <a href="https://www.w3.org/guide/chair/role">https://www.w3.org/guide/chair/role</a>
+   <dt id="biblio-charter">[CHARTER]
+   <dd><a href="https://www.w3.org/guide/process/charter"><cite>How to Create a Working Group or Interest Group</cite></a>. URL: <a href="https://www.w3.org/guide/process/charter">https://www.w3.org/guide/process/charter</a>
+   <dt id="biblio-council-report-index">[COUNCIL-REPORT-INDEX]
+   <dd><a href="https://www.w3.org/about/council/"><cite>Council Report Index</cite></a>. URL: <a href="https://www.w3.org/about/council/">https://www.w3.org/about/council/</a>
+   <dt id="biblio-current-ac">[CURRENT-AC]
+   <dd><a href="https://www.w3.org/Member/ACList"><cite>Current Advisory Committee representatives (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/ACList">https://www.w3.org/Member/ACList</a>
+   <dt id="biblio-decision-appeal">[DECISION-APPEAL]
+   <dd><a href="https://www.w3.org/guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a>. URL: <a href="https://www.w3.org/guide/process/ac-appeal">https://www.w3.org/guide/process/ac-appeal</a>
+   <dt id="biblio-election-howto">[ELECTION-HOWTO]
+   <dd><a href="https://www.w3.org/guide/process/election"><cite>How to Organize an Advisory Board or TAG election</cite></a>. URL: <a href="https://www.w3.org/guide/process/election">https://www.w3.org/guide/process/election</a>
+   <dt id="biblio-fellows">[FELLOWS]
+   <dd><a href="https://www.w3.org/careers/fellows/"><cite>W3C Fellows Program</cite></a>. URL: <a href="https://www.w3.org/careers/fellows/">https://www.w3.org/careers/fellows/</a>
+   <dt id="biblio-group-mail">[GROUP-MAIL]
+   <dd><a href="https://www.w3.org/groups/"><cite>Group mailing lists</cite></a>. URL: <a href="https://www.w3.org/groups/">https://www.w3.org/groups/</a>
+   <dt id="biblio-guide">[GUIDE]
+   <dd><a href="https://www.w3.org/guide/"><cite>The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators</cite></a>. URL: <a href="https://www.w3.org/guide/">https://www.w3.org/guide/</a>
+   <dt id="biblio-intro">[INTRO]
+   <dd><a href="https://www.w3.org/Member/Intro"><cite>Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/Intro">https://www.w3.org/Member/Intro</a>
+   <dt id="biblio-join">[JOIN]
+   <dd><a href="https://www.w3.org/membership/join/"><cite>How to Join W3C</cite></a>. URL: <a href="https://www.w3.org/membership/join/">https://www.w3.org/membership/join/</a>
+   <dt id="biblio-liaison">[LIAISON]
+   <dd><a href="https://www.w3.org/liaisons/"><cite>W3C liaisons with other organizations</cite></a>. URL: <a href="https://www.w3.org/liaisons/">https://www.w3.org/liaisons/</a>
+   <dt id="biblio-member-agreement">[MEMBER-AGREEMENT]
+   <dd><a href="https://www.w3.org/membership/agreement/"><cite>W3C Membership Agreement</cite></a>. URL: <a href="https://www.w3.org/membership/agreement/">https://www.w3.org/membership/agreement/</a>
+   <dt id="biblio-member-hp">[MEMBER-HP]
+   <dd><a href="https://www.w3.org/Member/"><cite>Member website (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/">https://www.w3.org/Member/</a>
+   <dt id="biblio-member-list">[MEMBER-LIST]
+   <dd><a href="https://www.w3.org/membership/list/"><cite>The list of current W3C Members</cite></a>. URL: <a href="https://www.w3.org/membership/list/">https://www.w3.org/membership/list/</a>
+   <dt id="biblio-member-sub">[MEMBER-SUB]
+   <dd><a href="https://www.w3.org/submissions/guide/"><cite>Member submissions guidebook</cite></a>. URL: <a href="https://www.w3.org/submissions/guide/">https://www.w3.org/submissions/guide/</a>
+   <dt id="biblio-mission">[MISSION]
+   <dd><a href="https://www.w3.org/mission/"><cite>The W3C Mission statement</cite></a>. URL: <a href="https://www.w3.org/mission/">https://www.w3.org/mission/</a>
+   <dt id="biblio-obs-resc">[OBS-RESC]
+   <dd><a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded"><cite>Obsoleting and Rescinding W3C Specifications</cite></a>. URL: <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">https://www.w3.org/guide/process/obsolete-rescinded-supserseded</a>
+   <dt id="biblio-rec-tips">[REC-TIPS]
+   <dd><a href="https://www.w3.org/guide/standards-track/rec-tips"><cite>Tips for Getting to Recommendation Faster</cite></a>. URL: <a href="https://www.w3.org/guide/standards-track/rec-tips">https://www.w3.org/guide/standards-track/rec-tips</a>
+   <dt id="biblio-republishing">[REPUBLISHING]
+   <dd><a href="https://www.w3.org/guide/standards-track/republishing"><cite>In-place modification of W3C Technical Reports</cite></a>. URL: <a href="https://www.w3.org/guide/standards-track/republishing">https://www.w3.org/guide/standards-track/republishing</a>
+   <dt id="biblio-submission-list">[SUBMISSION-LIST]
+   <dd><a href="https://www.w3.org/submissions/"><cite>The list of acknowledged Member Submissions</cite></a>. URL: <a href="https://www.w3.org/submissions/">https://www.w3.org/submissions/</a>
+   <dt id="biblio-tag-hp">[TAG-HP]
+   <dd><a href="https://www.w3.org/2001/tag/"><cite>The TAG home page</cite></a>. URL: <a href="https://www.w3.org/2001/tag/">https://www.w3.org/2001/tag/</a>
+   <dt id="biblio-team-contact">[TEAM-CONTACT]
+   <dd><a href="https://www.w3.org/guide/teamcontact/role"><cite>Role of the Team Contact</cite></a>. URL: <a href="https://www.w3.org/guide/teamcontact/role">https://www.w3.org/guide/teamcontact/role</a>
+   <dt id="biblio-tr">[TR]
+   <dd><a href="https://www.w3.org/TR/"><cite>The W3C technical reports index</cite></a>. URL: <a href="https://www.w3.org/TR/">https://www.w3.org/TR/</a>
+   <dt id="biblio-transition">[TRANSITION]
+   <dd><a href="https://www.w3.org/guide/transitions/"><cite>Organize a Technical Report Transition</cite></a>. URL: <a href="https://www.w3.org/guide/transitions/">https://www.w3.org/guide/transitions/</a>
+   <dt id="biblio-translation">[TRANSLATION]
+   <dd><a href="https://www.w3.org/Consortium/Translation/"><cite>Translations of W3C technical reports</cite></a>. URL: <a href="https://www.w3.org/Consortium/Translation/">https://www.w3.org/Consortium/Translation/</a>
+   <dt id="biblio-w3c-ipr">[W3C-IPR]
+   <dd><a href="https://www.w3.org/policies/"><cite>W3C IPR Policies</cite></a>. URL: <a href="https://www.w3.org/policies/">https://www.w3.org/policies/</a>
+  </dl>
+<script>/* Boilerplate: script-dom-helper */
+"use strict";
+function query(sel) { return document.querySelector(sel); }
+
+function queryAll(sel) { return [...document.querySelectorAll(sel)]; }
+
+function iter(obj) {
+	if(!obj) return [];
+	var it = obj[Symbol.iterator];
+	if(it) return it;
+	return Object.entries(obj);
+}
+
+function mk(tagname, attrs, ...children) {
+	const el = document.createElement(tagname);
+	for(const [k,v] of iter(attrs)) {
+		if(k.slice(0,3) == "_on") {
+			const eventName = k.slice(3);
+			el.addEventListener(eventName, v);
+		} else if(k[0] == "_") {
+			// property, not attribute
+			el[k.slice(1)] = v;
+		} else {
+			if(v === false || v == null) {
+        continue;
+      } else if(v === true) {
+        el.setAttribute(k, "");
+        continue;
+      } else {
+  			el.setAttribute(k, v);
+      }
+		}
+	}
+	append(el, children);
+	return el;
+}
+
+/* Create shortcuts for every known HTML element */
+[
+  "a",
+  "abbr",
+  "acronym",
+  "address",
+  "applet",
+  "area",
+  "article",
+  "aside",
+  "audio",
+  "b",
+  "base",
+  "basefont",
+  "bdo",
+  "big",
+  "blockquote",
+  "body",
+  "br",
+  "button",
+  "canvas",
+  "caption",
+  "center",
+  "cite",
+  "code",
+  "col",
+  "colgroup",
+  "datalist",
+  "dd",
+  "del",
+  "details",
+  "dfn",
+  "dialog",
+  "div",
+  "dl",
+  "dt",
+  "em",
+  "embed",
+  "fieldset",
+  "figcaption",
+  "figure",
+  "font",
+  "footer",
+  "form",
+  "frame",
+  "frameset",
+  "head",
+  "header",
+  "h1",
+  "h2",
+  "h3",
+  "h4",
+  "h5",
+  "h6",
+  "hr",
+  "html",
+  "i",
+  "iframe",
+  "img",
+  "input",
+  "ins",
+  "kbd",
+  "label",
+  "legend",
+  "li",
+  "link",
+  "main",
+  "map",
+  "mark",
+  "meta",
+  "meter",
+  "nav",
+  "nobr",
+  "noscript",
+  "object",
+  "ol",
+  "optgroup",
+  "option",
+  "output",
+  "p",
+  "param",
+  "pre",
+  "progress",
+  "q",
+  "s",
+  "samp",
+  "script",
+  "section",
+  "select",
+  "small",
+  "source",
+  "span",
+  "strike",
+  "strong",
+  "style",
+  "sub",
+  "summary",
+  "sup",
+  "table",
+  "tbody",
+  "td",
+  "template",
+  "textarea",
+  "tfoot",
+  "th",
+  "thead",
+  "time",
+  "title",
+  "tr",
+  "u",
+  "ul",
+  "var",
+  "video",
+  "wbr",
+  "xmp",
+].forEach(tagname=>{
+	mk[tagname] = (...args) => mk(tagname, ...args);
+});
+
+function* nodesFromChildList(children) {
+	for(const child of children.flat(Infinity)) {
+		if(child instanceof Node) {
+			yield child;
+		} else {
+			yield new Text(child);
+		}
+	}
+}
+function append(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		if(el instanceof Node) el.appendChild(child);
+		else el.push(child);
+	}
+	return el;
+}
+
+function insertAfter(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		el.parentNode.insertBefore(child, el.nextSibling);
+	}
+	return el;
+}
+
+function clearContents(el) {
+	el.innerHTML = "";
+	return el;
+}
+
+function parseHTML(markup) {
+	if(markup.toLowerCase().trim().indexOf('<!doctype') === 0) {
+		const doc = document.implementation.createHTMLDocument("");
+		doc.documentElement.innerHTML = markup;
+		return doc;
+	} else {
+		const el = mk.template({});
+		el.innerHTML = markup;
+		return el.content;
+	}
+}</script>
+<script>/* Boilerplate: script-dfn-panel */
+"use strict";
+{
+let dfnPanelData = {
+"33fd2aef": {"dfnID":"33fd2aef","dfnText":"Exclusion Opportunity","external":true,"refSections":[{"refs":[{"id":"ref-for-exclusion-opportunity"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
+"3a585f2f": {"dfnID":"3a585f2f","dfnText":"W3C Note","external":true,"refSections":[{"refs":[{"id":"ref-for-WGNote\u2460"}],"title":"6.1. \nTypes of Technical Reports"}],"url":"https://www.w3.org/policies/process/#WGNote"},
+"74c78a1e": {"dfnID":"74c78a1e","dfnText":"Patent Advisory Group","external":true,"refSections":[{"refs":[{"id":"ref-for-patent-advisory-group"}],"title":"4.7. \nChartered Group Closure"}],"url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
+"EventsW": {"dfnID":"EventsW","dfnText":"Workshop","external":false,"refSections":[{"refs":[{"id":"ref-for-EventsW"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-EventsW\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-EventsW\u2461"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-EventsW\u2462"}],"title":"7.1. \nPublic Communication"}],"url":"#EventsW"},
+"FormalObjection": {"dfnID":"FormalObjection","dfnText":"Formal Objection","external":false,"refSections":[{"refs":[{"id":"ref-for-FormalObjection"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-FormalObjection\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-FormalObjection\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-FormalObjection\u2462"},{"id":"ref-for-FormalObjection\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-FormalObjection\u2464"}],"title":"5. \nDecisions"},{"refs":[{"id":"ref-for-FormalObjection\u2465"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-FormalObjection\u2466"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-FormalObjection\u2467"},{"id":"ref-for-FormalObjection\u2468"},{"id":"ref-for-FormalObjection\u2460\u24ea"},{"id":"ref-for-FormalObjection\u2460\u2460"},{"id":"ref-for-FormalObjection\u2460\u2461"},{"id":"ref-for-FormalObjection\u2460\u2462"},{"id":"ref-for-FormalObjection\u2460\u2463"},{"id":"ref-for-FormalObjection\u2460\u2464"},{"id":"ref-for-FormalObjection\u2460\u2465"},{"id":"ref-for-FormalObjection\u2460\u2466"},{"id":"ref-for-FormalObjection\u2460\u2467"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-FormalObjection\u2460\u2468"},{"id":"ref-for-FormalObjection\u2461\u24ea"},{"id":"ref-for-FormalObjection\u2461\u2460"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2461"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2462"},{"id":"ref-for-FormalObjection\u2461\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2464"},{"id":"ref-for-FormalObjection\u2461\u2465"},{"id":"ref-for-FormalObjection\u2461\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2468"},{"id":"ref-for-FormalObjection\u2462\u24ea"},{"id":"ref-for-FormalObjection\u2462\u2460"},{"id":"ref-for-FormalObjection\u2462\u2461"},{"id":"ref-for-FormalObjection\u2462\u2462"},{"id":"ref-for-FormalObjection\u2462\u2463"},{"id":"ref-for-FormalObjection\u2462\u2464"},{"id":"ref-for-FormalObjection\u2462\u2465"},{"id":"ref-for-FormalObjection\u2462\u2466"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2468"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u24ea"},{"id":"ref-for-FormalObjection\u2463\u2460"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2461"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2462"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2463"}],"title":"9. \nMember Submissions"}],"url":"#FormalObjection"},
+"GeneralChairs": {"dfnID":"GeneralChairs","dfnText":"Chair","external":false,"refSections":[{"refs":[{"id":"ref-for-GeneralChairs"}],"title":"3.1.1.2. \nConflict of Interest Policy"},{"refs":[{"id":"ref-for-GeneralChairs\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-GeneralChairs\u2461"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-GeneralChairs\u2462"},{"id":"ref-for-GeneralChairs\u2463"},{"id":"ref-for-GeneralChairs\u2464"},{"id":"ref-for-GeneralChairs\u2465"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-GeneralChairs\u2466"},{"id":"ref-for-GeneralChairs\u2467"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GeneralChairs\u2468"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u24ea"},{"id":"ref-for-GeneralChairs\u2460\u2460"},{"id":"ref-for-GeneralChairs\u2460\u2461"},{"id":"ref-for-GeneralChairs\u2460\u2462"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2464"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2465"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2466"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2467"},{"id":"ref-for-GeneralChairs\u2460\u2468"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u24ea"},{"id":"ref-for-GeneralChairs\u2461\u2460"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2461"},{"id":"ref-for-GeneralChairs\u2461\u2462"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2463"},{"id":"ref-for-GeneralChairs\u2461\u2464"}],"title":"5.2.3. \nDeciding by Vote"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2465"},{"id":"ref-for-GeneralChairs\u2461\u2466"}],"title":"5.4. \nReopening a Decision When Presented With New Information"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2467"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2468"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-GeneralChairs\u2462\u24ea"},{"id":"ref-for-GeneralChairs\u2462\u2460"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-GeneralChairs\u2462\u2461"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#GeneralChairs"},
+"GroupsIG": {"dfnID":"GroupsIG","dfnText":"Interest Groups","external":false,"refSections":[{"refs":[{"id":"ref-for-GroupsIG"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-GroupsIG"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-GroupsIG\u2460"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GroupsIG\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-GroupsIG\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-GroupsIG\u2463"},{"id":"ref-for-GroupsIG\u2464"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GroupsIG\u2465"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-GroupsIG\u2466"},{"id":"ref-for-GroupsIG\u2467"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GroupsIG\u2468"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-GroupsIG\u2460\u24ea"},{"id":"ref-for-GroupsIG\u2460\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsIG\u2460\u2461"}],"title":"6.4.1. \nGroup Notes"}],"url":"#GroupsIG"},
+"GroupsWG": {"dfnID":"GroupsWG","dfnText":"Working Groups","external":false,"refSections":[{"refs":[{"id":"ref-for-GroupsWG"},{"id":"ref-for-GroupsWG\u2460"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-GroupsWG\u2461"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-GroupsWG\u2462"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-GroupsWG"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-GroupsWG\u2463"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GroupsWG\u2464"},{"id":"ref-for-GroupsWG\u2465"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-GroupsWG\u2466"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-GroupsWG\u2467"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-GroupsWG\u2468"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u24ea"},{"id":"ref-for-GroupsWG\u2460\u2460"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2461"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2462"},{"id":"ref-for-GroupsWG\u2460\u2463"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2464"}],"title":"6. \nW3C Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2465"},{"id":"ref-for-GroupsWG\u2460\u2466"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2467"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2468"},{"id":"ref-for-GroupsWG\u2461\u24ea"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2460"},{"id":"ref-for-GroupsWG\u2461\u2461"},{"id":"ref-for-GroupsWG\u2461\u2462"},{"id":"ref-for-GroupsWG\u2461\u2463"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2464"},{"id":"ref-for-GroupsWG\u2461\u2465"},{"id":"ref-for-GroupsWG\u2461\u2466"},{"id":"ref-for-GroupsWG\u2461\u2467"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2468"},{"id":"ref-for-GroupsWG\u2462\u24ea"},{"id":"ref-for-GroupsWG\u2462\u2460"},{"id":"ref-for-GroupsWG\u2462\u2461"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2462\u2462"},{"id":"ref-for-GroupsWG\u2462\u2463"},{"id":"ref-for-GroupsWG\u2462\u2464"},{"id":"ref-for-GroupsWG\u2462\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2462\u2466"},{"id":"ref-for-GroupsWG\u2462\u2467"},{"id":"ref-for-GroupsWG\u2462\u2468"},{"id":"ref-for-GroupsWG\u2463\u24ea"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2460"},{"id":"ref-for-GroupsWG\u2463\u2461"},{"id":"ref-for-GroupsWG\u2463\u2462"},{"id":"ref-for-GroupsWG\u2463\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2464"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2465"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2466"},{"id":"ref-for-GroupsWG\u2463\u2467"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2468"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u24ea"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2460"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2461"},{"id":"ref-for-GroupsWG\u2464\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2463"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2464"},{"id":"ref-for-GroupsWG\u2464\u2465"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2466"},{"id":"ref-for-GroupsWG\u2464\u2467"},{"id":"ref-for-GroupsWG\u2464\u2468"},{"id":"ref-for-GroupsWG\u2465\u24ea"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2460"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2461"}],"title":"6.3.12. \nRetiring Recommendation Track Documents"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2462"},{"id":"ref-for-GroupsWG\u2465\u2463"},{"id":"ref-for-GroupsWG\u2465\u2464"},{"id":"ref-for-GroupsWG\u2465\u2465"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2466"},{"id":"ref-for-GroupsWG\u2465\u2467"},{"id":"ref-for-GroupsWG\u2465\u2468"},{"id":"ref-for-GroupsWG\u2466\u24ea"},{"id":"ref-for-GroupsWG\u2466\u2460"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2461"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2462"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2463"},{"id":"ref-for-GroupsWG\u2466\u2464"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2465"}],"title":"10. \nProcess Evolution"}],"url":"#GroupsWG"},
+"Member-only": {"dfnID":"Member-only","dfnText":"Member-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Member-only"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-Member-only"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-Member-only"},{"id":"ref-for-Member-only"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-Member-only"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-Member-only\u2460"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-Member-only\u2461"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Member-only\u2462"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-Member-only\u2463"},{"id":"ref-for-Member-only\u2464"},{"id":"ref-for-Member-only\u2465"},{"id":"ref-for-Member-only\u2466"},{"id":"ref-for-Member-only\u2467"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Member-only\u2468"},{"id":"ref-for-Member-only\u2460\u24ea"},{"id":"ref-for-Member-only\u2460\u2460"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Member-only"},
+"MemberSubmission": {"dfnID":"MemberSubmission","dfnText":"Member Submission","external":false,"refSections":[{"refs":[{"id":"ref-for-MemberSubmission"},{"id":"ref-for-MemberSubmission\u2460"},{"id":"ref-for-MemberSubmission\u2461"},{"id":"ref-for-MemberSubmission\u2462"}],"title":"9. \nMember Submissions"}],"url":"#MemberSubmission"},
+"RecsCR": {"dfnID":"RecsCR","dfnText":"Candidate Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsCR"},{"id":"ref-for-RecsCR\u2460"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-RecsCR\u2461"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-RecsCR\u2462"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsCR\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-RecsCR\u2464"},{"id":"ref-for-RecsCR\u2465"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2466"},{"id":"ref-for-RecsCR\u2467"},{"id":"ref-for-RecsCR\u2468"},{"id":"ref-for-RecsCR\u2460\u24ea"},{"id":"ref-for-RecsCR\u2460\u2460"},{"id":"ref-for-RecsCR\u2460\u2461"},{"id":"ref-for-RecsCR\u2460\u2462"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2463"},{"id":"ref-for-RecsCR\u2460\u2464"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2467"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2468"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-RecsCR\u2461\u24ea"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-RecsCR\u2461\u2460"}],"title":"6.3.12.2. \nRescinding a Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2461\u2461"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsCR"},
+"RecsObs": {"dfnID":"RecsObs","dfnText":"Obsolete Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsObs"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsObs\u2460"},{"id":"ref-for-RecsObs\u2461"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsObs\u2462"},{"id":"ref-for-RecsObs\u2463"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RecsObs\u2464"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsObs"},
+"RecsPR": {"dfnID":"RecsPR","dfnText":"Proposed Recommendation","external":false,"refSections":[],"url":"#RecsPR"},
+"RecsSup": {"dfnID":"RecsSup","dfnText":"Superseded Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsSup"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsSup\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsSup"},
+"RecsW3C": {"dfnID":"RecsW3C","dfnText":"W3C Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsW3C"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-RecsW3C"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-RecsW3C\u2460"},{"id":"ref-for-RecsW3C\u2461"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-RecsW3C\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-RecsW3C\u2463"},{"id":"ref-for-RecsW3C\u2464"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-RecsW3C\u2465"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsW3C\u2466"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-RecsW3C\u2467"},{"id":"ref-for-RecsW3C"},{"id":"ref-for-RecsW3C\u2468"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2460\u24ea"},{"id":"ref-for-RecsW3C\u2460\u2460"},{"id":"ref-for-RecsW3C\u2460\u2461"},{"id":"ref-for-RecsW3C\u2460\u2462"},{"id":"ref-for-RecsW3C\u2460\u2463"},{"id":"ref-for-RecsW3C\u2460\u2464"},{"id":"ref-for-RecsW3C\u2460\u2465"},{"id":"ref-for-RecsW3C\u2460\u2466"},{"id":"ref-for-RecsW3C\u2460\u2467"},{"id":"ref-for-RecsW3C\u2460\u2468"},{"id":"ref-for-RecsW3C\u2461\u24ea"},{"id":"ref-for-RecsW3C\u2461\u2460"},{"id":"ref-for-RecsW3C\u2461\u2461"},{"id":"ref-for-RecsW3C\u2461\u2462"},{"id":"ref-for-RecsW3C\u2461\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2464"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2467"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2468"},{"id":"ref-for-RecsW3C\u2462\u24ea"},{"id":"ref-for-RecsW3C\u2462\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2461"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2462"},{"id":"ref-for-RecsW3C\u2462\u2463"},{"id":"ref-for-RecsW3C\u2462\u2464"},{"id":"ref-for-RecsW3C\u2462\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2466"},{"id":"ref-for-RecsW3C\u2462\u2467"}],"title":"6.3.9.4. \nNext Steps from W3C Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2468"},{"id":"ref-for-RecsW3C\u2463\u24ea"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-RecsW3C\u2463\u2460"},{"id":"ref-for-RecsW3C\u2463\u2461"},{"id":"ref-for-RecsW3C\u2463\u2462"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-RecsW3C\u2463\u2463"},{"id":"ref-for-RecsW3C\u2463\u2464"},{"id":"ref-for-RecsW3C\u2463\u2465"},{"id":"ref-for-RecsW3C\u2463\u2466"},{"id":"ref-for-RecsW3C\u2463\u2467"},{"id":"ref-for-RecsW3C\u2463\u2468"},{"id":"ref-for-RecsW3C\u2464\u24ea"},{"id":"ref-for-RecsW3C\u2464\u2460"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2461"},{"id":"ref-for-RecsW3C\u2464\u2462"},{"id":"ref-for-RecsW3C\u2464\u2463"},{"id":"ref-for-RecsW3C\u2464\u2464"},{"id":"ref-for-RecsW3C\u2464\u2465"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2466"}],"title":"6.3.12.2. \nRescinding a Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2467"},{"id":"ref-for-RecsW3C\u2464\u2468"},{"id":"ref-for-RecsW3C\u2465\u24ea"},{"id":"ref-for-RecsW3C\u2465\u2460"},{"id":"ref-for-RecsW3C\u2465\u2461"},{"id":"ref-for-RecsW3C\u2465\u2462"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2465\u2463"},{"id":"ref-for-RecsW3C\u2465\u2464"},{"id":"ref-for-RecsW3C\u2465\u2465"},{"id":"ref-for-RecsW3C\u2465\u2466"},{"id":"ref-for-RecsW3C\u2465\u2467"},{"id":"ref-for-RecsW3C\u2465\u2468"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u24ea"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2460"},{"id":"ref-for-RecsW3C\u2466\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2462"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2463"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#RecsW3C"},
+"RecsWD": {"dfnID":"RecsWD","dfnText":"Working Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsWD"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-RecsWD\u2460"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsWD\u2461"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsWD\u2462"},{"id":"ref-for-RecsWD\u2463"},{"id":"ref-for-RecsWD\u2464"},{"id":"ref-for-RecsWD\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsWD\u2466"},{"id":"ref-for-RecsWD\u2467"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-RecsWD\u2468"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-RecsWD\u2460\u24ea"},{"id":"ref-for-RecsWD\u2460\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-RecsWD\u2460\u2461"},{"id":"ref-for-RecsWD\u2460\u2462"},{"id":"ref-for-RecsWD\u2460\u2463"}],"title":"6.6. \nSwitching Tracks"}],"url":"#RecsWD"},
+"RescindedRec": {"dfnID":"RescindedRec","dfnText":"Rescinded Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RescindedRec"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RescindedRec\u2460"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RescindedRec\u2461"},{"id":"ref-for-RescindedRec\u2462"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RescindedRec\u2463"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RescindedRec"},
+"Team-only": {"dfnID":"Team-only","dfnText":"Team-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Team-only"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-Team-only"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Team-only\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Team-only\u2461"},{"id":"ref-for-Team-only\u2462"},{"id":"ref-for-Team-only\u2463"},{"id":"ref-for-Team-only\u2464"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Team-only"},
+"TeamContact": {"dfnID":"TeamContact","dfnText":"Staff Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-TeamContact"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-TeamContact\u2460"},{"id":"ref-for-TeamContact\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2462"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2463"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2464"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2465"},{"id":"ref-for-TeamContact\u2466"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-TeamContact\u2467"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-TeamContact\u2468"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-TeamContact\u2460\u24ea"}],"title":"5.5. \nRegistering Formal Objections"}],"url":"#TeamContact"},
+"TeamSubmission": {"dfnID":"TeamSubmission","dfnText":"Team Submissions","external":false,"refSections":[],"url":"#TeamSubmission"},
+"WGNote": {"dfnID":"WGNote","dfnText":"Group Note","external":false,"refSections":[{"refs":[{"id":"ref-for-WGNote"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-WGNote"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-WGNote\u2461"},{"id":"ref-for-WGNote\u2462"},{"id":"ref-for-WGNote\u2463"},{"id":"ref-for-WGNote\u2464"},{"id":"ref-for-WGNote\u2465"},{"id":"ref-for-WGNote\u2466"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-WGNote\u2467"},{"id":"ref-for-WGNote\u2468"},{"id":"ref-for-WGNote\u2460\u24ea"},{"id":"ref-for-WGNote\u2460\u2460"},{"id":"ref-for-WGNote\u2460\u2461"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-WGNote\u2460\u2462"},{"id":"ref-for-WGNote\u2460\u2463"},{"id":"ref-for-WGNote\u2460\u2464"},{"id":"ref-for-WGNote\u2460\u2465"},{"id":"ref-for-WGNote\u2460\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#WGNote"},
+"acknowledged": {"dfnID":"acknowledged","dfnText":"acknowledged","external":false,"refSections":[{"refs":[{"id":"ref-for-acknowledged"},{"id":"ref-for-acknowledged\u2460"}],"title":"9. \nMember Submissions"}],"url":"#acknowledged"},
+"adequate-implementation": {"dfnID":"adequate-implementation","dfnText":"adequate implementation experience","external":false,"refSections":[{"refs":[{"id":"ref-for-adequate-implementation"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-adequate-implementation\u2460"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-adequate-implementation\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-adequate-implementation\u2462"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#adequate-implementation"},
+"adopted-draft": {"dfnID":"adopted-draft","dfnText":"Adopted Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-adopted-draft"}],"title":"4.3. \nContent of a Charter"}],"url":"#adopted-draft"},
+"advisory-board": {"dfnID":"advisory-board","dfnText":"Advisory Board","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-board"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-advisory-board\u2460"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-advisory-board\u2461"},{"id":"ref-for-advisory-board\u2462"},{"id":"ref-for-advisory-board\u2463"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2464"},{"id":"ref-for-advisory-board\u2465"},{"id":"ref-for-advisory-board\u2466"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2467"}],"title":"3.3.1.3. \nCommunications of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2468"},{"id":"ref-for-advisory-board\u2460\u24ea"},{"id":"ref-for-advisory-board\u2460\u2460"}],"title":"3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2461"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2462"},{"id":"ref-for-advisory-board\u2460\u2463"},{"id":"ref-for-advisory-board\u2460\u2464"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2465"},{"id":"ref-for-advisory-board\u2460\u2466"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2467"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2468"}],"title":"3.3.3.5. \nVerifiable Random Selection Procedure"},{"refs":[{"id":"ref-for-advisory-board\u2461\u24ea"},{"id":"ref-for-advisory-board\u2461\u2460"},{"id":"ref-for-advisory-board\u2461\u2461"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2462"},{"id":"ref-for-advisory-board\u2461\u2463"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2464"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2465"},{"id":"ref-for-advisory-board\u2461\u2466"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2467"},{"id":"ref-for-advisory-board\u2461\u2468"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-advisory-board\u2462\u24ea"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2460"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2461"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2462"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2463"},{"id":"ref-for-advisory-board\u2462\u2464"},{"id":"ref-for-advisory-board\u2462\u2465"},{"id":"ref-for-advisory-board\u2462\u2466"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-board"},
+"advisory-committee": {"dfnID":"advisory-committee","dfnText":"Advisory Committee","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-advisory-committee\u2460"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee\u2461"},{"id":"ref-for-advisory-committee\u2462"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-advisory-committee\u2463"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-advisory-committee\u2464"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-advisory-committee\u2465"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-committee\u2466"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-advisory-committee\u2467"},{"id":"ref-for-advisory-committee\u2468"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u24ea"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2460"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2461"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2462"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2464"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2465"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2466"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2467"},{"id":"ref-for-advisory-committee\u2460\u2468"},{"id":"ref-for-advisory-committee\u2461\u24ea"},{"id":"ref-for-advisory-committee\u2461\u2460"},{"id":"ref-for-advisory-committee\u2461\u2461"},{"id":"ref-for-advisory-committee\u2461\u2462"},{"id":"ref-for-advisory-committee\u2461\u2463"},{"id":"ref-for-advisory-committee\u2461\u2464"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-advisory-committee\u2461\u2465"},{"id":"ref-for-advisory-committee\u2461\u2466"}],"title":"5.8. \nAdvisory Committee Votes"},{"refs":[{"id":"ref-for-advisory-committee\u2461\u2467"},{"id":"ref-for-advisory-committee\u2461\u2468"},{"id":"ref-for-advisory-committee\u2462\u24ea"},{"id":"ref-for-advisory-committee\u2462\u2460"},{"id":"ref-for-advisory-committee\u2462\u2461"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2462"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2463"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2464"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2466"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2467"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2468"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee\u2463\u24ea"},{"id":"ref-for-advisory-committee\u2463\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee\u2463\u2461"},{"id":"ref-for-advisory-committee\u2463\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-committee"},
+"advisory-committee-appeal": {"dfnID":"advisory-committee-appeal","dfnText":"Advisory Committee Appeal","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-appeal"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2461"}],"title":"5.8. \nAdvisory Committee Votes"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2462"},{"id":"ref-for-advisory-committee-appeal\u2463"},{"id":"ref-for-advisory-committee-appeal\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2468"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u24ea"},{"id":"ref-for-advisory-committee-appeal\u2460\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u2461"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-committee-appeal"},
+"advisory-committee-representative": {"dfnID":"advisory-committee-representative","dfnText":"representative","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-representative"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460"}],"title":"3.1.1.3. \nIndividuals Representing a Member Organization"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461"},{"id":"ref-for-advisory-committee-representative\u2462"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2463"},{"id":"ref-for-advisory-committee-representative\u2464"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2465"},{"id":"ref-for-advisory-committee-representative\u2466"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2467"},{"id":"ref-for-advisory-committee-representative\u2468"},{"id":"ref-for-advisory-committee-representative\u2460\u24ea"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2460"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2461"}],"title":"3.4.3.2. \nMember Representative in an Interest Group"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2462"},{"id":"ref-for-advisory-committee-representative\u2460\u2463"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2464"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2465"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2466"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2468"},{"id":"ref-for-advisory-committee-representative\u2461\u24ea"},{"id":"ref-for-advisory-committee-representative\u2461\u2460"},{"id":"ref-for-advisory-committee-representative\u2461\u2461"},{"id":"ref-for-advisory-committee-representative\u2461\u2462"},{"id":"ref-for-advisory-committee-representative\u2461\u2463"},{"id":"ref-for-advisory-committee-representative\u2461\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2468"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u24ea"},{"id":"ref-for-advisory-committee-representative\u2462\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2461"}],"title":"7.3. \nChanging Confidentiality Level"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2462"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2463"},{"id":"ref-for-advisory-committee-representative\u2462\u2464"},{"id":"ref-for-advisory-committee-representative\u2462\u2465"}],"title":"9. \nMember Submissions"}],"url":"#advisory-committee-representative"},
+"advisory-committee-review": {"dfnID":"advisory-committee-review","dfnText":"Advisory Committee review","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-review"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460"},{"id":"ref-for-advisory-committee-review\u2461"},{"id":"ref-for-advisory-committee-review\u2462"},{"id":"ref-for-advisory-committee-review\u2463"},{"id":"ref-for-advisory-committee-review\u2464"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-review\u2465"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-advisory-committee-review\u2466"},{"id":"ref-for-advisory-committee-review\u2467"},{"id":"ref-for-advisory-committee-review\u2468"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u24ea"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2460"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2461"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2462"},{"id":"ref-for-advisory-committee-review\u2460\u2463"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2464"},{"id":"ref-for-advisory-committee-review\u2460\u2465"},{"id":"ref-for-advisory-committee-review\u2460\u2466"},{"id":"ref-for-advisory-committee-review\u2460\u2467"},{"id":"ref-for-advisory-committee-review\u2460\u2468"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u24ea"},{"id":"ref-for-advisory-committee-review\u2461\u2460"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2462"},{"id":"ref-for-advisory-committee-review\u2461\u2463"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2465"},{"id":"ref-for-advisory-committee-review\u2461\u2466"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2467"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2468"},{"id":"ref-for-advisory-committee-review\u2462\u24ea"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2461"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2462"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2463"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2464"}],"title":"10. \nProcess Evolution"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2465"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#advisory-committee-review"},
+"affirm": {"dfnID":"affirm","dfnText":"affirm","external":false,"refSections":[{"refs":[{"id":"ref-for-affirm"},{"id":"ref-for-affirm\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-affirm\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-affirm\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"#affirm"},
+"allow-new-features": {"dfnID":"allow-new-features","dfnText":"allow new features","external":false,"refSections":[{"refs":[{"id":"ref-for-allow-new-features"},{"id":"ref-for-allow-new-features\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-allow-new-features\u2461"},{"id":"ref-for-allow-new-features\u2462"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-allow-new-features\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#allow-new-features"},
+"alternate-ac-representative": {"dfnID":"alternate-ac-representative","dfnText":"alternate","external":false,"refSections":[],"url":"#alternate-ac-representative"},
+"appeal-vote": {"dfnID":"appeal-vote","dfnText":"appeal vote","external":false,"refSections":[{"refs":[{"id":"ref-for-appeal-vote"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-appeal-vote\u2460"}],"title":"5.8. \nAdvisory Committee Votes"}],"url":"#appeal-vote"},
+"at-risk": {"dfnID":"at-risk","dfnText":"at risk","external":false,"refSections":[{"refs":[{"id":"ref-for-at-risk"},{"id":"ref-for-at-risk\u2460"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-at-risk\u2461"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-at-risk\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-at-risk\u2463"}],"title":"6.3.9.3. \nResolution of Review"}],"url":"#at-risk"},
+"bod": {"dfnID":"bod","dfnText":"W3C Board of Directors","external":false,"refSections":[{"refs":[{"id":"ref-for-bod"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-bod\u2460"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-bod\u2461"},{"id":"ref-for-bod\u2462"},{"id":"ref-for-bod\u2463"},{"id":"ref-for-bod\u2464"},{"id":"ref-for-bod\u2465"}],"title":"3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"},{"refs":[{"id":"ref-for-bod\u2466"},{"id":"ref-for-bod\u2467"}],"title":"8. \nLiaisons"}],"url":"#bod"},
+"candidate-addition": {"dfnID":"candidate-addition","dfnText":"candidate addition","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-addition"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-addition\u2460"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"}],"url":"#candidate-addition"},
+"candidate-amendment": {"dfnID":"candidate-amendment","dfnText":"candidate amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-amendment"},{"id":"ref-for-candidate-amendment\u2460"},{"id":"ref-for-candidate-amendment\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-amendment\u2462"},{"id":"ref-for-candidate-amendment\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-candidate-amendment\u2464"},{"id":"ref-for-candidate-amendment\u2465"},{"id":"ref-for-candidate-amendment\u2466"},{"id":"ref-for-candidate-amendment\u2467"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-candidate-amendment\u2468"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#candidate-amendment"},
+"candidate-correction": {"dfnID":"candidate-correction","dfnText":"candidate correction","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-correction"},{"id":"ref-for-candidate-correction\u2460"},{"id":"ref-for-candidate-correction\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-correction\u2462"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-candidate-correction\u2463"},{"id":"ref-for-candidate-correction\u2464"},{"id":"ref-for-candidate-correction\u2465"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"}],"url":"#candidate-correction"},
+"candidate-recommendation-draft": {"dfnID":"candidate-recommendation-draft","dfnText":"Candidate Recommendation Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-draft"},{"id":"ref-for-candidate-recommendation-draft\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2461"},{"id":"ref-for-candidate-recommendation-draft\u2462"},{"id":"ref-for-candidate-recommendation-draft\u2463"},{"id":"ref-for-candidate-recommendation-draft\u2464"},{"id":"ref-for-candidate-recommendation-draft\u2465"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2466"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2467"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#candidate-recommendation-draft"},
+"candidate-recommendation-review-period": {"dfnID":"candidate-recommendation-review-period","dfnText":"Candidate Recommendation review period","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-review-period"},{"id":"ref-for-candidate-recommendation-review-period\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"}],"url":"#candidate-recommendation-review-period"},
+"candidate-recommendation-snapshot": {"dfnID":"candidate-recommendation-snapshot","dfnText":"Candidate Recommendation Snapshot","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-snapshot"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460"},{"id":"ref-for-candidate-recommendation-snapshot\u2461"},{"id":"ref-for-candidate-recommendation-snapshot\u2462"},{"id":"ref-for-candidate-recommendation-snapshot\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2464"},{"id":"ref-for-candidate-recommendation-snapshot\u2465"},{"id":"ref-for-candidate-recommendation-snapshot\u2466"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2467"},{"id":"ref-for-candidate-recommendation-snapshot\u2468"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u24ea"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2460"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2461"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2462"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2463"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2464"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2465"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2466"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2467"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2468"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#candidate-recommendation-snapshot"},
+"candidate-registry": {"dfnID":"candidate-registry","dfnText":"Candidate Registry","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-registry"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#candidate-registry"},
+"candidate-registry-draft": {"dfnID":"candidate-registry-draft","dfnText":"Candidate Registry Draft","external":false,"refSections":[],"url":"#candidate-registry-draft"},
+"candidate-registry-snapshot": {"dfnID":"candidate-registry-snapshot","dfnText":"Candidate Registry Snapshot","external":false,"refSections":[],"url":"#candidate-registry-snapshot"},
+"ceo": {"dfnID":"ceo","dfnText":"CEO","external":false,"refSections":[{"refs":[{"id":"ref-for-ceo"}],"title":"2.1.2.1. \nMembership Associations"},{"refs":[{"id":"ref-for-ceo\u2460"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-ceo\u2461"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-ceo\u2462"}],"title":"3.1.1.3. \nIndividuals Representing a Member Organization"},{"refs":[{"id":"ref-for-ceo\u2463"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-ceo\u2464"},{"id":"ref-for-ceo\u2465"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-ceo\u2466"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-ceo\u2467"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-ceo\u2468"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#ceo"},
+"chair-decisions": {"dfnID":"chair-decisions","dfnText":"chair decisions","external":false,"refSections":[],"url":"#chair-decisions"},
+"charter": {"dfnID":"charter","dfnText":"charter","external":false,"refSections":[{"refs":[{"id":"ref-for-charter"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-charter\u2460"},{"id":"ref-for-charter\u2461"},{"id":"ref-for-charter\u2462"},{"id":"ref-for-charter\u2463"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-charter\u2464"},{"id":"ref-for-charter\u2465"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter\u2466"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-charter\u2467"},{"id":"ref-for-charter\u2468"},{"id":"ref-for-charter\u2460\u24ea"},{"id":"ref-for-charter\u2460\u2460"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-charter\u2460\u2461"},{"id":"ref-for-charter\u2460\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-charter\u2460\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-charter\u2460\u2464"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-charter\u2460\u2465"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-charter\u2460\u2466"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-charter\u2460\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"}],"url":"#charter"},
+"charter-draft": {"dfnID":"charter-draft","dfnText":"charter draft","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-draft"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-draft\u2460"},{"id":"ref-for-charter-draft\u2461"},{"id":"ref-for-charter-draft\u2462"},{"id":"ref-for-charter-draft\u2463"}],"title":"4.2. \nCharter Refinement"}],"url":"#charter-draft"},
+"charter-refinement": {"dfnID":"charter-refinement","dfnText":"charter refinement","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-refinement"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-charter-refinement\u2460"},{"id":"ref-for-charter-refinement\u2461"},{"id":"ref-for-charter-refinement\u2462"},{"id":"ref-for-charter-refinement\u2463"},{"id":"ref-for-charter-refinement\u2464"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-refinement\u2465"},{"id":"ref-for-charter-refinement\u2466"},{"id":"ref-for-charter-refinement\u2467"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-charter-refinement\u2468"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-charter-refinement\u2460\u24ea"},{"id":"ref-for-charter-refinement\u2460\u2460"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-charter-refinement\u2460\u2461"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#charter-refinement"},
+"charter-review-notice": {"dfnID":"charter-review-notice","dfnText":"charter review notice","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-review-notice"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-review-notice\u2460"}],"title":"4.2. \nCharter Refinement"}],"url":"#charter-review-notice"},
+"chartered-group": {"dfnID":"chartered-group","dfnText":"chartered groups","external":false,"refSections":[{"refs":[{"id":"ref-for-chartered-group"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-chartered-group\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-chartered-group\u2461"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-chartered-group\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-chartered-group\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-chartered-group\u2464"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-chartered-group\u2465"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#chartered-group"},
+"chartering-facilitator": {"dfnID":"chartering-facilitator","dfnText":"Chartering Facilitator","external":false,"refSections":[{"refs":[{"id":"ref-for-chartering-facilitator"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-chartering-facilitator\u2460"},{"id":"ref-for-chartering-facilitator\u2461"},{"id":"ref-for-chartering-facilitator\u2462"}],"title":"4.2. \nCharter Refinement"}],"url":"#chartering-facilitator"},
+"convened": {"dfnID":"convened","dfnText":"convened","external":false,"refSections":[{"refs":[{"id":"ref-for-convened"},{"id":"ref-for-convened\u2460"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-convened\u2461"},{"id":"ref-for-convened\u2462"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#convened"},
+"council-report": {"dfnID":"council-report","dfnText":"Council Report","external":false,"refSections":[{"refs":[{"id":"ref-for-council-report"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-council-report\u2460"},{"id":"ref-for-council-report\u2461"},{"id":"ref-for-council-report\u2462"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-council-report\u2463"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-council-report\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-council-report\u2465"}],"title":"9. \nMember Submissions"}],"url":"#council-report"},
+"council-staff-contact": {"dfnID":"council-staff-contact","dfnText":"Council Staff Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-council-staff-contact"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-council-staff-contact\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#council-staff-contact"},
+"custodian": {"dfnID":"custodian","dfnText":"custodian","external":false,"refSections":[{"refs":[{"id":"ref-for-custodian"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-custodian\u2460"},{"id":"ref-for-custodian\u2461"},{"id":"ref-for-custodian\u2462"},{"id":"ref-for-custodian\u2463"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-custodian\u2464"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-custodian\u2465"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#custodian"},
+"def-Consensus": {"dfnID":"def-Consensus","dfnText":"Consensus","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Consensus"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-def-Consensus\u2460"},{"id":"ref-for-def-Consensus\u2461"},{"id":"ref-for-def-Consensus\u2462"},{"id":"ref-for-def-Consensus\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-def-Consensus\u2464"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-def-Consensus\u2465"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-def-Consensus\u2466"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-def-Consensus\u2467"},{"id":"ref-for-def-Consensus\u2468"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u24ea"},{"id":"ref-for-def-Consensus\u2460\u2460"},{"id":"ref-for-def-Consensus\u2460\u2461"},{"id":"ref-for-def-Consensus\u2460\u2462"},{"id":"ref-for-def-Consensus\u2460\u2463"},{"id":"ref-for-def-Consensus\u2460\u2464"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2465"}],"title":"6. \nW3C Technical Reports"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2466"},{"id":"ref-for-def-Consensus\u2460\u2467"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2468"},{"id":"ref-for-def-Consensus\u2461\u24ea"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-def-Consensus\u2461\u2460"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-def-Consensus\u2461\u2461"}],"title":"10. \nProcess Evolution"}],"url":"#def-Consensus"},
+"def-Dissent": {"dfnID":"def-Dissent","dfnText":"Dissent","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Dissent"},{"id":"ref-for-def-Dissent\u2460"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-def-Dissent\u2461"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-def-Dissent\u2462"},{"id":"ref-for-def-Dissent\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-Dissent\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-def-Dissent\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#def-Dissent"},
+"def-Unanimity": {"dfnID":"def-Unanimity","dfnText":"Unanimity","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Unanimity"}],"title":"5.2.1. \nConsensus"}],"url":"#def-Unanimity"},
+"def-W3CChair": {"dfnID":"def-W3CChair","dfnText":"W3C Chair","external":false,"refSections":[],"url":"#def-W3CChair"},
+"def-w3c-decision": {"dfnID":"def-w3c-decision","dfnText":"W3C decision","external":false,"refSections":[{"refs":[{"id":"ref-for-def-w3c-decision"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-def-w3c-decision\u2461"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-def-w3c-decision\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-def-w3c-decision\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-def-w3c-decision\u2464"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-def-w3c-decision\u2465"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-def-w3c-decision\u2466"},{"id":"ref-for-def-w3c-decision\u2467"},{"id":"ref-for-def-w3c-decision\u2468"},{"id":"ref-for-def-w3c-decision\u2460\u24ea"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2460"},{"id":"ref-for-def-w3c-decision\u2460\u2461"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2462"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2464"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2465"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2466"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#def-w3c-decision"},
+"dfn-charter-extension": {"dfnID":"dfn-charter-extension","dfnText":"extensions","external":false,"refSections":[{"refs":[{"id":"ref-for-dfn-charter-extension"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"}],"url":"#dfn-charter-extension"},
+"dfn-wide-review": {"dfnID":"dfn-wide-review","dfnText":"wide review","external":false,"refSections":[{"refs":[{"id":"ref-for-dfn-wide-review"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-dfn-wide-review\u2461"},{"id":"ref-for-dfn-wide-review\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-dfn-wide-review\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-dfn-wide-review\u2464"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2466"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2467"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-dfn-wide-review\u2468"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460\u24ea"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#dfn-wide-review"},
+"discontinuedREC": {"dfnID":"discontinuedREC","dfnText":"Discontinued Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-discontinuedREC"},{"id":"ref-for-discontinuedREC\u2460"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"}],"url":"#discontinuedREC"},
+"dismissed": {"dfnID":"dismissed","dfnText":"dismissed","external":false,"refSections":[{"refs":[{"id":"ref-for-dismissed"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-dismissed\u2460"},{"id":"ref-for-dismissed\u2461"},{"id":"ref-for-dismissed\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-dismissed\u2463"},{"id":"ref-for-dismissed\u2464"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-dismissed\u2465"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#dismissed"},
+"distributed-meeting": {"dfnID":"distributed-meeting","dfnText":"distributed meeting","external":false,"refSections":[{"refs":[{"id":"ref-for-distributed-meeting"}],"title":"5.2.1. \nConsensus"}],"url":"#distributed-meeting"},
+"edited-recommendation": {"dfnID":"edited-recommendation","dfnText":"Edited Recommendation","external":false,"refSections":[],"url":"#edited-recommendation"},
+"editorial-change": {"dfnID":"editorial-change","dfnText":"editorial changes","external":false,"refSections":[{"refs":[{"id":"ref-for-editorial-change"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-editorial-change\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2462"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2463"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-editorial-change\u2464"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-editorial-change\u2465"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-editorial-change\u2466"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-editorial-change\u2467"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-editorial-change\u2468"},{"id":"ref-for-editorial-change\u2460\u24ea"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#editorial-change"},
+"editors-draft": {"dfnID":"editors-draft","dfnText":"Editor\u2019s drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-editors-draft"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"}],"url":"#editors-draft"},
+"elected-group": {"dfnID":"elected-group","dfnText":"elected groups","external":false,"refSections":[{"refs":[{"id":"ref-for-elected-group"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-elected-group\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-elected-group\u2461"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#elected-group"},
+"embedded-registry": {"dfnID":"embedded-registry","dfnText":"embedded registry","external":false,"refSections":[{"refs":[{"id":"ref-for-embedded-registry"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-embedded-registry\u2460"},{"id":"ref-for-embedded-registry\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-embedded-registry\u2462"},{"id":"ref-for-embedded-registry\u2463"}],"title":"6.5.6. \nRegistries and Patents"},{"refs":[{"id":"ref-for-embedded-registry\u2464"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#embedded-registry"},
+"erratum": {"dfnID":"erratum","dfnText":"erratum","external":false,"refSections":[{"refs":[{"id":"ref-for-erratum"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-erratum\u2460"},{"id":"ref-for-erratum\u2461"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#erratum"},
+"exclusion-draft": {"dfnID":"exclusion-draft","dfnText":"Exclusion Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-exclusion-draft"},{"id":"ref-for-exclusion-draft\u2460"}],"title":"4.3. \nContent of a Charter"}],"url":"#exclusion-draft"},
+"exclusion-draft-charter": {"dfnID":"exclusion-draft-charter","dfnText":"Exclusion Draft Charter","external":false,"refSections":[{"refs":[{"id":"ref-for-exclusion-draft-charter"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#exclusion-draft-charter"},
+"fdn-member-consortium": {"dfnID":"fdn-member-consortium","dfnText":"Member Consortium","external":false,"refSections":[],"url":"#fdn-member-consortium"},
+"fellows": {"dfnID":"fellows","dfnText":"W3C Fellows","external":false,"refSections":[{"refs":[{"id":"ref-for-fellows"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-fellows"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}],"url":"#fellows"},
+"formally-addressed": {"dfnID":"formally-addressed","dfnText":"formally addressed","external":false,"refSections":[{"refs":[{"id":"ref-for-formally-addressed"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-formally-addressed\u2460"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-formally-addressed\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-formally-addressed\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-formally-addressed\u2463"},{"id":"ref-for-formally-addressed\u2464"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-formally-addressed\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-formally-addressed\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-formally-addressed\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#formally-addressed"},
+"fpwd": {"dfnID":"fpwd","dfnText":"First Public Working Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-fpwd"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-fpwd\u2460"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-fpwd\u2461"},{"id":"ref-for-fpwd\u2462"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-fpwd\u2463"},{"id":"ref-for-fpwd\u2464"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-fpwd\u2465"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-fpwd\u2466"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-fpwd\u2467"},{"id":"ref-for-fpwd\u2468"}],"title":"6.6. \nSwitching Tracks"}],"url":"#fpwd"},
+"ftf-meeting": {"dfnID":"ftf-meeting","dfnText":"face-to-face meeting","external":false,"refSections":[{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"5.6.2.1. \nCouncil Composition"}],"url":"#ftf-meeting"},
+"fully-addressed": {"dfnID":"fully-addressed","dfnText":"fully addressed","external":false,"refSections":[{"refs":[{"id":"ref-for-fully-addressed"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-fully-addressed\u2460"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#fully-addressed"},
+"good-standing": {"dfnID":"good-standing","dfnText":"Good Standing","external":false,"refSections":[{"refs":[{"id":"ref-for-good-standing"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-good-standing\u2460"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-good-standing\u2461"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#good-standing"},
+"group-decision": {"dfnID":"group-decision","dfnText":"group decisions","external":false,"refSections":[{"refs":[{"id":"ref-for-group-decision"},{"id":"ref-for-group-decision\u2460"}],"title":"3.1.2.2. \nMeeting Minutes"},{"refs":[{"id":"ref-for-group-decision\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-group-decision\u2462"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-group-decision\u2463"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-group-decision\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-group-decision\u2465"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-group-decision\u2466"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-group-decision\u2467"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-group-decision\u2468"}],"title":"6.6. \nSwitching Tracks"}],"url":"#group-decision"},
+"igparticipant": {"dfnID":"igparticipant","dfnText":"participants in an Interest Group","external":false,"refSections":[{"refs":[{"id":"ref-for-igparticipant"}],"title":"3. \nGroups and Participation"},{"refs":[{"id":"ref-for-igparticipant"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#igparticipant"},
+"inv-expert-info": {"dfnID":"inv-expert-info","dfnText":"participate in a Working Group as an Invited Expert","external":false,"refSections":[{"refs":[{"id":"ref-for-inv-expert-info"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-inv-expert-info"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"}],"url":"#inv-expert-info"},
+"invited-expert-in-a-working-group": {"dfnID":"invited-expert-in-a-working-group","dfnText":"Invited Expert in a Working Group","external":false,"refSections":[{"refs":[{"id":"ref-for-invited-expert-in-a-working-group"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-invited-expert-in-a-working-group\u2460"}],"title":"3.4.3.4. \nInvited Expert in an Interest Group"}],"url":"#invited-expert-in-a-working-group"},
+"invited-expert-in-an-interest-group": {"dfnID":"invited-expert-in-an-interest-group","dfnText":"Invited Expert in an Interest Group","external":false,"refSections":[],"url":"#invited-expert-in-an-interest-group"},
+"last-call": {"dfnID":"last-call","dfnText":"Last Call","external":false,"refSections":[],"url":"#last-call"},
+"last-call-for-review-of-proposed-additions": {"dfnID":"last-call-for-review-of-proposed-additions","dfnText":"Last Call for Review of Proposed Additions","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-additions"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-for-review-of-proposed-additions"},
+"last-call-for-review-of-proposed-corrections": {"dfnID":"last-call-for-review-of-proposed-corrections","dfnText":"Last Call for Review of Proposed Corrections","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-corrections"}],"title":"6.4.4. \nRevising W3C Statements"}],"url":"#last-call-for-review-of-proposed-corrections"},
+"last-call-for-review-of-proposed-corrections-and-additions": {"dfnID":"last-call-for-review-of-proposed-corrections-and-additions","dfnText":"Last Call for Review of Proposed Corrections and Additions","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-corrections-and-additions"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-for-review-of-proposed-corrections-and-additions"},
+"last-call-review": {"dfnID":"last-call-review","dfnText":"Last Call for Review of Proposed Amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-review"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-last-call-review\u2460"},{"id":"ref-for-last-call-review\u2461"},{"id":"ref-for-last-call-review\u2462"},{"id":"ref-for-last-call-review\u2463"},{"id":"ref-for-last-call-review\u2464"},{"id":"ref-for-last-call-review\u2465"},{"id":"ref-for-last-call-review\u2466"},{"id":"ref-for-last-call-review\u2467"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-review"},
+"liaison": {"dfnID":"liaison","dfnText":"liaison","external":false,"refSections":[],"url":"#liaison"},
+"maturity-levels": {"dfnID":"maturity-levels","dfnText":"Maturity level","external":false,"refSections":[],"url":"#maturity-levels"},
+"member-association": {"dfnID":"member-association","dfnText":"Member Association","external":false,"refSections":[{"refs":[{"id":"ref-for-member-association"},{"id":"ref-for-member-association\u2460"},{"id":"ref-for-member-association\u2461"},{"id":"ref-for-member-association\u2462"},{"id":"ref-for-member-association\u2463"},{"id":"ref-for-member-association\u2464"}],"title":"2.1.2.1. \nMembership Associations"},{"refs":[{"id":"ref-for-member-association\u2465"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#member-association"},
+"member-representative-in-a-working-group": {"dfnID":"member-representative-in-a-working-group","dfnText":"Member representative in a Working Group","external":false,"refSections":[],"url":"#member-representative-in-a-working-group"},
+"member-representative-in-an-interest-group": {"dfnID":"member-representative-in-an-interest-group","dfnText":"Member representative in an Interest Group","external":false,"refSections":[{"refs":[{"id":"ref-for-member-representative-in-an-interest-group"}],"title":"3.4.3.2. \nMember Representative in an Interest Group"}],"url":"#member-representative-in-an-interest-group"},
+"minor-changes": {"dfnID":"minor-changes","dfnText":"minor changes","external":false,"refSections":[{"refs":[{"id":"ref-for-minor-changes"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-minor-changes\u2460"},{"id":"ref-for-minor-changes\u2461"},{"id":"ref-for-minor-changes\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#minor-changes"},
+"minority-opinion": {"dfnID":"minority-opinion","dfnText":"Minority Opinion","external":false,"refSections":[{"refs":[{"id":"ref-for-minority-opinion"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#minority-opinion"},
+"minutes": {"dfnID":"minutes","dfnText":"minutes","external":false,"refSections":[{"refs":[{"id":"ref-for-minutes"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-minutes\u2460"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-minutes\u2461"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#minutes"},
+"mou": {"dfnID":"mou","dfnText":"Memorandum of Understanding","external":false,"refSections":[],"url":"#mou"},
+"mtg-substitute": {"dfnID":"mtg-substitute","dfnText":"substitute","external":false,"refSections":[{"refs":[{"id":"ref-for-mtg-substitute"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#mtg-substitute"},
+"not-required": {"dfnID":"not-required","dfnText":"not required","external":false,"refSections":[],"url":"#not-required"},
+"note-draft": {"dfnID":"note-draft","dfnText":"Note Drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-note-draft"},{"id":"ref-for-note-draft\u2460"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-note-draft\u2461"},{"id":"ref-for-note-draft\u2462"},{"id":"ref-for-note-draft\u2463"},{"id":"ref-for-note-draft\u2464"}],"title":"6.4.2. \nPublishing Notes"}],"url":"#note-draft"},
+"obsolete-registry": {"dfnID":"obsolete-registry","dfnText":"Obsolete Registry","external":false,"refSections":[],"url":"#obsolete-registry"},
+"other-charter": {"dfnID":"other-charter","dfnText":"Other Charter","external":false,"refSections":[],"url":"#other-charter"},
+"overrule": {"dfnID":"overrule","dfnText":"overruled","external":false,"refSections":[{"refs":[{"id":"ref-for-overrule"},{"id":"ref-for-overrule\u2460"},{"id":"ref-for-overrule\u2461"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-overrule\u2462"}],"title":"6.3.9.3. \nResolution of Review"}],"url":"#overrule"},
+"overturn": {"dfnID":"overturn","dfnText":"overturn","external":false,"refSections":[{"refs":[{"id":"ref-for-overturn"},{"id":"ref-for-overturn\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-overturn\u2461"},{"id":"ref-for-overturn\u2462"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#overturn"},
+"participant": {"dfnID":"participant","dfnText":"participant","external":false,"refSections":[{"refs":[{"id":"ref-for-participant"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-participant\u2460"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#participant"},
+"patent-review-drafts": {"dfnID":"patent-review-drafts","dfnText":"Patent Review Drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-patent-review-drafts"},{"id":"ref-for-patent-review-drafts\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-patent-review-drafts\u2461"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-patent-review-drafts\u2462"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-patent-review-drafts\u2463"}],"title":"6.6. \nSwitching Tracks"}],"url":"#patent-review-drafts"},
+"primary-affiliation": {"dfnID":"primary-affiliation","dfnText":"primary affiliation","external":false,"refSections":[{"refs":[{"id":"ref-for-primary-affiliation"},{"id":"ref-for-primary-affiliation\u2460"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-primary-affiliation\u2461"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}],"url":"#primary-affiliation"},
+"proposed-additions": {"dfnID":"proposed-additions","dfnText":"proposed additions","external":false,"refSections":[],"url":"#proposed-additions"},
+"proposed-amendments": {"dfnID":"proposed-amendments","dfnText":"proposed amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-proposed-amendments"},{"id":"ref-for-proposed-amendments\u2460"},{"id":"ref-for-proposed-amendments\u2461"},{"id":"ref-for-proposed-amendments\u2462"},{"id":"ref-for-proposed-amendments\u2463"},{"id":"ref-for-proposed-amendments\u2464"},{"id":"ref-for-proposed-amendments\u2465"},{"id":"ref-for-proposed-amendments\u2466"},{"id":"ref-for-proposed-amendments\u2467"},{"id":"ref-for-proposed-amendments\u2468"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-proposed-amendments\u2460\u24ea"},{"id":"ref-for-proposed-amendments\u2460\u2460"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-proposed-amendments\u2460\u2461"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#proposed-amendments"},
+"proposed-corrections": {"dfnID":"proposed-corrections","dfnText":"proposed corrections","external":false,"refSections":[],"url":"#proposed-corrections"},
+"public-participant-ig": {"dfnID":"public-participant-ig","dfnText":"public participants","external":false,"refSections":[{"refs":[{"id":"ref-for-public-participant-ig"}],"title":"4.3. \nContent of a Charter"}],"url":"#public-participant-ig"},
+"publishing": {"dfnID":"publishing","dfnText":"Publishing","external":false,"refSections":[{"refs":[{"id":"ref-for-publishing"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-publishing\u2460"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-publishing\u2461"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-publishing\u2462"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-publishing\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-publishing\u2464"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-publishing\u2465"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-publishing\u2466"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-publishing\u2467"},{"id":"ref-for-publishing\u2468"},{"id":"ref-for-publishing\u2460\u24ea"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-publishing\u2460\u2460"},{"id":"ref-for-publishing\u2460\u2461"}],"title":"6.4.1. \nGroup Notes"}],"url":"#publishing"},
+"rec-amended": {"dfnID":"rec-amended","dfnText":"Amended Recommendation","external":false,"refSections":[],"url":"#rec-amended"},
+"registry": {"dfnID":"registry","dfnText":"registry","external":false,"refSections":[{"refs":[{"id":"ref-for-registry"},{"id":"ref-for-registry\u2460"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry\u2461"},{"id":"ref-for-registry\u2462"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry\u2463"},{"id":"ref-for-registry\u2464"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry\u2465"},{"id":"ref-for-registry\u2466"},{"id":"ref-for-registry\u2467"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry\u2468"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry"},
+"registry-change": {"dfnID":"registry-change","dfnText":"registry changes","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-change"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-change\u2460"},{"id":"ref-for-registry-change\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-change\u2462"},{"id":"ref-for-registry-change\u2463"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#registry-change"},
+"registry-data": {"dfnID":"registry-data","dfnText":"registry data","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-data"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-data\u2460"},{"id":"ref-for-registry-data\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-data"},
+"registry-data-report": {"dfnID":"registry-data-report","dfnText":"Registry Data Report","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-data-report"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-data-report\u2460"},{"id":"ref-for-registry-data-report\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-data-report"},
+"registry-definition": {"dfnID":"registry-definition","dfnText":"registry definition","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-definition"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry-definition\u2460"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry-definition\u2461"},{"id":"ref-for-registry-definition\u2462"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-definition\u2463"},{"id":"ref-for-registry-definition\u2464"},{"id":"ref-for-registry-definition\u2465"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-definition\u2466"},{"id":"ref-for-registry-definition\u2467"},{"id":"ref-for-registry-definition\u2468"},{"id":"ref-for-registry-definition\u2460\u24ea"},{"id":"ref-for-registry-definition\u2460\u2460"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-registry-definition\u2460\u2461"},{"id":"ref-for-registry-definition\u2460\u2462"},{"id":"ref-for-registry-definition\u2460\u2463"},{"id":"ref-for-registry-definition\u2460\u2464"},{"id":"ref-for-registry-definition\u2460\u2465"},{"id":"ref-for-registry-definition\u2460\u2466"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-definition"},
+"registry-draft": {"dfnID":"registry-draft","dfnText":"Registry Draft","external":false,"refSections":[],"url":"#registry-draft"},
+"registry-entry": {"dfnID":"registry-entry","dfnText":"registry entries","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-entry"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-registry-entry\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-entry\u2461"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-registry-entry\u2462"}],"title":"6.5.5. \nSpecifications that Reference Registries"}],"url":"#registry-entry"},
+"registry-report": {"dfnID":"registry-report","dfnText":"registry report","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-report"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry-report\u2460"},{"id":"ref-for-registry-report\u2461"},{"id":"ref-for-registry-report\u2462"},{"id":"ref-for-registry-report\u2463"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-report\u2464"}],"title":"6.5.6. \nRegistries and Patents"}],"url":"#registry-report"},
+"registry-table": {"dfnID":"registry-table","dfnText":"registry tables","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-table"},{"id":"ref-for-registry-table\u2460"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-registry-table\u2461"},{"id":"ref-for-registry-table\u2462"},{"id":"ref-for-registry-table\u2463"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry-table\u2464"},{"id":"ref-for-registry-table\u2465"},{"id":"ref-for-registry-table\u2466"},{"id":"ref-for-registry-table\u2467"},{"id":"ref-for-registry-table\u2468"},{"id":"ref-for-registry-table\u2460\u24ea"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-table\u2460\u2460"},{"id":"ref-for-registry-table\u2460\u2461"},{"id":"ref-for-registry-table\u2460\u2462"},{"id":"ref-for-registry-table\u2460\u2463"},{"id":"ref-for-registry-table\u2460\u2464"},{"id":"ref-for-registry-table\u2460\u2465"},{"id":"ref-for-registry-table\u2460\u2466"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-table\u2460\u2467"},{"id":"ref-for-registry-table\u2460\u2468"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-registry-table\u2461\u24ea"},{"id":"ref-for-registry-table\u2461\u2460"},{"id":"ref-for-registry-table\u2461\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-table"},
+"registry-track": {"dfnID":"registry-track","dfnText":"Registry Track","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-track"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#registry-track"},
+"rejected": {"dfnID":"rejected","dfnText":"rejected","external":false,"refSections":[{"refs":[{"id":"ref-for-rejected"}],"title":"9. \nMember Submissions"}],"url":"#rejected"},
+"related-member": {"dfnID":"related-member","dfnText":"related","external":false,"refSections":[{"refs":[{"id":"ref-for-related-member"}],"title":"2.1.2.2. \nRelated Members"},{"refs":[{"id":"ref-for-related-member\u2460"}],"title":"2.1.3. \nGood Standing"},{"refs":[{"id":"ref-for-related-member\u2461"},{"id":"ref-for-related-member\u2462"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-related-member\u2463"}],"title":"5.8. \nAdvisory Committee Votes"}],"url":"#related-member"},
+"renounce": {"dfnID":"renounce","dfnText":"renounce","external":false,"refSections":[{"refs":[{"id":"ref-for-renounce"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-renounce\u2460"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-renounce\u2461"},{"id":"ref-for-renounce\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-renounce\u2463"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#renounce"},
+"rescinded-candidate-recommendation": {"dfnID":"rescinded-candidate-recommendation","dfnText":"Rescinded Candidate Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-rescinded-candidate-recommendation"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-rescinded-candidate-recommendation\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#rescinded-candidate-recommendation"},
+"reviewform": {"dfnID":"reviewform","dfnText":"Call for Review","external":false,"refSections":[{"refs":[{"id":"ref-for-reviewform"},{"id":"ref-for-reviewform\u2460"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-reviewform\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"}],"url":"#reviewform"},
+"statement": {"dfnID":"statement","dfnText":"W3C Statement","external":false,"refSections":[{"refs":[{"id":"ref-for-statement"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-statement\u2460"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-statement\u2461"},{"id":"ref-for-statement\u2462"},{"id":"ref-for-statement\u2463"},{"id":"ref-for-statement\u2464"},{"id":"ref-for-statement\u2465"},{"id":"ref-for-statement\u2466"},{"id":"ref-for-statement\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-statement\u2468"},{"id":"ref-for-statement\u2460\u24ea"},{"id":"ref-for-statement\u2460\u2460"},{"id":"ref-for-statement\u2460\u2461"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-statement\u2460\u2462"}],"title":"6.6. \nSwitching Tracks"}],"url":"#statement"},
+"submission-appeals": {"dfnID":"submission-appeals","dfnText":"Submission Appeals","external":false,"refSections":[{"refs":[{"id":"ref-for-submission-appeals"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-submission-appeals\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-submission-appeals\u2461"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-submission-appeals\u2462"},{"id":"ref-for-submission-appeals\u2463"}],"title":"9. \nMember Submissions"}],"url":"#submission-appeals"},
+"submitter": {"dfnID":"submitter","dfnText":"Submitter(s)","external":false,"refSections":[{"refs":[{"id":"ref-for-submitter"},{"id":"ref-for-submitter\u2460"},{"id":"ref-for-submitter\u2461"},{"id":"ref-for-submitter\u2462"},{"id":"ref-for-submitter\u2463"},{"id":"ref-for-submitter\u2464"},{"id":"ref-for-submitter\u2465"},{"id":"ref-for-submitter\u2466"}],"title":"9. \nMember Submissions"}],"url":"#submitter"},
+"subsidiary": {"dfnID":"subsidiary","dfnText":"subsidiary","external":false,"refSections":[{"refs":[{"id":"ref-for-subsidiary"},{"id":"ref-for-subsidiary\u2460"}],"title":"2.1.2.2. \nRelated Members"}],"url":"#subsidiary"},
+"substantive-change": {"dfnID":"substantive-change","dfnText":"substantive changes","external":false,"refSections":[{"refs":[{"id":"ref-for-substantive-change"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-substantive-change\u2460"},{"id":"ref-for-substantive-change\u2461"},{"id":"ref-for-substantive-change\u2462"},{"id":"ref-for-substantive-change\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-substantive-change\u2464"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-substantive-change\u2465"},{"id":"ref-for-substantive-change\u2466"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-substantive-change\u2467"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-substantive-change\u2468"},{"id":"ref-for-substantive-change\u2460\u24ea"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2460"},{"id":"ref-for-substantive-change\u2460\u2461"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2462"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2463"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"}],"url":"#substantive-change"},
+"superseded-registry": {"dfnID":"superseded-registry","dfnText":"Superseded Registry","external":false,"refSections":[],"url":"#superseded-registry"},
+"supplemental-confidential-council-report": {"dfnID":"supplemental-confidential-council-report","dfnText":"Supplemental Confidential Council Report","external":false,"refSections":[],"url":"#supplemental-confidential-council-report"},
+"team": {"dfnID":"team","dfnText":"Team","external":false,"refSections":[{"refs":[{"id":"ref-for-team"},{"id":"ref-for-team\u2460"},{"id":"ref-for-team\u2461"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-team\u2462"},{"id":"ref-for-team\u2463"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-team\u2464"},{"id":"ref-for-team\u2465"},{"id":"ref-for-team\u2466"}],"title":"3.1.1.2. \nConflict of Interest Policy"},{"refs":[{"id":"ref-for-team\u2467"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-team\u2468"},{"id":"ref-for-team\u2460\u24ea"}],"title":"3.1.4. \nResignation from a Group"},{"refs":[{"id":"ref-for-team\u2460\u2460"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-team\u2460\u2461"},{"id":"ref-for-team\u2460\u2462"},{"id":"ref-for-team\u2460\u2463"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-team\u2460\u2464"},{"id":"ref-for-team\u2460\u2465"},{"id":"ref-for-team\u2460\u2466"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-team\u2460\u2467"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-team\u2460\u2468"}],"title":"3.3.1.3. \nCommunications of the Advisory Board"},{"refs":[{"id":"ref-for-team\u2461\u24ea"},{"id":"ref-for-team\u2461\u2460"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-team\u2461\u2461"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-team\u2461\u2462"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-team\u2461\u2463"},{"id":"ref-for-team\u2461\u2464"},{"id":"ref-for-team\u2461\u2465"},{"id":"ref-for-team\u2461\u2466"},{"id":"ref-for-team\u2461\u2467"},{"id":"ref-for-team\u2461\u2468"},{"id":"ref-for-team\u2462\u24ea"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-team\u2462\u2460"},{"id":"ref-for-team\u2462\u2461"},{"id":"ref-for-team\u2462\u2462"},{"id":"ref-for-team\u2462\u2463"},{"id":"ref-for-team\u2462\u2464"},{"id":"ref-for-team\u2462\u2465"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-team\u2462\u2466"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-team\u2462\u2467"},{"id":"ref-for-team\u2462\u2468"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-team\u2463\u24ea"},{"id":"ref-for-team\u2463\u2460"},{"id":"ref-for-team\u2463\u2461"},{"id":"ref-for-team\u2463\u2462"},{"id":"ref-for-team\u2463\u2463"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-team\u2463\u2464"},{"id":"ref-for-team\u2463\u2465"},{"id":"ref-for-team\u2463\u2466"},{"id":"ref-for-team\u2463\u2467"},{"id":"ref-for-team\u2463\u2468"},{"id":"ref-for-team\u2464\u24ea"},{"id":"ref-for-team\u2464\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-team\u2464\u2461"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-team\u2464\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-team\u2464\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-team\u2464\u2464"},{"id":"ref-for-team\u2464\u2465"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-team\u2464\u2466"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-team\u2464\u2467"},{"id":"ref-for-team\u2464\u2468"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-team\u2465\u24ea"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-team\u2465\u2460"},{"id":"ref-for-team\u2465\u2461"},{"id":"ref-for-team\u2465\u2462"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-team\u2465\u2463"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-team\u2465\u2464"},{"id":"ref-for-team\u2465\u2465"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-team\u2465\u2466"},{"id":"ref-for-team\u2465\u2467"},{"id":"ref-for-team\u2465\u2468"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-team\u2466\u24ea"},{"id":"ref-for-team\u2466\u2460"},{"id":"ref-for-team\u2466\u2461"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-team\u2466\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-team\u2466\u2463"},{"id":"ref-for-team\u2466\u2464"},{"id":"ref-for-team\u2466\u2465"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-team\u2466\u2466"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-team\u2466\u2467"},{"id":"ref-for-team\u2466\u2468"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-team\u2467\u24ea"},{"id":"ref-for-team\u2467\u2460"},{"id":"ref-for-team\u2467\u2461"},{"id":"ref-for-team\u2467\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-team\u2467\u2463"},{"id":"ref-for-team\u2467\u2464"},{"id":"ref-for-team\u2467\u2465"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-team\u2467\u2466"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-team\u2467\u2467"},{"id":"ref-for-team\u2467\u2468"},{"id":"ref-for-team\u2468\u24ea"},{"id":"ref-for-team\u2468\u2460"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-team\u2468\u2461"}],"title":"6.2.7. \nLicense Grants from Non-Participants"},{"refs":[{"id":"ref-for-team\u2468\u2462"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-team\u2468\u2463"}],"title":"6.3.2. \nImplementation Experience"},{"refs":[{"id":"ref-for-team\u2468\u2464"},{"id":"ref-for-team\u2468\u2465"},{"id":"ref-for-team\u2468\u2466"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2468\u2467"},{"id":"ref-for-team\u2468\u2468"},{"id":"ref-for-team\u2460\u24ea\u24ea"},{"id":"ref-for-team\u2460\u24ea\u2460"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2461"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2462"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2463"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2464"},{"id":"ref-for-team\u2460\u24ea\u2465"},{"id":"ref-for-team\u2460\u24ea\u2466"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2467"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2468"},{"id":"ref-for-team\u2460\u2460\u24ea"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2460"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2461"},{"id":"ref-for-team\u2460\u2460\u2462"},{"id":"ref-for-team\u2460\u2460\u2463"},{"id":"ref-for-team\u2460\u2460\u2464"},{"id":"ref-for-team\u2460\u2460\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2466"},{"id":"ref-for-team\u2460\u2460\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2468"},{"id":"ref-for-team\u2460\u2461\u24ea"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2461"},{"id":"ref-for-team\u2460\u2461\u2462"}],"title":"7.1. \nPublic Communication"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2463"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2464"},{"id":"ref-for-team\u2460\u2461\u2465"},{"id":"ref-for-team\u2460\u2461\u2466"},{"id":"ref-for-team\u2460\u2461\u2467"}],"title":"7.3. \nChanging Confidentiality Level"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2468"},{"id":"ref-for-team\u2460\u2462\u24ea"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-team\u2460\u2462\u2460"},{"id":"ref-for-team\u2460\u2462\u2461"},{"id":"ref-for-team\u2460\u2462\u2462"},{"id":"ref-for-team\u2460\u2462\u2463"},{"id":"ref-for-team\u2460\u2462\u2464"},{"id":"ref-for-team\u2460\u2462\u2465"},{"id":"ref-for-team\u2460\u2462\u2466"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-team\u2460\u2462\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#team"},
+"team-contact": {"dfnID":"team-contact","dfnText":"Team Contact","external":false,"refSections":[],"url":"#team-contact"},
+"team-correction": {"dfnID":"team-correction","dfnText":"Team correction","external":false,"refSections":[{"refs":[{"id":"ref-for-team-correction"},{"id":"ref-for-team-correction\u2460"},{"id":"ref-for-team-correction\u2461"},{"id":"ref-for-team-correction\u2462"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#team-correction"},
+"team-decision": {"dfnID":"team-decision","dfnText":"Team Decisions","external":false,"refSections":[{"refs":[{"id":"ref-for-team-decision"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-team-decision\u2460"},{"id":"ref-for-team-decision\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-team-decision\u2462"},{"id":"ref-for-team-decision\u2463"},{"id":"ref-for-team-decision\u2464"},{"id":"ref-for-team-decision\u2465"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-team-decision\u2466"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-team-decision\u2467"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-team-decision\u2468"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-team-decision\u2460\u24ea"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-team-decision\u2460\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-team-decision\u2460\u2461"}],"title":"8. \nLiaisons"}],"url":"#team-decision"},
+"team-representative-in-a-working-group": {"dfnID":"team-representative-in-a-working-group","dfnText":"Team representative in a Working Group","external":false,"refSections":[],"url":"#team-representative-in-a-working-group"},
+"team-representative-in-an-interest-group": {"dfnID":"team-representative-in-an-interest-group","dfnText":"Team representative in an Interest Group","external":false,"refSections":[],"url":"#team-representative-in-an-interest-group"},
+"technical-agreement": {"dfnID":"technical-agreement","dfnText":"technical agreement","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-agreement"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-technical-agreement\u2460"},{"id":"ref-for-technical-agreement\u2461"},{"id":"ref-for-technical-agreement\u2462"},{"id":"ref-for-technical-agreement\u2463"},{"id":"ref-for-technical-agreement\u2464"},{"id":"ref-for-technical-agreement\u2465"},{"id":"ref-for-technical-agreement\u2466"},{"id":"ref-for-technical-agreement\u2467"},{"id":"ref-for-technical-agreement\u2468"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-technical-agreement\u2460\u24ea"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#technical-agreement"},
+"technical-architecture-group": {"dfnID":"technical-architecture-group","dfnText":"TAG","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-architecture-group"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461"},{"id":"ref-for-technical-architecture-group\u2462"},{"id":"ref-for-technical-architecture-group\u2463"},{"id":"ref-for-technical-architecture-group\u2464"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2465"},{"id":"ref-for-technical-architecture-group\u2466"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2467"},{"id":"ref-for-technical-architecture-group\u2468"},{"id":"ref-for-technical-architecture-group\u2460\u24ea"},{"id":"ref-for-technical-architecture-group\u2460\u2460"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2461"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2462"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2463"},{"id":"ref-for-technical-architecture-group\u2460\u2464"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2465"},{"id":"ref-for-technical-architecture-group\u2460\u2466"},{"id":"ref-for-technical-architecture-group\u2460\u2467"},{"id":"ref-for-technical-architecture-group\u2460\u2468"},{"id":"ref-for-technical-architecture-group\u2461\u24ea"},{"id":"ref-for-technical-architecture-group\u2461\u2460"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2461"}],"title":"3.3.3.5. \nVerifiable Random Selection Procedure"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2462"},{"id":"ref-for-technical-architecture-group\u2461\u2463"},{"id":"ref-for-technical-architecture-group\u2461\u2464"},{"id":"ref-for-technical-architecture-group\u2461\u2465"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2466"},{"id":"ref-for-technical-architecture-group\u2461\u2467"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2468"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u24ea"},{"id":"ref-for-technical-architecture-group\u2462\u2460"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2461"},{"id":"ref-for-technical-architecture-group\u2462\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2463"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2465"},{"id":"ref-for-technical-architecture-group\u2462\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2467"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2468"}],"title":"9. \nMember Submissions"}],"url":"#technical-architecture-group"},
+"technical-report": {"dfnID":"technical-report","dfnText":"Technical Report","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-report"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-technical-report\u2460"},{"id":"ref-for-technical-report\u2461"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-technical-report\u2462"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-technical-report\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-technical-report\u2464"},{"id":"ref-for-technical-report\u2465"},{"id":"ref-for-technical-report\u2466"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-technical-report\u2467"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-technical-report\u2468"},{"id":"ref-for-technical-report\u2460\u24ea"},{"id":"ref-for-technical-report\u2460\u2460"},{"id":"ref-for-technical-report\u2460\u2461"},{"id":"ref-for-technical-report\u2460\u2462"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-technical-report\u2460\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-technical-report\u2460\u2464"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2460\u2465"},{"id":"ref-for-technical-report\u2460\u2466"},{"id":"ref-for-technical-report\u2460\u2467"},{"id":"ref-for-technical-report\u2460\u2468"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2461\u24ea"},{"id":"ref-for-technical-report\u2461\u2460"},{"id":"ref-for-technical-report\u2461\u2461"},{"id":"ref-for-technical-report\u2461\u2462"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-technical-report\u2461\u2463"},{"id":"ref-for-technical-report\u2461\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2461\u2465"},{"id":"ref-for-technical-report\u2461\u2466"},{"id":"ref-for-technical-report\u2461\u2467"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-technical-report\u2461\u2468"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-technical-report\u2462\u24ea"},{"id":"ref-for-technical-report\u2462\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-technical-report\u2462\u2461"},{"id":"ref-for-technical-report\u2462\u2462"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-technical-report\u2462\u2463"},{"id":"ref-for-technical-report\u2462\u2464"},{"id":"ref-for-technical-report\u2462\u2465"},{"id":"ref-for-technical-report\u2462\u2466"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-technical-report\u2462\u2467"},{"id":"ref-for-technical-report\u2462\u2468"},{"id":"ref-for-technical-report\u2463\u24ea"},{"id":"ref-for-technical-report\u2463\u2460"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-technical-report\u2463\u2461"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-technical-report\u2463\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#technical-report"},
+"trans-req": {"dfnID":"trans-req","dfnText":"Transition Requests","external":false,"refSections":[{"refs":[{"id":"ref-for-trans-req"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2460"},{"id":"ref-for-trans-req\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2462"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2463"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"}],"url":"#trans-req"},
+"update-requests": {"dfnID":"update-requests","dfnText":"Update Requests","external":false,"refSections":[{"refs":[{"id":"ref-for-update-requests"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-update-requests\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-update-requests\u2461"},{"id":"ref-for-update-requests\u2462"},{"id":"ref-for-update-requests\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-update-requests\u2464"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-update-requests\u2465"},{"id":"ref-for-update-requests\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-update-requests\u2467"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-update-requests\u2468"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-update-requests\u2460\u24ea"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-update-requests\u2460\u2460"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#update-requests"},
+"upheld": {"dfnID":"upheld","dfnText":"upheld","external":false,"refSections":[{"refs":[{"id":"ref-for-upheld"},{"id":"ref-for-upheld\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-upheld\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-upheld\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-upheld\u2463"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-upheld\u2464"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#upheld"},
+"w3c-council": {"dfnID":"w3c-council","dfnText":"W3C Council","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-council"},{"id":"ref-for-w3c-council\u2460"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-w3c-council\u2461"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-w3c-council\u2462"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-w3c-council\u2463"},{"id":"ref-for-w3c-council\u2464"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-w3c-council\u2465"},{"id":"ref-for-w3c-council\u2466"},{"id":"ref-for-w3c-council\u2467"},{"id":"ref-for-w3c-council\u2468"},{"id":"ref-for-w3c-council\u2460\u24ea"},{"id":"ref-for-w3c-council\u2460\u2460"},{"id":"ref-for-w3c-council\u2460\u2461"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2462"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2463"},{"id":"ref-for-w3c-council\u2460\u2464"},{"id":"ref-for-w3c-council\u2460\u2465"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2466"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2467"},{"id":"ref-for-w3c-council\u2460\u2468"},{"id":"ref-for-w3c-council\u2461\u24ea"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-w3c-council\u2461\u2460"},{"id":"ref-for-w3c-council\u2461\u2461"},{"id":"ref-for-w3c-council\u2461\u2462"},{"id":"ref-for-w3c-council\u2461\u2463"},{"id":"ref-for-w3c-council\u2461\u2464"},{"id":"ref-for-w3c-council\u2461\u2465"},{"id":"ref-for-w3c-council\u2461\u2466"},{"id":"ref-for-w3c-council\u2461\u2467"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-w3c-council\u2461\u2468"},{"id":"ref-for-w3c-council\u2462\u24ea"},{"id":"ref-for-w3c-council\u2462\u2460"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2461"},{"id":"ref-for-w3c-council\u2462\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2463"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2464"},{"id":"ref-for-w3c-council\u2462\u2465"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2466"},{"id":"ref-for-w3c-council\u2462\u2467"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#w3c-council"},
+"w3c-council-chair": {"dfnID":"w3c-council-chair","dfnText":"Chair","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-council-chair"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-w3c-council-chair\u2460"}],"title":"5.6.2.4. \nShort Circuit"},{"refs":[{"id":"ref-for-w3c-council-chair\u2461"},{"id":"ref-for-w3c-council-chair\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-w3c-council-chair\u2463"},{"id":"ref-for-w3c-council-chair\u2464"},{"id":"ref-for-w3c-council-chair\u2465"},{"id":"ref-for-w3c-council-chair\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#w3c-council-chair"},
+"w3c-group": {"dfnID":"w3c-group","dfnText":"W3C Group","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-group"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-w3c-group\u2460"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-w3c-group\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-w3c-group\u2462"},{"id":"ref-for-w3c-group\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"#w3c-group"},
+"w3c-member": {"dfnID":"w3c-member","dfnText":"W3C Members","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-member"}],"title":"2.1.3. \nGood Standing"},{"refs":[{"id":"ref-for-w3c-member\u2460"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-w3c-member\u2461"},{"id":"ref-for-w3c-member\u2462"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-w3c-member\u2463"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-w3c-member\u2464"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-w3c-member\u2465"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-w3c-member\u2466"}],"title":"9. \nMember Submissions"}],"url":"#w3c-member"},
+"w3c-recommendation-track": {"dfnID":"w3c-recommendation-track","dfnText":"W3C Recommendation Track","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-recommendation-track"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460"},{"id":"ref-for-w3c-recommendation-track\u2461"},{"id":"ref-for-w3c-recommendation-track\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2463"},{"id":"ref-for-w3c-recommendation-track\u2464"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2465"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2466"},{"id":"ref-for-w3c-recommendation-track\u2467"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2468"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u24ea"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2462"}],"title":"6.5.6. \nRegistries and Patents"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2463"},{"id":"ref-for-w3c-recommendation-track\u2460\u2464"},{"id":"ref-for-w3c-recommendation-track\u2460\u2465"}],"title":"6.6. \nSwitching Tracks"}],"url":"#w3c-recommendation-track"},
+"w3c-recommendation-track-document": {"dfnID":"w3c-recommendation-track-document","dfnText":"W3C Recommendation Track document","external":false,"refSections":[],"url":"#w3c-recommendation-track-document"},
+"w3c-registry": {"dfnID":"w3c-registry","dfnText":"W3C Registry","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-registry"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-w3c-registry\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#w3c-registry"},
+"wgparticipant": {"dfnID":"wgparticipant","dfnText":"participants in a Working Group","external":false,"refSections":[{"refs":[{"id":"ref-for-wgparticipant"}],"title":"3. \nGroups and Participation"},{"refs":[{"id":"ref-for-wgparticipant"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#wgparticipant"},
+};
+
+document.addEventListener("DOMContentLoaded", ()=>{
+    genAllDfnPanels();
+
+    document.body.addEventListener("click", (e) => {
+        // If not handled already, just hide all dfn panels.
+        hideAllDfnPanels();
+    });
+});
+
+window.addEventListener("resize", () => {
+    // Pin any visible dfn panel
+    queryAll(".dfn-panel.on, .dfn-panel.activated").forEach(el=>positionDfnPanel(el));
+});
+
+function genAllDfnPanels() {
+    for(const panelData of Object.values(dfnPanelData)) {
+        const dfnID = panelData.dfnID;
+        const dfn = document.getElementById(dfnID);
+        if(!dfn) {
+            console.log(`Can't find dfn#${dfnID}.`, panelData);
+            continue;
+        }
+        dfn.panelData = panelData;
+        insertDfnPopupAction(dfn);
+    }
+}
+
+function genDfnPanel(dfn, { dfnID, url, dfnText, refSections, external }) {
+    const dfnPanel = mk.aside({
+        class: "dfn-panel on",
+        id: `infopanel-for-${dfnID}`,
+        "data-for": dfnID,
+        "aria-labelled-by":`infopaneltitle-for-${dfnID}`,
+        },
+        mk.span({id:`infopaneltitle-for-${dfnID}`, style:"display:none"},
+            `Info about the '${dfnText}' ${external?"external":""} reference.`),
+        mk.a({href:url, class:"dfn-link"}, url),
+        refSections.length == 0 ? [] :
+            mk.b({}, "Referenced in:"),
+            mk.ul({},
+                ...refSections.map(section=>
+                    mk.li({},
+                        ...section.refs.map((ref, refI)=>
+                            [
+                                mk.a({ href: `#${ref.id}` },
+                                    (refI == 0) ? section.title : `(${refI + 1})`
+                                ),
+                                " ",
+                            ]
+                        ),
+                    ),
+                ),
+            ),
+        genLinkingSyntaxes(dfn),
+    );
+
+    dfnPanel.addEventListener('click', (event) => {
+        if (event.target.nodeName == 'A') {
+            scrollToTargetAndHighlight(event);
+            pinDfnPanel(dfnPanel);
+        }
+        event.stopPropagation();
+        refocusOnTarget(event);
+    });
+    dfnPanel.addEventListener('keydown', (event) => {
+        if(event.keyCode == 27) { // Escape key
+            hideDfnPanel({dfnPanel});
+            event.stopPropagation();
+            event.preventDefault();
+        }
+    });
+
+    dfnPanel.dfn = dfn;
+    dfn.dfnPanel = dfnPanel;
+    return dfnPanel;
+}
+
+
+
+function hideAllDfnPanels() {
+    // Delete the currently-active dfn panel.
+    queryAll(".dfn-panel").forEach(dfnPanel=>hideDfnPanel({dfnPanel}));
+}
+
+function showDfnPanel(dfn) {
+    hideAllDfnPanels(); // Only display one at a time.
+
+    dfn.setAttribute("aria-expanded", "true");
+
+    const dfnPanel = genDfnPanel(dfn, dfn.panelData);
+
+    // Give the dfn a unique tabindex, and then
+    // give all the tabbable panel bits successive indexes.
+    let tabIndex = 100;
+    dfn.tabIndex = tabIndex++;
+    const tabbable = dfnPanel.querySelectorAll(":is(a, button)");
+    for (const el of tabbable) {
+        el.tabIndex = tabIndex++;
+    }
+
+    append(document.body, dfnPanel);
+    positionDfnPanel(dfnPanel);
+}
+
+function positionDfnPanel(dfnPanel) {
+    const dfn = dfnPanel.dfn;
+    const dfnPos = getBounds(dfn);
+    dfnPanel.style.top = dfnPos.bottom + "px";
+    dfnPanel.style.left = dfnPos.left + "px";
+
+    const panelPos = dfnPanel.getBoundingClientRect();
+    const panelMargin = 8;
+    const maxRight = document.body.parentNode.clientWidth - panelMargin;
+    if (panelPos.right > maxRight) {
+        const overflowAmount = panelPos.right - maxRight;
+        const newLeft = Math.max(panelMargin, dfnPos.left - overflowAmount);
+        dfnPanel.style.left = newLeft + "px";
+    }
+}
+
+function pinDfnPanel(dfnPanel) {
+    // Switch it to "activated" state, which pins it.
+    dfnPanel.classList.add("activated");
+    dfnPanel.style.position = "fixed";
+    dfnPanel.style.left = null;
+    dfnPanel.style.top = null;
+}
+
+function hideDfnPanel({dfn, dfnPanel}) {
+    if(!dfnPanel) dfnPanel = dfn.dfnPanel;
+    if(!dfn) dfn = dfnPanel.dfn;
+    dfn.dfnPanel = undefined;
+    dfnPanel.dfn = undefined;
+    dfn.setAttribute("aria-expanded", "false");
+    dfn.tabIndex = undefined;
+    dfnPanel.remove()
+}
+
+function toggleDfnPanel(dfn) {
+    if(dfn.dfnPanel) {
+        hideDfnPanel(dfn);
+    } else {
+        showDfnPanel(dfn);
+    }
+}
+
+function insertDfnPopupAction(dfn) {
+    dfn.setAttribute('role', 'button');
+    dfn.setAttribute('aria-expanded', 'false')
+    dfn.tabIndex = 0;
+    dfn.classList.add('has-dfn-panel');
+    dfn.addEventListener('click', (event) => {
+        toggleDfnPanel(dfn);
+        event.stopPropagation();
+    });
+    dfn.addEventListener('keypress', (event) => {
+        const kc = event.keyCode;
+        // 32->Space, 13->Enter
+        if(kc == 32 || kc == 13) {
+            toggleDfnPanel(dfn);
+            event.stopPropagation();
+            event.preventDefault();
+        }
+    });
+}
+
+function refocusOnTarget(event) {
+    const target = event.target;
+    setTimeout(() => {
+        // Refocus on the event.target element.
+        // This is needed after browser scrolls to the destination.
+        target.focus();
+    });
+}
+
+// TODO: shared util
+// Returns the root-level absolute position {left and top} of element.
+function getBounds(el, relativeTo=document.body) {
+    const relativeRect = relativeTo.getBoundingClientRect();
+    const elRect = el.getBoundingClientRect();
+    const top = elRect.top - relativeRect.top;
+    const left = elRect.left - relativeRect.left;
+    return {
+        top,
+        left,
+        bottom: top + elRect.height,
+        right: left + elRect.width,
+    }
+}
+
+function scrollToTargetAndHighlight(event) {
+    let hash = event.target.hash;
+    if (hash) {
+        hash = decodeURIComponent(hash.substring(1));
+        const dest = document.getElementById(hash);
+        if (dest) {
+            dest.classList.add('highlighted');
+            setTimeout(() => dest.classList.remove('highlighted'), 1000);
+        }
+    }
+}
+
+// Functions, divided by link type, that wrap an autolink's
+// contents with the appropriate outer syntax.
+// Alternately, a string naming another type they format
+// the same as.
+function needsFor(type) {
+    switch(type) {
+        case "descriptor":
+        case "value":
+        case "element-attr":
+        case "attr-value":
+        case "element-state":
+        case "method":
+        case "constructor":
+        case "argument":
+        case "attribute":
+        case "const":
+        case "dict-member":
+        case "event":
+        case "enum-value":
+        case "stringifier":
+        case "serializer":
+        case "iterator":
+        case "maplike":
+        case "setlike":
+        case "state":
+        case "mode":
+        case "context":
+        case "facet": return true;
+
+        default: return false;
+    }
+}
+function refusesFor(type) {
+    switch(type) {
+        case "property":
+        case "element":
+        case "interface":
+        case "namespace":
+        case "callback":
+        case "dictionary":
+        case "enum":
+        case "exception":
+        case "typedef":
+        case "http-header":
+        case "permission": return true;
+
+        default: return false;
+    }
+}
+function linkFormatterFromType(type) {
+    switch(type) {
+        case 'scheme':
+        case 'permission':
+        case 'dfn': return (text) => `[=${text}=]`;
+
+        case 'abstract-op': return (text) => `[\$${text}\$]`;
+
+        case 'function':
+        case 'at-rule':
+        case 'selector':
+        case 'value': return (text) => `''${text}''`;
+
+        case 'http-header': return (text) => `[:${text}:]`;
+
+        case 'interface':
+        case 'constructor':
+        case 'method':
+        case 'argument':
+        case 'attribute':
+        case 'callback':
+        case 'dictionary':
+        case 'dict-member':
+        case 'enum':
+        case 'enum-value':
+        case 'exception':
+        case 'const':
+        case 'typedef':
+        case 'stringifier':
+        case 'serializer':
+        case 'iterator':
+        case 'maplike':
+        case 'setlike':
+        case 'extended-attribute':
+        case 'event':
+        case 'idl': return (text) => `{{${text}}}`;
+
+        case 'element-state':
+        case 'element-attr':
+        case 'attr-value':
+        case 'element': return (element) => `<{${element}}>`;
+
+        case 'grammar': return (text) => `${text} (within a <pre class=prod>)`;
+
+        case 'type': return (text)=> `<<${text}>>`;
+
+        case 'descriptor':
+        case 'property': return (text) => `'${text}'`;
+
+        default: return;
+    };
+};
+
+function genLinkingSyntaxes(dfn) {
+    if(dfn.tagName != "DFN") return;
+
+    const type = dfn.getAttribute('data-dfn-type');
+    if(!type) {
+        console.log(`<dfn> doesn't have a data-dfn-type:`, dfn);
+        return [];
+    }
+
+    // Return a function that wraps link text based on the type
+    const linkFormatter = linkFormatterFromType(type);
+    if(!linkFormatter) {
+        console.log(`<dfn> has an unknown data-dfn-type:`, dfn);
+        return [];
+    }
+
+    let ltAlts;
+    if(dfn.hasAttribute('data-lt')) {
+        ltAlts = dfn.getAttribute('data-lt')
+            .split("|")
+            .map(x=>x.trim());
+    } else {
+        ltAlts = [dfn.textContent.trim()];
+    }
+    if(type == "type") {
+        // lt of "<foo>", but "foo" is the interior;
+        // <<foo/bar>> is how you write it with a for,
+        // not <foo/<bar>> or whatever.
+        for(var i = 0; i < ltAlts.length; i++) {
+            const lt = ltAlts[i];
+            const match = /<(.*)>/.exec(lt);
+            if(match) { ltAlts[i] = match[1]; }
+        }
+    }
+
+    let forAlts;
+    if(dfn.hasAttribute('data-dfn-for')) {
+        forAlts = dfn.getAttribute('data-dfn-for')
+            .split(",")
+            .map(x=>x.trim());
+    } else {
+        forAlts = [''];
+    }
+
+    let linkingSyntaxes = [];
+    if(!needsFor(type)) {
+        for(const lt of ltAlts) {
+            linkingSyntaxes.push(linkFormatter(lt));
+        }
+    }
+    if(!refusesFor(type)) {
+        for(const f of forAlts) {
+            linkingSyntaxes.push(linkFormatter(`${f}/${ltAlts[0]}`))
+        }
+    }
+    return [
+        mk.b({}, 'Possible linking syntaxes:'),
+        mk.ul({},
+            ...linkingSyntaxes.map(link => {
+                const copyLink = async () =>
+                    await navigator.clipboard.writeText(link);
+                return mk.li({},
+                    mk.div({ class: 'link-item' },
+                        mk.button({
+                            class: 'copy-icon', title: 'Copy',
+                            type: 'button',
+                            _onclick: copyLink,
+                            tabindex: 0,
+                        }, mk.span({ class: 'icon' }) ),
+                        mk.span({}, link)
+                    )
+                );
+            })
+        )
+    ];
+}
+}
+</script>
+<script>/* Boilerplate: script-ref-hints */
+"use strict";
+{
+let refsData = {
+"#EventsW": {"displayText":"workshop","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"workshop","type":"dfn","url":"#EventsW"},
+"#FormalObjection": {"displayText":"formal objection","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"formal objection","type":"dfn","url":"#FormalObjection"},
+"#GeneralChairs": {"displayText":"chair","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chair","type":"dfn","url":"#GeneralChairs"},
+"#GroupsIG": {"displayText":"interest groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"interest groups","type":"dfn","url":"#GroupsIG"},
+"#GroupsWG": {"displayText":"working groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"working groups","type":"dfn","url":"#GroupsWG"},
+"#Member-only": {"displayText":"member-only","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member-only","type":"dfn","url":"#Member-only"},
+"#MemberSubmission": {"displayText":"member submission","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member submission","type":"dfn","url":"#MemberSubmission"},
+"#RecsCR": {"displayText":"candidate recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation","type":"dfn","url":"#RecsCR"},
+"#RecsObs": {"displayText":"obsolete recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"obsolete recommendation","type":"dfn","url":"#RecsObs"},
+"#RecsSup": {"displayText":"superseded recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"superseded recommendation","type":"dfn","url":"#RecsSup"},
+"#RecsW3C": {"displayText":"w3c recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c recommendation","type":"dfn","url":"#RecsW3C"},
+"#RecsWD": {"displayText":"working draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"working draft","type":"dfn","url":"#RecsWD"},
+"#RescindedRec": {"displayText":"rescinded recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rescinded recommendation","type":"dfn","url":"#RescindedRec"},
+"#Team-only": {"displayText":"team-only","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team-only","type":"dfn","url":"#Team-only"},
+"#TeamContact": {"displayText":"staff contact","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"staff contact","type":"dfn","url":"#TeamContact"},
+"#WGNote": {"displayText":"note","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"note","type":"dfn","url":"#WGNote"},
+"#acknowledged": {"displayText":"acknowledged","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"acknowledged","type":"dfn","url":"#acknowledged"},
+"#adequate-implementation": {"displayText":"adequate implementation experience","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"adequate implementation experience","type":"dfn","url":"#adequate-implementation"},
+"#adopted-draft": {"displayText":"adopted draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"adopted draft","type":"dfn","url":"#adopted-draft"},
+"#advisory-board": {"displayText":"ab","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ab","type":"dfn","url":"#advisory-board"},
+"#advisory-committee": {"displayText":"advisory committee","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"advisory committee","type":"dfn","url":"#advisory-committee"},
+"#advisory-committee-appeal": {"displayText":"ac appeal","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ac appeal","type":"dfn","url":"#advisory-committee-appeal"},
+"#advisory-committee-representative": {"displayText":"advisory committee representative","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"advisory committee representative","type":"dfn","url":"#advisory-committee-representative"},
+"#advisory-committee-review": {"displayText":"ac review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ac review","type":"dfn","url":"#advisory-committee-review"},
+"#affirm": {"displayText":"affirm","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"affirm","type":"dfn","url":"#affirm"},
+"#allow-new-features": {"displayText":"allow new features","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"allow new features","type":"dfn","url":"#allow-new-features"},
+"#appeal-vote": {"displayText":"appeal vote","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"appeal vote","type":"dfn","url":"#appeal-vote"},
+"#at-risk": {"displayText":"at risk","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"at risk","type":"dfn","url":"#at-risk"},
+"#bod": {"displayText":"board","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"board","type":"dfn","url":"#bod"},
+"#candidate-addition": {"displayText":"candidate addition","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate addition","type":"dfn","url":"#candidate-addition"},
+"#candidate-amendment": {"displayText":"candidate amendment","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate amendment","type":"dfn","url":"#candidate-amendment"},
+"#candidate-correction": {"displayText":"candidate correction","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate correction","type":"dfn","url":"#candidate-correction"},
+"#candidate-recommendation-draft": {"displayText":"candidate recommendation draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation draft","type":"dfn","url":"#candidate-recommendation-draft"},
+"#candidate-recommendation-review-period": {"displayText":"candidate recommendation review period","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation review period","type":"dfn","url":"#candidate-recommendation-review-period"},
+"#candidate-recommendation-snapshot": {"displayText":"crs","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"crs","type":"dfn","url":"#candidate-recommendation-snapshot"},
+"#candidate-registry": {"displayText":"candidate registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate registry","type":"dfn","url":"#candidate-registry"},
+"#ceo": {"displayText":"ceo","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ceo","type":"dfn","url":"#ceo"},
+"#charter": {"displayText":"charter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter","type":"dfn","url":"#charter"},
+"#charter-draft": {"displayText":"charter draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter draft","type":"dfn","url":"#charter-draft"},
+"#charter-refinement": {"displayText":"charter refinement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter refinement","type":"dfn","url":"#charter-refinement"},
+"#charter-review-notice": {"displayText":"charter review notice","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter review notice","type":"dfn","url":"#charter-review-notice"},
+"#chartered-group": {"displayText":"chartered groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chartered groups","type":"dfn","url":"#chartered-group"},
+"#chartering-facilitator": {"displayText":"chartering facilitator","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chartering facilitator","type":"dfn","url":"#chartering-facilitator"},
+"#convened": {"displayText":"convened","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"convened","type":"dfn","url":"#convened"},
+"#council-report": {"displayText":"council report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council report","type":"dfn","url":"#council-report"},
+"#council-staff-contact": {"displayText":"council staff contact","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council staff contact","type":"dfn","url":"#council-staff-contact"},
+"#custodian": {"displayText":"custodian","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"custodian","type":"dfn","url":"#custodian"},
+"#def-Consensus": {"displayText":"consensus","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"consensus","type":"dfn","url":"#def-Consensus"},
+"#def-Dissent": {"displayText":"dissent","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"dissent","type":"dfn","url":"#def-Dissent"},
+"#def-Unanimity": {"displayText":"unanimity","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"unanimity","type":"dfn","url":"#def-Unanimity"},
+"#def-w3c-decision": {"displayText":"w3c decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c decision","type":"dfn","url":"#def-w3c-decision"},
+"#dfn-charter-extension": {"displayText":"charter extension","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter extension","type":"dfn","url":"#dfn-charter-extension"},
+"#dfn-wide-review": {"displayText":"wide review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"wide review","type":"dfn","url":"#dfn-wide-review"},
+"#discontinuedREC": {"displayText":"discontinued draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"discontinued draft","type":"dfn","url":"#discontinuedREC"},
+"#dismissed": {"displayText":"dismissal","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"dismissal","type":"dfn","url":"#dismissed"},
+"#editorial-change": {"displayText":"editorial change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"editorial change","type":"dfn","url":"#editorial-change"},
+"#editors-draft": {"displayText":"editor's draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"editor's draft","type":"dfn","url":"#editors-draft"},
+"#elected-group": {"displayText":"elected groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"elected groups","type":"dfn","url":"#elected-group"},
+"#embedded-registry": {"displayText":"embedded registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"embedded registry","type":"dfn","url":"#embedded-registry"},
+"#erratum": {"displayText":"erratum","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"erratum","type":"dfn","url":"#erratum"},
+"#exclusion-draft": {"displayText":"exclusion draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"exclusion draft","type":"dfn","url":"#exclusion-draft"},
+"#exclusion-draft-charter": {"displayText":"exclusion draft charter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"exclusion draft charter","type":"dfn","url":"#exclusion-draft-charter"},
+"#formally-addressed": {"displayText":"formally addressed","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"formally addressed","type":"dfn","url":"#formally-addressed"},
+"#fpwd": {"displayText":"first public working draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"first public working draft","type":"dfn","url":"#fpwd"},
+"#ftf-meeting": {"displayText":"face-to-face meeting","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"face-to-face meeting","type":"dfn","url":"#ftf-meeting"},
+"#fully-addressed": {"displayText":"fully addressed","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"fully addressed","type":"dfn","url":"#fully-addressed"},
+"#good-standing": {"displayText":"good standing","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"good standing","type":"dfn","url":"#good-standing"},
+"#group-decision": {"displayText":"group decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"group decision","type":"dfn","url":"#group-decision"},
+"#invited-expert-in-a-working-group": {"displayText":"invited expert in a working group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"invited expert in a working group","type":"dfn","url":"#invited-expert-in-a-working-group"},
+"#last-call-for-review-of-proposed-additions": {"displayText":"last call for review of proposed additions","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed additions","type":"dfn","url":"#last-call-for-review-of-proposed-additions"},
+"#last-call-for-review-of-proposed-corrections": {"displayText":"last call for review of proposed corrections","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed corrections","type":"dfn","url":"#last-call-for-review-of-proposed-corrections"},
+"#last-call-for-review-of-proposed-corrections-and-additions": {"displayText":"last call for review of proposed corrections and additions","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed corrections and additions","type":"dfn","url":"#last-call-for-review-of-proposed-corrections-and-additions"},
+"#last-call-review": {"displayText":"last call for review of proposed amendments","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed amendments","type":"dfn","url":"#last-call-review"},
+"#member-association": {"displayText":"member association","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member association","type":"dfn","url":"#member-association"},
+"#member-representative-in-an-interest-group": {"displayText":"member representative in an interest group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member representative in an interest group","type":"dfn","url":"#member-representative-in-an-interest-group"},
+"#minor-changes": {"displayText":"minor changes","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minor changes","type":"dfn","url":"#minor-changes"},
+"#minority-opinion": {"displayText":"minority opinion","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minority opinion","type":"dfn","url":"#minority-opinion"},
+"#minutes": {"displayText":"minutes","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minutes","type":"dfn","url":"#minutes"},
+"#note-draft": {"displayText":"note draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"note draft","type":"dfn","url":"#note-draft"},
+"#overrule": {"displayText":"overrule","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"overrule","type":"dfn","url":"#overrule"},
+"#overturn": {"displayText":"overturn","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"overturn","type":"dfn","url":"#overturn"},
+"#participant": {"displayText":"participant","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"participant","type":"dfn","url":"#participant"},
+"#patent-review-drafts": {"displayText":"patent review drafts","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"patent review drafts","type":"dfn","url":"#patent-review-drafts"},
+"#primary-affiliation": {"displayText":"primary affiliation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"primary affiliation","type":"dfn","url":"#primary-affiliation"},
+"#proposed-amendments": {"displayText":"proposed amendments","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"proposed amendments","type":"dfn","url":"#proposed-amendments"},
+"#publishing": {"displayText":"publish","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"publish","type":"dfn","url":"#publishing"},
+"#registry": {"displayText":"registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry","type":"dfn","url":"#registry"},
+"#registry-change": {"displayText":"registry change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry change","type":"dfn","url":"#registry-change"},
+"#registry-data": {"displayText":"registry data","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry data","type":"dfn","url":"#registry-data"},
+"#registry-data-report": {"displayText":"registry data report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry data report","type":"dfn","url":"#registry-data-report"},
+"#registry-definition": {"displayText":"registry definition","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry definition","type":"dfn","url":"#registry-definition"},
+"#registry-entry": {"displayText":"registry entry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry entry","type":"dfn","url":"#registry-entry"},
+"#registry-report": {"displayText":"registry report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry report","type":"dfn","url":"#registry-report"},
+"#registry-table": {"displayText":"registry table","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry table","type":"dfn","url":"#registry-table"},
+"#registry-track": {"displayText":"registry track","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry track","type":"dfn","url":"#registry-track"},
+"#rejected": {"displayText":"rejected","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rejected","type":"dfn","url":"#rejected"},
+"#related-member": {"displayText":"related member","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"related member","type":"dfn","url":"#related-member"},
+"#renounce": {"displayText":"renunciation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"renunciation","type":"dfn","url":"#renounce"},
+"#rescinded-candidate-recommendation": {"displayText":"rescinded candidate recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rescinded candidate recommendation","type":"dfn","url":"#rescinded-candidate-recommendation"},
+"#reviewform": {"displayText":"call for review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"call for review","type":"dfn","url":"#reviewform"},
+"#statement": {"displayText":"w3c statement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c statement","type":"dfn","url":"#statement"},
+"#submission-appeals": {"displayText":"submission appeals","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"submission appeals","type":"dfn","url":"#submission-appeals"},
+"#submitter": {"displayText":"submitter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"submitter","type":"dfn","url":"#submitter"},
+"#subsidiary": {"displayText":"subsidiary","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"subsidiary","type":"dfn","url":"#subsidiary"},
+"#substantive-change": {"displayText":"substantive change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"substantive change","type":"dfn","url":"#substantive-change"},
+"#team": {"displayText":"team","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team","type":"dfn","url":"#team"},
+"#team-correction": {"displayText":"team correction","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team correction","type":"dfn","url":"#team-correction"},
+"#team-decision": {"displayText":"team decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team decision","type":"dfn","url":"#team-decision"},
+"#technical-agreement": {"displayText":"technical agreement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"technical agreement","type":"dfn","url":"#technical-agreement"},
+"#technical-architecture-group": {"displayText":"tag","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"tag","type":"dfn","url":"#technical-architecture-group"},
+"#technical-report": {"displayText":"technical report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"technical report","type":"dfn","url":"#technical-report"},
+"#trans-req": {"displayText":"transition requests","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"transition requests","type":"dfn","url":"#trans-req"},
+"#update-requests": {"displayText":"update requests","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"update requests","type":"dfn","url":"#update-requests"},
+"#upheld": {"displayText":"upheld","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"upheld","type":"dfn","url":"#upheld"},
+"#w3c-council": {"displayText":"w3c council","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c council","type":"dfn","url":"#w3c-council"},
+"#w3c-council-chair": {"displayText":"council chair","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council chair","type":"dfn","url":"#w3c-council-chair"},
+"#w3c-group": {"displayText":"w3c group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c group","type":"dfn","url":"#w3c-group"},
+"#w3c-member": {"displayText":"member","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member","type":"dfn","url":"#w3c-member"},
+"#w3c-recommendation-track": {"displayText":"rec track","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rec track","type":"dfn","url":"#w3c-recommendation-track"},
+"#w3c-registry": {"displayText":"w3c registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c registry","type":"dfn","url":"#w3c-registry"},
+"https://www.w3.org/policies/patent-policy/#exclusion-opportunity": {"displayText":"Exclusion Opportunity","export":false,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"exclusion opportunity","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
+"https://www.w3.org/policies/patent-policy/#patent-advisory-group": {"displayText":"Patent Advisory Group","export":true,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"patent advisory group","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
+"https://www.w3.org/policies/process/#WGNote": {"displayText":"W3C Note","export":true,"for_":[],"level":"1","normative":true,"shortname":"w3c-process","spec":"w3c-process","status":"current","text":"w3c note","type":"dfn","url":"https://www.w3.org/policies/process/#WGNote"},
+};
+
+function mkRefHint(link, ref) {
+    const linkText = link.textContent;
+    let dfnTextElements = '';
+    if (ref.displayText.toLowerCase() != linkText.toLowerCase()) {
+        // Give the original term if it's being displayed in a different way.
+        // But allow casing differences, they're insignificant.
+        dfnTextElements =
+            mk.li({},
+                mk.b({}, "Term: "),
+                mk.span({}, ref.displayText)
+            );
+    }
+    const forList = ref.for_;
+    let forListElements;
+    if(forList.length == 0) {
+        forListElements = [];
+    } else if(forList.length == 1) {
+        forListElements = mk.li({},
+            mk.b({}, "For: "),
+            mk.span({}, forList[0]),
+        );
+    } else {
+        forListElements = mk.li({},
+            mk.b({}, "For: "),
+            mk.ul({},
+                ...forList.map(forItem =>
+                    mk.li({},
+                        mk.span({}, forItem)
+                    ),
+                ),
+            ),
+        );
+    }
+    const url = ref.url;
+    const safeUrl = encodeURIComponent(url);
+    const hintPanel = mk.aside({
+        class: "ref-hint",
+        id: `ref-hint-for-${safeUrl}`,
+        "data-for": url,
+        "aria-labelled-by": `ref-hint-for-${safeUrl}`,
+    },
+        mk.ul({},
+            dfnTextElements,
+            mk.li({},
+                mk.b({}, "URL: "),
+                mk.a({ href: url, class: "ref" }, url),
+            ),
+            mk.li({},
+                mk.b({}, "Type: "),
+                mk.span({}, `${ref.type}`),
+            ),
+            mk.li({},
+                mk.b({}, "Spec: "),
+                mk.span({}, `${ref.spec ? ref.spec : ''}`),
+            ),
+            forListElements
+        ),
+    );
+    hintPanel.forLink = link;
+    setupRefHintEventListeners(link, hintPanel);
+    return hintPanel;
+}
+
+function hideAllRefHints() {
+    queryAll(".ref-hint").forEach(el=>hideRefHint(el));
+}
+
+function hideRefHint(refHint) {
+    const link = refHint.forLink;
+    link.setAttribute("aria-expanded", "false");
+    if(refHint.teardownEventListeners) {
+        refHint.teardownEventListeners();
+    }
+    refHint.remove();
+}
+
+function showRefHint(link) {
+    if(link.classList.contains("dfn-link")) return;
+    const url = link.getAttribute("href");
+    const refHintKey = link.getAttribute("data-refhint-key");
+    let key = url;
+    if(refHintKey) {
+        key = refHintKey + "_" + url;
+    }
+    const ref = refsData[key];
+    if(!ref) return;
+
+    hideAllRefHints(); // Only display one at this time.
+
+    const refHint = mkRefHint(link, ref);
+    append(document.body, refHint);
+    link.setAttribute("aria-expanded", "true");
+    positionRefHint(refHint);
+}
+
+function setupRefHintEventListeners(link, refHint) {
+    if (refHint.teardownEventListeners) return;
+    // Add event handlers to hide the refHint after the user moves away
+    // from both the link and refHint, if not hovering either within one second.
+    let timeout = null;
+    const startHidingRefHint = (event) => {
+        if (timeout) {
+            clearTimeout(timeout);
+        }
+        timeout = setTimeout(() => {
+            hideRefHint(refHint);
+        }, 1000);
+    }
+    const resetHidingRefHint = (event) => {
+        if (timeout) clearTimeout(timeout);
+        timeout = null;
+    };
+    link.addEventListener("mouseleave", startHidingRefHint);
+    link.addEventListener("mouseenter", resetHidingRefHint);
+    link.addEventListener("blur", startHidingRefHint);
+    link.addEventListener("focus", resetHidingRefHint);
+    refHint.addEventListener("mouseleave", startHidingRefHint);
+    refHint.addEventListener("mouseenter", resetHidingRefHint);
+    refHint.addEventListener("blur", startHidingRefHint);
+    refHint.addEventListener("focus", resetHidingRefHint);
+
+    refHint.teardownEventListeners = () => {
+        // remove event listeners
+        resetHidingRefHint();
+        link.removeEventListener("mouseleave", startHidingRefHint);
+        link.removeEventListener("mouseenter", resetHidingRefHint);
+        link.removeEventListener("blur", startHidingRefHint);
+        link.removeEventListener("focus", resetHidingRefHint);
+        refHint.removeEventListener("mouseleave", startHidingRefHint);
+        refHint.removeEventListener("mouseenter", resetHidingRefHint);
+        refHint.removeEventListener("blur", startHidingRefHint);
+        refHint.removeEventListener("focus", resetHidingRefHint);
+    };
+}
+
+function positionRefHint(refHint) {
+    const link = refHint.forLink;
+    const linkPos = getBounds(link);
+    refHint.style.top = linkPos.bottom + "px";
+    refHint.style.left = linkPos.left + "px";
+
+    const panelPos = refHint.getBoundingClientRect();
+    const panelMargin = 8;
+    const maxRight = document.body.parentNode.clientWidth - panelMargin;
+    if (panelPos.right > maxRight) {
+        const overflowAmount = panelPos.right - maxRight;
+        const newLeft = Math.max(panelMargin, linkPos.left - overflowAmount);
+        refHint.style.left = newLeft + "px";
+    }
+}
+
+// TODO: shared util
+// Returns the root-level absolute position {left and top} of element.
+function getBounds(el, relativeTo=document.body) {
+    const relativeRect = relativeTo.getBoundingClientRect();
+    const elRect = el.getBoundingClientRect();
+    const top = elRect.top - relativeRect.top;
+    const left = elRect.left - relativeRect.left;
+    return {
+        top,
+        left,
+        bottom: top + elRect.height,
+        right: left + elRect.width,
+    }
+}
+
+function showRefHintListener(e) {
+    // If the target isn't in a link (or is a link),
+    // just ignore it.
+    let link = e.target.closest("a");
+    if(!link) return;
+
+    // If the target is in a ref-hint panel
+    // (aka a link in the already-open one),
+    // also just ignore it.
+    if(link.closest(".ref-hint")) return;
+
+    // Otherwise, show the panel for the link.
+    showRefHint(link);
+}
+
+function hideAllHintsListener(e) {
+    // If the click is inside a ref-hint panel, ignore it.
+    if(e.target.closest(".ref-hint")) return;
+    // Otherwise, close all the current panels.
+    hideAllRefHints();
+}
+
+document.addEventListener("DOMContentLoaded", () => {
+    document.body.addEventListener("mousedown", showRefHintListener);
+    document.body.addEventListener("focus", showRefHintListener);
+
+    document.body.addEventListener("click", hideAllHintsListener);
+});
+
+window.addEventListener("resize", () => {
+    // Hide any open ref hint.
+    hideAllRefHints();
+});
+}
+</script>
\ No newline at end of file

From 9715bd816d21191563400d77029188bd9f18c72a Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 24 Jun 2025 08:36:25 +0200
Subject: [PATCH 228/237] Fix stray reference

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 2893638f..9c338336 100644
--- a/index.bs
+++ b/index.bs
@@ -3086,7 +3086,7 @@ Types of Technical Reports</h3>
 
 		<dt>Notes
 		<dd>
-			Groups can also publish documents as [=W3C Notes=] and [=W3C Statements=],
+			Groups can also publish documents as [=Group Notes=] and [=W3C Statements=],
 			typically either to document information
 			other than technical specifications,
 			such as use cases motivating a specification

From d11049dfecd39105304abff68d5aa9596ac6cbab Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Tue, 24 Jun 2025 08:37:10 +0200
Subject: [PATCH 229/237] Fixup 2025-06 snapshot

---
 snapshots/2025-06.html | 39 +++++++++------------------------------
 1 file changed, 9 insertions(+), 30 deletions(-)

diff --git a/snapshots/2025-06.html b/snapshots/2025-06.html
index 67dcedc3..c6de3797 100644
--- a/snapshots/2025-06.html
+++ b/snapshots/2025-06.html
@@ -8,7 +8,7 @@
   <meta content="Bikeshed version b25686b9f, updated Fri Mar 14 14:15:20 2025 -0700" name="generator">
   <link href="https://www.w3.org/policies/process/" rel="canonical">
   <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
-  <meta content="b077baa3b38881c4e04f5819e36bc6148ca24872" name="revision">
+  <meta content="69f1a8979cede347a0edb3d2431a90c5397f0877" name="revision">
   <meta content="dark light" name="color-scheme">
   <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
 <style>
@@ -613,12 +613,14 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
-   <p id="w3c-state"><a href="https://www.w3.org/standards/types/#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2025-06-23">23 June 2025</time></p>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types/#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2025-06-24">24 June 2025</time></p>
    <details open>
     <summary>More details about this document</summary>
     <div data-fill-with="spec-metadata">
      <dl>
       <dt>This version:
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/snapshots/2025-06">https://www.w3.org/policies/process/drafts/snapshots/2025-06</a>
+      <dt>Editor’s Draft:
       <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/</a>
       <dt>Latest published version:
       <dd><a href="https://www.w3.org/policies/process/">https://www.w3.org/policies/process/</a>
@@ -658,7 +660,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content"
 	follows the <a href="https://www.w3.org/policies/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
 	working within the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a> (which anyone can join).
-	This is the 23 June 2025 Draft Community Group Report for the proposed next version of the W3C Process Document. </p>
+	This is the 24 June 2025 Draft Community Group Report for the proposed next version of the W3C Process Document. </p>
    <p>This document,
 which is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>,
 is offered for W3C Advisory Committee Review of the proposal to adopt this
@@ -3011,7 +3013,7 @@ <h3 class="heading settled" data-level="6.1" id="recs-and-notes"><span class="se
 			under which participants commit to Royalty-Free IPR licenses for implementations.
 			See <a href="#rec-track">§ 6.3 The W3C Recommendation Track</a> for details. 
      <dt>Notes 
-     <dd> Groups can also publish documents as <a data-link-type="dfn" href="https://www.w3.org/policies/process/#WGNote" id="ref-for-WGNote①">W3C Notes</a> and <a data-link-type="dfn" href="#statement" id="ref-for-statement">W3C Statements</a>,
+     <dd> Groups can also publish documents as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①">Group Notes</a> and <a data-link-type="dfn" href="#statement" id="ref-for-statement">W3C Statements</a>,
 			typically either to document information
 			other than technical specifications,
 			such as use cases motivating a specification
@@ -4976,9 +4978,9 @@ <h2 class="non-normative nonum heading settled" id="changes"><span class="conten
     <h3 class="no-num heading settled" id="changes-2025"><span class="content"> Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></span><a class="self-link" href="#changes-2025"></a></h3>
     <p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
 	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
-	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2F">diff from Process 2023 to this latest version</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2Fsnapshots%2F2025-05">diff from Process 2023 to this latest version</a>,
 	as well as
-	a <a href="https://github.com/w3c/process/compare/p2023_1...main">detailed log of all changes since then</a> are available. </p>
+	a <a href="https://github.com/w3c/process/compare/p2023_1...2025-ballot-draft">detailed log of all changes since then</a> are available. </p>
     <p>In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:</p>
     <dl>
      <dt id="changes-2025-tr"><a class="self-link" href="#changes-2025-tr"></a>Changes to technical reports and their publication 
@@ -5102,40 +5104,26 @@ <h3 class="no-num heading settled" id="changes-previous"><span class="bs-old-id"
     <h2 class="no-ref no-num heading settled" id="w3c-conformance"><span class="content">Conformance</span><a class="self-link" href="#w3c-conformance"></a></h2>
     <h3 class="no-ref no-num heading settled" id="w3c-conventions"><span class="content">Document conventions</span><a class="self-link" href="#w3c-conventions"></a></h3>
     <p>Conformance requirements are expressed
-
     with a combination of descriptive assertions
-
     and RFC 2119 terminology.
-
     The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
-
     in the normative parts of this document
-
     are to be interpreted as described in RFC 2119.
-
     However, for readability,
-
     these words do not appear in all uppercase letters in this specification. </p>
     <p>All of the text of this specification is normative
-
     except sections explicitly marked as non-normative, examples, and notes. <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a> </p>
     <p>Examples in this specification are introduced with the words “for example”
-
     or are set apart from the normative text
-
     with <code>class="example"</code>,
-
     like this: </p>
     <div class="example" id="w3c-example">
      <a class="self-link" href="#w3c-example"></a> 
      <p>This is an example of an informative example. </p>
     </div>
     <p>Informative notes begin with the word “Note”
-
     and are set apart from the normative text
-
     with <code>class="note"</code>,
-
     like this: </p>
     <p class="note" role="note">Note, this is an informative note.</p>
    </div>
@@ -5351,11 +5339,6 @@ <h3 class="no-num no-ref heading settled" id="index-defined-elsewhere"><span cla
      <li><span class="dfn-paneled" id="33fd2aef">Exclusion Opportunity</span>
      <li><span class="dfn-paneled" id="74c78a1e">Patent Advisory Group</span>
     </ul>
-   <li>
-    <a data-link-type="biblio">[W3C-PROCESS]</a> defines the following terms:
-    <ul>
-     <li><span class="dfn-paneled" id="3a585f2f">W3C Note</span>
-    </ul>
   </ul>
   <h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
   <h3 class="no-num no-ref heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
@@ -5382,8 +5365,6 @@ <h3 class="no-num no-ref heading settled" id="normative"><span class="content">N
    <dd>D. Eastlake 3rd. <a href="https://www.rfc-editor.org/rfc/rfc3797"><cite>Publicly Verifiable Nominations Committee (NomCom) Random Selection</cite></a>. June 2004. Informational. URL: <a href="https://www.rfc-editor.org/rfc/rfc3797">https://www.rfc-editor.org/rfc/rfc3797</a>
    <dt id="biblio-w3c-patent-policy">[W3C-PATENT-POLICY]
    <dd>Wendy Seltzer. <a href="https://www.w3.org/policies/patent-policy/"><cite>W3C Patent Policy</cite></a>. 15 September 2020. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
-   <dt id="biblio-w3c-process">[W3C-PROCESS]
-   <dd>Elika J. Etemad (fantasai); Florian Rivoal. <a href="https://www.w3.org/policies/process/"><cite>W3C Process Document</cite></a>. 3 November 2023. URL: <a href="https://www.w3.org/policies/process/">https://www.w3.org/policies/process/</a>
   </dl>
   <h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
   <dl>
@@ -5653,7 +5634,6 @@ <h3 class="no-num no-ref heading settled" id="informative"><span class="content"
 {
 let dfnPanelData = {
 "33fd2aef": {"dfnID":"33fd2aef","dfnText":"Exclusion Opportunity","external":true,"refSections":[{"refs":[{"id":"ref-for-exclusion-opportunity"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
-"3a585f2f": {"dfnID":"3a585f2f","dfnText":"W3C Note","external":true,"refSections":[{"refs":[{"id":"ref-for-WGNote\u2460"}],"title":"6.1. \nTypes of Technical Reports"}],"url":"https://www.w3.org/policies/process/#WGNote"},
 "74c78a1e": {"dfnID":"74c78a1e","dfnText":"Patent Advisory Group","external":true,"refSections":[{"refs":[{"id":"ref-for-patent-advisory-group"}],"title":"4.7. \nChartered Group Closure"}],"url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
 "EventsW": {"dfnID":"EventsW","dfnText":"Workshop","external":false,"refSections":[{"refs":[{"id":"ref-for-EventsW"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-EventsW\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-EventsW\u2461"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-EventsW\u2462"}],"title":"7.1. \nPublic Communication"}],"url":"#EventsW"},
 "FormalObjection": {"dfnID":"FormalObjection","dfnText":"Formal Objection","external":false,"refSections":[{"refs":[{"id":"ref-for-FormalObjection"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-FormalObjection\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-FormalObjection\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-FormalObjection\u2462"},{"id":"ref-for-FormalObjection\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-FormalObjection\u2464"}],"title":"5. \nDecisions"},{"refs":[{"id":"ref-for-FormalObjection\u2465"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-FormalObjection\u2466"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-FormalObjection\u2467"},{"id":"ref-for-FormalObjection\u2468"},{"id":"ref-for-FormalObjection\u2460\u24ea"},{"id":"ref-for-FormalObjection\u2460\u2460"},{"id":"ref-for-FormalObjection\u2460\u2461"},{"id":"ref-for-FormalObjection\u2460\u2462"},{"id":"ref-for-FormalObjection\u2460\u2463"},{"id":"ref-for-FormalObjection\u2460\u2464"},{"id":"ref-for-FormalObjection\u2460\u2465"},{"id":"ref-for-FormalObjection\u2460\u2466"},{"id":"ref-for-FormalObjection\u2460\u2467"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-FormalObjection\u2460\u2468"},{"id":"ref-for-FormalObjection\u2461\u24ea"},{"id":"ref-for-FormalObjection\u2461\u2460"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2461"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2462"},{"id":"ref-for-FormalObjection\u2461\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2464"},{"id":"ref-for-FormalObjection\u2461\u2465"},{"id":"ref-for-FormalObjection\u2461\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2468"},{"id":"ref-for-FormalObjection\u2462\u24ea"},{"id":"ref-for-FormalObjection\u2462\u2460"},{"id":"ref-for-FormalObjection\u2462\u2461"},{"id":"ref-for-FormalObjection\u2462\u2462"},{"id":"ref-for-FormalObjection\u2462\u2463"},{"id":"ref-for-FormalObjection\u2462\u2464"},{"id":"ref-for-FormalObjection\u2462\u2465"},{"id":"ref-for-FormalObjection\u2462\u2466"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2468"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u24ea"},{"id":"ref-for-FormalObjection\u2463\u2460"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2461"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2462"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2463"}],"title":"9. \nMember Submissions"}],"url":"#FormalObjection"},
@@ -5672,7 +5652,7 @@ <h3 class="no-num no-ref heading settled" id="informative"><span class="content"
 "Team-only": {"dfnID":"Team-only","dfnText":"Team-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Team-only"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-Team-only"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Team-only\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Team-only\u2461"},{"id":"ref-for-Team-only\u2462"},{"id":"ref-for-Team-only\u2463"},{"id":"ref-for-Team-only\u2464"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Team-only"},
 "TeamContact": {"dfnID":"TeamContact","dfnText":"Staff Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-TeamContact"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-TeamContact\u2460"},{"id":"ref-for-TeamContact\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2462"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2463"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2464"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2465"},{"id":"ref-for-TeamContact\u2466"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-TeamContact\u2467"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-TeamContact\u2468"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-TeamContact\u2460\u24ea"}],"title":"5.5. \nRegistering Formal Objections"}],"url":"#TeamContact"},
 "TeamSubmission": {"dfnID":"TeamSubmission","dfnText":"Team Submissions","external":false,"refSections":[],"url":"#TeamSubmission"},
-"WGNote": {"dfnID":"WGNote","dfnText":"Group Note","external":false,"refSections":[{"refs":[{"id":"ref-for-WGNote"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-WGNote"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-WGNote\u2461"},{"id":"ref-for-WGNote\u2462"},{"id":"ref-for-WGNote\u2463"},{"id":"ref-for-WGNote\u2464"},{"id":"ref-for-WGNote\u2465"},{"id":"ref-for-WGNote\u2466"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-WGNote\u2467"},{"id":"ref-for-WGNote\u2468"},{"id":"ref-for-WGNote\u2460\u24ea"},{"id":"ref-for-WGNote\u2460\u2460"},{"id":"ref-for-WGNote\u2460\u2461"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-WGNote\u2460\u2462"},{"id":"ref-for-WGNote\u2460\u2463"},{"id":"ref-for-WGNote\u2460\u2464"},{"id":"ref-for-WGNote\u2460\u2465"},{"id":"ref-for-WGNote\u2460\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#WGNote"},
+"WGNote": {"dfnID":"WGNote","dfnText":"Group Note","external":false,"refSections":[{"refs":[{"id":"ref-for-WGNote"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-WGNote"},{"id":"ref-for-WGNote\u2460"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-WGNote\u2461"},{"id":"ref-for-WGNote\u2462"},{"id":"ref-for-WGNote\u2463"},{"id":"ref-for-WGNote\u2464"},{"id":"ref-for-WGNote\u2465"},{"id":"ref-for-WGNote\u2466"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-WGNote\u2467"},{"id":"ref-for-WGNote\u2468"},{"id":"ref-for-WGNote\u2460\u24ea"},{"id":"ref-for-WGNote\u2460\u2460"},{"id":"ref-for-WGNote\u2460\u2461"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-WGNote\u2460\u2462"},{"id":"ref-for-WGNote\u2460\u2463"},{"id":"ref-for-WGNote\u2460\u2464"},{"id":"ref-for-WGNote\u2460\u2465"},{"id":"ref-for-WGNote\u2460\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#WGNote"},
 "acknowledged": {"dfnID":"acknowledged","dfnText":"acknowledged","external":false,"refSections":[{"refs":[{"id":"ref-for-acknowledged"},{"id":"ref-for-acknowledged\u2460"}],"title":"9. \nMember Submissions"}],"url":"#acknowledged"},
 "adequate-implementation": {"dfnID":"adequate-implementation","dfnText":"adequate implementation experience","external":false,"refSections":[{"refs":[{"id":"ref-for-adequate-implementation"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-adequate-implementation\u2460"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-adequate-implementation\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-adequate-implementation\u2462"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#adequate-implementation"},
 "adopted-draft": {"dfnID":"adopted-draft","dfnText":"Adopted Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-adopted-draft"}],"title":"4.3. \nContent of a Charter"}],"url":"#adopted-draft"},
@@ -6320,7 +6300,6 @@ <h3 class="no-num no-ref heading settled" id="informative"><span class="content"
 "#w3c-registry": {"displayText":"w3c registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c registry","type":"dfn","url":"#w3c-registry"},
 "https://www.w3.org/policies/patent-policy/#exclusion-opportunity": {"displayText":"Exclusion Opportunity","export":false,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"exclusion opportunity","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
 "https://www.w3.org/policies/patent-policy/#patent-advisory-group": {"displayText":"Patent Advisory Group","export":true,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"patent advisory group","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
-"https://www.w3.org/policies/process/#WGNote": {"displayText":"W3C Note","export":true,"for_":[],"level":"1","normative":true,"shortname":"w3c-process","spec":"w3c-process","status":"current","text":"w3c note","type":"dfn","url":"https://www.w3.org/policies/process/#WGNote"},
 };
 
 function mkRefHint(link, ref) {

From 66d45153890a1d8423004de16ae93030c4edf1ab Mon Sep 17 00:00:00 2001
From: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
Date: Wed, 23 Jul 2025 16:40:40 +0200
Subject: [PATCH 230/237] Fix typo: teaks -> tweaks (#1075)

---
 index.bs                  | 2 +-
 snapshots/2023-04.html    | 2 +-
 snapshots/2023-06-12.html | 2 +-
 snapshots/2025-05.html    | 2 +-
 snapshots/2025-06.html    | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/index.bs b/index.bs
index 9c338336..1955a06b 100644
--- a/index.bs
+++ b/index.bs
@@ -5647,7 +5647,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 	a <a href="https://github.com/w3c/process/compare/p2023_1...main">detailed log of all changes since then</a>
 	are available.
 
-	In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:
+	In addition to a number of editorial adjustments and minor tweaks, the following is a summary of the main differences:
 
 	<dl>
 		<dt id=changes-2025-tr>Changes to technical reports and their publication
diff --git a/snapshots/2023-04.html b/snapshots/2023-04.html
index e363f4b1..09958634 100644
--- a/snapshots/2023-04.html
+++ b/snapshots/2023-04.html
@@ -4800,7 +4800,7 @@ <h3 class="no-num heading settled" id="changes-2021"><span class="content"> Chan
 	as well as
 	a <a href="https://github.com/w3c/w3process/compare/p2021...main">detailed log of all changes since then</a> are available. </p>
     <p>In addition to a number of editorial adjustments
-	and minor teaks,
+	and minor tweaks,
 	the following is a summary of the main differences:</p>
     <h4 class="heading settled" id="dirfree-changes"><span class="content"> Changes related to the role of the Director</span><a class="self-link" href="#dirfree-changes"></a></h4>
     <ul>
diff --git a/snapshots/2023-06-12.html b/snapshots/2023-06-12.html
index a31ff787..42945755 100644
--- a/snapshots/2023-06-12.html
+++ b/snapshots/2023-06-12.html
@@ -4572,7 +4572,7 @@ <h3 class="no-num heading settled" id="changes-2021"><span class="content"> Chan
 	as well as
 	a <a href="https://github.com/w3c/w3process/compare/p2021...main">detailed log of all changes since then</a> are available. </p>
     <p>In addition to a number of editorial adjustments
-	and minor teaks,
+	and minor tweaks,
 	the following is a summary of the main differences:</p>
     <h4 class="heading settled" id="dirfree-changes"><span class="content"> Changes related to the role of the Director</span><a class="self-link" href="#dirfree-changes"></a></h4>
     <ul>
diff --git a/snapshots/2025-05.html b/snapshots/2025-05.html
index 1773a6c5..29eb4923 100644
--- a/snapshots/2025-05.html
+++ b/snapshots/2025-05.html
@@ -4959,7 +4959,7 @@ <h3 class="no-num heading settled" id="changes-2025"><span class="content"> Chan
 	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2Fsnapshots%2F2025-05">diff from Process 2023 to this latest version</a>,
 	as well as
 	a <a href="https://github.com/w3c/process/compare/p2023_1...2025-review-draft">detailed log of all changes since then</a> are available. </p>
-    <p>In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:</p>
+    <p>In addition to a number of editorial adjustments and minor tweaks, the following is a summary of the main differences:</p>
     <dl>
      <dt id="changes-2025-tr"><a class="self-link" href="#changes-2025-tr"></a>Changes to technical reports and their publication 
      <dd>
diff --git a/snapshots/2025-06.html b/snapshots/2025-06.html
index c6de3797..4c8ecdc5 100644
--- a/snapshots/2025-06.html
+++ b/snapshots/2025-06.html
@@ -4981,7 +4981,7 @@ <h3 class="no-num heading settled" id="changes-2025"><span class="content"> Chan
 	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2Fsnapshots%2F2025-05">diff from Process 2023 to this latest version</a>,
 	as well as
 	a <a href="https://github.com/w3c/process/compare/p2023_1...2025-ballot-draft">detailed log of all changes since then</a> are available. </p>
-    <p>In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:</p>
+    <p>In addition to a number of editorial adjustments and minor tweaks, the following is a summary of the main differences:</p>
     <dl>
      <dt id="changes-2025-tr"><a class="self-link" href="#changes-2025-tr"></a>Changes to technical reports and their publication 
      <dd>

From bc8775ebd483cf2b36ac2c078d4994bd15eb7c5f Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 23 Jul 2025 07:42:47 -0700
Subject: [PATCH 231/237] Editorial tweaks based on ac-review (#1074)

* Drop extraneous article

Caught during the AC review for approval of Process 2025

* fix stray reference to "the" member agreement

As discussed in #879, as templates for the member agreement evolve over
time, each member has their own agreement, and there isn't a singular
member agreement.

* Adjust word order for better readability
* Add missing comma
* Correct pluralization
* Disammbiguate pronoun
* Use clearer terminology
* Crosslink
* Improve syntax

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
---
 index.bs | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)

diff --git a/index.bs b/index.bs
index 1955a06b..54ba48cf 100644
--- a/index.bs
+++ b/index.bs
@@ -463,13 +463,12 @@ Expectations and Discipline</h5>
 	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,
+	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, or
-	(b) the membership agreement, or
-	(c) applicable laws,
-	occur.
+	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">
@@ -1442,7 +1441,7 @@ Requirements for All Chartered Groups</h4>
 	(also known as <dfn export>Team Contact</dfn>),
 	who acts as the interface between the [=Chair=],
 	group participants,
-	and the rest of the Team.
+	and the rest of the [=Team=].
 	
 	Note: The <a href="https://www.w3.org/guide/teamcontact/role">role of the Staff Contact</a> [[TEAM-CONTACT]]
 	is described in the <a href="https://www.w3.org/guide/">Art of Consensus</a> [[GUIDE]].
@@ -2036,7 +2035,7 @@ Minor Changes to Active Charters</h4>
 	is a major, not [=minor change|minor=], change.
 	The following are examples of [=minor changes=]:
 	the renaming or restructuring (e.g. splitting or combining) of existing in-scope deliverables,
-	the addition of new [[#note-track|Note track]] deliverables that help explain the group’s work
+	the addition of new [[#note-track|Note track]] deliverables that help explain the group’s work,
 	a change of [=Staff Contact=],
 	or a change of [=Chair=].
 	[=Minor changes=], other than a change of [=Staff Contact=],
@@ -2444,7 +2443,7 @@ Registering Formal Objections</h3>
 	A Call for Review to the Advisory Committee
 	<em class="rfc2119">must</em> identify any [=Formal Objections=]
 	related to that review.
-	This requirement is waived
+	These requirements are waived
 	if the [=Formal Objection=] is resolved to the satisfaction of the objector
 	before its <a href="#confidentiality-change">confidentiality is changed</a>.
 
@@ -2690,7 +2689,7 @@ Council Deliberations</h5>
 
 	<p id=fo-mitigations>
 	When [=overturning=] a decision,
-	it <em class=rfc2199>should</em> recommend a way forward.
+	the [=Council=] <em class=rfc2199>should</em> recommend a way forward.
 	If the overturned decision has already had consequences
 	pertaining to [=upheld=] aspects of the Formal Objection(s)
 	(e.g., if the objection concerns material already in a published document)
@@ -5131,7 +5130,7 @@ Confidentiality Levels</h3>
 
 		<li>
 			<em class="rfc2119">must not</em> release this information to the general public or press,
-			nor beyond the proper level of access.
+			nor beyond the designated level of access.
 	</ul>
 
 	The [=Team=] <em class="rfc2119">must</em> provide mechanisms
@@ -5707,7 +5706,7 @@ Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 Nove
 					and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>).
 
 				<li>
-					Consolidate and harmonize into a <a href="#no-group-maintenance">one section</a>
+					Consolidate and harmonize into <a href="#no-group-maintenance">one section</a>
 					the various parts of the Process
 					that described whether and how the Team can maintain technical reports
 					that no longer have a Group chartered to maintain them.

From d4a28c0142a70117c5d6c01497c582663e33dfcd Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 23 Jul 2025 07:48:11 -0700
Subject: [PATCH 232/237] Editorial reorg of text defining REC track statuses
 (#1079)

* Switched the definition of REC track to point to the full list of
maturity stages, rather than the summarized version of it.
* Move a few paragraphs around, for ease of reading
* Use more open-ended phrasing for the sentence introducing the summarized list of statuses


Co-authored-by: fantasai <fantasai.bugs@inkedblade.net>
Co-authored-by: Jeffrey Yasskin <jyasskin@gmail.com>
Co-authored-by: Ian Jacobs <ij@w3.org>
---
 index.bs | 41 ++++++++++++++++++++---------------------
 1 file changed, 20 insertions(+), 21 deletions(-)

diff --git a/index.bs b/index.bs
index 54ba48cf..80c954d4 100644
--- a/index.bs
+++ b/index.bs
@@ -3458,7 +3458,7 @@ The W3C Recommendation Track</h3>
 	and if there is support from its Membership,
 	W3C publishes it as a <a href="#RecsW3C">Recommendation</a>.
 
-	In summary, the <dfn lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track">W3C Recommendation Track</dfn> consists of:
+	In summary, the main steps of <dfn lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track">W3C Recommendation Track</dfn> are:
 
 	<ol>
 		<li>Publication of the [=First Public Working Draft=].
@@ -3467,9 +3467,6 @@ The W3C Recommendation Track</h3>
 		<li>Publication as a [=W3C Recommendation=].
 	</ol>
 
-	A <dfn export lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document">W3C Recommendation Track document</dfn>
-	is any document whose current status is one of the four in the numbered list above.
-
 	<figure>
 		<pre class=include-raw>
 			path: basic-rec-track.svg
@@ -3477,23 +3474,25 @@ The W3C Recommendation Track</h3>
 		<figcaption>Non-Normative Summary of the [=Recommendation Track=]</figcaption>
 	</figure>
 
-	This Process defines certain [=Recommendation Track=] publications as <dfn>Patent Review Drafts</dfn>.
-	Under the 2004 Patent Policy (and its 2017 update) [[!PATENT-POLICY-2004]],
-	these correspond to “Last Call Working Draft” in the Patent Policy;
-	Starting from the 2020 Patent Policy [[!PATENT-POLICY-2020]],
-	these correspond to “Patent Review Draft” in the Patent Policy [[!PATENT-POLICY]].
-
-	W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.
-
+	Only sufficiently technically mature work should be advanced.
 	As described in [[#transition-reqs]],
 	the [=Team=] will decline a request to advance in maturity stage
 	and return the specification to a [=Working Group=] for further work
 	if it determines that the requirements for advancement
 	have not been met.
 
+	Note: Should faster advancement to meet scheduling considerations be desired,
+	this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring
+	less stable features to other technical reports.
+
+	W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.
+
 <h4 id="maturity-stages">
 Maturity Stages on the Recommendation Track</h4>
 
+	A <dfn export lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document">W3C Recommendation Track document</dfn>
+	is any document whose current status is one of those described in this section.
+
 	<dl>
 		<dt>
 			<dfn id="RecsWD" export lt="W3C Working Draft | Working Draft | WD">Working Draft</dfn> (<abbr>WD</abbr>)
@@ -3689,11 +3688,16 @@ Maturity Stages on the Recommendation Track</h4>
 
 	</dl>
 
-	Only sufficiently technically mature work should be advanced.
+	This Process defines certain [=Recommendation Track=] publications as <dfn>Patent Review Drafts</dfn>.
+	Under the 2004 Patent Policy (and its 2017 update) [[!PATENT-POLICY-2004]],
+	these correspond to “Last Call Working Draft” in the Patent Policy;
+	Starting from the 2020 Patent Policy [[!PATENT-POLICY-2020]],
+	these correspond to “Patent Review Draft” in the Patent Policy [[!PATENT-POLICY]].
 
-	Note: Should faster advancement to meet scheduling considerations be desired,
-	this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring
-	less stable features to other technical reports.
+	[=Working Groups=] and [=Interest Groups=] <em class="rfc2119">may</em> make available [=Editor's drafts=].
+	<dfn export lt="Editor's Draft | Editor Draft | ED">Editor's drafts</dfn> (<abbr>ED</abbr>) have no official standing whatsoever,
+	and do not necessarily imply consensus of a [=Working Group=] or [=Interest Group=],
+	nor are their contents endorsed in any way by W3C.
 
 	When publishing an updated version of an existing [=Candidate Recommendation=] or [=Recommendation=],
 	technical reports are expected to meet the same maturity criteria as when they are first published under that status.
@@ -3703,11 +3707,6 @@ Maturity Stages on the Recommendation Track</h4>
 	it is also permissible to publish an updated [=CR=] or [=REC=] following the usual process,
 	even if only some of these flaws have been satisfactorily addressed.
 
-	[=Working Groups=] and [=Interest Groups=] <em class="rfc2119">may</em> make available [=Editor's drafts=].
-	<dfn export lt="Editor's Draft | Editor Draft | ED">Editor's drafts</dfn> (<abbr>ED</abbr>) have no official standing whatsoever,
-	and do not necessarily imply consensus of a [=Working Group=] or [=Interest Group=],
-	nor are their contents endorsed in any way by W3C.
-
 <h4 id="implementation-experience">
 Implementation Experience</h4>
 

From 99e4a5f0e07b40a3cf8c9b880b05a374278efe6e Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 23 Jul 2025 17:17:43 +0200
Subject: [PATCH 233/237] Create Snapshot for the 2025 version of the Process

---
 snapshots/2025-07-31.html | 6504 +++++++++++++++++++++++++++++++++++++
 1 file changed, 6504 insertions(+)
 create mode 100644 snapshots/2025-07-31.html

diff --git a/snapshots/2025-07-31.html b/snapshots/2025-07-31.html
new file mode 100644
index 00000000..8aaa0705
--- /dev/null
+++ b/snapshots/2025-07-31.html
@@ -0,0 +1,6504 @@
+<!doctype html><html lang="en">
+ <head>
+  <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+  <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
+  <title>W3C Process Document</title>
+  <meta content="CG-DRAFT" name="w3c-status">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/cg-draft" rel="stylesheet">
+  <meta content="Bikeshed version b25686b9f, updated Fri Mar 14 14:15:20 2025 -0700" name="generator">
+  <link href="https://www.w3.org/policies/process/" rel="canonical">
+  <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
+  <meta content="d4a28c0142a70117c5d6c01497c582663e33dfcd" name="revision">
+  <meta content="dark light" name="color-scheme">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
+<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>
+<style>/* Boilerplate: style-autolinks */
+.css.css, .property.property, .descriptor.descriptor {
+    color: var(--a-normal-text);
+    font-size: inherit;
+    font-family: inherit;
+}
+.css::before, .property::before, .descriptor::before {
+    content: "‘";
+}
+.css::after, .property::after, .descriptor::after {
+    content: "’";
+}
+.property, .descriptor {
+    /* Don't wrap property and descriptor names */
+    white-space: nowrap;
+}
+.type { /* CSS value <type> */
+    font-style: italic;
+}
+pre .property::before, pre .property::after {
+    content: "";
+}
+[data-link-type="property"]::before,
+[data-link-type="propdesc"]::before,
+[data-link-type="descriptor"]::before,
+[data-link-type="value"]::before,
+[data-link-type="function"]::before,
+[data-link-type="at-rule"]::before,
+[data-link-type="selector"]::before,
+[data-link-type="maybe"]::before {
+    content: "‘";
+}
+[data-link-type="property"]::after,
+[data-link-type="propdesc"]::after,
+[data-link-type="descriptor"]::after,
+[data-link-type="value"]::after,
+[data-link-type="function"]::after,
+[data-link-type="at-rule"]::after,
+[data-link-type="selector"]::after,
+[data-link-type="maybe"]::after {
+    content: "’";
+}
+
+[data-link-type].production::before,
+[data-link-type].production::after,
+.prod [data-link-type]::before,
+.prod [data-link-type]::after {
+    content: "";
+}
+
+[data-link-type=element],
+[data-link-type=element-attr] {
+    font-family: Menlo, Consolas, "DejaVu Sans Mono", monospace;
+    font-size: .9em;
+}
+[data-link-type=element]::before { content: "<" }
+[data-link-type=element]::after  { content: ">" }
+
+[data-link-type=biblio] {
+    white-space: pre;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --selflink-text: black;
+        --selflink-bg: silver;
+        --selflink-hover-text: white;
+    }
+}
+</style>
+<style>/* Boilerplate: style-colors */
+/* Any --*-text not paired with a --*-bg is assumed to have a transparent bg */
+:root {
+    color-scheme: light dark;
+
+    --text: black;
+    --bg: white;
+
+    --unofficial-watermark: url(https://www.w3.org/StyleSheets/TR/2016/logos/UD-watermark);
+
+    --logo-bg: #1a5e9a;
+    --logo-active-bg: #c00;
+    --logo-text: white;
+
+    --tocnav-normal-text: #707070;
+    --tocnav-normal-bg: var(--bg);
+    --tocnav-hover-text: var(--tocnav-normal-text);
+    --tocnav-hover-bg: #f8f8f8;
+    --tocnav-active-text: #c00;
+    --tocnav-active-bg: var(--tocnav-normal-bg);
+
+    --tocsidebar-text: var(--text);
+    --tocsidebar-bg: #f7f8f9;
+    --tocsidebar-shadow: rgba(0,0,0,.1);
+    --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+    --toclink-text: var(--text);
+    --toclink-underline: #3980b5;
+    --toclink-visited-text: var(--toclink-text);
+    --toclink-visited-underline: #054572;
+
+    --heading-text: #005a9c;
+
+    --hr-text: var(--text);
+
+    --algo-border: #def;
+
+    --del-text: red;
+    --del-bg: transparent;
+    --ins-text: #080;
+    --ins-bg: transparent;
+
+    --a-normal-text: #034575;
+    --a-normal-underline: #bbb;
+    --a-visited-text: var(--a-normal-text);
+    --a-visited-underline: #707070;
+    --a-hover-bg: rgba(75%, 75%, 75%, .25);
+    --a-active-text: #c00;
+    --a-active-underline: #c00;
+
+    --blockquote-border: silver;
+    --blockquote-bg: transparent;
+    --blockquote-text: currentcolor;
+
+    --issue-border: #e05252;
+    --issue-bg: #fbe9e9;
+    --issue-text: var(--text);
+    --issueheading-text: #831616;
+
+    --example-border: #e0cb52;
+    --example-bg: #fcfaee;
+    --example-text: var(--text);
+    --exampleheading-text: #574b0f;
+
+    --note-border: #52e052;
+    --note-bg: #e9fbe9;
+    --note-text: var(--text);
+    --noteheading-text: hsl(120, 70%, 30%);
+    --notesummary-underline: silver;
+
+    --assertion-border: #aaa;
+    --assertion-bg: #eee;
+    --assertion-text: black;
+
+    --advisement-border: orange;
+    --advisement-bg: #fec;
+    --advisement-text: var(--text);
+    --advisementheading-text: #b35f00;
+
+    --warning-border: red;
+    --warning-bg: hsla(40,100%,50%,0.95);
+    --warning-text: var(--text);
+
+    --amendment-border: #330099;
+    --amendment-bg: #F5F0FF;
+    --amendment-text: var(--text);
+    --amendmentheading-text: #220066;
+
+    --def-border: #8ccbf2;
+    --def-bg: #def;
+    --def-text: var(--text);
+    --defrow-border: #bbd7e9;
+
+    --datacell-border: silver;
+
+    --indexinfo-text: #707070;
+
+    --indextable-hover-text: black;
+    --indextable-hover-bg: #f7f8f9;
+
+    --outdatedspec-bg: rgba(0, 0, 0, .5);
+    --outdatedspec-text: black;
+    --outdated-bg: maroon;
+    --outdated-text: white;
+    --outdated-shadow: red;
+
+    --editedrec-bg: darkorange;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --text: #ddd;
+        --bg: black;
+
+        --unofficial-watermark: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='400' height='400'%3E%3Cg fill='%23100808' transform='translate(200 200) rotate(-45) translate(-200 -200)' stroke='%23100808' stroke-width='3'%3E%3Ctext x='50%25' y='220' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EUNOFFICIAL%3C/text%3E%3Ctext x='50%25' y='305' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EDRAFT%3C/text%3E%3C/g%3E%3C/svg%3E");
+
+        --logo-bg: #1a5e9a;
+        --logo-active-bg: #c00;
+        --logo-text: white;
+
+        --tocnav-normal-text: #999;
+        --tocnav-normal-bg: var(--bg);
+        --tocnav-hover-text: var(--tocnav-normal-text);
+        --tocnav-hover-bg: #080808;
+        --tocnav-active-text: #f44;
+        --tocnav-active-bg: var(--tocnav-normal-bg);
+
+        --tocsidebar-text: var(--text);
+        --tocsidebar-bg: #080808;
+        --tocsidebar-shadow: rgba(255,255,255,.1);
+        --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+        --toclink-text: var(--text);
+        --toclink-underline: #6af;
+        --toclink-visited-text: var(--toclink-text);
+        --toclink-visited-underline: #054572;
+
+        --heading-text: #8af;
+
+        --hr-text: var(--text);
+
+        --algo-border: #456;
+
+        --del-text: #f44;
+        --del-bg: transparent;
+        --ins-text: #4a4;
+        --ins-bg: transparent;
+
+        --a-normal-text: #6af;
+        --a-normal-underline: #555;
+        --a-visited-text: var(--a-normal-text);
+        --a-visited-underline: var(--a-normal-underline);
+        --a-hover-bg: rgba(25%, 25%, 25%, .2);
+        --a-active-text: #f44;
+        --a-active-underline: var(--a-active-text);
+
+        --borderedblock-bg: rgba(255, 255, 255, .05);
+
+        --blockquote-border: silver;
+        --blockquote-bg: var(--borderedblock-bg);
+        --blockquote-text: currentcolor;
+
+        --issue-border: #e05252;
+        --issue-bg: var(--borderedblock-bg);
+        --issue-text: var(--text);
+        --issueheading-text: hsl(0deg, 70%, 70%);
+
+        --example-border: hsl(50deg, 90%, 60%);
+        --example-bg: var(--borderedblock-bg);
+        --example-text: var(--text);
+        --exampleheading-text: hsl(50deg, 70%, 70%);
+
+        --note-border: hsl(120deg, 100%, 35%);
+        --note-bg: var(--borderedblock-bg);
+        --note-text: var(--text);
+        --noteheading-text: hsl(120, 70%, 70%);
+        --notesummary-underline: silver;
+
+        --assertion-border: #444;
+        --assertion-bg: var(--borderedblock-bg);
+        --assertion-text: var(--text);
+
+        --advisement-border: orange;
+        --advisement-bg: #222218;
+        --advisement-text: var(--text);
+        --advisementheading-text: #f84;
+
+        --warning-border: red;
+        --warning-bg: hsla(40,100%,20%,0.95);
+        --warning-text: var(--text);
+
+        --amendment-border: #330099;
+        --amendment-bg: #080010;
+        --amendment-text: var(--text);
+        --amendmentheading-text: #cc00ff;
+
+        --def-border: #8ccbf2;
+        --def-bg: #080818;
+        --def-text: var(--text);
+        --defrow-border: #136;
+
+        --datacell-border: silver;
+
+        --indexinfo-text: #aaa;
+
+        --indextable-hover-text: var(--text);
+        --indextable-hover-bg: #181818;
+
+        --outdatedspec-bg: rgba(255, 255, 255, .5);
+        --outdatedspec-text: black;
+        --outdated-bg: maroon;
+        --outdated-text: white;
+        --outdated-shadow: red;
+
+        --editedrec-bg: darkorange;
+    }
+    /* In case a transparent-bg image doesn't expect to be on a dark bg,
+       which is quite common in practice... */
+    img { background: white; }
+}
+</style>
+<style>/* Boilerplate: style-counters */
+body {
+    counter-reset: example figure issue;
+}
+.issue {
+    counter-increment: issue;
+}
+.issue:not(.no-marker)::before {
+    content: "Issue " counter(issue);
+}
+
+.example {
+    counter-increment: example;
+}
+.example:not(.no-marker)::before {
+    content: "Example " counter(example);
+}
+.invalid.example:not(.no-marker)::before,
+.illegal.example:not(.no-marker)::before {
+    content: "Invalid Example" counter(example);
+}
+
+figcaption {
+    counter-increment: figure;
+}
+figcaption:not(.no-marker)::before {
+    content: "Figure " counter(figure) " ";
+}
+</style>
+<style>/* Boilerplate: style-dfn-panel */
+:root {
+    --dfnpanel-bg: #ddd;
+    --dfnpanel-text: var(--text);
+    --dfnpanel-target-bg: #ffc;
+    --dfnpanel-target-outline: orange;
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --dfnpanel-bg: #222;
+        --dfnpanel-text: var(--text);
+        --dfnpanel-target-bg: #333;
+        --dfnpanel-target-outline: silver;
+    }
+}
+.dfn-panel {
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.75em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--dfnpanel-bg);
+    color: var(--dfnpanel-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+.dfn-panel:not(.on) { display: none; }
+.dfn-panel * { margin: 0; padding: 0; text-indent: 0; }
+.dfn-panel > b { display: block; }
+.dfn-panel a { color: var(--dfnpanel-text); }
+.dfn-panel a:not(:hover) { text-decoration: none !important; border-bottom: none !important; }
+.dfn-panel a:focus {
+    outline: 5px auto Highlight;
+    outline: 5px auto -webkit-focus-ring-color;
+}
+.dfn-panel > b + b { margin-top: 0.25em; }
+.dfn-panel ul { padding: 0 0 0 1em; list-style: none; }
+.dfn-panel li a {
+    max-width: calc(300px - 1.5em - 1em);
+    overflow: hidden;
+    text-overflow: ellipsis;
+}
+
+.dfn-panel.activated {
+    display: inline-block;
+    position: fixed;
+    left: 8px;
+    bottom: 2em;
+    margin: 0 auto;
+    max-width: calc(100vw - 1.5em - .4em - .5em);
+    max-height: 30vh;
+    transition: left 1s ease-out, bottom 1s ease-out;
+}
+
+.dfn-panel .link-item:hover {
+    text-decoration: underline;
+}
+.dfn-panel .link-item .copy-icon {
+    opacity: 0;
+}
+.dfn-panel .link-item:hover .copy-icon,
+.dfn-panel .link-item .copy-icon:focus {
+    opacity: 1;
+}
+
+.dfn-panel .copy-icon {
+    display: inline-block;
+    margin-right: 0.5em;
+    width: 0.85em;
+    height: 1em;
+    border-radius: 3px;
+    background-color: #ccc;
+    cursor: pointer;
+}
+
+.dfn-panel .copy-icon .icon {
+    width: 100%;
+    height: 100%;
+    background-color: #fff;
+    display: flex;
+    justify-content: center;
+    align-items: center;
+    position: relative;
+}
+
+.dfn-panel .copy-icon .icon::before {
+    content: "";
+    position: absolute;
+    top: 0;
+    left: 0;
+    width: 100%;
+    height: 100%;
+    border: 1px solid black;
+    background-color: #ccc;
+    opacity: 0.25;
+    transform: translate(3px, -3px);
+}
+
+.dfn-panel .copy-icon:active .icon::before {
+    opacity: 1;
+}
+
+.dfn-paneled[role="button"] { cursor: help; }
+
+.highlighted {
+    animation: target-fade 3s;
+}
+
+@keyframes target-fade {
+    from {
+        background-color: var(--dfnpanel-target-bg);
+        outline: 5px solid var(--dfnpanel-target-outline);
+    }
+    to {
+        color: var(--a-normal-text);
+        background-color: transparent;
+        outline: transparent;
+    }
+}
+</style>
+<style>/* Boilerplate: style-issues */
+a[href].issue-return {
+    float: right;
+    float: inline-end;
+    color: var(--issueheading-text);
+    font-weight: bold;
+    text-decoration: none;
+}
+</style>
+<style>/* Boilerplate: style-md-lists */
+/* This is a weird hack for me not yet following the commonmark spec
+   regarding paragraph and lists. */
+[data-md] > :first-child {
+    margin-top: 0;
+}
+[data-md] > :last-child {
+    margin-bottom: 0;
+}
+</style>
+<style>/* Boilerplate: style-ref-hints */
+:root {
+    --ref-hint-bg: #ddd;
+    --ref-hint-text: var(--text);
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --ref-hint-bg: #222;
+        --ref-hint-text: var(--text);
+    }
+}
+
+.ref-hint {
+    display: inline-block;
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.5em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--ref-hint-bg);
+    color: var(--ref-hint-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+
+.ref-hint * { margin: 0; padding: 0; text-indent: 0; }
+
+.ref-hint ul { padding: 0 0 0 1em; list-style: none; }
+</style>
+<style>/* Boilerplate: style-selflinks */
+:root {
+    --selflink-text: white;
+    --selflink-bg: gray;
+    --selflink-hover-text: black;
+}
+.heading, .issue, .note, .example, li, dt {
+    position: relative;
+}
+a.self-link {
+    position: absolute;
+    top: 0;
+    left: calc(-1 * (3.5rem - 26px));
+    width: calc(3.5rem - 26px);
+    height: 2em;
+    text-align: center;
+    border: none;
+    transition: opacity .2s;
+    opacity: .5;
+}
+a.self-link:hover {
+    opacity: 1;
+}
+.heading > a.self-link {
+    font-size: 83%;
+}
+.example > a.self-link,
+.note > a.self-link,
+.issue > a.self-link {
+    /* These blocks are overflow:auto, so positioning outside
+       doesn't work. */
+    left: auto;
+    right: 0;
+}
+li > a.self-link {
+    left: calc(-1 * (3.5rem - 26px) - 2em);
+}
+dfn > a.self-link {
+    top: auto;
+    left: auto;
+    opacity: 0;
+    width: 1.5em;
+    height: 1.5em;
+    background: var(--selflink-bg);
+    color: var(--selflink-text);
+    font-style: normal;
+    transition: opacity .2s, background-color .2s, color .2s;
+}
+dfn:hover > a.self-link {
+    opacity: 1;
+}
+dfn > a.self-link:hover {
+    color: var(--selflink-hover-text);
+}
+
+a.self-link::before            { content: "¶"; }
+.heading > a.self-link::before { content: "§"; }
+dfn > a.self-link::before      { content: "#"; }
+</style>
+ <body class="h-entry">
+  <div class="head">
+   <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
+   <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types/#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2025-07-31">31 July 2025</time></p>
+   <details open>
+    <summary>More details about this document</summary>
+    <div data-fill-with="spec-metadata">
+     <dl>
+      <dt>This version:
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/snapshots/2025-06">https://www.w3.org/policies/process/drafts/snapshots/2025-07-31</a>
+      <dt>Editor’s Draft:
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/</a>
+      <dt>Latest published version:
+      <dd><a href="https://www.w3.org/policies/process/">https://www.w3.org/policies/process/</a>
+      <dt>Previous Versions:
+      <dd><a href="https://www.w3.org/policies/process/20231103/" rel="prev">https://www.w3.org/policies/process/20231103/</a>
+      <dt>Feedback:
+      <dd><a href="https://github.com/w3c/process/issues/">Github (preferred)</a>
+      <dd><a href="https://lists.w3.org/Archives/Public/public-w3process/">Public mailing list</a>
+      <dd><a href="https://lists.w3.org/Archives/Member/process-issues">Member-only mailing list</a>
+      <dt class="editor">Editors:
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://fantasai.inkedblade.net/contact">Elika J. Etemad / fantasai</a> (<span class="p-org org">Apple</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://florian.rivoal.net/">Florian Rivoal</a> (<span class="p-org org">Invited Expert</span>)
+      <dt class="editor">Former Editors:
+      <dd class="editor p-author h-card vcard"><span class="p-name fn">Natasha Rooney</span> (<span class="p-org org">Invited Expert</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://yandex.com">Charles McCathie Nevile</a> (<span class="p-org org">Yandex</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://www.w3.org/">Ian Jacobs</a> (<span class="p-org org">W3C</span>)
+     </dl>
+    </div>
+   </details>
+   <div data-fill-with="warning"></div>
+   <p class="copyright" data-fill-with="copyright"><a href="https://www.w3.org/policies/#copyright">Copyright</a> © 2025 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/policies/#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/policies/#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/copyright/software-license/" rel="license" title="W3C Software and Document License">permissive document license</a> rules apply. </p>
+   <hr title="Separator for header">
+  </div>
+  <div class="p-summary" data-fill-with="abstract">
+   <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></h2>
+   <p>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.</p>
+   <p>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>.</p>
+  </div>
+  <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content">Status of this document</span></h2>
+  <div data-fill-with="status">
+   <p> W3C, including all existing chartered groups,
+	follows the <a href="https://www.w3.org/policies/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
+	working within the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a> (which anyone can join).
+	This is the 31 July 2025 Draft Community Group Report for the proposed next version of the W3C Process Document. </p>
+   <p>This document,
+having completed Advisory Committee Review,
+is proposed to be the next version of the W3C Process
+after the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
+How it is adopted is detailed in <a href="https://www.w3.org/policies/process/#GAProcess">Section 11 Process Changes</a>.</p>
+   <p> A <a href="#changes">history of substantial changes</a> from previous versions of the Process Document is provided. </p>
+  </div>
+  <div data-fill-with="at-risk"></div>
+  <nav data-fill-with="table-of-contents" id="toc">
+   <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
+   <ol class="toc" role="directory">
+    <li><a href="#Intro"><span class="secno">1</span> <span class="content"> Introduction</span></a>
+    <li>
+     <a href="#Organization"><span class="secno">2</span> <span class="content"> Members and the Team</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Members"><span class="secno">2.1</span> <span class="content"> Members</span></a>
+       <ol class="toc">
+        <li><a href="#MemberBenefits"><span class="secno">2.1.1</span> <span class="content"> Rights of Members</span></a>
+        <li>
+         <a href="#RelatedAndAssociatedMembers"><span class="secno">2.1.2</span> <span class="content"> Member Associations and Related Members</span></a>
+         <ol class="toc">
+          <li><a href="#MemberAssoc"><span class="secno">2.1.2.1</span> <span class="content"> Membership Associations</span></a>
+          <li><a href="#MemberRelated"><span class="secno">2.1.2.2</span> <span class="content"> Related Members</span></a>
+         </ol>
+        <li><a href="#standing"><span class="secno">2.1.3</span> <span class="content"> Good Standing</span></a>
+       </ol>
+      <li><a href="#Team"><span class="secno">2.2</span> <span class="content"> The W3C Team</span></a>
+     </ol>
+    <li>
+     <a href="#groups"><span class="secno">3</span> <span class="content"> Groups and Participation</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Policies"><span class="secno">3.1</span> <span class="content"> Policies for Participation in W3C Groups</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#ParticipationCriteria"><span class="secno">3.1.1</span> <span class="content"> Individual Participation Criteria</span></a>
+         <ol class="toc">
+          <li><a href="#discipline"><span class="secno">3.1.1.1</span> <span class="content"> Expectations and Discipline</span></a>
+          <li><a href="#coi"><span class="secno">3.1.1.2</span> <span class="content"> Conflict of Interest Policy</span></a>
+          <li><a href="#member-rep"><span class="secno">3.1.1.3</span> <span class="content"> Individuals Representing a Member Organization</span></a>
+         </ol>
+        <li>
+         <a href="#GeneralMeetings"><span class="secno">3.1.2</span> <span class="content"> Meetings</span></a>
+         <ol class="toc">
+          <li><a href="#meeting-schedules"><span class="secno">3.1.2.1</span> <span class="content"> Meeting Scheduling and Announcements</span></a>
+          <li><a href="#meeting-minutes"><span class="secno">3.1.2.2</span> <span class="content"> Meeting Minutes</span></a>
+          <li><a href="#meeting-recording"><span class="secno">3.1.2.3</span> <span class="content"> Meeting Recordings and Transcripts</span></a>
+         </ol>
+        <li><a href="#tooling"><span class="secno">3.1.3</span> <span class="content"> Tooling and Archiving for Discussions and Publications</span></a>
+        <li><a href="#resignation"><span class="secno">3.1.4</span> <span class="content"> Resignation from a Group</span></a>
+       </ol>
+      <li>
+       <a href="#AC"><span class="secno">3.2</span> <span class="content"> The Advisory Committee (AC)</span></a>
+       <ol class="toc">
+        <li><a href="#ac-role"><span class="secno">3.2.1</span> <span class="content"> Role of the Advisory Committee</span></a>
+        <li><a href="#ac-participation"><span class="secno">3.2.2</span> <span class="content"> Participation in the Advisory Committee</span></a>
+        <li><a href="#ACCommunication"><span class="secno">3.2.3</span> <span class="content"> Advisory Committee Mailing Lists</span></a>
+        <li><a href="#ACMeetings"><span class="secno">3.2.4</span> <span class="content"> Advisory Committee Meetings</span></a>
+       </ol>
+      <li>
+       <a href="#elected-groups"><span class="secno">3.3</span> <span class="content"> Elected Groups: The AB and the TAG</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#AB"><span class="secno">3.3.1</span> <span class="content"> Advisory Board (AB)</span></a>
+         <ol class="toc">
+          <li><a href="#ab-role"><span class="secno">3.3.1.1</span> <span class="content"> Role of the Advisory Board</span></a>
+          <li><a href="#ABParticipation"><span class="secno">3.3.1.2</span> <span class="content"> Composition of the Advisory Board</span></a>
+          <li><a href="#ab-comm"><span class="secno">3.3.1.3</span> <span class="content"> Communications of the Advisory Board</span></a>
+          <li><a href="#ab-bod-liaison"><span class="secno">3.3.1.4</span> <span class="content"> Liaisons between the Advisory Board and the Board of Directors</span></a>
+         </ol>
+        <li>
+         <a href="#TAG"><span class="secno">3.3.2</span> <span class="content"> Technical Architecture Group (TAG)</span></a>
+         <ol class="toc">
+          <li><a href="#tag-role"><span class="secno">3.3.2.1</span> <span class="content"> Role of the Technical Architecture Group</span></a>
+          <li><a href="#tag-participation"><span class="secno">3.3.2.2</span> <span class="content"> Composition of the Technical Architecture Group</span></a>
+          <li><a href="#tag-comm"><span class="secno">3.3.2.3</span> <span class="content"> Communications of the Technical Architecture Group</span></a>
+         </ol>
+        <li>
+         <a href="#AB-TAG-participation"><span class="secno">3.3.3</span> <span class="content"> Participation in Elected Groups</span></a>
+         <ol class="toc">
+          <li><a href="#elected-expectations"><span class="secno">3.3.3.1</span> <span class="content"> Expectations for Elected Groups Participants</span></a>
+          <li><a href="#AB-TAG-constraints"><span class="secno">3.3.3.2</span> <span class="content"> Elected Groups Participation Constraints</span></a>
+          <li><a href="#AB-TAG-elections"><span class="secno">3.3.3.3</span> <span class="content"> Advisory Board and Technical Architecture Group Elections</span></a>
+          <li><a href="#TAG-appointments"><span class="secno">3.3.3.4</span> <span class="content"> Technical Architecture Group Appointments</span></a>
+          <li><a href="#random"><span class="secno">3.3.3.5</span> <span class="content"> Verifiable Random Selection Procedure</span></a>
+          <li><a href="#AB-TAG-vacated"><span class="secno">3.3.3.6</span> <span class="content"> Elected Groups Vacated Seats</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#GAGeneral"><span class="secno">3.4</span> <span class="content"> Chartered Groups: Working Groups and Interest Groups</span></a>
+       <ol class="toc">
+        <li><a href="#ReqsAllGroups"><span class="secno">3.4.1</span> <span class="content"> Requirements for All Chartered Groups</span></a>
+        <li><a href="#group-participation"><span class="secno">3.4.2</span> <span class="content"> Participation in Chartered Groups</span></a>
+        <li>
+         <a href="#chartered-group-participants"><span class="secno">3.4.3</span> <span class="content"> Types of Participants in Chartered Groups</span></a>
+         <ol class="toc">
+          <li><a href="#member-rep-wg"><span class="secno">3.4.3.1</span> <span class="content"> Member Representative in a Working Group</span></a>
+          <li><a href="#member-rep-ig"><span class="secno">3.4.3.2</span> <span class="content"> Member Representative in an Interest Group</span></a>
+          <li><a href="#invited-expert-wg"><span class="secno">3.4.3.3</span> <span class="content"> Invited Expert in a Working Group</span></a>
+          <li><a href="#invited-expert-ig"><span class="secno">3.4.3.4</span> <span class="content"> Invited Expert in an Interest Group</span></a>
+          <li><a href="#team-rep-wg"><span class="secno">3.4.3.5</span> <span class="content"> Team Representative in a Working Group</span></a>
+          <li><a href="#team-rep-ig"><span class="secno">3.4.3.6</span> <span class="content"> Team Representative in an Interest Group</span></a>
+         </ol>
+       </ol>
+     </ol>
+    <li>
+     <a href="#group-lifecycle"><span class="secno">4</span> <span class="content"> Lifecycle of Chartered Groups</span></a>
+     <ol class="toc">
+      <li><a href="#charter-initiation"><span class="secno">4.1</span> <span class="content"> Initiating Charter Refinement</span></a>
+      <li><a href="#charter-development"><span class="secno">4.2</span> <span class="content"> Charter Refinement</span></a>
+      <li><a href="#WGCharter"><span class="secno">4.3</span> <span class="content"> Content of a Charter</span></a>
+      <li>
+       <a href="#CharterReview"><span class="secno">4.4</span> <span class="content"> Charter Review and Approval</span></a>
+       <ol class="toc">
+        <li><a href="#charter-major-changes"><span class="secno">4.4.1</span> <span class="content"> New Charters and Major Changes</span></a>
+        <li><a href="#charter-minor-changes"><span class="secno">4.4.2</span> <span class="content"> Minor Changes to Active Charters</span></a>
+       </ol>
+      <li><a href="#cfp"><span class="secno">4.5</span> <span class="content"> Call for Participation in a Chartered Group</span></a>
+      <li><a href="#charter-extension"><span class="secno">4.6</span> <span class="content"> Charter Extension</span></a>
+      <li><a href="#GeneralTermination"><span class="secno">4.7</span> <span class="content"> Chartered Group Closure</span></a>
+     </ol>
+    <li>
+     <a href="#decisions"><span class="secno">5</span> <span class="content"> Decisions</span></a>
+     <ol class="toc">
+      <li><a href="#decision-types"><span class="secno">5.1</span> <span class="content"> Types of Decisions</span></a>
+      <li>
+       <a href="#consensus-building"><span class="secno">5.2</span> <span class="content"> Consensus Building</span></a>
+       <ol class="toc">
+        <li><a href="#Consensus"><span class="secno">5.2.1</span> <span class="content"> Consensus</span></a>
+        <li><a href="#managing-dissent"><span class="secno">5.2.2</span> <span class="content"> Managing Dissent</span></a>
+        <li><a href="#Votes"><span class="secno">5.2.3</span> <span class="content"> Deciding by Vote</span></a>
+       </ol>
+      <li><a href="#formal-address"><span class="secno">5.3</span> <span class="content"> Formally Addressing an Issue</span></a>
+      <li><a href="#WGChairReopen"><span class="secno">5.4</span> <span class="content"> Reopening a Decision When Presented With New Information</span></a>
+      <li><a href="#registering-objections"><span class="secno">5.5</span> <span class="content"> Registering Formal Objections</span></a>
+      <li>
+       <a href="#addressing-fo"><span class="secno">5.6</span> <span class="content"> Addressing Formal Objections</span></a>
+       <ol class="toc">
+        <li><a href="#team-fo-mediation"><span class="secno">5.6.1</span> <span class="content"> Investigation and Mediation by the Team</span></a>
+        <li>
+         <a href="#council"><span class="secno">5.6.2</span> <span class="content"> W3C Council</span></a>
+         <ol class="toc">
+          <li><a href="#council-composition"><span class="secno">5.6.2.1</span> <span class="content"> Council Composition</span></a>
+          <li><a href="#council-delegation"><span class="secno">5.6.2.2</span> <span class="content"> Extraordinary Delegation</span></a>
+          <li><a href="#council-participation"><span class="secno">5.6.2.3</span> <span class="content"> Council Participation, Dismissal, and Renunciation</span></a>
+          <li><a href="#council-short-circuit"><span class="secno">5.6.2.4</span> <span class="content"> Short Circuit</span></a>
+          <li><a href="#council-chairing"><span class="secno">5.6.2.5</span> <span class="content"> Council Chairing</span></a>
+          <li><a href="#council-convention"><span class="secno">5.6.2.6</span> <span class="content"> Convening the Council</span></a>
+          <li><a href="#council-deliberations"><span class="secno">5.6.2.7</span> <span class="content"> Council Deliberations</span></a>
+          <li><a href="#council-decision"><span class="secno">5.6.2.8</span> <span class="content"> Council Decision Report</span></a>
+          <li><a href="#council-appeals"><span class="secno">5.6.2.9</span> <span class="content"> Appealing Council Decisions</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#ACReview"><span class="secno">5.7</span> <span class="content"> Advisory Committee Reviews and W3C Decisions</span></a>
+       <ol class="toc">
+        <li><a href="#ACReviewStart"><span class="secno">5.7.1</span> <span class="content"> Initiating an Advisory Committee Review</span></a>
+        <li><a href="#ACReviewAfter"><span class="secno">5.7.2</span> <span class="content"> Determining the W3C Decision</span></a>
+       </ol>
+      <li><a href="#ACVotes"><span class="secno">5.8</span> <span class="content"> Advisory Committee Votes</span></a>
+      <li><a href="#ACAppeal"><span class="secno">5.9</span> <span class="content"> Appeal by Advisory Committee Representatives</span></a>
+     </ol>
+    <li>
+     <a href="#Reports"><span class="secno">6</span> <span class="content"> W3C Technical Reports</span></a>
+     <ol class="toc">
+      <li><a href="#recs-and-notes"><span class="secno">6.1</span> <span class="content"> Types of Technical Reports</span></a>
+      <li>
+       <a href="#general-requirements"><span class="secno">6.2</span> <span class="content"> General Requirements for Technical Reports</span></a>
+       <ol class="toc">
+        <li><a href="#publication"><span class="secno">6.2.1</span> <span class="content"> Publication of Technical Reports</span></a>
+        <li>
+         <a href="#doc-reviews"><span class="secno">6.2.2</span> <span class="content"> Reviews and Review Responsibilities</span></a>
+         <ol class="toc">
+          <li><a href="#wide-review"><span class="secno">6.2.2.1</span> <span class="content"> Wide Review</span></a>
+         </ol>
+        <li><a href="#correction-classes"><span class="secno">6.2.3</span> <span class="content"> Classes of Changes</span></a>
+        <li><a href="#errata"><span class="secno">6.2.4</span> <span class="content"> Errata Management</span></a>
+        <li><a href="#candidate-amendments"><span class="secno">6.2.5</span> <span class="content"> Candidate Amendments</span></a>
+        <li><a href="#no-group-maintenance"><span class="secno">6.2.6</span> <span class="content"> Maintenance Without a Group</span></a>
+        <li><a href="#contributor-license"><span class="secno">6.2.7</span> <span class="content"> License Grants from Non-Participants</span></a>
+       </ol>
+      <li>
+       <a href="#rec-track"><span class="secno">6.3</span> <span class="content"> The W3C Recommendation Track</span></a>
+       <ol class="toc">
+        <li><a href="#maturity-stages"><span class="secno">6.3.1</span> <span class="content"> Maturity Stages on the Recommendation Track</span></a>
+        <li><a href="#implementation-experience"><span class="secno">6.3.2</span> <span class="content"> Implementation Experience</span></a>
+        <li><a href="#transition-reqs"><span class="secno">6.3.3</span> <span class="content"> Advancement on the Recommendation Track</span></a>
+        <li><a href="#update-reqs"><span class="secno">6.3.4</span> <span class="content"> Updating Mature Publications on the Recommendation Track</span></a>
+        <li><a href="#first-wd"><span class="secno">6.3.5</span> <span class="content"> Publishing a First Public Working Draft</span></a>
+        <li><a href="#revising-wd"><span class="secno">6.3.6</span> <span class="content"> Revising a Working Draft</span></a>
+        <li><a href="#transition-cr"><span class="secno">6.3.7</span> <span class="content"> Transitioning to Candidate Recommendation</span></a>
+        <li>
+         <a href="#revising-cr"><span class="secno">6.3.8</span> <span class="content"> Revising a Candidate Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#publishing-crrs"><span class="secno">6.3.8.1</span> <span class="content"> Publishing a <span>Candidate Recommendation Snapshot</span></span></a>
+          <li><a href="#publishing-crud"><span class="secno">6.3.8.2</span> <span class="content"> Publishing a <span>Candidate Recommendation Draft</span></span></a>
+         </ol>
+        <li>
+         <a href="#transition-rec"><span class="secno">6.3.9</span> <span class="content"> Transitioning to Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#transition-rec-requirements"><span class="secno">6.3.9.1</span> <span class="content"> Requirements for Transition</span></a>
+          <li><a href="#initiating-rec-review"><span class="secno">6.3.9.2</span> <span class="content"> Initiating Review</span></a>
+          <li><a href="#rec-review-resolution"><span class="secno">6.3.9.3</span> <span class="content"> Resolution of Review</span></a>
+          <li><a href="#rec-next-steps"><span class="secno">6.3.9.4</span> <span class="content"> Next Steps from W3C Recommendation</span></a>
+         </ol>
+        <li>
+         <a href="#revising-rec"><span class="secno">6.3.10</span> <span class="content"> Revising a W3C Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#revised-rec-editorial"><span class="secno">6.3.10.1</span> <span class="content"> Revising a Recommendation: Editorial Changes</span></a>
+          <li><a href="#revised-rec-substantive"><span class="secno">6.3.10.2</span> <span class="content"> Revising a Recommendation: Substantive Changes</span></a>
+          <li><a href="#revised-rec-features"><span class="secno">6.3.10.3</span> <span class="content"> Revising a Recommendation: New Features</span></a>
+          <li><a href="#change-review"><span class="secno">6.3.10.4</span> <span class="content"> Incorporating Candidate Amendments</span></a>
+         </ol>
+        <li><a href="#rec-track-regression"><span class="secno">6.3.11</span> <span class="content"> Regression on the Recommendation Track</span></a>
+        <li>
+         <a href="#tr-end"><span class="secno">6.3.12</span> <span class="content"> Retiring Recommendation Track Documents</span></a>
+         <ol class="toc">
+          <li><a href="#abandon-draft"><span class="secno">6.3.12.1</span> <span class="content"> Abandoning an Unfinished Recommendation</span></a>
+          <li><a href="#rescind-cr"><span class="secno">6.3.12.2</span> <span class="content"> Rescinding a Candidate Recommendation</span></a>
+          <li><a href="#rec-rescind"><span class="secno">6.3.12.3</span> <span class="content"> Abandoning a W3C Recommendation</span></a>
+          <li><a href="#deactivation"><span class="secno">6.3.12.4</span> <span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#note-track"><span class="secno">6.4</span> <span class="content"> The Note Track (Notes and Statements)</span></a>
+       <ol class="toc">
+        <li><a href="#Note"><span class="secno">6.4.1</span> <span class="content"> Group Notes</span></a>
+        <li><a href="#publishing-notes"><span class="secno">6.4.2</span> <span class="content"> Publishing Notes</span></a>
+        <li><a href="#w3c-statement"><span class="secno">6.4.3</span> <span class="content"> Elevating Group Notes to W3C Statement status</span></a>
+        <li><a href="#revising-memo"><span class="secno">6.4.4</span> <span class="content"> Revising W3C Statements</span></a>
+       </ol>
+      <li>
+       <a href="#registries"><span class="secno">6.5</span> <span class="content"> The Registry Track</span></a>
+       <ol class="toc">
+        <li><a href="#reg-def"><span class="secno">6.5.1</span> <span class="content"> Registry Definitions</span></a>
+        <li><a href="#reg-pub"><span class="secno">6.5.2</span> <span class="content"> Publishing Registries</span></a>
+        <li><a href="#reg-table-update"><span class="secno">6.5.3</span> <span class="content"> Updating Registry Tables</span></a>
+        <li><a href="#reg-data-reports"><span class="secno">6.5.4</span> <span class="content"> Registry Data Reports</span></a>
+        <li><a href="#reg-ref-specifications"><span class="secno">6.5.5</span> <span class="content"> Specifications that Reference Registries</span></a>
+        <li><a href="#reg-pat"><span class="secno">6.5.6</span> <span class="content"> Registries and Patents</span></a>
+       </ol>
+      <li><a href="#switching-tracks"><span class="secno">6.6</span> <span class="content"> Switching Tracks</span></a>
+      <li><a href="#further-reading"><span class="secno">6.7</span> <span class="content"> Further reading</span></a>
+     </ol>
+    <li>
+     <a href="#dissemination"><span class="secno">7</span> <span class="content"> <span></span> Dissemination Policies</span></a>
+     <ol class="toc">
+      <li><a href="#pub-com"><span class="secno">7.1</span> <span class="content"> Public Communication</span></a>
+      <li><a href="#confidentiality-levels"><span class="secno">7.2</span> <span class="content"> Confidentiality Levels</span></a>
+      <li><a href="#confidentiality-change"><span class="secno">7.3</span> <span class="content"> Changing Confidentiality Level</span></a>
+     </ol>
+    <li><a href="#Liaisons"><span class="secno">8</span> <span class="content"> Liaisons</span></a>
+    <li><a href="#Submission"><span class="secno">9</span> <span class="content"> Member Submissions</span></a>
+    <li><a href="#GAProcess"><span class="secno">10</span> <span class="content"> Process Evolution</span></a>
+    <li><a href="#old-terms"><span class="secno"></span> <span class="content"> Appendix A: Retired Terminology</span></a>
+    <li><a href="#acks"><span class="secno"></span> <span class="content"> Appendix B: Acknowledgments</span></a>
+    <li>
+     <a href="#changes"><span class="secno"></span> <span class="content"> Appendix C: Changes</span></a>
+     <ol class="toc">
+      <li><a href="#changes-2025"><span class="secno"></span> <span class="content"> Changes since the <span>3 November 2023 Process</span></span></a>
+      <li><a href="#changes-previous"><span class="secno"></span> <span class="content"> Changes since earlier versions</span></a>
+     </ol>
+    <li>
+     <a href="#w3c-conformance"><span class="secno"></span> <span class="content">Conformance</span></a>
+     <ol class="toc">
+      <li><a href="#w3c-conventions"><span class="secno"></span> <span class="content">Document conventions</span></a>
+     </ol>
+    <li>
+     <a href="#index"><span class="secno"></span> <span class="content">Index</span></a>
+     <ol class="toc">
+      <li><a href="#index-defined-here"><span class="secno"></span> <span class="content">Terms defined by this specification</span></a>
+      <li><a href="#index-defined-elsewhere"><span class="secno"></span> <span class="content">Terms defined by reference</span></a>
+     </ol>
+    <li>
+     <a href="#references"><span class="secno"></span> <span class="content">References</span></a>
+     <ol class="toc">
+      <li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
+      <li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
+     </ol>
+   </ol>
+  </nav>
+  <main>
+   <h2 class="no-num no-toc no-ref heading settled" id="pp"><span class="content"> Relation of Process Document to Patent Policy and Other Policies</span></h2>
+   <p>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> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	The <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and other policies
+	incorporated by normative reference as a part of the Process Document
+	are equally binding.</p>
+   <p>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.</p>
+   <p>In the Process Document, the term “participant” refers to an individual, not an organization.</p>
+   <h2 class="no-num no-toc no-ref heading settled" id="terms"><span class="content"> Conformance and specialized terms</span></h2>
+   <p>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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="not-required"><em class="rfc2119">not required</em></dfn> is equivalent to the term <em class="rfc2119">may</em> as defined in RFC2119 <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a>.</p>
+   <p>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.</p>
+   <nav data-fill-with="table-of-contents"></nav>
+   <main>
+    <h2 class="heading settled" data-level="1" id="Intro"><span class="secno">1. </span><span class="content"> Introduction</span><a class="self-link" href="#Intro"></a></h2>
+    <p>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>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>. <a href="#group-participation">Participants</a> in W3C include <a href="#member-rep">representatives of its Members</a> and the <a data-link-type="dfn" href="#team" id="ref-for-team">Team</a>,
+	as well as <a href="#invited-expert-wg">Invited Experts</a> who can bring additional expertise or represent additional stakeholders. <a data-link-type="dfn" href="#team" id="ref-for-team①">Team</a> representatives both contribute to the technical work
+	and help ensure each group’s proper integration with the rest of W3C.</p>
+    <p>W3C’s technical standards, called <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C">W3C Recommendations</a>,
+	are developed by its <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG">Working Groups</a>;
+	W3C also has other types of publications,
+	all described in <a href="#Reports">§ 6 W3C Technical Reports</a>.
+	W3C has various types of groups;
+	this document describes the formation and policies
+	of its chartered <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG">Interest Groups</a>,
+	see <a href="#Policies">§ 3.1 Policies for Participation in W3C Groups</a> and <a href="#GAGeneral">§ 3.4 Chartered Groups: Working Groups and Interest Groups</a>.
+	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> <a data-link-type="biblio" href="#biblio-bg-cg" title="Community and Business Group Process">[BG-CG]</a>.</p>
+    <p>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.</p>
+    <p>Here is a general overview of how W3C initiates standardization of a Web technology:</p>
+    <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 <a data-link-type="dfn" href="#team" id="ref-for-team②">Team</a> 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>
+    <p>Further sections of this Process Document deal with topics including
+	liaisons (<a href="#Liaisons">§ 8 Liaisons</a>),
+	confidentiality (<a href="#dissemination">§ 7 Dissemination Policies</a>),
+	and formal decisions and appeals (<a href="#decisions">§ 5 Decisions</a>).</p>
+    <h2 class="heading settled" data-level="2" id="Organization"><span class="secno">2. </span><span class="content"> Members and the Team</span><a class="self-link" href="#Organization"></a></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 class="heading settled" data-level="2.1" id="Members"><span class="secno">2.1. </span><span class="content"> Members</span><a class="self-link" href="#Members"></a></h3>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Member|Member" data-noexport id="w3c-member">W3C Members</dfn> are
+	organizations subscribed according to a <a href="https://www.w3.org/membership/agreement/">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	They are represented in W3C processes as follows:</p>
+    <ol>
+     <li> One representative per Member organization participates
+			in the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee">Advisory Committee</a> 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>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>;
+	(refer to the public list of <a href="https://www.w3.org/membership/list/">current W3C Members</a> <a data-link-type="biblio" href="#biblio-member-list" title="The list of current W3C Members">[MEMBER-LIST]</a>).
+	The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure
+	that Member participation agreements remain <a href="#Team-only" id="ref-for-Team-only">Team-only</a> and that no Member receives preferential treatment within W3C. </p>
+    <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. </p>
+    <h4 class="heading settled" data-level="2.1.1" id="MemberBenefits"><span class="secno">2.1.1. </span><span class="content"> Rights of Members</span><a class="self-link" href="#MemberBenefits"></a></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> Access to <a href="#Member-only" id="ref-for-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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>. 
+    </ul>
+    <p>Furthermore, subject to further restrictions included in their 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>
+       In <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW">Workshops</a>. 
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>)</p>
+     <li> On the Team, as <a href="#fellows" id="ref-for-fellows">W3C Fellows</a>. 
+    </ul>
+    <p>The rights and benefits of W3C membership <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> are contingent upon conformance to the processes described in this document.
+	Disciplinary action for anyone participating in W3C activities is described in <a href="#discipline">§ 3.1.1.1 Expectations and Discipline</a>.</p>
+    <p>Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member website</a> <a data-link-type="biblio" href="#biblio-member-hp" title="Member website (Member-only access)">[MEMBER-HP]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.2" id="RelatedAndAssociatedMembers"><span class="secno">2.1.2. </span><span class="bs-old-id" id="RelatedAndConsortiumMembers"></span><span class="content"> Member Associations and Related Members</span><a class="self-link" href="#RelatedAndAssociatedMembers"></a></h4>
+    <h5 class="heading settled" data-level="2.1.2.1" id="MemberAssoc"><span class="secno">2.1.2.1. </span><span class="bs-old-id" id="MemberConsortia"></span><span class="content"> Membership Associations</span><a class="self-link" href="#MemberAssoc"></a></h5>
+    <p>A “<dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Member Association | Member Associations" data-noexport id="member-association">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 <a data-link-type="dfn" href="#member-association" id="ref-for-member-association">Member Association</a> merely because it has shareholders or stockholders.
+	If it is not clear whether a prospective Member qualifies as a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association①">Member Association</a>,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo">CEO</a> may reasonably make the determination.
+	For a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association②">Member Association</a>, the rights and privileges of W3C Membership
+	described in the W3C Process Document extend to the <a data-link-type="dfn" href="#member-association" id="ref-for-member-association③">Member Association</a>’s paid staff
+	and Advisory Committee representative.</p>
+    <p><a data-link-type="dfn" href="#member-association" id="ref-for-member-association④">Member Associations</a> <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>
+    <p>For <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑤">Member Associations</a> 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.</p>
+    <p>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.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="2.1.2.2" id="MemberRelated"><span class="secno">2.1.2.2. </span><span class="content"> Related Members</span><a class="self-link" href="#MemberRelated"></a></h5>
+    <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 <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Related Member" id="related-member">related</dfn> if:</p>
+    <ol>
+     <li> Either Member is a <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary">subsidiary</a> of the other, or 
+     <li> Both Members are <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary①">subsidiaries</a> of a common entity, or 
+     <li> The Members have an employment contract or consulting contract that affects W3C participation. 
+    </ol>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="subsidiary">subsidiary</dfn> is an organization of which effective control and/or majority ownership rests with another,
+	single organization.</p>
+    <p><a data-link-type="dfn" href="#related-member" id="ref-for-related-member">Related Members</a> <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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.3" id="standing"><span class="secno">2.1.3. </span><span class="content"> Good Standing</span><a class="self-link" href="#standing"></a></h4>
+    <p><a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member">Members</a> who have not lost Good Standing as defined in the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a> are considered, for the purposes of this Process,
+	to be in <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="good-standing">Good Standing</dfn>.
+	A group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member①">related Members</a> is in Good Standing if
+	at least one of them is in Good Standing.</p>
+    <h3 class="heading settled" data-level="2.2" id="Team"><span class="secno">2.2. </span><span class="bs-old-id" id="def-Director"></span><span class="content"> The W3C Team</span><a class="self-link" href="#Team"></a></h3>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team | W3C Team" id="team">Team</dfn> consists of <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="ceo">CEO</dfn>,
+	W3C paid staff,
+	unpaid interns,
+	and W3C Fellows. <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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> <a data-link-type="biblio" href="#biblio-fellows" title="W3C Fellows Program">[FELLOWS]</a>.
+	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.</p>
+    <p>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. <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision">Team Decisions</a> derive from the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo①">CEO</a>’s authority,
+	even when they are carried out by other members of the <a data-link-type="dfn" href="#team" id="ref-for-team③">Team</a>.</p>
+    <p>Oversight over the <a data-link-type="dfn" href="#team" id="ref-for-team④">Team</a>,
+	budgeting,
+	and other business decisions,
+	is provided by the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="BoD | Board | Board of Directors | W3C Board of Directors" id="bod">W3C Board of Directors</dfn>,
+	rather than managed directly by the Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf">W3C Bylaws</a> for more details
+	on the <a data-link-type="dfn" href="#bod" id="ref-for-bod">Board</a> and overall governance of W3C.</p>
+    <h2 class="heading settled" data-level="3" id="groups"><span class="secno">3. </span><span class="content"> Groups and Participation</span><a class="self-link" href="#groups"></a></h2>
+    <p>For the purposes of this Process, a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="group" data-noexport id="w3c-group">W3C Group</dfn> is one of W3C’s <a href="#wgparticipant" id="ref-for-wgparticipant">Working Groups</a>, <a href="#igparticipant" id="ref-for-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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="participant">participant</dfn> is a member of such a group.</p>
+    <h3 class="heading settled" data-level="3.1" id="Policies"><span class="secno">3.1. </span><span class="content"> Policies for Participation in W3C Groups</span><a class="self-link" href="#Policies"></a></h3>
+    <h4 class="heading settled" data-level="3.1.1" id="ParticipationCriteria"><span class="secno">3.1.1. </span><span class="content"> Individual Participation Criteria</span><a class="self-link" href="#ParticipationCriteria"></a></h4>
+    <h5 class="heading settled" data-level="3.1.1.1" id="discipline"><span class="secno">3.1.1.1. </span><span class="content"> Expectations and Discipline</span><a class="self-link" href="#discipline"></a></h5>
+    <p>There are three qualities an individual is expected to demonstrate in order to participate in W3C:</p>
+    <ol>
+     <li> Technical competence in one’s role; 
+     <li> The ability to act fairly; 
+     <li> Social competence in one’s role. 
+    </ol>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative">Advisory Committee representatives</a> who nominate individuals from their organization for participation in W3C activities
+	are responsible for assessing and attesting to the qualities of those nominees.</p>
+    <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> <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a> and the participation requirements described in
+	“Disclosure”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. </p>
+    <p>The <a data-link-type="dfn" href="#ceo" id="ref-for-ceo②">CEO</a> <em class="rfc2119">may</em> take disciplinary action,
+	including suspending or removing for cause
+	a participant in any group (including the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group">TAG</a>)
+	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>.</p>
+    <h5 class="heading settled" data-level="3.1.1.2" id="coi"><span class="secno">3.1.1.2. </span><span class="content"> Conflict of Interest Policy</span><a class="self-link" href="#coi"></a></h5>
+    <p>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.</p>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑤">Team</a> <em class="rfc2119">may</em> appoint a new group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs">Chair</a> 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).</p>
+    <p>The following are some scenarios where disclosure is appropriate:</p>
+    <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>
+    <p>Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the <a data-link-type="dfn" href="#team" id="ref-for-team⑥">Team</a>.</p>
+    <p><a data-link-type="dfn" href="#team" id="ref-for-team⑦">Team</a> 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> <a data-link-type="biblio" href="#biblio-conflict-policy" title="Conflict of Interest Policy for the W3C Team">[CONFLICT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.3" id="member-rep"><span class="secno">3.1.1.3. </span><span class="content"> Individuals Representing a Member Organization</span><a class="self-link" href="#member-rep"></a></h5>
+    <p>Generally, individuals representing a Member in an official capacity within W3C
+	are employees of the Member organization.
+	However, an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①">Advisory Committee representative</a> <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.</p>
+    <p>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 <a data-link-type="dfn" href="#ceo" id="ref-for-ceo③">CEO</a> <em class="rfc2119">may</em> decline
+	to allow an individual designated by an Advisory Committee representative to participate in a group.</p>
+    <p>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>).</p>
+    <h4 class="heading settled" data-level="3.1.2" id="GeneralMeetings"><span class="secno">3.1.2. </span><span class="bs-old-id" id="EventsS"></span><span class="bs-old-id" id="GAEvents"></span><span class="content"> Meetings</span><a class="self-link" href="#GeneralMeetings"></a></h4>
+    <p>The requirements in this section apply to the official meetings of any <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group">W3C group</a>,
+	as well as to official W3C meetings with open-ended participation from the Membership and/or the public,
+	such as <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW①">Workshops</a>.</p>
+    <p>W3C distinguishes two types of meetings:</p>
+    <ol>
+     <li> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 class="dfn-paneled" data-dfn-type="dfn" data-noexport 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>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①">Chair</a> <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 <a data-link-type="dfn" href="#participant" id="ref-for-participant">participant</a>.
+	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.</p>
+    <h5 class="heading settled" data-level="3.1.2.1" id="meeting-schedules"><span class="secno">3.1.2.1. </span><span class="content"> Meeting Scheduling and Announcements</span><a class="self-link" href="#meeting-schedules"></a></h5>
+    <p>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.</p>
+    <p>The following table lists <em class="rfc2119">recommendations</em> for organizing a meeting:</p>
+    <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"><a data-link-type="dfn" href="#minutes" id="ref-for-minutes">Minutes</a> available (after) 
+       <td><span class="time-interval">two weeks</span> 
+       <td><span class="time-interval">48 hours</span> 
+    </table>
+    <p><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 <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW②">Workshops</a>,
+	shorter notice is not allowed.</p>
+    <h5 class="heading settled" data-level="3.1.2.2" id="meeting-minutes"><span class="secno">3.1.2.2. </span><span class="content"> Meeting Minutes</span><a class="self-link" href="#meeting-minutes"></a></h5>
+    <p>Groups <em class="rfc2119">should</em> take and retain <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minutes">minutes</dfn> of their meetings,
+	and <em class="rfc2119">must</em> record
+	any official <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision">group decisions</a> made during the meeting discussions.
+	Details of the discussion leading to such decisions are not required,
+	provided that the rationale for the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision①">group decision</a> is nonetheless clear.</p>
+    <h5 class="heading settled" data-level="3.1.2.3" id="meeting-recording"><span class="secno">3.1.2.3. </span><span class="content"> Meeting Recordings and Transcripts</span><a class="self-link" href="#meeting-recording"></a></h5>
+    <p>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.</p>
+    <h4 class="heading settled" data-level="3.1.3" id="tooling"><span class="secno">3.1.3. </span><span class="content"> Tooling and Archiving for Discussions and Publications</span><a class="self-link" href="#tooling"></a></h4>
+    <p>For <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group①">W3C Groups</a> 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:</p>
+    <ul>
+     <li id="report-stability"><a class="self-link" href="#report-stability"></a> 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"><a class="self-link" href="#report-accessibility"></a> 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">
+      <a class="self-link" href="#discussion-archiving"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> The lack, or loss, of such archives does not by itself
+			invalidate an otherwise-valid decision.</p>
+     <li id="tool-accessibility">
+      <a class="self-link" href="#tool-accessibility"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> If a new participant joins who cannot use the tool,
+			this can require the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②">Working Group</a> to change its tooling
+			or operate some workaround.</p>
+     <li id="where-is-your-stuff"><a class="self-link" href="#where-is-your-stuff"></a> 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>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧">Team</a> is responsible for ensuring adherence to these rules
+	and for bringing any group not in compliance into compliance.</p>
+    <h4 class="heading settled" data-level="3.1.4" id="resignation"><span class="secno">3.1.4. </span><span class="content"> Resignation from a Group</span><a class="self-link" href="#resignation"></a></h4>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑨">Team</a>,
+	the Member and their representatives
+	or the Invited Expert
+	will be deemed to have resigned from the relevant group.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪">Team</a> <em class="rfc2119">must</em> record the notification.
+	See “Exclusion and Resignation from the Working Group” in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for information about obligations remaining after resignation from certain groups.</p>
+    <h3 class="heading settled" data-level="3.2" id="AC"><span class="secno">3.2. </span><span class="content"> The Advisory Committee (AC)</span><a class="self-link" href="#AC"></a></h3>
+    <h4 class="heading settled" data-level="3.2.1" id="ac-role"><span class="secno">3.2.1. </span><span class="content"> Role of the Advisory Committee</span><a class="self-link" href="#ac-role"></a></h4>
+    <p id="ReviewAppeal"> The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee|AC" id="advisory-committee">Advisory Committee</dfn> represents
+	the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member①">Members</a> of W3C at large.
+	It is responsible for: </p>
+    <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>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> of a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision">W3C decision</a> or <a data-link-type="dfn" href="#team" id="ref-for-team①①">Team</a>’s decision.</p>
+    <p>See also the additional roles of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③">Advisory Committee representatives</a> described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h4 class="heading settled" data-level="3.2.2" id="ac-participation"><span class="secno">3.2.2. </span><span class="content"> Participation in the Advisory Committee</span><a class="self-link" href="#ac-participation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①">Advisory Committee</a> is composed of one <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee representative| AC representative" id="advisory-committee-representative">representative</dfn> from each Member organization
+	(refer to the <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①②">Member-only</a> list
+	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. <a data-link-type="biblio" href="#biblio-current-ac" title="Current Advisory Committee representatives (Member-only access)">[CURRENT-AC]</a>)</p>
+    <p>When an organization joins W3C
+	(see “<a href="https://www.w3.org/membership/join/">How to Join W3C</a>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>),
+	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of their Membership Agreement.
+	The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a> 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 <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative④">Advisory Committee representative</a>,
+	and more. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑤">Advisory Committee representatives</a> <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.</p>
+    <p>The AC representative may delegate any of their rights and responsibilities
+	to an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="alternate AC representative | alternate Advisory Committee representative | alt AC rep" id="alternate-ac-representative">alternate</dfn> (except the ability to designate an alternate).</p>
+    <h4 class="heading settled" data-level="3.2.3" id="ACCommunication"><span class="secno">3.2.3. </span><span class="content"> Advisory Committee Mailing Lists</span><a class="self-link" href="#ACCommunication"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②">Team</a> <em class="rfc2119">must</em> provide two mailing lists for use by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②">Advisory Committee</a>:</p>
+    <ol>
+     <li> One for official announcements (e.g., those required by this document) from the <a data-link-type="dfn" href="#team" id="ref-for-team①③">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③">Advisory Committee</a>.
+			This list is read-only for Advisory Committee representatives. 
+     <li> One for discussion among <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑥">Advisory Committee representatives</a>.
+			Though this list is primarily for Advisory Committee representatives,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①④">Team</a> <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>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑦">Advisory Committee representative</a> <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.</p>
+    <h4 class="heading settled" data-level="3.2.4" id="ACMeetings"><span class="secno">3.2.4. </span><span class="content"> Advisory Committee Meetings</span><a class="self-link" href="#ACMeetings"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑤">Team</a> organizes a <a href="#ftf-meeting" id="ref-for-ftf-meeting">face-to-face meeting</a> for the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④">Advisory Committee</a> <span class="time-interval">twice a year</span>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⑥">Team</a> 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:</p>
+    <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>
+    </dl>
+    <p>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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑦">Team</a> <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.</p>
+    <p>More information about <a href="https://www.w3.org/events/ac/">Advisory Committee meetings</a> <a data-link-type="biblio" href="#biblio-ac-meeting" title="Advisory Committee meetings (Member-only access)">[AC-MEETING]</a> is available at the Member website.</p>
+    <h3 class="heading settled" data-level="3.3" id="elected-groups"><span class="secno">3.3. </span><span class="content"> Elected Groups: The AB and the TAG</span><a class="self-link" href="#elected-groups"></a></h3>
+    <p>The W3C Process defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="elected-group">elected groups</dfn>:
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①">Advisory Board</a> (AB) and
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①">Technical Architecture Group</a> (TAG),
+	both elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑤">Advisory Committee</a>.</p>
+    <h4 class="heading settled" data-level="3.3.1" id="AB"><span class="secno">3.3.1. </span><span class="content"> Advisory Board (AB)</span><a class="self-link" href="#AB"></a></h4>
+    <h5 class="heading settled" data-level="3.3.1.1" id="ab-role"><span class="secno">3.3.1.1. </span><span class="content"> Role of the Advisory Board</span><a class="self-link" href="#ab-role"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Board|AB" id="advisory-board">Advisory Board</dfn> 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>.
+	As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council">W3C Council</a>,
+	members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②">Advisory Board</a> hear and adjudicate on <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③">Advisory Board</a> is distinct from the <a data-link-type="dfn" href="#bod" id="ref-for-bod①">Board of Directors</a> and has no decision-making authority within W3C;
+	its role is strictly advisory.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> While the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board④">AB</a> as such does not have decision-making authority,
+	its members do when sitting as part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①">W3C Council</a>.</p>
+    <p>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> <a data-link-type="biblio" href="#biblio-ab-hp" title="The Advisory Board home page">[AB-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.1.2" id="ABParticipation"><span class="secno">3.3.1.2. </span><span class="content"> Composition of the Advisory Board</span><a class="self-link" href="#ABParticipation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑤">Advisory Board</a> 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 <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑥">AB</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⑧">Team</a> 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.</p>
+    <p>The team also appoints a <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact">Staff Contact</a>,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.
+	The CEO and Staff Contact have a standing invitation
+	to all regular Advisory Board sessions.</p>
+    <p>The nine to eleven <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑦">Advisory Board</a> participants are elected by the W3C <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑥">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="3.3.1.3" id="ab-comm"><span class="secno">3.3.1.3. </span><span class="content"> Communications of the Advisory Board</span><a class="self-link" href="#ab-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑨">Team</a> <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.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑧">Advisory Board</a> <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>.</p>
+    <h5 class="heading settled" data-level="3.3.1.4" id="ab-bod-liaison"><span class="secno">3.3.1.4. </span><span class="content"> Liaisons between the Advisory Board and the Board of Directors</span><a class="self-link" href="#ab-bod-liaison"></a></h5>
+    <p>To ensure good communication between the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑨">AB</a> and the <a data-link-type="dfn" href="#bod" id="ref-for-bod②">Board of Directors</a> and facilitate operational and management consistency,
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⓪">AB</a> <em class="rfc2119">may</em> appoint up to two of its participants as liaisons to the <a data-link-type="dfn" href="#bod" id="ref-for-bod③">Board</a>.
+	Such appointees are expected to attend and participate in <a data-link-type="dfn" href="#bod" id="ref-for-bod④">Board</a> meetings
+	and access <a data-link-type="dfn" href="#bod" id="ref-for-bod⑤">Board</a> materials
+	as Non-voting Observers. <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a> They do not form part of the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑥">Board</a>’s decision-making body,
+	and may be excluded from such participation
+	in accordance with applicable Board procedures.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①①">Advisory Board</a> <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.</p>
+    <h4 class="heading settled" data-level="3.3.2" id="TAG"><span class="secno">3.3.2. </span><span class="content"> Technical Architecture Group (TAG)</span><a class="self-link" href="#TAG"></a></h4>
+    <h5 class="heading settled" data-level="3.3.2.1" id="tag-role"><span class="secno">3.3.2.1. </span><span class="content"> Role of the Technical Architecture Group</span><a class="self-link" href="#tag-role"></a></h5>
+    <p>The mission of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Technical Architecture Group|TAG" id="technical-architecture-group">TAG</dfn> is stewardship of the Web architecture.
+	There are three aspects to this mission:</p>
+    <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> to help coordinate cross-technology architecture developments inside and outside W3C. 
+    </ol>
+    <p>As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②">W3C Council</a>,
+	the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②">TAG</a> hear and adjudicate on <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals①">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③">TAG</a>’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.</p>
+    <p>When the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④">TAG</a> votes to resolve an issue,
+	each TAG participant
+	(whether appointed, elected, or the Chair)
+	has one vote;
+	see also the general section on <a href="#Votes">votes</a> in this Process Document.</p>
+    <p>Details about the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑤">TAG</a> (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings)
+	are available at the <a href="https://www.w3.org/2001/tag/">TAG home page</a> <a data-link-type="biblio" href="#biblio-tag-hp" title="The TAG home page">[TAG-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.2.2" id="tag-participation"><span class="secno">3.3.2.2. </span><span class="content"> Composition of the Technical Architecture Group</span><a class="self-link" href="#tag-participation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑥">TAG</a> consists of:</p>
+    <ul>
+     <li> Tim Berners-Lee, who is a life member; 
+     <li> Three participants <a href="#TAG-appointments">appointed by the Team</a>; 
+     <li> Eight participants elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑦">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>. 
+    </ul>
+    <p>Participants in the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑦">TAG</a> choose by consensus their Chair or co-Chairs;
+	in the absence of consensus, the <a data-link-type="dfn" href="#team" id="ref-for-team②⓪">Team</a> appoints the Chair or co-Chairs of the TAG.
+	The Chair or co-Chairs <em class="rfc2119">must</em> be selected from the participants of the TAG.
+	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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②①">Team</a> also appoints a <a href="https://www.w3.org/guide/teamcontact/role">Staff Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> for the TAG,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.</p>
+    <p>The terms of TAG participants last for <span class="time-interval">two years</span>.
+	Terms are staggered so that four elected terms
+	and either one or two appointed terms expire each year.
+	If an individual is appointed or elected to fill an incomplete term,
+	that individual’s term ends at the normal expiration date of that term.
+	Regular TAG terms begin on 1 February and end on 31 January.</p>
+    <h5 class="heading settled" data-level="3.3.2.3" id="tag-comm"><span class="secno">3.3.2.3. </span><span class="content"> Communications of the Technical Architecture Group</span><a class="self-link" href="#tag-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②②">Team</a> <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
+    <ul>
+     <li> a public discussion (not just input) list for issues of Web architecture.
+			The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑧">TAG</a> will conduct its public business on this list. 
+     <li> a <a href="#Member-only" id="ref-for-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. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑨">TAG</a> <em class="rfc2119">may</em> also request the creation of additional topic-specific, public mailing lists.
+	For some TAG discussions (e.g.,  a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals②">Submission Appeal</a>),
+	the TAG <em class="rfc2119">may</em> use a list that will be <a href="#Member-only" id="ref-for-Member-only①④">Member-only</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⓪">TAG</a> <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 <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①①">TAG</a> <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
+    <h4 class="heading settled" data-level="3.3.3" id="AB-TAG-participation"><span class="secno">3.3.3. </span><span class="content"> Participation in Elected Groups</span><a class="self-link" href="#AB-TAG-participation"></a></h4>
+    <h5 class="heading settled" data-level="3.3.3.1" id="elected-expectations"><span class="secno">3.3.3.1. </span><span class="content"> Expectations for Elected Groups Participants</span><a class="self-link" href="#elected-expectations"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①②">Advisory Board</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①②">TAG</a> participants have a special role within W3C:
+	they are elected by the Membership and appointed by the <a data-link-type="dfn" href="#team" id="ref-for-team②③">Team</a> with the expectation that they will use their best judgment
+	to find the best solutions for the Web,
+	not just for any particular network,
+	technology,
+	vendor,
+	or user.
+	Advisory Board and TAG participants are expected to participate regularly and fully.
+	Advisory Board and TAG participants <em class="rfc2119">should</em> attend <a href="#ACMeetings">Advisory Committee meetings</a>.</p>
+    <p>Individuals elected or appointed to the Advisory Board or TAG act in their personal capacity,
+	to serve the needs of the W3C membership as a whole,
+	and the Web community.
+	Whether they are Member representatives or Invited Experts,
+	their activities in those roles are separate and distinct from their activities on the Advisory Board or TAG.</p>
+    <p>An individual participates on the Advisory Board or TAG
+	from the moment the individual’s term begins until the seat is <a href="#AB-TAG-vacated">vacated</a> (e.g. because the term ends).
+	Although Advisory Board and TAG participants do not advocate for the commercial interests of their employers,
+	their participation does carry the responsibilities associated with Member representation,
+	Invited Expert status,
+	or Team representation
+	(as described in the section on the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>).</p>
+    <p>Participation in the TAG or AB is afforded to the specific individuals elected or appointed to those positions,
+	and a participant’s seat <em class="rfc2119">must not</em> be delegated to any other person.</p>
+    <h5 class="heading settled" data-level="3.3.3.2" id="AB-TAG-constraints"><span class="secno">3.3.3.2. </span><span class="content"> Elected Groups Participation Constraints</span><a class="self-link" href="#AB-TAG-constraints"></a></h5>
+    <p>Given the few seats available on the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①③">Advisory Board</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①③">TAG</a>,
+	and in order to ensure that the diversity of W3C Members is represented:</p>
+    <ul>
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the TAG
+			except when this is caused by a change of affiliation of an existing participant.
+			At the completion of the next regularly scheduled election for the TAG,
+			the organization <em class="rfc2119">must</em> have returned to having at most one seat. 
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation①">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the AB.
+			If, for whatever reason, these constraints are not satisfied
+			(e.g., because an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①④">AB</a> participant changes jobs),
+			one participant <em class="rfc2119">must</em> cease <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑤">AB</a> participation
+			until the situation has been resolved.
+			If after <span class="time-interval">30 days</span> the situation has not been resolved,
+			the Chair will apply
+			the <a href="#random">verifiable random selection procedure</a> described below
+			to choose one person for continued participation and declare the other seat(s) vacant. 
+     <li> An individual <em class="rfc2119">must not</em> participate on both the TAG and the AB. 
+    </ul>
+    <h5 class="heading settled" data-level="3.3.3.3" id="AB-TAG-elections"><span class="secno">3.3.3.3. </span><span class="content"> Advisory Board and Technical Architecture Group Elections</span><a class="self-link" href="#AB-TAG-elections"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑥">Advisory Board</a> and a portion of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①④">Technical Architecture Group</a> are elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑧">Advisory Committee</a>,
+	using a Single Transferable Vote system.
+	An election begins when the Team sends a Call for Nominations to the Advisory Committee.
+	Any Call for Nominations specifies the minimum and maximum number of available seats,
+	the deadline for nominations,
+	details about the specific vote tabulation system selected by the Team for the election,
+	and operational information such as how to nominate a candidate.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②④">Team</a> <em class="rfc2119">may</em> modify the tabulation system after the Call for Nominations
+	but <em class="rfc2119">must</em> stabilize it no later than the Call for Votes.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②⑤">Team</a> announces appointments
+	after the results of the election are known,
+	and before the start of the term,
+	as described in <a href="#TAG-appointments">§ 3.3.3.4 Technical Architecture Group Appointments</a>.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑤">TAG</a>,
+	the minimum and maximum number of available seats are the same:
+	the 4 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑦">AB</a>,
+	the minimum and maximum number of available seats differ:
+	The maximum number is the 5 or 6 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats;
+	the minimum number is such that when added to the occupied seats from the prior year,
+	the minimum size of the AB (9) is reached.</p>
+    <p>Each Member (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member②">related Members</a>) <em class="rfc2119">may</em> nominate one individual.
+	A nomination <em class="rfc2119">must</em> be made with the consent of the nominee.
+	In order for an individual to be nominated as a Member representative,
+	the individual <em class="rfc2119">must</em> qualify for <a href="#member-rep">Member representation</a> and the Member’s <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑧">Advisory Committee representative</a> <em class="rfc2119">must</em> include in the nomination
+	the (same) <a href="#member-rep-info">information required for a Member representative in a Working Group</a>.
+	In order for an individual to be nominated as an Invited Expert,
+	the individual <em class="rfc2119">must</em> provide
+	the (same) <a href="#inv-expert-info" id="ref-for-inv-expert-info">information required for an Invited Expert in a Working Group</a> and the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑨">Advisory Committee representative</a> <em class="rfc2119">must</em> include that information in the nomination.
+	In order for an individual to be nominated as a <a data-link-type="dfn" href="#team" id="ref-for-team②⑥">Team</a> representative,
+	the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⓪">Advisory Committee representative</a> <em class="rfc2119">must</em> first secure approval from <a data-link-type="dfn" href="#team" id="ref-for-team②⑦">Team</a> management.
+	A nominee is <em class="rfc2119">not required</em> to be an employee of a Member organization,
+	and <em class="rfc2119">may</em> be a <a href="#fellows" id="ref-for-fellows①">W3C Fellow</a>.
+	The nomination form <em class="rfc2119">must</em> ask for the nominee’s <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation②">primary affiliation</a>,
+	and this will be reported on the ballot.
+	For most nominees,
+	the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="primary-affiliation">primary affiliation</dfn> is their employer and will match their affiliation in the W3C database.
+	For contractors and invited experts,
+	this will normally be their contracting company
+	or their invited expert status;
+	in some cases
+	(e.g. where a consultant is consulting for only one organization)
+	this <em class="rfc2119">may</em> be the organization for whom the nominee is consulting.
+	A <a href="#AB-TAG-constraints">change of affiliation</a> is defined
+	such that this field would carry a different answer
+	if the nominee were to be re-nominated
+	(therefore,
+	terminating employment,
+	or accepting new employment,
+	are changes of affiliation).
+	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
+	Each nomination <em class="rfc2119">should</em> include
+	a few informative paragraphs about the nominee.
+	If an identified candidate’s nomination information is only partially complete
+	as of the deadline for nominations,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team②⑧">Team</a> <em class="rfc2119">may</em> allow extra time for that candidate’s nomination to be completed,
+	so long as it does not delay the election as a whole.</p>
+    <p>If, after the deadline for nominations, the number of nominees is:</p>
+    <ul>
+     <li> Greater than or equal to the minimum number of available seats
+			and less than or equal to the maximum number of available seats,
+			those nominees are thereby elected.
+			This situation constitutes a tie for the purpose of assigning <a href="#short-term">incomplete terms</a>.
+			Furthermore, if the number is less than the maximum number of available seats,
+			the longest terms are filled first. 
+     <li> Less than the minimum number of available seats,
+			Calls for Nominations are issued until a sufficient number of people have been nominated.
+			Those already nominated do not need to be renominated after a renewed call. 
+     <li> Greater than the maximum number of available seats,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team②⑨">Team</a> issues a Call for Votes
+			that includes the names of all candidates,
+			the (maximum) number of available seats,
+			the deadline for votes,
+			details about the vote tabulation system selected by the Team for the election,
+			and operational information. 
+    </ul>
+    <p>When there is a vote,
+	each Member in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing">Good Standing</a> (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member③">related Members</a>) <em class="rfc2119">may</em> submit one ballot that ranks candidates in the Member’s preferred order.
+	Once the deadline for votes has passed,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⓪">Team</a> announces the results to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑨">Advisory Committee</a>.
+	In case of a tie the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to fill the available seats.</p>
+    <p id="short-term">The shortest incomplete term is assigned to the elected candidate ranked lowest by the tabulation of votes,
+	the next shortest term to the next-lowest ranked elected candidate,
+	and so on.
+	In the case of a tie among those eligible for a incomplete term,
+	the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to assign the incomplete term. </p>
+    <p>Refer to <a href="https://www.w3.org/guide/process/election">How to Organize an Advisory Board or TAG election</a> <a data-link-type="biblio" href="#biblio-election-howto" title="How to Organize an Advisory Board or TAG election">[ELECTION-HOWTO]</a> for more details.</p>
+    <h5 class="heading settled" data-level="3.3.3.4" id="TAG-appointments"><span class="secno">3.3.3.4. </span><span class="content"> Technical Architecture Group Appointments</span><a class="self-link" href="#TAG-appointments"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③①">Team</a> is responsible for appointing
+	3 of the participants to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑥">Technical Architecture Group</a>.
+	This mechanism complements the election process.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③②">Team</a> <em class="rfc2119">should</em> use its appointments to support
+	a diverse and well-balanced <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑦">TAG</a>,
+	including diversity of technical background, knowledge, and skill sets.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③③">Team</a> <em class="rfc2119">should</em> actively seek
+	candidates for appointment to the TAG,
+	and <em class="rfc2119">must</em> make available to
+	the W3C community at large
+	a means to propose candidates for consideration,
+	explicitly soliciting input from at least
+	current and incoming <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑧">TAG</a> members, the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⓪">Advisory Committee</a>, and <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②">Chairs</a>.</p>
+    <p>The constraints for appointment to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑨">TAG</a> are
+	the same as for elected participants
+	(see <a href="#AB-TAG-constraints">§ 3.3.3.2 Elected Groups Participation Constraints</a> and <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a>),
+	with the additional constraint that
+	a person <em class="rfc2119">must not</em> be appointed
+	for more than two <em>consecutive</em> terms.
+	(Partial terms used to fill a vacated seat do not count towards this limit.)</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since there are no limits on elected terms,
+	this limit on appointed terms does not constrain
+	term-limited appointees
+	from running for election at any time.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③④">Team</a>’s choice of appointee(s)
+	is subject to ratification by secret ballot
+	by both the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑧">AB</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⓪">TAG</a>,
+	requiring a two-thirds approval from each.
+	In the case of regularly scheduled elections,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②①">TAG</a> participants in this ratification are
+	its members for the upcoming term.</p>
+    <p>For regularly scheduled elections,
+	selection begins once the results of the elections are known,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team③⑤">Team</a> <em class="rfc2119">should</em> announce the ratified appointment(s)
+	no later than the start of the regularly scheduled term.
+	When an appointed seat is vacated outside of a regularly scheduled election,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⑥">Team</a> <em class="rfc2119">should</em> seek to appoint a replacement
+	unless a regular Call for Nominations is scheduled within 2 months,
+	and it <em class="rfc2119">must</em> announce the ratified appointment
+	no later than the Call for Nominations of the next scheduled election.</p>
+    <h5 class="heading settled" data-level="3.3.3.5" id="random"><span class="secno">3.3.3.5. </span><span class="content"> Verifiable Random Selection Procedure</span><a class="self-link" href="#random"></a></h5>
+    <p>When it is necessary to use a verifiable random selection process
+	(e.g., in an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑨">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②②">TAG</a> election,
+	to “draw straws” in case of a tie
+	or to fill a incomplete term),
+	W3C uses the random and verifiable procedure defined in <a href="https://www.ietf.org/rfc/rfc3797.txt">RFC 3797</a> <a data-link-type="biblio" href="#biblio-rfc3797" title="Publicly Verifiable Nominations Committee (NomCom) Random Selection">[RFC3797]</a>.
+	The procedure orders an input list of names
+	(listed in alphabetical order by family name unless otherwise specified)
+	into a “result order”.</p>
+    <p>W3C applies this procedure as follows:</p>
+    <ol>
+     <li> When N people have tied for M (less than N) seats.
+			In this case, only the names of the N individuals who tied
+			are provided as input to the procedure.
+			The M seats are assigned in result order. 
+     <li> After all elected individuals have been identified,
+			when N people are eligible for M (less than N) incomplete terms.
+			In this case, only the names of those N individuals are provided as input to the procedure.
+			The incomplete terms are assigned in result order. 
+    </ol>
+    <h5 class="heading settled" data-level="3.3.3.6" id="AB-TAG-vacated"><span class="secno">3.3.3.6. </span><span class="content"> Elected Groups Vacated Seats</span><a class="self-link" href="#AB-TAG-vacated"></a></h5>
+    <p>An <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⓪">Advisory Board</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②③">TAG</a> participant’s seat is vacated when:</p>
+    <ul>
+     <li> the participant resigns, or 
+     <li> an Advisory Board or TAG participant changes affiliations
+			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
+			or 
+     <li> the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo④">CEO</a> dismisses the participant
+			for failing to meet the criteria in section <a href="#ParticipationCriteria">§ 3.1.1 Individual Participation Criteria</a>,
+			or 
+     <li> their term ends. 
+    </ul>
+    <p>If a participant changes affiliation,
+	but the <a href="#AB-TAG-constraints">participation constraints</a> are met,
+	that participant’s seat becomes vacant at the next regularly scheduled election for that group.</p>
+    <p>Vacated seats are filled according to this schedule:</p>
+    <ul>
+     <li> When an appointed <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②④">TAG</a> seat is vacated,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team③⑦">Team</a> <a href="#TAG-appointments">appoints</a> a replacement. 
+     <li>
+       When an elected seat on either the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②①">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑤">TAG</a> is vacated,
+			the seat is filled at the next regularly scheduled election for the group
+			unless the group Chair requests that W3C hold an election before then
+			(for instance, due to the group’s workload). 
+      <ul>
+       <li> The group Chair <em class="rfc2119">should not</em> request such an election
+					if the next regularly scheduled election is fewer than three months away. 
+       <li> The group Chair <em class="rfc2119">may</em> request an election,
+					and the election may begin, as soon as a current member gives notice of a resignation,
+					including a resignation effective as of a given date in the future. 
+      </ul>
+      <p>When such an election is held,
+			the minimum number of available seats is such that
+			when added to the number of continuing participants,
+			the minimum total number of elected seats is met
+			(8 for the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑥">TAG</a>, 9 for the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②②">AB</a>);
+			and the maximum number corresponds to all unoccupied seats.
+			Except for the number of available seats and the length of the terms,
+			the <a href="#AB-TAG-elections">usual rules for Advisory Board and Technical Architecture Group Elections</a> apply.</p>
+    </ul>
+    <h3 class="heading settled" data-level="3.4" id="GAGeneral"><span class="secno">3.4. </span><span class="bs-old-id" id="WG-and-IG"></span><span class="bs-old-id" id="ChapterGroups"></span><span class="content"> Chartered Groups: Working Groups and Interest Groups</span><a class="self-link" href="#GAGeneral"></a></h3>
+    <p id="GAGroups">This document defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chartered-group">chartered groups</dfn>: </p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsWG"><a href="#GroupsWG" id="ref-for-GroupsWG⑦⑦">Working Groups</a></dfn>. 
+     <dd>
+       Working Groups typically produce deliverables
+			(e.g., <a href="#rec-advance">Recommendation Track technical reports</a>,
+			software,
+			test suites,
+			and reviews of the deliverables of other groups)
+			as defined in their <a href="#WGCharter">charter</a>. 
+      <p>Working Groups have additional participation requirements
+			described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			see particularly the “<a href="https://www.w3.org/policies/patent-policy/#sec-Obligations">Licensing Obligations of Working Group Participants</a>”
+			and the patent claim exclusion process
+			in “<a href="https://www.w3.org/policies/patent-policy/#sec-Exclusion">Exclusion From W3C RF Licensing Requirements</a>”.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsIG"><a href="#GroupsIG" id="ref-for-GroupsIG①③">Interest Groups</a></dfn>. 
+     <dd>
+       The primary goal of an Interest Group
+			is to bring together people who wish to evaluate potential Web technologies and policies.
+			An Interest Group is a forum for the exchange of ideas. 
+      <p>Interest Groups do not publish <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑤">Recommendation Track technical reports</a>;
+			but can publish <a href="#WGNote" id="ref-for-WGNote">technical reports on the Note Track</a>.</p>
+    </dl>
+    <h4 class="heading settled" data-level="3.4.1" id="ReqsAllGroups"><span class="secno">3.4.1. </span><span class="content"> Requirements for All Chartered Groups</span><a class="self-link" href="#ReqsAllGroups"></a></h4>
+    <p>Each group <em class="rfc2119">must</em> have a <a data-link-type="dfn" href="#charter" id="ref-for-charter">charter</a>.
+	Requirements for the charter depend on the group type.
+	All group charters <em class="rfc2119">must</em> be public
+	(even if other proceedings of the group are <a href="#Member-only" id="ref-for-Member-only①⑤">Member-only</a>).</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GeneralChairs">Chair</dfn> (or co-Chairs)
+	to facilitate effective discussion and coordinate the group’s activities.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③⑧">Team</a> appoints (and re-appoints) Chairs for all groups.
+	The Chair is a <a href="#member-rep">Member representative</a>,
+	a <a href="#Team">Team representative</a>,
+	or an <a href="#invited-expert-wg">Invited Expert</a> (invited by the <a data-link-type="dfn" href="#team" id="ref-for-team③⑨">Team</a>).
+	The requirements of this document that apply to those types of participants apply to Chairs as well.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/guide/chair/role">role of the Chair</a> <a data-link-type="biblio" href="#biblio-chair" title="W3C Working/Interest Group Chair">[CHAIR]</a> is described
+	in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="TeamContact">Staff Contact</dfn> (also known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-contact">Team Contact</dfn>),
+	who acts as the interface between the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③">Chair</a>,
+	group participants,
+	and the rest of the <a data-link-type="dfn" href="#team" id="ref-for-team④⓪">Team</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/guide/teamcontact/role">role of the Staff Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> is described in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs④">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①">Staff Contact</a> of a group <em class="rfc2119">should not</em> be the same individual.</p>
+    <p>Each group <em class="rfc2119">must</em> have an archived mailing list
+	for formal group communication
+	(e.g., for meeting announcements and <a data-link-type="dfn" href="#minutes" id="ref-for-minutes①">minutes</a>,
+	documentation of decisions,
+	and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②">Formal Objections</a> to decisions).
+	It is the responsibility of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑤">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact②">Staff Contact</a> to ensure that new participants are subscribed to all relevant mailing lists.
+	Refer to the list of <a href="https://www.w3.org/groups/">group mailing lists</a> <a data-link-type="biblio" href="#biblio-group-mail" title="Group mailing lists">[GROUP-MAIL]</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑥">Chair</a> <em class="rfc2119">may</em> form task forces
+	(composed of group participants)
+	to carry out assignments for the group.
+	The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group’s charter.
+	A group <em class="rfc2119">should</em> document the process it uses
+	to create task forces
+	(e.g., each task force might have an informal "charter").
+	Task forces do not publish <a href="#Reports">technical reports</a>;
+	the Working Group <em class="rfc2119">may</em> choose to publish their results as part of a technical report. </p>
+    <h4 class="heading settled" data-level="3.4.2" id="group-participation"><span class="secno">3.4.2. </span><span class="content"> Participation in Chartered Groups</span><a class="self-link" href="#group-participation"></a></h4>
+    <p>There are three types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="wgparticipant">participants in a Working Group</dfn>: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
+	and <a href="#Team">Team representatives</a> (including the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact③">Staff Contact</a>).</p>
+    <p>There are four types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="igparticipant">participants in an Interest Group</dfn>:
+	the same three types as for Working Groups plus,
+	for an Interest Group where the only <a href="#ig-mail-only">participation requirement is mailing list subscription</a>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="public-participant-ig">public participants</dfn>.</p>
+    <p>Except where noted in this document or in a group charter,
+	all participants share the same rights and responsibilities in a group;
+	see also the <a href="#ParticipationCriteria">individual participation criteria</a>.</p>
+    <p>A participant <em class="rfc2119">may</em> represent more than one organization
+	in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①">Interest Group</a>.
+	Those organizations <em class="rfc2119">must</em> all be members of the group.</p>
+    <p>An individual <em class="rfc2119">may</em> become
+	a Working or Interest Group participant
+	at any time during the group’s existence.
+	See also relevant requirements in
+	“Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>On an exceptional basis,
+	a Working or Interest Group participant <em class="rfc2119">may</em> designate
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mtg-substitute">substitute</dfn> to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑦">Chair</a>.
+	The substitute <em class="rfc2119">may</em> act on behalf of the participant,
+	including for <a href="#Votes">votes</a>.
+	For the substitute to vote,
+	the participant <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑧">Chair</a> in writing in advance.</p>
+    <p>To allow rapid progress,
+	Working Groups are intended to be small
+	(typically fewer than 15 people)
+	and composed of experts in the area defined by the charter.
+	In principle,
+	Interest Groups have no limit on the number of participants.
+	When a Working Group grows too large to be effective,
+	W3C <em class="rfc2119">may</em> split it into an Interest Group
+	(a discussion forum)
+	and a much smaller Working Group
+	(a core group of highly dedicated participants).</p>
+    <h4 class="heading settled" data-level="3.4.3" id="chartered-group-participants"><span class="secno">3.4.3. </span><span class="content"> Types of Participants in Chartered Groups</span><a class="self-link" href="#chartered-group-participants"></a></h4>
+    <h5 class="heading settled" data-level="3.4.3.1" id="member-rep-wg"><span class="secno">3.4.3.1. </span><span class="content"> Member Representative in a Working Group</span><a class="self-link" href="#member-rep-wg"></a></h5>
+    <p>An individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-a-working-group">Member representative in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Advisory Committee representative of the Member in question
+			has designated the individual as a Working Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a Member representative in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤">Working Group</a>,
+	an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①①">Advisory Committee representative</a> <em class="rfc2119">must</em> provide the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑨">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact④">Staff Contact</a> with all of the following <span id="member-rep-info">information</span>,
+	in addition to any other information required by the <a href="#cfp">Call for Participation</a> and charter
+	(including the participation requirements of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>):</p>
+    <ol>
+     <li> The name of the W3C Member the individual represents
+			and whether the individual is an employee of that Member organization; 
+     <li> A statement that the individual accepts the participation terms
+			set forth in the charter
+			(with an indication of charter date or version); 
+     <li> A statement that the Member will provide the necessary financial support for participation
+			(e.g., for travel, telephone calls, and conferences). 
+    </ol>
+    <p>A Member participates in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥">Working Group</a> from the moment the first Member representative joins the group
+	until either of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Member <a href="#resignation">resigns</a> from the Working Group;
+			this is done through the Member’s Advisory Committee representative. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.2" id="member-rep-ig"><span class="secno">3.4.3.2. </span><span class="content"> Member Representative in an Interest Group</span><a class="self-link" href="#member-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-an-interest-group">Member representative in an Interest Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①②">Advisory Committee representative</a> of the Member in question has designated the individual
+			as an Interest Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a <a data-link-type="dfn" href="#member-representative-in-an-interest-group" id="ref-for-member-representative-in-an-interest-group">Member representative in an Interest Group</a>,
+	the Advisory Committee representative <em class="rfc2119">must</em> follow the instructions
+	in the <a href="#cfp">Call for Participation</a> and charter.</p>
+    <p>Member participation in an Interest Group ceases under the same conditions as for a Working Group.</p>
+    <h5 class="heading settled" data-level="3.4.3.3" id="invited-expert-wg"><span class="secno">3.4.3.3. </span><span class="content"> Invited Expert in a Working Group</span><a class="self-link" href="#invited-expert-wg"></a></h5>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⓪">Chair</a> <em class="rfc2119">may</em> invite an individual with a particular expertise
+	to participate in a Working Group.
+	This individual <em class="rfc2119">may</em> represent an organization in the group
+	(e.g., if acting as a liaison with another organization).</p>
+    <p>An individual is an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-a-working-group">Invited Expert in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Chair has designated the individual as a group participant, 
+     <li> the Staff Contact has agreed with the Chair’s choice, and 
+     <li> the individual has provided the <a href="#inv-expert-info" id="ref-for-inv-expert-info①">information required of an Invited Expert</a> to the Chair and Staff Contact. 
+    </ul>
+    <p>To designate an individual as an Invited Expert in a Working Group,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①①">Chair</a> <em class="rfc2119">must</em> inform the Staff Contact
+	and provide rationale for the choice.
+	When the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①②">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑤">Staff Contact</a> disagree about a designation,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑤">CEO</a> determines
+	whether the individual will be invited to participate in the Working Group.</p>
+    <p>To <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="inv-expert-info">participate in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦">Working Group</a> as an Invited Expert</dfn>,
+	an individual <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> identify the organization, if any, the individual represents as a participant in this group, 
+     <li> agree to the terms of the <a href="https://www.w3.org/invited-experts/agreement-2023/">invited expert and collaborators agreement</a> <a data-link-type="biblio" href="#biblio-collaborators-agreement" title="Invited expert and collaborators agreement">[COLLABORATORS-AGREEMENT]</a>, 
+     <li> accept the participation terms set forth in the charter,
+			including the participation requirements of
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			especially in “Note on Licensing Commitments for Invited Experts”
+			and in “Disclosure”,
+			indicating a specific charter date or version, 
+     <li> disclose whether the individual is an employee of a W3C Member;
+			see the <a href="#coi">conflict of interest policy</a>, 
+     <li> provide a statement of who will provide the necessary financial support
+			for the individual’s participation
+			(e.g., for travel, telephone calls, and conferences), and 
+     <li> if the individual’s employer (including a self-employed individual)
+			or the organization the individual represents
+			is not a W3C Member,
+			indicate whether that organization intends to join W3C.
+			If the organization does not intend to join W3C,
+			indicate reasons the individual is aware of for this choice. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①③">Chair</a> <em class="rfc2119">should not</em> designate as an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group">Invited Expert in a Working Group</a> an individual who is an employee of a W3C Member.
+	The Chair <em class="rfc2119">must not</em> use Invited Expert status
+	to circumvent participation limits imposed by the <a href="#WGCharter">charter</a>.</p>
+    <p>An Invited Expert participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Chair or <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑥">CEO</a> withdraws the invitation to participate, or 
+     <li> the individual <a href="#resignation">resigns</a>. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.4" id="invited-expert-ig"><span class="secno">3.4.3.4. </span><span class="content"> Invited Expert in an Interest Group</span><a class="self-link" href="#invited-expert-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	the participation requirements for an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-an-interest-group">Invited Expert in an Interest Group</dfn> are the same as those for an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group①">Invited Expert in a Working Group</a>.</p>
+    <h5 class="heading settled" data-level="3.4.3.5" id="team-rep-wg"><span class="secno">3.4.3.5. </span><span class="content"> Team Representative in a Working Group</span><a class="self-link" href="#team-rep-wg"></a></h5>
+    <p>An individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-representative-in-a-working-group">Team representative in a Working Group</dfn> when so designated by W3C management.
+	Team representatives both contribute to the technical work
+	and help ensure the group’s proper integration with the rest of W3C.</p>
+    <p>A Team representative participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> W3C management changes Team representation by sending email to the Chair,
+			copying the group mailing list. 
+    </ul>
+    <p>The Team participates in a Working Group
+	from the moment the creation of the group is announced
+	until the group closes.</p>
+    <h5 class="heading settled" data-level="3.4.3.6" id="team-rep-ig"><span class="secno">3.4.3.6. </span><span class="content"> Team Representative in an Interest Group</span><a class="self-link" href="#team-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-representative-in-an-interest-group">Team representative in an Interest Group</dfn> when so designated by W3C management.</p>
+    <h2 class="heading settled" data-level="4" id="group-lifecycle"><span class="secno">4. </span><span class="content"> Lifecycle of Chartered Groups</span><a class="self-link" href="#group-lifecycle"></a></h2>
+    <p>W3C creates <a data-link-type="dfn" href="#charter" id="ref-for-charter①">charters</a> for <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group">chartered groups</a> based on W3C community interest.
+	W3C fosters awareness of <a data-link-type="dfn" href="#charter" id="ref-for-charter②">charters</a>,
+	improves their quality,
+	and gauges Membership support in two formal phases:</p>
+    <ul>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement">refinement</a> phase helps ensure <a data-link-type="dfn" href="#charter" id="ref-for-charter③">charters</a> are mission-aligned,
+reflect community input and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus">consensus</a>,
+and have been well-socialized
+and <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review">widely reviewed</a>.</p>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#charter" id="ref-for-charter④">Charters</a> then are formally approved through an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review">AC Review</a> and <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①">W3C Decision</a> (see <a href="#CharterReview">§ 4.4 Charter Review and Approval</a>).</p>
+    </ul>
+    <h3 class="heading settled" data-level="4.1" id="charter-initiation"><span class="secno">4.1. </span><span class="content"> Initiating Charter Refinement</span><a class="self-link" href="#charter-initiation"></a></h3>
+    <p><a data-link-type="dfn" href="#charter" id="ref-for-charter⑤">Charters</a> can originate in many venues,
+	including existing <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧">Working</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG②">Interest Groups</a>,
+	Community Groups,
+	and from the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member②">Membership</a>.
+	Prior to the formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①">refinement</a> phase,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④①">Team</a> engages with those various parties
+	to help prepare <a data-link-type="dfn" href="#charter" id="ref-for-charter⑥">charters</a> for broader audiences.</p>
+    <p>Formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement②">charter refinement</a> (see below) is initiated
+	by the <a data-link-type="dfn" href="#team" id="ref-for-team④②">Team</a> sending a <a data-link-type="dfn" href="#charter-review-notice" id="ref-for-charter-review-notice">charter review notice</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①①">Advisory Committee</a>,
+	to the public,
+	and, in the case of rechartering, to the affected <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group②">Group</a>.</p>
+    <p>This <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-review-notice">charter review notice</dfn> must include:</p>
+    <ul>
+     <li data-md>
+      <p>A short summary of the proposal.</p>
+     <li data-md>
+      <p>The location of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-draft">charter draft</dfn>, which must be public.</p>
+     <li data-md>
+      <p>How to participate in the discussion of this <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft">charter draft</a> and where to file issues.</p>
+     <li data-md>
+      <p>The expected duration of the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement③">charter refinement</a> phase,
+which must not be less than 28 days,
+and should not be more than 6 months.</p>
+     <li data-md>
+      <p>Who the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator">Chartering Facilitator</a> is.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④③">Team</a> is responsible for initiating <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement④">charter refinement</a> at its discretion, in consideration of discussions with the community.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①③">Advisory Committee representative</a> <em class="rfc2119">may</em> formally request
+	that the <a data-link-type="dfn" href="#team" id="ref-for-team④④">Team</a> initiate <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑤">charter refinement</a>.
+	The Team <em class="rfc2119">may</em> deny such a request
+	if it thinks the proposal is insufficiently mature,
+	does not align with W3C’s scope and mission,
+	or otherwise does not meet the charter assessment criteria
+	described in the Guide (see <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/guide/process/charter"><cite>How to Create a Working Group or Interest Group</cite></a>),
+	and <em class="rfc2119">must</em> reply with its rationale.
+	This rejection is a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①">Team Decision</a>,
+	and can be appealed only by 5 or more <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member③">Members</a>,
+	through their <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①④">Advisory Committee representative</a>,
+	formally objecting to the decision within 8 weeks of the decision being announced.
+	In this case the <a data-link-type="dfn" href="#team" id="ref-for-team④⑤">Team</a> <em class="rfc2119">must</em> start an <a data-link-type="dfn" href="#appeal-vote" id="ref-for-appeal-vote">appeal vote</a> on whether to overturn the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision②">Team Decision</a>.
+	(No action is required to be taken when fewer than 5 members object.)</p>
+    <h3 class="heading settled" data-level="4.2" id="charter-development"><span class="secno">4.2. </span><span class="bs-old-id" id="WGCharterDevelopment"></span><span class="content"> Charter Refinement</span><a class="self-link" href="#charter-development"></a></h3>
+    <p>During <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-refinement">charter refinement</dfn>,
+	the W3C community,
+	under the guidance of the <a data-link-type="dfn" href="#team" id="ref-for-team④⑥">Team</a>,
+	further develops the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft①">charter draft</a> with the goal of achieving <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①">consensus</a> on the proposal.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="chartering-facilitator">Chartering Facilitator</dfn>—​who is chosen (and <em class="rfc2119">may</em> be replaced) by the <a data-link-type="dfn" href="#team" id="ref-for-team④⑦">Team</a>—​is responsible for seeking community <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②">consensus</a> among those participating in the refinement process
+	and making decisions reflecting that <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus③">consensus</a>.
+	In cases where <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus④">consensus</a> cannot be found,
+	the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator①">Chartering Facilitator</a> <em class="rfc2119">may</em> ask the <a data-link-type="dfn" href="#team" id="ref-for-team④⑧">Team</a> to make a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision③">Team Decision</a>,
+	and <em class="rfc2119">must</em> document the rationale for the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator②">Chartering Facilitator</a> is not necessarily the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①④">Chair</a> of the <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group①">group</a> being chartered.</p>
+    <p>During <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑥">charter refinement</a>:</p>
+    <ul>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①">Wide review</a> of the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft②">charter draft</a> is initiated and completed.</p>
+     <li data-md>
+      <p>All issues filed against the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft③">charter draft</a> must be <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed">formally addressed</a>,
+and their resolutions tracked in a disposition of comments
+highlighting any issues not resolved by consensus.</p>
+    </ul>
+    <p>Before the end of the announced duration
+	for the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑦">charter refinement</a> phase,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④⑨">Team</a> (informed by the work of the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator③">Chartering Facilitator</a>) <em class="rfc2119">must</em> <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision④">decide</a> which of the following to do:</p>
+    <ul>
+     <li data-md>
+      <p>Complete charter refinement by initiating <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①">AC Review</a> of the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft④">charter draft</a>.</p>
+     <li data-md>
+      <p>Abandon the proposal.</p>
+     <li data-md>
+      <p>Extend the charter refinement period.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⓪">Team</a> <em class="rfc2119">must</em> announce its <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑤">decision</a> with the same visibility as the initial <a data-link-type="dfn" href="#charter-review-notice" id="ref-for-charter-review-notice①">charter review notice</a>,
+	and <em class="rfc2119">must</em> include a rationale
+	if they are not initiating <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②">AC Review</a>.
+	Reaching the end of the announced period (including any announced extension)
+	with no announced decision
+	is considered a de-facto <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑥">Team decision</a> to abandon the proposal.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤①">Team</a> <em class="rfc2119">may</em> revise such a decision
+	by announcing an alternative decision.</p>
+    <p><a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③">Formal Objections</a> filed during the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑧">charter refinement</a> phase
+	are specially handled:</p>
+    <ul>
+     <li data-md>
+      <p>Objections to decisions pertaining to the content of the charter,
+as well as objections to initiating the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③">AC Review</a>,
+are considered registered at the close of the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review④">Advisory Committee Review</a> of the charter,
+and are registered against that <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision②">W3C Decision</a>.</p>
+      <p class="note" role="note"><span class="marker">Note:</span> This enables all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④">Formal Objections</a> on the same proposed <a data-link-type="dfn" href="#charter" id="ref-for-charter⑦">charter</a> to be handled together.</p>
+     <li data-md>
+      <p>Objections to abandoning the proposal or to extending the refinement period can be appealed only if 5 or more Members,
+through their <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑤">Advisory Committee representative</a>,
+formally object to the decision within 8 weeks of the decision.
+In this case,
+the <a data-link-type="dfn" href="#team" id="ref-for-team⑤②">Team</a> <em class="rfc2119">must</em> do one of the following:</p>
+      <ul>
+       <li data-md>
+        <p>Abide by the objectors' request, if they all agree on the
+alternative course of action (e.g., to abandon,
+extend, or complete charter refinement).</p>
+       <li data-md>
+        <p>Initiate an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑤">AC Review</a> to formally solicit the input of
+the community and take a W3C Decision on the subsequent
+course of action.</p>
+       <li data-md>
+        <p>Convene a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③">Council</a> to decide the subsequent course of action.</p>
+      </ul>
+      <p>(No action is required to be taken when fewer than 5 members object.)</p>
+     <li data-md>
+      <p>Any other objections are processed normally (See <a href="#addressing-fo">§ 5.6 Addressing Formal Objections</a>).</p>
+    </ul>
+    <h3 class="heading settled" data-level="4.3" id="WGCharter"><span class="secno">4.3. </span><span class="content"> Content of a Charter</span><a class="self-link" href="#WGCharter"></a></h3>
+    <p>A Working Group or Interest Group <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="charter">charter</dfn> <em class="rfc2119">must</em> include all of the following information.</p>
+    <ul>
+     <li> The group’s mission
+			(e.g., develop a technology or process, review the work of other groups). 
+     <li> The scope of the group’s work and criteria for success. 
+     <li> The duration of the proposed charter for the group. 
+     <li> The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software). 
+     <li>
+       Expected milestone dates where available. 
+      <p class="note" role="note"><span class="marker">Note:</span> A charter does not need to include
+			schedules for review of other group’s deliverables.</p>
+     <li> The process for the group to approve the release of deliverables
+			(including intermediate results). 
+     <li> Any dependencies by groups within or outside of W3C on the deliverables of this group.
+			For any dependencies, the charter <em class="rfc2119">must</em> specify
+			the mechanisms for communication about the deliverables. 
+     <li> Any dependencies of this group on other groups within or outside of W3C.
+			Such dependencies include interactions with <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a>. 
+     <li> The <a href="#confidentiality-levels">level of confidentiality</a> of the group’s proceedings and deliverables. 
+     <li> The name and affiliation of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑤">Chair</a> or co-Chairs. 
+     <li> Meeting mechanisms and expected frequency. 
+     <li> If known,
+			the date of the first <a href="#ftf-meeting" id="ref-for-ftf-meeting①">face-to-face meeting</a>.
+			The date of the first face-to-face meeting of a proposed group <em class="rfc2119">must not</em> be sooner than <span class="time-interval">eight weeks</span> after the date of the proposal. 
+     <li> Communication mechanisms to be employed within the group,
+			between the group and the rest of W3C,
+			and with the general public. 
+     <li> Any voting procedures or requirements
+			other than those specified in <a href="#Votes">§ 5.2.3 Deciding by Vote</a>. 
+     <li> An estimate of the expected time commitment from participants. 
+     <li> The expected time commitment and level of involvement by the Team
+			(e.g., to track developments,
+			write and edit technical reports,
+			develop code,
+			or organize pilot experiments). 
+     <li> Intellectual property information.
+			What are the intellectual property (including patents and copyright)
+			considerations affecting the success of the Group?
+			In particular, is there any reason to believe
+			that it will be difficult to meet the Royalty-Free licensing goals
+			in “Licensing Goals for W3C Specifications”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>? 
+    </ul>
+    <p>See also the charter requirements in “Licensing Goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>For every Recommendation Track deliverable
+	that continues work on a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report">technical report</a> published under any other Charter (including a predecessor group of the same name),
+	for which there is at least an existing <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd">First Public Working Draft</a> the description of that deliverable in the proposed charter of the adopting Working Group <em class="rfc2119">must</em> provide the following information:</p>
+    <ul>
+     <li> The title,
+			stable URL,
+			and publication date of the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD">Working Draft</a> or other Recommendation-track document
+			that will serve as the basis for work on the deliverable
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="adopted-draft">Adopted Draft</dfn>”); 
+     <li> The title,
+			stable URL,
+			and publication date of the document
+			that was used as the basis for its most recent Exclusion Opportunity
+			as per
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft">Exclusion Draft</dfn>”); and 
+     <li> The stable URL of the Working Group charter
+			under which the Exclusion Draft was published
+			(labeled the “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft-charter">Exclusion Draft Charter</dfn>”). 
+    </ul>
+    <p>All of the above data <em class="rfc2119">must</em> be identified
+	in the adopting Working Group’s charter using the labels indicated.</p>
+    <p>The <a data-link-type="dfn" href="#adopted-draft" id="ref-for-adopted-draft">Adopted Draft</a> and the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft">Exclusion Draft</a> <em class="rfc2119">must</em> each be adopted in their entirety and without any modification.
+	The proposed charter <em class="rfc2119">must</em> state
+	the dates on which the Exclusion Opportunity
+	that arose on publishing the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft①">Exclusion Draft</a> began and ended.
+	As per “Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	this potentially means that exclusions can only be made immediately on joining a Working Group.</p>
+    <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding participation,
+	including specifying
+	that the <span id="ig-mail-only">only requirement for participation (by anyone) in
+	the Interest Group is subscription to the Interest Group mailing list</span>.
+	This type of Interest Group <em class="rfc2119">may</em> have <a href="#public-participant-ig" id="ref-for-public-participant-ig">public participants</a>. </p>
+    <p>A charter <em class="rfc2119">may</em> include
+	provisions other than those required by this document.
+	The charter <em class="rfc2119">should</em> highlight
+	whether additional provisions impose constraints
+	beyond those of the W3C 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>
+    <h3 class="heading settled" data-level="4.4" id="CharterReview"><span class="secno">4.4. </span><span class="content"> Charter Review and Approval</span><a class="self-link" href="#CharterReview"></a></h3>
+    <h4 class="heading settled" data-level="4.4.1" id="charter-major-changes"><span class="secno">4.4.1. </span><span class="content"> New Charters and Major Changes</span><a class="self-link" href="#charter-major-changes"></a></h4>
+    <p>Any new <a data-link-type="dfn" href="#charter" id="ref-for-charter⑧">charter</a> (including re-chartering of existing <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group②">chartered groups</a>)
+	and any change that is not a <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes">minor change</a> (per <a href="#charter-minor-changes">§ 4.4.2 Minor Changes to Active Charters</a>) to an already-approved <a data-link-type="dfn" href="#charter" id="ref-for-charter⑨">charter</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG③">Interest Group</a> <em class="rfc2119">must</em> be approved by a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision③">W3C Decision</a> following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑥">AC Review</a> of that <a data-link-type="dfn" href="#charter" id="ref-for-charter①⓪">charter</a>.
+	Modifications to a <a data-link-type="dfn" href="#charter" id="ref-for-charter①①">charter</a> <em class="rfc2119">should</em> have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑤">consensus</a> of the group.</p>
+    <p>The review period <em class="rfc2119">must</em> be at least 28 days.
+	Any <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑥">Advisory Committee representative</a> <em class="rfc2119">may</em> request an extended review period
+	in response to the Call for Review;
+	upon receipt of any such request,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤③">Team</a> <em class="rfc2119">must</em> extend the review period
+	to at least 60 days.</p>
+    <p>The Call for Review of a modified charter <em class="rfc2119">must</em> highlight important changes
+	(e.g., regarding changes in scope, deliverables, or resource allocation)
+	and <em class="rfc2119">must</em> include rationale for those changes.</p>
+    <p>The Call for Review of a new or modified charter <em class="rfc2119">must</em> include a disposition of comments received during the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑨">charter refinement</a> process,
+	highlighting any issues that were closed despite sustained objections.</p>
+    <h4 class="heading settled" data-level="4.4.2" id="charter-minor-changes"><span class="secno">4.4.2. </span><span class="content"> Minor Changes to Active Charters</span><a class="self-link" href="#charter-minor-changes"></a></h4>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change">Editorial changes</a> or <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change">substantive changes</a> to a <a data-link-type="dfn" href="#charter" id="ref-for-charter①②">charter</a> (including <a href="#charter-extension">extensions</a>)
+	that do not affect the scope of the group’s work
+	or the way the group functions in any significant way
+	are deemed <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minor-changes">minor changes</dfn> and <em class="rfc2119">may</em> be approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑦">Team Decision</a>,
+	in which case they do not require <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①⓪">charter refinement</a> nor <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑦">Advisory Committee Review</a>.
+	Any change to the scope of the <a data-link-type="dfn" href="#charter" id="ref-for-charter①③">charter</a> or addition of a new <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track">REC track</a> deliverable
+	that does not fall within the scope of an existing deliverable
+	is a major, not <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes①">minor</a>, change.
+	The following are examples of <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes②">minor changes</a>:
+	the renaming or restructuring (e.g. splitting or combining) of existing in-scope deliverables,
+	the addition of new <a href="#note-track">Note track</a> deliverables that help explain the group’s work,
+	a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑥">Staff Contact</a>,
+	or a change of <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑥">Chair</a>. <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes③">Minor changes</a>, other than a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑦">Staff Contact</a>, <em class="rfc2119">should</em> have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑥">consensus</a> of the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤④">Team</a> <em class="rfc2119">may</em> nevertheless choose
+	to initiate <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①①">charter refinement</a> and/or <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑧">Advisory Committee Review</a> when it thinks the changes would benefit from more scrutiny or explicit buy-in.</p>
+    <p>Though <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑨">Advisory Committee Review</a> is not required,
+	such changes <em class="rfc2119">must</em> still be announced
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①②">Advisory Committee</a>,
+	and to participants in the <a href="#wgparticipant" id="ref-for-wgparticipant①">Working</a> or <a href="#igparticipant" id="ref-for-igparticipant①">Interest</a> Group,
+	and a rationale must be provided.</p>
+    <h3 class="heading settled" data-level="4.5" id="cfp"><span class="secno">4.5. </span><span class="content"> Call for Participation in a Chartered Group</span><a class="self-link" href="#cfp"></a></h3>
+    <p>Deciding whether to adopt a proposed <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⓪">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG④">Interest Group</a> <a data-link-type="dfn" href="#charter" id="ref-for-charter①④">charter</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision④">W3C Decision</a>.
+	Charters <em class="rfc2119">may</em> be amended based on review comments
+	per <a href="#ACReviewAfter">§ 5.7.2 Determining the W3C Decision</a> before the Call for Participation.</p>
+    <p>If the decision is to charter the group,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑤">Team</a> <em class="rfc2119">must</em> issue a Call for Participation to the Advisory Committee.
+	For a new group, this announcement officially creates the group.
+	The announcement <em class="rfc2119">must</em> include a reference to the <a href="#WGCharter">charter</a>,
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑦">Chair(s)</a>,
+	and the name(s) of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑧">Staff Contact(s)</a>.</p>
+    <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).
+	When a group is re-chartered,
+	individuals participating in the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①①">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑤">Interest Group</a> before the new Call for Participation
+	may attend any meetings held within forty-five (45) days of the Call for Participation
+	even if they have not yet formally rejoined the group
+	(i.e., committed to the terms of the charter and patent policy).</p>
+    <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against the decision to create
+	or substantially modify
+	a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.6" id="charter-extension"><span class="secno">4.6. </span><span class="content"> Charter Extension</span><a class="self-link" href="#charter-extension"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑥">Team</a> <em class="rfc2119">may</em> decide
+	to extend a Working Group or Interest Group charter
+	with no other substantive modifications.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑦">Team</a> <em class="rfc2119">must</em> announce
+	such <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="charter extension" id="dfn-charter-extension">extensions</dfn> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①③">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate the new duration.
+	The announcement <em class="rfc2119">must</em> also include rationale for the extension,
+	a reference to the <a href="#WGCharter">charter</a>,
+	and the Group homepage
+	(which includes at least
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑧">Chair(s)</a>,
+	the name of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑨">Staff Contact</a>,
+	and instructions for joining the group).</p>
+    <p>After a charter extension,
+	Advisory Committee representatives
+	and the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑨">Chair</a> 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> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑧">Team decision</a> regarding the extension of a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.7" id="GeneralTermination"><span class="secno">4.7. </span><span class="content"> Chartered Group Closure</span><a class="self-link" href="#GeneralTermination"></a></h3>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①②">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑥">Interest Group</a> charter specifies a duration for the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑧">Team</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑦">TAG</a>, or the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②③">AB</a> <em class="rfc2119">may</em> propose to close a group
+	prior to the date specified in the charter in any of the following circumstances:</p>
+    <ul>
+     <li data-md>
+      <p>There are insufficient member resources to produce chartered deliverables
+or to maintain the group,
+according to priorities established within W3C.</p>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="https://www.w3.org/policies/patent-policy/#patent-advisory-group" id="ref-for-patent-advisory-group">Patent Advisory Group</a> concluded that the work <em class="rfc2119">should</em> be terminated.</p>
+     <li data-md>
+      <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑧">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②④">AB</a> determined that continuing operation of the chartered group or its work
+would be detrimental to W3C or its mission.</p>
+     <li data-md>
+      <p>The group produced all chartered deliverables ahead of schedule.</p>
+    </ul>
+    <p>Such a proposal to close a group must be accompanied by rationale,
+	and the proposal must be confirmed by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⓪">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑤">W3C Decision</a>.</p>
+    <p>Closing a Working Group has implications
+	with respect to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h2 class="heading settled" data-level="5" id="decisions"><span class="secno">5. </span><span class="content"> Decisions</span><a class="self-link" href="#decisions"></a></h2>
+    <p>W3C attempts to resolve issues through dialog.
+	Individuals who disagree strongly with a decision <em class="rfc2119">should</em> register with the Chair any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑤">Formal Objections</a>.</p>
+    <h3 class="heading settled" data-level="5.1" id="decision-types"><span class="secno">5.1. </span><span class="content"> Types of Decisions</span><a class="self-link" href="#decision-types"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⓪">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①③">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑦">Interest Group</a> has the prerogative
+	to make certain decisions based on their own judgment.
+	Such decisions are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chair-decisions">chair decisions</dfn>.</p>
+    <p>In contrast,
+	decisions taken by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②①">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑧">Interest Group</a> on the basis of having assessed the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑦">consensus</a> of the group
+	or following a vote (see <a href="#Votes">§ 5.2.3 Deciding by Vote</a>)
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="group decision | resolution" id="group-decision">group decisions</dfn> (also known as group “resolutions”).</p>
+    <p>Decisions made by members of the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑨">Team</a> in connection with this Process,
+	based on their own individual or collective judgement,
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Team Decision | Team&apos;s Decision" data-noexport id="team-decision">Team Decisions</dfn>.</p>
+    <p>In contrast,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-w3c-decision">W3C decision</dfn> is
+	determined by the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⓪">Team</a> on behalf of the W3C community
+	by <a href="#ACReviewAfter">assessing the consensus of the W3C Community</a> after an <a href="#ACReview">Advisory Committee review</a>.</p>
+    <h3 class="heading settled" data-level="5.2" id="consensus-building"><span class="secno">5.2. </span><span class="content"> Consensus Building</span><a class="self-link" href="#consensus-building"></a></h3>
+    <h4 class="heading settled" data-level="5.2.1" id="Consensus"><span class="secno">5.2.1. </span><span class="content"> Consensus</span><a class="self-link" href="#Consensus"></a></h4>
+    <p>Consensus is a core value of W3C.
+	To promote consensus,
+	the W3C process requires Chairs to ensure
+	that groups consider all legitimate views and objections,
+	and endeavor to resolve them,
+	whether these views and objections are expressed by the active participants of the group
+	or by others
+	(e.g., another W3C group,
+	a group in another organization,
+	or the general public).
+	Decisions <em class="rfc2119">may</em> be made during meetings
+	(<a href="#ftf-meeting" id="ref-for-ftf-meeting②">face-to-face</a> or <a href="#distributed-meeting" id="ref-for-distributed-meeting">distributed</a>)
+	as well as through <a href="#discussion-archiving">persistent text-based discussions</a>.</p>
+    <p>The following terms are used in this document
+	to describe the level of support for a decision among a set of eligible individuals:</p>
+    <dl>
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Consensus">Consensus</dfn>: 
+     <dd> A substantial number of individuals in the set
+			support the decision
+			and there is no sustained objection from anybody in the set.
+			Individuals in the set <em class="rfc2119">may</em> abstain.
+			Abstention is either an explicit expression of no opinion
+			or silence by an individual in the set. 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Unanimity">Unanimity</dfn>: 
+     <dd> The particular case of <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑧">consensus</a> where all individuals in the set support the decision
+			(i.e., no individual in the set abstains). 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Dissent">Dissent</dfn>: 
+     <dd> At least one individual in the set sustains an objection. 
+    </dl>
+    <p class="note" role="note"><span class="marker">Note:</span> A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑥">Formal Objection</a> always indicates a sustained objection,
+	but isn’t necessary to express it
+	(except in the context of formal <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①①">AC Reviews</a>).
+	Disagreement with a proposed decision,
+	however, does not always rise to the level of sustained objection,
+	as individuals could be willing to accept a decision
+	while expressing disagreement.</p>
+    <p>By default, the set of individuals eligible to participate in a decision is the set of group participants.
+	The Process Document does not require a quorum for decisions
+	(i.e., the minimal number of eligible participants required to be present before the Chair can call a question).
+	A charter <em class="rfc2119">may</em> include a quorum requirement for consensus decisions.</p>
+    <p>Where <a data-link-type="dfn" href="#def-Unanimity" id="ref-for-def-Unanimity">unanimity</a> is not possible,
+	a group <em class="rfc2119">should</em> strive to make <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑨">consensus</a> decisions
+	where there is significant support and few abstentions.
+	The Process Document does not require a particular percentage of eligible participants
+	to agree to a motion in order for a decision to be made.
+	To avoid decisions where there is widespread apathy,
+	(i.e., little support and many abstentions),
+	groups <em class="rfc2119">should</em> set minimum thresholds of active support before a decision can be recorded.
+	The appropriate percentage <em class="rfc2119">may</em> vary depending on the size of the group
+	and the nature of the decision.
+	A charter <em class="rfc2119">may</em> include threshold requirements for consensus decisions.
+	For instance, a charter might require a supermajority of eligible participants
+	(i.e., some established percentage above 50%)
+	to support certain types of consensus decisions.</p>
+    <div class="note" role="note">
+      Note: Chairs have substantial flexibility
+	in how they obtain and assess consensus among their groups.
+	Unless otherwise constrained by charter,
+	they can use modes including but not limited to explicit calls for consensus,
+	polls of participants,
+	“lazy consensus” in which lack of objection after sufficient notice is taken as assent;
+	they can also delegate and empower a document editor
+	to assess consensus on their behalf,
+	whether in general
+	or for specific pre-determined circumstances
+	(e.g. in non-controversial situations, for specific types of issues, etc.). 
+     <p>If questions or disagreements arise,
+	the final determination of consensus remains with the chair.</p>
+    </div>
+    <h4 class="heading settled" data-level="5.2.2" id="managing-dissent"><span class="secno">5.2.2. </span><span class="content"> Managing Dissent</span><a class="self-link" href="#managing-dissent"></a></h4>
+    <p>In some cases, even after careful consideration of all points of view,
+	a group might find itself unable to reach consensus.
+	The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②②">Chair</a> <em class="rfc2119">may</em> record a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent">dissent</a> so that the group can make progress
+	(for example, to produce a deliverable in a timely manner).
+	Dissenters cannot stop a group’s work
+	simply by saying that they cannot live with a decision.
+	When the Chair believes that the Group has duly considered
+	the legitimate concerns of dissenters as far as is possible and reasonable,
+	the group <em class="rfc2119">should</em> move on.</p>
+    <p>Groups <em class="rfc2119">should</em> favor proposals that create the weakest objections.
+	This is preferred over proposals that are supported by a large majority
+	but that cause strong objections from a few people.
+	As part of making a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent①">dissent</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②③">Chair</a> is expected to be aware of which participants work for the same
+	(or <a href="#MemberRelated">related</a>)
+	Member organizations and weigh their input accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Dissenters can escalate their sustained objection to a decision by registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑦">Formal Objection</a>.</p>
+    <h4 class="heading settled" data-level="5.2.3" id="Votes"><span class="secno">5.2.3. </span><span class="content"> Deciding by Vote</span><a class="self-link" href="#Votes"></a></h4>
+    <p>A group <em class="rfc2119">should</em> only conduct a vote to resolve a <em>substantive issue</em> after the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②④">Chair</a> has determined that all available means of <a href="#Consensus">reaching consensus</a> through technical discussion and compromise have failed,
+	and that a vote is necessary to break a deadlock.
+	In this case the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑤">Chair</a> <em class="rfc2119">must</em> record
+	(e.g., in the <a data-link-type="dfn" href="#minutes" id="ref-for-minutes②">minutes</a> of the meeting or in an archived email message):</p>
+    <ul>
+     <li> an explanation of the issue being voted on; 
+     <li> the decision to conduct a vote
+			(e.g., a simple majority vote) to resolve the issue; 
+     <li> the outcome of the vote; 
+     <li> any Formal Objections. 
+    </ul>
+    <p>In order to vote to resolve a substantive issue,
+	an individual <em class="rfc2119">must</em> be a group <a data-link-type="dfn" href="#participant" id="ref-for-participant①">participant</a>.
+	Each organization represented in the group <em class="rfc2119">must</em> have at most one vote,
+	even when the organization is represented by several participants in the group
+	(including Invited Experts).
+	For the purposes of voting:</p>
+    <ul>
+     <li> A Member or group of <a href="#MemberRelated">related Members</a> is considered a single organization. 
+     <li> The <a href="#Team">Team</a> is considered an organization. 
+    </ul>
+    <p>Unless the charter states otherwise, <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">may</em> vote.</p>
+    <p>If a participant is unable to attend a vote,
+	that individual <em class="rfc2119">may</em> authorize anyone at the meeting
+	to act as a proxy.
+	The absent participant <em class="rfc2119">must</em> inform the Chair in writing
+	who is acting as proxy, with written instructions on the use of the proxy.
+	For a Working Group or Interest Group,
+	see the related requirements regarding an individual
+	who attends a meeting as a <a href="#mtg-substitute" id="ref-for-mtg-substitute">substitute</a> for a participant.</p>
+    <p>A group <em class="rfc2119">may</em> vote for other purposes than to resolve a substantive issue.
+	For instance, the Chair often conducts a “straw poll” vote
+	as a means of determining whether there is consensus about a potential decision.</p>
+    <p>A group <em class="rfc2119">may</em> also vote to make a process decision.
+	For example,
+	it is appropriate to decide by simple majority
+	whether to hold a meeting in San Francisco or San Jose
+	(there’s not much difference geographically).
+	When simple majority votes are used to decide minor issues,
+	voters are <em class="rfc2119">not required</em> to state the reasons for votes,
+	and the group is <em class="rfc2119">not required</em> to record individual votes.</p>
+    <p>A group charter <em class="rfc2119">may</em> include formal voting procedures
+	(e.g., quorum or threshold requirements)
+	for making decisions about substantive issues.</p>
+    <h3 class="heading settled" data-level="5.3" id="formal-address"><span class="secno">5.3. </span><span class="content"> Formally Addressing an Issue</span><a class="self-link" href="#formal-address"></a></h3>
+    <p>In the context of this document,
+	a group has <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="formally-addressed">formally addressed</dfn> an issue when it has sent a public, substantive response
+	to the reviewer who raised the issue.
+	A substantive response is expected to include rationale for decisions
+	(e.g., a technical explanation, a pointer to charter scope, or a pointer to a requirements document).
+	The adequacy of a response is measured
+	against what a W3C reviewer would generally consider to be technically sound.
+	If a group believes that a reviewer’s comments result from a misunderstanding,
+	the group <em class="rfc2119">should</em> seek clarification before reaching a decision.</p>
+    <p>As a courtesy,
+	both Chairs and reviewers <em class="rfc2119">should</em> set expectations
+	for the schedule of responses and acknowledgments.
+	The group <em class="rfc2119">should</em> reply to a reviewer’s initial comments
+	in a timely manner.
+	The group <em class="rfc2119">should</em> set a time limit
+	for acknowledgment by a reviewer of the group’s substantive response;
+	a reviewer cannot block a group’s progress.
+	It is common for a reviewer to require a week or more
+	to acknowledge and comment on a substantive response.
+	The group’s responsibility to respond to reviewers
+	does not end once a reasonable amount of time has elapsed.
+	However, reviewers <em class="rfc2119">should</em> realize
+	that their comments will carry less weight
+	if not sent to the group in a timely manner.</p>
+    <p>Substantive responses <em class="rfc2119">should</em> be recorded.
+	The group <em class="rfc2119">should</em> maintain an accurate summary
+	of all substantive issues and responses to them
+	(e.g., in the form of an issues list with links to mailing list archives).</p>
+    <h3 class="heading settled" data-level="5.4" id="WGChairReopen"><span class="secno">5.4. </span><span class="content"> Reopening a Decision When Presented With New Information</span><a class="self-link" href="#WGChairReopen"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑥">Chair</a> <em class="rfc2119">may</em> reopen a decision
+	when presented with new information, including:</p>
+    <ul>
+     <li> additional technical information, 
+     <li> comments by email from participants who were unable to attend a scheduled meeting, 
+     <li> comments by email from meeting attendees
+			who chose not to speak out during a meeting
+			(e.g., so they could confer later with colleagues or for cultural reasons). 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑦">Chair</a> <em class="rfc2119">should</em> record
+	that a decision has been reopened,
+	and <em class="rfc2119">must</em> do so upon request from a group participant.</p>
+    <h3 class="heading settled" data-level="5.5" id="registering-objections"><span class="secno">5.5. </span><span class="bs-old-id" id="chair-decision-appeal"></span><span class="bs-old-id" id="wg-decision-appeal"></span><span class="bs-old-id" id="WGAppeals"></span><span class="bs-old-id" id="WGArchiveMinorityViews"></span><span class="content"> Registering Formal Objections</span><a class="self-link" href="#registering-objections"></a></h3>
+    <p>Any individual
+	(regardless of whether they are associated with a Member) <em class="rfc2119">may</em> appeal any decision made in connection with this Process
+	(except those having a different appeal process)
+	by registering a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="FormalObjection">Formal Objection</dfn> with the <a data-link-type="dfn" href="#team" id="ref-for-team⑥①">Team</a>.
+	Group participants <em class="rfc2119">should</em> inform
+	their <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①⓪">Staff Contact</a> as well as the group’s Chair(s).
+	The Staff Contact <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑦">CEO</a> when a group participant has also raised concerns about due process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> In this document, the term <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑧">Formal Objection</a> is used to emphasize this process implication:
+	Formal Objections receive formal consideration and a formal response.
+	The word “objection” used alone has its ordinary English connotations.
+	See <a href="#consensus-building">§ 5.2 Consensus Building</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑨">Formal Objection</a> <em class="rfc2119">must</em> include a summary of
+	the issue (whether technical or procedural),
+	the decision being appealed,
+	and the rationale for the objection.
+	It <em class="rfc2119">should</em> cite technical arguments
+	and propose changes that would remove the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⓪">Formal Objection</a>;
+	these proposals <em class="rfc2119">may</em> be vague or incomplete. <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①①">Formal Objections</a> that do not provide substantive arguments
+	or rationale are unlikely to receive serious consideration.
+	Counter-arguments,
+	rationales,
+	and decisions <em class="rfc2119">should</em> also be recorded.</p>
+    <p>No later than when the <a href="#team-fo-mediation">relevant Council is initiated</a>,
+	a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①②">Formal Objection</a> against a decision regarding a publicly-available document <em class="rfc2119">must</em> be made <a href="#confidentiality-change">publicly available</a>;
+	likewise, a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①③">Formal Objection</a> against a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①">Member-visible</a> decision <em class="rfc2119">must</em> be made <a href="#confidentiality-change">available to Members</a>.
+	A Call for Review to the Advisory Committee <em class="rfc2119">must</em> identify any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①④">Formal Objections</a> related to that review.
+	These requirements are waived
+	if the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑤">Formal Objection</a> is resolved to the satisfaction of the objector
+	before its <a href="#confidentiality-change">confidentiality is changed</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑥">Formal Objections</a> against matter in a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①">technical report</a> <a href="#adv-verif-reqs">are expected to be fully addressed</a> before <a href="#rec-advance">requesting advancement</a> of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②">technical report</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑦">Formal Objection</a> filed during an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①②">Advisory Committee Review</a> is considered registered at the close of the review period.</p>
+    <p>Registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑧">Formal Objection</a> initiates the process of <a href="#addressing-fo">addressing the Formal Objection</a>.
+	The resolution of a recorded Formal Objection—​whether by a Council decision, adoption of a consensus proposal, retraction of the Formal Objection, etc.—​must be recorded and made available at the same level of visibility as the record of the Formal Objection itself.</p>
+    <h3 class="heading settled" data-level="5.6" id="addressing-fo"><span class="secno">5.6. </span><span class="content"> Addressing Formal Objections</span><a class="self-link" href="#addressing-fo"></a></h3>
+    <h4 class="heading settled" data-level="5.6.1" id="team-fo-mediation"><span class="secno">5.6.1. </span><span class="content"> Investigation and Mediation by the Team</span><a class="self-link" href="#team-fo-mediation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑥②">Team</a> considers the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑨">Formal objection</a>,
+	researches the question,
+	interviews parties,
+	and so on,
+	to make sure the problem and the various viewpoints are well understood,
+	and to the extent possible,
+	to arrive at a recommended disposition.</p>
+    <p>In parallel, the Team <em class="rfc2119">should</em> start the steps necessary
+	to <a href="#council-convention">convene</a> a Council.</p>
+    <p>If the <a data-link-type="dfn" href="#team" id="ref-for-team⑥③">Team</a> can resolve the issue
+	to the satisfaction of the individual that filed the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⓪">Formal Objection</a>,
+	the individual withdraws the objection and the disposition process terminates.</p>
+    <p>Otherwise,
+	upon concluding that consensus cannot be found,
+	and no later than 90 days after the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②①">Formal Objection</a> being registered,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑥④">Team</a> <em class="rfc2119">must</em> deliver to the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council④">Council</a> a report
+	documenting its findings and attempts to find consensus,
+	and hand over the matter to the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑤">W3C Council</a>.</p>
+    <h4 class="heading settled" data-level="5.6.2" id="council"><span class="secno">5.6.2. </span><span class="content"> W3C Council</span><a class="self-link" href="#council"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-local-lt="Council" id="w3c-council">W3C Council</dfn> is the body convened to resolve <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②②">Formal Objections</a> by combining the capabilities and perspectives of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑤">AB</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑨">TAG</a>, and the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑤">Team</a>,
+	and is tasked with doing so in the best interests of the Web and W3C.</p>
+    <h5 class="heading settled" data-level="5.6.2.1" id="council-composition"><span class="secno">5.6.2.1. </span><span class="content"> Council Composition</span><a class="self-link" href="#council-composition"></a></h5>
+    <p>Each <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑥">W3C Council</a> is composed of the following members (excepting any <a href="#council-participation">renounced or dismissed</a>):</p>
+    <ul>
+     <li data-md>
+      <p>the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑧">CEO</a> or their chosen <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑥">Team</a> delegate</p>
+     <li data-md>
+      <p>the members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑥">Advisory Board</a></p>
+     <li data-md>
+      <p>the elected and appointed members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⓪">Technical Architecture Group</a></p>
+    </ul>
+    <p>Participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑦">W3C Council</a> <em class="rfc2119">must not</em> require attendance of <a data-link-type="dfn" href="#ftf-meeting" id="ref-for-ftf-meeting③">face-to-face meetings</a>.</p>
+    <p>A distinct instance of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑧">W3C Council</a> is convened for each decision being appealed or objected to.
+	The list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑨">Council</a> members evolves
+	as <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑦">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③①">TAG</a> terms start and end
+	until <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed">dismissal</a> and <a data-link-type="dfn" href="#renounce" id="ref-for-renounce">renunciation</a> are concluded,
+	at which point the membership of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⓪">Council</a> is fixed.
+	However, if the number of active members in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①①">Council</a> falls so low as to hinder effective and balanced deliberations,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair">Council Chair</a> <em class="rfc2119">should</em> dissolve the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①②">Council</a> and call for a new one to be convened.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> TAG and AB elections have no effect on the Council’s membership
+	once it is fixed.</p>
+    <p>A <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑦">Team</a> member is assigned
+	to act as the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-staff-contact"><span class="bs-old-id" id="council-team-contact"></span>Council Staff Contact</dfn>,
+	to support this Council
+	and to facilitate adherence to this Process.</p>
+    <h5 class="heading settled" data-level="5.6.2.2" id="council-delegation"><span class="secno">5.6.2.2. </span><span class="content"> Extraordinary Delegation</span><a class="self-link" href="#council-delegation"></a></h5>
+    <p>In extraordinary cases,
+	if they feel a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①③">Council</a> would not be the appropriate deciding body,
+	a member of the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑧">Team</a> (particularly the Legal Counsel) or
+	any potential Council member
+	may suggest that the decision for that specific Formal Objection be delegated
+	to the W3C Board of Directors,
+	to an officer of its corporation (such as the Legal Counsel),
+	or to one or more specific individuals from the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑨">Team</a>.
+	The potential Council members then <em class="rfc2119">may</em> confidentially discuss
+	and <em class="rfc2119">must</em> vote
+	whether to delegate the decision for that specific <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②③">Formal Objection</a>.
+	A decision to delegate <em class="rfc2119">must</em> be supported by a two-thirds supermajority vote
+	(i.e., at least twice as many votes in favor as against).
+	Delegation in such cases cannot be later revoked.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⓪">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①④">Advisory Committee</a> when a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②④">Formal Objection</a> has been delegated,
+	and to whom it has been delegated.</p>
+    <h5 class="heading settled" data-level="5.6.2.3" id="council-participation"><span class="secno">5.6.2.3. </span><span class="content"> Council Participation, Dismissal, and Renunciation</span><a class="self-link" href="#council-participation"></a></h5>
+    <p>A potential Council member may be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="dismissed | dismiss | dismissal" data-noexport id="dismissed">dismissed</dfn> from the Council.
+	In order to apply consistent criteria,
+	the potential Council members decide collectively
+	which reasons against service
+	rise to a sufficient level for a potential member to be <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed①">dismissed</a>.
+	No-one is automatically dismissed,
+	and individual recusal is not used in the Council. <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed②">Dismissal</a> applies to an individual person in the context of a specific Council,
+	and should be used rarely in order to preserve the greatest diversity on the Council.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> A W3C Council is a deliberative body whose purpose is
+	to find the best way forward for the Web and for W3C.
+	It is not a judicial body tasked with determining right or wrong.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦①">Team</a> <em class="rfc2119">must</em> draft a list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①④">Council</a> members,
+	with annotations of possible reasons for dismissal against each one.
+	The W3C community,
+	including members and team, and potential council members, <em class="rfc2119">must</em> be given an opportunity to contribute possible reasons to this list.
+	Affected members <em class="rfc2119">must</em> be given
+	an opportunity to respond to such comments about themselves.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦②">Team</a> may report comments verbatim
+	or may paraphrase them while preserving their intent;
+	they may also elide inappropriate comments,
+	such as any that violate applicable laws or the <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a>.</p>
+    <p>Before a Council forms,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦③">Team</a> presents the entire list of potential members
+	and collected reasons and responses
+	to the potential Council members,
+	who then consider for each potential member
+	whether that individual’s participation
+	would compromise the integrity of the Council decision,
+	and vote whether to dismiss that potential member.
+	No one is allowed to vote on their own dismissal;
+	each dismissal is enacted if there are at least as many ballots for as against.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since dismissal is individual,
+	when the decision being objected to was made by the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③②">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑧">AB</a> acting as a body,
+	the entire <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③③">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑨">AB</a> is not expected to be dismissed.</p>
+    <p>An individual <em class="rfc2119">may</em> also <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="renounce | renunciation" data-noexport id="renounce">renounce</dfn> their seat on a Council, for strong reason,
+	such as being forbidden by their employer to serve. The individual chooses the extent to which they explain
+	their renunciation.
+	Renunciation is disqualification from participation,
+	not abstention,
+	and <em class="rfc2119">should not</em> be used
+	to excuse an absence of participation.</p>
+    <p>Any person who has been <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed③">dismissed</a> or who <a data-link-type="dfn" href="#renounce" id="ref-for-renounce①">renounces</a> their seat
+	does not receive <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑤">Council</a> materials,
+	take part in its deliberations,
+	help in the determination of consensus,
+	or vote.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑥">W3C Council</a> <em class="rfc2110">may</em> still solicit and hear their testimony,
+	as they can of anyone else in the W3C community.</p>
+    <h5 class="heading settled" data-level="5.6.2.4" id="council-short-circuit"><span class="secno">5.6.2.4. </span><span class="content"> Short Circuit</span><a class="self-link" href="#council-short-circuit"></a></h5>
+    <p>The full Council process <em class="rfc2119">may</em> be short-circuited if
+	the Team recommends a resolution
+	and potential members of a Council who are not renouncing their seat
+	confirm it by a vote which results in both of the following:</p>
+    <ul>
+     <li data-md>
+      <p>at least 80% of them vote affirmatively to adopt this resolution</p>
+     <li data-md>
+      <p>none of them vote against adopting the resolution</p>
+    </ul>
+    <p>The request for confirmation <em class="rfc2119">must</em> be open for a period of at least two weeks,
+	or until every potential member of the Council not renouncing their seat
+	has voted,
+	whichever is shortest.</p>
+    <p>This step <em class="rfc2119">may</em> be run concurrently with <a href="#council-participation">§ 5.6.2.3 Council Participation, Dismissal, and Renunciation</a> and prior to choosing a <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair①">Chair</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This is intended for exceptional cases
+	that don’t seem to warrant a full Council response
+	because they are, for instance, too trivial, duplicative, etc.</p>
+    <h5 class="heading settled" data-level="5.6.2.5" id="council-chairing"><span class="secno">5.6.2.5. </span><span class="content"> Council Chairing</span><a class="self-link" href="#council-chairing"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Council Chair | Council Chair" data-noexport id="w3c-council-chair">Chair</dfn> of each W3C Council is chosen by its members,
+	by consensus if possible,
+	falling back to a vote if that fails.
+	The chair must be a member of that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑦">W3C Council</a>.
+	Chair selection happens during formation of each Council,
+	and <em class="rfc2119">must</em> be re-run
+	if requested by the <a data-link-type="dfn" href="#council-staff-contact" id="ref-for-council-staff-contact">Council Staff Contact</a> or by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑧">Chair</a> during the Council’s operation.</p>
+    <h5 class="heading settled" data-level="5.6.2.6" id="council-convention"><span class="secno">5.6.2.6. </span><span class="content"> Convening the Council</span><a class="self-link" href="#council-convention"></a></h5>
+    <p>When <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed④">dismissal</a>, <a data-link-type="dfn" href="#renounce" id="ref-for-renounce②">renunciation</a>, and
+	appointment of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair②">W3C Council Chair</a> have concluded,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team⑦④">Team</a>’s report has been delivered,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑧">W3C Council</a> is considered to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="convened">convened</dfn> and can start <a href="#council-deliberations">deliberations</a>.</p>
+    <p>If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑨">W3C Council</a> has not yet been <a data-link-type="dfn" href="#convened" id="ref-for-convened">convened</a> within 90 days of a Formal Objection
+	being <a href="#registering-objections">registered</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑨">Chairs</a> of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③④">TAG</a> and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⓪">AB</a> <em class="rfc2119">may</em> take independent action to ensure
+	that the <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed⑤">dismissal</a>, <a data-link-type="dfn" href="#renounce" id="ref-for-renounce③">renunciation</a>,
+	and <a href="#council-chairing">chair selection</a> processes have been run.
+	If a report from the Team is not delivered within those 90 days,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⓪">Council</a> is considered <a data-link-type="dfn" href="#convened" id="ref-for-convened①">convened</a> upon selection of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair③">Council Chair</a>.</p>
+    <h5 class="heading settled" data-level="5.6.2.7" id="council-deliberations"><span class="secno">5.6.2.7. </span><span class="content"> Council Deliberations</span><a class="self-link" href="#council-deliberations"></a></h5>
+    <p>Once <a data-link-type="dfn" href="#convened" id="ref-for-convened②">convened</a>,
+	the Council <em class="rfc2119">may</em> conduct additional research or analysis,
+	or request additional information or interviews from anyone,
+	including the Team.</p>
+    <p id="broker-consensus"> The Council <em class="rfc2119">may</em> further attempt to broker consensus on one or more of the formal objections,
+	which, if successful, would allow them to be resolved. </p>
+    <p>Otherwise,
+	after sufficient deliberation,
+	and with due consideration of each argument in the applicable <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑤">Formal Objections</a>,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②①">W3C Council</a> decides whether to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="affirm">affirm</dfn> or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="overturn">overturn</dfn> the decision being objected to.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②②">W3C Council</a> <em class="rfc2119">may</em> <a data-link-type="dfn" href="#affirm" id="ref-for-affirm">affirm</a> the decision
+	even if it agrees with some of the arguments made as part of a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑥">Formal Objection</a>.
+	When a decision is <a data-link-type="dfn" href="#affirm" id="ref-for-affirm①">affirmed</a>,
+	all Formal Objections against it are said to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="overrule" data-noexport id="overrule">overruled</dfn>.
+	Conversely,
+	aspects of Formal Objections that are found by the Council
+	to justify <a data-link-type="dfn" href="#overturn" id="ref-for-overturn">overturning</a> a decision
+	are said to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="upheld">upheld</dfn>.</p>
+    <p id="fo-mitigations"> When <a data-link-type="dfn" href="#overturn" id="ref-for-overturn①">overturning</a> a decision,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②③">Council</a> <em class="rfc2199">should</em> recommend a way forward.
+	If the overturned decision has already had consequences
+	pertaining to <a data-link-type="dfn" href="#upheld" id="ref-for-upheld">upheld</a> aspects of the Formal Objection(s)
+	(e.g., if the objection concerns material already in a published document)
+	the Council <em class="rfc2119">should</em> suggest how these consequences might be mitigated.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑤">Team</a> is responsible for making sure that adequate mitigations are enacted in a timely fashion;
+	and the <a data-link-type="dfn" href="#upheld" id="ref-for-upheld①">upheld</a> aspects of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑦">Formal Objection(s)</a> (as identified in the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report">Council Report</a>) are not considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fully-addressed">fully addressed</dfn> until then. </p>
+    <p class="note" role="note"><span class="marker">Note:</span> This does not create new powers for the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑥">Team</a>,
+	such as the ability to “unpublish” documents.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑦">Team</a>’s role is to ensure the responsible parties enact adequate mitigations,
+	by whatever means they already have at their disposal.</p>
+    <p>A Council <em class="rfc2119">may</em> form sub-groups for deliberation,
+	who may return with a recommendation,
+	but the full Council issues the final decision.
+	The decision of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②④">W3C Council</a> <em class="rfc2119">should</em> be unanimous,
+	and <em class="rfc2119">may</em> be issued under consensus.
+	However, if despite careful deliberation
+	a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑤">W3C Council</a> is unable to reach consensus,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair④">W3C Council Chair</a> may instead resort to voting.
+	In that case,
+	the decision is adopted if there are more ballots for than against;
+	in case of a tie,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑤">W3C Council Chair</a> determines the outcome.
+	However,
+	if the decision or proposal being objected to
+	originated with the TAG or AB,
+	then members of that group at the time the decision or proposal was made
+	must abstain in such a vote.
+	In case of a vote,
+	if two members of a Council who share the same affiliation cast an identical ballot,
+	then their ballots count as a one vote,
+	not two.</p>
+    <p>In the case of non-unanimous decisions,
+	members of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑥">W3C Council</a> who disagree with the Council’s decision <em class="rfc2119">may</em> write a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minority-opinion">Minority Opinion</dfn> explaining the reason for their disagreement.</p>
+    <p>The deliberations of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑦">W3C Council</a> are confidential to that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑧">W3C Council</a> and its <a data-link-type="dfn" href="#council-staff-contact" id="ref-for-council-staff-contact①">Council Staff Contact</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This confidentiality requirement is put in place so that
+	the Council can receive sensitive information in confidence
+	and to enable Council members to speak freely in their individual expert capacity
+	without pressure or fear of retaliation
+	by those involved in the dispute, business relations, their employer, etc.</p>
+    <p id="45-day-update"> If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑨">W3C Council</a> is unable to come to a conclusion within 45 days of being <a data-link-type="dfn" href="#convened" id="ref-for-convened③">convened</a>,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑥">W3C Council Chair</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑤">AC</a> of this delay
+	and of the status of the discussions.
+	The <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑦">W3C Council Chair</a> <em class="rfc2119">may</em> additionally make this report <a href="#confidentiality-levels">public</a>. </p>
+    <h5 class="heading settled" data-level="5.6.2.8" id="council-decision"><span class="secno">5.6.2.8. </span><span class="content"> Council Decision Report</span><a class="self-link" href="#council-decision"></a></h5>
+    <p>A <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⓪">Council</a> terminates by issuing a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-report">Council Report</dfn>,
+	which:</p>
+    <ul>
+     <li data-md>
+      <p><em class="rfc2119">must</em> state whether the Council <a data-link-type="dfn" href="#affirm" id="ref-for-affirm②">affirms</a> or <a data-link-type="dfn" href="#overturn" id="ref-for-overturn②">overturns</a> the decision being objected to.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> provide a rationale supporting its conclusion,
+which <em class="rfc2119">should</em> address each argument raised in the Formal Objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include any recommendation decided by the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③①">Council</a>.</p>
+     <li data-md>
+      <p>if the decision has been <a data-link-type="dfn" href="#overturn" id="ref-for-overturn③">overturned</a>, <em class="rfc2119">must</em> identify which aspects of the Formal Objection(s) are being <a data-link-type="dfn" href="#upheld" id="ref-for-upheld②">upheld</a>, and <em class="rfc2119">should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include the <a data-link-type="dfn" href="#minority-opinion" id="ref-for-minority-opinion">Minority Opinion(s)</a>, if any.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of those who were <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed⑥">dismissed</a> or <a data-link-type="dfn" href="#renounce" id="ref-for-renounce④">renounced</a> their seat as well as those who were qualified to serve.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of the individuals who participated in the final Council decision.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the number of votes for/against dismissing each participant.</p>
+     <li data-md>
+      <p><em class="rfc2119">may</em> report vote totals for the Council’s decision, if a formal vote was held.</p>
+     <li data-md>
+      <p><em class="rfc2119">must not</em> attribute any position to any individual on the Council.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑧">Team</a> <em class="rfc2119">must</em> maintain a <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/about/council/">public page on the W3C website</a> indexing all completed <a data-link-type="dfn" href="#council-report" id="ref-for-council-report①">Council Reports</a>.
+	If a Council decision is later overturned by an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal">AC Appeal</a>,
+	this <em class="rfc2119">must</em> also be mentioned. <a data-link-type="dfn" href="#council-report" id="ref-for-council-report②">Council Reports</a> <em class="rfc2119">must</em> be no more confidential
+	than the decision or document being objected to.</p>
+    <p>The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③②">Council</a> <em class="rfc2119">may</em> also issue a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="supplemental-confidential-council-report">Supplemental Confidential Council Report</dfn> with a more restricted <a href="#confidentiality-levels">level of confidentiality</a> than its main report
+	when it believes that additional commentary on confidential aspects of the case
+	would be informative.
+	However, the main <a data-link-type="dfn" href="#council-report" id="ref-for-council-report③">Council Report</a> <em class="rfc2119">should</em> be self-sufficient
+	and understandable without reference to Supplemental Confidential Council Reports.</p>
+    <h5 class="heading settled" data-level="5.6.2.9" id="council-appeals"><span class="secno">5.6.2.9. </span><span class="content"> Appealing Council Decisions</span><a class="self-link" href="#council-appeals"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑦">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①">Advisory Committee Appeal</a> of a Council decision issued in a <a data-link-type="dfn" href="#council-report" id="ref-for-council-report④">Council Report</a>.</p>
+    <h3 class="heading settled" data-level="5.7" id="ACReview"><span class="secno">5.7. </span><span class="content"> Advisory Committee Reviews and W3C Decisions</span><a class="self-link" href="#ACReview"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑥">Advisory Committee</a> formally confers its approval
+	on <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑤">charters</a>, <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③">technical reports</a>,
+	and other matters
+	through an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee review | AC Review" id="advisory-committee-review">Advisory Committee review</dfn> and its resulting <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑥">W3C Decision</a>.</p>
+    <h4 class="heading settled" data-level="5.7.1" id="ACReviewStart"><span class="secno">5.7.1. </span><span class="content"> Initiating an Advisory Committee Review</span><a class="self-link" href="#ACReviewStart"></a></h4>
+    <p>Each <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①③">Advisory Committee review</a> period
+	begins with a Call for Review from the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑨">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑦">Advisory Committee</a>.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="reviewform">Call for Review</dfn> describes the proposal,
+	raises attention to deadlines,
+	estimates when the decision will be available,
+	and includes other practical information.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⓪">Team</a> <em class="rfc2119">may</em> share its perspective on the proposal
+	in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform">Call for Review</a>.
+	Each Member organization <em class="rfc2119">may</em> send one review,
+	which <em class="rfc2119">must</em> be returned by its <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑧">Advisory Committee representative</a>.</p>
+    <p>For clarity,
+	in the context of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①④">AC Review</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent②">dissent</a> <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑧">Formal Objection</a>.</p>
+    <p>The Team <em class="rfc2119">must</em> provide two channels for Advisory Committee review comments:</p>
+    <ol>
+     <li> an archived <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑥">Team-only</a> channel; 
+     <li> an archived <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only②">Member-only</a> channel. 
+    </ol>
+    <p>The <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform①">Call for Review</a> <em class="rfc2119">must</em> specify
+	which channel is the default for review comments on that Call.</p>
+    <p>Reviewers <em class="rfc2119">may</em> send information
+	to either or both channels.
+	A reviewer <em class="rfc2119">may</em> also share their own reviews
+	with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>,
+	and <em class="rfc2119">may</em> also make it available to the public.</p>
+    <p>A Member organization <em class="rfc2119">may</em> modify its review
+	during a review period
+	(e.g., in light of comments from other Members).</p>
+    <h4 class="heading settled" data-level="5.7.2" id="ACReviewAfter"><span class="secno">5.7.2. </span><span class="content"> Determining the W3C Decision</span><a class="self-link" href="#ACReviewAfter"></a></h4>
+    <p>After the review period,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧①">Team</a> determines the appropriate <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑦">W3C Decision</a>,
+	which they <em class="rfc2119">must</em> announce to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑧">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate
+	the level of support for the proposal
+	(<a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⓪">consensus</a> or <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent③">dissent</a>),
+	and specifically
+	whether there were any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑨">Formal Objections</a>,
+	with attention to <a href="#confidentiality-change">changing the confidentiality level</a> of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⓪">Formal Objections</a>.</p>
+    <p>If there were <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③①">Formal Objections</a>, at least some of which were <a data-link-type="dfn" href="#upheld" id="ref-for-upheld③">upheld</a>,
+	or if there is not <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①①">consensus</a> because of insufficient support, <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑧">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to improve the proposal. 
+     <li> The proposal is rejected. 
+    </ul>
+    <p>If the proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①②">consensus</a>,
+	or if all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③②">Formal Objections</a> are retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule">overruled</a> and the proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①③">consensus</a>,
+	this <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑨">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is adopted,
+			possibly with additional changes integrated
+			in order to address the comments of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑨">AC</a> (see below). 
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to make desirable changes identified during the review
+			and to resubmit. 
+    </ul>
+    <p>If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>,
+	then those changes <em class="rfc2119">must</em> be announced to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⓪">AC</a> and to the <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group③">Group</a> that owns the document (if any).
+	Additionally, when adopting a proposal with <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①">substantive changes</a> integrated,
+	the announcement <em class="rfc2119">must</em> include rationale
+	for the substantive changes.</p>
+    <p><a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change②">Substantive changes</a> to the proposal <em class="rfc2119">may</em> be adopted
+	only if the revised proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①④">consensus</a> of the subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②①">AC</a> that voted on the initial proposal
+	(including anyone who explicitly abstained),
+	or if all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③③">Formal Objections</a> against the revised proposal are retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule①">overruled</a> and the revised proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑤">consensus</a>.
+	For clarity,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧②">Team</a> <em class="rfc2119">should</em> seek a response from this subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②②">AC</a> using the same tooling and degree of formality as it did for the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑤">AC Review</a>;
+	and as is the case during <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑥">AC Reviews</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent④">dissent</a> in this context <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③④">Formal Objection</a>.</p>
+    <p>Any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑤">Formal Objection</a> raised at this stage against the revised proposal
+	is handled by the same <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③③">Council</a> responsible for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑥">Formal Objections</a> raised against the initial proposal,
+	if any.</p>
+    <p>Such a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③④">Council</a> has the ability to <a data-link-type="dfn" href="#affirm" id="ref-for-affirm③">affirm</a> either the original or the revised proposal for advancement,
+	thereby <a data-link-type="dfn" href="#overrule" id="ref-for-overrule②">overruling</a> all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑦">Formal Objections</a> against the original or revised proposal,
+	respectively.</p>
+    <p>For publications which have conditions in addition to <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②③">AC</a> approval
+	for introducing <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change③">substantive changes</a> (such as <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group④">Group</a> consensus or implementation experience
+	or going through a patent <a data-link-type="dfn" href="https://www.w3.org/policies/patent-policy/#exclusion-opportunity" id="ref-for-exclusion-opportunity">Exclusion Opportunity</a>),
+	those other conditions must also be re-fulfilled.</p>
+    <div class="example" id="example-2c1b534e"><a class="self-link" href="#example-2c1b534e"></a> For example, if <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change④">substantive changes</a> to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④">technical report</a> are requested when assessing the transition from <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR">Candidate Recommendation</a> to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①">Recommendation</a>,
+		the technical report would need to go through a new <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests">Update Request</a> and be republished as a new <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①">Candidate Recommendation</a>;
+		that new version would then need to satisfy the criteria for advancement.
+		Alternatively, the desired changes can be introduced as non-substantive amendments
+		using the process for <a href="#revising-rec">revising a Recommendation</a>.
+		However, with the exception of the removal of at-risk features,
+		they cannot be directly integrated between <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot">CRS</a> and <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②">REC</a>,
+		because that would fail to trigger a patent exclusion opportunity. </div>
+    <p>For <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑥">charters</a>,
+	substantive changes from the initial proposal that underwent <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑦">AC Review</a> <em class="rfc2119">must not</em> include any increase to the scope.
+	If any such change is desired,
+	it <em class="rfc2119">must</em> be returned for additional work
+	and go through a complete new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑧">AC Review</a>.</p>
+    <p>This document does not specify
+	time intervals between the end of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑨">Advisory Committee review</a> period
+	and the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⓪">W3C decision</a>.
+	This is to ensure that the Members and <a data-link-type="dfn" href="#team" id="ref-for-team⑧③">Team</a> have sufficient time to consider comments
+	gathered during the review.
+	The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②④">Advisory Committee</a> <em class="rfc2119">should not</em> expect an announcement
+	sooner than <span class="time-interval">two weeks</span> after the end of a review period.
+	If, after <span class="time-interval">three weeks</span>, the outcome has not been announced,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧④">Team</a> <em class="rfc2119">should</em> provide the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑤">Advisory Committee</a> with an update.</p>
+    <h3 class="heading settled" data-level="5.8" id="ACVotes"><span class="secno">5.8. </span><span class="content"> Advisory Committee Votes</span><a class="self-link" href="#ACVotes"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑥">Advisory Committee</a> votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>,
+	and in the event of an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal②">Advisory Committee Appeal</a> achieving the required support to trigger an <a data-link-type="dfn" href="#appeal-vote" id="ref-for-appeal-vote①">appeal vote</a>.
+	Whenever the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑦">Advisory Committee</a> votes,
+	each Member or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member④">related Members</a> has one vote.</p>
+    <h3 class="heading settled" data-level="5.9" id="ACAppeal"><span class="secno">5.9. </span><span class="content"> Appeal by Advisory Committee Representatives</span><a class="self-link" href="#ACAppeal"></a></h3>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑨">Advisory Committee representatives</a> <em class="rfc2119">may</em> appeal certain decisions,
+	though appeals are only expected to occur in extraordinary circumstances.
+	For the purpose of this section, only <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⓪">Advisory Committee representatives</a> of <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member④">Members</a> in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing①">Good Standing</a> are counted.</p>
+    <p>When a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①①">W3C decision</a> is made following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⓪">Advisory Committee review</a>, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②①">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee Appeal|AC Appeal| Appeal" id="advisory-committee-appeal">Advisory Committee Appeal</dfn>.
+	These <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①②">W3C decisions</a> include those related to group creation and modification,
+	and transitions to new maturity stages for Recommendation Track documents
+	and the Process document.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②②">Advisory Committee representatives</a> <em class="rfc2119">may</em> also initiate an appeal
+	for decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑤">W3C Council</a>, and
+	for certain decisions that do not involve an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②①">Advisory Committee review</a>.
+	These cases are identified in the sections
+	which describe the requirements for the decision
+	and include
+	additional (non-reviewed) maturity stages of Recommendation Track documents,
+	group <a data-link-type="dfn" href="#dfn-charter-extension" id="ref-for-dfn-charter-extension">charter extensions</a> and closures,
+	and <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement">technical agreements</a>.</p>
+    <p>In all cases,
+	an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal③">appeal</a> <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the decision.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②③">Advisory Committee representative</a> initiates an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal④">appeal</a> by sending a request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑤">Team</a>,
+	and should also share this request with the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑧">Advisory Committee</a>.
+	The request should say “I appeal this Decision”
+	and identify the decision,
+	and may also include their rationale for appealing the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a> for a recommendation
+	on how to communicate an appeal request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑥">Team</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑨">AC</a>.</p>
+    <p>Within one week the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑦">Team</a> <em class="rfc2119">must</em> announce the appeal process
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⓪">Advisory Committee</a> and provide a mechanism for <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②④">Advisory Committee representatives</a> to respond with a statement of positive support for this appeal.
+	The archive of these statements <em class="rfc2119">must</em> be <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only③">member-only</a>.
+	If, within <span class="time-interval">one week</span> of the Team’s announcement,
+	5% or more of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③①">Advisory Committee</a> support the appeal request,
+	the Team <em class="rfc2119">must</em> organize an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="appeal-vote">appeal vote</dfn> asking the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③②">Advisory Committee</a> “Do you approve of the Decision?”
+	together with links to the decision and the appeal support.</p>
+    <p>The ballot <em class="rfc2119">must</em> allow for three possible responses:
+	“Approve”,
+	“Reject”,
+	and “Abstain”,
+	together with Comments.</p>
+    <p>The level of support needed for an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑤">Advisory Committee Appeal</a> to pass
+	depends on the level of ballot participation 
+	(including explicit “abstain” ballots) 
+	by <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑤">Advisory Committee Representatives</a>:</p>
+    <ul>
+     <li data-md>
+      <p>if fewer than 5% participate,
+the vote fails.</p>
+     <li data-md>
+      <p>if at least 5% but no more than 15% participate,
+and the number of “Approve” ballots exceeds three times (3x) the number of “Reject” ballots,
+the vote passes.</p>
+     <li data-md>
+      <p>if more than 15% but fewer than 20% participate,
+and the number of “Approve” ballots exceeds twice (2x) the number of “Reject” ballots,
+the vote passes.</p>
+     <li data-md>
+      <p>if 20% or more participate,
+and the number of “Approve” ballots exceeds the number of “Reject” ballots,
+the vote passes.</p>
+    </ul>
+    <p>If the vote passes,
+	the decision is overturned.
+	Following such rejection,
+	those who had initiated the proposal may revise it
+	to address the causes of rejection
+	and follow the ordinary applicable process
+	to submit the revised proposal.</p>
+    <h2 class="heading settled" data-level="6" id="Reports"><span class="secno">6. </span><span class="content"> W3C Technical Reports</span><a class="self-link" href="#Reports"></a></h2>
+    <p>The W3C technical report development process is the set of steps and requirements
+	followed by W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑤">Working Groups</a> to standardize Web technology.
+	The W3C technical report development process is designed to:</p>
+    <ul>
+     <li> support multiple specification development methodologies 
+     <li> maximize <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑥">consensus</a> about the content of stable technical reports 
+     <li> ensure high technical and editorial quality 
+     <li> promote consistency among specifications 
+     <li> facilitate royalty-free, interoperable implementations of Web Standards, and 
+     <li> earn endorsement by W3C and the broader community. 
+    </ul>
+    <p>See also “licensing goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.1" id="recs-and-notes"><span class="secno">6.1. </span><span class="content"> Types of Technical Reports</span><a class="self-link" href="#recs-and-notes"></a></h3>
+    <p>This chapter describes the formal requirements
+	for <a data-link-type="dfn" href="#publishing" id="ref-for-publishing">publishing</a> and maintaining a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③">W3C Recommendation</a>, <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑧">Note</a>,
+	or <a data-link-type="dfn" href="#registry" id="ref-for-registry">Registry</a>.</p>
+    <dl>
+     <dt>Recommendations 
+     <dd> <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑥">Working Groups</a> develop technical reports on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①">W3C Recommendation Track</a> in order to produce normative specifications or guidelines
+			as standards for the Web.
+			The <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track②">Recommendation Track</a> process incorporates requirements for <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review②">wide review</a>, <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation">adequate implementation experience</a>,
+			and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑦">consensus</a>-building,
+			and is subject to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			under which participants commit to Royalty-Free IPR licenses for implementations.
+			See <a href="#rec-track">§ 6.3 The W3C Recommendation Track</a> for details. 
+     <dt>Notes 
+     <dd> Groups can also publish documents as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①">Group Notes</a> and <a data-link-type="dfn" href="#statement" id="ref-for-statement">W3C Statements</a>,
+			typically either to document information
+			other than technical specifications,
+			such as use cases motivating a specification
+			and best practices for its use.
+			See <a href="#note-track">§ 6.4 The Note Track (Notes and Statements)</a> for details. 
+     <dt>Registries 
+     <dd> <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group③">Chartered</a> and <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group">elected groups</a> can also publish <a data-link-type="dfn" href="#registry" id="ref-for-registry①">registries</a> in order to document collections of values or other data.
+			A registry can be published either as a distinct <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report">registry report</a>,
+			or directly within a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track③">Recommendation Track</a> document
+			as an <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry">embedded registry</a>. <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition">Defining a registry</a> requires <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review③">wide review</a> and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑧">consensus</a>,
+			but once set up, changes to registry entries are lightweight
+			and can even be done without the initiating group’s involvement.
+			See <a href="#registries">§ 6.5 The Registry Track</a> for details. 
+    </dl>
+    <p>Individual <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑦">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑨">Interest Groups</a> <em class="rfc2119">should</em> adopt additional processes
+	for developing publications,
+	so long as they do not conflict with the requirements in this chapter.</p>
+    <h3 class="heading settled" data-level="6.2" id="general-requirements"><span class="secno">6.2. </span><span class="content"> General Requirements for Technical Reports</span><a class="self-link" href="#general-requirements"></a></h3>
+    <h4 class="heading settled" data-level="6.2.1" id="publication"><span class="secno">6.2.1. </span><span class="content"> Publication of Technical Reports</span><a class="self-link" href="#publication"></a></h4>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="publish" data-noexport id="publishing">Publishing</dfn> as used in this document
+	refers to producing a version which is listed as a W3C <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="technical-report">Technical Report</dfn> on its <a href="https://www.w3.org/TR/">Technical Reports index at https://www.w3.org/TR</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a>.
+	Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public document.
+	W3C strives to make archival documents indefinitely available
+	at their original address in their original form.</p>
+    <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate its <a href="#maturity-stages">maturity stage</a>,
+	and <em class="rfc2119" id="DocumentStatus">must</em> include information about the status of the document.
+	This status information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> be unique each time a specification is <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①">published</a>, 
+     <li> <em class="rfc2119">must</em> state which <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑧">Working Group</a> developed the specification, 
+     <li> <em class="rfc2119">must</em> state how to send comments or file bugs,
+			and where these are recorded, 
+     <li> <em class="rfc2119">must</em> include expectations about next steps, 
+     <li> <em class="rfc2119">should</em> explain how the technology relates to existing international standards
+			and related work inside or outside W3C,
+			and 
+     <li> <em class="rfc2119">should</em> explain
+			or link to
+			an explanation of significant changes from the previous version. 
+    </ul>
+    <p>Every Technical Report published
+	as part of the Technical Report development process
+	is edited by one or more editors
+	appointed by a Group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③⓪">Chair</a>.
+	It is the responsibility of these editors to ensure that the decisions of the Group are
+	correctly reflected in subsequent drafts of the technical report.
+	An editor <em class="rfc2119">must</em> be a participant,
+	per <a href="#group-participation">§ 3.4.2 Participation in Chartered Groups</a> in the Group responsible for the document(s) they are editing.</p>
+    <p>The Team is <em class="rfc2119">not required</em> to publish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑤">Technical Report</a> that does not conform to the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules" title="Publication Rules">[PUBRULES]</a> (e.g., for <span id="DocumentName">naming</span>,
+	status information,
+	style,
+	and <span id="document-copyright">copyright requirements</span>).
+	These rules are subject to change by the Team from time to time.
+	The Team <em class="rfc2119">must</em> inform group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③①">Chairs</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③③">Advisory Committee</a> of any changes to these rules.</p>
+    <p>The primary language for W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑥">Technical Reports</a> is English.
+	W3C encourages the translation of its <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑦">Technical Reports</a>. <a href="https://www.w3.org/Consortium/Translation/">Information about translations of W3C technical reports</a> <a data-link-type="biblio" href="#biblio-translation" title="Translations of W3C technical reports">[TRANSLATION]</a> is available at the W3C website.</p>
+    <h4 class="heading settled" data-level="6.2.2" id="doc-reviews"><span class="secno">6.2.2. </span><span class="content"> Reviews and Review Responsibilities</span><a class="self-link" href="#doc-reviews"></a></h4>
+    <p>A document is available for review
+	from the moment it is first <a data-link-type="dfn" href="#publishing" id="ref-for-publishing②">published</a>.
+	Working Groups <em class="rfc2119">should</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed①">formally address</a> <em>any</em> substantive review comment
+	about a technical report in a timely manner.</p>
+    <p>Reviewers <em class="rfc2119">should</em> send substantive technical reviews as early as possible. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑨">Working Groups</a> are often reluctant to make <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑤">substantive changes</a> to a mature document,
+	particularly if this would cause significant compatibility problems
+	due to existing implementation. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⓪">Working Groups</a> <em class="rfc2119">should</em> record substantive
+	or interesting proposals raised by reviews
+	but not incorporated into a current specification.</p>
+    <h5 class="heading settled" data-level="6.2.2.1" id="wide-review"><span class="secno">6.2.2.1. </span><span class="content"> Wide Review</span><a class="self-link" href="#wide-review"></a></h5>
+    <p>The requirements for <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="dfn-wide-review">wide review</dfn> are not precisely defined by the W3C Process.
+	The objective is to ensure that the entire set of stakeholders of the Web community,
+	including the general public,
+	have had adequate notice of the progress of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②①">Working Group</a> and were able to actually perform reviews of and provide comments on the specification.
+	A second objective is to encourage groups to request reviews
+	early enough that comments and suggested changes
+	can still be reasonably incorporated in response to the review.
+	Before approving transitions,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑧">Team</a> will consider who has been explicitly offered
+	a reasonable opportunity to review the document,
+	who has provided comments,
+	the record of requests to and responses from reviewers,
+	especially <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a> and groups identified as dependencies in the charter
+	or identified as <a href="https://www.w3.org/liaisons/">liaisons</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a>,
+	and seek evidence of clear communication to the general public
+	about appropriate times and which content to review
+	and whether such reviews actually occurred.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The Team documents <a href="https://www.w3.org/guide/documentreview/">best practices for wide review</a> in the Guidebook. <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a></p>
+    <p>For example,
+	inviting review of new or significantly revised sections published in Working Drafts,
+	and tracking those comments
+	and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②②">Working Group</a>’s responses,
+	is generally a good practice which would often be considered positive evidence of wide review. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②③">Working Groups</a> <em class="rfc2119">should</em> follow the <a href="https://www.w3.org/guide/documentreview/#how-to-get-horizontal-review">W3C Horizontal Groups</a>’ review processes,
+	and <em class="rfc2119">should</em> announce to other W3C Working Groups
+	as well as the general public,
+	especially those affected by this specification,
+	a proposal to enter <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②">Candidate Recommendation</a> (for example in approximately 28 days).
+	By contrast a generic statement in a document
+	requesting review at any time
+	is likely not to be considered as sufficient evidence
+	that the group has solicited wide review.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②④">Working Group</a> could present evidence that wide review has been received,
+	irrespective of solicitation.
+	But it is important to note that receiving many detailed reviews
+	is not necessarily the same as wide review,
+	since they might only represent comment
+	from a small segment of the relevant stakeholder community.</p>
+    <h4 class="heading settled" data-level="6.2.3" id="correction-classes"><span class="secno">6.2.3. </span><span class="content"> Classes of Changes</span><a class="self-link" href="#correction-classes"></a></h4>
+    <p>This document distinguishes the following 5 classes of changes to a document.
+	The first two classes of change are considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="editorial change" data-noexport id="editorial-change">editorial changes</dfn>,
+	the next two <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="substantive change" data-noexport id="substantive-change">substantive changes</dfn>,
+	and the last one <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="registry change" data-noexport id="registry-change">registry changes</dfn>.</p>
+    <dl>
+     <dt id="class-1">
+      <a class="self-link" href="#class-1"></a> 
+      <ol>
+       <li data-md>
+        <p>No changes to text content</p>
+      </ol>
+     <dd> These changes include fixing broken links, style sheets, or invalid markup. 
+     <dt id="class-2">
+      <a class="self-link" href="#class-2"></a> 
+      <ol start="2">
+       <li data-md>
+        <p>Changes that do not functionally affect interpretation of the document</p>
+      </ol>
+     <dd> For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track④">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑧">technical reports</a> specifically,
+			this constitutes changes that do not affect conformance,
+			i.e. changes that reasonable implementers
+			would not interpret as changing architectural
+			or interoperability requirements
+			or their implementation.
+			Changes which resolve ambiguities in the specification
+			are considered to change (by clarification) the implementation requirements
+			and do not fall into this class. 
+     <dd> Examples of changes in this class include
+			correcting non-normative examples
+			which clearly conflict with normative requirements,
+			clarifying various other non-normative text,
+			fixing typos or grammatical errors
+			where the change does not change requirements. 
+     <dd> If there is any doubt or disagreement
+			as to whether a change functionally affects interpretation,
+			that change does not fall into this class. 
+     <dt id="class-3">
+      <a class="self-link" href="#class-3"></a> 
+      <ol start="3">
+       <li data-md>
+        <p>Other changes that do not add new features</p>
+      </ol>
+     <dd>
+       For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑤">Recommendation-track</a> documents,
+			these changes <em class="rfc2119">may</em> affect conformance to the specification.
+			A change that affects conformance is one that: 
+      <ul>
+       <li> makes conforming data, processors, or other conforming agents become non-conforming according to the new version,
+					or 
+       <li> makes non-conforming data, processors, or other agents become conforming,
+					or 
+       <li> clears up an ambiguity or under-specified part of the specification
+					in such a way that data,
+					a processor,
+					or an agent
+					whose conformance was once unclear
+					becomes clearly either conforming or non-conforming. 
+      </ul>
+     <dt id="class-4">
+      <a class="self-link" href="#class-4"></a> 
+      <ol start="4">
+       <li data-md>
+        <p>New features</p>
+      </ol>
+     <dd> Changes that add new functionality,
+			such as new elements, new APIs, new rules, etc. 
+     <dt id="class-5">
+      <a class="self-link" href="#class-5"></a> 
+      <ol start="5">
+       <li data-md>
+        <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table">registry table</a></p>
+      </ol>
+     <dd> Changes that add, remove, or alter <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry">registry entries</a> in a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①">registry table</a>. 
+    </dl>
+    <h4 class="heading settled" data-level="6.2.4" id="errata"><span class="secno">6.2.4. </span><span class="content"> Errata Management</span><a class="self-link" href="#errata"></a></h4>
+    <p>Tracking errors is an important part of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑤">Working Group</a>’s ongoing care of a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑨">technical report</a>;
+	for this reason,
+	the scope of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑥">Working Group</a> charter generally allows time
+	for work after publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④">Recommendation</a>.
+	In this Process Document,
+	the term “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="erratum | errata" id="erratum">erratum</dfn>”
+	(plural “errata”) refers to any error
+	that can be resolved by one or more changes in classes 1-3
+	of section <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑦">Working Groups</a> <em class="rfc2119">must</em> keep
+	a public record of errors
+	that are reported by readers and implementers
+	for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤">Recommendations</a>.
+	Such error reports <em class="rfc2119">should</em> be compiled
+	no less frequently than quarterly.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑧">Working Groups</a> decide how to document errata.
+	Such documentation <em class="rfc2119">must</em> identify
+	the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⓪">technical report</a> text
+	and describe the error;
+	it <em class="rfc2119">may</em> also describe some possible solution(s).
+	Readers of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①①">technical report</a> <em class="rfc2119">should</em> be able easily
+	to find and see the errata
+	that apply to that specific <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①②">technical report</a> with their associated tests.
+	Errata <em class="rfc2119">may</em> be documented
+	in a separate errata page or tracking system.
+	They <em class="rfc2119">may</em>,
+	in addition or alternatively,
+	be annotated inline
+	alongside the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①③">technical report</a> text
+	or at the start or end of the most relevant section(s).</p>
+    <h4 class="heading settled" data-level="6.2.5" id="candidate-amendments"><span class="secno">6.2.5. </span><span class="bs-old-id" id="candidate-changes"></span><span class="content"> Candidate Amendments</span><a class="self-link" href="#candidate-amendments"></a></h4>
+    <p>An <a data-link-type="dfn" href="#erratum" id="ref-for-erratum">erratum</a> <em class="rfc2119">may</em> be accompanied by a non-normative, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-correction">candidate correction</dfn> approved by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision②">group decision</a>.
+	When annotated inline,
+	errata—​including their <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction">candidate corrections</a>—​must be marked as such,
+	are treated as <a href="#correction-classes">class 2 changes</a>,
+	and are published accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Annotating changes in this way allows more mature documents
+	such as <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥">Recommendations</a> and <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR③">Candidate Recommendations</a> to be updated quickly with the Working Group’s most current thinking,
+	even when the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment">candidate amendments</a> have not yet received
+	sufficient review or implementation experience
+	to be normatively incorporated into the specification proper.</p>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-addition">candidate addition</dfn> is similar to a <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction①">candidate correction</a>,
+	except that it proposes a new feature
+	rather than an error correction.</p>
+    <p><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction②">Candidate corrections</a> and <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition">candidate additions</a> are collectively known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="candidate amendment" data-noexport id="candidate-amendment">candidate amendments</dfn>.</p>
+    <p>In addition to their actual <a href="#maturity-stages">maturity stage</a>, <a data-link-type="dfn" href="#publishing" id="ref-for-publishing③">published</a> <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑥">REC Track</a> documents with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①">candidate amendments</a> are also considered,
+	for the purpose of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	to be <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①">Working Drafts</a> with those <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment②">candidate amendments</a> treated as normative.</p>
+    <h4 class="heading settled" data-level="6.2.6" id="no-group-maintenance"><span class="secno">6.2.6. </span><span class="content"> Maintenance Without a Group</span><a class="self-link" href="#no-group-maintenance"></a></h4>
+    <p>For all <a href="#recs-and-notes">types of technical reports</a> and all <a href="#maturity-stages">maturity stages</a>,
+	if there is no <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group④">group</a> chartered to maintain a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①④">technical report</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑨">Team</a> <em class="rfc2119">may</em> republish it
+	at the same <a href="#maturity-stages">maturity stage</a>,
+	integrating as needed:</p>
+    <ol>
+     <li><a href="#correction-classes">class 1 changes</a>; 
+     <li>inline <a data-link-type="dfn" href="#erratum" id="ref-for-erratum①">errata</a>; 
+     <li><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction③">candidate corrections</a>,
+			which <em class="rfc2119">must</em> be marked as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="team-correction">Team correction</dfn>; 
+     <li><a href="#correction-classes">class 2 changes</a> other than inline <a data-link-type="dfn" href="#erratum" id="ref-for-erratum②">errata</a> and <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction">Team corrections</a>. 
+    </ol>
+    <p>To avoid any potential doubt or disagreement
+	about whether changes really do fall into <a href="#correction-classes">class 2</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⓪">Team</a> <em class="rfc2119">should</em> be conservative,
+	limiting itself to obvious and limited fixes,
+	and <em class="rfc2119">must</em> avoid substantial rephrasing,
+	even of non-normative examples and notes.
+	If any such change is desired,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨①">Team</a> <em class="rfc2119">must</em> mark it as a <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction①">Team correction</a>.</p>
+    <p><a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction②">Team corrections</a> do not constitute
+	a normative portion of the Recommendation,
+	as defined in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (i.e., they are not covered by the Patent Policy).
+	For <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR④">Candidate Recommendations</a>, <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦">W3C Recommendations</a>, <a data-link-type="dfn" href="#candidate-registry" id="ref-for-candidate-registry">Candidate Registries</a>, <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry">W3C Registries</a>,
+	as well as <a data-link-type="dfn" href="#statement" id="ref-for-statement①">W3C Statements</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨②">Team</a> <em class="rfc2119">must</em> solicit <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review④">wide review</a> on <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction③">Team corrections</a> that it produces.</p>
+    <h4 class="heading settled" data-level="6.2.7" id="contributor-license"><span class="secno">6.2.7. </span><span class="content"> License Grants from Non-Participants</span><a class="self-link" href="#contributor-license"></a></h4>
+    <p>When a party who is not already obligated under the Patent Policy
+	offers a change in class 3 or 4
+	(as described in <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>) to a technical report under this process
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨③">Team</a> <em class="rfc2119">must</em> request
+	a recorded royalty-free patent commitment;
+	for a change in class 4, the Team <em class="rfc2119">must</em> secure such commitment.
+	Such commitment <em class="rfc2119">should</em> cover,
+	at a minimum,
+	all the party’s Essential Claims both in the contribution,
+	and that become Essential Claims as a result of incorporating the contribution into the draft
+	that existed at the time of the contribution,
+	on the terms specified in the “W3C Royalty-Free (RF) Licensing Requirements” section of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.3" id="rec-track"><span class="secno">6.3. </span><span class="bs-old-id" id="rec-advance"></span><span class="content"> The W3C Recommendation Track</span><a class="self-link" href="#rec-track"></a></h3>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑨">Working Groups</a> create specifications and guidelines
+	to complete the scope of work envisioned by a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⓪">Working Group</a>’s <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑦">charter</a>.
+	These <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑤">technical reports</a> undergo cycles of revision and review
+	as they advance towards <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑧">W3C Recommendation</a> status.
+	Once review suggests the Working Group has met their requirements for a new standard,
+	including <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑤">wide review</a>,
+	a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑤">Candidate Recommendation</a> phase
+	allows the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③①">Working Group</a> to formally collect <a href="#implementation-experience">implementation experience</a> to demonstrate that the specification works in practice.
+	At the end of the process,
+	the Advisory Committee reviews the mature technical report,
+	and if there is support from its Membership,
+	W3C publishes it as a <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑥">Recommendation</a>.</p>
+    <p>In summary, the main steps of <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track" data-noexport id="w3c-recommendation-track">W3C Recommendation Track</dfn> are:</p>
+    <ol>
+     <li>Publication of the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd①">First Public Working Draft</a>. 
+     <li>Publication of zero or more revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD②">Working Drafts</a>. 
+     <li>Publication of one or more <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑥">Candidate Recommendations</a>. 
+     <li>Publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑨">W3C Recommendation</a>. 
+    </ol>
+    <figure>
+     <svg viewBox="-5 30 457 175" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Basic W3C Recommendation Track</title>
+      <g role="list">
+       <g fill="#060" role="listitem">
+        <a href="#wd-1">
+         <rect fill="white" height="45" role="img" width="57" y="122">
+          <title>First Public Working Draft (FPWD) - Exclusion opportunity</title>
+         </rect>
+         <text font-size="8">
+          <tspan aria-hidden="true" x="0" y="132">First Public WD</tspan>
+          <tspan x="0" y="152">WG Decision +</tspan>
+          <tspan x="0" y="160">Team Approval</tspan>
+         </text>
+         <path d="M0,140h53" fill="none" stroke="#060"></path>
+         <polygon points="47,136 57,140 47,144"></polygon>
+        </a>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="97" cy="140" fill="#fff" id="wd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Working Draft (WD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="97" y="144">WD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Publish a new Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="97" y="100">WG Decision</tspan>
+           </text>
+           <path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114" fill="none" stroke="black" stroke-dasharray="6 2"></path>
+           <polygon points="120,114 116,124 114,113"></polygon>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Advance to Candidate Recommendation</title>
+           </g>
+           <text font-size="8" x="135" y="129">WG Decision +</text>
+           <text font-size="8" x="135" y="137">Team Approval</text>
+           <path d="M135,140h81" stroke="#060"></path>
+           <polygon points="211,136 221,140 211,144"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="260" cy="140" fill="#fff" id="cr-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="144">CRS</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="232" y="118">WG</tspan>
+            <tspan x="232" y="126">Decision</tspan>
+           </text>
+           <path d="M234,127v-34" stroke="#000"></path>
+           <polygon points="234,92 230,102 238,102"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="99">WG Decision</tspan>
+            <tspan x="290" y="107">Team Approval</tspan>
+           </text>
+           <path d="M242,124C238,114 244,104 260,104 271,104 285,108 286,117" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#rec-1">
+           <g role="img">
+            <title>Advance to Recommendation</title>
+           </g>
+           <text font-size="8" x="298" y="121">WG Decision +</text>
+           <text font-size="8" x="298" y="129">Team Approval +</text>
+           <text font-size="8" x="298" y="137">AC Review</text>
+           <path d="M298,140h77" stroke="#060"></path>
+           <polygon points="374,136 384,140 374,144"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="228" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="228" y="165">(or Team Decision with AB+TAG Approval)</tspan>
+           </text>
+           <path d="M140,147h84" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="140,145 133,147 140,149"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="260" cy="80" fill="#fff" id="crd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Draft (CRD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="84">CRD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="259" y="41">WG Decision</tspan>
+           </text>
+           <path d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="282,54 277,64 275,53"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="99">WG Decision +</tspan>
+            <tspan x="290" y="107">Team Approval</tspan>
+           </text>
+           <path d="M286,127v-34" stroke="#000"></path>
+           <polygon points="286,128 282,118 290,118"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="413" cy="140" fill="#fff" id="rec-1" role="img" rx="28" ry="18" stroke="black" stroke-width="2">
+          <title>Recommendation</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="413" y="144">REC</text>
+        </a>
+        <g role="list">
+         <g fill="#900" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Return to Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8" text-anchor="start">
+            <tspan x="342" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="342" y="165">(or Team Decision</tspan>
+            <tspan font-size="6" x="342" y="173">with AB+TAG</tspan>
+            <tspan font-size="6" x="342" y="181">Approval)</tspan>
+           </text>
+           <path d="M301,147h88" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="301,145 296,147 301,149"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="start">
+            <tspan x="342" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="342" y="165">(or Team Decision</tspan>
+            <tspan font-size="6" x="342" y="173">with AB+TAG</tspan>
+            <tspan font-size="6" x="342" y="181">Approval)</tspan>
+           </text>
+           <path d="M339,147v41h-242v-26" fill="none" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="95,164 97,159 99,164"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a fill="#000" href="#rec-1">
+           <g role="img">
+            <title>Publish revised Recommendation with editorial changes</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="413" y="103">WG Decision</tspan>
+            <tspan font-size="6" x="413" y="116">(editorial)</tspan>
+           </text>
+           <path d="M395,127C391,117 397,107 413,107 424,107 430,111 432,117" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="435,117 430,127 428,116"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a fill="#000" href="#rec-1">
+           <g role="img">
+            <title>Publish revised Recommendation with substantive changes</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="413" y="184">WG Decision +</tspan>
+            <tspan x="413" y="192">Team Approval +</tspan>
+            <tspan x="413" y="200">AC Review</tspan>
+            <tspan font-size="6" x="413" y="169">(substantive)</tspan>
+           </text>
+           <path d="M395,155C391,166 397,176 413,176 424,176 431,173 431,165" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="435,164 430,155 428,165"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+     <figcaption>Non-Normative Summary of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑦">Recommendation Track</a></figcaption>
+    </figure>
+    <p>Only sufficiently technically mature work should be advanced.
+	As described in <a href="#transition-reqs">§ 6.3.3 Advancement on the Recommendation Track</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨④">Team</a> will decline a request to advance in maturity stage
+	and return the specification to a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③②">Working Group</a> for further work
+	if it determines that the requirements for advancement
+	have not been met.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Should faster advancement to meet scheduling considerations be desired,
+	this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring
+	less stable features to other technical reports.</p>
+    <p>W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.</p>
+    <h4 class="heading settled" data-level="6.3.1" id="maturity-stages"><span class="secno">6.3.1. </span><span class="content"> Maturity Stages on the Recommendation Track</span><a class="self-link" href="#maturity-stages"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document" id="w3c-recommendation-track-document">W3C Recommendation Track document</dfn> is any document whose current status is one of those described in this section.</p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Working Draft | Working Draft | WD" id="RecsWD">Working Draft</dfn> (<abbr>WD</abbr>) 
+     <dd>
+       A Working Draft is a document that W3C has <a data-link-type="dfn" href="#publishing" id="ref-for-publishing④">published</a> on the <a href="https://www.w3.org/TR/">W3C’s Technical Reports page</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a> for review by the community (including W3C Members), the public,
+			and other technical organizations,
+			and for simple historical reference.
+			Some, but not all, Working Drafts are meant to advance to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⓪">Recommendation</a>;
+			see the <a href="#DocumentStatus">document status section</a> of a Working Draft
+			for the group’s expectations. <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD③">Working Drafts</a> do not necessarily represent a <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑨">consensus</a> of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③③">Working Group</a> with respect to their content,
+			and do not imply any endorsement by W3C
+			or its members beyond agreement to work on a general area of technology.
+			Nevertheless the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③④">Working Group</a> decided to adopt the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD④">Working Draft</a> as the basis for their work at the time of adoption.
+			A <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑤">Working Draft</a> is suitable for gathering <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑥">wide review</a> prior to advancing to the next stage of maturity. 
+      <p>For all Working Drafts a Working Group:</p>
+      <ul>
+       <li> <em class="rfc2119">should</em> document outstanding issues,
+					and parts of the document on which the Working Group does not have consensus,
+					and 
+       <li> <em class="rfc2119">may</em> request publication of a Working Draft
+					even if its content is considered unstable
+					and does not meet all Working Group requirements. 
+      </ul>
+      <p>The first Working Draft of a technical report is called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="fpwd">First Public Working Draft</dfn> (<abbr>FPWD</abbr>),
+			and has patent implications as defined in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Candidate Recommendation | Candidate Recommendation | CR" id="RecsCR">Candidate Recommendation</dfn> (<abbr>CR</abbr>) 
+     <dd>
+       A Candidate Recommendation is a document that satisfies the technical
+			requirements of the Working Group that produced it and their dependencies,
+			and has already received wide review.
+			W3C publishes a Candidate Recommendation to 
+      <ul>
+       <li> signal to the wider community that it is time to do a final review 
+       <li> gather <a href="#implementation-experience">implementation experience</a> 
+      </ul>
+      <p class="note" role="note"><span class="marker">Note:</span> Advancing to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑦">Candidate Recommendation</a> indicates
+			that the document is considered complete and fit for purpose,
+			and that no further refinement to the text is expected
+			without additional implementation experience and testing;
+			however, additional features might be expected in a later revision.
+			A <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑧">Candidate Recommendation</a> is expected to be as well-written,
+			detailed,
+			self-consistent,
+			and technically complete
+			as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①①">Recommendation</a>,
+			and acceptable as such
+			if and when the requirements for further advancement are met.</p>
+      <p>Candidate Recommendation publications take one of two forms:</p>
+      <dl>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Snapshot | CRS" id="candidate-recommendation-snapshot">Candidate Recommendation Snapshot</dfn> (<abbr>CRS</abbr>) 
+       <dd>
+         A Candidate Recommendation Snapshot
+					corresponds to a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts">Patent Review Draft</a> as used in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+					Publishing a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts①">Patent Review Draft</a> triggers a Call for Exclusions,
+					per “Exclusion From W3C RF Licensing Requirements”
+					in the W3C Patent Policy. 
+        <p>Publication as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①">Candidate Recommendation Snapshot</a> requires verification of either a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req">Transition Request</a> (for the first <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑨">Candidate Recommendation</a> publication from another maturity stage)
+					or an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①">Update Request</a> (for subsequent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot②">Candidate Recommendation Snapshots</a>).</p>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Draft | CRD" id="candidate-recommendation-draft">Candidate Recommendation Draft</dfn> (<abbr>CRD</abbr>) 
+       <dd>
+         A Candidate Recommendation Draft
+					is published
+					to solicit review of intended changes from the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot③">Candidate Recommendation Snapshot</a>.
+					This allows for wider review of the changes
+					and for ease of reference to the integrated specification. 
+        <p>Any changes published directly into a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft">Candidate Recommendation Draft</a> should be at the same level of quality as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot④">Candidate Recommendation Snapshot</a>.
+					However, the process requirements are minimized
+					so that the Working Group can easily keep the specification up to date.</p>
+        <p>A <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft①">Candidate Recommendation Draft</a> <em>does not</em> provide an exclusion opportunity;
+					instead, it is considered a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑥">Working Draft</a> for the purpose of the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+      </dl>
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rescinded-candidate-recommendation">Rescinded Candidate Recommendation</dfn> is a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⓪">Candidate Recommendation</a> in which significant problems have been discovered
+			such that W3C cannot endorse it or continue work on it,
+			for example due to burdensome patent claims that affect implementers and cannot be resolved
+			(see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “PAG Conclusion”).
+			There is no path to restoration for a <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a>.
+			See “W3C Royalty-Free (RF) Licensing Requirements”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for implication on patent licensing obligations.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation | Recommendation | REC" id="RecsW3C">W3C Recommendation</dfn> (<abbr>REC</abbr>) 
+     <dd>
+       A W3C Recommendation is a specification
+			or set of guidelines
+			or requirements that,
+			after extensive <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②⓪">consensus</a>-building,
+			has received the endorsement of W3C and its Members.
+			W3C recommends the wide deployment
+			of its Recommendations as standards for the Web.
+			The W3C Royalty-Free IPR licenses
+			granted under the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> apply to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①②">W3C Recommendations</a>. 
+      <p id="expandable-rec"> After its initial publication,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①③">W3C Recommendation</a> <em class="rfc2119">may</em> be revised
+			(in accordance with <a href="#revising-rec">§ 6.3.10 Revising a W3C Recommendation</a>)
+			to address <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①">editorial</a> or <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑥">substantive</a> issues
+			that are discovered later.
+			However, <a href="#class-4">new features</a> can only be added
+			if the document already identifies itself
+			as intending to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="allow-new-features">allow new features</dfn>.
+			Adding or removing this allowance is a <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑦">substantive change</a>.
+			Such an allowance cannot be added
+			to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑥">technical report</a> previously published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①④">Recommendation</a> that did not allow such changes;
+			this requires a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑦">technical report</a> (which could, for example, be similarly named but with an incremented version number). </p>
+      <p>As technology evolves,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑤">W3C Recommendation</a> may become:</p>
+      <dl>
+       <dt> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsSup">Superseded Recommendation</dfn> 
+       <dd>
+         A Superseded Recommendation is a specification
+					that has been replaced by a newer version
+					that W3C recommends for new adoption.
+					An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs">Obsolete</a> or Superseded specification
+					has the same status as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑥">W3C Recommendation</a> with regards to W3C Royalty-Free IPR Licenses granted under the Patent Policy. 
+        <p class="note" role="note"><span class="marker">Note:</span> When a Technical Report which had previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑦">Recommendation</a> is again published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑧">Recommendation</a> after following the necessary steps to <a href="#revising-rec">revise</a> it,
+					the latest version replaces the previous one,
+					without the need to invoke the steps of <a href="#rec-rescind">§ 6.3.12.3 Abandoning a W3C Recommendation</a>:
+					it is the same document, updated.
+					Explicitly declaring a documented superseded, using the process documented in <a href="#rec-rescind">§ 6.3.12.3 Abandoning a W3C Recommendation</a>,
+					is intended for cases where a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑨">Recommendation</a> is superseded by a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑧">Technical Report</a> (or by a document managed outside of W3C).</p>
+       <dt> An <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsObs">Obsolete Recommendation</dfn> 
+       <dd> An Obsolete Recommendation is a specification
+					that W3C has determined lacks sufficient market relevance
+					to continue recommending it for implementation,
+					but which does not have fundamental problems
+					that would require it to be <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec">Rescinded</a>.
+					If an Obsolete specification gains sufficient market relevance,
+					W3C may decide to restore it to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⓪">Recommendation</a> status. 
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RescindedRec">Rescinded Recommendation</dfn> 
+       <dd> A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses,
+					and believes is unlikely to ever be restored to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②①">Recommendation</a> status.
+					See also “W3C Royalty-Free (RF) Licensing Requirements”
+					in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+      </dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="discontinuedREC">Discontinued Draft</dfn> 
+     <dd> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑨">technical report</a> representing the state of a Recommendation-track document
+			at the point at which work on it was discontinued.
+			See <a href="#abandon-draft">§ 6.3.12.1 Abandoning an Unfinished Recommendation</a>. 
+    </dl>
+    <p>This Process defines certain <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑧">Recommendation Track</a> publications as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="patent-review-drafts">Patent Review Drafts</dfn>.
+	Under the 2004 Patent Policy (and its 2017 update) <a data-link-type="biblio" href="#biblio-patent-policy-2004" title="The W3C 2004 Patent Policy, Updated 2017">[PATENT-POLICY-2004]</a>,
+	these correspond to “Last Call Working Draft” in the Patent Policy;
+	Starting from the 2020 Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy-2020" title="The W3C 2020 Patent Policy">[PATENT-POLICY-2020]</a>,
+	these correspond to “Patent Review Draft” in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑤">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①⓪">Interest Groups</a> <em class="rfc2119">may</em> make available <a data-link-type="dfn" href="#editors-draft" id="ref-for-editors-draft">Editor’s drafts</a>. <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Editor&apos;s Draft | Editor Draft | ED" id="editors-draft">Editor’s drafts</dfn> (<abbr>ED</abbr>) have no official standing whatsoever,
+	and do not necessarily imply consensus of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑥">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①①">Interest Group</a>,
+	nor are their contents endorsed in any way by W3C.</p>
+    <p>When publishing an updated version of an existing <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①①">Candidate Recommendation</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②②">Recommendation</a>,
+	technical reports are expected to meet the same maturity criteria as when they are first published under that status.
+	However, in the interest of replacing stale documents with improved ones in a timely manner,
+	if flaws have been discovered in the technical report after its initial publication as a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①②">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②③">REC</a> that would have been severe enough to reject that publication had they be known in time,
+	it is also permissible to publish an updated <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①③">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②④">REC</a> following the usual process,
+	even if only some of these flaws have been satisfactorily addressed.</p>
+    <h4 class="heading settled" data-level="6.3.2" id="implementation-experience"><span class="secno">6.3.2. </span><span class="content"> Implementation Experience</span><a class="self-link" href="#implementation-experience"></a></h4>
+    <p>Implementation experience is required to show that a specification is sufficiently clear,
+	complete,
+	and relevant to market needs,
+	to ensure that independent interoperable implementations
+	of each feature of the specification will be realized.
+	While no exhaustive list of requirements is provided here,
+	when assessing that there is <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="adequate-implementation">adequate implementation experience</dfn> the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑤">Team</a> will consider (though not be limited to):</p>
+    <ul>
+     <li> is each feature of the current specification implemented,
+			and how is this demonstrated? 
+     <li> are there independent interoperable implementations of the current specification? 
+     <li> are there implementations created by people other than the authors of the specification? 
+     <li> are implementations publicly deployed? 
+     <li> is there implementation experience
+			at all levels of the specification’s ecosystem
+			(authoring, consuming, publishing…)? 
+     <li> are there reports of difficulties or problems with implementation? 
+    </ul>
+    <p>Planning and accomplishing a demonstration of (interoperable) implementations can be very time consuming.
+	Groups are often able to work more effectively
+	if they plan how they will demonstrate interoperable implementations
+	early in the development process;
+	for example, developing tests in concert with implementation efforts.</p>
+    <h4 class="heading settled" data-level="6.3.3" id="transition-reqs"><span class="secno">6.3.3. </span><span class="content"> Advancement on the Recommendation Track</span><a class="self-link" href="#transition-reqs"></a></h4>
+    <p>For <em>all</em> requests to advance a specification
+	to a new maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="trans-req">Transition Requests</dfn>),
+	the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request advancement. 
+     <li id="adv-verif-reqs"><a class="self-link" href="#adv-verif-reqs"></a> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑥">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑦">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑨">Team decision</a>) <em class="rfc2119">must</em> be withheld if any Process requirements are not met
+			or if there remain any unresolved Formal Objections
+			(including any aspect <a data-link-type="dfn" href="#upheld" id="ref-for-upheld④">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑥">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed">fully addressed</a>),
+			or if the document does not adequately reflect all relevant decisions of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑦">W3C Council</a> (or its delegates).
+			If the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑧">Team</a> rejects a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req①">Transition Request</a> it <em class="rfc2119">must</em> indicate its rationale
+			to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③④">Advisory Committee</a> and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑦">Working Group</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change②">editorial changes</a> have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed②">formally address</a> all issues
+			raised about the document since the previous <a href="#maturity-stages">maturity stage</a>. 
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑧">Formal Objections</a>. 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑧">Working Group</a>’s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑨">Working Group</a>. 
+    </ul>
+    <p>For a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd②">First Public Working Draft</a> there is no “previous maturity stage”,
+	so many requirements do not apply,
+	and verification is normally fairly straightforward.
+	For later stages,
+	especially transitions to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①④">Candidate</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑤">Recommendation</a>,
+	there is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p><a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req②">Transition Requests</a> to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd③">First Public Working Draft</a> or <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑤">Candidate Recommendation</a> will not normally be approved
+	while a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⓪">Working Group</a>’s <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑧">charter</a> is undergoing or awaiting a decision
+	on an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②②">Advisory Committee Review</a>.</p>
+    <h4 class="heading settled" data-level="6.3.4" id="update-reqs"><span class="secno">6.3.4. </span><span class="content"> Updating Mature Publications on the Recommendation Track</span><a class="self-link" href="#update-reqs"></a></h4>
+    <p>Certain requests to re-publish a specification
+	within its current maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="update-requests">Update Requests</dfn>)
+	require extra verification.
+	For such <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests②">update requests</a>, the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request the update. 
+     <li> <em class="rfc2119">must</em> show that the changes have received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑦">wide review</a>. 
+     <li>
+       <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑨">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⓪">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①⓪">Team decision</a>): 
+      <ul>
+       <li data-md>
+        <p><em class="rfc2119">should</em> be withheld
+if any Process requirements are not met,</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+in consideration of unresolved Formal Objections
+(including any aspect <a data-link-type="dfn" href="#upheld" id="ref-for-upheld⑤">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑧">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed①">fully addressed</a>),</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+if the document does not adequately reflect
+all relevant decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑨">W3C Council</a> (or its delegates),</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+if the Team believes the Group is not making reasonable progress
+on addressing issues raised by individuals external to the Group.</p>
+      </ul>
+      <p>If the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪①">Team</a> rejects an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests③">Update Request</a>,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④①">Working Group</a>.
+			If it waives any Process requirements,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑤">AC</a>.</p>
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑨">Formal Objections</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document of all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change③">editorial changes</a> changes have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> show that the revised specification
+			meets all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④②">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④③">Working Group</a>’s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④④">Working Group</a>. 
+    </ul>
+    <p>There is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests④">Update request</a> verification is expected to be fairly simple
+	compared to verification of a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req③">transition request</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪②">Team</a> <em class="rfc2119">must</em> announce the publication
+	of the revised specification
+	to other W3C groups and the Public.</p>
+    <h4 class="heading settled" data-level="6.3.5" id="first-wd"><span class="secno">6.3.5. </span><span class="content"> Publishing a First Public Working Draft</span><a class="self-link" href="#first-wd"></a></h4>
+    <p>To publish the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd④">First Public Working Draft</a> of a document,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑤">Working Group</a> <em class="rfc2119">must</em> meet the applicable <a href="#transition-reqs">requirements for advancement</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪③">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑤">First Public Working Draft</a> to other W3C groups and to the public.</p>
+    <h4 class="heading settled" data-level="6.3.6" id="revising-wd"><span class="secno">6.3.6. </span><span class="bs-old-id" id="revised-wd"></span><span class="content"> Revising a Working Draft</span><a class="self-link" href="#revising-wd"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑥">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑤">publish</a> a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑦">Working Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a Working draft, a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication. <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②①">Consensus</a> is not required,
+			as this is a procedural step, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑧">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑧">Working Draft</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change④">editorial changes</a> to the technical report
+			since the previous step, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups, 
+    </ul>
+    <p>Possible next steps for any Working Draft:</p>
+    <ul>
+     <li>Revised <a href="#revising-wd">Working Draft</a> 
+     <li><a href="#transition-cr">Candidate Recommendation</a> 
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.7" id="transition-cr"><span class="secno">6.3.7. </span><span class="bs-old-id" id="candidate-rec"></span><span class="content"> Transitioning to Candidate Recommendation</span><a class="self-link" href="#transition-cr"></a></h4>
+    <p>To publish a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑥">Candidate Recommendation</a>,
+	in addition to meeting the <a href="#transition-reqs">requirements for advancement</a> a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑦">Working Group</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> show that the specification
+			has met all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑧">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">must</em> document changes to dependencies during the development of the specification, 
+     <li> <em class="rfc2119">must</em> document
+			how <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation①">adequate implementation experience</a> will be demonstrated, 
+     <li> <em class="rfc2119">must</em> specify the deadline for comments,
+			delineating the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-recommendation-review-period">Candidate Recommendation review period</dfn>,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">must</em> show that the specification has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑧">wide review</a>, and 
+     <li> <em class="rfc2119">may</em> identify features in the document as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="at-risk">at risk</dfn>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑥">Recommendation</a> without requiring an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑤">Update Request</a>. 
+    </ul>
+    <p>The first Candidate Recommendation publication
+	after verification of having met the requirements for a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req④">Transition Request</a> is always a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑤">Candidate Recommendation Snapshot</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪④">Team</a> <em class="rfc2119">must</em> announce
+	the publication of the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑥">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑦">Candidate Recommendation Snapshot</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Recommendation</a>
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <p><a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑥">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 class="heading settled" data-level="6.3.8" id="revising-cr"><span class="secno">6.3.8. </span><span class="bs-old-id" id="revised-cr"></span><span class="content"> Revising a Candidate Recommendation</span><a class="self-link" href="#revising-cr"></a></h4>
+    <h5 class="heading settled" data-level="6.3.8.1" id="publishing-crrs"><span class="secno">6.3.8.1. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑧">Candidate Recommendation Snapshot</a></span><a class="self-link" href="#publishing-crrs"></a></h5>
+    <p>If there are any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑨">substantive changes</a> made to a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑦">Candidate Recommendation</a> since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑨">Candidate Recommendation Snapshot</a> other than to remove features explicitly identified as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk">at risk</a>,
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑨">Working Group</a> <em class="rfc2119">must</em> meet the requirements of an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑥">update request</a> in order to republish.</p>
+    <p>In addition the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> specify the deadline for further comments,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">may</em> identify features in the document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk①">at risk</a>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑦">Recommendation</a> without requiring an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑦">Update Request</a>. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑤">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a revised <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⓪">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>To provide timely updates and patent protection,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①①">Candidate Recommendation Snapshot</a> <em class="rfc2119">should</em> be published
+	within 24 months of the Working Group accepting
+	any proposal for a substantive change
+	(and preferably sooner).
+	To make scheduling reviews easier,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①②">Candidate Recommendation Snapshot</a> <em class="rfc2119">should not</em> be published
+	more often than approximately once every 6 months.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①⓪">Substantive changes</a> trigger a new Exclusion Opportunity
+	per “Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.8.2" id="publishing-crud"><span class="secno">6.3.8.2. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft②">Candidate Recommendation Draft</a></span><a class="self-link" href="#publishing-crud"></a></h5>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⓪">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑥">publish</a> an <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft③">Update Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft④">Candidate Recommendation Draft</a>,
+	a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①①">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①③">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑤">editorial changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①④">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> document outstanding issues,
+			and parts of the document on which the Working Group does not have consensus, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+    </ul>
+    <p class="note" role="note"><span class="marker">Note:</span> A Working Group <em>does not</em> need to
+	meet the requirements of a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑤">Candidate Recommendation Snapshot</a> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑧">update request</a> in order to publish a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑤">Candidate Recommendation Draft</a>.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑥">Candidate Recommendation Draft</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Recommendation</a>,
+		if there are no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①②">substantive change</a> other than dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk②">at risk</a> features
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.9" id="transition-rec"><span class="secno">6.3.9. </span><span class="bs-old-id" id="transition-pr"></span><span class="bs-old-id" id="rec-pr"></span><span class="bs-old-id" id="rec-publication"></span><span class="content"> Transitioning to Recommendation</span><a class="self-link" href="#transition-rec"></a></h4>
+    <p>When a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤①">Working Group</a> estimates
+	that a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑧">Candidate Recommendation</a> has fulfilled all the relevant criteria,
+	it <em class="rfc2119">may</em> <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision③">decide</a> to request advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑧">W3C Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.1" id="transition-rec-requirements"><span class="secno">6.3.9.1. </span><span class="content"> Requirements for Transition</span><a class="self-link" href="#transition-rec-requirements"></a></h5>
+    <p>In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,
+	the Working Group:</p>
+    <ul>
+     <li>
+       <em class="rfc2119">must</em> show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation②">adequate implementation experience</a> except where an exception is approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①①">Team Decision</a>. 
+      <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑥">Team</a> <em class="rfc2119">may</em> approve a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑨">Candidate Recommendation</a> with minimal <a href="#implementation-experience">implementation experience</a> where there is a compelling reason to do so.
+			In such a case, the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑦">Team</a> <em class="rfc2119">must</em> explain the reasons for that decision,
+			and that information <em class="rfc2119">must</em> be included in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform②">Call for Review</a> proposing advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑨">W3C Recommendation</a>.</p>
+     <li> <em class="rfc2119">must</em> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑨">wide review</a>. 
+     <li> <em class="rfc2119">must</em> show that all issues
+			raised during the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period">Candidate Recommendation review period</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed③">formally addressed</a>. 
+     <li> <em class="rfc2119">must </em>identify any substantive issues
+			raised since the close of the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period①">Candidate Recommendation review period</a>. 
+     <li> <em class="rfc2119">must</em> identify, in the document, where errata are tracked. 
+    </ul>
+    <p>Additionally,
+	if the document has previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⓪">W3C Recommendation</a>, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤②">Working Group</a> <em class="rfc2119">must not</em> include any <a href="#correction-classes">class 4 change</a> to that publication
+	unless it was explicitly marked as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features">allowing new features</a>,
+	and <em class="rfc2119">must not</em> include any such marking
+	if not already present.</p>
+    <p>If the document’s most recent publication is a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑦">Candidate Recommendation Draft</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑧">Team</a> <em class="rfc2119">must</em> verify
+	that it contains no changes since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑥">Candidate Recommendation Snapshot</a> other than:</p>
+    <ul>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑥">editorial changes</a>,</p>
+     <li data-md>
+      <p>the addition or removal of a statement as to whether the document will <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features①">allow new features</a> after its publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③①">Recommendation</a>.</p>
+     <li data-md>
+      <p>dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk③">at risk</a> features</p>
+    </ul>
+    <p>Otherwise, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤③">Working Group</a> <em class="rfc2119">must</em> republish it
+	as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑦">Candidate Recommendation Snapshot</a> prior to initiating the review.</p>
+    <h5 class="heading settled" data-level="6.3.9.2" id="initiating-rec-review"><span class="secno">6.3.9.2. </span><span class="content"> Initiating Review</span><a class="self-link" href="#initiating-rec-review"></a></h5>
+    <p>If all the criteria above are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑨">Team</a> <em class="rfc2119">must</em> begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②③">Advisory Committee Review</a> on the question of whether the identified <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②⓪">Candidate Recommendation</a> is appropriate to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑦">publish</a> as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③②">W3C Recommendation</a>.
+	The deadline for <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②④">Advisory Committee review</a> <em class="rfc2119">must</em> allow <strong>at least</strong> 28 days,
+	and <em class="rfc2119">must</em> end at least 10 days
+	after the end of the last Exclusion Opportunity
+	per ”Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.3" id="rec-review-resolution"><span class="secno">6.3.9.3. </span><span class="content"> Resolution of Review</span><a class="self-link" href="#rec-review-resolution"></a></h5>
+    <p>If there was any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④⓪">Formal Objection</a> during the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑤">Advisory Committee Review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⓪">Team</a> <em class="rfc2119">must</em> publish the substantive content of the <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑤">dissent</a> to W3C and the general public,
+	and the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③③">W3C Recommendation</a> <em class="rfc2119">must not</em> be published
+	unless all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④①">Formal Objections</a> to the document have been retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule③">overruled</a> and at least 14 days have elapsed since the publication of the corresponding <a data-link-type="dfn" href="#council-report" id="ref-for-council-report⑤">Council Report</a>.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③④">Recommendation</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①③">W3C Decision</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①①①">Team</a> <em class="rfc2119">must</em> announce the publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑤">W3C Recommendation</a> to the <a href="#AC">Advisory Committee</a>,
+	to other W3C groups
+	and to the public. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑥">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑥">Advisory Committee Appeal</a> of the decision to advance the technical report.</p>
+    <p>The newly published <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑥">Recommendation</a> <em class="rfc2119">must not</em> make any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①③">substantive changes</a> to the document
+	compared to the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑧">Candidate Recommendation Snapshot</a> submitted for AC Review,
+	other than dropping features identified <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk④">at risk</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.4" id="rec-next-steps"><span class="secno">6.3.9.4. </span><span class="content"> Next Steps from W3C Recommendation</span><a class="self-link" href="#rec-next-steps"></a></h5>
+    <p>Possible next steps:
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑦">W3C Recommendation</a> normally retains its status indefinitely.
+	However it <em class="rfc2119">may</em> be:</p>
+    <ul>
+     <li> republished as a <a href="#revising-rec">revised Recommendation</a>, or 
+     <li> republished as a <a href="#transition-cr">Candidate Recommendation</a> or <a href="#revising-wd">Working Draft</a> to be developed towards a revised <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑧">Recommendation</a>, or 
+     <li> declared <a href="#rec-rescind">superseded or obsolete</a>, or 
+     <li> <a href="#rec-rescind">rescinded</a>. 
+    </ul>
+    <h4 class="heading settled" data-level="6.3.10" id="revising-rec"><span class="secno">6.3.10. </span><span class="bs-old-id" id="revised-rec"></span><span class="bs-old-id" id="rec-modify"></span><span class="content"> Revising a W3C Recommendation</span><a class="self-link" href="#revising-rec"></a></h4>
+    <h5 class="heading settled" data-level="6.3.10.1" id="revised-rec-editorial"><span class="secno">6.3.10.1. </span><span class="bs-old-id" id="revised-rec-markup"></span><span class="content"> Revising a Recommendation: Editorial Changes</span><a class="self-link" href="#revised-rec-editorial"></a></h5>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑦">Editorial changes</a> to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑨">Recommendation</a> require no technical review of the intended changes.
+	A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤④">Working Group</a>,
+	provided there are no votes against the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision④">decision</a> to publish, <em class="rfc2119">may</em> request publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⓪">Recommendation</a> to make this class of change without passing through earlier maturity stages.
+	(See <a href="#class-1">class 1</a> and <a href="#class-2">class 2 changes</a>.)</p>
+    <h5 class="heading settled" data-level="6.3.10.2" id="revised-rec-substantive"><span class="secno">6.3.10.2. </span><span class="content"> Revising a Recommendation: Substantive Changes</span><a class="self-link" href="#revised-rec-substantive"></a></h5>
+    <p>Tentative corrections (see <a href="#class-3">class 3 changes</a>) <em class="rfc2119">may</em> be annotated into a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④①">Recommendation</a> using <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction④">candidate corrections</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑤">Candidate corrections</a> do not normatively modify the document;
+	they editorially indicate how one might do so.
+	They are therefore published following the provisions of <a href="#revised-rec-editorial">§ 6.3.10.1 Revising a Recommendation: Editorial Changes</a>.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑥">candidate correction</a> can be made normative
+	and be folded into the main text of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④②">Recommendation</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④③">Recommendation</a>,
+	including review by the community to ensure
+	its technical and editorial soundness.
+	To validate this, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑤">Working Group</a> must request
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review">Last Call for Review of Proposed Amendments</a>,
+	followed by an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑨">update request</a>.
+	See <a href="#change-review">§ 6.3.10.4 Incorporating Candidate Amendments</a>.</p>
+    <p>Alternatively,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑥">Working Group</a> <em class="rfc2119">may</em> incorporate the changes
+	and <a href="#revising-wd">publish as a Working Draft</a>—​or, if the relevant criteria are fulfilled, <a href="#transition-cr">publish as a Candidate Recommendation</a>—​and advance the specification from that state.
+	(See <a href="#correction-classes">class 3 changes</a>.)</p>
+    <h5 class="heading settled" data-level="6.3.10.3" id="revised-rec-features"><span class="secno">6.3.10.3. </span><span class="content"> Revising a Recommendation: New Features</span><a class="self-link" href="#revised-rec-features"></a></h5>
+    <p>For <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④④">Recommendations</a> explicitly identified as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features②">allowing new features</a>,
+	tentative new features (see <a href="#correction-classes">class 4 changes</a>) <em class="rfc2119">may</em> be added as <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition①">candidate additions</a> in annotations,
+	and <a href="#correction-classes">class 4 changes</a> may be normatively incorporated
+	in the same fashion as <a href="#correction-classes">class 3 changes</a> in <a href="#revised-rec-substantive">§ 6.3.10.2 Revising a Recommendation: Substantive Changes</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Limiting the addition of new features to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑤">Recommendations</a> that explicitly allow them
+	enables third parties to depend on a stable feature-set for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑥">Recommendations</a> that do not advertise that ability,
+	as was the case for all <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑦">Recommendations</a> prior to the 2020 revision of this Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> When a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑧">Recommendation</a> does not <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features③">allow new features</a>,
+	new features can be added by creating a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⓪">technical report</a> and following the full process of advancing that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②①">technical report</a> to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑨">Recommendation</a>—​beginning with a new <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑥">First Public Working Draft</a>.
+	Such <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②②">technical reports</a> could be written to represent
+	additional modules building on top of the original <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⓪">Recommendation</a> of the core technology,
+	or an expanded replacement of the original <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤①">Recommendation</a> of the core technology
+	(in which case the new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②③">technical report</a> will typically have the same name as the original,
+	with an incremented version number).</p>
+    <h5 class="heading settled" data-level="6.3.10.4" id="change-review"><span class="secno">6.3.10.4. </span><span class="content"> Incorporating Candidate Amendments</span><a class="self-link" href="#change-review"></a></h5>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-review">Last Call for Review of Proposed Amendments</dfn> verifies acceptance by the W3C community of <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment③">candidate amendments</a> by combining an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑥">AC Review</a> with a patent exclusion opportunity.</p>
+    <p>The <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review①">Last Call for Review of Proposed Amendments</a> must be announced to other W3C groups, the public, and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑦">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Identify whether this is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</dfn>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</dfn>,
+			or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</dfn>. 
+     <li> Identify the specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment④">candidate amendments</a> under review
+			as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-amendments">proposed amendments</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="proposed-corrections">proposed corrections</dfn>/<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="proposed-additions"><span class="bs-old-id" id="proposed-addition"></span>proposed additions</dfn>). 
+     <li> Specify the deadline for review comments,
+			which must not be any sooner than 60 days from the Call for Review. 
+     <li> Solicit review and, if it does not already have it, implementation experience. 
+    </ul>
+    <p>The combination of the existing <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤②">Recommendation</a> with the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments">proposed amendments</a> included in the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review②">Last Call for Review of Proposed Amendments</a> is considered a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts②">Patent Review Draft</a> for the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+	Also, the review initiated by the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review③">Last Call for Review of Proposed Amendments</a> is an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑦">Advisory Committee Review</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#last-call-for-review-of-proposed-additions" id="ref-for-last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a> and <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections-and-additions" id="ref-for-last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a> can only be issued for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤③">Recommendations</a> that <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features④">allow new features</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑦">Working Group</a> <em class="rfc2119">may</em> batch
+	multiple <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①">proposed amendments</a> into a single <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review④">Last Call for Review of Proposed Amendments</a>.
+	To facilitate review,
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑤">Last Call for Review of Proposed Amendments</a> on a given specification <em class="rfc2119">should not</em> be issued more frequently
+	than approximately once every 6 months.</p>
+    <p>At the end of the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑥">Last Call for Review of Proposed Amendments</a>,
+	the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①④">W3C Decision</a> may either be
+	to reject the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments②">proposed amendment</a>,
+	or to clear the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments③">proposed amendment</a> for advancement as is,
+	or to return the proposal to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑧">Working Group</a> with a request to <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed④">formally address</a> comments made on the changes under review.
+	If the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑨">Working Group</a> needs to amend a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments④">proposed amendment</a> in response to review feedback
+	it must issue another <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑦">Last Call for Review of Proposed Amendments</a> on the revised change
+	before it can be incorporated into the main text.</p>
+    <p>Once all comments on a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑤">proposed amendment</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑤">formally addressed</a>,
+	and after the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⓪">Working Group</a> can show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation③">adequate implementation experience</a> and the fulfillment of all other requirements of Recommendation text,
+	it may incorporate the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑥">proposed amendment</a> into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤④">Recommendation</a> by issuing an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①⓪">update request</a> for publication of the updated <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑤">Recommendation</a>.</p>
+    <p>To ensure adequate review of <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑦">proposed amendment</a> combinations,
+	only <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑧">proposed amendments</a> included in the most recent <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑧">Last Call for Review of Proposed Amendments</a> can be incorporated into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑥">Recommendation</a> text.
+	(Thus if incorporation of a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑨">proposed amendment</a> is postponed,
+	it may need to be included in multiple Last Calls for Review of Proposed Amendments.)</p>
+    <h4 class="heading settled" data-level="6.3.11" id="rec-track-regression"><span class="secno">6.3.11. </span><span class="content"> Regression on the Recommendation Track</span><a class="self-link" href="#rec-track-regression"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥①">Working Group</a> may republish a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑨">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②④">technical report</a> at a lower <a href="#maturity-stages">maturity stage</a> by fulfilling the requirements to transition to that maturity stage,
+	as described above.</p>
+    <p>Additionally,
+	with the approvals (by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑤">group decision</a>) of each of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑤">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③①">AB</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①①②">Team</a> <em class="rfc2119">may</em> return
+	the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑤">technical report</a> to a lower <a href="#maturity-stages">maturity stage</a> in response to <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①⓪">wide review</a> or a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④②">formal objection</a>.</p>
+    <h4 class="heading settled" data-level="6.3.12" id="tr-end"><span class="secno">6.3.12. </span><span class="content"> Retiring Recommendation Track Documents</span><a class="self-link" href="#tr-end"></a></h4>
+    <p>Work on a technical report <em class="rfc2119">may</em> cease at any time.
+	Work <em class="rfc2119 new">should</em> cease
+	if W3C or a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥②">Working Group</a> determines
+	that it cannot productively carry the work any further.</p>
+    <h5 class="heading settled" data-level="6.3.12.1" id="abandon-draft"><span class="secno">6.3.12.1. </span><span class="content"> Abandoning an Unfinished Recommendation</span><a class="self-link" href="#abandon-draft"></a></h5>
+    <p>Any <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⓪">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑥">technical report</a> no longer intended
+	to advance or to be maintained,
+	and that is not being rescinded, <em class="rfc2119">should</em> be <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑧">published</a> as a <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC">Discontinued Draft</a>,
+	with no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①④">substantive change</a> compared to the previous publication.
+	This can happen if
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥③">Working Group</a> decided
+	to abandon work on the report,
+	or as the result of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑧">AC Review</a> requiring the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥④">Working Group</a> to discontinue work on the technical report before completion.
+	If a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑤">Working Group</a> is made to <a href="#GeneralTermination">close</a>,
+	W3C <em class="rfc2119">must</em> re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑨">publish</a> any unfinished <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑦">technical report</a> on the Recommendation track as <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC①">Discontinued Draft</a>.</p>
+    <p>Such a document should include in its status section
+	an explanation of why it was discontinued.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑥">Working Group</a> <em class="rfc2119">may</em> resume work
+	on such a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑧">technical report</a> within the scope of its charter
+	at any time,
+	by re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing①⓪">publishing</a> it as a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑨">Working Draft</a>.</p>
+    <h5 class="heading settled" data-level="6.3.12.2" id="rescind-cr"><span class="secno">6.3.12.2. </span><span class="content"> Rescinding a Candidate Recommendation</span><a class="self-link" href="#rescind-cr"></a></h5>
+    <p>The process for rescinding a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②①">Candidate Recommendation</a> is the same as for rescinding a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑦">Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.12.3" id="rec-rescind"><span class="secno">6.3.12.3. </span><span class="content"> Abandoning a W3C Recommendation</span><a class="self-link" href="#rec-rescind"></a></h5>
+    <p>It is possible that W3C decides
+	that implementing a particular <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑧">Recommendation</a> is no longer recommended.
+	There are three designations for such specifications,
+	chosen depending on the advice W3C wishes to give about further use of the specification.</p>
+    <p>W3C <em class="rfc2119">may</em> obsolete a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑨">Recommendation</a>,
+	for example if the W3C Community decides that the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⓪">Recommendation</a> no longer represents best practices,
+	or is not adopted and is not apparently likely to be adopted.
+	An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs①">Obsolete Recommendation</a> <em class="rfc2119">may</em> be restored to normal <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥①">Recommendation</a>,
+	for example because despite marking it Obsolete the specification is later more broadly adopted.</p>
+    <p>W3C <em class="rfc2119">may</em> declare a Recommendation Superseded
+	if a newer version exists which W3C recommends for new adoption.
+	The process for declaring a Recommendation Superseded is the same as for declaring it Obsolete, below;
+	only the name and explanation change.</p>
+    <p>W3C <em class="rfc2119">may</em> rescind a Recommendation
+	if W3C believes there is no reasonable prospect of it being restored
+	for example due to burdensome patent claims that affect implementers and cannot be resolved;
+	see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “W3C Royalty-Free (RF) Licensing Requirements”
+	and “PAG Conclusion”.</p>
+    <p>W3C only rescinds, supersedes, or obsoletes entire Recommendations.
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥②">Recommendation</a> can be both superseded and obsolete.
+	To rescind, supersede, or obsolete some part of a Recommendation,
+	W3C follows the process for <a href="#revising-rec">modifying a Recommendation</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> For the purposes of the W3C Patent Policy, <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs②">Obsolete</a> or <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup">Superseded Recommendation</a> has the status of an active <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥③">Recommendation</a>,
+	although it is not advised for future implementation;
+	a <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec①">Rescinded Recommendation</a> ceases to be in effect
+	and no new licenses are granted under the Patent Policy.</p>
+    <figure>
+     <svg viewBox="0 0 300 135" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Supersede, Obsolete or Rescind a W3C Recommendation</title>
+      <g role="list">
+       <g role="listitem">
+        <ellipse cx="40" cy="50" fill="#fff" id="rec-3" role="img" rx="30" ry="20" stroke="black" stroke-width="2">
+         <title>Recommendation (Rec)</title>
+        </ellipse>
+        <text aria-hidden="true" font-size="18" stroke-width=".3" text-anchor="middle" x="40" y="55">REC</text>
+        <g role="list">
+         <g role="listitem">
+          <title>A major problem and an AC review can lead to a Recommendation being Rescinded.
+								There are no new IPR licences issued under the W3C Patent Policy,
+								and reinstating the Recommendation requires going through the full Rec-track process again.</title>
+          <path d="M40,29v-5s0,-5 5,-5h150" fill="none" stroke="black" stroke-dasharray="3 1" stroke-width="2"></path>
+          <text font-size="8" text-anchor="middle" x="105" y="16">Major problem, AC review</text>
+          <polygon points="195,16 195,22 199,19"></polygon>
+          <rect fill="#fff" height="36" id="rescinded" role="img" stroke="black" stroke-width="2" width="80" x="200" y="4"></rect>
+          <title>Rescinded Recommendation - no new IPR licenses</title>
+          <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="240" y="19">Rescinded</text>
+          <path d="M198,42l84,-40" stroke="red" stroke-width="2"></path>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="28">No new IPR licenses</text>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="37">No reinstatement path</text>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="black" stroke-dasharray="4 4"></path>
+           <title>With little uptake, following AC review a specification may become an Obsolete Recommendation</title>
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="red" stroke-dasharray="2 6" stroke-dashoffset="3"></path>
+           <polygon points="204,75 200,72 200,78"></polygon>
+           <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="42">Minimal usage, AC review</text>
+           <rect fill="#fff" height="26" id="obsolete" rx="8" stroke="black" stroke-dasharray="3 3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <title>Obsolete Recommendation</title>
+           <rect fill="none" height="26" rx="8" stroke="red" stroke-dasharray="3 3" stroke-dashoffset="3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="242" y="84">Obsolete</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <path d="M204,82h-149s-5,0 -5,-5v-5" fill="none" stroke="black" stroke-dasharray="2 3"></path>
+             <title>If there is new uptake, with AC review an Obsolete Recommendation may return to normal Recommendation status</title>
+             <polygon points="50,70 47,74 53,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="79">New uptake, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M40,71v29s0,5 5,5h140" fill="none" stroke="black"></path>
+           <polygon points="189,105 185,102 185,108"></polygon>
+           <text font-size="8" text-anchor="middle" x="115" y="102">Replaced by a new version, AC review</text>
+           <rect fill="#fff" height="30" id="superseded" role="img" rx="3" stroke="#600" stroke-width="2" width="90" x="190" y="100">
+            <title>Superseded Recommendation</title>
+           </rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="235" y="119">Superseded</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <title>A Superseded Recommendation can become a normal Recommendation with AC review</title>
+             <path d="M189,125h-154s-5,0 -5,-5v-52" fill="none" stroke="black" stroke-dasharray="1 4"></path>
+             <polygon points="30,70 27,74 33,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="110" y="122">Oops! The Web still needs this, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+     <figcaption>Non-Normative Summary of the Paths to Retiring a W3C Recommendation</figcaption>
+    </figure>
+    <h5 class="heading settled" data-level="6.3.12.4" id="deactivation"><span class="secno">6.3.12.4. </span><span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span><a class="self-link" href="#deactivation"></a></h5>
+    <p>The process of rescinding, obsoleting,
+	superseding,
+	or restoring
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥④">Recommendation</a> can be initiated
+	either by a request from the <a data-link-type="dfn" href="#team" id="ref-for-team①①③">Team</a> or via a request from any of the following:</p>
+    <ul>
+     <li> The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑦">Working Group</a> who produced,
+			or is chartered to maintain,
+			the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑤">Recommendation</a> 
+     <li> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑥">TAG</a>, if there is no such <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑧">Working Group</a> 
+     <li> Any individual who made a request to the relevant <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑨">Working Group</a> as described above,
+			or the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑦">TAG</a> if such a group does not exist, to obsolete, rescind, supersede, or restore a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑥">Recommendation</a>,
+			where the request was not answered within 90 days 
+     <li> 5% of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑦">Advisory Committee representatives</a> of <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑤">Members</a> in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing②">Good Standing</a> 
+    </ul>
+    <p id="proposed-rescinded-rec">The <a data-link-type="dfn" href="#team" id="ref-for-team①①④">Team</a> <em class="rfc2119">must</em> then
+	submit the request to the <a href="#AC">Advisory Committee</a> for review.
+	For any <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑨">Advisory Committee review</a> of a proposal to
+	rescind,
+	obsolete,
+	supersede,
+	or restore
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑦">Recommendation</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑤">Team</a> <em class="rfc2119">must</em>: </p>
+    <ul>
+     <li> announce the proposal to all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⓪">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③②">Chairs</a>,
+			and to the Public,
+			as well as to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑧">Advisory Committee</a> 
+     <li> indicate that this is a proposal to
+			Rescind,
+			Obsolete,
+			Supersede,
+			or restore,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑧">Recommendation</a> as appropriate 
+     <li> identify the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑨">Recommendation</a> by URL 
+     <li> publish a rationale for the proposal 
+     <li> identify known dependencies
+			and solicit review from all dependent <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦①">Working Groups</a> 
+     <li> solicit public review 
+     <li> specify the deadline for review comments,
+			which <em class="rfc2119">must</em> be at least 28 days
+			after the announcement 
+    </ul>
+    <p>and <em class="rfc2119">should</em></p>
+    <ul>
+     <li> identify known implementations. 
+    </ul>
+    <p>If there was any <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑥">dissent</a> in the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⓪">Advisory Committee review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑥">Team</a> <em class="rfc2119">must</em> publish
+	the substantive content of the dissent to W3C <strong>and the public</strong>,
+	and <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑥">formally address</a> the dissent
+	at least 14 days
+	before publication as an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs③">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec②">Rescinded Recommendation</a>.</p>
+    <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑦">Advisory Committee Appeal</a> of the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑦">Team</a>’s decision.</p>
+    <p>W3C <em class="rfc2119">must</em> publish an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs④">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec③">Rescinded Recommendation</a> 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 <em class="rfc2119">should</em> link
+	to the explanation of <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">Obsoleting and Rescinding W3C Specifications</a> <a data-link-type="biblio" href="#biblio-obs-resc" title="Obsoleting and Rescinding W3C Specifications">[OBS-RESC]</a> as appropriate.</p>
+    <p>Once W3C has published a Rescinded Recommendation,
+	future W3C technical reports <em class="rfc2119">must not</em> include normative references
+	to that technical report.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> W3C strives to ensure that all Technical Reports
+	will continue to be available at their version-specific URL.</p>
+    <h3 class="heading settled" data-level="6.4" id="note-track"><span class="secno">6.4. </span><span class="content"> The Note Track (Notes and Statements)</span><a class="self-link" href="#note-track"></a></h3>
+    <h4 class="heading settled" data-level="6.4.1" id="Note"><span class="secno">6.4.1. </span><span class="content"> Group Notes</span><a class="self-link" href="#Note"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Group Note | Note" id="WGNote">Group Note</dfn> (<abbr>NOTE</abbr>)
+	is published
+	to provide a stable reference for a useful document
+	that is not intended to be a formal standard.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦②">Working Groups</a>, <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①②">Interest Groups</a>,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑧">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③②">AB</a> <em class="rfc2119">may</em> publish work as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②">Notes</a>.
+	Examples include:</p>
+    <ul>
+     <li> supporting documentation for a specification,
+			such as explanations of design principles
+			or use cases and requirements 
+     <li> non-normative guides to good practices 
+    </ul>
+    <p>Some <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote③">Notes</a> are developed through successive <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Note Draft" data-noexport id="note-draft"><span class="bs-old-id" id="draft-note"></span>Note Drafts</dfn> before publication as a full <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote④">Notes</a>,
+	while others are <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①①">published</a> directly as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑤">Note</a>.
+	There are few formal requirements to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①②">publish</a> a document as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑥">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft">Note Draft</a>,
+	and they have no standing as a recommendation of W3C
+	but are simply documents preserved for historical reference.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> does not apply any licensing requirements or commitments for <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑦">Notes</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft①">Note Drafts</a>.</p>
+    <h4 class="heading settled" data-level="6.4.2" id="publishing-notes"><span class="secno">6.4.2. </span><span class="content"> Publishing Notes</span><a class="self-link" href="#publishing-notes"></a></h4>
+    <p>In order to publish a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑧">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft②">Note Draft</a>,
+	the group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record their decision
+			to request publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑨">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft③">Note Draft</a>, and 
+     <li> <em class="rfc2119">should</em> publish documentation
+			of significant changes to the technical report
+			since any previous publication. 
+    </ul>
+    <p>Both <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⓪">Notes</a> and <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft④">Note Drafts</a> can be updated by republishing
+	as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①①">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft⑤">Note Draft</a>.
+	A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑨">technical report</a> <em class="rfc2119">may</em> remain
+	a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①②">Note</a> indefinitely.</p>
+    <h4 class="heading settled" data-level="6.4.3" id="w3c-statement"><span class="secno">6.4.3. </span><span class="bs-old-id" id="memo"></span><span class="content"> Elevating Group Notes to W3C Statement status</span><a class="self-link" href="#w3c-statement"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Statement | W3C Statement" data-noexport id="statement">W3C Statement</dfn> is a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①③">Note</a> that has been endorsed by W3C as a whole.
+	In order to elevate a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①④">Note</a> to <a data-link-type="dfn" href="#statement" id="ref-for-statement②">W3C Statement</a> status,
+	A group <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①①">wide review</a>. 
+     <li> record the group’s decision to request publication as a <a data-link-type="dfn" href="#statement" id="ref-for-statement③">W3C Statement</a>. 
+     <li> show that all issues raised against the document
+			since its first publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑤">Note</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑦">formally addressed</a>. 
+     <li> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④③">Formal Objections</a>. 
+    </ul>
+    <p>A <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑥">Note</a> specifying implementable technology <em class="rfc2119">should not</em> be elevated to <a data-link-type="dfn" href="#statement" id="ref-for-statement④">W3C Statement</a> status;
+	if it does,
+	the request to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑤">Statement</a> <em class="rfc2119">must</em> include rationale
+	for why it should be elevated,
+	and why it is not on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①①">Recommendation track</a>.</p>
+    <p>Once these conditions are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑧">Team</a> <em class="rfc2119">must</em> then
+	begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③①">Advisory Committee Review</a> on the question of
+	whether the document is appropriate to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑥">W3C Statement</a>.
+	During this review period,
+	the <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑦">Note</a> <em class="rfc2119">must not</em> be updated.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#statement" id="ref-for-statement⑦">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑤">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑧">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑧">Advisory Committee Appeal</a> of the decision.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①①⑨">Team</a> must announce the publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑧">W3C Statement</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑨">Advisory Committee</a>, other W3C groups, and the public.</p>
+    <h4 class="heading settled" data-level="6.4.4" id="revising-memo"><span class="secno">6.4.4. </span><span class="content"> Revising W3C Statements</span><a class="self-link" href="#revising-memo"></a></h4>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑥">group decision</a> to do so,
+	groups can request publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑨">W3C Statement</a> with <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑧">editorial changes</a>—​including <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑤">candidate amendment</a>—​without any additional process.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑥">candidate amendment</a> can be folded into the main text of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①⓪">W3C Statement</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①①">Statement</a>,
+	including review by the community to ensure
+	the substantive and editorial soundness of the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑦">candidate amendments</a>.
+	To validate this, the group must request
+	an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③②">Advisory Committee review</a> of the changes it wishes to incorporate.
+	The specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑧">candidate amendments</a> under review <em class="rfc2119">must</em> be identified as <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①⓪">proposed amendments</a> just as in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections" id="ref-for-last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a>.</p>
+    <p>The decision to incorporate <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①①">proposed amendments</a> into <a data-link-type="dfn" href="#statement" id="ref-for-statement①②">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑥">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑨">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑨">Advisory Committee Appeal</a> of the decision.</p>
+    <h3 class="heading settled" data-level="6.5" id="registries"><span class="secno">6.5. </span><span class="content"> The Registry Track</span><a class="self-link" href="#registries"></a></h3>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry">registry</dfn> documents a data set
+	consisting of one or more <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry table" id="registry-table">registry tables</dfn>,
+	each table representing an updatable collection
+	of logically independent, consistently-structured <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry entry" id="registry-entry">registry entries</dfn>.
+	A registry consists of:</p>
+    <ul>
+     <li>the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①">registry definition</a>, defining how the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②">registry tables</a> are structured and maintained 
+     <li>one or more <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table③">registry tables</a>, holding the data set represented by the <a data-link-type="dfn" href="#registry" id="ref-for-registry②">registry</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data">registry data</dfn>) 
+    </ul>
+    <p>The purposes of maintaining a <a data-link-type="dfn" href="#registry" id="ref-for-registry③">registry</a> can include:</p>
+    <dl>
+     <dt>non-collision 
+     <dd> Avoiding the problem
+			of two entities using the same value with different semantics. 
+     <dt>non-duplication 
+     <dd> Avoiding the problem
+			of having two or more different values in use with the same semantics. 
+     <dt>information 
+     <dd> Providing a central index
+			where anyone can find out
+			what a value means
+			and what its formal definition is
+			(and where it is). 
+     <dt>submission 
+     <dd> Ease of adding new terms,
+			including by stakeholders external to the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian">custodian</a> organization. 
+     <dt>consensus 
+     <dd> Promoting a clear consensus of the community on the terms. 
+    </dl>
+    <p>This section of the W3C Process provides a specialized process
+	facilitating the publication and maintenance of such <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table④">registry tables</a>,
+	particularly those required by or closely related to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦⓪">W3C Recommendations</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Not every table in a specification is a potential registry.
+	If the intent or effect is that the table enumerates
+	all the possibilities the authors of the specification expect or envisage,
+	then the table by itself is enough.
+	Similarly, if the table is managed by the Working Group
+	and only updated as part of specification update,
+	then the complexities of registry management are not needed.</p>
+    <h4 class="heading settled" data-level="6.5.1" id="reg-def"><span class="secno">6.5.1. </span><span class="content"> Registry Definitions</span><a class="self-link" href="#reg-def"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-definition">registry definition</dfn> defines what each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑤">registry table</a> is and how it is maintained.
+	It <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Define the scope and purpose of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑥">registry table</a>. 
+     <li> Define the fields of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑦">registry table</a> and their constraints
+			(e.g. values must be drawn from a defined set, or be unique,
+			or only reference publicly available resources,
+			etc.) 
+     <li>
+       Define the policy for changes to existing entries, such as 
+      <ul>
+       <li>whether entries can be deleted or deprecated 
+       <li>whether entries can be changed after being published, and what kinds of changes are allowed 
+       <li>whether previously-deleted unique identifiers can be re-used, or are reserved indefinitely 
+      </ul>
+     <li> Define the method and criteria by which changes are proposed, approved, and incorporated.
+			(For example, a <a data-link-type="dfn" href="#registry" id="ref-for-registry④">registry</a> could define
+			that changes to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry①">registry entries</a> can be proposed using a particular web form or email address,
+			that they must be accompanied by certain background information,
+			or that they do or do not need to be approved by any member of a particular Working Group.) 
+     <li>
+       Identify the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="custodian">custodian</dfn> of the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑧">registry table</a>:
+			the entity to which requests for <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change">registry changes</a> must be sent,
+			and which is responsible for evaluating whether such requests
+			satisfy the criteria defined in the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition②">registry definition</a>. 
+      <p>The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian①">custodian</a> may be the initiating group, the <a data-link-type="dfn" href="#team" id="ref-for-team①②⓪">Team</a>, or a delegated entity.
+			The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian②">custodian</a> for all <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑨">registry tables</a> in a single <a data-link-type="dfn" href="#registry" id="ref-for-registry⑤">registry</a> <em class="rfc2119">should</em> generally be the same entity.</p>
+      <p>If the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian③">custodian</a> of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⓪">registry table</a> ceases to exist or to operate as a custodian
+			(e.g., the relevant group is disbanded, or 
+			the custodian is unresponsive to repeated attempts to make contact),
+			and the <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group⑤">chartered</a> or <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group①">elected group</a> that owns the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition③">registry definition</a> is itself <a href="#GeneralTermination">closed</a> or 
+			unresponsive,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①②①">Team</a> <em class="rfc2119">should</em> propose replacing the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian④">custodian</a>,
+			which <em class="rfc2119">must</em> be confirmed
+			by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③③">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑦">W3C Decision</a>.</p>
+    </ul>
+    <h4 class="heading settled" data-level="6.5.2" id="reg-pub"><span class="secno">6.5.2. </span><span class="content"> Publishing Registries</span><a class="self-link" href="#reg-pub"></a></h4>
+    <p>A <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group⑥">chartered</a> or <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group②">elected group</a> can publish a <a data-link-type="dfn" href="#registry" id="ref-for-registry⑥">registry</a> as a stand-alone <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⓪">technical report</a> on the <a data-link-type="dfn" href="#registry-track" id="ref-for-registry-track">Registry Track</a>,
+	where it is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-report">registry report</dfn>. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦③">Working Groups</a> have the additional option of
+	incorporating a <a data-link-type="dfn" href="#registry" id="ref-for-registry⑦">registry</a> as part of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦①">Recommendation</a>,
+	as an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="embedded-registry"><span class="bs-old-id" id="registry-section"></span>embedded registry</dfn>.</p>
+    <p>The <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report①">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry①">embedded registry</a> <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Clearly label the <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report②">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry②">embedded registry</a>,
+			its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①①">tables</a>,
+			and its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition④">registry definitions</a> as such,
+			including a link to <a href="#registries">§ 6.5 The Registry Track</a> in this Process. 
+     <li> Include the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑤">registry definition</a> for each of its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①②">registry tables</a>. 
+     <li>
+       Provide the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data">registry data</a> by either: 
+      <ul>
+       <li> Including the entire contents of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①③">registry table</a>,
+					either inline in the report
+					(e.g. formatted as a table, or list, or other appropriate representation),
+					or in a machine-readable file published as part of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③①">technical report</a>,
+					or (preferably) both. 
+       <li> Linking to one or more standalone <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report">Registry Data Reports</a> containing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①④">registry tables</a> in human-readable form, machine-readable form,
+					or (preferably) both. 
+      </ul>
+     <li> Include, if the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑤">registry table</a> is provided in a machine-readable file,
+			a definition of the format of that file. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②②">Team</a> <em class="rfc2119">must</em> make available
+	a means for interested parties to be notified of any updates to a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑥">registry table</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since the Process does not impose requirements
+	on changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑦">registry table</a> other than those imposed by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑥">registry definition</a>,
+	acceptance of proposed <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change①">registry changes</a> on behalf of the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian⑤">custodian</a> and
+	publication of an updated <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report③">registry report</a> that contains
+	only <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change②">registry changes</a> since the previous publication
+	can be automated
+	if satisfaction of those rules can be automatically verified.</p>
+    <p>Rules for publication and advancement on the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-track">Registry Track</dfn> are identical to that of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①②">Recommendation Track</a> with the following exceptions:</p>
+    <ul>
+     <li> <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report④">Registry reports</a> are not subject to the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			and therefore none of their publications correspond,
+			to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑦">First Public Working Draft</a>, <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①⓪">Working Draft</a>,
+			or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts③">Patent Review Draft</a> for the purposes of the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+     <li> For the same reason,
+			there is no equivalent to <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec④">Rescinded Recommendation</a> nor to <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation①">Rescinded Candidate Recommendation</a> for <a data-link-type="dfn" href="#registry" id="ref-for-registry⑧">Registries</a>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①①">Working Draft</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-draft"><span class="bs-old-id" id="draft-registry"></span>Registry Draft</dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②②">Candidate Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry">Candidate Registry</dfn>,
+			with <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑨">Candidate Recommendation Snapshot</a> and <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑧">Candidate Recommendation Draft</a> corresponding to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-snapshot">Candidate Registry Snapshot</dfn> and <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-draft">Candidate Registry Draft</dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦②">W3C Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="w3c-registry">W3C Registry</dfn>; <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs⑤">Obsolete Recommendation</a> and <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup①">Superseded Recommendation</a> correspond to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="obsolete-registry">Obsolete Registry</dfn> and <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="superseded-registry">Superseded Registry</dfn>. 
+     <li> Changes that add new features (i.e., <a href="#correction-classes">class 4 changes</a>) are allowed
+			in all <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry①">W3C Registries</a>,
+			without needing them to explicitly indicate that this is allowed. 
+    </ul>
+    <h4 class="heading settled" data-level="6.5.3" id="reg-table-update"><span class="secno">6.5.3. </span><span class="content"> Updating Registry Tables</span><a class="self-link" href="#reg-table-update"></a></h4>
+    <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑧">registry table</a> that are in accordance with the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑦">registry definition</a>,
+	(i.e. <a href="#correction-classes">Class 5 changes</a>)
+	can be made by re-publishing the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③②">technical report</a> that contains the affected table,
+	without needing to satisfy any other requirements for the publication
+	(not even a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑦">group decision</a>, unless this is required by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑧">registry definition</a>).
+	Such <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change③">registry changes</a> do not trigger new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③④">Advisory Committee Reviews</a>,
+	nor Exclusion Opportunities,
+	and do not require verification via an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①①">update request</a>,
+	even for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③③">technical reports</a> at maturities where this would normally be expected.
+	Such publications can be made
+	even in the absence of a group chartered to maintain the registry
+	when the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian⑥">custodian</a> is another entity.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The custodian is only empowered to make <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change④">registry changes</a>.
+	If the group establishing the registry wishes
+	to empower the custodian to add commentary on individual entries,
+	this needs to be part of the registry table’s definition.
+	If other changes are desired,
+	they need to be requested of the group responsible for maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑨">registry definition</a>—​or in the absence of such a group, of the Team.</p>
+    <p>Changes to the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑨">registry tables</a> made in accordance with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑨">candidate</a> or <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①②">proposed amendments</a> to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⓪">registry definition</a> which would not be allowed by the unamended <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①①">registry definition</a> <em class="rfc2119">must</em> be identified as such.</p>
+    <h4 class="heading settled" data-level="6.5.4" id="reg-data-reports"><span class="secno">6.5.4. </span><span class="content"> Registry Data Reports</span><a class="self-link" href="#reg-data-reports"></a></h4>
+    <p>When the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data①">registry data</a> is published in a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③④">technical report</a> from its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①②">registry definition</a>,
+	that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑤">report</a> is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data-report">Registry Data Report</dfn>.
+	This <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑥">technical report</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">Must</em> link to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①③">registry definition</a> establishing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②⓪">registry tables</a> that it contain. 
+     <li> <em class="rfc2119">May</em> contain non-normative introductory text, examples, and notes
+			about the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②①">registry tables</a> and <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry②">entries</a> that it contains.
+			(Changes to these parts are deemed to be <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑨">editorial changes</a>). 
+    </ul>
+    <p><a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report①">Registry Data Reports</a> do not have maturity stages in and of themselves;
+	The maturity stage of the <a data-link-type="dfn" href="#registry" id="ref-for-registry⑨">registry</a> whose <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data②">data</a> they record
+	is that of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑦">technical report</a> holding the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①④">registry definition</a>.</p>
+    <p>Anytime a change is made to a <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑤">registry definition</a>,
+	the group maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑥">registry definition</a> <em class="rfc2119">must</em> update and republish
+	any document holding the corresponding <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②②">registry tables</a> to make it consistent with these changes.</p>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑧">group decision</a> to do so,
+	the group maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑦">registry definition</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report②">Registry Data Report</a> to incorporate <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①⓪">editorial changes</a>.</p>
+    <h4 class="heading settled" data-level="6.5.5" id="reg-ref-specifications"><span class="secno">6.5.5. </span><span class="content"> Specifications that Reference Registries</span><a class="self-link" href="#reg-ref-specifications"></a></h4>
+    <p>Registries document values,
+	they do not define any architectural or interoperability requirements
+	related to those values.
+	All architectural and interoperability requirements
+	pertaining to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry③">registry entries</a> <em class="rfc2119">must</em> be contained in the specifications that reference the registry,
+	and are therefore subject to the processes
+	(including approval and intellectual property provisions)
+	applicable to those referencing specifications.</p>
+    <p>If there are entries that must be implemented,
+	or any other such restrictions,
+	they <em class="rfc2119">must</em> be defined or documented
+	in the referencing specification
+	without dependency on the registry.</p>
+    <div class="example" id="example-87a6a8f6"><a class="self-link" href="#example-87a6a8f6"></a> For example, <span class="allow-2119">“All implementations must implement the <code>Basic-Method</code> as defined in the registry”</span> is not acceptable because
+		a change to the definition of the <code>Basic-Method</code> in the registry would then affect conformance.
+		Instead, the requirement has to be complete in the specification,
+		directly or by reference to another specification.
+		For example <span class="allow-2119">“All implementations must recognize the name <code>Basic-Method</code>,
+		and implement it as defined by section yy of IETF RFC xxxx”</span>.
+		(The Registry is nonetheless expected to contain <code>Basic-Method</code> as an entry.) </div>
+    <h4 class="heading settled" data-level="6.5.6" id="reg-pat"><span class="secno">6.5.6. </span><span class="content"> Registries and Patents</span><a class="self-link" href="#reg-pat"></a></h4>
+    <p>A <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report⑤">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry③">embedded registry</a> is not subject to the W3C Patent Policy,
+	and <em class="rfc2119">must not</em> define any requirements on implementations.
+	For the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (only),
+	any <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry④">embedded registry</a> in a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①③">Recommendation track</a> document
+	is not a normative portion of that specification.</p>
+    <h3 class="heading settled" data-level="6.6" id="switching-tracks"><span class="secno">6.6. </span><span class="content"> Switching Tracks</span><a class="self-link" href="#switching-tracks"></a></h3>
+    <p>Given a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑨">Group decision</a> to do so, <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦④">Working Groups</a> can republish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑧">technical report</a> on a different track than the one it is on,
+	under the following restrictions:</p>
+    <ul>
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑨">technical report</a> that is or was
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦③">W3C Recommendation</a>, <a data-link-type="dfn" href="#statement" id="ref-for-statement①③">W3C Statement</a>, or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts④">Patent Review Draft</a> cannot switch tracks. 
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④⓪">technical report</a> should not switch away from the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①④">Recommendation Track</a> without due consideration of the Patent Policy implications
+			and approval of W3C’s legal counsel
+			if the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑤">Working Group</a> envisions a likelihood of returning to it later. 
+    </ul>
+    <p><a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④①">Technical reports</a> that switch tracks start at
+	their new track’s initial maturity stage,
+	while retaining any established identity (url, shortname, etc.).</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The initial maturity stage of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⑤">Recommendation track</a> is <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①②">Working Draft</a>. <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑧">First Public Working Draft</a> designates a specific type of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①③">Working Draft</a> and is not a separate maturity stage.
+	A document which switches to the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⑥">Recommendation track</a> is only published as a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑨">First Public Working Draft</a> if it was never previously published as such;
+	otherwise, it is simply a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①④">Working Draft</a>.</p>
+    <h3 class="heading settled" data-level="6.7" id="further-reading"><span class="secno">6.7. </span><span class="content"> Further reading</span><a class="self-link" href="#further-reading"></a></h3>
+    <p>Refer to <a href="https://www.w3.org/guide/transitions/">"How to Organize a Recommendation Track Transition"</a> <a data-link-type="biblio" href="#biblio-transition" title="Organize a Technical Report Transition">[TRANSITION]</a> in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a> for practical information about preparing for the reviews
+	and announcements of the various steps,
+	and <a href="https://www.w3.org/guide/standards-track/rec-tips">tips on getting to Recommendation faster</a> <a data-link-type="biblio" href="#biblio-rec-tips" title="Tips for Getting to Recommendation Faster">[REC-TIPS]</a>.
+	Please see also the <a href="https://www.w3.org/guide/standards-track/republishing">Requirements for modification of W3C Technical Reports</a> <a data-link-type="biblio" href="#biblio-republishing" title="In-place modification of W3C Technical Reports">[REPUBLISHING]</a>.</p>
+    <h2 class="heading settled" data-level="7" id="dissemination"><span class="secno">7. </span><span class="content"> <span id="chapterDissemination"></span> Dissemination Policies</span><a class="self-link" href="#dissemination"></a></h2>
+    <h3 class="heading settled" data-level="7.1" id="pub-com"><span class="secno">7.1. </span><span class="content"> Public Communication</span><a class="self-link" href="#pub-com"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②③">Team</a> is responsible for managing communication within W3C
+	and with the general public
+	(e.g., news services, press releases, managing the website and access privileges, and managing calendars).
+	Members <em class="rfc2119">should</em> solicit review by the Team
+	prior to issuing press releases about their work within W3C.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②④">Team</a> makes every effort to ensure the persistence and availability of the following public information:</p>
+    <ul>
+     <li> <a href="#Reports">W3C technical reports</a> whose publication has been approved.
+			Per <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/policies/"><cite>W3C IPR Policies</cite></a>,
+			W3C technical reports (and software) are available free of charge to the general public. 
+     <li> A <a href="https://www.w3.org/mission/">mission statement</a> <a data-link-type="biblio" href="#biblio-mission" title="The W3C Mission statement">[MISSION]</a> that explains the purpose and mission of W3C,
+			the key benefits for Members,
+			and the organizational structure of W3C. 
+     <li> Legal documents,
+			including <a href="https://www.w3.org/membership/agreement/">Membership Agreements</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> and documentation of any legal commitments W3C has with other entities. 
+     <li> The Process Document. 
+     <li> Public results of W3C activities and <a href="#GAEvents">Workshops</a>. 
+    </ul>
+    <p>To keep the Members abreast of W3C meetings, <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW③">Workshops</a>,
+	and review deadlines,
+	the Team provides them with a regular (e.g., weekly) news service
+	and maintains a <a href="https://www.w3.org/events/">calendar</a> <a data-link-type="biblio" href="#biblio-calendar" title="Calendar of all scheduled official W3C events">[CALENDAR]</a> of official W3C events.
+	Members are encouraged to send schedule and event information to the Team for inclusion on this calendar.</p>
+    <h3 class="heading settled" data-level="7.2" id="confidentiality-levels"><span class="secno">7.2. </span><span class="content"> Confidentiality Levels</span><a class="self-link" href="#confidentiality-levels"></a></h3>
+    <p>There are three principal levels of access to W3C information
+	(on the W3C website, in W3C meetings, etc.):
+	public,
+	Member-only,
+	and Team-only.</p>
+    <p>While much information made available by W3C is public,
+	“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Member-Only" id="Member-only">Member-only</dfn>” information
+	is available to authorized parties only,
+	including representatives of Member organizations, <a href="#invited-expert-wg">Invited Experts</a> (as described in <a href="https://www.w3.org/invited-experts/#memaccess">https://www.w3.org/invited-experts/#memaccess</a>),
+	the Advisory Board,
+	the TAG,
+	and the Team.
+	For example,
+	the <a href="#WGCharter">charter</a> of some Working Groups <em class="rfc2119">may</em> specify a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only④">Member-only</a> confidentiality level for group proceedings.</p>
+    <p>“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team-Only" id="Team-only">Team-only</dfn>” information
+	is available to the Team and other authorized parties.</p>
+    <p>Those authorized to access <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑤">Member-only</a> and <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only①">Team-only</a> information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> treat the information as confidential within W3C, 
+     <li> <em class="rfc2119">must</em> use reasonable efforts to preserve that confidentiality, and 
+     <li> <em class="rfc2119">must not</em> release this information to the general public or press,
+			nor beyond the designated level of access. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑤">Team</a> <em class="rfc2119">must</em> provide mechanisms
+	to protect the confidentiality of <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑥">Member-only</a> information
+	and ensure that authorized parties have proper access to this information.
+	Documents <em class="rfc2119">should</em> clearly indicate
+	whether they require <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑦">Member-only</a> confidentiality.
+	Individuals uncertain of the confidentiality level of a piece of information <em class="rfc2119">should</em> contact the Team.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⓪">Advisory Committee representatives</a> <em class="rfc2119">may</em> authorize <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑧">Member-only</a> access to <a href="#member-rep">Member representatives</a> and other individuals employed by the Member
+	who are considered appropriate recipients.
+	For instance,
+	it is the responsibility of the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③①">Advisory Committee representative</a> and other employees
+	and official representatives of the organization
+	to ensure that Member-only news announcements
+	are distributed for internal use only within their organization.
+	Information about Member mailing lists is available
+	in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h3 class="heading settled" data-level="7.3" id="confidentiality-change"><span class="secno">7.3. </span><span class="content"> Changing Confidentiality Level</span><a class="self-link" href="#confidentiality-change"></a></h3>
+    <p>As a benefit of membership,
+	W3C provides some <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only②">Team-only</a> and <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑨">Member-only</a> channels
+	for certain types of communication.
+	For example, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③②">Advisory Committee representatives</a> can send <a href="#ACReview">reviews</a> to a <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only③">Team-only</a> channel.
+	However, for W3C processes with a significant public component,
+	such as the technical report development process,
+	it is also important for information that affects decision-making to be publicly available.
+	The Team <em class="rfc2119">may</em> need to communicate <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only④">Team-only</a> information to a Working Group or the public.
+	Similarly, a Working Group whose proceedings are <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①⓪">Member-only</a> <em class="rfc2119">must</em> make public
+	information pertinent to the technical report development process.</p>
+    <p>This document clearly indicates which information <em class="rfc2119">must</em> be available to Members or the public,
+	even though that information was initially communicated on <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑤">Team-only</a> or <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①①">Member-only</a> channels.
+	Only the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑥">Team</a> and parties authorized by the Team
+	may change the level of confidentiality of this information.
+	When doing so:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑦">Team</a> <em class="rfc2119">must</em> use a version of the information
+			that was expressly provided by the author for the new confidentiality level.
+			In Calls for Review and other similar messages,
+			the Team <em class="rfc2119">should</em> remind recipients to provide such alternatives. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑧">Team</a> <em class="rfc2119">must not</em> attribute the version
+			for the new confidentiality level to the author without the author’s consent. 
+     <li> If the author has not conveyed to the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑨">Team</a> a version
+			that is suitable for another confidentiality level,
+			the Team <em class="rfc2119">may</em> make available a version that reasonably communicates what is required,
+			while respecting the original level of confidentiality,
+			and without attribution to the original author. 
+    </ol>
+    <h2 class="heading settled" data-level="8" id="Liaisons"><span class="secno">8. </span><span class="content"> Liaisons</span><a class="self-link" href="#Liaisons"></a></h2>
+    <p>W3C uses the term <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="liaison">liaison</dfn> 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 <a data-link-type="dfn" href="#team" id="ref-for-team①③⓪">Team</a> due to requirements for public communication;
+	patent,
+	copyright,
+	and other IPR policies;
+	confidentiality agreements;
+	and mutual membership agreements.</p>
+    <p>W3C <em class="rfc2119">may</em> negotiate <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①">technical agreements</a> with another organization.
+	For purposes of the W3C Process,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="agreement" data-noexport id="technical-agreement">technical agreement</dfn> is a formal contract,
+	or a Memorandum of Understanding (<abbr>MoU</abbr>),
+	or a similar document,
+	between W3C and another party or parties,
+	that relates to the technical activity of the Consortium
+	(e.g., its publications, groups, or liaisons).
+	It specifies rights and obligations of each party toward the others.
+	These rights and obligations <em class="rfc2119">may</em> include joint deliverables,
+	an agreed share of technical responsibilities with due coordination,
+	and/or considerations for confidentiality and specific IPR.</p>
+    <p>Non-technical agreements, including
+	those between W3C and its <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑥">Members</a> for the purposes of membership,
+	between W3C and its Partners for the purposes of partnership <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a>,
+	and other agreements related to the operation of the Consortium
+	or to the ordinary provision of services,
+	are not subject to these Process provisions.</p>
+    <p>When considering a <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement②">technical agreement</a> (i.e., before the decision whether to sign is made),
+	the Team <em class="rfc2119">should</em> provide
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④⓪">Advisory Committee</a> with a draft of the proposed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement③">agreement</a>,
+	along with an explanation of how W3C would benefit from signing this <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement④">agreement</a>,
+	for their review and discussion.
+	After addressing any comments,
+	and subject to any management or governance procedures that apply
+	(e.g., formal review of proposed contracts by legal counsel or by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑦">Board</a>),
+	if the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①②">Team decides</a> to proceed with signing the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑤">agreement</a>,
+	the Team <em class="rfc2119">must</em> announce the intent to sign,
+	and provide the final text of the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑥">agreement</a>,
+	with an explanation of signing rationale, to
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④①">Advisory Committee</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③③">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①⓪">Advisory Committee Appeal</a> of the decision to sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑦">agreement</a>.
+	If the proposal is rejected on <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①①">appeal</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③①">Team</a> <em class="rfc2119">must not</em> sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑧">agreement</a> on behalf of W3C
+	unless directed to do so by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑧">Board</a>.
+	A signed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑨">agreement</a> <em class="rfc2119">should</em> be made public.</p>
+    <p>Information about <a href="https://www.w3.org/liaisons/">W3C liaisons with other organizations</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a> and the guidelines W3C follows when creating a liaison is available on the Web.</p>
+    <h2 class="heading settled" data-level="9" id="Submission"><span class="secno">9. </span><span class="bs-old-id" id="SubmissionNo"></span><span class="bs-old-id" id="SubmissionYes"></span><span class="bs-old-id" id="TeamSubmissionRights"></span><span class="bs-old-id" id="SubmissionScope"></span><span class="bs-old-id" id="SubmissionRights"></span><span class="content"> Member Submissions</span><a class="self-link" href="#Submission"></a></h2>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="MemberSubmission">Member Submission</dfn> is a document or set of documents
+	developed outside of W3C,
+	and submitted to W3C
+	by one or more <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑦">Members</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="submitter" id="submitter">Submitter(s)</dfn>)
+	to propose technology or other ideas.
+	After review,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③②">Team</a> <em class="rfc2119">may</em> make the material available at the W3C website.</p>
+    <p>Making a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission">Member Submission</a> available at the W3C website
+	does not indicate endorsement, acceptance, or adoption by W3C,
+	its Team, or its Members.
+	The <a data-link-type="dfn" href="#acknowledged" id="ref-for-acknowledged">acknowledgment</a> of a Submission request
+	does not imply that any action will be taken by W3C.
+	It merely records publicly
+	that the Submission has been made by the Submitter(s).
+	A Member Submission made available by W3C
+	is not a W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④②">technical report</a> and <em class="rfc2119">must not</em> be referred to as
+	an output or “work in progress” of W3C.</p>
+    <p>The <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission①">Member Submission</a> process consists of the following steps:</p>
+    <dl>
+     <dt>Submission 
+     <dd> One of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter">Submitters</a>,
+			copying the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③④">Advisory Committee representatives</a> of the other <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①">Submitters</a> (if any),
+			sends a request to the Team to acknowledge the Submission request.
+			The <a data-link-type="dfn" href="#team" id="ref-for-team①③③">Team</a> and <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②">Submitter(s)</a> communicate to ensure that the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission②">Member Submission</a> is complete. 
+     <dt>Review 
+     <dd>
+       The <a data-link-type="dfn" href="#team" id="ref-for-team①③④">Team</a> reviews the Submission
+			to evaluate its scope, quality, and compliance with the Submission requirements,
+			including licensing requirements: 
+      <ul>
+       <li> The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter③">Submitter(s)</a> and any other authors of the submitted material <em class="rfc2119">must</em> agree
+					to license the Submission under the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a>. 
+       <li> The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments
+					in <a href="https://www.w3.org/policies/patent-policy/#sec-submissions">The W3C Patent Policy § sec-submissions</a>. 
+      </ul>
+      <p>Detailed procedures and requirements are defined by the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑤">Team</a> and documented in the “<a href="https://www.w3.org/submissions/guide/">Member submissions guidebook</a>” <a data-link-type="biblio" href="#biblio-member-sub" title="Member submissions guidebook">[MEMBER-SUB]</a>.</p>
+     <dt>Decision 
+     <dd>
+       After review, the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑥">Team</a> <em class="rfc2119">must</em> either <a data-link-type="dfn" href="#acknowledged" id="ref-for-acknowledged①">acknowledge</a> or <a data-link-type="dfn" href="#rejected" id="ref-for-rejected">reject</a> the Submission request. 
+      <ul>
+       <li> If <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="acknowledged">acknowledged</dfn>,
+					the Team <em class="rfc2119">must</em> make the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission③">Member Submission</a> available
+					at the public W3C website
+					alongside other <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a> <a data-link-type="biblio" href="#biblio-submission-list" title="The list of acknowledged Member Submissions">[SUBMISSION-LIST]</a>. 
+       <li> If <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rejected">rejected</dfn>,
+					the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑦">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⑤">Advisory Committee representative(s)</a> of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter④">Submitter(s)</a>,
+					and <em class="rfc2119">must</em> provide rationale if requested by the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑤">Submitter(s)</a>.
+					The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑥">Submitter(s)</a> <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals③">Submission Appeal</a>. 
+      </ul>
+    </dl>
+    <p>The <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⑥">Advisory Committee representative(s)</a> of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑦">Submitter(s)</a> <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals④">Submission Appeal</a>.
+	The procedure for handling <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="submission-appeals">Submission Appeals</dfn> is the same as for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④④">Formal Objections</a>,
+	except that an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①②">AC Appeal</a> is not possible
+	and both the Formal Objection and the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report⑥">Council Report</a> are confidential to the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑧">Team</a>, <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑨">TAG</a>, and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③③">AB</a>.</p>
+    <h2 class="heading settled" data-level="10" id="GAProcess"><span class="secno">10. </span><span class="content"> Process Evolution</span><a class="self-link" href="#GAProcess"></a></h2>
+    <p>Revision of the W3C Process and related documents (see below) undergoes similar <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②②">consensus</a>-building processes as for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④③">technical reports</a>,
+	with the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③④">Advisory Board</a> acting as the sponsoring <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑥">Working Group</a>.
+	The documents may be developed by the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑤">AB</a> or by another group to whom the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑥">AB</a> has delegated development.
+	Review includes
+	soliciting input from the W3C community,
+	and in particular the Team.</p>
+    <p>The documents covered by this section are:</p>
+    <ul>
+     <li data-md>
+      <p>the W3C Process (this document)</p>
+     <li data-md>
+      <p>the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a></p>
+     <li data-md>
+      <p>the W3C Code of Conduct <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a></p>
+     <li data-md>
+      <p>The W3C Document License <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a></p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑦">Advisory Board</a> initiates review as follows:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③⑨">Team</a> sends a Call for Review to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④②">Advisory Committee</a> and other W3C groups. 
+     <li> After comments have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑧">formally addressed</a> and the document possibly modified,
+			the Team seeks endorsement from the Members by initiating an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑤">Advisory Committee review</a>.
+			The review period <em class="rfc2119">must</em> last at least <span class="time-interval">28 days</span>. 
+     <li> <a href="#ACReviewAfter">After the Advisory Committee review</a>,
+			following a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑧">W3C decision</a> to adopt the document(s),
+			the Team does so
+			and sends an announcement to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④③">Advisory Committee</a>.
+			Advisory Committee representatives <em class="rfc2119">may</em> initiate
+			an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①③">Advisory Committee Appeal</a> to W3C. 
+    </ol>
+    <p class="note" role="note"><span class="marker">Note:</span> As of June 2020,
+	the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">Patent Policy</a> is developed in the <a href="https://www.w3.org/2004/pp/psig/">Patents and Standards Interest Group</a>,
+	the <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">Code of Conduct</a> in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
+	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.</p>
+    <h2 class="non-normative nonum heading settled" id="old-terms"><span class="content"> Appendix A: Retired Terminology</span><a class="self-link" href="#old-terms"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>Previous versions of this process defined and used various concepts and document statuses
+	that have since been retired or renamed.
+	For ease of reference,
+	this appendix lists the more notable ones,
+	and it links to the the definition or relevant section
+	in the most recent version of the Process that used them,
+	and gives the more recent equivalent term when there is one.</p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rec-amended">Amended Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2020/Process-20200915/#rec-amended">in section 6.2.1 of the 2020 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="edited-recommendation">Edited Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2019/Process-20190301/#maturity-levels">in section 6.1.2 of the 2019 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call">Last Call</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2005/10/Process-20051014/tr.html#last-call">in section 7.4.2 of the 2005 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="maturity-levels">Maturity level</dfn> (renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#maturity-levels">in section 6.3.1 of the 2021 Process</a>,
+			now called <a href="#maturity-stages">maturity stage</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fdn-member-consortium">Member Consortium</dfn>, plural: Member Consortia
+			(renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#fdn-member-consortium">in section 2.1.2.1 of the 2021 Process</a>,
+			now called <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑥">Member Association</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mou">Memorandum of Understanding</dfn>, plural: Memoranda of Understanding, abbreviation: MoU
+			(renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#mou">in section 9 of the 2021 Process</a>,
+			now called <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①⓪">technical agreement</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="other-charter">Other Charter</dfn> (renamed term) 
+     <dd> Last used <a href="https://www.w3.org/2020/Process-20200915/#other-charter">in section 5.2.6 of the 2020 Process</a>,
+			now called <a data-link-type="dfn" href="#exclusion-draft-charter" id="ref-for-exclusion-draft-charter">Exclusion Draft Charter</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="RecsPR">Proposed Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/policies/process/20231103/#RecsPR">in section 6.3.1 of the 2023 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="TeamSubmission">Team Submissions</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2019/Process-20190301/#TeamSubmission">in section 2.2.1 of the 2019 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-W3CChair">W3C Chair</dfn> (renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2014/Process-20140801/#def-W3CChair">in section 2.2 of the 2014 Process</a>,
+			now called <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑨">CEO</a>. 
+    </dl>
+    <h2 class="non-normative nonum heading settled" id="acks"><span class="content"> Appendix B: Acknowledgments</span><a class="self-link" href="#acks"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>The editors are grateful to the following people,
+	who as interested individuals and/or with the affiliation(s) listed,
+	have contributed to this proposal for a revised Process:
+	Adam Basha,
+	Anna Weinberg (Apple)
+	Charles McCathie Nevile,
+	Chris Lilley (W3C),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	Coralie Mercier (W3C),
+	David W. Singer (Apple),
+	Denis Ah-Kang (W3C),
+	Dominique Hazael-Massieux (W3C),
+	Ian Jacobs (W3C),
+	Jeffrey Yasskin (Google),
+	Jill Schmidt (Apple),
+	Marcos Cáceres (Apple),
+	Mark Nottingham,
+	Martin Thomson (Mozilla),
+	Michael Champion,
+	Michael Sirtori (Intel),
+	Mike Smith (W3C),
+	Nick Doty (Center for Democracy and Technology),
+	Nigel Megitt (BBC),
+	Philippe Le Hégaret (W3C),
+	Sam Sneddon (Apple),
+	Shawn Lawton Henry (W3C),
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Theresa O’Connor (Apple),
+	Vivien Lacourba (W3C).</p>
+    <p>The editors are sorry for forgetting any names,
+	and grateful to those who have listened patiently to conversations about this document
+	without feeling a need to add more.</p>
+    <p>The following individuals contributed to the development of earlier versions of the Process:
+	Alex Russell (Google),
+	Andreas Tai (Institut fuer Rundfunktechnik),
+	Andrew Betts (Fastly),
+	Ann Bassetti (The Boeing Company),
+	Anne van Kesteren,
+	Art Barstow (Nokia, unaffiliated),
+	Bede McCall (MITRE),
+	Ben Wilson,
+	Brad Hill (Facebook),
+	Brian Kardell (JQuery, Igalia),
+	Carine Bournez (W3C),
+	Carl Cargill (Netscape, Sun Microsystems, Adobe),
+	Charles McCathie Nevile (ConsenSys),
+	Chris Lilley (W3C),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	Claus von Riegen (SAP AG),
+	Coralie Mercier (W3C),
+	Cullen Jennings (Cisco),
+	Dan Appelquist (Telefonica, Samsung),
+	Dan Connolly (W3C),
+	Daniel Dardailler (W3C),
+	Daniel Glazman (Disruptive Innovations),
+	David Baron (Mozilla),
+	David Fallside (IBM),
+	David W. Singer (Apple),
+	David Singer (IBM),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Don Brutzman (Web3D),
+	Don Deutsch (Oracle),
+	Eduardo Gutentag (Sun Microsystems),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Florian Rivoal,
+	Fuqiao Xue (W3C),
+	Geoffrey Creighton (Microsoft),
+	Giri Mandyam (Qualcomm),
+	Gregg Kellogg,
+	Hadley Beeman,
+	Håkon Wium Lie (Opera Software),
+	Helene Workman (Apple),
+	Henri Sivonen (Mozilla),
+	Ian Hickson (Google),
+	Ian Jacobs (W3C),
+	Ivan Herman (W3C),
+	J Alan Bird (W3C),
+	Jay Kishigami 岸上順一 (NTT),
+	Jean-Charles Verdié (MStar),
+	Jean-François Abramatic (IBM, ILOG, W3C),
+	Jeff Jaffe (W3C),
+	Jeffrey Yasskin (Google),
+	Jim Bell (HP),
+	Jim Miller (W3C),
+	Joe Hall (CDT),
+	John Klensin (MCI),
+	Josh Soref (BlackBerry, unaffiliated),
+	Judy Brewer (W3C),
+	Judy Zhu 朱红儒 (Alibaba),
+	Kari Laihonen (Ericsson),
+	Karl Dubost (Mozilla),
+	Ken Laskey (MITRE),
+	Kevin Fleming (Bloomberg),
+	Klaus Birkenbihl (Fraunhofer Gesellschaft),
+	Larry Masinter (Adobe Systems),
+	Lauren Wood (unaffiliated),
+	Léonie Watson (The Paciello Group),
+	Liam Quin (W3C),
+	Marcos Cáceres (Mozilla),
+	Maria Courtemanche (IBM),
+	Mark Crawford (SAP),
+	Mark Nottingham,
+	Michael Champion (Microsoft),
+	Michael Geldblum (Oracle),
+	Mike West (Google),
+	Mitch Stoltz (EFF),
+	Natasha Rooney (GSMA),
+	Nigel Megitt (BBC),
+	Olle Olsson (SICS),
+	Ora Lassila (Nokia),
+	Paul Cotton (Microsoft),
+	Paul Grosso (Arbortext),
+	Peter Linss,
+	Peter Patel-Schneider,
+	Philippe Le Hégaret (W3C),
+	Qiuling Pan (Huawei),
+	Ralph Swick (W3C),
+	Renato Iannella (IPR Systems),
+	Rigo Wenning (W3C),
+	Rob Sanderson (J Paul Getty Trust),
+	Robin Berjon (W3C),
+	Sally Khudairi (W3C),
+	Sam Ruby (IBM),
+	Sam Sneddon,
+	Samuel Weiler (W3C),
+	Sandro Hawke (W3C),
+	Sangwhan Moon (Odd Concepts),
+	Scott Peterson (Google),
+	Shawn Lawton Henry,
+	Steve Holbrook (IBM),
+	Steve Zilles (Adobe Systems)
+	Steven Pemberton (CWI),
+	TV Raman (Google),
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Terence Eden (Her Majesty’s Government),
+	Thomas Reardon (Microsoft),
+	Tim Berners-Lee (W3C),
+	Tim Krauskopf (Spyglass),
+	Travis Leithead (Microsoft),
+	Virginia Fournier (Apple),
+	Virginie Galindo (Gemalto),
+	Wayne Carr (Intel),
+	Wendy Fong (Hewlett-Packard),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <h2 class="non-normative nonum heading settled" id="changes"><span class="content"> Appendix C: Changes</span><a class="self-link" href="#changes"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <h3 class="no-num heading settled" id="changes-2025"><span class="content"> Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></span><a class="self-link" href="#changes-2025"></a></h3>
+    <p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
+	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2Fsnapshots%2F2025-07-31">diff from Process 2023 to this latest version</a>,
+	as well as
+	a <a href="https://github.com/w3c/process/compare/p2023_1...p2025">detailed log of all changes since then</a> are available. </p>
+    <p>In addition to a number of editorial adjustments and minor tweaks, the following is a summary of the main differences:</p>
+    <dl>
+     <dt id="changes-2025-tr"><a class="self-link" href="#changes-2025-tr"></a>Changes to technical reports and their publication 
+     <dd>
+      <ul>
+       <li> <strong> Retire the Proposed Recommendation phase of the Recommendation track. </strong> It was only used as a short-lived transition
+					during which various verifications and votes about CR were done.
+					These can be done on a CR
+					without having to republish it as a separate thing.
+					This simplifies the Process without changing the actual quality or consensus expectations.
+					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 
+       <li id="streamlined-update"><a class="self-link" href="#streamlined-update"></a> Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
+					This was meant to enable REC track publication with fewer/faster approval steps
+					when some stricter than usual criteria were fulfilled.
+					However, regular REC track publication have improved enough
+					that this became unnecessary,
+					and nobody was using it.
+					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>) 
+       <li> Add a requirement to make progress on external issues for update requests
+					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>) 
+       <li> Drop the requirement to publish every 6 months if nothing has changed.
+					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>) 
+       <li> Enable Team to replace defunct registry custodians when no-one else can.
+					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>) 
+       <li> Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
+					in addition to Working Groups.
+					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>) 
+       <li> Rename “registry sections” to <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry⑤">embedded registries</a> to avoid confusion over whether they can be split across multiple sections of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦④">Recommendation</a>.
+					(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>) 
+       <li> Rename "Draft Note" into "Note Draft",
+					and "Draft Registry" into "Registry Draft"
+					to be consistent with other statuses that uses the word "Draft",
+					and to make that word stand out more.
+					(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>) 
+       <li> Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
+					and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>). 
+       <li> Consolidate and harmonize into <a href="#no-group-maintenance">one section</a> the various parts of the Process
+					that described whether and how the Team can maintain technical reports
+					that no longer have a Group chartered to maintain them.
+					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>) 
+      </ul>
+     <dt id="changes-2025-charter"><a class="self-link" href="#changes-2025-charter"></a>Changes to chartering 
+     <dd>
+      <ul>
+       <li> <strong> Introduce a formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①②">Charter Refinement</a> phase prior to the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑥">AC Review</a>. </strong> (See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>) 
+       <li> Be more specific about which types of changes to a charter must go through AC Review.
+					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>) 
+       <li> Require Chairs to be listed in Charters.
+					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>) 
+       <li> Reorganize and rephrase <a href="#CharterReview">§ 4.4 Charter Review and Approval</a> for readability and ease of understanding.
+					This change, while moderate in size, is purely editorial.
+					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>) 
+      </ul>
+     <dt id="changes-2025-decisions"><a class="self-link" href="#changes-2025-decisions"></a>Changes to formal decision making and escalation 
+     <dd>
+      <ul>
+       <li> Adjust the rules guiding initiation of Councils,
+					to make the deadline strict,
+					and to provide a fallback mechanism if they are not met.
+					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>) 
+       <li> Make the Council’s short-circuit a little more flexible.
+					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>) 
+       <li> Exclude TAG/AB Members from voting on TAG/AB proposals in Councils.
+					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>) 
+       <li> Limit the involvement of Tim Berners-Lee to the TAG proper,
+					not including the Council.
+					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>) 
+       <li> Council dismissal vote counts must be reported.
+					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>) 
+       <li> Require documentation of how Formal Objections get resolved.
+					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>) 
+       <li> Put constraints on the timing of making Formal Objections public.
+					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>) 
+       <li> Fine-tune the rules about
+					how changes can be incorporated into a proposal
+					following an AC Review.
+					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>) 
+       <li> Adjust AC appeal vote threshold based on participation,
+					aligning with the thresholds and super majority requirements
+					for "Requisite Member Vote" from the W3C Bylaws.
+					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>) 
+       <li> Let the originator of a proposal decide whether to try again
+					after addressing feedback
+					following an AC Appeal.
+					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>) 
+       <li> Simplify provisions regarding substitute representatives and proxies.
+					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>) 
+      </ul>
+     <dt id="changes-other"><a class="self-link" href="#changes-other"></a>Other changes 
+     <dd>
+      <ul>
+       <li> Reuse the bylaws’ notion of Good Standing,
+					and restrict TAG and AB elections
+					as well as AC Votes where a decision is made based on counting ballots
+					to Members in Good Standing.
+					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a> and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>) 
+       <li> The section on Member Submissions was significantly shortened and simplified,
+					reducing the complexity under formal Process authority,
+					and shifting much of the material to /Guide,
+					under Team authority.
+					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a> and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>) 
+       <li> Clarify how the outcome of certain ballots are determined.
+					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>) 
+       <li> Stop citing the superseded TAG charter.
+					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>) 
+       <li> Clarify amount of leeway around incomplete nominations to TAG or AB elections.
+					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>) 
+       <li> Shift most of the non-normative discussion about Workshops to <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>,
+					and reorganize the remaining normative requirements.
+					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>) 
+       <li> The URL of this document was changed
+					from /Consortium/Process/ to /policies/process/
+					for better integration in the W3C website architecture. 
+      </ul>
+      <h3 class="no-num heading settled" id="changes-previous"><span class="bs-old-id" id="changes-2017"></span><span class="bs-old-id" id="changes-2018"></span><span class="bs-old-id" id="changes-2019"></span><span class="bs-old-id" id="changes-2020"></span><span class="bs-old-id" id="changes-2021"></span><span class="bs-old-id" id="changes-2023"></span><span class="bs-old-id" id="changes-2023-1"></span><span class="content"> Changes since earlier versions</span><a class="self-link" href="#changes-previous"></a></h3>
+      <p>Changes since earlier versions of the Process are detailed
+	in the <a href="https://www.w3.org/policies/process/20231103/#changes">changes section of the previous version</a> of the Process.</p>
+    </dl>
+   </main>
+   <div data-fill-with="conformance">
+    <h2 class="no-ref no-num heading settled" id="w3c-conformance"><span class="content">Conformance</span><a class="self-link" href="#w3c-conformance"></a></h2>
+    <h3 class="no-ref no-num heading settled" id="w3c-conventions"><span class="content">Document conventions</span><a class="self-link" href="#w3c-conventions"></a></h3>
+    <p>Conformance requirements are expressed
+    with a combination of descriptive assertions
+    and RFC 2119 terminology.
+    The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
+    in the normative parts of this document
+    are to be interpreted as described in RFC 2119.
+    However, for readability,
+    these words do not appear in all uppercase letters in this specification. </p>
+    <p>All of the text of this specification is normative
+    except sections explicitly marked as non-normative, examples, and notes. <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a> </p>
+    <p>Examples in this specification are introduced with the words “for example”
+    or are set apart from the normative text
+    with <code>class="example"</code>,
+    like this: </p>
+    <div class="example" id="w3c-example">
+     <a class="self-link" href="#w3c-example"></a> 
+     <p>This is an example of an informative example. </p>
+    </div>
+    <p>Informative notes begin with the word “Note”
+    and are set apart from the normative text
+    with <code>class="note"</code>,
+    like this: </p>
+    <p class="note" role="note">Note, this is an informative note.</p>
+   </div>
+   <script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script>
+  </main>
+  <h2 class="no-num no-ref heading settled" id="index"><span class="content">Index</span><a class="self-link" href="#index"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="content">Terms defined by this specification</span><a class="self-link" href="#index-defined-here"></a></h3>
+  <ul class="index">
+   <li><a href="#advisory-board">AB</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">AC</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">AC Appeal</a><span>, in § 5.9</span>
+   <li><a href="#acknowledged">acknowledged</a><span>, in § 9</span>
+   <li><a href="#advisory-committee-representative">AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">AC Review</a><span>, in § 5.7</span>
+   <li><a href="#adequate-implementation">adequate implementation experience</a><span>, in § 6.3.2</span>
+   <li><a href="#adopted-draft">Adopted Draft</a><span>, in § 4.3</span>
+   <li><a href="#advisory-board">Advisory Board</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">Advisory Committee</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">Advisory Committee Appeal</a><span>, in § 5.9</span>
+   <li><a href="#advisory-committee-representative">Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">Advisory Committee review</a><span>, in § 5.7</span>
+   <li><a href="#affirm">affirm</a><span>, in § 5.6.2.7</span>
+   <li><a href="#technical-agreement">agreement</a><span>, in § 8</span>
+   <li><a href="#allow-new-features">allow new features</a><span>, in § 6.3.1</span>
+   <li><a href="#alternate-ac-representative">alt AC rep</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#rec-amended">Amended Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#advisory-committee-appeal">Appeal</a><span>, in § 5.9</span>
+   <li><a href="#appeal-vote">appeal vote</a><span>, in § 5.9</span>
+   <li><a href="#at-risk">at risk</a><span>, in § 6.3.7</span>
+   <li><a href="#bod">Board</a><span>, in § 2.2</span>
+   <li><a href="#bod">Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#bod">BoD</a><span>, in § 2.2</span>
+   <li><a href="#reviewform">Call for Review</a><span>, in § 5.7.1</span>
+   <li><a href="#candidate-addition">candidate addition</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-amendment">candidate amendment</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-correction">candidate correction</a><span>, in § 6.2.5</span>
+   <li><a href="#RecsCR">Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">Candidate Recommendation Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-review-period">Candidate Recommendation review period</a><span>, in § 6.3.7</span>
+   <li><a href="#candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-registry">Candidate Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-draft">Candidate Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-snapshot">Candidate Registry Snapshot</a><span>, in § 6.5.2</span>
+   <li><a href="#ceo">CEO</a><span>, in § 2.2</span>
+   <li><a href="#GeneralChairs">Chair</a><span>, in § 3.4.1</span>
+   <li><a href="#chair-decisions">chair decisions</a><span>, in § 5.1</span>
+   <li><a href="#charter">charter</a><span>, in § 4.3</span>
+   <li><a href="#charter-draft">charter draft</a><span>, in § 4.1</span>
+   <li><a href="#chartered-group">chartered groups</a><span>, in § 3.4</span>
+   <li><a href="#dfn-charter-extension">charter extension</a><span>, in § 4.6</span>
+   <li><a href="#chartering-facilitator">Chartering Facilitator</a><span>, in § 4.2</span>
+   <li><a href="#charter-refinement">charter refinement</a><span>, in § 4.2</span>
+   <li><a href="#charter-review-notice">charter review notice</a><span>, in § 4.1</span>
+   <li><a href="#def-Consensus">Consensus</a><span>, in § 5.2.1</span>
+   <li><a href="#convened">convened</a><span>, in § 5.6.2.6</span>
+   <li><a href="#w3c-council">Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#council-report">Council Report</a><span>, in § 5.6.2.8</span>
+   <li><a href="#council-staff-contact">Council Staff Contact</a><span>, in § 5.6.2.1</span>
+   <li><a href="#RecsCR">CR</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">CRD</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-snapshot">CRS</a><span>, in § 6.3.1</span>
+   <li><a href="#custodian">custodian</a><span>, in § 6.5.1</span>
+   <li><a href="#discontinuedREC">Discontinued Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#dismissed">dismiss</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissal</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissed</a><span>, in § 5.6.2.3</span>
+   <li><a href="#def-Dissent">Dissent</a><span>, in § 5.2.1</span>
+   <li><a href="#distributed-meeting">distributed meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#editors-draft">ED</a><span>, in § 6.3.1</span>
+   <li><a href="#edited-recommendation">Edited Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#editors-draft">Editor Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#editorial-change">editorial change</a><span>, in § 6.2.3</span>
+   <li><a href="#editors-draft">Editor's Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#elected-group">elected groups</a><span>, in § 3.3</span>
+   <li><a href="#embedded-registry">embedded registry</a><span>, in § 6.5.2</span>
+   <li><a href="#erratum">errata</a><span>, in § 6.2.4</span>
+   <li><a href="#erratum">erratum</a><span>, in § 6.2.4</span>
+   <li><a href="#exclusion-draft">Exclusion Draft</a><span>, in § 4.3</span>
+   <li><a href="#exclusion-draft-charter">Exclusion Draft Charter</a><span>, in § 4.3</span>
+   <li><a href="#ftf-meeting">face-to-face meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#fpwd">First Public Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#formally-addressed">formally addressed</a><span>, in § 5.3</span>
+   <li><a href="#FormalObjection">Formal Objection</a><span>, in § 5.5</span>
+   <li><a href="#fully-addressed">fully addressed</a><span>, in § 5.6.2.7</span>
+   <li><a href="#good-standing">Good Standing</a><span>, in § 2.1.3</span>
+   <li><a href="#w3c-group">group</a><span>, in § 3</span>
+   <li><a href="#group-decision">group decision</a><span>, in § 5.1</span>
+   <li><a href="#WGNote">Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsIG">Interest Groups</a><span>, in § 3.4</span>
+   <li><a href="#invited-expert-in-an-interest-group">Invited Expert in an Interest Group</a><span>, in § 3.4.3.4</span>
+   <li><a href="#invited-expert-in-a-working-group">Invited Expert in a Working Group</a><span>, in § 3.4.3.3</span>
+   <li><a href="#last-call">Last Call</a><span>, in § Unnumbered section</span>
+   <li><a href="#last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-review">Last Call for Review of Proposed Amendments</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#liaison">liaison</a><span>, in § 8</span>
+   <li><a href="#maturity-levels">Maturity level</a><span>, in § Unnumbered section</span>
+   <li><a href="#w3c-member">Member</a><span>, in § 2.1</span>
+   <li><a href="#member-association">Member Association</a><span>, in § 2.1.2.1</span>
+   <li><a href="#member-association">Member Associations</a><span>, in § 2.1.2.1</span>
+   <li><a href="#fdn-member-consortium">Member Consortium</a><span>, in § Unnumbered section</span>
+   <li><a href="#Member-only">Member-Only</a><span>, in § 7.2</span>
+   <li><a href="#member-representative-in-an-interest-group">Member representative in an Interest Group</a><span>, in § 3.4.3.2</span>
+   <li><a href="#member-representative-in-a-working-group">Member representative in a Working Group</a><span>, in § 3.4.3.1</span>
+   <li><a href="#MemberSubmission">Member Submission</a><span>, in § 9</span>
+   <li><a href="#mou">Memorandum of Understanding</a><span>, in § Unnumbered section</span>
+   <li><a href="#minor-changes">minor changes</a><span>, in § 4.4.2</span>
+   <li><a href="#minority-opinion">Minority Opinion</a><span>, in § 5.6.2.7</span>
+   <li><a href="#minutes">minutes</a><span>, in § 3.1.2.2</span>
+   <li><a href="#WGNote">Note</a><span>, in § 6.4.1</span>
+   <li><a href="#note-draft">Note Draft</a><span>, in § 6.4.1</span>
+   <li><a href="#not-required">not required</a><span>, in § Unnumbered section</span>
+   <li><a href="#RecsObs">Obsolete Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#obsolete-registry">Obsolete Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#other-charter">Other Charter</a><span>, in § Unnumbered section</span>
+   <li><a href="#overrule">overrule</a><span>, in § 5.6.2.7</span>
+   <li><a href="#overturn">overturn</a><span>, in § 5.6.2.7</span>
+   <li><a href="#participant">participant</a><span>, in § 3</span>
+   <li><a href="#igparticipant">participants in an Interest Group</a><span>, in § 3.4.2</span>
+   <li><a href="#wgparticipant">participants in a Working Group</a><span>, in § 3.4.2</span>
+   <li><a href="#inv-expert-info">participate in a Working Group as an Invited Expert</a><span>, in § 3.4.3.3</span>
+   <li><a href="#patent-review-drafts">Patent Review Drafts</a><span>, in § 6.3.1</span>
+   <li><a href="#primary-affiliation">primary affiliation</a><span>, in § 3.3.3.3</span>
+   <li><a href="#proposed-additions">proposed additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#proposed-amendments">proposed amendments</a><span>, in § 6.3.10.4</span>
+   <li><a href="#proposed-corrections">proposed corrections</a><span>, in § 6.3.10.4</span>
+   <li><a href="#RecsPR">Proposed Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#public-participant-ig">public participants</a><span>, in § 3.4.2</span>
+   <li><a href="#publishing">publish</a><span>, in § 6.2.1</span>
+   <li><a href="#RecsW3C">REC</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsW3C">Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">Recommendation-track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">Recommendation Track document</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track-document">Recommendation-track document</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">REC Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">REC Track document</a><span>, in § 6.3.1</span>
+   <li><a href="#registry">registry</a><span>, in § 6.5</span>
+   <li><a href="#registry-change">registry change</a><span>, in § 6.2.3</span>
+   <li><a href="#registry-data">registry data</a><span>, in § 6.5</span>
+   <li><a href="#registry-data-report">Registry Data Report</a><span>, in § 6.5.4</span>
+   <li><a href="#registry-definition">registry definition</a><span>, in § 6.5.1</span>
+   <li><a href="#registry-draft">Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-entry">registry entry</a><span>, in § 6.5</span>
+   <li><a href="#registry-report">registry report</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-table">registry table</a><span>, in § 6.5</span>
+   <li><a href="#registry-track">Registry Track</a><span>, in § 6.5.2</span>
+   <li><a href="#rejected">rejected</a><span>, in § 9</span>
+   <li><a href="#related-member">Related Member</a><span>, in § 2.1.2.2</span>
+   <li><a href="#renounce">renounce</a><span>, in § 5.6.2.3</span>
+   <li><a href="#renounce">renunciation</a><span>, in § 5.6.2.3</span>
+   <li><a href="#rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#RescindedRec">Rescinded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#group-decision">resolution</a><span>, in § 5.1</span>
+   <li><a href="#TeamContact">Staff Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#statement">Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#submission-appeals">Submission Appeals</a><span>, in § 9</span>
+   <li><a href="#submitter">submitter</a><span>, in § 9</span>
+   <li><a href="#subsidiary">subsidiary</a><span>, in § 2.1.2.2</span>
+   <li><a href="#substantive-change">substantive change</a><span>, in § 6.2.3</span>
+   <li><a href="#mtg-substitute">substitute</a><span>, in § 3.4.2</span>
+   <li><a href="#RecsSup">Superseded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#superseded-registry">Superseded Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#supplemental-confidential-council-report">Supplemental Confidential Council Report</a><span>, in § 5.6.2.8</span>
+   <li><a href="#technical-architecture-group">TAG</a><span>, in § 3.3.2.1</span>
+   <li><a href="#team">Team</a><span>, in § 2.2</span>
+   <li><a href="#team-contact">Team Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#team-correction">Team correction</a><span>, in § 6.2.6</span>
+   <li><a href="#team-decision">Team Decision</a><span>, in § 5.1</span>
+   <li><a href="#Team-only">Team-Only</a><span>, in § 7.2</span>
+   <li><a href="#team-representative-in-an-interest-group">Team representative in an Interest Group</a><span>, in § 3.4.3.6</span>
+   <li><a href="#team-representative-in-a-working-group">Team representative in a Working Group</a><span>, in § 3.4.3.5</span>
+   <li><a href="#team-decision">Team's Decision</a><span>, in § 5.1</span>
+   <li><a href="#TeamSubmission">Team Submissions</a><span>, in § Unnumbered section</span>
+   <li><a href="#technical-agreement">technical agreement</a><span>, in § 8</span>
+   <li><a href="#technical-architecture-group">Technical Architecture Group</a><span>, in § 3.3.2.1</span>
+   <li><a href="#technical-report">Technical Report</a><span>, in § 6.2.1</span>
+   <li><a href="#trans-req">Transition Requests</a><span>, in § 6.3.3</span>
+   <li><a href="#def-Unanimity">Unanimity</a><span>, in § 5.2.1</span>
+   <li><a href="#update-requests">Update Requests</a><span>, in § 6.3.4</span>
+   <li><a href="#upheld">upheld</a><span>, in § 5.6.2.7</span>
+   <li><a href="#bod">W3C Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#RecsCR">W3C Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#def-W3CChair">W3C Chair</a><span>, in § Unnumbered section</span>
+   <li><a href="#w3c-council">W3C Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">W3C Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#def-w3c-decision">W3C decision</a><span>, in § 5.1</span>
+   <li><a href="#fellows">W3C Fellows</a><span>, in § 2.2</span>
+   <li><a href="#w3c-group">W3C Group</a><span>, in § 3</span>
+   <li><a href="#w3c-member">W3C Member</a><span>, in § 2.1</span>
+   <li><a href="#RecsW3C">W3C Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">W3C Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">W3C Recommendation Track document</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-registry">W3C Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#statement">W3C Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#team">W3C Team</a><span>, in § 2.2</span>
+   <li><a href="#RecsWD">W3C Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsWD">WD</a><span>, in § 6.3.1</span>
+   <li><a href="#dfn-wide-review">wide review</a><span>, in § 6.2.2.1</span>
+   <li><a href="#RecsWD">Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#GroupsWG">Working Groups</a><span>, in § 3.4</span>
+   <li><a href="#EventsW">Workshop</a><span>, in § 2.1.1</span>
+  </ul>
+  <h3 class="no-num no-ref heading settled" id="index-defined-elsewhere"><span class="content">Terms defined by reference</span><a class="self-link" href="#index-defined-elsewhere"></a></h3>
+  <ul class="index">
+   <li>
+    <a data-link-type="biblio">[W3C-PATENT-POLICY]</a> defines the following terms:
+    <ul>
+     <li><span class="dfn-paneled" id="33fd2aef">Exclusion Opportunity</span>
+     <li><span class="dfn-paneled" id="74c78a1e">Patent Advisory Group</span>
+    </ul>
+  </ul>
+  <h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
+  <dl>
+   <dt id="biblio-coc">[COC]
+   <dd><a href="https://www.w3.org/policies/code-of-conduct/"><cite>W3C Code of Conduct</cite></a>. URL: <a href="https://www.w3.org/policies/code-of-conduct/">https://www.w3.org/policies/code-of-conduct/</a>
+   <dt id="biblio-collaborators-agreement">[COLLABORATORS-AGREEMENT]
+   <dd><a href="https://www.w3.org/invited-experts/agreement-2023/"><cite>Invited expert and collaborators agreement</cite></a>. URL: <a href="https://www.w3.org/invited-experts/agreement-2023/">https://www.w3.org/invited-experts/agreement-2023/</a>
+   <dt id="biblio-conflict-policy">[CONFLICT-POLICY]
+   <dd><a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/"><cite>Conflict of Interest Policy for the W3C Team</cite></a>. URL: <a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/">https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/</a>
+   <dt id="biblio-doc-license">[DOC-LICENSE]
+   <dd><a href="https://www.w3.org/copyright/document-license-2023/"><cite>W3C Document License</cite></a>. URL: <a href="https://www.w3.org/copyright/document-license-2023/">https://www.w3.org/copyright/document-license-2023/</a>
+   <dt id="biblio-patent-policy">[PATENT-POLICY]
+   <dd><a href="https://www.w3.org/policies/patent-policy/"><cite>The W3C Patent Policy</cite></a>. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
+   <dt id="biblio-patent-policy-2004">[PATENT-POLICY-2004]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy-20170801/"><cite>The W3C 2004 Patent Policy, Updated 2017</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy-20170801/">https://www.w3.org/Consortium/Patent-Policy-20170801/</a>
+   <dt id="biblio-patent-policy-2020">[PATENT-POLICY-2020]
+   <dd><a href="https://www.w3.org/policies/patent-policy/20200915/"><cite>The W3C 2020 Patent Policy</cite></a>. URL: <a href="https://www.w3.org/policies/patent-policy/20200915/">https://www.w3.org/policies/patent-policy/20200915/</a>
+   <dt id="biblio-pubrules">[PUBRULES]
+   <dd><a href="https://www.w3.org/pubrules/"><cite>Publication Rules</cite></a>. URL: <a href="https://www.w3.org/pubrules/">https://www.w3.org/pubrules/</a>
+   <dt id="biblio-rfc2119">[RFC2119]
+   <dd>S. Bradner. <a href="https://datatracker.ietf.org/doc/html/rfc2119"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. March 1997. Best Current Practice. URL: <a href="https://datatracker.ietf.org/doc/html/rfc2119">https://datatracker.ietf.org/doc/html/rfc2119</a>
+   <dt id="biblio-rfc3797">[RFC3797]
+   <dd>D. Eastlake 3rd. <a href="https://www.rfc-editor.org/rfc/rfc3797"><cite>Publicly Verifiable Nominations Committee (NomCom) Random Selection</cite></a>. June 2004. Informational. URL: <a href="https://www.rfc-editor.org/rfc/rfc3797">https://www.rfc-editor.org/rfc/rfc3797</a>
+   <dt id="biblio-w3c-patent-policy">[W3C-PATENT-POLICY]
+   <dd>Wendy Seltzer. <a href="https://www.w3.org/policies/patent-policy/"><cite>W3C Patent Policy</cite></a>. 15 September 2020. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
+  </dl>
+  <h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
+  <dl>
+   <dt id="biblio-ab-hp">[AB-HP]
+   <dd><a href="https://www.w3.org/2002/ab/"><cite>The Advisory Board home page</cite></a>. URL: <a href="https://www.w3.org/2002/ab/">https://www.w3.org/2002/ab/</a>
+   <dt id="biblio-ac-meeting">[AC-MEETING]
+   <dd><a href="https://www.w3.org/events/ac/"><cite>Advisory Committee meetings (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/events/ac/">https://www.w3.org/events/ac/</a>
+   <dt id="biblio-bg-cg">[BG-CG]
+   <dd><a href="https://www.w3.org/community/about/process/"><cite>Community and Business Group Process</cite></a>. URL: <a href="https://www.w3.org/community/about/process/">https://www.w3.org/community/about/process/</a>
+   <dt id="biblio-bylaws">[BYLAWS]
+   <dd><a href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a>. URL: <a href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf">https://www.w3.org/2024/09/25-w3c-bylaws.pdf</a>
+   <dt id="biblio-calendar">[CALENDAR]
+   <dd><a href="https://www.w3.org/events/"><cite>Calendar of all scheduled official W3C events</cite></a>. URL: <a href="https://www.w3.org/events/">https://www.w3.org/events/</a>
+   <dt id="biblio-chair">[CHAIR]
+   <dd><a href="https://www.w3.org/guide/chair/role"><cite>W3C Working/Interest Group Chair</cite></a>. URL: <a href="https://www.w3.org/guide/chair/role">https://www.w3.org/guide/chair/role</a>
+   <dt id="biblio-charter">[CHARTER]
+   <dd><a href="https://www.w3.org/guide/process/charter"><cite>How to Create a Working Group or Interest Group</cite></a>. URL: <a href="https://www.w3.org/guide/process/charter">https://www.w3.org/guide/process/charter</a>
+   <dt id="biblio-council-report-index">[COUNCIL-REPORT-INDEX]
+   <dd><a href="https://www.w3.org/about/council/"><cite>Council Report Index</cite></a>. URL: <a href="https://www.w3.org/about/council/">https://www.w3.org/about/council/</a>
+   <dt id="biblio-current-ac">[CURRENT-AC]
+   <dd><a href="https://www.w3.org/Member/ACList"><cite>Current Advisory Committee representatives (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/ACList">https://www.w3.org/Member/ACList</a>
+   <dt id="biblio-decision-appeal">[DECISION-APPEAL]
+   <dd><a href="https://www.w3.org/guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a>. URL: <a href="https://www.w3.org/guide/process/ac-appeal">https://www.w3.org/guide/process/ac-appeal</a>
+   <dt id="biblio-election-howto">[ELECTION-HOWTO]
+   <dd><a href="https://www.w3.org/guide/process/election"><cite>How to Organize an Advisory Board or TAG election</cite></a>. URL: <a href="https://www.w3.org/guide/process/election">https://www.w3.org/guide/process/election</a>
+   <dt id="biblio-fellows">[FELLOWS]
+   <dd><a href="https://www.w3.org/careers/fellows/"><cite>W3C Fellows Program</cite></a>. URL: <a href="https://www.w3.org/careers/fellows/">https://www.w3.org/careers/fellows/</a>
+   <dt id="biblio-group-mail">[GROUP-MAIL]
+   <dd><a href="https://www.w3.org/groups/"><cite>Group mailing lists</cite></a>. URL: <a href="https://www.w3.org/groups/">https://www.w3.org/groups/</a>
+   <dt id="biblio-guide">[GUIDE]
+   <dd><a href="https://www.w3.org/guide/"><cite>The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators</cite></a>. URL: <a href="https://www.w3.org/guide/">https://www.w3.org/guide/</a>
+   <dt id="biblio-intro">[INTRO]
+   <dd><a href="https://www.w3.org/Member/Intro"><cite>Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/Intro">https://www.w3.org/Member/Intro</a>
+   <dt id="biblio-join">[JOIN]
+   <dd><a href="https://www.w3.org/membership/join/"><cite>How to Join W3C</cite></a>. URL: <a href="https://www.w3.org/membership/join/">https://www.w3.org/membership/join/</a>
+   <dt id="biblio-liaison">[LIAISON]
+   <dd><a href="https://www.w3.org/liaisons/"><cite>W3C liaisons with other organizations</cite></a>. URL: <a href="https://www.w3.org/liaisons/">https://www.w3.org/liaisons/</a>
+   <dt id="biblio-member-agreement">[MEMBER-AGREEMENT]
+   <dd><a href="https://www.w3.org/membership/agreement/"><cite>W3C Membership Agreement</cite></a>. URL: <a href="https://www.w3.org/membership/agreement/">https://www.w3.org/membership/agreement/</a>
+   <dt id="biblio-member-hp">[MEMBER-HP]
+   <dd><a href="https://www.w3.org/Member/"><cite>Member website (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/">https://www.w3.org/Member/</a>
+   <dt id="biblio-member-list">[MEMBER-LIST]
+   <dd><a href="https://www.w3.org/membership/list/"><cite>The list of current W3C Members</cite></a>. URL: <a href="https://www.w3.org/membership/list/">https://www.w3.org/membership/list/</a>
+   <dt id="biblio-member-sub">[MEMBER-SUB]
+   <dd><a href="https://www.w3.org/submissions/guide/"><cite>Member submissions guidebook</cite></a>. URL: <a href="https://www.w3.org/submissions/guide/">https://www.w3.org/submissions/guide/</a>
+   <dt id="biblio-mission">[MISSION]
+   <dd><a href="https://www.w3.org/mission/"><cite>The W3C Mission statement</cite></a>. URL: <a href="https://www.w3.org/mission/">https://www.w3.org/mission/</a>
+   <dt id="biblio-obs-resc">[OBS-RESC]
+   <dd><a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded"><cite>Obsoleting and Rescinding W3C Specifications</cite></a>. URL: <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">https://www.w3.org/guide/process/obsolete-rescinded-supserseded</a>
+   <dt id="biblio-rec-tips">[REC-TIPS]
+   <dd><a href="https://www.w3.org/guide/standards-track/rec-tips"><cite>Tips for Getting to Recommendation Faster</cite></a>. URL: <a href="https://www.w3.org/guide/standards-track/rec-tips">https://www.w3.org/guide/standards-track/rec-tips</a>
+   <dt id="biblio-republishing">[REPUBLISHING]
+   <dd><a href="https://www.w3.org/guide/standards-track/republishing"><cite>In-place modification of W3C Technical Reports</cite></a>. URL: <a href="https://www.w3.org/guide/standards-track/republishing">https://www.w3.org/guide/standards-track/republishing</a>
+   <dt id="biblio-submission-list">[SUBMISSION-LIST]
+   <dd><a href="https://www.w3.org/submissions/"><cite>The list of acknowledged Member Submissions</cite></a>. URL: <a href="https://www.w3.org/submissions/">https://www.w3.org/submissions/</a>
+   <dt id="biblio-tag-hp">[TAG-HP]
+   <dd><a href="https://www.w3.org/2001/tag/"><cite>The TAG home page</cite></a>. URL: <a href="https://www.w3.org/2001/tag/">https://www.w3.org/2001/tag/</a>
+   <dt id="biblio-team-contact">[TEAM-CONTACT]
+   <dd><a href="https://www.w3.org/guide/teamcontact/role"><cite>Role of the Team Contact</cite></a>. URL: <a href="https://www.w3.org/guide/teamcontact/role">https://www.w3.org/guide/teamcontact/role</a>
+   <dt id="biblio-tr">[TR]
+   <dd><a href="https://www.w3.org/TR/"><cite>The W3C technical reports index</cite></a>. URL: <a href="https://www.w3.org/TR/">https://www.w3.org/TR/</a>
+   <dt id="biblio-transition">[TRANSITION]
+   <dd><a href="https://www.w3.org/guide/transitions/"><cite>Organize a Technical Report Transition</cite></a>. URL: <a href="https://www.w3.org/guide/transitions/">https://www.w3.org/guide/transitions/</a>
+   <dt id="biblio-translation">[TRANSLATION]
+   <dd><a href="https://www.w3.org/Consortium/Translation/"><cite>Translations of W3C technical reports</cite></a>. URL: <a href="https://www.w3.org/Consortium/Translation/">https://www.w3.org/Consortium/Translation/</a>
+   <dt id="biblio-w3c-ipr">[W3C-IPR]
+   <dd><a href="https://www.w3.org/policies/"><cite>W3C IPR Policies</cite></a>. URL: <a href="https://www.w3.org/policies/">https://www.w3.org/policies/</a>
+  </dl>
+<script>/* Boilerplate: script-dom-helper */
+"use strict";
+function query(sel) { return document.querySelector(sel); }
+
+function queryAll(sel) { return [...document.querySelectorAll(sel)]; }
+
+function iter(obj) {
+	if(!obj) return [];
+	var it = obj[Symbol.iterator];
+	if(it) return it;
+	return Object.entries(obj);
+}
+
+function mk(tagname, attrs, ...children) {
+	const el = document.createElement(tagname);
+	for(const [k,v] of iter(attrs)) {
+		if(k.slice(0,3) == "_on") {
+			const eventName = k.slice(3);
+			el.addEventListener(eventName, v);
+		} else if(k[0] == "_") {
+			// property, not attribute
+			el[k.slice(1)] = v;
+		} else {
+			if(v === false || v == null) {
+        continue;
+      } else if(v === true) {
+        el.setAttribute(k, "");
+        continue;
+      } else {
+  			el.setAttribute(k, v);
+      }
+		}
+	}
+	append(el, children);
+	return el;
+}
+
+/* Create shortcuts for every known HTML element */
+[
+  "a",
+  "abbr",
+  "acronym",
+  "address",
+  "applet",
+  "area",
+  "article",
+  "aside",
+  "audio",
+  "b",
+  "base",
+  "basefont",
+  "bdo",
+  "big",
+  "blockquote",
+  "body",
+  "br",
+  "button",
+  "canvas",
+  "caption",
+  "center",
+  "cite",
+  "code",
+  "col",
+  "colgroup",
+  "datalist",
+  "dd",
+  "del",
+  "details",
+  "dfn",
+  "dialog",
+  "div",
+  "dl",
+  "dt",
+  "em",
+  "embed",
+  "fieldset",
+  "figcaption",
+  "figure",
+  "font",
+  "footer",
+  "form",
+  "frame",
+  "frameset",
+  "head",
+  "header",
+  "h1",
+  "h2",
+  "h3",
+  "h4",
+  "h5",
+  "h6",
+  "hr",
+  "html",
+  "i",
+  "iframe",
+  "img",
+  "input",
+  "ins",
+  "kbd",
+  "label",
+  "legend",
+  "li",
+  "link",
+  "main",
+  "map",
+  "mark",
+  "meta",
+  "meter",
+  "nav",
+  "nobr",
+  "noscript",
+  "object",
+  "ol",
+  "optgroup",
+  "option",
+  "output",
+  "p",
+  "param",
+  "pre",
+  "progress",
+  "q",
+  "s",
+  "samp",
+  "script",
+  "section",
+  "select",
+  "small",
+  "source",
+  "span",
+  "strike",
+  "strong",
+  "style",
+  "sub",
+  "summary",
+  "sup",
+  "table",
+  "tbody",
+  "td",
+  "template",
+  "textarea",
+  "tfoot",
+  "th",
+  "thead",
+  "time",
+  "title",
+  "tr",
+  "u",
+  "ul",
+  "var",
+  "video",
+  "wbr",
+  "xmp",
+].forEach(tagname=>{
+	mk[tagname] = (...args) => mk(tagname, ...args);
+});
+
+function* nodesFromChildList(children) {
+	for(const child of children.flat(Infinity)) {
+		if(child instanceof Node) {
+			yield child;
+		} else {
+			yield new Text(child);
+		}
+	}
+}
+function append(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		if(el instanceof Node) el.appendChild(child);
+		else el.push(child);
+	}
+	return el;
+}
+
+function insertAfter(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		el.parentNode.insertBefore(child, el.nextSibling);
+	}
+	return el;
+}
+
+function clearContents(el) {
+	el.innerHTML = "";
+	return el;
+}
+
+function parseHTML(markup) {
+	if(markup.toLowerCase().trim().indexOf('<!doctype') === 0) {
+		const doc = document.implementation.createHTMLDocument("");
+		doc.documentElement.innerHTML = markup;
+		return doc;
+	} else {
+		const el = mk.template({});
+		el.innerHTML = markup;
+		return el.content;
+	}
+}</script>
+<script>/* Boilerplate: script-dfn-panel */
+"use strict";
+{
+let dfnPanelData = {
+"33fd2aef": {"dfnID":"33fd2aef","dfnText":"Exclusion Opportunity","external":true,"refSections":[{"refs":[{"id":"ref-for-exclusion-opportunity"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
+"74c78a1e": {"dfnID":"74c78a1e","dfnText":"Patent Advisory Group","external":true,"refSections":[{"refs":[{"id":"ref-for-patent-advisory-group"}],"title":"4.7. \nChartered Group Closure"}],"url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
+"EventsW": {"dfnID":"EventsW","dfnText":"Workshop","external":false,"refSections":[{"refs":[{"id":"ref-for-EventsW"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-EventsW\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-EventsW\u2461"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-EventsW\u2462"}],"title":"7.1. \nPublic Communication"}],"url":"#EventsW"},
+"FormalObjection": {"dfnID":"FormalObjection","dfnText":"Formal Objection","external":false,"refSections":[{"refs":[{"id":"ref-for-FormalObjection"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-FormalObjection\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-FormalObjection\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-FormalObjection\u2462"},{"id":"ref-for-FormalObjection\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-FormalObjection\u2464"}],"title":"5. \nDecisions"},{"refs":[{"id":"ref-for-FormalObjection\u2465"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-FormalObjection\u2466"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-FormalObjection\u2467"},{"id":"ref-for-FormalObjection\u2468"},{"id":"ref-for-FormalObjection\u2460\u24ea"},{"id":"ref-for-FormalObjection\u2460\u2460"},{"id":"ref-for-FormalObjection\u2460\u2461"},{"id":"ref-for-FormalObjection\u2460\u2462"},{"id":"ref-for-FormalObjection\u2460\u2463"},{"id":"ref-for-FormalObjection\u2460\u2464"},{"id":"ref-for-FormalObjection\u2460\u2465"},{"id":"ref-for-FormalObjection\u2460\u2466"},{"id":"ref-for-FormalObjection\u2460\u2467"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-FormalObjection\u2460\u2468"},{"id":"ref-for-FormalObjection\u2461\u24ea"},{"id":"ref-for-FormalObjection\u2461\u2460"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2461"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2462"},{"id":"ref-for-FormalObjection\u2461\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2464"},{"id":"ref-for-FormalObjection\u2461\u2465"},{"id":"ref-for-FormalObjection\u2461\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2468"},{"id":"ref-for-FormalObjection\u2462\u24ea"},{"id":"ref-for-FormalObjection\u2462\u2460"},{"id":"ref-for-FormalObjection\u2462\u2461"},{"id":"ref-for-FormalObjection\u2462\u2462"},{"id":"ref-for-FormalObjection\u2462\u2463"},{"id":"ref-for-FormalObjection\u2462\u2464"},{"id":"ref-for-FormalObjection\u2462\u2465"},{"id":"ref-for-FormalObjection\u2462\u2466"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2468"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u24ea"},{"id":"ref-for-FormalObjection\u2463\u2460"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2461"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2462"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2463"}],"title":"9. \nMember Submissions"}],"url":"#FormalObjection"},
+"GeneralChairs": {"dfnID":"GeneralChairs","dfnText":"Chair","external":false,"refSections":[{"refs":[{"id":"ref-for-GeneralChairs"}],"title":"3.1.1.2. \nConflict of Interest Policy"},{"refs":[{"id":"ref-for-GeneralChairs\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-GeneralChairs\u2461"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-GeneralChairs\u2462"},{"id":"ref-for-GeneralChairs\u2463"},{"id":"ref-for-GeneralChairs\u2464"},{"id":"ref-for-GeneralChairs\u2465"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-GeneralChairs\u2466"},{"id":"ref-for-GeneralChairs\u2467"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GeneralChairs\u2468"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u24ea"},{"id":"ref-for-GeneralChairs\u2460\u2460"},{"id":"ref-for-GeneralChairs\u2460\u2461"},{"id":"ref-for-GeneralChairs\u2460\u2462"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2464"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2465"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2466"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2467"},{"id":"ref-for-GeneralChairs\u2460\u2468"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u24ea"},{"id":"ref-for-GeneralChairs\u2461\u2460"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2461"},{"id":"ref-for-GeneralChairs\u2461\u2462"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2463"},{"id":"ref-for-GeneralChairs\u2461\u2464"}],"title":"5.2.3. \nDeciding by Vote"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2465"},{"id":"ref-for-GeneralChairs\u2461\u2466"}],"title":"5.4. \nReopening a Decision When Presented With New Information"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2467"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2468"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-GeneralChairs\u2462\u24ea"},{"id":"ref-for-GeneralChairs\u2462\u2460"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-GeneralChairs\u2462\u2461"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#GeneralChairs"},
+"GroupsIG": {"dfnID":"GroupsIG","dfnText":"Interest Groups","external":false,"refSections":[{"refs":[{"id":"ref-for-GroupsIG"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-GroupsIG"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-GroupsIG\u2460"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GroupsIG\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-GroupsIG\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-GroupsIG\u2463"},{"id":"ref-for-GroupsIG\u2464"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GroupsIG\u2465"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-GroupsIG\u2466"},{"id":"ref-for-GroupsIG\u2467"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GroupsIG\u2468"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-GroupsIG\u2460\u24ea"},{"id":"ref-for-GroupsIG\u2460\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsIG\u2460\u2461"}],"title":"6.4.1. \nGroup Notes"}],"url":"#GroupsIG"},
+"GroupsWG": {"dfnID":"GroupsWG","dfnText":"Working Groups","external":false,"refSections":[{"refs":[{"id":"ref-for-GroupsWG"},{"id":"ref-for-GroupsWG\u2460"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-GroupsWG\u2461"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-GroupsWG\u2462"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-GroupsWG"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-GroupsWG\u2463"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GroupsWG\u2464"},{"id":"ref-for-GroupsWG\u2465"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-GroupsWG\u2466"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-GroupsWG\u2467"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-GroupsWG\u2468"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u24ea"},{"id":"ref-for-GroupsWG\u2460\u2460"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2461"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2462"},{"id":"ref-for-GroupsWG\u2460\u2463"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2464"}],"title":"6. \nW3C Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2465"},{"id":"ref-for-GroupsWG\u2460\u2466"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2467"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2468"},{"id":"ref-for-GroupsWG\u2461\u24ea"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2460"},{"id":"ref-for-GroupsWG\u2461\u2461"},{"id":"ref-for-GroupsWG\u2461\u2462"},{"id":"ref-for-GroupsWG\u2461\u2463"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2464"},{"id":"ref-for-GroupsWG\u2461\u2465"},{"id":"ref-for-GroupsWG\u2461\u2466"},{"id":"ref-for-GroupsWG\u2461\u2467"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2468"},{"id":"ref-for-GroupsWG\u2462\u24ea"},{"id":"ref-for-GroupsWG\u2462\u2460"},{"id":"ref-for-GroupsWG\u2462\u2461"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2462\u2462"},{"id":"ref-for-GroupsWG\u2462\u2463"},{"id":"ref-for-GroupsWG\u2462\u2464"},{"id":"ref-for-GroupsWG\u2462\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2462\u2466"},{"id":"ref-for-GroupsWG\u2462\u2467"},{"id":"ref-for-GroupsWG\u2462\u2468"},{"id":"ref-for-GroupsWG\u2463\u24ea"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2460"},{"id":"ref-for-GroupsWG\u2463\u2461"},{"id":"ref-for-GroupsWG\u2463\u2462"},{"id":"ref-for-GroupsWG\u2463\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2464"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2465"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2466"},{"id":"ref-for-GroupsWG\u2463\u2467"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2468"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u24ea"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2460"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2461"},{"id":"ref-for-GroupsWG\u2464\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2463"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2464"},{"id":"ref-for-GroupsWG\u2464\u2465"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2466"},{"id":"ref-for-GroupsWG\u2464\u2467"},{"id":"ref-for-GroupsWG\u2464\u2468"},{"id":"ref-for-GroupsWG\u2465\u24ea"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2460"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2461"}],"title":"6.3.12. \nRetiring Recommendation Track Documents"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2462"},{"id":"ref-for-GroupsWG\u2465\u2463"},{"id":"ref-for-GroupsWG\u2465\u2464"},{"id":"ref-for-GroupsWG\u2465\u2465"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2466"},{"id":"ref-for-GroupsWG\u2465\u2467"},{"id":"ref-for-GroupsWG\u2465\u2468"},{"id":"ref-for-GroupsWG\u2466\u24ea"},{"id":"ref-for-GroupsWG\u2466\u2460"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2461"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2462"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2463"},{"id":"ref-for-GroupsWG\u2466\u2464"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2465"}],"title":"10. \nProcess Evolution"}],"url":"#GroupsWG"},
+"Member-only": {"dfnID":"Member-only","dfnText":"Member-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Member-only"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-Member-only"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-Member-only"},{"id":"ref-for-Member-only"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-Member-only"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-Member-only\u2460"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-Member-only\u2461"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Member-only\u2462"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-Member-only\u2463"},{"id":"ref-for-Member-only\u2464"},{"id":"ref-for-Member-only\u2465"},{"id":"ref-for-Member-only\u2466"},{"id":"ref-for-Member-only\u2467"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Member-only\u2468"},{"id":"ref-for-Member-only\u2460\u24ea"},{"id":"ref-for-Member-only\u2460\u2460"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Member-only"},
+"MemberSubmission": {"dfnID":"MemberSubmission","dfnText":"Member Submission","external":false,"refSections":[{"refs":[{"id":"ref-for-MemberSubmission"},{"id":"ref-for-MemberSubmission\u2460"},{"id":"ref-for-MemberSubmission\u2461"},{"id":"ref-for-MemberSubmission\u2462"}],"title":"9. \nMember Submissions"}],"url":"#MemberSubmission"},
+"RecsCR": {"dfnID":"RecsCR","dfnText":"Candidate Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsCR"},{"id":"ref-for-RecsCR\u2460"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-RecsCR\u2461"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-RecsCR\u2462"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsCR\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-RecsCR\u2464"},{"id":"ref-for-RecsCR\u2465"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2466"},{"id":"ref-for-RecsCR\u2467"},{"id":"ref-for-RecsCR\u2468"},{"id":"ref-for-RecsCR\u2460\u24ea"},{"id":"ref-for-RecsCR\u2460\u2460"},{"id":"ref-for-RecsCR\u2460\u2461"},{"id":"ref-for-RecsCR\u2460\u2462"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2463"},{"id":"ref-for-RecsCR\u2460\u2464"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2467"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2468"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-RecsCR\u2461\u24ea"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-RecsCR\u2461\u2460"}],"title":"6.3.12.2. \nRescinding a Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2461\u2461"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsCR"},
+"RecsObs": {"dfnID":"RecsObs","dfnText":"Obsolete Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsObs"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsObs\u2460"},{"id":"ref-for-RecsObs\u2461"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsObs\u2462"},{"id":"ref-for-RecsObs\u2463"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RecsObs\u2464"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsObs"},
+"RecsPR": {"dfnID":"RecsPR","dfnText":"Proposed Recommendation","external":false,"refSections":[],"url":"#RecsPR"},
+"RecsSup": {"dfnID":"RecsSup","dfnText":"Superseded Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsSup"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsSup\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsSup"},
+"RecsW3C": {"dfnID":"RecsW3C","dfnText":"W3C Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsW3C"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-RecsW3C"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-RecsW3C\u2460"},{"id":"ref-for-RecsW3C\u2461"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-RecsW3C\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-RecsW3C\u2463"},{"id":"ref-for-RecsW3C\u2464"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-RecsW3C\u2465"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsW3C\u2466"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-RecsW3C\u2467"},{"id":"ref-for-RecsW3C"},{"id":"ref-for-RecsW3C\u2468"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2460\u24ea"},{"id":"ref-for-RecsW3C\u2460\u2460"},{"id":"ref-for-RecsW3C\u2460\u2461"},{"id":"ref-for-RecsW3C\u2460\u2462"},{"id":"ref-for-RecsW3C\u2460\u2463"},{"id":"ref-for-RecsW3C\u2460\u2464"},{"id":"ref-for-RecsW3C\u2460\u2465"},{"id":"ref-for-RecsW3C\u2460\u2466"},{"id":"ref-for-RecsW3C\u2460\u2467"},{"id":"ref-for-RecsW3C\u2460\u2468"},{"id":"ref-for-RecsW3C\u2461\u24ea"},{"id":"ref-for-RecsW3C\u2461\u2460"},{"id":"ref-for-RecsW3C\u2461\u2461"},{"id":"ref-for-RecsW3C\u2461\u2462"},{"id":"ref-for-RecsW3C\u2461\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2464"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2467"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2468"},{"id":"ref-for-RecsW3C\u2462\u24ea"},{"id":"ref-for-RecsW3C\u2462\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2461"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2462"},{"id":"ref-for-RecsW3C\u2462\u2463"},{"id":"ref-for-RecsW3C\u2462\u2464"},{"id":"ref-for-RecsW3C\u2462\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2466"},{"id":"ref-for-RecsW3C\u2462\u2467"}],"title":"6.3.9.4. \nNext Steps from W3C Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2468"},{"id":"ref-for-RecsW3C\u2463\u24ea"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-RecsW3C\u2463\u2460"},{"id":"ref-for-RecsW3C\u2463\u2461"},{"id":"ref-for-RecsW3C\u2463\u2462"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-RecsW3C\u2463\u2463"},{"id":"ref-for-RecsW3C\u2463\u2464"},{"id":"ref-for-RecsW3C\u2463\u2465"},{"id":"ref-for-RecsW3C\u2463\u2466"},{"id":"ref-for-RecsW3C\u2463\u2467"},{"id":"ref-for-RecsW3C\u2463\u2468"},{"id":"ref-for-RecsW3C\u2464\u24ea"},{"id":"ref-for-RecsW3C\u2464\u2460"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2461"},{"id":"ref-for-RecsW3C\u2464\u2462"},{"id":"ref-for-RecsW3C\u2464\u2463"},{"id":"ref-for-RecsW3C\u2464\u2464"},{"id":"ref-for-RecsW3C\u2464\u2465"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2466"}],"title":"6.3.12.2. \nRescinding a Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2467"},{"id":"ref-for-RecsW3C\u2464\u2468"},{"id":"ref-for-RecsW3C\u2465\u24ea"},{"id":"ref-for-RecsW3C\u2465\u2460"},{"id":"ref-for-RecsW3C\u2465\u2461"},{"id":"ref-for-RecsW3C\u2465\u2462"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2465\u2463"},{"id":"ref-for-RecsW3C\u2465\u2464"},{"id":"ref-for-RecsW3C\u2465\u2465"},{"id":"ref-for-RecsW3C\u2465\u2466"},{"id":"ref-for-RecsW3C\u2465\u2467"},{"id":"ref-for-RecsW3C\u2465\u2468"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u24ea"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2460"},{"id":"ref-for-RecsW3C\u2466\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2462"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2463"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#RecsW3C"},
+"RecsWD": {"dfnID":"RecsWD","dfnText":"Working Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsWD"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-RecsWD\u2460"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsWD\u2461"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsWD\u2462"},{"id":"ref-for-RecsWD\u2463"},{"id":"ref-for-RecsWD\u2464"},{"id":"ref-for-RecsWD\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsWD\u2466"},{"id":"ref-for-RecsWD\u2467"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-RecsWD\u2468"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-RecsWD\u2460\u24ea"},{"id":"ref-for-RecsWD\u2460\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-RecsWD\u2460\u2461"},{"id":"ref-for-RecsWD\u2460\u2462"},{"id":"ref-for-RecsWD\u2460\u2463"}],"title":"6.6. \nSwitching Tracks"}],"url":"#RecsWD"},
+"RescindedRec": {"dfnID":"RescindedRec","dfnText":"Rescinded Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RescindedRec"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RescindedRec\u2460"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RescindedRec\u2461"},{"id":"ref-for-RescindedRec\u2462"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RescindedRec\u2463"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RescindedRec"},
+"Team-only": {"dfnID":"Team-only","dfnText":"Team-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Team-only"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-Team-only"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Team-only\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Team-only\u2461"},{"id":"ref-for-Team-only\u2462"},{"id":"ref-for-Team-only\u2463"},{"id":"ref-for-Team-only\u2464"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Team-only"},
+"TeamContact": {"dfnID":"TeamContact","dfnText":"Staff Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-TeamContact"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-TeamContact\u2460"},{"id":"ref-for-TeamContact\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2462"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2463"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2464"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2465"},{"id":"ref-for-TeamContact\u2466"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-TeamContact\u2467"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-TeamContact\u2468"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-TeamContact\u2460\u24ea"}],"title":"5.5. \nRegistering Formal Objections"}],"url":"#TeamContact"},
+"TeamSubmission": {"dfnID":"TeamSubmission","dfnText":"Team Submissions","external":false,"refSections":[],"url":"#TeamSubmission"},
+"WGNote": {"dfnID":"WGNote","dfnText":"Group Note","external":false,"refSections":[{"refs":[{"id":"ref-for-WGNote"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-WGNote"},{"id":"ref-for-WGNote\u2460"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-WGNote\u2461"},{"id":"ref-for-WGNote\u2462"},{"id":"ref-for-WGNote\u2463"},{"id":"ref-for-WGNote\u2464"},{"id":"ref-for-WGNote\u2465"},{"id":"ref-for-WGNote\u2466"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-WGNote\u2467"},{"id":"ref-for-WGNote\u2468"},{"id":"ref-for-WGNote\u2460\u24ea"},{"id":"ref-for-WGNote\u2460\u2460"},{"id":"ref-for-WGNote\u2460\u2461"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-WGNote\u2460\u2462"},{"id":"ref-for-WGNote\u2460\u2463"},{"id":"ref-for-WGNote\u2460\u2464"},{"id":"ref-for-WGNote\u2460\u2465"},{"id":"ref-for-WGNote\u2460\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#WGNote"},
+"acknowledged": {"dfnID":"acknowledged","dfnText":"acknowledged","external":false,"refSections":[{"refs":[{"id":"ref-for-acknowledged"},{"id":"ref-for-acknowledged\u2460"}],"title":"9. \nMember Submissions"}],"url":"#acknowledged"},
+"adequate-implementation": {"dfnID":"adequate-implementation","dfnText":"adequate implementation experience","external":false,"refSections":[{"refs":[{"id":"ref-for-adequate-implementation"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-adequate-implementation\u2460"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-adequate-implementation\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-adequate-implementation\u2462"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#adequate-implementation"},
+"adopted-draft": {"dfnID":"adopted-draft","dfnText":"Adopted Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-adopted-draft"}],"title":"4.3. \nContent of a Charter"}],"url":"#adopted-draft"},
+"advisory-board": {"dfnID":"advisory-board","dfnText":"Advisory Board","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-board"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-advisory-board\u2460"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-advisory-board\u2461"},{"id":"ref-for-advisory-board\u2462"},{"id":"ref-for-advisory-board\u2463"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2464"},{"id":"ref-for-advisory-board\u2465"},{"id":"ref-for-advisory-board\u2466"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2467"}],"title":"3.3.1.3. \nCommunications of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2468"},{"id":"ref-for-advisory-board\u2460\u24ea"},{"id":"ref-for-advisory-board\u2460\u2460"}],"title":"3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2461"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2462"},{"id":"ref-for-advisory-board\u2460\u2463"},{"id":"ref-for-advisory-board\u2460\u2464"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2465"},{"id":"ref-for-advisory-board\u2460\u2466"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2467"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2468"}],"title":"3.3.3.5. \nVerifiable Random Selection Procedure"},{"refs":[{"id":"ref-for-advisory-board\u2461\u24ea"},{"id":"ref-for-advisory-board\u2461\u2460"},{"id":"ref-for-advisory-board\u2461\u2461"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2462"},{"id":"ref-for-advisory-board\u2461\u2463"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2464"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2465"},{"id":"ref-for-advisory-board\u2461\u2466"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2467"},{"id":"ref-for-advisory-board\u2461\u2468"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-advisory-board\u2462\u24ea"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2460"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2461"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2462"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2463"},{"id":"ref-for-advisory-board\u2462\u2464"},{"id":"ref-for-advisory-board\u2462\u2465"},{"id":"ref-for-advisory-board\u2462\u2466"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-board"},
+"advisory-committee": {"dfnID":"advisory-committee","dfnText":"Advisory Committee","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-advisory-committee\u2460"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee\u2461"},{"id":"ref-for-advisory-committee\u2462"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-advisory-committee\u2463"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-advisory-committee\u2464"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-advisory-committee\u2465"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-committee\u2466"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-advisory-committee\u2467"},{"id":"ref-for-advisory-committee\u2468"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u24ea"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2460"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2461"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2462"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2464"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2465"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2466"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2467"},{"id":"ref-for-advisory-committee\u2460\u2468"},{"id":"ref-for-advisory-committee\u2461\u24ea"},{"id":"ref-for-advisory-committee\u2461\u2460"},{"id":"ref-for-advisory-committee\u2461\u2461"},{"id":"ref-for-advisory-committee\u2461\u2462"},{"id":"ref-for-advisory-committee\u2461\u2463"},{"id":"ref-for-advisory-committee\u2461\u2464"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-advisory-committee\u2461\u2465"},{"id":"ref-for-advisory-committee\u2461\u2466"}],"title":"5.8. \nAdvisory Committee Votes"},{"refs":[{"id":"ref-for-advisory-committee\u2461\u2467"},{"id":"ref-for-advisory-committee\u2461\u2468"},{"id":"ref-for-advisory-committee\u2462\u24ea"},{"id":"ref-for-advisory-committee\u2462\u2460"},{"id":"ref-for-advisory-committee\u2462\u2461"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2462"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2463"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2464"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2466"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2467"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2468"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee\u2463\u24ea"},{"id":"ref-for-advisory-committee\u2463\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee\u2463\u2461"},{"id":"ref-for-advisory-committee\u2463\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-committee"},
+"advisory-committee-appeal": {"dfnID":"advisory-committee-appeal","dfnText":"Advisory Committee Appeal","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-appeal"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2461"}],"title":"5.8. \nAdvisory Committee Votes"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2462"},{"id":"ref-for-advisory-committee-appeal\u2463"},{"id":"ref-for-advisory-committee-appeal\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2468"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u24ea"},{"id":"ref-for-advisory-committee-appeal\u2460\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u2461"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-committee-appeal"},
+"advisory-committee-representative": {"dfnID":"advisory-committee-representative","dfnText":"representative","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-representative"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460"}],"title":"3.1.1.3. \nIndividuals Representing a Member Organization"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461"},{"id":"ref-for-advisory-committee-representative\u2462"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2463"},{"id":"ref-for-advisory-committee-representative\u2464"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2465"},{"id":"ref-for-advisory-committee-representative\u2466"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2467"},{"id":"ref-for-advisory-committee-representative\u2468"},{"id":"ref-for-advisory-committee-representative\u2460\u24ea"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2460"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2461"}],"title":"3.4.3.2. \nMember Representative in an Interest Group"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2462"},{"id":"ref-for-advisory-committee-representative\u2460\u2463"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2464"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2465"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2466"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2468"},{"id":"ref-for-advisory-committee-representative\u2461\u24ea"},{"id":"ref-for-advisory-committee-representative\u2461\u2460"},{"id":"ref-for-advisory-committee-representative\u2461\u2461"},{"id":"ref-for-advisory-committee-representative\u2461\u2462"},{"id":"ref-for-advisory-committee-representative\u2461\u2463"},{"id":"ref-for-advisory-committee-representative\u2461\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2468"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u24ea"},{"id":"ref-for-advisory-committee-representative\u2462\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2461"}],"title":"7.3. \nChanging Confidentiality Level"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2462"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2463"},{"id":"ref-for-advisory-committee-representative\u2462\u2464"},{"id":"ref-for-advisory-committee-representative\u2462\u2465"}],"title":"9. \nMember Submissions"}],"url":"#advisory-committee-representative"},
+"advisory-committee-review": {"dfnID":"advisory-committee-review","dfnText":"Advisory Committee review","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-review"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460"},{"id":"ref-for-advisory-committee-review\u2461"},{"id":"ref-for-advisory-committee-review\u2462"},{"id":"ref-for-advisory-committee-review\u2463"},{"id":"ref-for-advisory-committee-review\u2464"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-review\u2465"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-advisory-committee-review\u2466"},{"id":"ref-for-advisory-committee-review\u2467"},{"id":"ref-for-advisory-committee-review\u2468"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u24ea"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2460"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2461"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2462"},{"id":"ref-for-advisory-committee-review\u2460\u2463"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2464"},{"id":"ref-for-advisory-committee-review\u2460\u2465"},{"id":"ref-for-advisory-committee-review\u2460\u2466"},{"id":"ref-for-advisory-committee-review\u2460\u2467"},{"id":"ref-for-advisory-committee-review\u2460\u2468"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u24ea"},{"id":"ref-for-advisory-committee-review\u2461\u2460"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2462"},{"id":"ref-for-advisory-committee-review\u2461\u2463"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2465"},{"id":"ref-for-advisory-committee-review\u2461\u2466"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2467"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2468"},{"id":"ref-for-advisory-committee-review\u2462\u24ea"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2461"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2462"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2463"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2464"}],"title":"10. \nProcess Evolution"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2465"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#advisory-committee-review"},
+"affirm": {"dfnID":"affirm","dfnText":"affirm","external":false,"refSections":[{"refs":[{"id":"ref-for-affirm"},{"id":"ref-for-affirm\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-affirm\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-affirm\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"#affirm"},
+"allow-new-features": {"dfnID":"allow-new-features","dfnText":"allow new features","external":false,"refSections":[{"refs":[{"id":"ref-for-allow-new-features"},{"id":"ref-for-allow-new-features\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-allow-new-features\u2461"},{"id":"ref-for-allow-new-features\u2462"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-allow-new-features\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#allow-new-features"},
+"alternate-ac-representative": {"dfnID":"alternate-ac-representative","dfnText":"alternate","external":false,"refSections":[],"url":"#alternate-ac-representative"},
+"appeal-vote": {"dfnID":"appeal-vote","dfnText":"appeal vote","external":false,"refSections":[{"refs":[{"id":"ref-for-appeal-vote"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-appeal-vote\u2460"}],"title":"5.8. \nAdvisory Committee Votes"}],"url":"#appeal-vote"},
+"at-risk": {"dfnID":"at-risk","dfnText":"at risk","external":false,"refSections":[{"refs":[{"id":"ref-for-at-risk"},{"id":"ref-for-at-risk\u2460"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-at-risk\u2461"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-at-risk\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-at-risk\u2463"}],"title":"6.3.9.3. \nResolution of Review"}],"url":"#at-risk"},
+"bod": {"dfnID":"bod","dfnText":"W3C Board of Directors","external":false,"refSections":[{"refs":[{"id":"ref-for-bod"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-bod\u2460"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-bod\u2461"},{"id":"ref-for-bod\u2462"},{"id":"ref-for-bod\u2463"},{"id":"ref-for-bod\u2464"},{"id":"ref-for-bod\u2465"}],"title":"3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"},{"refs":[{"id":"ref-for-bod\u2466"},{"id":"ref-for-bod\u2467"}],"title":"8. \nLiaisons"}],"url":"#bod"},
+"candidate-addition": {"dfnID":"candidate-addition","dfnText":"candidate addition","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-addition"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-addition\u2460"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"}],"url":"#candidate-addition"},
+"candidate-amendment": {"dfnID":"candidate-amendment","dfnText":"candidate amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-amendment"},{"id":"ref-for-candidate-amendment\u2460"},{"id":"ref-for-candidate-amendment\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-amendment\u2462"},{"id":"ref-for-candidate-amendment\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-candidate-amendment\u2464"},{"id":"ref-for-candidate-amendment\u2465"},{"id":"ref-for-candidate-amendment\u2466"},{"id":"ref-for-candidate-amendment\u2467"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-candidate-amendment\u2468"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#candidate-amendment"},
+"candidate-correction": {"dfnID":"candidate-correction","dfnText":"candidate correction","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-correction"},{"id":"ref-for-candidate-correction\u2460"},{"id":"ref-for-candidate-correction\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-correction\u2462"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-candidate-correction\u2463"},{"id":"ref-for-candidate-correction\u2464"},{"id":"ref-for-candidate-correction\u2465"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"}],"url":"#candidate-correction"},
+"candidate-recommendation-draft": {"dfnID":"candidate-recommendation-draft","dfnText":"Candidate Recommendation Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-draft"},{"id":"ref-for-candidate-recommendation-draft\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2461"},{"id":"ref-for-candidate-recommendation-draft\u2462"},{"id":"ref-for-candidate-recommendation-draft\u2463"},{"id":"ref-for-candidate-recommendation-draft\u2464"},{"id":"ref-for-candidate-recommendation-draft\u2465"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2466"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2467"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#candidate-recommendation-draft"},
+"candidate-recommendation-review-period": {"dfnID":"candidate-recommendation-review-period","dfnText":"Candidate Recommendation review period","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-review-period"},{"id":"ref-for-candidate-recommendation-review-period\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"}],"url":"#candidate-recommendation-review-period"},
+"candidate-recommendation-snapshot": {"dfnID":"candidate-recommendation-snapshot","dfnText":"Candidate Recommendation Snapshot","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-snapshot"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460"},{"id":"ref-for-candidate-recommendation-snapshot\u2461"},{"id":"ref-for-candidate-recommendation-snapshot\u2462"},{"id":"ref-for-candidate-recommendation-snapshot\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2464"},{"id":"ref-for-candidate-recommendation-snapshot\u2465"},{"id":"ref-for-candidate-recommendation-snapshot\u2466"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2467"},{"id":"ref-for-candidate-recommendation-snapshot\u2468"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u24ea"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2460"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2461"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2462"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2463"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2464"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2465"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2466"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2467"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2468"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#candidate-recommendation-snapshot"},
+"candidate-registry": {"dfnID":"candidate-registry","dfnText":"Candidate Registry","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-registry"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#candidate-registry"},
+"candidate-registry-draft": {"dfnID":"candidate-registry-draft","dfnText":"Candidate Registry Draft","external":false,"refSections":[],"url":"#candidate-registry-draft"},
+"candidate-registry-snapshot": {"dfnID":"candidate-registry-snapshot","dfnText":"Candidate Registry Snapshot","external":false,"refSections":[],"url":"#candidate-registry-snapshot"},
+"ceo": {"dfnID":"ceo","dfnText":"CEO","external":false,"refSections":[{"refs":[{"id":"ref-for-ceo"}],"title":"2.1.2.1. \nMembership Associations"},{"refs":[{"id":"ref-for-ceo\u2460"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-ceo\u2461"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-ceo\u2462"}],"title":"3.1.1.3. \nIndividuals Representing a Member Organization"},{"refs":[{"id":"ref-for-ceo\u2463"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-ceo\u2464"},{"id":"ref-for-ceo\u2465"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-ceo\u2466"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-ceo\u2467"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-ceo\u2468"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#ceo"},
+"chair-decisions": {"dfnID":"chair-decisions","dfnText":"chair decisions","external":false,"refSections":[],"url":"#chair-decisions"},
+"charter": {"dfnID":"charter","dfnText":"charter","external":false,"refSections":[{"refs":[{"id":"ref-for-charter"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-charter\u2460"},{"id":"ref-for-charter\u2461"},{"id":"ref-for-charter\u2462"},{"id":"ref-for-charter\u2463"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-charter\u2464"},{"id":"ref-for-charter\u2465"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter\u2466"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-charter\u2467"},{"id":"ref-for-charter\u2468"},{"id":"ref-for-charter\u2460\u24ea"},{"id":"ref-for-charter\u2460\u2460"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-charter\u2460\u2461"},{"id":"ref-for-charter\u2460\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-charter\u2460\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-charter\u2460\u2464"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-charter\u2460\u2465"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-charter\u2460\u2466"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-charter\u2460\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"}],"url":"#charter"},
+"charter-draft": {"dfnID":"charter-draft","dfnText":"charter draft","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-draft"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-draft\u2460"},{"id":"ref-for-charter-draft\u2461"},{"id":"ref-for-charter-draft\u2462"},{"id":"ref-for-charter-draft\u2463"}],"title":"4.2. \nCharter Refinement"}],"url":"#charter-draft"},
+"charter-refinement": {"dfnID":"charter-refinement","dfnText":"charter refinement","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-refinement"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-charter-refinement\u2460"},{"id":"ref-for-charter-refinement\u2461"},{"id":"ref-for-charter-refinement\u2462"},{"id":"ref-for-charter-refinement\u2463"},{"id":"ref-for-charter-refinement\u2464"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-refinement\u2465"},{"id":"ref-for-charter-refinement\u2466"},{"id":"ref-for-charter-refinement\u2467"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-charter-refinement\u2468"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-charter-refinement\u2460\u24ea"},{"id":"ref-for-charter-refinement\u2460\u2460"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-charter-refinement\u2460\u2461"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#charter-refinement"},
+"charter-review-notice": {"dfnID":"charter-review-notice","dfnText":"charter review notice","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-review-notice"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-review-notice\u2460"}],"title":"4.2. \nCharter Refinement"}],"url":"#charter-review-notice"},
+"chartered-group": {"dfnID":"chartered-group","dfnText":"chartered groups","external":false,"refSections":[{"refs":[{"id":"ref-for-chartered-group"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-chartered-group\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-chartered-group\u2461"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-chartered-group\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-chartered-group\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-chartered-group\u2464"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-chartered-group\u2465"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#chartered-group"},
+"chartering-facilitator": {"dfnID":"chartering-facilitator","dfnText":"Chartering Facilitator","external":false,"refSections":[{"refs":[{"id":"ref-for-chartering-facilitator"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-chartering-facilitator\u2460"},{"id":"ref-for-chartering-facilitator\u2461"},{"id":"ref-for-chartering-facilitator\u2462"}],"title":"4.2. \nCharter Refinement"}],"url":"#chartering-facilitator"},
+"convened": {"dfnID":"convened","dfnText":"convened","external":false,"refSections":[{"refs":[{"id":"ref-for-convened"},{"id":"ref-for-convened\u2460"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-convened\u2461"},{"id":"ref-for-convened\u2462"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#convened"},
+"council-report": {"dfnID":"council-report","dfnText":"Council Report","external":false,"refSections":[{"refs":[{"id":"ref-for-council-report"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-council-report\u2460"},{"id":"ref-for-council-report\u2461"},{"id":"ref-for-council-report\u2462"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-council-report\u2463"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-council-report\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-council-report\u2465"}],"title":"9. \nMember Submissions"}],"url":"#council-report"},
+"council-staff-contact": {"dfnID":"council-staff-contact","dfnText":"Council Staff Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-council-staff-contact"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-council-staff-contact\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#council-staff-contact"},
+"custodian": {"dfnID":"custodian","dfnText":"custodian","external":false,"refSections":[{"refs":[{"id":"ref-for-custodian"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-custodian\u2460"},{"id":"ref-for-custodian\u2461"},{"id":"ref-for-custodian\u2462"},{"id":"ref-for-custodian\u2463"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-custodian\u2464"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-custodian\u2465"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#custodian"},
+"def-Consensus": {"dfnID":"def-Consensus","dfnText":"Consensus","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Consensus"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-def-Consensus\u2460"},{"id":"ref-for-def-Consensus\u2461"},{"id":"ref-for-def-Consensus\u2462"},{"id":"ref-for-def-Consensus\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-def-Consensus\u2464"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-def-Consensus\u2465"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-def-Consensus\u2466"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-def-Consensus\u2467"},{"id":"ref-for-def-Consensus\u2468"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u24ea"},{"id":"ref-for-def-Consensus\u2460\u2460"},{"id":"ref-for-def-Consensus\u2460\u2461"},{"id":"ref-for-def-Consensus\u2460\u2462"},{"id":"ref-for-def-Consensus\u2460\u2463"},{"id":"ref-for-def-Consensus\u2460\u2464"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2465"}],"title":"6. \nW3C Technical Reports"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2466"},{"id":"ref-for-def-Consensus\u2460\u2467"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2468"},{"id":"ref-for-def-Consensus\u2461\u24ea"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-def-Consensus\u2461\u2460"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-def-Consensus\u2461\u2461"}],"title":"10. \nProcess Evolution"}],"url":"#def-Consensus"},
+"def-Dissent": {"dfnID":"def-Dissent","dfnText":"Dissent","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Dissent"},{"id":"ref-for-def-Dissent\u2460"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-def-Dissent\u2461"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-def-Dissent\u2462"},{"id":"ref-for-def-Dissent\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-Dissent\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-def-Dissent\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#def-Dissent"},
+"def-Unanimity": {"dfnID":"def-Unanimity","dfnText":"Unanimity","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Unanimity"}],"title":"5.2.1. \nConsensus"}],"url":"#def-Unanimity"},
+"def-W3CChair": {"dfnID":"def-W3CChair","dfnText":"W3C Chair","external":false,"refSections":[],"url":"#def-W3CChair"},
+"def-w3c-decision": {"dfnID":"def-w3c-decision","dfnText":"W3C decision","external":false,"refSections":[{"refs":[{"id":"ref-for-def-w3c-decision"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-def-w3c-decision\u2461"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-def-w3c-decision\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-def-w3c-decision\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-def-w3c-decision\u2464"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-def-w3c-decision\u2465"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-def-w3c-decision\u2466"},{"id":"ref-for-def-w3c-decision\u2467"},{"id":"ref-for-def-w3c-decision\u2468"},{"id":"ref-for-def-w3c-decision\u2460\u24ea"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2460"},{"id":"ref-for-def-w3c-decision\u2460\u2461"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2462"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2464"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2465"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2466"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#def-w3c-decision"},
+"dfn-charter-extension": {"dfnID":"dfn-charter-extension","dfnText":"extensions","external":false,"refSections":[{"refs":[{"id":"ref-for-dfn-charter-extension"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"}],"url":"#dfn-charter-extension"},
+"dfn-wide-review": {"dfnID":"dfn-wide-review","dfnText":"wide review","external":false,"refSections":[{"refs":[{"id":"ref-for-dfn-wide-review"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-dfn-wide-review\u2461"},{"id":"ref-for-dfn-wide-review\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-dfn-wide-review\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-dfn-wide-review\u2464"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2466"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2467"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-dfn-wide-review\u2468"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460\u24ea"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#dfn-wide-review"},
+"discontinuedREC": {"dfnID":"discontinuedREC","dfnText":"Discontinued Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-discontinuedREC"},{"id":"ref-for-discontinuedREC\u2460"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"}],"url":"#discontinuedREC"},
+"dismissed": {"dfnID":"dismissed","dfnText":"dismissed","external":false,"refSections":[{"refs":[{"id":"ref-for-dismissed"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-dismissed\u2460"},{"id":"ref-for-dismissed\u2461"},{"id":"ref-for-dismissed\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-dismissed\u2463"},{"id":"ref-for-dismissed\u2464"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-dismissed\u2465"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#dismissed"},
+"distributed-meeting": {"dfnID":"distributed-meeting","dfnText":"distributed meeting","external":false,"refSections":[{"refs":[{"id":"ref-for-distributed-meeting"}],"title":"5.2.1. \nConsensus"}],"url":"#distributed-meeting"},
+"edited-recommendation": {"dfnID":"edited-recommendation","dfnText":"Edited Recommendation","external":false,"refSections":[],"url":"#edited-recommendation"},
+"editorial-change": {"dfnID":"editorial-change","dfnText":"editorial changes","external":false,"refSections":[{"refs":[{"id":"ref-for-editorial-change"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-editorial-change\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2462"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2463"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-editorial-change\u2464"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-editorial-change\u2465"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-editorial-change\u2466"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-editorial-change\u2467"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-editorial-change\u2468"},{"id":"ref-for-editorial-change\u2460\u24ea"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#editorial-change"},
+"editors-draft": {"dfnID":"editors-draft","dfnText":"Editor\u2019s drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-editors-draft"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"}],"url":"#editors-draft"},
+"elected-group": {"dfnID":"elected-group","dfnText":"elected groups","external":false,"refSections":[{"refs":[{"id":"ref-for-elected-group"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-elected-group\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-elected-group\u2461"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#elected-group"},
+"embedded-registry": {"dfnID":"embedded-registry","dfnText":"embedded registry","external":false,"refSections":[{"refs":[{"id":"ref-for-embedded-registry"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-embedded-registry\u2460"},{"id":"ref-for-embedded-registry\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-embedded-registry\u2462"},{"id":"ref-for-embedded-registry\u2463"}],"title":"6.5.6. \nRegistries and Patents"},{"refs":[{"id":"ref-for-embedded-registry\u2464"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#embedded-registry"},
+"erratum": {"dfnID":"erratum","dfnText":"erratum","external":false,"refSections":[{"refs":[{"id":"ref-for-erratum"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-erratum\u2460"},{"id":"ref-for-erratum\u2461"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#erratum"},
+"exclusion-draft": {"dfnID":"exclusion-draft","dfnText":"Exclusion Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-exclusion-draft"},{"id":"ref-for-exclusion-draft\u2460"}],"title":"4.3. \nContent of a Charter"}],"url":"#exclusion-draft"},
+"exclusion-draft-charter": {"dfnID":"exclusion-draft-charter","dfnText":"Exclusion Draft Charter","external":false,"refSections":[{"refs":[{"id":"ref-for-exclusion-draft-charter"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#exclusion-draft-charter"},
+"fdn-member-consortium": {"dfnID":"fdn-member-consortium","dfnText":"Member Consortium","external":false,"refSections":[],"url":"#fdn-member-consortium"},
+"fellows": {"dfnID":"fellows","dfnText":"W3C Fellows","external":false,"refSections":[{"refs":[{"id":"ref-for-fellows"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-fellows"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}],"url":"#fellows"},
+"formally-addressed": {"dfnID":"formally-addressed","dfnText":"formally addressed","external":false,"refSections":[{"refs":[{"id":"ref-for-formally-addressed"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-formally-addressed\u2460"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-formally-addressed\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-formally-addressed\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-formally-addressed\u2463"},{"id":"ref-for-formally-addressed\u2464"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-formally-addressed\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-formally-addressed\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-formally-addressed\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#formally-addressed"},
+"fpwd": {"dfnID":"fpwd","dfnText":"First Public Working Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-fpwd"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-fpwd\u2460"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-fpwd\u2461"},{"id":"ref-for-fpwd\u2462"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-fpwd\u2463"},{"id":"ref-for-fpwd\u2464"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-fpwd\u2465"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-fpwd\u2466"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-fpwd\u2467"},{"id":"ref-for-fpwd\u2468"}],"title":"6.6. \nSwitching Tracks"}],"url":"#fpwd"},
+"ftf-meeting": {"dfnID":"ftf-meeting","dfnText":"face-to-face meeting","external":false,"refSections":[{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"5.6.2.1. \nCouncil Composition"}],"url":"#ftf-meeting"},
+"fully-addressed": {"dfnID":"fully-addressed","dfnText":"fully addressed","external":false,"refSections":[{"refs":[{"id":"ref-for-fully-addressed"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-fully-addressed\u2460"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#fully-addressed"},
+"good-standing": {"dfnID":"good-standing","dfnText":"Good Standing","external":false,"refSections":[{"refs":[{"id":"ref-for-good-standing"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-good-standing\u2460"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-good-standing\u2461"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#good-standing"},
+"group-decision": {"dfnID":"group-decision","dfnText":"group decisions","external":false,"refSections":[{"refs":[{"id":"ref-for-group-decision"},{"id":"ref-for-group-decision\u2460"}],"title":"3.1.2.2. \nMeeting Minutes"},{"refs":[{"id":"ref-for-group-decision\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-group-decision\u2462"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-group-decision\u2463"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-group-decision\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-group-decision\u2465"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-group-decision\u2466"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-group-decision\u2467"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-group-decision\u2468"}],"title":"6.6. \nSwitching Tracks"}],"url":"#group-decision"},
+"igparticipant": {"dfnID":"igparticipant","dfnText":"participants in an Interest Group","external":false,"refSections":[{"refs":[{"id":"ref-for-igparticipant"}],"title":"3. \nGroups and Participation"},{"refs":[{"id":"ref-for-igparticipant"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#igparticipant"},
+"inv-expert-info": {"dfnID":"inv-expert-info","dfnText":"participate in a Working Group as an Invited Expert","external":false,"refSections":[{"refs":[{"id":"ref-for-inv-expert-info"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-inv-expert-info"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"}],"url":"#inv-expert-info"},
+"invited-expert-in-a-working-group": {"dfnID":"invited-expert-in-a-working-group","dfnText":"Invited Expert in a Working Group","external":false,"refSections":[{"refs":[{"id":"ref-for-invited-expert-in-a-working-group"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-invited-expert-in-a-working-group\u2460"}],"title":"3.4.3.4. \nInvited Expert in an Interest Group"}],"url":"#invited-expert-in-a-working-group"},
+"invited-expert-in-an-interest-group": {"dfnID":"invited-expert-in-an-interest-group","dfnText":"Invited Expert in an Interest Group","external":false,"refSections":[],"url":"#invited-expert-in-an-interest-group"},
+"last-call": {"dfnID":"last-call","dfnText":"Last Call","external":false,"refSections":[],"url":"#last-call"},
+"last-call-for-review-of-proposed-additions": {"dfnID":"last-call-for-review-of-proposed-additions","dfnText":"Last Call for Review of Proposed Additions","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-additions"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-for-review-of-proposed-additions"},
+"last-call-for-review-of-proposed-corrections": {"dfnID":"last-call-for-review-of-proposed-corrections","dfnText":"Last Call for Review of Proposed Corrections","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-corrections"}],"title":"6.4.4. \nRevising W3C Statements"}],"url":"#last-call-for-review-of-proposed-corrections"},
+"last-call-for-review-of-proposed-corrections-and-additions": {"dfnID":"last-call-for-review-of-proposed-corrections-and-additions","dfnText":"Last Call for Review of Proposed Corrections and Additions","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-corrections-and-additions"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-for-review-of-proposed-corrections-and-additions"},
+"last-call-review": {"dfnID":"last-call-review","dfnText":"Last Call for Review of Proposed Amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-review"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-last-call-review\u2460"},{"id":"ref-for-last-call-review\u2461"},{"id":"ref-for-last-call-review\u2462"},{"id":"ref-for-last-call-review\u2463"},{"id":"ref-for-last-call-review\u2464"},{"id":"ref-for-last-call-review\u2465"},{"id":"ref-for-last-call-review\u2466"},{"id":"ref-for-last-call-review\u2467"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-review"},
+"liaison": {"dfnID":"liaison","dfnText":"liaison","external":false,"refSections":[],"url":"#liaison"},
+"maturity-levels": {"dfnID":"maturity-levels","dfnText":"Maturity level","external":false,"refSections":[],"url":"#maturity-levels"},
+"member-association": {"dfnID":"member-association","dfnText":"Member Association","external":false,"refSections":[{"refs":[{"id":"ref-for-member-association"},{"id":"ref-for-member-association\u2460"},{"id":"ref-for-member-association\u2461"},{"id":"ref-for-member-association\u2462"},{"id":"ref-for-member-association\u2463"},{"id":"ref-for-member-association\u2464"}],"title":"2.1.2.1. \nMembership Associations"},{"refs":[{"id":"ref-for-member-association\u2465"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#member-association"},
+"member-representative-in-a-working-group": {"dfnID":"member-representative-in-a-working-group","dfnText":"Member representative in a Working Group","external":false,"refSections":[],"url":"#member-representative-in-a-working-group"},
+"member-representative-in-an-interest-group": {"dfnID":"member-representative-in-an-interest-group","dfnText":"Member representative in an Interest Group","external":false,"refSections":[{"refs":[{"id":"ref-for-member-representative-in-an-interest-group"}],"title":"3.4.3.2. \nMember Representative in an Interest Group"}],"url":"#member-representative-in-an-interest-group"},
+"minor-changes": {"dfnID":"minor-changes","dfnText":"minor changes","external":false,"refSections":[{"refs":[{"id":"ref-for-minor-changes"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-minor-changes\u2460"},{"id":"ref-for-minor-changes\u2461"},{"id":"ref-for-minor-changes\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#minor-changes"},
+"minority-opinion": {"dfnID":"minority-opinion","dfnText":"Minority Opinion","external":false,"refSections":[{"refs":[{"id":"ref-for-minority-opinion"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#minority-opinion"},
+"minutes": {"dfnID":"minutes","dfnText":"minutes","external":false,"refSections":[{"refs":[{"id":"ref-for-minutes"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-minutes\u2460"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-minutes\u2461"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#minutes"},
+"mou": {"dfnID":"mou","dfnText":"Memorandum of Understanding","external":false,"refSections":[],"url":"#mou"},
+"mtg-substitute": {"dfnID":"mtg-substitute","dfnText":"substitute","external":false,"refSections":[{"refs":[{"id":"ref-for-mtg-substitute"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#mtg-substitute"},
+"not-required": {"dfnID":"not-required","dfnText":"not required","external":false,"refSections":[],"url":"#not-required"},
+"note-draft": {"dfnID":"note-draft","dfnText":"Note Drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-note-draft"},{"id":"ref-for-note-draft\u2460"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-note-draft\u2461"},{"id":"ref-for-note-draft\u2462"},{"id":"ref-for-note-draft\u2463"},{"id":"ref-for-note-draft\u2464"}],"title":"6.4.2. \nPublishing Notes"}],"url":"#note-draft"},
+"obsolete-registry": {"dfnID":"obsolete-registry","dfnText":"Obsolete Registry","external":false,"refSections":[],"url":"#obsolete-registry"},
+"other-charter": {"dfnID":"other-charter","dfnText":"Other Charter","external":false,"refSections":[],"url":"#other-charter"},
+"overrule": {"dfnID":"overrule","dfnText":"overruled","external":false,"refSections":[{"refs":[{"id":"ref-for-overrule"},{"id":"ref-for-overrule\u2460"},{"id":"ref-for-overrule\u2461"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-overrule\u2462"}],"title":"6.3.9.3. \nResolution of Review"}],"url":"#overrule"},
+"overturn": {"dfnID":"overturn","dfnText":"overturn","external":false,"refSections":[{"refs":[{"id":"ref-for-overturn"},{"id":"ref-for-overturn\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-overturn\u2461"},{"id":"ref-for-overturn\u2462"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#overturn"},
+"participant": {"dfnID":"participant","dfnText":"participant","external":false,"refSections":[{"refs":[{"id":"ref-for-participant"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-participant\u2460"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#participant"},
+"patent-review-drafts": {"dfnID":"patent-review-drafts","dfnText":"Patent Review Drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-patent-review-drafts"},{"id":"ref-for-patent-review-drafts\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-patent-review-drafts\u2461"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-patent-review-drafts\u2462"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-patent-review-drafts\u2463"}],"title":"6.6. \nSwitching Tracks"}],"url":"#patent-review-drafts"},
+"primary-affiliation": {"dfnID":"primary-affiliation","dfnText":"primary affiliation","external":false,"refSections":[{"refs":[{"id":"ref-for-primary-affiliation"},{"id":"ref-for-primary-affiliation\u2460"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-primary-affiliation\u2461"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}],"url":"#primary-affiliation"},
+"proposed-additions": {"dfnID":"proposed-additions","dfnText":"proposed additions","external":false,"refSections":[],"url":"#proposed-additions"},
+"proposed-amendments": {"dfnID":"proposed-amendments","dfnText":"proposed amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-proposed-amendments"},{"id":"ref-for-proposed-amendments\u2460"},{"id":"ref-for-proposed-amendments\u2461"},{"id":"ref-for-proposed-amendments\u2462"},{"id":"ref-for-proposed-amendments\u2463"},{"id":"ref-for-proposed-amendments\u2464"},{"id":"ref-for-proposed-amendments\u2465"},{"id":"ref-for-proposed-amendments\u2466"},{"id":"ref-for-proposed-amendments\u2467"},{"id":"ref-for-proposed-amendments\u2468"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-proposed-amendments\u2460\u24ea"},{"id":"ref-for-proposed-amendments\u2460\u2460"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-proposed-amendments\u2460\u2461"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#proposed-amendments"},
+"proposed-corrections": {"dfnID":"proposed-corrections","dfnText":"proposed corrections","external":false,"refSections":[],"url":"#proposed-corrections"},
+"public-participant-ig": {"dfnID":"public-participant-ig","dfnText":"public participants","external":false,"refSections":[{"refs":[{"id":"ref-for-public-participant-ig"}],"title":"4.3. \nContent of a Charter"}],"url":"#public-participant-ig"},
+"publishing": {"dfnID":"publishing","dfnText":"Publishing","external":false,"refSections":[{"refs":[{"id":"ref-for-publishing"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-publishing\u2460"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-publishing\u2461"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-publishing\u2462"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-publishing\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-publishing\u2464"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-publishing\u2465"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-publishing\u2466"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-publishing\u2467"},{"id":"ref-for-publishing\u2468"},{"id":"ref-for-publishing\u2460\u24ea"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-publishing\u2460\u2460"},{"id":"ref-for-publishing\u2460\u2461"}],"title":"6.4.1. \nGroup Notes"}],"url":"#publishing"},
+"rec-amended": {"dfnID":"rec-amended","dfnText":"Amended Recommendation","external":false,"refSections":[],"url":"#rec-amended"},
+"registry": {"dfnID":"registry","dfnText":"registry","external":false,"refSections":[{"refs":[{"id":"ref-for-registry"},{"id":"ref-for-registry\u2460"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry\u2461"},{"id":"ref-for-registry\u2462"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry\u2463"},{"id":"ref-for-registry\u2464"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry\u2465"},{"id":"ref-for-registry\u2466"},{"id":"ref-for-registry\u2467"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry\u2468"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry"},
+"registry-change": {"dfnID":"registry-change","dfnText":"registry changes","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-change"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-change\u2460"},{"id":"ref-for-registry-change\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-change\u2462"},{"id":"ref-for-registry-change\u2463"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#registry-change"},
+"registry-data": {"dfnID":"registry-data","dfnText":"registry data","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-data"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-data\u2460"},{"id":"ref-for-registry-data\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-data"},
+"registry-data-report": {"dfnID":"registry-data-report","dfnText":"Registry Data Report","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-data-report"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-data-report\u2460"},{"id":"ref-for-registry-data-report\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-data-report"},
+"registry-definition": {"dfnID":"registry-definition","dfnText":"registry definition","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-definition"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry-definition\u2460"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry-definition\u2461"},{"id":"ref-for-registry-definition\u2462"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-definition\u2463"},{"id":"ref-for-registry-definition\u2464"},{"id":"ref-for-registry-definition\u2465"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-definition\u2466"},{"id":"ref-for-registry-definition\u2467"},{"id":"ref-for-registry-definition\u2468"},{"id":"ref-for-registry-definition\u2460\u24ea"},{"id":"ref-for-registry-definition\u2460\u2460"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-registry-definition\u2460\u2461"},{"id":"ref-for-registry-definition\u2460\u2462"},{"id":"ref-for-registry-definition\u2460\u2463"},{"id":"ref-for-registry-definition\u2460\u2464"},{"id":"ref-for-registry-definition\u2460\u2465"},{"id":"ref-for-registry-definition\u2460\u2466"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-definition"},
+"registry-draft": {"dfnID":"registry-draft","dfnText":"Registry Draft","external":false,"refSections":[],"url":"#registry-draft"},
+"registry-entry": {"dfnID":"registry-entry","dfnText":"registry entries","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-entry"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-registry-entry\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-entry\u2461"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-registry-entry\u2462"}],"title":"6.5.5. \nSpecifications that Reference Registries"}],"url":"#registry-entry"},
+"registry-report": {"dfnID":"registry-report","dfnText":"registry report","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-report"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry-report\u2460"},{"id":"ref-for-registry-report\u2461"},{"id":"ref-for-registry-report\u2462"},{"id":"ref-for-registry-report\u2463"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-report\u2464"}],"title":"6.5.6. \nRegistries and Patents"}],"url":"#registry-report"},
+"registry-table": {"dfnID":"registry-table","dfnText":"registry tables","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-table"},{"id":"ref-for-registry-table\u2460"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-registry-table\u2461"},{"id":"ref-for-registry-table\u2462"},{"id":"ref-for-registry-table\u2463"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry-table\u2464"},{"id":"ref-for-registry-table\u2465"},{"id":"ref-for-registry-table\u2466"},{"id":"ref-for-registry-table\u2467"},{"id":"ref-for-registry-table\u2468"},{"id":"ref-for-registry-table\u2460\u24ea"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-table\u2460\u2460"},{"id":"ref-for-registry-table\u2460\u2461"},{"id":"ref-for-registry-table\u2460\u2462"},{"id":"ref-for-registry-table\u2460\u2463"},{"id":"ref-for-registry-table\u2460\u2464"},{"id":"ref-for-registry-table\u2460\u2465"},{"id":"ref-for-registry-table\u2460\u2466"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-table\u2460\u2467"},{"id":"ref-for-registry-table\u2460\u2468"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-registry-table\u2461\u24ea"},{"id":"ref-for-registry-table\u2461\u2460"},{"id":"ref-for-registry-table\u2461\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-table"},
+"registry-track": {"dfnID":"registry-track","dfnText":"Registry Track","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-track"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#registry-track"},
+"rejected": {"dfnID":"rejected","dfnText":"rejected","external":false,"refSections":[{"refs":[{"id":"ref-for-rejected"}],"title":"9. \nMember Submissions"}],"url":"#rejected"},
+"related-member": {"dfnID":"related-member","dfnText":"related","external":false,"refSections":[{"refs":[{"id":"ref-for-related-member"}],"title":"2.1.2.2. \nRelated Members"},{"refs":[{"id":"ref-for-related-member\u2460"}],"title":"2.1.3. \nGood Standing"},{"refs":[{"id":"ref-for-related-member\u2461"},{"id":"ref-for-related-member\u2462"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-related-member\u2463"}],"title":"5.8. \nAdvisory Committee Votes"}],"url":"#related-member"},
+"renounce": {"dfnID":"renounce","dfnText":"renounce","external":false,"refSections":[{"refs":[{"id":"ref-for-renounce"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-renounce\u2460"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-renounce\u2461"},{"id":"ref-for-renounce\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-renounce\u2463"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#renounce"},
+"rescinded-candidate-recommendation": {"dfnID":"rescinded-candidate-recommendation","dfnText":"Rescinded Candidate Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-rescinded-candidate-recommendation"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-rescinded-candidate-recommendation\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#rescinded-candidate-recommendation"},
+"reviewform": {"dfnID":"reviewform","dfnText":"Call for Review","external":false,"refSections":[{"refs":[{"id":"ref-for-reviewform"},{"id":"ref-for-reviewform\u2460"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-reviewform\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"}],"url":"#reviewform"},
+"statement": {"dfnID":"statement","dfnText":"W3C Statement","external":false,"refSections":[{"refs":[{"id":"ref-for-statement"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-statement\u2460"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-statement\u2461"},{"id":"ref-for-statement\u2462"},{"id":"ref-for-statement\u2463"},{"id":"ref-for-statement\u2464"},{"id":"ref-for-statement\u2465"},{"id":"ref-for-statement\u2466"},{"id":"ref-for-statement\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-statement\u2468"},{"id":"ref-for-statement\u2460\u24ea"},{"id":"ref-for-statement\u2460\u2460"},{"id":"ref-for-statement\u2460\u2461"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-statement\u2460\u2462"}],"title":"6.6. \nSwitching Tracks"}],"url":"#statement"},
+"submission-appeals": {"dfnID":"submission-appeals","dfnText":"Submission Appeals","external":false,"refSections":[{"refs":[{"id":"ref-for-submission-appeals"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-submission-appeals\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-submission-appeals\u2461"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-submission-appeals\u2462"},{"id":"ref-for-submission-appeals\u2463"}],"title":"9. \nMember Submissions"}],"url":"#submission-appeals"},
+"submitter": {"dfnID":"submitter","dfnText":"Submitter(s)","external":false,"refSections":[{"refs":[{"id":"ref-for-submitter"},{"id":"ref-for-submitter\u2460"},{"id":"ref-for-submitter\u2461"},{"id":"ref-for-submitter\u2462"},{"id":"ref-for-submitter\u2463"},{"id":"ref-for-submitter\u2464"},{"id":"ref-for-submitter\u2465"},{"id":"ref-for-submitter\u2466"}],"title":"9. \nMember Submissions"}],"url":"#submitter"},
+"subsidiary": {"dfnID":"subsidiary","dfnText":"subsidiary","external":false,"refSections":[{"refs":[{"id":"ref-for-subsidiary"},{"id":"ref-for-subsidiary\u2460"}],"title":"2.1.2.2. \nRelated Members"}],"url":"#subsidiary"},
+"substantive-change": {"dfnID":"substantive-change","dfnText":"substantive changes","external":false,"refSections":[{"refs":[{"id":"ref-for-substantive-change"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-substantive-change\u2460"},{"id":"ref-for-substantive-change\u2461"},{"id":"ref-for-substantive-change\u2462"},{"id":"ref-for-substantive-change\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-substantive-change\u2464"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-substantive-change\u2465"},{"id":"ref-for-substantive-change\u2466"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-substantive-change\u2467"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-substantive-change\u2468"},{"id":"ref-for-substantive-change\u2460\u24ea"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2460"},{"id":"ref-for-substantive-change\u2460\u2461"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2462"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2463"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"}],"url":"#substantive-change"},
+"superseded-registry": {"dfnID":"superseded-registry","dfnText":"Superseded Registry","external":false,"refSections":[],"url":"#superseded-registry"},
+"supplemental-confidential-council-report": {"dfnID":"supplemental-confidential-council-report","dfnText":"Supplemental Confidential Council Report","external":false,"refSections":[],"url":"#supplemental-confidential-council-report"},
+"team": {"dfnID":"team","dfnText":"Team","external":false,"refSections":[{"refs":[{"id":"ref-for-team"},{"id":"ref-for-team\u2460"},{"id":"ref-for-team\u2461"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-team\u2462"},{"id":"ref-for-team\u2463"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-team\u2464"},{"id":"ref-for-team\u2465"},{"id":"ref-for-team\u2466"}],"title":"3.1.1.2. \nConflict of Interest Policy"},{"refs":[{"id":"ref-for-team\u2467"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-team\u2468"},{"id":"ref-for-team\u2460\u24ea"}],"title":"3.1.4. \nResignation from a Group"},{"refs":[{"id":"ref-for-team\u2460\u2460"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-team\u2460\u2461"},{"id":"ref-for-team\u2460\u2462"},{"id":"ref-for-team\u2460\u2463"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-team\u2460\u2464"},{"id":"ref-for-team\u2460\u2465"},{"id":"ref-for-team\u2460\u2466"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-team\u2460\u2467"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-team\u2460\u2468"}],"title":"3.3.1.3. \nCommunications of the Advisory Board"},{"refs":[{"id":"ref-for-team\u2461\u24ea"},{"id":"ref-for-team\u2461\u2460"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-team\u2461\u2461"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-team\u2461\u2462"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-team\u2461\u2463"},{"id":"ref-for-team\u2461\u2464"},{"id":"ref-for-team\u2461\u2465"},{"id":"ref-for-team\u2461\u2466"},{"id":"ref-for-team\u2461\u2467"},{"id":"ref-for-team\u2461\u2468"},{"id":"ref-for-team\u2462\u24ea"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-team\u2462\u2460"},{"id":"ref-for-team\u2462\u2461"},{"id":"ref-for-team\u2462\u2462"},{"id":"ref-for-team\u2462\u2463"},{"id":"ref-for-team\u2462\u2464"},{"id":"ref-for-team\u2462\u2465"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-team\u2462\u2466"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-team\u2462\u2467"},{"id":"ref-for-team\u2462\u2468"},{"id":"ref-for-team\u2463\u24ea"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-team\u2463\u2460"},{"id":"ref-for-team\u2463\u2461"},{"id":"ref-for-team\u2463\u2462"},{"id":"ref-for-team\u2463\u2463"},{"id":"ref-for-team\u2463\u2464"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-team\u2463\u2465"},{"id":"ref-for-team\u2463\u2466"},{"id":"ref-for-team\u2463\u2467"},{"id":"ref-for-team\u2463\u2468"},{"id":"ref-for-team\u2464\u24ea"},{"id":"ref-for-team\u2464\u2460"},{"id":"ref-for-team\u2464\u2461"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-team\u2464\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-team\u2464\u2463"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-team\u2464\u2464"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-team\u2464\u2465"},{"id":"ref-for-team\u2464\u2466"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-team\u2464\u2467"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-team\u2464\u2468"},{"id":"ref-for-team\u2465\u24ea"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-team\u2465\u2460"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-team\u2465\u2461"},{"id":"ref-for-team\u2465\u2462"},{"id":"ref-for-team\u2465\u2463"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-team\u2465\u2464"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-team\u2465\u2465"},{"id":"ref-for-team\u2465\u2466"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-team\u2465\u2467"},{"id":"ref-for-team\u2465\u2468"},{"id":"ref-for-team\u2466\u24ea"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-team\u2466\u2460"},{"id":"ref-for-team\u2466\u2461"},{"id":"ref-for-team\u2466\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-team\u2466\u2463"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-team\u2466\u2464"},{"id":"ref-for-team\u2466\u2465"},{"id":"ref-for-team\u2466\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-team\u2466\u2467"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-team\u2466\u2468"},{"id":"ref-for-team\u2467\u24ea"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-team\u2467\u2460"},{"id":"ref-for-team\u2467\u2461"},{"id":"ref-for-team\u2467\u2462"},{"id":"ref-for-team\u2467\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-team\u2467\u2464"},{"id":"ref-for-team\u2467\u2465"},{"id":"ref-for-team\u2467\u2466"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-team\u2467\u2467"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-team\u2467\u2468"},{"id":"ref-for-team\u2468\u24ea"},{"id":"ref-for-team\u2468\u2460"},{"id":"ref-for-team\u2468\u2461"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-team\u2468\u2462"}],"title":"6.2.7. \nLicense Grants from Non-Participants"},{"refs":[{"id":"ref-for-team\u2468\u2463"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-team\u2468\u2464"}],"title":"6.3.2. \nImplementation Experience"},{"refs":[{"id":"ref-for-team\u2468\u2465"},{"id":"ref-for-team\u2468\u2466"},{"id":"ref-for-team\u2468\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2468\u2468"},{"id":"ref-for-team\u2460\u24ea\u24ea"},{"id":"ref-for-team\u2460\u24ea\u2460"},{"id":"ref-for-team\u2460\u24ea\u2461"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2462"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2463"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2464"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2465"},{"id":"ref-for-team\u2460\u24ea\u2466"},{"id":"ref-for-team\u2460\u24ea\u2467"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2468"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-team\u2460\u2460\u24ea"},{"id":"ref-for-team\u2460\u2460\u2460"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2461"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2462"},{"id":"ref-for-team\u2460\u2460\u2463"},{"id":"ref-for-team\u2460\u2460\u2464"},{"id":"ref-for-team\u2460\u2460\u2465"},{"id":"ref-for-team\u2460\u2460\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2467"},{"id":"ref-for-team\u2460\u2460\u2468"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-team\u2460\u2461\u24ea"},{"id":"ref-for-team\u2460\u2461\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2462"},{"id":"ref-for-team\u2460\u2461\u2463"}],"title":"7.1. \nPublic Communication"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2464"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2465"},{"id":"ref-for-team\u2460\u2461\u2466"},{"id":"ref-for-team\u2460\u2461\u2467"},{"id":"ref-for-team\u2460\u2461\u2468"}],"title":"7.3. \nChanging Confidentiality Level"},{"refs":[{"id":"ref-for-team\u2460\u2462\u24ea"},{"id":"ref-for-team\u2460\u2462\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-team\u2460\u2462\u2461"},{"id":"ref-for-team\u2460\u2462\u2462"},{"id":"ref-for-team\u2460\u2462\u2463"},{"id":"ref-for-team\u2460\u2462\u2464"},{"id":"ref-for-team\u2460\u2462\u2465"},{"id":"ref-for-team\u2460\u2462\u2466"},{"id":"ref-for-team\u2460\u2462\u2467"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-team\u2460\u2462\u2468"}],"title":"10. \nProcess Evolution"}],"url":"#team"},
+"team-contact": {"dfnID":"team-contact","dfnText":"Team Contact","external":false,"refSections":[],"url":"#team-contact"},
+"team-correction": {"dfnID":"team-correction","dfnText":"Team correction","external":false,"refSections":[{"refs":[{"id":"ref-for-team-correction"},{"id":"ref-for-team-correction\u2460"},{"id":"ref-for-team-correction\u2461"},{"id":"ref-for-team-correction\u2462"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#team-correction"},
+"team-decision": {"dfnID":"team-decision","dfnText":"Team Decisions","external":false,"refSections":[{"refs":[{"id":"ref-for-team-decision"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-team-decision\u2460"},{"id":"ref-for-team-decision\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-team-decision\u2462"},{"id":"ref-for-team-decision\u2463"},{"id":"ref-for-team-decision\u2464"},{"id":"ref-for-team-decision\u2465"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-team-decision\u2466"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-team-decision\u2467"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-team-decision\u2468"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-team-decision\u2460\u24ea"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-team-decision\u2460\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-team-decision\u2460\u2461"}],"title":"8. \nLiaisons"}],"url":"#team-decision"},
+"team-representative-in-a-working-group": {"dfnID":"team-representative-in-a-working-group","dfnText":"Team representative in a Working Group","external":false,"refSections":[],"url":"#team-representative-in-a-working-group"},
+"team-representative-in-an-interest-group": {"dfnID":"team-representative-in-an-interest-group","dfnText":"Team representative in an Interest Group","external":false,"refSections":[],"url":"#team-representative-in-an-interest-group"},
+"technical-agreement": {"dfnID":"technical-agreement","dfnText":"technical agreement","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-agreement"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-technical-agreement\u2460"},{"id":"ref-for-technical-agreement\u2461"},{"id":"ref-for-technical-agreement\u2462"},{"id":"ref-for-technical-agreement\u2463"},{"id":"ref-for-technical-agreement\u2464"},{"id":"ref-for-technical-agreement\u2465"},{"id":"ref-for-technical-agreement\u2466"},{"id":"ref-for-technical-agreement\u2467"},{"id":"ref-for-technical-agreement\u2468"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-technical-agreement\u2460\u24ea"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#technical-agreement"},
+"technical-architecture-group": {"dfnID":"technical-architecture-group","dfnText":"TAG","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-architecture-group"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461"},{"id":"ref-for-technical-architecture-group\u2462"},{"id":"ref-for-technical-architecture-group\u2463"},{"id":"ref-for-technical-architecture-group\u2464"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2465"},{"id":"ref-for-technical-architecture-group\u2466"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2467"},{"id":"ref-for-technical-architecture-group\u2468"},{"id":"ref-for-technical-architecture-group\u2460\u24ea"},{"id":"ref-for-technical-architecture-group\u2460\u2460"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2461"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2462"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2463"},{"id":"ref-for-technical-architecture-group\u2460\u2464"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2465"},{"id":"ref-for-technical-architecture-group\u2460\u2466"},{"id":"ref-for-technical-architecture-group\u2460\u2467"},{"id":"ref-for-technical-architecture-group\u2460\u2468"},{"id":"ref-for-technical-architecture-group\u2461\u24ea"},{"id":"ref-for-technical-architecture-group\u2461\u2460"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2461"}],"title":"3.3.3.5. \nVerifiable Random Selection Procedure"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2462"},{"id":"ref-for-technical-architecture-group\u2461\u2463"},{"id":"ref-for-technical-architecture-group\u2461\u2464"},{"id":"ref-for-technical-architecture-group\u2461\u2465"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2466"},{"id":"ref-for-technical-architecture-group\u2461\u2467"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2468"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u24ea"},{"id":"ref-for-technical-architecture-group\u2462\u2460"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2461"},{"id":"ref-for-technical-architecture-group\u2462\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2463"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2465"},{"id":"ref-for-technical-architecture-group\u2462\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2467"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2468"}],"title":"9. \nMember Submissions"}],"url":"#technical-architecture-group"},
+"technical-report": {"dfnID":"technical-report","dfnText":"Technical Report","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-report"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-technical-report\u2460"},{"id":"ref-for-technical-report\u2461"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-technical-report\u2462"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-technical-report\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-technical-report\u2464"},{"id":"ref-for-technical-report\u2465"},{"id":"ref-for-technical-report\u2466"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-technical-report\u2467"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-technical-report\u2468"},{"id":"ref-for-technical-report\u2460\u24ea"},{"id":"ref-for-technical-report\u2460\u2460"},{"id":"ref-for-technical-report\u2460\u2461"},{"id":"ref-for-technical-report\u2460\u2462"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-technical-report\u2460\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-technical-report\u2460\u2464"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2460\u2465"},{"id":"ref-for-technical-report\u2460\u2466"},{"id":"ref-for-technical-report\u2460\u2467"},{"id":"ref-for-technical-report\u2460\u2468"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2461\u24ea"},{"id":"ref-for-technical-report\u2461\u2460"},{"id":"ref-for-technical-report\u2461\u2461"},{"id":"ref-for-technical-report\u2461\u2462"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-technical-report\u2461\u2463"},{"id":"ref-for-technical-report\u2461\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2461\u2465"},{"id":"ref-for-technical-report\u2461\u2466"},{"id":"ref-for-technical-report\u2461\u2467"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-technical-report\u2461\u2468"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-technical-report\u2462\u24ea"},{"id":"ref-for-technical-report\u2462\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-technical-report\u2462\u2461"},{"id":"ref-for-technical-report\u2462\u2462"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-technical-report\u2462\u2463"},{"id":"ref-for-technical-report\u2462\u2464"},{"id":"ref-for-technical-report\u2462\u2465"},{"id":"ref-for-technical-report\u2462\u2466"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-technical-report\u2462\u2467"},{"id":"ref-for-technical-report\u2462\u2468"},{"id":"ref-for-technical-report\u2463\u24ea"},{"id":"ref-for-technical-report\u2463\u2460"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-technical-report\u2463\u2461"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-technical-report\u2463\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#technical-report"},
+"trans-req": {"dfnID":"trans-req","dfnText":"Transition Requests","external":false,"refSections":[{"refs":[{"id":"ref-for-trans-req"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2460"},{"id":"ref-for-trans-req\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2462"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2463"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"}],"url":"#trans-req"},
+"update-requests": {"dfnID":"update-requests","dfnText":"Update Requests","external":false,"refSections":[{"refs":[{"id":"ref-for-update-requests"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-update-requests\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-update-requests\u2461"},{"id":"ref-for-update-requests\u2462"},{"id":"ref-for-update-requests\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-update-requests\u2464"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-update-requests\u2465"},{"id":"ref-for-update-requests\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-update-requests\u2467"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-update-requests\u2468"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-update-requests\u2460\u24ea"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-update-requests\u2460\u2460"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#update-requests"},
+"upheld": {"dfnID":"upheld","dfnText":"upheld","external":false,"refSections":[{"refs":[{"id":"ref-for-upheld"},{"id":"ref-for-upheld\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-upheld\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-upheld\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-upheld\u2463"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-upheld\u2464"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#upheld"},
+"w3c-council": {"dfnID":"w3c-council","dfnText":"W3C Council","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-council"},{"id":"ref-for-w3c-council\u2460"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-w3c-council\u2461"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-w3c-council\u2462"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-w3c-council\u2463"},{"id":"ref-for-w3c-council\u2464"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-w3c-council\u2465"},{"id":"ref-for-w3c-council\u2466"},{"id":"ref-for-w3c-council\u2467"},{"id":"ref-for-w3c-council\u2468"},{"id":"ref-for-w3c-council\u2460\u24ea"},{"id":"ref-for-w3c-council\u2460\u2460"},{"id":"ref-for-w3c-council\u2460\u2461"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2462"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2463"},{"id":"ref-for-w3c-council\u2460\u2464"},{"id":"ref-for-w3c-council\u2460\u2465"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2466"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2467"},{"id":"ref-for-w3c-council\u2460\u2468"},{"id":"ref-for-w3c-council\u2461\u24ea"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-w3c-council\u2461\u2460"},{"id":"ref-for-w3c-council\u2461\u2461"},{"id":"ref-for-w3c-council\u2461\u2462"},{"id":"ref-for-w3c-council\u2461\u2463"},{"id":"ref-for-w3c-council\u2461\u2464"},{"id":"ref-for-w3c-council\u2461\u2465"},{"id":"ref-for-w3c-council\u2461\u2466"},{"id":"ref-for-w3c-council\u2461\u2467"},{"id":"ref-for-w3c-council\u2461\u2468"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-w3c-council\u2462\u24ea"},{"id":"ref-for-w3c-council\u2462\u2460"},{"id":"ref-for-w3c-council\u2462\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2462"},{"id":"ref-for-w3c-council\u2462\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2465"},{"id":"ref-for-w3c-council\u2462\u2466"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2467"},{"id":"ref-for-w3c-council\u2462\u2468"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#w3c-council"},
+"w3c-council-chair": {"dfnID":"w3c-council-chair","dfnText":"Chair","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-council-chair"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-w3c-council-chair\u2460"}],"title":"5.6.2.4. \nShort Circuit"},{"refs":[{"id":"ref-for-w3c-council-chair\u2461"},{"id":"ref-for-w3c-council-chair\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-w3c-council-chair\u2463"},{"id":"ref-for-w3c-council-chair\u2464"},{"id":"ref-for-w3c-council-chair\u2465"},{"id":"ref-for-w3c-council-chair\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#w3c-council-chair"},
+"w3c-group": {"dfnID":"w3c-group","dfnText":"W3C Group","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-group"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-w3c-group\u2460"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-w3c-group\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-w3c-group\u2462"},{"id":"ref-for-w3c-group\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"#w3c-group"},
+"w3c-member": {"dfnID":"w3c-member","dfnText":"W3C Members","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-member"}],"title":"2.1.3. \nGood Standing"},{"refs":[{"id":"ref-for-w3c-member\u2460"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-w3c-member\u2461"},{"id":"ref-for-w3c-member\u2462"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-w3c-member\u2463"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-w3c-member\u2464"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-w3c-member\u2465"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-w3c-member\u2466"}],"title":"9. \nMember Submissions"}],"url":"#w3c-member"},
+"w3c-recommendation-track": {"dfnID":"w3c-recommendation-track","dfnText":"W3C Recommendation Track","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-recommendation-track"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460"},{"id":"ref-for-w3c-recommendation-track\u2461"},{"id":"ref-for-w3c-recommendation-track\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2463"},{"id":"ref-for-w3c-recommendation-track\u2464"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2465"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2466"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2467"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2468"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u24ea"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2462"}],"title":"6.5.6. \nRegistries and Patents"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2463"},{"id":"ref-for-w3c-recommendation-track\u2460\u2464"},{"id":"ref-for-w3c-recommendation-track\u2460\u2465"}],"title":"6.6. \nSwitching Tracks"}],"url":"#w3c-recommendation-track"},
+"w3c-recommendation-track-document": {"dfnID":"w3c-recommendation-track-document","dfnText":"W3C Recommendation Track document","external":false,"refSections":[],"url":"#w3c-recommendation-track-document"},
+"w3c-registry": {"dfnID":"w3c-registry","dfnText":"W3C Registry","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-registry"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-w3c-registry\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#w3c-registry"},
+"wgparticipant": {"dfnID":"wgparticipant","dfnText":"participants in a Working Group","external":false,"refSections":[{"refs":[{"id":"ref-for-wgparticipant"}],"title":"3. \nGroups and Participation"},{"refs":[{"id":"ref-for-wgparticipant"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#wgparticipant"},
+};
+
+document.addEventListener("DOMContentLoaded", ()=>{
+    genAllDfnPanels();
+
+    document.body.addEventListener("click", (e) => {
+        // If not handled already, just hide all dfn panels.
+        hideAllDfnPanels();
+    });
+});
+
+window.addEventListener("resize", () => {
+    // Pin any visible dfn panel
+    queryAll(".dfn-panel.on, .dfn-panel.activated").forEach(el=>positionDfnPanel(el));
+});
+
+function genAllDfnPanels() {
+    for(const panelData of Object.values(dfnPanelData)) {
+        const dfnID = panelData.dfnID;
+        const dfn = document.getElementById(dfnID);
+        if(!dfn) {
+            console.log(`Can't find dfn#${dfnID}.`, panelData);
+            continue;
+        }
+        dfn.panelData = panelData;
+        insertDfnPopupAction(dfn);
+    }
+}
+
+function genDfnPanel(dfn, { dfnID, url, dfnText, refSections, external }) {
+    const dfnPanel = mk.aside({
+        class: "dfn-panel on",
+        id: `infopanel-for-${dfnID}`,
+        "data-for": dfnID,
+        "aria-labelled-by":`infopaneltitle-for-${dfnID}`,
+        },
+        mk.span({id:`infopaneltitle-for-${dfnID}`, style:"display:none"},
+            `Info about the '${dfnText}' ${external?"external":""} reference.`),
+        mk.a({href:url, class:"dfn-link"}, url),
+        refSections.length == 0 ? [] :
+            mk.b({}, "Referenced in:"),
+            mk.ul({},
+                ...refSections.map(section=>
+                    mk.li({},
+                        ...section.refs.map((ref, refI)=>
+                            [
+                                mk.a({ href: `#${ref.id}` },
+                                    (refI == 0) ? section.title : `(${refI + 1})`
+                                ),
+                                " ",
+                            ]
+                        ),
+                    ),
+                ),
+            ),
+        genLinkingSyntaxes(dfn),
+    );
+
+    dfnPanel.addEventListener('click', (event) => {
+        if (event.target.nodeName == 'A') {
+            scrollToTargetAndHighlight(event);
+            pinDfnPanel(dfnPanel);
+        }
+        event.stopPropagation();
+        refocusOnTarget(event);
+    });
+    dfnPanel.addEventListener('keydown', (event) => {
+        if(event.keyCode == 27) { // Escape key
+            hideDfnPanel({dfnPanel});
+            event.stopPropagation();
+            event.preventDefault();
+        }
+    });
+
+    dfnPanel.dfn = dfn;
+    dfn.dfnPanel = dfnPanel;
+    return dfnPanel;
+}
+
+
+
+function hideAllDfnPanels() {
+    // Delete the currently-active dfn panel.
+    queryAll(".dfn-panel").forEach(dfnPanel=>hideDfnPanel({dfnPanel}));
+}
+
+function showDfnPanel(dfn) {
+    hideAllDfnPanels(); // Only display one at a time.
+
+    dfn.setAttribute("aria-expanded", "true");
+
+    const dfnPanel = genDfnPanel(dfn, dfn.panelData);
+
+    // Give the dfn a unique tabindex, and then
+    // give all the tabbable panel bits successive indexes.
+    let tabIndex = 100;
+    dfn.tabIndex = tabIndex++;
+    const tabbable = dfnPanel.querySelectorAll(":is(a, button)");
+    for (const el of tabbable) {
+        el.tabIndex = tabIndex++;
+    }
+
+    append(document.body, dfnPanel);
+    positionDfnPanel(dfnPanel);
+}
+
+function positionDfnPanel(dfnPanel) {
+    const dfn = dfnPanel.dfn;
+    const dfnPos = getBounds(dfn);
+    dfnPanel.style.top = dfnPos.bottom + "px";
+    dfnPanel.style.left = dfnPos.left + "px";
+
+    const panelPos = dfnPanel.getBoundingClientRect();
+    const panelMargin = 8;
+    const maxRight = document.body.parentNode.clientWidth - panelMargin;
+    if (panelPos.right > maxRight) {
+        const overflowAmount = panelPos.right - maxRight;
+        const newLeft = Math.max(panelMargin, dfnPos.left - overflowAmount);
+        dfnPanel.style.left = newLeft + "px";
+    }
+}
+
+function pinDfnPanel(dfnPanel) {
+    // Switch it to "activated" state, which pins it.
+    dfnPanel.classList.add("activated");
+    dfnPanel.style.position = "fixed";
+    dfnPanel.style.left = null;
+    dfnPanel.style.top = null;
+}
+
+function hideDfnPanel({dfn, dfnPanel}) {
+    if(!dfnPanel) dfnPanel = dfn.dfnPanel;
+    if(!dfn) dfn = dfnPanel.dfn;
+    dfn.dfnPanel = undefined;
+    dfnPanel.dfn = undefined;
+    dfn.setAttribute("aria-expanded", "false");
+    dfn.tabIndex = undefined;
+    dfnPanel.remove()
+}
+
+function toggleDfnPanel(dfn) {
+    if(dfn.dfnPanel) {
+        hideDfnPanel(dfn);
+    } else {
+        showDfnPanel(dfn);
+    }
+}
+
+function insertDfnPopupAction(dfn) {
+    dfn.setAttribute('role', 'button');
+    dfn.setAttribute('aria-expanded', 'false')
+    dfn.tabIndex = 0;
+    dfn.classList.add('has-dfn-panel');
+    dfn.addEventListener('click', (event) => {
+        toggleDfnPanel(dfn);
+        event.stopPropagation();
+    });
+    dfn.addEventListener('keypress', (event) => {
+        const kc = event.keyCode;
+        // 32->Space, 13->Enter
+        if(kc == 32 || kc == 13) {
+            toggleDfnPanel(dfn);
+            event.stopPropagation();
+            event.preventDefault();
+        }
+    });
+}
+
+function refocusOnTarget(event) {
+    const target = event.target;
+    setTimeout(() => {
+        // Refocus on the event.target element.
+        // This is needed after browser scrolls to the destination.
+        target.focus();
+    });
+}
+
+// TODO: shared util
+// Returns the root-level absolute position {left and top} of element.
+function getBounds(el, relativeTo=document.body) {
+    const relativeRect = relativeTo.getBoundingClientRect();
+    const elRect = el.getBoundingClientRect();
+    const top = elRect.top - relativeRect.top;
+    const left = elRect.left - relativeRect.left;
+    return {
+        top,
+        left,
+        bottom: top + elRect.height,
+        right: left + elRect.width,
+    }
+}
+
+function scrollToTargetAndHighlight(event) {
+    let hash = event.target.hash;
+    if (hash) {
+        hash = decodeURIComponent(hash.substring(1));
+        const dest = document.getElementById(hash);
+        if (dest) {
+            dest.classList.add('highlighted');
+            setTimeout(() => dest.classList.remove('highlighted'), 1000);
+        }
+    }
+}
+
+// Functions, divided by link type, that wrap an autolink's
+// contents with the appropriate outer syntax.
+// Alternately, a string naming another type they format
+// the same as.
+function needsFor(type) {
+    switch(type) {
+        case "descriptor":
+        case "value":
+        case "element-attr":
+        case "attr-value":
+        case "element-state":
+        case "method":
+        case "constructor":
+        case "argument":
+        case "attribute":
+        case "const":
+        case "dict-member":
+        case "event":
+        case "enum-value":
+        case "stringifier":
+        case "serializer":
+        case "iterator":
+        case "maplike":
+        case "setlike":
+        case "state":
+        case "mode":
+        case "context":
+        case "facet": return true;
+
+        default: return false;
+    }
+}
+function refusesFor(type) {
+    switch(type) {
+        case "property":
+        case "element":
+        case "interface":
+        case "namespace":
+        case "callback":
+        case "dictionary":
+        case "enum":
+        case "exception":
+        case "typedef":
+        case "http-header":
+        case "permission": return true;
+
+        default: return false;
+    }
+}
+function linkFormatterFromType(type) {
+    switch(type) {
+        case 'scheme':
+        case 'permission':
+        case 'dfn': return (text) => `[=${text}=]`;
+
+        case 'abstract-op': return (text) => `[\$${text}\$]`;
+
+        case 'function':
+        case 'at-rule':
+        case 'selector':
+        case 'value': return (text) => `''${text}''`;
+
+        case 'http-header': return (text) => `[:${text}:]`;
+
+        case 'interface':
+        case 'constructor':
+        case 'method':
+        case 'argument':
+        case 'attribute':
+        case 'callback':
+        case 'dictionary':
+        case 'dict-member':
+        case 'enum':
+        case 'enum-value':
+        case 'exception':
+        case 'const':
+        case 'typedef':
+        case 'stringifier':
+        case 'serializer':
+        case 'iterator':
+        case 'maplike':
+        case 'setlike':
+        case 'extended-attribute':
+        case 'event':
+        case 'idl': return (text) => `{{${text}}}`;
+
+        case 'element-state':
+        case 'element-attr':
+        case 'attr-value':
+        case 'element': return (element) => `<{${element}}>`;
+
+        case 'grammar': return (text) => `${text} (within a <pre class=prod>)`;
+
+        case 'type': return (text)=> `<<${text}>>`;
+
+        case 'descriptor':
+        case 'property': return (text) => `'${text}'`;
+
+        default: return;
+    };
+};
+
+function genLinkingSyntaxes(dfn) {
+    if(dfn.tagName != "DFN") return;
+
+    const type = dfn.getAttribute('data-dfn-type');
+    if(!type) {
+        console.log(`<dfn> doesn't have a data-dfn-type:`, dfn);
+        return [];
+    }
+
+    // Return a function that wraps link text based on the type
+    const linkFormatter = linkFormatterFromType(type);
+    if(!linkFormatter) {
+        console.log(`<dfn> has an unknown data-dfn-type:`, dfn);
+        return [];
+    }
+
+    let ltAlts;
+    if(dfn.hasAttribute('data-lt')) {
+        ltAlts = dfn.getAttribute('data-lt')
+            .split("|")
+            .map(x=>x.trim());
+    } else {
+        ltAlts = [dfn.textContent.trim()];
+    }
+    if(type == "type") {
+        // lt of "<foo>", but "foo" is the interior;
+        // <<foo/bar>> is how you write it with a for,
+        // not <foo/<bar>> or whatever.
+        for(var i = 0; i < ltAlts.length; i++) {
+            const lt = ltAlts[i];
+            const match = /<(.*)>/.exec(lt);
+            if(match) { ltAlts[i] = match[1]; }
+        }
+    }
+
+    let forAlts;
+    if(dfn.hasAttribute('data-dfn-for')) {
+        forAlts = dfn.getAttribute('data-dfn-for')
+            .split(",")
+            .map(x=>x.trim());
+    } else {
+        forAlts = [''];
+    }
+
+    let linkingSyntaxes = [];
+    if(!needsFor(type)) {
+        for(const lt of ltAlts) {
+            linkingSyntaxes.push(linkFormatter(lt));
+        }
+    }
+    if(!refusesFor(type)) {
+        for(const f of forAlts) {
+            linkingSyntaxes.push(linkFormatter(`${f}/${ltAlts[0]}`))
+        }
+    }
+    return [
+        mk.b({}, 'Possible linking syntaxes:'),
+        mk.ul({},
+            ...linkingSyntaxes.map(link => {
+                const copyLink = async () =>
+                    await navigator.clipboard.writeText(link);
+                return mk.li({},
+                    mk.div({ class: 'link-item' },
+                        mk.button({
+                            class: 'copy-icon', title: 'Copy',
+                            type: 'button',
+                            _onclick: copyLink,
+                            tabindex: 0,
+                        }, mk.span({ class: 'icon' }) ),
+                        mk.span({}, link)
+                    )
+                );
+            })
+        )
+    ];
+}
+}
+</script>
+<script>/* Boilerplate: script-ref-hints */
+"use strict";
+{
+let refsData = {
+"#EventsW": {"displayText":"workshop","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"workshop","type":"dfn","url":"#EventsW"},
+"#FormalObjection": {"displayText":"formal objection","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"formal objection","type":"dfn","url":"#FormalObjection"},
+"#GeneralChairs": {"displayText":"chair","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chair","type":"dfn","url":"#GeneralChairs"},
+"#GroupsIG": {"displayText":"interest groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"interest groups","type":"dfn","url":"#GroupsIG"},
+"#GroupsWG": {"displayText":"working groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"working groups","type":"dfn","url":"#GroupsWG"},
+"#Member-only": {"displayText":"member-only","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member-only","type":"dfn","url":"#Member-only"},
+"#MemberSubmission": {"displayText":"member submission","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member submission","type":"dfn","url":"#MemberSubmission"},
+"#RecsCR": {"displayText":"candidate recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation","type":"dfn","url":"#RecsCR"},
+"#RecsObs": {"displayText":"obsolete recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"obsolete recommendation","type":"dfn","url":"#RecsObs"},
+"#RecsSup": {"displayText":"superseded recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"superseded recommendation","type":"dfn","url":"#RecsSup"},
+"#RecsW3C": {"displayText":"w3c recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c recommendation","type":"dfn","url":"#RecsW3C"},
+"#RecsWD": {"displayText":"working draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"working draft","type":"dfn","url":"#RecsWD"},
+"#RescindedRec": {"displayText":"rescinded recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rescinded recommendation","type":"dfn","url":"#RescindedRec"},
+"#Team-only": {"displayText":"team-only","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team-only","type":"dfn","url":"#Team-only"},
+"#TeamContact": {"displayText":"staff contact","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"staff contact","type":"dfn","url":"#TeamContact"},
+"#WGNote": {"displayText":"note","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"note","type":"dfn","url":"#WGNote"},
+"#acknowledged": {"displayText":"acknowledged","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"acknowledged","type":"dfn","url":"#acknowledged"},
+"#adequate-implementation": {"displayText":"adequate implementation experience","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"adequate implementation experience","type":"dfn","url":"#adequate-implementation"},
+"#adopted-draft": {"displayText":"adopted draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"adopted draft","type":"dfn","url":"#adopted-draft"},
+"#advisory-board": {"displayText":"ab","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ab","type":"dfn","url":"#advisory-board"},
+"#advisory-committee": {"displayText":"advisory committee","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"advisory committee","type":"dfn","url":"#advisory-committee"},
+"#advisory-committee-appeal": {"displayText":"ac appeal","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ac appeal","type":"dfn","url":"#advisory-committee-appeal"},
+"#advisory-committee-representative": {"displayText":"advisory committee representative","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"advisory committee representative","type":"dfn","url":"#advisory-committee-representative"},
+"#advisory-committee-review": {"displayText":"ac review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ac review","type":"dfn","url":"#advisory-committee-review"},
+"#affirm": {"displayText":"affirm","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"affirm","type":"dfn","url":"#affirm"},
+"#allow-new-features": {"displayText":"allow new features","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"allow new features","type":"dfn","url":"#allow-new-features"},
+"#appeal-vote": {"displayText":"appeal vote","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"appeal vote","type":"dfn","url":"#appeal-vote"},
+"#at-risk": {"displayText":"at risk","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"at risk","type":"dfn","url":"#at-risk"},
+"#bod": {"displayText":"board","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"board","type":"dfn","url":"#bod"},
+"#candidate-addition": {"displayText":"candidate addition","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate addition","type":"dfn","url":"#candidate-addition"},
+"#candidate-amendment": {"displayText":"candidate amendment","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate amendment","type":"dfn","url":"#candidate-amendment"},
+"#candidate-correction": {"displayText":"candidate correction","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate correction","type":"dfn","url":"#candidate-correction"},
+"#candidate-recommendation-draft": {"displayText":"candidate recommendation draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation draft","type":"dfn","url":"#candidate-recommendation-draft"},
+"#candidate-recommendation-review-period": {"displayText":"candidate recommendation review period","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation review period","type":"dfn","url":"#candidate-recommendation-review-period"},
+"#candidate-recommendation-snapshot": {"displayText":"crs","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"crs","type":"dfn","url":"#candidate-recommendation-snapshot"},
+"#candidate-registry": {"displayText":"candidate registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate registry","type":"dfn","url":"#candidate-registry"},
+"#ceo": {"displayText":"ceo","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ceo","type":"dfn","url":"#ceo"},
+"#charter": {"displayText":"charter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter","type":"dfn","url":"#charter"},
+"#charter-draft": {"displayText":"charter draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter draft","type":"dfn","url":"#charter-draft"},
+"#charter-refinement": {"displayText":"charter refinement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter refinement","type":"dfn","url":"#charter-refinement"},
+"#charter-review-notice": {"displayText":"charter review notice","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter review notice","type":"dfn","url":"#charter-review-notice"},
+"#chartered-group": {"displayText":"chartered groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chartered groups","type":"dfn","url":"#chartered-group"},
+"#chartering-facilitator": {"displayText":"chartering facilitator","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chartering facilitator","type":"dfn","url":"#chartering-facilitator"},
+"#convened": {"displayText":"convened","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"convened","type":"dfn","url":"#convened"},
+"#council-report": {"displayText":"council report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council report","type":"dfn","url":"#council-report"},
+"#council-staff-contact": {"displayText":"council staff contact","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council staff contact","type":"dfn","url":"#council-staff-contact"},
+"#custodian": {"displayText":"custodian","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"custodian","type":"dfn","url":"#custodian"},
+"#def-Consensus": {"displayText":"consensus","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"consensus","type":"dfn","url":"#def-Consensus"},
+"#def-Dissent": {"displayText":"dissent","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"dissent","type":"dfn","url":"#def-Dissent"},
+"#def-Unanimity": {"displayText":"unanimity","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"unanimity","type":"dfn","url":"#def-Unanimity"},
+"#def-w3c-decision": {"displayText":"w3c decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c decision","type":"dfn","url":"#def-w3c-decision"},
+"#dfn-charter-extension": {"displayText":"charter extension","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter extension","type":"dfn","url":"#dfn-charter-extension"},
+"#dfn-wide-review": {"displayText":"wide review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"wide review","type":"dfn","url":"#dfn-wide-review"},
+"#discontinuedREC": {"displayText":"discontinued draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"discontinued draft","type":"dfn","url":"#discontinuedREC"},
+"#dismissed": {"displayText":"dismissal","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"dismissal","type":"dfn","url":"#dismissed"},
+"#editorial-change": {"displayText":"editorial change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"editorial change","type":"dfn","url":"#editorial-change"},
+"#editors-draft": {"displayText":"editor's draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"editor's draft","type":"dfn","url":"#editors-draft"},
+"#elected-group": {"displayText":"elected groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"elected groups","type":"dfn","url":"#elected-group"},
+"#embedded-registry": {"displayText":"embedded registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"embedded registry","type":"dfn","url":"#embedded-registry"},
+"#erratum": {"displayText":"erratum","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"erratum","type":"dfn","url":"#erratum"},
+"#exclusion-draft": {"displayText":"exclusion draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"exclusion draft","type":"dfn","url":"#exclusion-draft"},
+"#exclusion-draft-charter": {"displayText":"exclusion draft charter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"exclusion draft charter","type":"dfn","url":"#exclusion-draft-charter"},
+"#formally-addressed": {"displayText":"formally addressed","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"formally addressed","type":"dfn","url":"#formally-addressed"},
+"#fpwd": {"displayText":"first public working draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"first public working draft","type":"dfn","url":"#fpwd"},
+"#ftf-meeting": {"displayText":"face-to-face meeting","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"face-to-face meeting","type":"dfn","url":"#ftf-meeting"},
+"#fully-addressed": {"displayText":"fully addressed","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"fully addressed","type":"dfn","url":"#fully-addressed"},
+"#good-standing": {"displayText":"good standing","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"good standing","type":"dfn","url":"#good-standing"},
+"#group-decision": {"displayText":"group decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"group decision","type":"dfn","url":"#group-decision"},
+"#invited-expert-in-a-working-group": {"displayText":"invited expert in a working group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"invited expert in a working group","type":"dfn","url":"#invited-expert-in-a-working-group"},
+"#last-call-for-review-of-proposed-additions": {"displayText":"last call for review of proposed additions","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed additions","type":"dfn","url":"#last-call-for-review-of-proposed-additions"},
+"#last-call-for-review-of-proposed-corrections": {"displayText":"last call for review of proposed corrections","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed corrections","type":"dfn","url":"#last-call-for-review-of-proposed-corrections"},
+"#last-call-for-review-of-proposed-corrections-and-additions": {"displayText":"last call for review of proposed corrections and additions","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed corrections and additions","type":"dfn","url":"#last-call-for-review-of-proposed-corrections-and-additions"},
+"#last-call-review": {"displayText":"last call for review of proposed amendments","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed amendments","type":"dfn","url":"#last-call-review"},
+"#member-association": {"displayText":"member association","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member association","type":"dfn","url":"#member-association"},
+"#member-representative-in-an-interest-group": {"displayText":"member representative in an interest group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member representative in an interest group","type":"dfn","url":"#member-representative-in-an-interest-group"},
+"#minor-changes": {"displayText":"minor changes","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minor changes","type":"dfn","url":"#minor-changes"},
+"#minority-opinion": {"displayText":"minority opinion","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minority opinion","type":"dfn","url":"#minority-opinion"},
+"#minutes": {"displayText":"minutes","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minutes","type":"dfn","url":"#minutes"},
+"#note-draft": {"displayText":"note draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"note draft","type":"dfn","url":"#note-draft"},
+"#overrule": {"displayText":"overrule","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"overrule","type":"dfn","url":"#overrule"},
+"#overturn": {"displayText":"overturn","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"overturn","type":"dfn","url":"#overturn"},
+"#participant": {"displayText":"participant","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"participant","type":"dfn","url":"#participant"},
+"#patent-review-drafts": {"displayText":"patent review drafts","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"patent review drafts","type":"dfn","url":"#patent-review-drafts"},
+"#primary-affiliation": {"displayText":"primary affiliation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"primary affiliation","type":"dfn","url":"#primary-affiliation"},
+"#proposed-amendments": {"displayText":"proposed amendments","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"proposed amendments","type":"dfn","url":"#proposed-amendments"},
+"#publishing": {"displayText":"publish","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"publish","type":"dfn","url":"#publishing"},
+"#registry": {"displayText":"registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry","type":"dfn","url":"#registry"},
+"#registry-change": {"displayText":"registry change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry change","type":"dfn","url":"#registry-change"},
+"#registry-data": {"displayText":"registry data","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry data","type":"dfn","url":"#registry-data"},
+"#registry-data-report": {"displayText":"registry data report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry data report","type":"dfn","url":"#registry-data-report"},
+"#registry-definition": {"displayText":"registry definition","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry definition","type":"dfn","url":"#registry-definition"},
+"#registry-entry": {"displayText":"registry entry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry entry","type":"dfn","url":"#registry-entry"},
+"#registry-report": {"displayText":"registry report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry report","type":"dfn","url":"#registry-report"},
+"#registry-table": {"displayText":"registry table","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry table","type":"dfn","url":"#registry-table"},
+"#registry-track": {"displayText":"registry track","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry track","type":"dfn","url":"#registry-track"},
+"#rejected": {"displayText":"rejected","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rejected","type":"dfn","url":"#rejected"},
+"#related-member": {"displayText":"related member","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"related member","type":"dfn","url":"#related-member"},
+"#renounce": {"displayText":"renunciation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"renunciation","type":"dfn","url":"#renounce"},
+"#rescinded-candidate-recommendation": {"displayText":"rescinded candidate recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rescinded candidate recommendation","type":"dfn","url":"#rescinded-candidate-recommendation"},
+"#reviewform": {"displayText":"call for review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"call for review","type":"dfn","url":"#reviewform"},
+"#statement": {"displayText":"w3c statement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c statement","type":"dfn","url":"#statement"},
+"#submission-appeals": {"displayText":"submission appeals","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"submission appeals","type":"dfn","url":"#submission-appeals"},
+"#submitter": {"displayText":"submitter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"submitter","type":"dfn","url":"#submitter"},
+"#subsidiary": {"displayText":"subsidiary","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"subsidiary","type":"dfn","url":"#subsidiary"},
+"#substantive-change": {"displayText":"substantive change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"substantive change","type":"dfn","url":"#substantive-change"},
+"#team": {"displayText":"team","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team","type":"dfn","url":"#team"},
+"#team-correction": {"displayText":"team correction","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team correction","type":"dfn","url":"#team-correction"},
+"#team-decision": {"displayText":"team decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team decision","type":"dfn","url":"#team-decision"},
+"#technical-agreement": {"displayText":"technical agreement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"technical agreement","type":"dfn","url":"#technical-agreement"},
+"#technical-architecture-group": {"displayText":"tag","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"tag","type":"dfn","url":"#technical-architecture-group"},
+"#technical-report": {"displayText":"technical report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"technical report","type":"dfn","url":"#technical-report"},
+"#trans-req": {"displayText":"transition requests","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"transition requests","type":"dfn","url":"#trans-req"},
+"#update-requests": {"displayText":"update requests","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"update requests","type":"dfn","url":"#update-requests"},
+"#upheld": {"displayText":"upheld","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"upheld","type":"dfn","url":"#upheld"},
+"#w3c-council": {"displayText":"w3c council","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c council","type":"dfn","url":"#w3c-council"},
+"#w3c-council-chair": {"displayText":"council chair","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council chair","type":"dfn","url":"#w3c-council-chair"},
+"#w3c-group": {"displayText":"w3c group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c group","type":"dfn","url":"#w3c-group"},
+"#w3c-member": {"displayText":"member","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member","type":"dfn","url":"#w3c-member"},
+"#w3c-recommendation-track": {"displayText":"rec track","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rec track","type":"dfn","url":"#w3c-recommendation-track"},
+"#w3c-registry": {"displayText":"w3c registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c registry","type":"dfn","url":"#w3c-registry"},
+"https://www.w3.org/policies/patent-policy/#exclusion-opportunity": {"displayText":"Exclusion Opportunity","export":false,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"exclusion opportunity","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
+"https://www.w3.org/policies/patent-policy/#patent-advisory-group": {"displayText":"Patent Advisory Group","export":true,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"patent advisory group","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
+};
+
+function mkRefHint(link, ref) {
+    const linkText = link.textContent;
+    let dfnTextElements = '';
+    if (ref.displayText.toLowerCase() != linkText.toLowerCase()) {
+        // Give the original term if it's being displayed in a different way.
+        // But allow casing differences, they're insignificant.
+        dfnTextElements =
+            mk.li({},
+                mk.b({}, "Term: "),
+                mk.span({}, ref.displayText)
+            );
+    }
+    const forList = ref.for_;
+    let forListElements;
+    if(forList.length == 0) {
+        forListElements = [];
+    } else if(forList.length == 1) {
+        forListElements = mk.li({},
+            mk.b({}, "For: "),
+            mk.span({}, forList[0]),
+        );
+    } else {
+        forListElements = mk.li({},
+            mk.b({}, "For: "),
+            mk.ul({},
+                ...forList.map(forItem =>
+                    mk.li({},
+                        mk.span({}, forItem)
+                    ),
+                ),
+            ),
+        );
+    }
+    const url = ref.url;
+    const safeUrl = encodeURIComponent(url);
+    const hintPanel = mk.aside({
+        class: "ref-hint",
+        id: `ref-hint-for-${safeUrl}`,
+        "data-for": url,
+        "aria-labelled-by": `ref-hint-for-${safeUrl}`,
+    },
+        mk.ul({},
+            dfnTextElements,
+            mk.li({},
+                mk.b({}, "URL: "),
+                mk.a({ href: url, class: "ref" }, url),
+            ),
+            mk.li({},
+                mk.b({}, "Type: "),
+                mk.span({}, `${ref.type}`),
+            ),
+            mk.li({},
+                mk.b({}, "Spec: "),
+                mk.span({}, `${ref.spec ? ref.spec : ''}`),
+            ),
+            forListElements
+        ),
+    );
+    hintPanel.forLink = link;
+    setupRefHintEventListeners(link, hintPanel);
+    return hintPanel;
+}
+
+function hideAllRefHints() {
+    queryAll(".ref-hint").forEach(el=>hideRefHint(el));
+}
+
+function hideRefHint(refHint) {
+    const link = refHint.forLink;
+    link.setAttribute("aria-expanded", "false");
+    if(refHint.teardownEventListeners) {
+        refHint.teardownEventListeners();
+    }
+    refHint.remove();
+}
+
+function showRefHint(link) {
+    if(link.classList.contains("dfn-link")) return;
+    const url = link.getAttribute("href");
+    const refHintKey = link.getAttribute("data-refhint-key");
+    let key = url;
+    if(refHintKey) {
+        key = refHintKey + "_" + url;
+    }
+    const ref = refsData[key];
+    if(!ref) return;
+
+    hideAllRefHints(); // Only display one at this time.
+
+    const refHint = mkRefHint(link, ref);
+    append(document.body, refHint);
+    link.setAttribute("aria-expanded", "true");
+    positionRefHint(refHint);
+}
+
+function setupRefHintEventListeners(link, refHint) {
+    if (refHint.teardownEventListeners) return;
+    // Add event handlers to hide the refHint after the user moves away
+    // from both the link and refHint, if not hovering either within one second.
+    let timeout = null;
+    const startHidingRefHint = (event) => {
+        if (timeout) {
+            clearTimeout(timeout);
+        }
+        timeout = setTimeout(() => {
+            hideRefHint(refHint);
+        }, 1000);
+    }
+    const resetHidingRefHint = (event) => {
+        if (timeout) clearTimeout(timeout);
+        timeout = null;
+    };
+    link.addEventListener("mouseleave", startHidingRefHint);
+    link.addEventListener("mouseenter", resetHidingRefHint);
+    link.addEventListener("blur", startHidingRefHint);
+    link.addEventListener("focus", resetHidingRefHint);
+    refHint.addEventListener("mouseleave", startHidingRefHint);
+    refHint.addEventListener("mouseenter", resetHidingRefHint);
+    refHint.addEventListener("blur", startHidingRefHint);
+    refHint.addEventListener("focus", resetHidingRefHint);
+
+    refHint.teardownEventListeners = () => {
+        // remove event listeners
+        resetHidingRefHint();
+        link.removeEventListener("mouseleave", startHidingRefHint);
+        link.removeEventListener("mouseenter", resetHidingRefHint);
+        link.removeEventListener("blur", startHidingRefHint);
+        link.removeEventListener("focus", resetHidingRefHint);
+        refHint.removeEventListener("mouseleave", startHidingRefHint);
+        refHint.removeEventListener("mouseenter", resetHidingRefHint);
+        refHint.removeEventListener("blur", startHidingRefHint);
+        refHint.removeEventListener("focus", resetHidingRefHint);
+    };
+}
+
+function positionRefHint(refHint) {
+    const link = refHint.forLink;
+    const linkPos = getBounds(link);
+    refHint.style.top = linkPos.bottom + "px";
+    refHint.style.left = linkPos.left + "px";
+
+    const panelPos = refHint.getBoundingClientRect();
+    const panelMargin = 8;
+    const maxRight = document.body.parentNode.clientWidth - panelMargin;
+    if (panelPos.right > maxRight) {
+        const overflowAmount = panelPos.right - maxRight;
+        const newLeft = Math.max(panelMargin, linkPos.left - overflowAmount);
+        refHint.style.left = newLeft + "px";
+    }
+}
+
+// TODO: shared util
+// Returns the root-level absolute position {left and top} of element.
+function getBounds(el, relativeTo=document.body) {
+    const relativeRect = relativeTo.getBoundingClientRect();
+    const elRect = el.getBoundingClientRect();
+    const top = elRect.top - relativeRect.top;
+    const left = elRect.left - relativeRect.left;
+    return {
+        top,
+        left,
+        bottom: top + elRect.height,
+        right: left + elRect.width,
+    }
+}
+
+function showRefHintListener(e) {
+    // If the target isn't in a link (or is a link),
+    // just ignore it.
+    let link = e.target.closest("a");
+    if(!link) return;
+
+    // If the target is in a ref-hint panel
+    // (aka a link in the already-open one),
+    // also just ignore it.
+    if(link.closest(".ref-hint")) return;
+
+    // Otherwise, show the panel for the link.
+    showRefHint(link);
+}
+
+function hideAllHintsListener(e) {
+    // If the click is inside a ref-hint panel, ignore it.
+    if(e.target.closest(".ref-hint")) return;
+    // Otherwise, close all the current panels.
+    hideAllRefHints();
+}
+
+document.addEventListener("DOMContentLoaded", () => {
+    document.body.addEventListener("mousedown", showRefHintListener);
+    document.body.addEventListener("focus", showRefHintListener);
+
+    document.body.addEventListener("click", hideAllHintsListener);
+});
+
+window.addEventListener("resize", () => {
+    // Hide any open ref hint.
+    hideAllRefHints();
+});
+}
+</script>

From ab0db0477564f3d7576f76490b094b602341d338 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 23 Jul 2025 22:16:14 +0200
Subject: [PATCH 234/237] Fix typo

---
 index.bs                  | 2 +-
 snapshots/2025-07-31.html | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 80c954d4..c7971ce6 100644
--- a/index.bs
+++ b/index.bs
@@ -3458,7 +3458,7 @@ The W3C Recommendation Track</h3>
 	and if there is support from its Membership,
 	W3C publishes it as a <a href="#RecsW3C">Recommendation</a>.
 
-	In summary, the main steps of <dfn lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track">W3C Recommendation Track</dfn> are:
+	In summary, the main steps of the <dfn lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track">W3C Recommendation Track</dfn> are:
 
 	<ol>
 		<li>Publication of the [=First Public Working Draft=].
diff --git a/snapshots/2025-07-31.html b/snapshots/2025-07-31.html
index 8aaa0705..236b8e76 100644
--- a/snapshots/2025-07-31.html
+++ b/snapshots/2025-07-31.html
@@ -3294,7 +3294,7 @@ <h3 class="heading settled" data-level="6.3" id="rec-track"><span class="secno">
 	the Advisory Committee reviews the mature technical report,
 	and if there is support from its Membership,
 	W3C publishes it as a <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑥">Recommendation</a>.</p>
-    <p>In summary, the main steps of <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track" data-noexport id="w3c-recommendation-track">W3C Recommendation Track</dfn> are:</p>
+    <p>In summary, the main steps of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track" data-noexport id="w3c-recommendation-track">W3C Recommendation Track</dfn> are:</p>
     <ol>
      <li>Publication of the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd①">First Public Working Draft</a>. 
      <li>Publication of zero or more revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD②">Working Drafts</a>. 

From a9474ef05e75abcdb22e436e5e6660ffc4266033 Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 31 Jul 2025 12:49:52 +0200
Subject: [PATCH 235/237] Remove auto generated redundant conformance section

---
 index.bs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/index.bs b/index.bs
index c7971ce6..b71e146c 100644
--- a/index.bs
+++ b/index.bs
@@ -60,6 +60,7 @@ 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>
 

From b7535396bf07be9dfbcf3086c7b89eac42e4313c Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Thu, 31 Jul 2025 17:13:28 +0200
Subject: [PATCH 236/237] Updated Snapshot

---
 snapshots/2025-07-31.html |    2 +-
 snapshots/2025-08-18.html | 6472 +++++++++++++++++++++++++++++++++++++
 2 files changed, 6473 insertions(+), 1 deletion(-)
 create mode 100644 snapshots/2025-08-18.html

diff --git a/snapshots/2025-07-31.html b/snapshots/2025-07-31.html
index 236b8e76..6ed1011a 100644
--- a/snapshots/2025-07-31.html
+++ b/snapshots/2025-07-31.html
@@ -619,7 +619,7 @@ <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
     <div data-fill-with="spec-metadata">
      <dl>
       <dt>This version:
-      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/snapshots/2025-06">https://www.w3.org/policies/process/drafts/snapshots/2025-07-31</a>
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/snapshots/2025-07-31">https://www.w3.org/policies/process/drafts/snapshots/2025-07-31</a>
       <dt>Editor’s Draft:
       <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/</a>
       <dt>Latest published version:
diff --git a/snapshots/2025-08-18.html b/snapshots/2025-08-18.html
new file mode 100644
index 00000000..85cc8b15
--- /dev/null
+++ b/snapshots/2025-08-18.html
@@ -0,0 +1,6472 @@
+<!doctype html><html lang="en">
+ <head>
+  <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
+  <meta content="width=device-width, initial-scale=1, shrink-to-fit=no" name="viewport">
+  <title>W3C Process Document</title>
+  <meta content="CG-DRAFT" name="w3c-status">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/cg-draft" rel="stylesheet">
+  <meta content="Bikeshed version b25686b9f, updated Fri Mar 14 14:15:20 2025 -0700" name="generator">
+  <link href="https://www.w3.org/policies/process/" rel="canonical">
+  <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
+  <meta content="dbe17f75f1b91075d85515deb0df718cdb74c7ce" name="revision">
+  <meta content="dark light" name="color-scheme">
+  <link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
+<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>
+<style>/* Boilerplate: style-autolinks */
+.css.css, .property.property, .descriptor.descriptor {
+    color: var(--a-normal-text);
+    font-size: inherit;
+    font-family: inherit;
+}
+.css::before, .property::before, .descriptor::before {
+    content: "‘";
+}
+.css::after, .property::after, .descriptor::after {
+    content: "’";
+}
+.property, .descriptor {
+    /* Don't wrap property and descriptor names */
+    white-space: nowrap;
+}
+.type { /* CSS value <type> */
+    font-style: italic;
+}
+pre .property::before, pre .property::after {
+    content: "";
+}
+[data-link-type="property"]::before,
+[data-link-type="propdesc"]::before,
+[data-link-type="descriptor"]::before,
+[data-link-type="value"]::before,
+[data-link-type="function"]::before,
+[data-link-type="at-rule"]::before,
+[data-link-type="selector"]::before,
+[data-link-type="maybe"]::before {
+    content: "‘";
+}
+[data-link-type="property"]::after,
+[data-link-type="propdesc"]::after,
+[data-link-type="descriptor"]::after,
+[data-link-type="value"]::after,
+[data-link-type="function"]::after,
+[data-link-type="at-rule"]::after,
+[data-link-type="selector"]::after,
+[data-link-type="maybe"]::after {
+    content: "’";
+}
+
+[data-link-type].production::before,
+[data-link-type].production::after,
+.prod [data-link-type]::before,
+.prod [data-link-type]::after {
+    content: "";
+}
+
+[data-link-type=element],
+[data-link-type=element-attr] {
+    font-family: Menlo, Consolas, "DejaVu Sans Mono", monospace;
+    font-size: .9em;
+}
+[data-link-type=element]::before { content: "<" }
+[data-link-type=element]::after  { content: ">" }
+
+[data-link-type=biblio] {
+    white-space: pre;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --selflink-text: black;
+        --selflink-bg: silver;
+        --selflink-hover-text: white;
+    }
+}
+</style>
+<style>/* Boilerplate: style-colors */
+/* Any --*-text not paired with a --*-bg is assumed to have a transparent bg */
+:root {
+    color-scheme: light dark;
+
+    --text: black;
+    --bg: white;
+
+    --unofficial-watermark: url(https://www.w3.org/StyleSheets/TR/2016/logos/UD-watermark);
+
+    --logo-bg: #1a5e9a;
+    --logo-active-bg: #c00;
+    --logo-text: white;
+
+    --tocnav-normal-text: #707070;
+    --tocnav-normal-bg: var(--bg);
+    --tocnav-hover-text: var(--tocnav-normal-text);
+    --tocnav-hover-bg: #f8f8f8;
+    --tocnav-active-text: #c00;
+    --tocnav-active-bg: var(--tocnav-normal-bg);
+
+    --tocsidebar-text: var(--text);
+    --tocsidebar-bg: #f7f8f9;
+    --tocsidebar-shadow: rgba(0,0,0,.1);
+    --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+    --toclink-text: var(--text);
+    --toclink-underline: #3980b5;
+    --toclink-visited-text: var(--toclink-text);
+    --toclink-visited-underline: #054572;
+
+    --heading-text: #005a9c;
+
+    --hr-text: var(--text);
+
+    --algo-border: #def;
+
+    --del-text: red;
+    --del-bg: transparent;
+    --ins-text: #080;
+    --ins-bg: transparent;
+
+    --a-normal-text: #034575;
+    --a-normal-underline: #bbb;
+    --a-visited-text: var(--a-normal-text);
+    --a-visited-underline: #707070;
+    --a-hover-bg: rgba(75%, 75%, 75%, .25);
+    --a-active-text: #c00;
+    --a-active-underline: #c00;
+
+    --blockquote-border: silver;
+    --blockquote-bg: transparent;
+    --blockquote-text: currentcolor;
+
+    --issue-border: #e05252;
+    --issue-bg: #fbe9e9;
+    --issue-text: var(--text);
+    --issueheading-text: #831616;
+
+    --example-border: #e0cb52;
+    --example-bg: #fcfaee;
+    --example-text: var(--text);
+    --exampleheading-text: #574b0f;
+
+    --note-border: #52e052;
+    --note-bg: #e9fbe9;
+    --note-text: var(--text);
+    --noteheading-text: hsl(120, 70%, 30%);
+    --notesummary-underline: silver;
+
+    --assertion-border: #aaa;
+    --assertion-bg: #eee;
+    --assertion-text: black;
+
+    --advisement-border: orange;
+    --advisement-bg: #fec;
+    --advisement-text: var(--text);
+    --advisementheading-text: #b35f00;
+
+    --warning-border: red;
+    --warning-bg: hsla(40,100%,50%,0.95);
+    --warning-text: var(--text);
+
+    --amendment-border: #330099;
+    --amendment-bg: #F5F0FF;
+    --amendment-text: var(--text);
+    --amendmentheading-text: #220066;
+
+    --def-border: #8ccbf2;
+    --def-bg: #def;
+    --def-text: var(--text);
+    --defrow-border: #bbd7e9;
+
+    --datacell-border: silver;
+
+    --indexinfo-text: #707070;
+
+    --indextable-hover-text: black;
+    --indextable-hover-bg: #f7f8f9;
+
+    --outdatedspec-bg: rgba(0, 0, 0, .5);
+    --outdatedspec-text: black;
+    --outdated-bg: maroon;
+    --outdated-text: white;
+    --outdated-shadow: red;
+
+    --editedrec-bg: darkorange;
+}
+
+@media (prefers-color-scheme: dark) {
+    :root {
+        --text: #ddd;
+        --bg: black;
+
+        --unofficial-watermark: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='400' height='400'%3E%3Cg fill='%23100808' transform='translate(200 200) rotate(-45) translate(-200 -200)' stroke='%23100808' stroke-width='3'%3E%3Ctext x='50%25' y='220' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EUNOFFICIAL%3C/text%3E%3Ctext x='50%25' y='305' style='font: bold 70px sans-serif; text-anchor: middle; letter-spacing: 6px;'%3EDRAFT%3C/text%3E%3C/g%3E%3C/svg%3E");
+
+        --logo-bg: #1a5e9a;
+        --logo-active-bg: #c00;
+        --logo-text: white;
+
+        --tocnav-normal-text: #999;
+        --tocnav-normal-bg: var(--bg);
+        --tocnav-hover-text: var(--tocnav-normal-text);
+        --tocnav-hover-bg: #080808;
+        --tocnav-active-text: #f44;
+        --tocnav-active-bg: var(--tocnav-normal-bg);
+
+        --tocsidebar-text: var(--text);
+        --tocsidebar-bg: #080808;
+        --tocsidebar-shadow: rgba(255,255,255,.1);
+        --tocsidebar-heading-text: hsla(203,20%,40%,.7);
+
+        --toclink-text: var(--text);
+        --toclink-underline: #6af;
+        --toclink-visited-text: var(--toclink-text);
+        --toclink-visited-underline: #054572;
+
+        --heading-text: #8af;
+
+        --hr-text: var(--text);
+
+        --algo-border: #456;
+
+        --del-text: #f44;
+        --del-bg: transparent;
+        --ins-text: #4a4;
+        --ins-bg: transparent;
+
+        --a-normal-text: #6af;
+        --a-normal-underline: #555;
+        --a-visited-text: var(--a-normal-text);
+        --a-visited-underline: var(--a-normal-underline);
+        --a-hover-bg: rgba(25%, 25%, 25%, .2);
+        --a-active-text: #f44;
+        --a-active-underline: var(--a-active-text);
+
+        --borderedblock-bg: rgba(255, 255, 255, .05);
+
+        --blockquote-border: silver;
+        --blockquote-bg: var(--borderedblock-bg);
+        --blockquote-text: currentcolor;
+
+        --issue-border: #e05252;
+        --issue-bg: var(--borderedblock-bg);
+        --issue-text: var(--text);
+        --issueheading-text: hsl(0deg, 70%, 70%);
+
+        --example-border: hsl(50deg, 90%, 60%);
+        --example-bg: var(--borderedblock-bg);
+        --example-text: var(--text);
+        --exampleheading-text: hsl(50deg, 70%, 70%);
+
+        --note-border: hsl(120deg, 100%, 35%);
+        --note-bg: var(--borderedblock-bg);
+        --note-text: var(--text);
+        --noteheading-text: hsl(120, 70%, 70%);
+        --notesummary-underline: silver;
+
+        --assertion-border: #444;
+        --assertion-bg: var(--borderedblock-bg);
+        --assertion-text: var(--text);
+
+        --advisement-border: orange;
+        --advisement-bg: #222218;
+        --advisement-text: var(--text);
+        --advisementheading-text: #f84;
+
+        --warning-border: red;
+        --warning-bg: hsla(40,100%,20%,0.95);
+        --warning-text: var(--text);
+
+        --amendment-border: #330099;
+        --amendment-bg: #080010;
+        --amendment-text: var(--text);
+        --amendmentheading-text: #cc00ff;
+
+        --def-border: #8ccbf2;
+        --def-bg: #080818;
+        --def-text: var(--text);
+        --defrow-border: #136;
+
+        --datacell-border: silver;
+
+        --indexinfo-text: #aaa;
+
+        --indextable-hover-text: var(--text);
+        --indextable-hover-bg: #181818;
+
+        --outdatedspec-bg: rgba(255, 255, 255, .5);
+        --outdatedspec-text: black;
+        --outdated-bg: maroon;
+        --outdated-text: white;
+        --outdated-shadow: red;
+
+        --editedrec-bg: darkorange;
+    }
+    /* In case a transparent-bg image doesn't expect to be on a dark bg,
+       which is quite common in practice... */
+    img { background: white; }
+}
+</style>
+<style>/* Boilerplate: style-counters */
+body {
+    counter-reset: example figure issue;
+}
+.issue {
+    counter-increment: issue;
+}
+.issue:not(.no-marker)::before {
+    content: "Issue " counter(issue);
+}
+
+.example {
+    counter-increment: example;
+}
+.example:not(.no-marker)::before {
+    content: "Example " counter(example);
+}
+.invalid.example:not(.no-marker)::before,
+.illegal.example:not(.no-marker)::before {
+    content: "Invalid Example" counter(example);
+}
+
+figcaption {
+    counter-increment: figure;
+}
+figcaption:not(.no-marker)::before {
+    content: "Figure " counter(figure) " ";
+}
+</style>
+<style>/* Boilerplate: style-dfn-panel */
+:root {
+    --dfnpanel-bg: #ddd;
+    --dfnpanel-text: var(--text);
+    --dfnpanel-target-bg: #ffc;
+    --dfnpanel-target-outline: orange;
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --dfnpanel-bg: #222;
+        --dfnpanel-text: var(--text);
+        --dfnpanel-target-bg: #333;
+        --dfnpanel-target-outline: silver;
+    }
+}
+.dfn-panel {
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.75em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--dfnpanel-bg);
+    color: var(--dfnpanel-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+.dfn-panel:not(.on) { display: none; }
+.dfn-panel * { margin: 0; padding: 0; text-indent: 0; }
+.dfn-panel > b { display: block; }
+.dfn-panel a { color: var(--dfnpanel-text); }
+.dfn-panel a:not(:hover) { text-decoration: none !important; border-bottom: none !important; }
+.dfn-panel a:focus {
+    outline: 5px auto Highlight;
+    outline: 5px auto -webkit-focus-ring-color;
+}
+.dfn-panel > b + b { margin-top: 0.25em; }
+.dfn-panel ul { padding: 0 0 0 1em; list-style: none; }
+.dfn-panel li a {
+    max-width: calc(300px - 1.5em - 1em);
+    overflow: hidden;
+    text-overflow: ellipsis;
+}
+
+.dfn-panel.activated {
+    display: inline-block;
+    position: fixed;
+    left: 8px;
+    bottom: 2em;
+    margin: 0 auto;
+    max-width: calc(100vw - 1.5em - .4em - .5em);
+    max-height: 30vh;
+    transition: left 1s ease-out, bottom 1s ease-out;
+}
+
+.dfn-panel .link-item:hover {
+    text-decoration: underline;
+}
+.dfn-panel .link-item .copy-icon {
+    opacity: 0;
+}
+.dfn-panel .link-item:hover .copy-icon,
+.dfn-panel .link-item .copy-icon:focus {
+    opacity: 1;
+}
+
+.dfn-panel .copy-icon {
+    display: inline-block;
+    margin-right: 0.5em;
+    width: 0.85em;
+    height: 1em;
+    border-radius: 3px;
+    background-color: #ccc;
+    cursor: pointer;
+}
+
+.dfn-panel .copy-icon .icon {
+    width: 100%;
+    height: 100%;
+    background-color: #fff;
+    display: flex;
+    justify-content: center;
+    align-items: center;
+    position: relative;
+}
+
+.dfn-panel .copy-icon .icon::before {
+    content: "";
+    position: absolute;
+    top: 0;
+    left: 0;
+    width: 100%;
+    height: 100%;
+    border: 1px solid black;
+    background-color: #ccc;
+    opacity: 0.25;
+    transform: translate(3px, -3px);
+}
+
+.dfn-panel .copy-icon:active .icon::before {
+    opacity: 1;
+}
+
+.dfn-paneled[role="button"] { cursor: help; }
+
+.highlighted {
+    animation: target-fade 3s;
+}
+
+@keyframes target-fade {
+    from {
+        background-color: var(--dfnpanel-target-bg);
+        outline: 5px solid var(--dfnpanel-target-outline);
+    }
+    to {
+        color: var(--a-normal-text);
+        background-color: transparent;
+        outline: transparent;
+    }
+}
+</style>
+<style>/* Boilerplate: style-issues */
+a[href].issue-return {
+    float: right;
+    float: inline-end;
+    color: var(--issueheading-text);
+    font-weight: bold;
+    text-decoration: none;
+}
+</style>
+<style>/* Boilerplate: style-md-lists */
+/* This is a weird hack for me not yet following the commonmark spec
+   regarding paragraph and lists. */
+[data-md] > :first-child {
+    margin-top: 0;
+}
+[data-md] > :last-child {
+    margin-bottom: 0;
+}
+</style>
+<style>/* Boilerplate: style-ref-hints */
+:root {
+    --ref-hint-bg: #ddd;
+    --ref-hint-text: var(--text);
+}
+@media (prefers-color-scheme: dark) {
+    :root {
+        --ref-hint-bg: #222;
+        --ref-hint-text: var(--text);
+    }
+}
+
+.ref-hint {
+    display: inline-block;
+    position: absolute;
+    z-index: 35;
+    width: 20em;
+    width: 300px;
+    height: auto;
+    max-height: 500px;
+    overflow: auto;
+    padding: 0.5em 0.5em;
+    font: small Helvetica Neue, sans-serif, Droid Sans Fallback;
+    background: var(--ref-hint-bg);
+    color: var(--ref-hint-text);
+    border: outset 0.2em;
+    white-space: normal; /* in case it's moved into a pre */
+}
+
+.ref-hint * { margin: 0; padding: 0; text-indent: 0; }
+
+.ref-hint ul { padding: 0 0 0 1em; list-style: none; }
+</style>
+<style>/* Boilerplate: style-selflinks */
+:root {
+    --selflink-text: white;
+    --selflink-bg: gray;
+    --selflink-hover-text: black;
+}
+.heading, .issue, .note, .example, li, dt {
+    position: relative;
+}
+a.self-link {
+    position: absolute;
+    top: 0;
+    left: calc(-1 * (3.5rem - 26px));
+    width: calc(3.5rem - 26px);
+    height: 2em;
+    text-align: center;
+    border: none;
+    transition: opacity .2s;
+    opacity: .5;
+}
+a.self-link:hover {
+    opacity: 1;
+}
+.heading > a.self-link {
+    font-size: 83%;
+}
+.example > a.self-link,
+.note > a.self-link,
+.issue > a.self-link {
+    /* These blocks are overflow:auto, so positioning outside
+       doesn't work. */
+    left: auto;
+    right: 0;
+}
+li > a.self-link {
+    left: calc(-1 * (3.5rem - 26px) - 2em);
+}
+dfn > a.self-link {
+    top: auto;
+    left: auto;
+    opacity: 0;
+    width: 1.5em;
+    height: 1.5em;
+    background: var(--selflink-bg);
+    color: var(--selflink-text);
+    font-style: normal;
+    transition: opacity .2s, background-color .2s, color .2s;
+}
+dfn:hover > a.self-link {
+    opacity: 1;
+}
+dfn > a.self-link:hover {
+    color: var(--selflink-hover-text);
+}
+
+a.self-link::before            { content: "¶"; }
+.heading > a.self-link::before { content: "§"; }
+dfn > a.self-link::before      { content: "#"; }
+</style>
+ <body class="h-entry">
+  <div class="head">
+   <p data-fill-with="logo"><a class="logo" href="https://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a> </p>
+   <h1 class="p-name no-ref" id="title">W3C Process Document</h1>
+   <p id="w3c-state"><a href="https://www.w3.org/standards/types/#CG-DRAFT">Draft Community Group Report</a>, <time class="dt-updated" datetime="2025-08-18">18 August 2025</time></p>
+   <details open>
+    <summary>More details about this document</summary>
+    <div data-fill-with="spec-metadata">
+     <dl>
+      <dt>This version:
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/snapshots/2025-08-18">https://www.w3.org/policies/process/drafts/snapshots/2025-08-18</a>
+      <dt>Editor’s Draft:
+      <dd><a class="u-url" href="https://www.w3.org/policies/process/drafts/">https://www.w3.org/policies/process/drafts/</a>
+      <dt>Latest published version:
+      <dd><a href="https://www.w3.org/policies/process/">https://www.w3.org/policies/process/</a>
+      <dt>Previous Versions:
+      <dd><a href="https://www.w3.org/policies/process/20231103/" rel="prev">https://www.w3.org/policies/process/20231103/</a>
+      <dt>Feedback:
+      <dd><a href="https://github.com/w3c/process/issues/">Github (preferred)</a>
+      <dd><a href="https://lists.w3.org/Archives/Public/public-w3process/">Public mailing list</a>
+      <dd><a href="https://lists.w3.org/Archives/Member/process-issues">Member-only mailing list</a>
+      <dt class="editor">Editors:
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://fantasai.inkedblade.net/contact">Elika J. Etemad / fantasai</a> (<span class="p-org org">Apple</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://florian.rivoal.net/">Florian Rivoal</a> (<span class="p-org org">Invited Expert</span>)
+      <dt class="editor">Former Editors:
+      <dd class="editor p-author h-card vcard"><span class="p-name fn">Natasha Rooney</span> (<span class="p-org org">Invited Expert</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://yandex.com">Charles McCathie Nevile</a> (<span class="p-org org">Yandex</span>)
+      <dd class="editor p-author h-card vcard"><a class="p-name fn u-url url" href="https://www.w3.org/">Ian Jacobs</a> (<span class="p-org org">W3C</span>)
+     </dl>
+    </div>
+   </details>
+   <div data-fill-with="warning"></div>
+   <p class="copyright" data-fill-with="copyright"><a href="https://www.w3.org/policies/#copyright">Copyright</a> © 2025 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/policies/#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/policies/#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/copyright/software-license/" rel="license" title="W3C Software and Document License">permissive document license</a> rules apply. </p>
+   <hr title="Separator for header">
+  </div>
+  <div class="p-summary" data-fill-with="abstract">
+   <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="content">Abstract</span></h2>
+   <p>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.</p>
+   <p>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>.</p>
+  </div>
+  <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content">Status of this document</span></h2>
+  <div data-fill-with="status">
+   <p> W3C, including all existing chartered groups,
+	follows the <a href="https://www.w3.org/policies/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
+	working within the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a> (which anyone can join).
+	This is the 18 August 2025 Draft Community Group Report for the proposed next version of the W3C Process Document. </p>
+   <p>This document,
+having completed Advisory Committee Review,
+is proposed to be the next version of the W3C Process
+after the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
+How it is adopted is detailed in <a href="https://www.w3.org/policies/process/#GAProcess">Section 11 Process Changes</a>.</p>
+   <p> A <a href="#changes">history of substantial changes</a> from previous versions of the Process Document is provided. </p>
+  </div>
+  <div data-fill-with="at-risk"></div>
+  <nav data-fill-with="table-of-contents" id="toc">
+   <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
+   <ol class="toc" role="directory">
+    <li><a href="#Intro"><span class="secno">1</span> <span class="content"> Introduction</span></a>
+    <li>
+     <a href="#Organization"><span class="secno">2</span> <span class="content"> Members and the Team</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Members"><span class="secno">2.1</span> <span class="content"> Members</span></a>
+       <ol class="toc">
+        <li><a href="#MemberBenefits"><span class="secno">2.1.1</span> <span class="content"> Rights of Members</span></a>
+        <li>
+         <a href="#RelatedAndAssociatedMembers"><span class="secno">2.1.2</span> <span class="content"> Member Associations and Related Members</span></a>
+         <ol class="toc">
+          <li><a href="#MemberAssoc"><span class="secno">2.1.2.1</span> <span class="content"> Membership Associations</span></a>
+          <li><a href="#MemberRelated"><span class="secno">2.1.2.2</span> <span class="content"> Related Members</span></a>
+         </ol>
+        <li><a href="#standing"><span class="secno">2.1.3</span> <span class="content"> Good Standing</span></a>
+       </ol>
+      <li><a href="#Team"><span class="secno">2.2</span> <span class="content"> The W3C Team</span></a>
+     </ol>
+    <li>
+     <a href="#groups"><span class="secno">3</span> <span class="content"> Groups and Participation</span></a>
+     <ol class="toc">
+      <li>
+       <a href="#Policies"><span class="secno">3.1</span> <span class="content"> Policies for Participation in W3C Groups</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#ParticipationCriteria"><span class="secno">3.1.1</span> <span class="content"> Individual Participation Criteria</span></a>
+         <ol class="toc">
+          <li><a href="#discipline"><span class="secno">3.1.1.1</span> <span class="content"> Expectations and Discipline</span></a>
+          <li><a href="#coi"><span class="secno">3.1.1.2</span> <span class="content"> Conflict of Interest Policy</span></a>
+          <li><a href="#member-rep"><span class="secno">3.1.1.3</span> <span class="content"> Individuals Representing a Member Organization</span></a>
+         </ol>
+        <li>
+         <a href="#GeneralMeetings"><span class="secno">3.1.2</span> <span class="content"> Meetings</span></a>
+         <ol class="toc">
+          <li><a href="#meeting-schedules"><span class="secno">3.1.2.1</span> <span class="content"> Meeting Scheduling and Announcements</span></a>
+          <li><a href="#meeting-minutes"><span class="secno">3.1.2.2</span> <span class="content"> Meeting Minutes</span></a>
+          <li><a href="#meeting-recording"><span class="secno">3.1.2.3</span> <span class="content"> Meeting Recordings and Transcripts</span></a>
+         </ol>
+        <li><a href="#tooling"><span class="secno">3.1.3</span> <span class="content"> Tooling and Archiving for Discussions and Publications</span></a>
+        <li><a href="#resignation"><span class="secno">3.1.4</span> <span class="content"> Resignation from a Group</span></a>
+       </ol>
+      <li>
+       <a href="#AC"><span class="secno">3.2</span> <span class="content"> The Advisory Committee (AC)</span></a>
+       <ol class="toc">
+        <li><a href="#ac-role"><span class="secno">3.2.1</span> <span class="content"> Role of the Advisory Committee</span></a>
+        <li><a href="#ac-participation"><span class="secno">3.2.2</span> <span class="content"> Participation in the Advisory Committee</span></a>
+        <li><a href="#ACCommunication"><span class="secno">3.2.3</span> <span class="content"> Advisory Committee Mailing Lists</span></a>
+        <li><a href="#ACMeetings"><span class="secno">3.2.4</span> <span class="content"> Advisory Committee Meetings</span></a>
+       </ol>
+      <li>
+       <a href="#elected-groups"><span class="secno">3.3</span> <span class="content"> Elected Groups: The AB and the TAG</span></a>
+       <ol class="toc">
+        <li>
+         <a href="#AB"><span class="secno">3.3.1</span> <span class="content"> Advisory Board (AB)</span></a>
+         <ol class="toc">
+          <li><a href="#ab-role"><span class="secno">3.3.1.1</span> <span class="content"> Role of the Advisory Board</span></a>
+          <li><a href="#ABParticipation"><span class="secno">3.3.1.2</span> <span class="content"> Composition of the Advisory Board</span></a>
+          <li><a href="#ab-comm"><span class="secno">3.3.1.3</span> <span class="content"> Communications of the Advisory Board</span></a>
+          <li><a href="#ab-bod-liaison"><span class="secno">3.3.1.4</span> <span class="content"> Liaisons between the Advisory Board and the Board of Directors</span></a>
+         </ol>
+        <li>
+         <a href="#TAG"><span class="secno">3.3.2</span> <span class="content"> Technical Architecture Group (TAG)</span></a>
+         <ol class="toc">
+          <li><a href="#tag-role"><span class="secno">3.3.2.1</span> <span class="content"> Role of the Technical Architecture Group</span></a>
+          <li><a href="#tag-participation"><span class="secno">3.3.2.2</span> <span class="content"> Composition of the Technical Architecture Group</span></a>
+          <li><a href="#tag-comm"><span class="secno">3.3.2.3</span> <span class="content"> Communications of the Technical Architecture Group</span></a>
+         </ol>
+        <li>
+         <a href="#AB-TAG-participation"><span class="secno">3.3.3</span> <span class="content"> Participation in Elected Groups</span></a>
+         <ol class="toc">
+          <li><a href="#elected-expectations"><span class="secno">3.3.3.1</span> <span class="content"> Expectations for Elected Groups Participants</span></a>
+          <li><a href="#AB-TAG-constraints"><span class="secno">3.3.3.2</span> <span class="content"> Elected Groups Participation Constraints</span></a>
+          <li><a href="#AB-TAG-elections"><span class="secno">3.3.3.3</span> <span class="content"> Advisory Board and Technical Architecture Group Elections</span></a>
+          <li><a href="#TAG-appointments"><span class="secno">3.3.3.4</span> <span class="content"> Technical Architecture Group Appointments</span></a>
+          <li><a href="#random"><span class="secno">3.3.3.5</span> <span class="content"> Verifiable Random Selection Procedure</span></a>
+          <li><a href="#AB-TAG-vacated"><span class="secno">3.3.3.6</span> <span class="content"> Elected Groups Vacated Seats</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#GAGeneral"><span class="secno">3.4</span> <span class="content"> Chartered Groups: Working Groups and Interest Groups</span></a>
+       <ol class="toc">
+        <li><a href="#ReqsAllGroups"><span class="secno">3.4.1</span> <span class="content"> Requirements for All Chartered Groups</span></a>
+        <li><a href="#group-participation"><span class="secno">3.4.2</span> <span class="content"> Participation in Chartered Groups</span></a>
+        <li>
+         <a href="#chartered-group-participants"><span class="secno">3.4.3</span> <span class="content"> Types of Participants in Chartered Groups</span></a>
+         <ol class="toc">
+          <li><a href="#member-rep-wg"><span class="secno">3.4.3.1</span> <span class="content"> Member Representative in a Working Group</span></a>
+          <li><a href="#member-rep-ig"><span class="secno">3.4.3.2</span> <span class="content"> Member Representative in an Interest Group</span></a>
+          <li><a href="#invited-expert-wg"><span class="secno">3.4.3.3</span> <span class="content"> Invited Expert in a Working Group</span></a>
+          <li><a href="#invited-expert-ig"><span class="secno">3.4.3.4</span> <span class="content"> Invited Expert in an Interest Group</span></a>
+          <li><a href="#team-rep-wg"><span class="secno">3.4.3.5</span> <span class="content"> Team Representative in a Working Group</span></a>
+          <li><a href="#team-rep-ig"><span class="secno">3.4.3.6</span> <span class="content"> Team Representative in an Interest Group</span></a>
+         </ol>
+       </ol>
+     </ol>
+    <li>
+     <a href="#group-lifecycle"><span class="secno">4</span> <span class="content"> Lifecycle of Chartered Groups</span></a>
+     <ol class="toc">
+      <li><a href="#charter-initiation"><span class="secno">4.1</span> <span class="content"> Initiating Charter Refinement</span></a>
+      <li><a href="#charter-development"><span class="secno">4.2</span> <span class="content"> Charter Refinement</span></a>
+      <li><a href="#WGCharter"><span class="secno">4.3</span> <span class="content"> Content of a Charter</span></a>
+      <li>
+       <a href="#CharterReview"><span class="secno">4.4</span> <span class="content"> Charter Review and Approval</span></a>
+       <ol class="toc">
+        <li><a href="#charter-major-changes"><span class="secno">4.4.1</span> <span class="content"> New Charters and Major Changes</span></a>
+        <li><a href="#charter-minor-changes"><span class="secno">4.4.2</span> <span class="content"> Minor Changes to Active Charters</span></a>
+       </ol>
+      <li><a href="#cfp"><span class="secno">4.5</span> <span class="content"> Call for Participation in a Chartered Group</span></a>
+      <li><a href="#charter-extension"><span class="secno">4.6</span> <span class="content"> Charter Extension</span></a>
+      <li><a href="#GeneralTermination"><span class="secno">4.7</span> <span class="content"> Chartered Group Closure</span></a>
+     </ol>
+    <li>
+     <a href="#decisions"><span class="secno">5</span> <span class="content"> Decisions</span></a>
+     <ol class="toc">
+      <li><a href="#decision-types"><span class="secno">5.1</span> <span class="content"> Types of Decisions</span></a>
+      <li>
+       <a href="#consensus-building"><span class="secno">5.2</span> <span class="content"> Consensus Building</span></a>
+       <ol class="toc">
+        <li><a href="#Consensus"><span class="secno">5.2.1</span> <span class="content"> Consensus</span></a>
+        <li><a href="#managing-dissent"><span class="secno">5.2.2</span> <span class="content"> Managing Dissent</span></a>
+        <li><a href="#Votes"><span class="secno">5.2.3</span> <span class="content"> Deciding by Vote</span></a>
+       </ol>
+      <li><a href="#formal-address"><span class="secno">5.3</span> <span class="content"> Formally Addressing an Issue</span></a>
+      <li><a href="#WGChairReopen"><span class="secno">5.4</span> <span class="content"> Reopening a Decision When Presented With New Information</span></a>
+      <li><a href="#registering-objections"><span class="secno">5.5</span> <span class="content"> Registering Formal Objections</span></a>
+      <li>
+       <a href="#addressing-fo"><span class="secno">5.6</span> <span class="content"> Addressing Formal Objections</span></a>
+       <ol class="toc">
+        <li><a href="#team-fo-mediation"><span class="secno">5.6.1</span> <span class="content"> Investigation and Mediation by the Team</span></a>
+        <li>
+         <a href="#council"><span class="secno">5.6.2</span> <span class="content"> W3C Council</span></a>
+         <ol class="toc">
+          <li><a href="#council-composition"><span class="secno">5.6.2.1</span> <span class="content"> Council Composition</span></a>
+          <li><a href="#council-delegation"><span class="secno">5.6.2.2</span> <span class="content"> Extraordinary Delegation</span></a>
+          <li><a href="#council-participation"><span class="secno">5.6.2.3</span> <span class="content"> Council Participation, Dismissal, and Renunciation</span></a>
+          <li><a href="#council-short-circuit"><span class="secno">5.6.2.4</span> <span class="content"> Short Circuit</span></a>
+          <li><a href="#council-chairing"><span class="secno">5.6.2.5</span> <span class="content"> Council Chairing</span></a>
+          <li><a href="#council-convention"><span class="secno">5.6.2.6</span> <span class="content"> Convening the Council</span></a>
+          <li><a href="#council-deliberations"><span class="secno">5.6.2.7</span> <span class="content"> Council Deliberations</span></a>
+          <li><a href="#council-decision"><span class="secno">5.6.2.8</span> <span class="content"> Council Decision Report</span></a>
+          <li><a href="#council-appeals"><span class="secno">5.6.2.9</span> <span class="content"> Appealing Council Decisions</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#ACReview"><span class="secno">5.7</span> <span class="content"> Advisory Committee Reviews and W3C Decisions</span></a>
+       <ol class="toc">
+        <li><a href="#ACReviewStart"><span class="secno">5.7.1</span> <span class="content"> Initiating an Advisory Committee Review</span></a>
+        <li><a href="#ACReviewAfter"><span class="secno">5.7.2</span> <span class="content"> Determining the W3C Decision</span></a>
+       </ol>
+      <li><a href="#ACVotes"><span class="secno">5.8</span> <span class="content"> Advisory Committee Votes</span></a>
+      <li><a href="#ACAppeal"><span class="secno">5.9</span> <span class="content"> Appeal by Advisory Committee Representatives</span></a>
+     </ol>
+    <li>
+     <a href="#Reports"><span class="secno">6</span> <span class="content"> W3C Technical Reports</span></a>
+     <ol class="toc">
+      <li><a href="#recs-and-notes"><span class="secno">6.1</span> <span class="content"> Types of Technical Reports</span></a>
+      <li>
+       <a href="#general-requirements"><span class="secno">6.2</span> <span class="content"> General Requirements for Technical Reports</span></a>
+       <ol class="toc">
+        <li><a href="#publication"><span class="secno">6.2.1</span> <span class="content"> Publication of Technical Reports</span></a>
+        <li>
+         <a href="#doc-reviews"><span class="secno">6.2.2</span> <span class="content"> Reviews and Review Responsibilities</span></a>
+         <ol class="toc">
+          <li><a href="#wide-review"><span class="secno">6.2.2.1</span> <span class="content"> Wide Review</span></a>
+         </ol>
+        <li><a href="#correction-classes"><span class="secno">6.2.3</span> <span class="content"> Classes of Changes</span></a>
+        <li><a href="#errata"><span class="secno">6.2.4</span> <span class="content"> Errata Management</span></a>
+        <li><a href="#candidate-amendments"><span class="secno">6.2.5</span> <span class="content"> Candidate Amendments</span></a>
+        <li><a href="#no-group-maintenance"><span class="secno">6.2.6</span> <span class="content"> Maintenance Without a Group</span></a>
+        <li><a href="#contributor-license"><span class="secno">6.2.7</span> <span class="content"> License Grants from Non-Participants</span></a>
+       </ol>
+      <li>
+       <a href="#rec-track"><span class="secno">6.3</span> <span class="content"> The W3C Recommendation Track</span></a>
+       <ol class="toc">
+        <li><a href="#maturity-stages"><span class="secno">6.3.1</span> <span class="content"> Maturity Stages on the Recommendation Track</span></a>
+        <li><a href="#implementation-experience"><span class="secno">6.3.2</span> <span class="content"> Implementation Experience</span></a>
+        <li><a href="#transition-reqs"><span class="secno">6.3.3</span> <span class="content"> Advancement on the Recommendation Track</span></a>
+        <li><a href="#update-reqs"><span class="secno">6.3.4</span> <span class="content"> Updating Mature Publications on the Recommendation Track</span></a>
+        <li><a href="#first-wd"><span class="secno">6.3.5</span> <span class="content"> Publishing a First Public Working Draft</span></a>
+        <li><a href="#revising-wd"><span class="secno">6.3.6</span> <span class="content"> Revising a Working Draft</span></a>
+        <li><a href="#transition-cr"><span class="secno">6.3.7</span> <span class="content"> Transitioning to Candidate Recommendation</span></a>
+        <li>
+         <a href="#revising-cr"><span class="secno">6.3.8</span> <span class="content"> Revising a Candidate Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#publishing-crrs"><span class="secno">6.3.8.1</span> <span class="content"> Publishing a <span>Candidate Recommendation Snapshot</span></span></a>
+          <li><a href="#publishing-crud"><span class="secno">6.3.8.2</span> <span class="content"> Publishing a <span>Candidate Recommendation Draft</span></span></a>
+         </ol>
+        <li>
+         <a href="#transition-rec"><span class="secno">6.3.9</span> <span class="content"> Transitioning to Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#transition-rec-requirements"><span class="secno">6.3.9.1</span> <span class="content"> Requirements for Transition</span></a>
+          <li><a href="#initiating-rec-review"><span class="secno">6.3.9.2</span> <span class="content"> Initiating Review</span></a>
+          <li><a href="#rec-review-resolution"><span class="secno">6.3.9.3</span> <span class="content"> Resolution of Review</span></a>
+          <li><a href="#rec-next-steps"><span class="secno">6.3.9.4</span> <span class="content"> Next Steps from W3C Recommendation</span></a>
+         </ol>
+        <li>
+         <a href="#revising-rec"><span class="secno">6.3.10</span> <span class="content"> Revising a W3C Recommendation</span></a>
+         <ol class="toc">
+          <li><a href="#revised-rec-editorial"><span class="secno">6.3.10.1</span> <span class="content"> Revising a Recommendation: Editorial Changes</span></a>
+          <li><a href="#revised-rec-substantive"><span class="secno">6.3.10.2</span> <span class="content"> Revising a Recommendation: Substantive Changes</span></a>
+          <li><a href="#revised-rec-features"><span class="secno">6.3.10.3</span> <span class="content"> Revising a Recommendation: New Features</span></a>
+          <li><a href="#change-review"><span class="secno">6.3.10.4</span> <span class="content"> Incorporating Candidate Amendments</span></a>
+         </ol>
+        <li><a href="#rec-track-regression"><span class="secno">6.3.11</span> <span class="content"> Regression on the Recommendation Track</span></a>
+        <li>
+         <a href="#tr-end"><span class="secno">6.3.12</span> <span class="content"> Retiring Recommendation Track Documents</span></a>
+         <ol class="toc">
+          <li><a href="#abandon-draft"><span class="secno">6.3.12.1</span> <span class="content"> Abandoning an Unfinished Recommendation</span></a>
+          <li><a href="#rescind-cr"><span class="secno">6.3.12.2</span> <span class="content"> Rescinding a Candidate Recommendation</span></a>
+          <li><a href="#rec-rescind"><span class="secno">6.3.12.3</span> <span class="content"> Abandoning a W3C Recommendation</span></a>
+          <li><a href="#deactivation"><span class="secno">6.3.12.4</span> <span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span></a>
+         </ol>
+       </ol>
+      <li>
+       <a href="#note-track"><span class="secno">6.4</span> <span class="content"> The Note Track (Notes and Statements)</span></a>
+       <ol class="toc">
+        <li><a href="#Note"><span class="secno">6.4.1</span> <span class="content"> Group Notes</span></a>
+        <li><a href="#publishing-notes"><span class="secno">6.4.2</span> <span class="content"> Publishing Notes</span></a>
+        <li><a href="#w3c-statement"><span class="secno">6.4.3</span> <span class="content"> Elevating Group Notes to W3C Statement status</span></a>
+        <li><a href="#revising-memo"><span class="secno">6.4.4</span> <span class="content"> Revising W3C Statements</span></a>
+       </ol>
+      <li>
+       <a href="#registries"><span class="secno">6.5</span> <span class="content"> The Registry Track</span></a>
+       <ol class="toc">
+        <li><a href="#reg-def"><span class="secno">6.5.1</span> <span class="content"> Registry Definitions</span></a>
+        <li><a href="#reg-pub"><span class="secno">6.5.2</span> <span class="content"> Publishing Registries</span></a>
+        <li><a href="#reg-table-update"><span class="secno">6.5.3</span> <span class="content"> Updating Registry Tables</span></a>
+        <li><a href="#reg-data-reports"><span class="secno">6.5.4</span> <span class="content"> Registry Data Reports</span></a>
+        <li><a href="#reg-ref-specifications"><span class="secno">6.5.5</span> <span class="content"> Specifications that Reference Registries</span></a>
+        <li><a href="#reg-pat"><span class="secno">6.5.6</span> <span class="content"> Registries and Patents</span></a>
+       </ol>
+      <li><a href="#switching-tracks"><span class="secno">6.6</span> <span class="content"> Switching Tracks</span></a>
+      <li><a href="#further-reading"><span class="secno">6.7</span> <span class="content"> Further reading</span></a>
+     </ol>
+    <li>
+     <a href="#dissemination"><span class="secno">7</span> <span class="content"> <span></span> Dissemination Policies</span></a>
+     <ol class="toc">
+      <li><a href="#pub-com"><span class="secno">7.1</span> <span class="content"> Public Communication</span></a>
+      <li><a href="#confidentiality-levels"><span class="secno">7.2</span> <span class="content"> Confidentiality Levels</span></a>
+      <li><a href="#confidentiality-change"><span class="secno">7.3</span> <span class="content"> Changing Confidentiality Level</span></a>
+     </ol>
+    <li><a href="#Liaisons"><span class="secno">8</span> <span class="content"> Liaisons</span></a>
+    <li><a href="#Submission"><span class="secno">9</span> <span class="content"> Member Submissions</span></a>
+    <li><a href="#GAProcess"><span class="secno">10</span> <span class="content"> Process Evolution</span></a>
+    <li><a href="#old-terms"><span class="secno"></span> <span class="content"> Appendix A: Retired Terminology</span></a>
+    <li><a href="#acks"><span class="secno"></span> <span class="content"> Appendix B: Acknowledgments</span></a>
+    <li>
+     <a href="#changes"><span class="secno"></span> <span class="content"> Appendix C: Changes</span></a>
+     <ol class="toc">
+      <li><a href="#changes-2025"><span class="secno"></span> <span class="content"> Changes since the <span>3 November 2023 Process</span></span></a>
+      <li><a href="#changes-previous"><span class="secno"></span> <span class="content"> Changes since earlier versions</span></a>
+     </ol>
+    <li>
+     <a href="#index"><span class="secno"></span> <span class="content">Index</span></a>
+     <ol class="toc">
+      <li><a href="#index-defined-here"><span class="secno"></span> <span class="content">Terms defined by this specification</span></a>
+      <li><a href="#index-defined-elsewhere"><span class="secno"></span> <span class="content">Terms defined by reference</span></a>
+     </ol>
+    <li>
+     <a href="#references"><span class="secno"></span> <span class="content">References</span></a>
+     <ol class="toc">
+      <li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
+      <li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
+     </ol>
+   </ol>
+  </nav>
+  <main>
+   <h2 class="no-num no-toc no-ref heading settled" id="pp"><span class="content"> Relation of Process Document to Patent Policy and Other Policies</span></h2>
+   <p>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> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	The <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and other policies
+	incorporated by normative reference as a part of the Process Document
+	are equally binding.</p>
+   <p>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.</p>
+   <p>In the Process Document, the term “participant” refers to an individual, not an organization.</p>
+   <h2 class="no-num no-toc no-ref heading settled" id="terms"><span class="content"> Conformance and specialized terms</span></h2>
+   <p>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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="not-required"><em class="rfc2119">not required</em></dfn> is equivalent to the term <em class="rfc2119">may</em> as defined in RFC2119 <a data-link-type="biblio" href="#biblio-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</a>.</p>
+   <p>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.</p>
+   <nav data-fill-with="table-of-contents"></nav>
+   <main>
+    <h2 class="heading settled" data-level="1" id="Intro"><span class="secno">1. </span><span class="content"> Introduction</span><a class="self-link" href="#Intro"></a></h2>
+    <p>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>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>. <a href="#group-participation">Participants</a> in W3C include <a href="#member-rep">representatives of its Members</a> and the <a data-link-type="dfn" href="#team" id="ref-for-team">Team</a>,
+	as well as <a href="#invited-expert-wg">Invited Experts</a> who can bring additional expertise or represent additional stakeholders. <a data-link-type="dfn" href="#team" id="ref-for-team①">Team</a> representatives both contribute to the technical work
+	and help ensure each group’s proper integration with the rest of W3C.</p>
+    <p>W3C’s technical standards, called <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C">W3C Recommendations</a>,
+	are developed by its <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG">Working Groups</a>;
+	W3C also has other types of publications,
+	all described in <a href="#Reports">§ 6 W3C Technical Reports</a>.
+	W3C has various types of groups;
+	this document describes the formation and policies
+	of its chartered <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG">Interest Groups</a>,
+	see <a href="#Policies">§ 3.1 Policies for Participation in W3C Groups</a> and <a href="#GAGeneral">§ 3.4 Chartered Groups: Working Groups and Interest Groups</a>.
+	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> <a data-link-type="biblio" href="#biblio-bg-cg" title="Community and Business Group Process">[BG-CG]</a>.</p>
+    <p>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.</p>
+    <p>Here is a general overview of how W3C initiates standardization of a Web technology:</p>
+    <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 <a data-link-type="dfn" href="#team" id="ref-for-team②">Team</a> 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>
+    <p>Further sections of this Process Document deal with topics including
+	liaisons (<a href="#Liaisons">§ 8 Liaisons</a>),
+	confidentiality (<a href="#dissemination">§ 7 Dissemination Policies</a>),
+	and formal decisions and appeals (<a href="#decisions">§ 5 Decisions</a>).</p>
+    <h2 class="heading settled" data-level="2" id="Organization"><span class="secno">2. </span><span class="content"> Members and the Team</span><a class="self-link" href="#Organization"></a></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 class="heading settled" data-level="2.1" id="Members"><span class="secno">2.1. </span><span class="content"> Members</span><a class="self-link" href="#Members"></a></h3>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Member|Member" data-noexport id="w3c-member">W3C Members</dfn> are
+	organizations subscribed according to a <a href="https://www.w3.org/membership/agreement/">Membership Agreement</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a>.
+	They are represented in W3C processes as follows:</p>
+    <ol>
+     <li> One representative per Member organization participates
+			in the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee">Advisory Committee</a> 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>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>;
+	(refer to the public list of <a href="https://www.w3.org/membership/list/">current W3C Members</a> <a data-link-type="biblio" href="#biblio-member-list" title="The list of current W3C Members">[MEMBER-LIST]</a>).
+	The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure
+	that Member participation agreements remain <a href="#Team-only" id="ref-for-Team-only">Team-only</a> and that no Member receives preferential treatment within W3C. </p>
+    <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. </p>
+    <h4 class="heading settled" data-level="2.1.1" id="MemberBenefits"><span class="secno">2.1.1. </span><span class="content"> Rights of Members</span><a class="self-link" href="#MemberBenefits"></a></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> Access to <a href="#Member-only" id="ref-for-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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>. 
+    </ul>
+    <p>Furthermore, subject to further restrictions included in their 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>
+       In <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW">Workshops</a>. 
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>)</p>
+     <li> On the Team, as <a href="#fellows" id="ref-for-fellows">W3C Fellows</a>. 
+    </ul>
+    <p>The rights and benefits of W3C membership <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> are contingent upon conformance to the processes described in this document.
+	Disciplinary action for anyone participating in W3C activities is described in <a href="#discipline">§ 3.1.1.1 Expectations and Discipline</a>.</p>
+    <p>Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member website</a> <a data-link-type="biblio" href="#biblio-member-hp" title="Member website (Member-only access)">[MEMBER-HP]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.2" id="RelatedAndAssociatedMembers"><span class="secno">2.1.2. </span><span class="bs-old-id" id="RelatedAndConsortiumMembers"></span><span class="content"> Member Associations and Related Members</span><a class="self-link" href="#RelatedAndAssociatedMembers"></a></h4>
+    <h5 class="heading settled" data-level="2.1.2.1" id="MemberAssoc"><span class="secno">2.1.2.1. </span><span class="bs-old-id" id="MemberConsortia"></span><span class="content"> Membership Associations</span><a class="self-link" href="#MemberAssoc"></a></h5>
+    <p>A “<dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Member Association | Member Associations" data-noexport id="member-association">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 <a data-link-type="dfn" href="#member-association" id="ref-for-member-association">Member Association</a> merely because it has shareholders or stockholders.
+	If it is not clear whether a prospective Member qualifies as a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association①">Member Association</a>,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo">CEO</a> may reasonably make the determination.
+	For a <a data-link-type="dfn" href="#member-association" id="ref-for-member-association②">Member Association</a>, the rights and privileges of W3C Membership
+	described in the W3C Process Document extend to the <a data-link-type="dfn" href="#member-association" id="ref-for-member-association③">Member Association</a>’s paid staff
+	and Advisory Committee representative.</p>
+    <p><a data-link-type="dfn" href="#member-association" id="ref-for-member-association④">Member Associations</a> <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>
+    <p>For <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑤">Member Associations</a> 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.</p>
+    <p>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.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="2.1.2.2" id="MemberRelated"><span class="secno">2.1.2.2. </span><span class="content"> Related Members</span><a class="self-link" href="#MemberRelated"></a></h5>
+    <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 <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Related Member" id="related-member">related</dfn> if:</p>
+    <ol>
+     <li> Either Member is a <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary">subsidiary</a> of the other, or 
+     <li> Both Members are <a data-link-type="dfn" href="#subsidiary" id="ref-for-subsidiary①">subsidiaries</a> of a common entity, or 
+     <li> The Members have an employment contract or consulting contract that affects W3C participation. 
+    </ol>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="subsidiary">subsidiary</dfn> is an organization of which effective control and/or majority ownership rests with another,
+	single organization.</p>
+    <p><a data-link-type="dfn" href="#related-member" id="ref-for-related-member">Related Members</a> <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> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h4 class="heading settled" data-level="2.1.3" id="standing"><span class="secno">2.1.3. </span><span class="content"> Good Standing</span><a class="self-link" href="#standing"></a></h4>
+    <p><a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member">Members</a> who have not lost Good Standing as defined in the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a> are considered, for the purposes of this Process,
+	to be in <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="good-standing">Good Standing</dfn>.
+	A group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member①">related Members</a> is in Good Standing if
+	at least one of them is in Good Standing.</p>
+    <h3 class="heading settled" data-level="2.2" id="Team"><span class="secno">2.2. </span><span class="bs-old-id" id="def-Director"></span><span class="content"> The W3C Team</span><a class="self-link" href="#Team"></a></h3>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team | W3C Team" id="team">Team</dfn> consists of <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="ceo">CEO</dfn>,
+	W3C paid staff,
+	unpaid interns,
+	and W3C Fellows. <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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> <a data-link-type="biblio" href="#biblio-fellows" title="W3C Fellows Program">[FELLOWS]</a>.
+	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.</p>
+    <p>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. <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision">Team Decisions</a> derive from the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo①">CEO</a>’s authority,
+	even when they are carried out by other members of the <a data-link-type="dfn" href="#team" id="ref-for-team③">Team</a>.</p>
+    <p>Oversight over the <a data-link-type="dfn" href="#team" id="ref-for-team④">Team</a>,
+	budgeting,
+	and other business decisions,
+	is provided by the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="BoD | Board | Board of Directors | W3C Board of Directors" id="bod">W3C Board of Directors</dfn>,
+	rather than managed directly by the Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See the <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf">W3C Bylaws</a> for more details
+	on the <a data-link-type="dfn" href="#bod" id="ref-for-bod">Board</a> and overall governance of W3C.</p>
+    <h2 class="heading settled" data-level="3" id="groups"><span class="secno">3. </span><span class="content"> Groups and Participation</span><a class="self-link" href="#groups"></a></h2>
+    <p>For the purposes of this Process, a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="group" data-noexport id="w3c-group">W3C Group</dfn> is one of W3C’s <a href="#wgparticipant" id="ref-for-wgparticipant">Working Groups</a>, <a href="#igparticipant" id="ref-for-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 class="dfn-paneled" data-dfn-type="dfn" data-noexport id="participant">participant</dfn> is a member of such a group.</p>
+    <h3 class="heading settled" data-level="3.1" id="Policies"><span class="secno">3.1. </span><span class="content"> Policies for Participation in W3C Groups</span><a class="self-link" href="#Policies"></a></h3>
+    <h4 class="heading settled" data-level="3.1.1" id="ParticipationCriteria"><span class="secno">3.1.1. </span><span class="content"> Individual Participation Criteria</span><a class="self-link" href="#ParticipationCriteria"></a></h4>
+    <h5 class="heading settled" data-level="3.1.1.1" id="discipline"><span class="secno">3.1.1.1. </span><span class="content"> Expectations and Discipline</span><a class="self-link" href="#discipline"></a></h5>
+    <p>There are three qualities an individual is expected to demonstrate in order to participate in W3C:</p>
+    <ol>
+     <li> Technical competence in one’s role; 
+     <li> The ability to act fairly; 
+     <li> Social competence in one’s role. 
+    </ol>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative">Advisory Committee representatives</a> who nominate individuals from their organization for participation in W3C activities
+	are responsible for assessing and attesting to the qualities of those nominees.</p>
+    <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> <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a> and the participation requirements described in
+	“Disclosure”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. </p>
+    <p>The <a data-link-type="dfn" href="#ceo" id="ref-for-ceo②">CEO</a> <em class="rfc2119">may</em> take disciplinary action,
+	including suspending or removing for cause
+	a participant in any group (including the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group">TAG</a>)
+	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>.</p>
+    <h5 class="heading settled" data-level="3.1.1.2" id="coi"><span class="secno">3.1.1.2. </span><span class="content"> Conflict of Interest Policy</span><a class="self-link" href="#coi"></a></h5>
+    <p>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.</p>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑤">Team</a> <em class="rfc2119">may</em> appoint a new group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs">Chair</a> 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).</p>
+    <p>The following are some scenarios where disclosure is appropriate:</p>
+    <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>
+    <p>Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the <a data-link-type="dfn" href="#team" id="ref-for-team⑥">Team</a>.</p>
+    <p><a data-link-type="dfn" href="#team" id="ref-for-team⑦">Team</a> 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> <a data-link-type="biblio" href="#biblio-conflict-policy" title="Conflict of Interest Policy for the W3C Team">[CONFLICT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="3.1.1.3" id="member-rep"><span class="secno">3.1.1.3. </span><span class="content"> Individuals Representing a Member Organization</span><a class="self-link" href="#member-rep"></a></h5>
+    <p>Generally, individuals representing a Member in an official capacity within W3C
+	are employees of the Member organization.
+	However, an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①">Advisory Committee representative</a> <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.</p>
+    <p>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 <a data-link-type="dfn" href="#ceo" id="ref-for-ceo③">CEO</a> <em class="rfc2119">may</em> decline
+	to allow an individual designated by an Advisory Committee representative to participate in a group.</p>
+    <p>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>).</p>
+    <h4 class="heading settled" data-level="3.1.2" id="GeneralMeetings"><span class="secno">3.1.2. </span><span class="bs-old-id" id="EventsS"></span><span class="bs-old-id" id="GAEvents"></span><span class="content"> Meetings</span><a class="self-link" href="#GeneralMeetings"></a></h4>
+    <p>The requirements in this section apply to the official meetings of any <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group">W3C group</a>,
+	as well as to official W3C meetings with open-ended participation from the Membership and/or the public,
+	such as <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW①">Workshops</a>.</p>
+    <p>W3C distinguishes two types of meetings:</p>
+    <ol>
+     <li> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport 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 class="dfn-paneled" data-dfn-type="dfn" data-noexport 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>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①">Chair</a> <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 <a data-link-type="dfn" href="#participant" id="ref-for-participant">participant</a>.
+	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.</p>
+    <h5 class="heading settled" data-level="3.1.2.1" id="meeting-schedules"><span class="secno">3.1.2.1. </span><span class="content"> Meeting Scheduling and Announcements</span><a class="self-link" href="#meeting-schedules"></a></h5>
+    <p>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.</p>
+    <p>The following table lists <em class="rfc2119">recommendations</em> for organizing a meeting:</p>
+    <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"><a data-link-type="dfn" href="#minutes" id="ref-for-minutes">Minutes</a> available (after) 
+       <td><span class="time-interval">two weeks</span> 
+       <td><span class="time-interval">48 hours</span> 
+    </table>
+    <p><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 <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW②">Workshops</a>,
+	shorter notice is not allowed.</p>
+    <h5 class="heading settled" data-level="3.1.2.2" id="meeting-minutes"><span class="secno">3.1.2.2. </span><span class="content"> Meeting Minutes</span><a class="self-link" href="#meeting-minutes"></a></h5>
+    <p>Groups <em class="rfc2119">should</em> take and retain <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minutes">minutes</dfn> of their meetings,
+	and <em class="rfc2119">must</em> record
+	any official <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision">group decisions</a> made during the meeting discussions.
+	Details of the discussion leading to such decisions are not required,
+	provided that the rationale for the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision①">group decision</a> is nonetheless clear.</p>
+    <h5 class="heading settled" data-level="3.1.2.3" id="meeting-recording"><span class="secno">3.1.2.3. </span><span class="content"> Meeting Recordings and Transcripts</span><a class="self-link" href="#meeting-recording"></a></h5>
+    <p>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.</p>
+    <h4 class="heading settled" data-level="3.1.3" id="tooling"><span class="secno">3.1.3. </span><span class="content"> Tooling and Archiving for Discussions and Publications</span><a class="self-link" href="#tooling"></a></h4>
+    <p>For <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group①">W3C Groups</a> 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:</p>
+    <ul>
+     <li id="report-stability"><a class="self-link" href="#report-stability"></a> 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"><a class="self-link" href="#report-accessibility"></a> 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">
+      <a class="self-link" href="#discussion-archiving"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> The lack, or loss, of such archives does not by itself
+			invalidate an otherwise-valid decision.</p>
+     <li id="tool-accessibility">
+      <a class="self-link" href="#tool-accessibility"></a> 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. 
+      <p class="note" role="note"><span class="marker">Note:</span> If a new participant joins who cannot use the tool,
+			this can require the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②">Working Group</a> to change its tooling
+			or operate some workaround.</p>
+     <li id="where-is-your-stuff"><a class="self-link" href="#where-is-your-stuff"></a> 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>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑧">Team</a> is responsible for ensuring adherence to these rules
+	and for bringing any group not in compliance into compliance.</p>
+    <h4 class="heading settled" data-level="3.1.4" id="resignation"><span class="secno">3.1.4. </span><span class="content"> Resignation from a Group</span><a class="self-link" href="#resignation"></a></h4>
+    <p>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 <a data-link-type="dfn" href="#team" id="ref-for-team⑨">Team</a>,
+	the Member and their representatives
+	or the Invited Expert
+	will be deemed to have resigned from the relevant group.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪">Team</a> <em class="rfc2119">must</em> record the notification.
+	See “Exclusion and Resignation from the Working Group” in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for information about obligations remaining after resignation from certain groups.</p>
+    <h3 class="heading settled" data-level="3.2" id="AC"><span class="secno">3.2. </span><span class="content"> The Advisory Committee (AC)</span><a class="self-link" href="#AC"></a></h3>
+    <h4 class="heading settled" data-level="3.2.1" id="ac-role"><span class="secno">3.2.1. </span><span class="content"> Role of the Advisory Committee</span><a class="self-link" href="#ac-role"></a></h4>
+    <p id="ReviewAppeal"> The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee|AC" id="advisory-committee">Advisory Committee</dfn> represents
+	the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member①">Members</a> of W3C at large.
+	It is responsible for: </p>
+    <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>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> of a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision">W3C decision</a> or <a data-link-type="dfn" href="#team" id="ref-for-team①①">Team</a>’s decision.</p>
+    <p>See also the additional roles of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③">Advisory Committee representatives</a> described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h4 class="heading settled" data-level="3.2.2" id="ac-participation"><span class="secno">3.2.2. </span><span class="content"> Participation in the Advisory Committee</span><a class="self-link" href="#ac-participation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①">Advisory Committee</a> is composed of one <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee representative| AC representative" id="advisory-committee-representative">representative</dfn> from each Member organization
+	(refer to the <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①②">Member-only</a> list
+	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. <a data-link-type="biblio" href="#biblio-current-ac" title="Current Advisory Committee representatives (Member-only access)">[CURRENT-AC]</a>)</p>
+    <p>When an organization joins W3C
+	(see “<a href="https://www.w3.org/membership/join/">How to Join W3C</a>” <a data-link-type="biblio" href="#biblio-join" title="How to Join W3C">[JOIN]</a>),
+	it <em class="rfc2119">must</em> name its Advisory Committee representative as part of their Membership Agreement.
+	The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a> 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 <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative④">Advisory Committee representative</a>,
+	and more. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑤">Advisory Committee representatives</a> <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.</p>
+    <p>The AC representative may delegate any of their rights and responsibilities
+	to an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="alternate AC representative | alternate Advisory Committee representative | alt AC rep" id="alternate-ac-representative">alternate</dfn> (except the ability to designate an alternate).</p>
+    <h4 class="heading settled" data-level="3.2.3" id="ACCommunication"><span class="secno">3.2.3. </span><span class="content"> Advisory Committee Mailing Lists</span><a class="self-link" href="#ACCommunication"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②">Team</a> <em class="rfc2119">must</em> provide two mailing lists for use by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②">Advisory Committee</a>:</p>
+    <ol>
+     <li> One for official announcements (e.g., those required by this document) from the <a data-link-type="dfn" href="#team" id="ref-for-team①③">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③">Advisory Committee</a>.
+			This list is read-only for Advisory Committee representatives. 
+     <li> One for discussion among <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑥">Advisory Committee representatives</a>.
+			Though this list is primarily for Advisory Committee representatives,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①④">Team</a> <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>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑦">Advisory Committee representative</a> <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.</p>
+    <h4 class="heading settled" data-level="3.2.4" id="ACMeetings"><span class="secno">3.2.4. </span><span class="content"> Advisory Committee Meetings</span><a class="self-link" href="#ACMeetings"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑤">Team</a> organizes a <a href="#ftf-meeting" id="ref-for-ftf-meeting">face-to-face meeting</a> for the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④">Advisory Committee</a> <span class="time-interval">twice a year</span>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⑥">Team</a> 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:</p>
+    <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>
+    </dl>
+    <p>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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑦">Team</a> <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.</p>
+    <p>More information about <a href="https://www.w3.org/events/ac/">Advisory Committee meetings</a> <a data-link-type="biblio" href="#biblio-ac-meeting" title="Advisory Committee meetings (Member-only access)">[AC-MEETING]</a> is available at the Member website.</p>
+    <h3 class="heading settled" data-level="3.3" id="elected-groups"><span class="secno">3.3. </span><span class="content"> Elected Groups: The AB and the TAG</span><a class="self-link" href="#elected-groups"></a></h3>
+    <p>The W3C Process defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="elected-group">elected groups</dfn>:
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①">Advisory Board</a> (AB) and
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①">Technical Architecture Group</a> (TAG),
+	both elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑤">Advisory Committee</a>.</p>
+    <h4 class="heading settled" data-level="3.3.1" id="AB"><span class="secno">3.3.1. </span><span class="content"> Advisory Board (AB)</span><a class="self-link" href="#AB"></a></h4>
+    <h5 class="heading settled" data-level="3.3.1.1" id="ab-role"><span class="secno">3.3.1.1. </span><span class="content"> Role of the Advisory Board</span><a class="self-link" href="#ab-role"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Board|AB" id="advisory-board">Advisory Board</dfn> 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>.
+	As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council">W3C Council</a>,
+	members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②">Advisory Board</a> hear and adjudicate on <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③">Advisory Board</a> is distinct from the <a data-link-type="dfn" href="#bod" id="ref-for-bod①">Board of Directors</a> and has no decision-making authority within W3C;
+	its role is strictly advisory.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> While the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board④">AB</a> as such does not have decision-making authority,
+	its members do when sitting as part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①">W3C Council</a>.</p>
+    <p>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> <a data-link-type="biblio" href="#biblio-ab-hp" title="The Advisory Board home page">[AB-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.1.2" id="ABParticipation"><span class="secno">3.3.1.2. </span><span class="content"> Composition of the Advisory Board</span><a class="self-link" href="#ABParticipation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑤">Advisory Board</a> 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 <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑥">AB</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⑧">Team</a> 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.</p>
+    <p>The team also appoints a <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact">Staff Contact</a>,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.
+	The CEO and Staff Contact have a standing invitation
+	to all regular Advisory Board sessions.</p>
+    <p>The nine to eleven <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑦">Advisory Board</a> participants are elected by the W3C <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑥">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>.</p>
+    <p>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.</p>
+    <h5 class="heading settled" data-level="3.3.1.3" id="ab-comm"><span class="secno">3.3.1.3. </span><span class="content"> Communications of the Advisory Board</span><a class="self-link" href="#ab-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⑨">Team</a> <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.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑧">Advisory Board</a> <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>.</p>
+    <h5 class="heading settled" data-level="3.3.1.4" id="ab-bod-liaison"><span class="secno">3.3.1.4. </span><span class="content"> Liaisons between the Advisory Board and the Board of Directors</span><a class="self-link" href="#ab-bod-liaison"></a></h5>
+    <p>To ensure good communication between the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board⑨">AB</a> and the <a data-link-type="dfn" href="#bod" id="ref-for-bod②">Board of Directors</a> and facilitate operational and management consistency,
+	the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⓪">AB</a> <em class="rfc2119">may</em> appoint up to two of its participants as liaisons to the <a data-link-type="dfn" href="#bod" id="ref-for-bod③">Board</a>.
+	Such appointees are expected to attend and participate in <a data-link-type="dfn" href="#bod" id="ref-for-bod④">Board</a> meetings
+	and access <a data-link-type="dfn" href="#bod" id="ref-for-bod⑤">Board</a> materials
+	as Non-voting Observers. <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a> They do not form part of the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑥">Board</a>’s decision-making body,
+	and may be excluded from such participation
+	in accordance with applicable Board procedures.</p>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①①">Advisory Board</a> <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.</p>
+    <h4 class="heading settled" data-level="3.3.2" id="TAG"><span class="secno">3.3.2. </span><span class="content"> Technical Architecture Group (TAG)</span><a class="self-link" href="#TAG"></a></h4>
+    <h5 class="heading settled" data-level="3.3.2.1" id="tag-role"><span class="secno">3.3.2.1. </span><span class="content"> Role of the Technical Architecture Group</span><a class="self-link" href="#tag-role"></a></h5>
+    <p>The mission of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Technical Architecture Group|TAG" id="technical-architecture-group">TAG</dfn> is stewardship of the Web architecture.
+	There are three aspects to this mission:</p>
+    <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> to help coordinate cross-technology architecture developments inside and outside W3C. 
+    </ol>
+    <p>As part of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②">W3C Council</a>,
+	the members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②">TAG</a> hear and adjudicate on <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals①">Submission Appeals</a> and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①">Formal Objections</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③">TAG</a>’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.</p>
+    <p>When the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group④">TAG</a> votes to resolve an issue,
+	each TAG participant
+	(whether appointed, elected, or the Chair)
+	has one vote;
+	see also the general section on <a href="#Votes">votes</a> in this Process Document.</p>
+    <p>Details about the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑤">TAG</a> (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings)
+	are available at the <a href="https://www.w3.org/2001/tag/">TAG home page</a> <a data-link-type="biblio" href="#biblio-tag-hp" title="The TAG home page">[TAG-HP]</a>.</p>
+    <h5 class="heading settled" data-level="3.3.2.2" id="tag-participation"><span class="secno">3.3.2.2. </span><span class="content"> Composition of the Technical Architecture Group</span><a class="self-link" href="#tag-participation"></a></h5>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑥">TAG</a> consists of:</p>
+    <ul>
+     <li> Tim Berners-Lee, who is a life member; 
+     <li> Three participants <a href="#TAG-appointments">appointed by the Team</a>; 
+     <li> Eight participants elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑦">Advisory Committee</a> following the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>. 
+    </ul>
+    <p>Participants in the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑦">TAG</a> choose by consensus their Chair or co-Chairs;
+	in the absence of consensus, the <a data-link-type="dfn" href="#team" id="ref-for-team②⓪">Team</a> appoints the Chair or co-Chairs of the TAG.
+	The Chair or co-Chairs <em class="rfc2119">must</em> be selected from the participants of the TAG.
+	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.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②①">Team</a> also appoints a <a href="https://www.w3.org/guide/teamcontact/role">Staff Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> for the TAG,
+	as described in <a href="#ReqsAllGroups">§ 3.4.1 Requirements for All Chartered Groups</a>.</p>
+    <p>The terms of TAG participants last for <span class="time-interval">two years</span>.
+	Terms are staggered so that four elected terms
+	and either one or two appointed terms expire each year.
+	If an individual is appointed or elected to fill an incomplete term,
+	that individual’s term ends at the normal expiration date of that term.
+	Regular TAG terms begin on 1 February and end on 31 January.</p>
+    <h5 class="heading settled" data-level="3.3.2.3" id="tag-comm"><span class="secno">3.3.2.3. </span><span class="content"> Communications of the Technical Architecture Group</span><a class="self-link" href="#tag-comm"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team②②">Team</a> <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
+    <ul>
+     <li> a public discussion (not just input) list for issues of Web architecture.
+			The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑧">TAG</a> will conduct its public business on this list. 
+     <li> a <a href="#Member-only" id="ref-for-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. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group⑨">TAG</a> <em class="rfc2119">may</em> also request the creation of additional topic-specific, public mailing lists.
+	For some TAG discussions (e.g.,  a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals②">Submission Appeal</a>),
+	the TAG <em class="rfc2119">may</em> use a list that will be <a href="#Member-only" id="ref-for-Member-only①④">Member-only</a>.</p>
+    <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⓪">TAG</a> <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 <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①①">TAG</a> <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory Committee meeting</a>.</p>
+    <h4 class="heading settled" data-level="3.3.3" id="AB-TAG-participation"><span class="secno">3.3.3. </span><span class="content"> Participation in Elected Groups</span><a class="self-link" href="#AB-TAG-participation"></a></h4>
+    <h5 class="heading settled" data-level="3.3.3.1" id="elected-expectations"><span class="secno">3.3.3.1. </span><span class="content"> Expectations for Elected Groups Participants</span><a class="self-link" href="#elected-expectations"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①②">Advisory Board</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①②">TAG</a> participants have a special role within W3C:
+	they are elected by the Membership and appointed by the <a data-link-type="dfn" href="#team" id="ref-for-team②③">Team</a> with the expectation that they will use their best judgment
+	to find the best solutions for the Web,
+	not just for any particular network,
+	technology,
+	vendor,
+	or user.
+	Advisory Board and TAG participants are expected to participate regularly and fully.
+	Advisory Board and TAG participants <em class="rfc2119">should</em> attend <a href="#ACMeetings">Advisory Committee meetings</a>.</p>
+    <p>Individuals elected or appointed to the Advisory Board or TAG act in their personal capacity,
+	to serve the needs of the W3C membership as a whole,
+	and the Web community.
+	Whether they are Member representatives or Invited Experts,
+	their activities in those roles are separate and distinct from their activities on the Advisory Board or TAG.</p>
+    <p>An individual participates on the Advisory Board or TAG
+	from the moment the individual’s term begins until the seat is <a href="#AB-TAG-vacated">vacated</a> (e.g. because the term ends).
+	Although Advisory Board and TAG participants do not advocate for the commercial interests of their employers,
+	their participation does carry the responsibilities associated with Member representation,
+	Invited Expert status,
+	or Team representation
+	(as described in the section on the <a href="#AB-TAG-elections">AB/TAG nomination and election process</a>).</p>
+    <p>Participation in the TAG or AB is afforded to the specific individuals elected or appointed to those positions,
+	and a participant’s seat <em class="rfc2119">must not</em> be delegated to any other person.</p>
+    <h5 class="heading settled" data-level="3.3.3.2" id="AB-TAG-constraints"><span class="secno">3.3.3.2. </span><span class="content"> Elected Groups Participation Constraints</span><a class="self-link" href="#AB-TAG-constraints"></a></h5>
+    <p>Given the few seats available on the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①③">Advisory Board</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①③">TAG</a>,
+	and in order to ensure that the diversity of W3C Members is represented:</p>
+    <ul>
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the TAG
+			except when this is caused by a change of affiliation of an existing participant.
+			At the completion of the next regularly scheduled election for the TAG,
+			the organization <em class="rfc2119">must</em> have returned to having at most one seat. 
+     <li> Two participants with the same <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation①">primary affiliation</a> per <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a> must not both occupy elected seats on the AB.
+			If, for whatever reason, these constraints are not satisfied
+			(e.g., because an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①④">AB</a> participant changes jobs),
+			one participant <em class="rfc2119">must</em> cease <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑤">AB</a> participation
+			until the situation has been resolved.
+			If after <span class="time-interval">30 days</span> the situation has not been resolved,
+			the Chair will apply
+			the <a href="#random">verifiable random selection procedure</a> described below
+			to choose one person for continued participation and declare the other seat(s) vacant. 
+     <li> An individual <em class="rfc2119">must not</em> participate on both the TAG and the AB. 
+    </ul>
+    <h5 class="heading settled" data-level="3.3.3.3" id="AB-TAG-elections"><span class="secno">3.3.3.3. </span><span class="content"> Advisory Board and Technical Architecture Group Elections</span><a class="self-link" href="#AB-TAG-elections"></a></h5>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑥">Advisory Board</a> and a portion of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①④">Technical Architecture Group</a> are elected by the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑧">Advisory Committee</a>,
+	using a Single Transferable Vote system.
+	An election begins when the Team sends a Call for Nominations to the Advisory Committee.
+	Any Call for Nominations specifies the minimum and maximum number of available seats,
+	the deadline for nominations,
+	details about the specific vote tabulation system selected by the Team for the election,
+	and operational information such as how to nominate a candidate.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②④">Team</a> <em class="rfc2119">may</em> modify the tabulation system after the Call for Nominations
+	but <em class="rfc2119">must</em> stabilize it no later than the Call for Votes.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team②⑤">Team</a> announces appointments
+	after the results of the election are known,
+	and before the start of the term,
+	as described in <a href="#TAG-appointments">§ 3.3.3.4 Technical Architecture Group Appointments</a>.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑤">TAG</a>,
+	the minimum and maximum number of available seats are the same:
+	the 4 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats.</p>
+    <p>In the case of regularly scheduled elections of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑦">AB</a>,
+	the minimum and maximum number of available seats differ:
+	The maximum number is the 5 or 6 seats of the terms expiring that year,
+	plus the number of other seats that are vacant or will be vacant by the time the newly elected members take their seats;
+	the minimum number is such that when added to the occupied seats from the prior year,
+	the minimum size of the AB (9) is reached.</p>
+    <p>Each Member (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member②">related Members</a>) <em class="rfc2119">may</em> nominate one individual.
+	A nomination <em class="rfc2119">must</em> be made with the consent of the nominee.
+	In order for an individual to be nominated as a Member representative,
+	the individual <em class="rfc2119">must</em> qualify for <a href="#member-rep">Member representation</a> and the Member’s <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑧">Advisory Committee representative</a> <em class="rfc2119">must</em> include in the nomination
+	the (same) <a href="#member-rep-info">information required for a Member representative in a Working Group</a>.
+	In order for an individual to be nominated as an Invited Expert,
+	the individual <em class="rfc2119">must</em> provide
+	the (same) <a href="#inv-expert-info" id="ref-for-inv-expert-info">information required for an Invited Expert in a Working Group</a> and the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative⑨">Advisory Committee representative</a> <em class="rfc2119">must</em> include that information in the nomination.
+	In order for an individual to be nominated as a <a data-link-type="dfn" href="#team" id="ref-for-team②⑥">Team</a> representative,
+	the nominating <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⓪">Advisory Committee representative</a> <em class="rfc2119">must</em> first secure approval from <a data-link-type="dfn" href="#team" id="ref-for-team②⑦">Team</a> management.
+	A nominee is <em class="rfc2119">not required</em> to be an employee of a Member organization,
+	and <em class="rfc2119">may</em> be a <a href="#fellows" id="ref-for-fellows①">W3C Fellow</a>.
+	The nomination form <em class="rfc2119">must</em> ask for the nominee’s <a data-link-type="dfn" href="#primary-affiliation" id="ref-for-primary-affiliation②">primary affiliation</a>,
+	and this will be reported on the ballot.
+	For most nominees,
+	the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="primary-affiliation">primary affiliation</dfn> is their employer and will match their affiliation in the W3C database.
+	For contractors and invited experts,
+	this will normally be their contracting company
+	or their invited expert status;
+	in some cases
+	(e.g. where a consultant is consulting for only one organization)
+	this <em class="rfc2119">may</em> be the organization for whom the nominee is consulting.
+	A <a href="#AB-TAG-constraints">change of affiliation</a> is defined
+	such that this field would carry a different answer
+	if the nominee were to be re-nominated
+	(therefore,
+	terminating employment,
+	or accepting new employment,
+	are changes of affiliation).
+	(Other formal relationships such as other contracts should be disclosed as potential conflicts of interest.)
+	Each nomination <em class="rfc2119">should</em> include
+	a few informative paragraphs about the nominee.
+	If an identified candidate’s nomination information is only partially complete
+	as of the deadline for nominations,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team②⑧">Team</a> <em class="rfc2119">may</em> allow extra time for that candidate’s nomination to be completed,
+	so long as it does not delay the election as a whole.</p>
+    <p>If, after the deadline for nominations, the number of nominees is:</p>
+    <ul>
+     <li> Greater than or equal to the minimum number of available seats
+			and less than or equal to the maximum number of available seats,
+			those nominees are thereby elected.
+			This situation constitutes a tie for the purpose of assigning <a href="#short-term">incomplete terms</a>.
+			Furthermore, if the number is less than the maximum number of available seats,
+			the longest terms are filled first. 
+     <li> Less than the minimum number of available seats,
+			Calls for Nominations are issued until a sufficient number of people have been nominated.
+			Those already nominated do not need to be renominated after a renewed call. 
+     <li> Greater than the maximum number of available seats,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team②⑨">Team</a> issues a Call for Votes
+			that includes the names of all candidates,
+			the (maximum) number of available seats,
+			the deadline for votes,
+			details about the vote tabulation system selected by the Team for the election,
+			and operational information. 
+    </ul>
+    <p>When there is a vote,
+	each Member in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing">Good Standing</a> (or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member③">related Members</a>) <em class="rfc2119">may</em> submit one ballot that ranks candidates in the Member’s preferred order.
+	Once the deadline for votes has passed,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⓪">Team</a> announces the results to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee⑨">Advisory Committee</a>.
+	In case of a tie the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to fill the available seats.</p>
+    <p id="short-term">The shortest incomplete term is assigned to the elected candidate ranked lowest by the tabulation of votes,
+	the next shortest term to the next-lowest ranked elected candidate,
+	and so on.
+	In the case of a tie among those eligible for a incomplete term,
+	the <a href="#random">verifiable random selection procedure</a> described below
+	will be used to assign the incomplete term. </p>
+    <p>Refer to <a href="https://www.w3.org/guide/process/election">How to Organize an Advisory Board or TAG election</a> <a data-link-type="biblio" href="#biblio-election-howto" title="How to Organize an Advisory Board or TAG election">[ELECTION-HOWTO]</a> for more details.</p>
+    <h5 class="heading settled" data-level="3.3.3.4" id="TAG-appointments"><span class="secno">3.3.3.4. </span><span class="content"> Technical Architecture Group Appointments</span><a class="self-link" href="#TAG-appointments"></a></h5>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③①">Team</a> is responsible for appointing
+	3 of the participants to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑥">Technical Architecture Group</a>.
+	This mechanism complements the election process.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③②">Team</a> <em class="rfc2119">should</em> use its appointments to support
+	a diverse and well-balanced <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑦">TAG</a>,
+	including diversity of technical background, knowledge, and skill sets.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③③">Team</a> <em class="rfc2119">should</em> actively seek
+	candidates for appointment to the TAG,
+	and <em class="rfc2119">must</em> make available to
+	the W3C community at large
+	a means to propose candidates for consideration,
+	explicitly soliciting input from at least
+	current and incoming <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑧">TAG</a> members, the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⓪">Advisory Committee</a>, and <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②">Chairs</a>.</p>
+    <p>The constraints for appointment to the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group①⑨">TAG</a> are
+	the same as for elected participants
+	(see <a href="#AB-TAG-constraints">§ 3.3.3.2 Elected Groups Participation Constraints</a> and <a href="#AB-TAG-elections">§ 3.3.3.3 Advisory Board and Technical Architecture Group Elections</a>),
+	with the additional constraint that
+	a person <em class="rfc2119">must not</em> be appointed
+	for more than two <em>consecutive</em> terms.
+	(Partial terms used to fill a vacated seat do not count towards this limit.)</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since there are no limits on elected terms,
+	this limit on appointed terms does not constrain
+	term-limited appointees
+	from running for election at any time.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team③④">Team</a>’s choice of appointee(s)
+	is subject to ratification by secret ballot
+	by both the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑧">AB</a> and the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⓪">TAG</a>,
+	requiring a two-thirds approval from each.
+	In the case of regularly scheduled elections,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②①">TAG</a> participants in this ratification are
+	its members for the upcoming term.</p>
+    <p>For regularly scheduled elections,
+	selection begins once the results of the elections are known,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team③⑤">Team</a> <em class="rfc2119">should</em> announce the ratified appointment(s)
+	no later than the start of the regularly scheduled term.
+	When an appointed seat is vacated outside of a regularly scheduled election,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team③⑥">Team</a> <em class="rfc2119">should</em> seek to appoint a replacement
+	unless a regular Call for Nominations is scheduled within 2 months,
+	and it <em class="rfc2119">must</em> announce the ratified appointment
+	no later than the Call for Nominations of the next scheduled election.</p>
+    <h5 class="heading settled" data-level="3.3.3.5" id="random"><span class="secno">3.3.3.5. </span><span class="content"> Verifiable Random Selection Procedure</span><a class="self-link" href="#random"></a></h5>
+    <p>When it is necessary to use a verifiable random selection process
+	(e.g., in an <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board①⑨">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②②">TAG</a> election,
+	to “draw straws” in case of a tie
+	or to fill a incomplete term),
+	W3C uses the random and verifiable procedure defined in <a href="https://www.ietf.org/rfc/rfc3797.txt">RFC 3797</a> <a data-link-type="biblio" href="#biblio-rfc3797" title="Publicly Verifiable Nominations Committee (NomCom) Random Selection">[RFC3797]</a>.
+	The procedure orders an input list of names
+	(listed in alphabetical order by family name unless otherwise specified)
+	into a “result order”.</p>
+    <p>W3C applies this procedure as follows:</p>
+    <ol>
+     <li> When N people have tied for M (less than N) seats.
+			In this case, only the names of the N individuals who tied
+			are provided as input to the procedure.
+			The M seats are assigned in result order. 
+     <li> After all elected individuals have been identified,
+			when N people are eligible for M (less than N) incomplete terms.
+			In this case, only the names of those N individuals are provided as input to the procedure.
+			The incomplete terms are assigned in result order. 
+    </ol>
+    <h5 class="heading settled" data-level="3.3.3.6" id="AB-TAG-vacated"><span class="secno">3.3.3.6. </span><span class="content"> Elected Groups Vacated Seats</span><a class="self-link" href="#AB-TAG-vacated"></a></h5>
+    <p>An <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⓪">Advisory Board</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②③">TAG</a> participant’s seat is vacated when:</p>
+    <ul>
+     <li> the participant resigns, or 
+     <li> an Advisory Board or TAG participant changes affiliations
+			such that the <a href="#AB-TAG-constraints">Advisory Board and TAG participation constraints</a> are no longer met,
+			or 
+     <li> the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo④">CEO</a> dismisses the participant
+			for failing to meet the criteria in section <a href="#ParticipationCriteria">§ 3.1.1 Individual Participation Criteria</a>,
+			or 
+     <li> their term ends. 
+    </ul>
+    <p>If a participant changes affiliation,
+	but the <a href="#AB-TAG-constraints">participation constraints</a> are met,
+	that participant’s seat becomes vacant at the next regularly scheduled election for that group.</p>
+    <p>Vacated seats are filled according to this schedule:</p>
+    <ul>
+     <li> When an appointed <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②④">TAG</a> seat is vacated,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team③⑦">Team</a> <a href="#TAG-appointments">appoints</a> a replacement. 
+     <li>
+       When an elected seat on either the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②①">AB</a> or <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑤">TAG</a> is vacated,
+			the seat is filled at the next regularly scheduled election for the group
+			unless the group Chair requests that W3C hold an election before then
+			(for instance, due to the group’s workload). 
+      <ul>
+       <li> The group Chair <em class="rfc2119">should not</em> request such an election
+					if the next regularly scheduled election is fewer than three months away. 
+       <li> The group Chair <em class="rfc2119">may</em> request an election,
+					and the election may begin, as soon as a current member gives notice of a resignation,
+					including a resignation effective as of a given date in the future. 
+      </ul>
+      <p>When such an election is held,
+			the minimum number of available seats is such that
+			when added to the number of continuing participants,
+			the minimum total number of elected seats is met
+			(8 for the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑥">TAG</a>, 9 for the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②②">AB</a>);
+			and the maximum number corresponds to all unoccupied seats.
+			Except for the number of available seats and the length of the terms,
+			the <a href="#AB-TAG-elections">usual rules for Advisory Board and Technical Architecture Group Elections</a> apply.</p>
+    </ul>
+    <h3 class="heading settled" data-level="3.4" id="GAGeneral"><span class="secno">3.4. </span><span class="bs-old-id" id="WG-and-IG"></span><span class="bs-old-id" id="ChapterGroups"></span><span class="content"> Chartered Groups: Working Groups and Interest Groups</span><a class="self-link" href="#GAGeneral"></a></h3>
+    <p id="GAGroups">This document defines two types of <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chartered-group">chartered groups</dfn>: </p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsWG"><a href="#GroupsWG" id="ref-for-GroupsWG⑦⑦">Working Groups</a></dfn>. 
+     <dd>
+       Working Groups typically produce deliverables
+			(e.g., <a href="#rec-advance">Recommendation Track technical reports</a>,
+			software,
+			test suites,
+			and reviews of the deliverables of other groups)
+			as defined in their <a href="#WGCharter">charter</a>. 
+      <p>Working Groups have additional participation requirements
+			described in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			see particularly the “<a href="https://www.w3.org/policies/patent-policy/#sec-Obligations">Licensing Obligations of Working Group Participants</a>”
+			and the patent claim exclusion process
+			in “<a href="https://www.w3.org/policies/patent-policy/#sec-Exclusion">Exclusion From W3C RF Licensing Requirements</a>”.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GroupsIG"><a href="#GroupsIG" id="ref-for-GroupsIG①③">Interest Groups</a></dfn>. 
+     <dd>
+       The primary goal of an Interest Group
+			is to bring together people who wish to evaluate potential Web technologies and policies.
+			An Interest Group is a forum for the exchange of ideas. 
+      <p>Interest Groups do not publish <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑤">Recommendation Track technical reports</a>;
+			but can publish <a href="#WGNote" id="ref-for-WGNote">technical reports on the Note Track</a>.</p>
+    </dl>
+    <h4 class="heading settled" data-level="3.4.1" id="ReqsAllGroups"><span class="secno">3.4.1. </span><span class="content"> Requirements for All Chartered Groups</span><a class="self-link" href="#ReqsAllGroups"></a></h4>
+    <p>Each group <em class="rfc2119">must</em> have a <a data-link-type="dfn" href="#charter" id="ref-for-charter">charter</a>.
+	Requirements for the charter depend on the group type.
+	All group charters <em class="rfc2119">must</em> be public
+	(even if other proceedings of the group are <a href="#Member-only" id="ref-for-Member-only①⑤">Member-only</a>).</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="GeneralChairs">Chair</dfn> (or co-Chairs)
+	to facilitate effective discussion and coordinate the group’s activities.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team③⑧">Team</a> appoints (and re-appoints) Chairs for all groups.
+	The Chair is a <a href="#member-rep">Member representative</a>,
+	a <a href="#Team">Team representative</a>,
+	or an <a href="#invited-expert-wg">Invited Expert</a> (invited by the <a data-link-type="dfn" href="#team" id="ref-for-team③⑨">Team</a>).
+	The requirements of this document that apply to those types of participants apply to Chairs as well.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/guide/chair/role">role of the Chair</a> <a data-link-type="biblio" href="#biblio-chair" title="W3C Working/Interest Group Chair">[CHAIR]</a> is described
+	in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>Each group <em class="rfc2119">must</em> have a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="TeamContact">Staff Contact</dfn> (also known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-contact">Team Contact</dfn>),
+	who acts as the interface between the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③">Chair</a>,
+	group participants,
+	and the rest of the <a data-link-type="dfn" href="#team" id="ref-for-team④⓪">Team</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a href="https://www.w3.org/guide/teamcontact/role">role of the Staff Contact</a> <a data-link-type="biblio" href="#biblio-team-contact" title="Role of the Team Contact">[TEAM-CONTACT]</a> is described in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>.</p>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs④">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①">Staff Contact</a> of a group <em class="rfc2119">should not</em> be the same individual.</p>
+    <p>Each group <em class="rfc2119">must</em> have an archived mailing list
+	for formal group communication
+	(e.g., for meeting announcements and <a data-link-type="dfn" href="#minutes" id="ref-for-minutes①">minutes</a>,
+	documentation of decisions,
+	and <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②">Formal Objections</a> to decisions).
+	It is the responsibility of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑤">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact②">Staff Contact</a> to ensure that new participants are subscribed to all relevant mailing lists.
+	Refer to the list of <a href="https://www.w3.org/groups/">group mailing lists</a> <a data-link-type="biblio" href="#biblio-group-mail" title="Group mailing lists">[GROUP-MAIL]</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑥">Chair</a> <em class="rfc2119">may</em> form task forces
+	(composed of group participants)
+	to carry out assignments for the group.
+	The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group’s charter.
+	A group <em class="rfc2119">should</em> document the process it uses
+	to create task forces
+	(e.g., each task force might have an informal "charter").
+	Task forces do not publish <a href="#Reports">technical reports</a>;
+	the Working Group <em class="rfc2119">may</em> choose to publish their results as part of a technical report. </p>
+    <h4 class="heading settled" data-level="3.4.2" id="group-participation"><span class="secno">3.4.2. </span><span class="content"> Participation in Chartered Groups</span><a class="self-link" href="#group-participation"></a></h4>
+    <p>There are three types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="wgparticipant">participants in a Working Group</dfn>: <a href="#member-rep">Member representatives</a>, <a href="#invited-expert-wg">Invited Experts</a>,
+	and <a href="#Team">Team representatives</a> (including the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact③">Staff Contact</a>).</p>
+    <p>There are four types of individual <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="igparticipant">participants in an Interest Group</dfn>:
+	the same three types as for Working Groups plus,
+	for an Interest Group where the only <a href="#ig-mail-only">participation requirement is mailing list subscription</a>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="public-participant-ig">public participants</dfn>.</p>
+    <p>Except where noted in this document or in a group charter,
+	all participants share the same rights and responsibilities in a group;
+	see also the <a href="#ParticipationCriteria">individual participation criteria</a>.</p>
+    <p>A participant <em class="rfc2119">may</em> represent more than one organization
+	in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①">Interest Group</a>.
+	Those organizations <em class="rfc2119">must</em> all be members of the group.</p>
+    <p>An individual <em class="rfc2119">may</em> become
+	a Working or Interest Group participant
+	at any time during the group’s existence.
+	See also relevant requirements in
+	“Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>On an exceptional basis,
+	a Working or Interest Group participant <em class="rfc2119">may</em> designate
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mtg-substitute">substitute</dfn> to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑦">Chair</a>.
+	The substitute <em class="rfc2119">may</em> act on behalf of the participant,
+	including for <a href="#Votes">votes</a>.
+	For the substitute to vote,
+	the participant <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑧">Chair</a> in writing in advance.</p>
+    <p>To allow rapid progress,
+	Working Groups are intended to be small
+	(typically fewer than 15 people)
+	and composed of experts in the area defined by the charter.
+	In principle,
+	Interest Groups have no limit on the number of participants.
+	When a Working Group grows too large to be effective,
+	W3C <em class="rfc2119">may</em> split it into an Interest Group
+	(a discussion forum)
+	and a much smaller Working Group
+	(a core group of highly dedicated participants).</p>
+    <h4 class="heading settled" data-level="3.4.3" id="chartered-group-participants"><span class="secno">3.4.3. </span><span class="content"> Types of Participants in Chartered Groups</span><a class="self-link" href="#chartered-group-participants"></a></h4>
+    <h5 class="heading settled" data-level="3.4.3.1" id="member-rep-wg"><span class="secno">3.4.3.1. </span><span class="content"> Member Representative in a Working Group</span><a class="self-link" href="#member-rep-wg"></a></h5>
+    <p>An individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-a-working-group">Member representative in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Advisory Committee representative of the Member in question
+			has designated the individual as a Working Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a Member representative in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤">Working Group</a>,
+	an <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①①">Advisory Committee representative</a> <em class="rfc2119">must</em> provide the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs⑨">Chair</a> and <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact④">Staff Contact</a> with all of the following <span id="member-rep-info">information</span>,
+	in addition to any other information required by the <a href="#cfp">Call for Participation</a> and charter
+	(including the participation requirements of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>):</p>
+    <ol>
+     <li> The name of the W3C Member the individual represents
+			and whether the individual is an employee of that Member organization; 
+     <li> A statement that the individual accepts the participation terms
+			set forth in the charter
+			(with an indication of charter date or version); 
+     <li> A statement that the Member will provide the necessary financial support for participation
+			(e.g., for travel, telephone calls, and conferences). 
+    </ol>
+    <p>A Member participates in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥">Working Group</a> from the moment the first Member representative joins the group
+	until either of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Member <a href="#resignation">resigns</a> from the Working Group;
+			this is done through the Member’s Advisory Committee representative. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.2" id="member-rep-ig"><span class="secno">3.4.3.2. </span><span class="content"> Member Representative in an Interest Group</span><a class="self-link" href="#member-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="member-representative-in-an-interest-group">Member representative in an Interest Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①②">Advisory Committee representative</a> of the Member in question has designated the individual
+			as an Interest Group participant, and 
+     <li> the individual qualifies for <a href="#member-rep">Member representation</a>. 
+    </ul>
+    <p>To designate an individual as a <a data-link-type="dfn" href="#member-representative-in-an-interest-group" id="ref-for-member-representative-in-an-interest-group">Member representative in an Interest Group</a>,
+	the Advisory Committee representative <em class="rfc2119">must</em> follow the instructions
+	in the <a href="#cfp">Call for Participation</a> and charter.</p>
+    <p>Member participation in an Interest Group ceases under the same conditions as for a Working Group.</p>
+    <h5 class="heading settled" data-level="3.4.3.3" id="invited-expert-wg"><span class="secno">3.4.3.3. </span><span class="content"> Invited Expert in a Working Group</span><a class="self-link" href="#invited-expert-wg"></a></h5>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⓪">Chair</a> <em class="rfc2119">may</em> invite an individual with a particular expertise
+	to participate in a Working Group.
+	This individual <em class="rfc2119">may</em> represent an organization in the group
+	(e.g., if acting as a liaison with another organization).</p>
+    <p>An individual is an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-a-working-group">Invited Expert in a Working Group</dfn> if all of the following conditions are satisfied:</p>
+    <ul>
+     <li> the Chair has designated the individual as a group participant, 
+     <li> the Staff Contact has agreed with the Chair’s choice, and 
+     <li> the individual has provided the <a href="#inv-expert-info" id="ref-for-inv-expert-info①">information required of an Invited Expert</a> to the Chair and Staff Contact. 
+    </ul>
+    <p>To designate an individual as an Invited Expert in a Working Group,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①①">Chair</a> <em class="rfc2119">must</em> inform the Staff Contact
+	and provide rationale for the choice.
+	When the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①②">Chair</a> and the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑤">Staff Contact</a> disagree about a designation,
+	the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑤">CEO</a> determines
+	whether the individual will be invited to participate in the Working Group.</p>
+    <p>To <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="inv-expert-info">participate in a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦">Working Group</a> as an Invited Expert</dfn>,
+	an individual <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> identify the organization, if any, the individual represents as a participant in this group, 
+     <li> agree to the terms of the <a href="https://www.w3.org/invited-experts/agreement-2023/">invited expert and collaborators agreement</a> <a data-link-type="biblio" href="#biblio-collaborators-agreement" title="Invited expert and collaborators agreement">[COLLABORATORS-AGREEMENT]</a>, 
+     <li> accept the participation terms set forth in the charter,
+			including the participation requirements of
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			especially in “Note on Licensing Commitments for Invited Experts”
+			and in “Disclosure”,
+			indicating a specific charter date or version, 
+     <li> disclose whether the individual is an employee of a W3C Member;
+			see the <a href="#coi">conflict of interest policy</a>, 
+     <li> provide a statement of who will provide the necessary financial support
+			for the individual’s participation
+			(e.g., for travel, telephone calls, and conferences), and 
+     <li> if the individual’s employer (including a self-employed individual)
+			or the organization the individual represents
+			is not a W3C Member,
+			indicate whether that organization intends to join W3C.
+			If the organization does not intend to join W3C,
+			indicate reasons the individual is aware of for this choice. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①③">Chair</a> <em class="rfc2119">should not</em> designate as an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group">Invited Expert in a Working Group</a> an individual who is an employee of a W3C Member.
+	The Chair <em class="rfc2119">must not</em> use Invited Expert status
+	to circumvent participation limits imposed by the <a href="#WGCharter">charter</a>.</p>
+    <p>An Invited Expert participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> the Chair or <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑥">CEO</a> withdraws the invitation to participate, or 
+     <li> the individual <a href="#resignation">resigns</a>. 
+    </ul>
+    <h5 class="heading settled" data-level="3.4.3.4" id="invited-expert-ig"><span class="secno">3.4.3.4. </span><span class="content"> Invited Expert in an Interest Group</span><a class="self-link" href="#invited-expert-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	the participation requirements for an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="invited-expert-in-an-interest-group">Invited Expert in an Interest Group</dfn> are the same as those for an <a data-link-type="dfn" href="#invited-expert-in-a-working-group" id="ref-for-invited-expert-in-a-working-group①">Invited Expert in a Working Group</a>.</p>
+    <h5 class="heading settled" data-level="3.4.3.5" id="team-rep-wg"><span class="secno">3.4.3.5. </span><span class="content"> Team Representative in a Working Group</span><a class="self-link" href="#team-rep-wg"></a></h5>
+    <p>An individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-representative-in-a-working-group">Team representative in a Working Group</dfn> when so designated by W3C management.
+	Team representatives both contribute to the technical work
+	and help ensure the group’s proper integration with the rest of W3C.</p>
+    <p>A Team representative participates in a Working Group
+	from the moment the individual joins the group
+	until any of the following occurs:</p>
+    <ul>
+     <li> the group closes, or 
+     <li> W3C management changes Team representation by sending email to the Chair,
+			copying the group mailing list. 
+    </ul>
+    <p>The Team participates in a Working Group
+	from the moment the creation of the group is announced
+	until the group closes.</p>
+    <h5 class="heading settled" data-level="3.4.3.6" id="team-rep-ig"><span class="secno">3.4.3.6. </span><span class="content"> Team Representative in an Interest Group</span><a class="self-link" href="#team-rep-ig"></a></h5>
+    <p>When the participation requirements exceed <a href="#ig-mail-only">Interest Group mailing list subscription</a>,
+	an individual is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="team-representative-in-an-interest-group">Team representative in an Interest Group</dfn> when so designated by W3C management.</p>
+    <h2 class="heading settled" data-level="4" id="group-lifecycle"><span class="secno">4. </span><span class="content"> Lifecycle of Chartered Groups</span><a class="self-link" href="#group-lifecycle"></a></h2>
+    <p>W3C creates <a data-link-type="dfn" href="#charter" id="ref-for-charter①">charters</a> for <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group">chartered groups</a> based on W3C community interest.
+	W3C fosters awareness of <a data-link-type="dfn" href="#charter" id="ref-for-charter②">charters</a>,
+	improves their quality,
+	and gauges Membership support in two formal phases:</p>
+    <ul>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement">refinement</a> phase helps ensure <a data-link-type="dfn" href="#charter" id="ref-for-charter③">charters</a> are mission-aligned,
+reflect community input and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus">consensus</a>,
+and have been well-socialized
+and <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review">widely reviewed</a>.</p>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#charter" id="ref-for-charter④">Charters</a> then are formally approved through an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review">AC Review</a> and <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①">W3C Decision</a> (see <a href="#CharterReview">§ 4.4 Charter Review and Approval</a>).</p>
+    </ul>
+    <h3 class="heading settled" data-level="4.1" id="charter-initiation"><span class="secno">4.1. </span><span class="content"> Initiating Charter Refinement</span><a class="self-link" href="#charter-initiation"></a></h3>
+    <p><a data-link-type="dfn" href="#charter" id="ref-for-charter⑤">Charters</a> can originate in many venues,
+	including existing <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑧">Working</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG②">Interest Groups</a>,
+	Community Groups,
+	and from the <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member②">Membership</a>.
+	Prior to the formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①">refinement</a> phase,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④①">Team</a> engages with those various parties
+	to help prepare <a data-link-type="dfn" href="#charter" id="ref-for-charter⑥">charters</a> for broader audiences.</p>
+    <p>Formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement②">charter refinement</a> (see below) is initiated
+	by the <a data-link-type="dfn" href="#team" id="ref-for-team④②">Team</a> sending a <a data-link-type="dfn" href="#charter-review-notice" id="ref-for-charter-review-notice">charter review notice</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①①">Advisory Committee</a>,
+	to the public,
+	and, in the case of rechartering, to the affected <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group②">Group</a>.</p>
+    <p>This <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-review-notice">charter review notice</dfn> must include:</p>
+    <ul>
+     <li data-md>
+      <p>A short summary of the proposal.</p>
+     <li data-md>
+      <p>The location of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-draft">charter draft</dfn>, which must be public.</p>
+     <li data-md>
+      <p>How to participate in the discussion of this <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft">charter draft</a> and where to file issues.</p>
+     <li data-md>
+      <p>The expected duration of the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement③">charter refinement</a> phase,
+which must not be less than 28 days,
+and should not be more than 6 months.</p>
+     <li data-md>
+      <p>Who the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator">Chartering Facilitator</a> is.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team④③">Team</a> is responsible for initiating <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement④">charter refinement</a> at its discretion, in consideration of discussions with the community.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①③">Advisory Committee representative</a> <em class="rfc2119">may</em> formally request
+	that the <a data-link-type="dfn" href="#team" id="ref-for-team④④">Team</a> initiate <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑤">charter refinement</a>.
+	The Team <em class="rfc2119">may</em> deny such a request
+	if it thinks the proposal is insufficiently mature,
+	does not align with W3C’s scope and mission,
+	or otherwise does not meet the charter assessment criteria
+	described in the Guide (see <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/guide/process/charter"><cite>How to Create a Working Group or Interest Group</cite></a>),
+	and <em class="rfc2119">must</em> reply with its rationale.
+	This rejection is a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①">Team Decision</a>,
+	and can be appealed only by 5 or more <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member③">Members</a>,
+	through their <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①④">Advisory Committee representative</a>,
+	formally objecting to the decision within 8 weeks of the decision being announced.
+	In this case the <a data-link-type="dfn" href="#team" id="ref-for-team④⑤">Team</a> <em class="rfc2119">must</em> start an <a data-link-type="dfn" href="#appeal-vote" id="ref-for-appeal-vote">appeal vote</a> on whether to overturn the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision②">Team Decision</a>.
+	(No action is required to be taken when fewer than 5 members object.)</p>
+    <h3 class="heading settled" data-level="4.2" id="charter-development"><span class="secno">4.2. </span><span class="bs-old-id" id="WGCharterDevelopment"></span><span class="content"> Charter Refinement</span><a class="self-link" href="#charter-development"></a></h3>
+    <p>During <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="charter-refinement">charter refinement</dfn>,
+	the W3C community,
+	under the guidance of the <a data-link-type="dfn" href="#team" id="ref-for-team④⑥">Team</a>,
+	further develops the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft①">charter draft</a> with the goal of achieving <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①">consensus</a> on the proposal.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="chartering-facilitator">Chartering Facilitator</dfn>—​who is chosen (and <em class="rfc2119">may</em> be replaced) by the <a data-link-type="dfn" href="#team" id="ref-for-team④⑦">Team</a>—​is responsible for seeking community <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②">consensus</a> among those participating in the refinement process
+	and making decisions reflecting that <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus③">consensus</a>.
+	In cases where <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus④">consensus</a> cannot be found,
+	the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator①">Chartering Facilitator</a> <em class="rfc2119">may</em> ask the <a data-link-type="dfn" href="#team" id="ref-for-team④⑧">Team</a> to make a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision③">Team Decision</a>,
+	and <em class="rfc2119">must</em> document the rationale for the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator②">Chartering Facilitator</a> is not necessarily the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①④">Chair</a> of the <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group①">group</a> being chartered.</p>
+    <p>During <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑥">charter refinement</a>:</p>
+    <ul>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①">Wide review</a> of the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft②">charter draft</a> is initiated and completed.</p>
+     <li data-md>
+      <p>All issues filed against the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft③">charter draft</a> must be <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed">formally addressed</a>,
+and their resolutions tracked in a disposition of comments
+highlighting any issues not resolved by consensus.</p>
+    </ul>
+    <p>Before the end of the announced duration
+	for the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑦">charter refinement</a> phase,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team④⑨">Team</a> (informed by the work of the <a data-link-type="dfn" href="#chartering-facilitator" id="ref-for-chartering-facilitator③">Chartering Facilitator</a>) <em class="rfc2119">must</em> <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision④">decide</a> which of the following to do:</p>
+    <ul>
+     <li data-md>
+      <p>Complete charter refinement by initiating <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①">AC Review</a> of the <a data-link-type="dfn" href="#charter-draft" id="ref-for-charter-draft④">charter draft</a>.</p>
+     <li data-md>
+      <p>Abandon the proposal.</p>
+     <li data-md>
+      <p>Extend the charter refinement period.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⓪">Team</a> <em class="rfc2119">must</em> announce its <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑤">decision</a> with the same visibility as the initial <a data-link-type="dfn" href="#charter-review-notice" id="ref-for-charter-review-notice①">charter review notice</a>,
+	and <em class="rfc2119">must</em> include a rationale
+	if they are not initiating <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②">AC Review</a>.
+	Reaching the end of the announced period (including any announced extension)
+	with no announced decision
+	is considered a de-facto <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑥">Team decision</a> to abandon the proposal.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤①">Team</a> <em class="rfc2119">may</em> revise such a decision
+	by announcing an alternative decision.</p>
+    <p><a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③">Formal Objections</a> filed during the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑧">charter refinement</a> phase
+	are specially handled:</p>
+    <ul>
+     <li data-md>
+      <p>Objections to decisions pertaining to the content of the charter,
+as well as objections to initiating the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③">AC Review</a>,
+are considered registered at the close of the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review④">Advisory Committee Review</a> of the charter,
+and are registered against that <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision②">W3C Decision</a>.</p>
+      <p class="note" role="note"><span class="marker">Note:</span> This enables all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④">Formal Objections</a> on the same proposed <a data-link-type="dfn" href="#charter" id="ref-for-charter⑦">charter</a> to be handled together.</p>
+     <li data-md>
+      <p>Objections to abandoning the proposal or to extending the refinement period can be appealed only if 5 or more Members,
+through their <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑤">Advisory Committee representative</a>,
+formally object to the decision within 8 weeks of the decision.
+In this case,
+the <a data-link-type="dfn" href="#team" id="ref-for-team⑤②">Team</a> <em class="rfc2119">must</em> do one of the following:</p>
+      <ul>
+       <li data-md>
+        <p>Abide by the objectors' request, if they all agree on the
+alternative course of action (e.g., to abandon,
+extend, or complete charter refinement).</p>
+       <li data-md>
+        <p>Initiate an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑤">AC Review</a> to formally solicit the input of
+the community and take a W3C Decision on the subsequent
+course of action.</p>
+       <li data-md>
+        <p>Convene a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③">Council</a> to decide the subsequent course of action.</p>
+      </ul>
+      <p>(No action is required to be taken when fewer than 5 members object.)</p>
+     <li data-md>
+      <p>Any other objections are processed normally (See <a href="#addressing-fo">§ 5.6 Addressing Formal Objections</a>).</p>
+    </ul>
+    <h3 class="heading settled" data-level="4.3" id="WGCharter"><span class="secno">4.3. </span><span class="content"> Content of a Charter</span><a class="self-link" href="#WGCharter"></a></h3>
+    <p>A Working Group or Interest Group <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="charter">charter</dfn> <em class="rfc2119">must</em> include all of the following information.</p>
+    <ul>
+     <li> The group’s mission
+			(e.g., develop a technology or process, review the work of other groups). 
+     <li> The scope of the group’s work and criteria for success. 
+     <li> The duration of the proposed charter for the group. 
+     <li> The nature of any deliverables (technical reports, reviews of the deliverables of other groups, or software). 
+     <li>
+       Expected milestone dates where available. 
+      <p class="note" role="note"><span class="marker">Note:</span> A charter does not need to include
+			schedules for review of other group’s deliverables.</p>
+     <li> The process for the group to approve the release of deliverables
+			(including intermediate results). 
+     <li> Any dependencies by groups within or outside of W3C on the deliverables of this group.
+			For any dependencies, the charter <em class="rfc2119">must</em> specify
+			the mechanisms for communication about the deliverables. 
+     <li> Any dependencies of this group on other groups within or outside of W3C.
+			Such dependencies include interactions with <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a>. 
+     <li> The <a href="#confidentiality-levels">level of confidentiality</a> of the group’s proceedings and deliverables. 
+     <li> The name and affiliation of the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑤">Chair</a> or co-Chairs. 
+     <li> Meeting mechanisms and expected frequency. 
+     <li> If known,
+			the date of the first <a href="#ftf-meeting" id="ref-for-ftf-meeting①">face-to-face meeting</a>.
+			The date of the first face-to-face meeting of a proposed group <em class="rfc2119">must not</em> be sooner than <span class="time-interval">eight weeks</span> after the date of the proposal. 
+     <li> Communication mechanisms to be employed within the group,
+			between the group and the rest of W3C,
+			and with the general public. 
+     <li> Any voting procedures or requirements
+			other than those specified in <a href="#Votes">§ 5.2.3 Deciding by Vote</a>. 
+     <li> An estimate of the expected time commitment from participants. 
+     <li> The expected time commitment and level of involvement by the Team
+			(e.g., to track developments,
+			write and edit technical reports,
+			develop code,
+			or organize pilot experiments). 
+     <li> Intellectual property information.
+			What are the intellectual property (including patents and copyright)
+			considerations affecting the success of the Group?
+			In particular, is there any reason to believe
+			that it will be difficult to meet the Royalty-Free licensing goals
+			in “Licensing Goals for W3C Specifications”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>? 
+    </ul>
+    <p>See also the charter requirements in “Licensing Goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p>For every Recommendation Track deliverable
+	that continues work on a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report">technical report</a> published under any other Charter (including a predecessor group of the same name),
+	for which there is at least an existing <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd">First Public Working Draft</a> the description of that deliverable in the proposed charter of the adopting Working Group <em class="rfc2119">must</em> provide the following information:</p>
+    <ul>
+     <li> The title,
+			stable URL,
+			and publication date of the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD">Working Draft</a> or other Recommendation-track document
+			that will serve as the basis for work on the deliverable
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="adopted-draft">Adopted Draft</dfn>”); 
+     <li> The title,
+			stable URL,
+			and publication date of the document
+			that was used as the basis for its most recent Exclusion Opportunity
+			as per
+			the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+			(labeled “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft">Exclusion Draft</dfn>”); and 
+     <li> The stable URL of the Working Group charter
+			under which the Exclusion Draft was published
+			(labeled the “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="exclusion-draft-charter">Exclusion Draft Charter</dfn>”). 
+    </ul>
+    <p>All of the above data <em class="rfc2119">must</em> be identified
+	in the adopting Working Group’s charter using the labels indicated.</p>
+    <p>The <a data-link-type="dfn" href="#adopted-draft" id="ref-for-adopted-draft">Adopted Draft</a> and the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft">Exclusion Draft</a> <em class="rfc2119">must</em> each be adopted in their entirety and without any modification.
+	The proposed charter <em class="rfc2119">must</em> state
+	the dates on which the Exclusion Opportunity
+	that arose on publishing the <a data-link-type="dfn" href="#exclusion-draft" id="ref-for-exclusion-draft①">Exclusion Draft</a> began and ended.
+	As per “Joining an Already Established Working Group”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	this potentially means that exclusions can only be made immediately on joining a Working Group.</p>
+    <p id="ig-charter-participation">An Interest Group charter <em class="rfc2119">may</em> include provisions regarding participation,
+	including specifying
+	that the <span id="ig-mail-only">only requirement for participation (by anyone) in
+	the Interest Group is subscription to the Interest Group mailing list</span>.
+	This type of Interest Group <em class="rfc2119">may</em> have <a href="#public-participant-ig" id="ref-for-public-participant-ig">public participants</a>. </p>
+    <p>A charter <em class="rfc2119">may</em> include
+	provisions other than those required by this document.
+	The charter <em class="rfc2119">should</em> highlight
+	whether additional provisions impose constraints
+	beyond those of the W3C 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>
+    <h3 class="heading settled" data-level="4.4" id="CharterReview"><span class="secno">4.4. </span><span class="content"> Charter Review and Approval</span><a class="self-link" href="#CharterReview"></a></h3>
+    <h4 class="heading settled" data-level="4.4.1" id="charter-major-changes"><span class="secno">4.4.1. </span><span class="content"> New Charters and Major Changes</span><a class="self-link" href="#charter-major-changes"></a></h4>
+    <p>Any new <a data-link-type="dfn" href="#charter" id="ref-for-charter⑧">charter</a> (including re-chartering of existing <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group②">chartered groups</a>)
+	and any change that is not a <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes">minor change</a> (per <a href="#charter-minor-changes">§ 4.4.2 Minor Changes to Active Charters</a>) to an already-approved <a data-link-type="dfn" href="#charter" id="ref-for-charter⑨">charter</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑨">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG③">Interest Group</a> <em class="rfc2119">must</em> be approved by a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision③">W3C Decision</a> following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑥">AC Review</a> of that <a data-link-type="dfn" href="#charter" id="ref-for-charter①⓪">charter</a>.
+	Modifications to a <a data-link-type="dfn" href="#charter" id="ref-for-charter①①">charter</a> <em class="rfc2119">should</em> have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑤">consensus</a> of the group.</p>
+    <p>The review period <em class="rfc2119">must</em> be at least 28 days.
+	Any <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑥">Advisory Committee representative</a> <em class="rfc2119">may</em> request an extended review period
+	in response to the Call for Review;
+	upon receipt of any such request,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤③">Team</a> <em class="rfc2119">must</em> extend the review period
+	to at least 60 days.</p>
+    <p>The Call for Review of a modified charter <em class="rfc2119">must</em> highlight important changes
+	(e.g., regarding changes in scope, deliverables, or resource allocation)
+	and <em class="rfc2119">must</em> include rationale for those changes.</p>
+    <p>The Call for Review of a new or modified charter <em class="rfc2119">must</em> include a disposition of comments received during the <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement⑨">charter refinement</a> process,
+	highlighting any issues that were closed despite sustained objections.</p>
+    <h4 class="heading settled" data-level="4.4.2" id="charter-minor-changes"><span class="secno">4.4.2. </span><span class="content"> Minor Changes to Active Charters</span><a class="self-link" href="#charter-minor-changes"></a></h4>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change">Editorial changes</a> or <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change">substantive changes</a> to a <a data-link-type="dfn" href="#charter" id="ref-for-charter①②">charter</a> (including <a href="#charter-extension">extensions</a>)
+	that do not affect the scope of the group’s work
+	or the way the group functions in any significant way
+	are deemed <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minor-changes">minor changes</dfn> and <em class="rfc2119">may</em> be approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑦">Team Decision</a>,
+	in which case they do not require <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①⓪">charter refinement</a> nor <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑦">Advisory Committee Review</a>.
+	Any change to the scope of the <a data-link-type="dfn" href="#charter" id="ref-for-charter①③">charter</a> or addition of a new <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track">REC track</a> deliverable
+	that does not fall within the scope of an existing deliverable
+	is a major, not <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes①">minor</a>, change.
+	The following are examples of <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes②">minor changes</a>:
+	the renaming or restructuring (e.g. splitting or combining) of existing in-scope deliverables,
+	the addition of new <a href="#note-track">Note track</a> deliverables that help explain the group’s work,
+	a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑥">Staff Contact</a>,
+	or a change of <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑥">Chair</a>. <a data-link-type="dfn" href="#minor-changes" id="ref-for-minor-changes③">Minor changes</a>, other than a change of <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑦">Staff Contact</a>, <em class="rfc2119">should</em> have the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑥">consensus</a> of the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤④">Team</a> <em class="rfc2119">may</em> nevertheless choose
+	to initiate <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①①">charter refinement</a> and/or <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑧">Advisory Committee Review</a> when it thinks the changes would benefit from more scrutiny or explicit buy-in.</p>
+    <p>Though <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review⑨">Advisory Committee Review</a> is not required,
+	such changes <em class="rfc2119">must</em> still be announced
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①②">Advisory Committee</a>,
+	and to participants in the <a href="#wgparticipant" id="ref-for-wgparticipant①">Working</a> or <a href="#igparticipant" id="ref-for-igparticipant①">Interest</a> Group,
+	and a rationale must be provided.</p>
+    <h3 class="heading settled" data-level="4.5" id="cfp"><span class="secno">4.5. </span><span class="content"> Call for Participation in a Chartered Group</span><a class="self-link" href="#cfp"></a></h3>
+    <p>Deciding whether to adopt a proposed <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⓪">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG④">Interest Group</a> <a data-link-type="dfn" href="#charter" id="ref-for-charter①④">charter</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision④">W3C Decision</a>.
+	Charters <em class="rfc2119">may</em> be amended based on review comments
+	per <a href="#ACReviewAfter">§ 5.7.2 Determining the W3C Decision</a> before the Call for Participation.</p>
+    <p>If the decision is to charter the group,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑤">Team</a> <em class="rfc2119">must</em> issue a Call for Participation to the Advisory Committee.
+	For a new group, this announcement officially creates the group.
+	The announcement <em class="rfc2119">must</em> include a reference to the <a href="#WGCharter">charter</a>,
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑦">Chair(s)</a>,
+	and the name(s) of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑧">Staff Contact(s)</a>.</p>
+    <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).
+	When a group is re-chartered,
+	individuals participating in the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①①">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑤">Interest Group</a> before the new Call for Participation
+	may attend any meetings held within forty-five (45) days of the Call for Participation
+	even if they have not yet formally rejoined the group
+	(i.e., committed to the terms of the charter and patent policy).</p>
+    <p>Advisory Committee representatives <em class="rfc2119">may</em> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against the decision to create
+	or substantially modify
+	a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.6" id="charter-extension"><span class="secno">4.6. </span><span class="content"> Charter Extension</span><a class="self-link" href="#charter-extension"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑥">Team</a> <em class="rfc2119">may</em> decide
+	to extend a Working Group or Interest Group charter
+	with no other substantive modifications.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑦">Team</a> <em class="rfc2119">must</em> announce
+	such <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="charter extension" id="dfn-charter-extension">extensions</dfn> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①③">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate the new duration.
+	The announcement <em class="rfc2119">must</em> also include rationale for the extension,
+	a reference to the <a href="#WGCharter">charter</a>,
+	and the Group homepage
+	(which includes at least
+	the name(s) of the group’s <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑧">Chair(s)</a>,
+	the name of the <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact⑨">Staff Contact</a>,
+	and instructions for joining the group).</p>
+    <p>After a charter extension,
+	Advisory Committee representatives
+	and the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs①⑨">Chair</a> 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> initiate
+	an <a href="#ACAppeal">Advisory Committee Appeal</a> against a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑧">Team decision</a> regarding the extension of a Working Group or Interest Group charter.</p>
+    <h3 class="heading settled" data-level="4.7" id="GeneralTermination"><span class="secno">4.7. </span><span class="content"> Chartered Group Closure</span><a class="self-link" href="#GeneralTermination"></a></h3>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①②">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑥">Interest Group</a> charter specifies a duration for the group.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑧">Team</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑦">TAG</a>, or the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②③">AB</a> <em class="rfc2119">may</em> propose to close a group
+	prior to the date specified in the charter in any of the following circumstances:</p>
+    <ul>
+     <li data-md>
+      <p>There are insufficient member resources to produce chartered deliverables
+or to maintain the group,
+according to priorities established within W3C.</p>
+     <li data-md>
+      <p>A <a data-link-type="dfn" href="https://www.w3.org/policies/patent-policy/#patent-advisory-group" id="ref-for-patent-advisory-group">Patent Advisory Group</a> concluded that the work <em class="rfc2119">should</em> be terminated.</p>
+     <li data-md>
+      <p>The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑧">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②④">AB</a> determined that continuing operation of the chartered group or its work
+would be detrimental to W3C or its mission.</p>
+     <li data-md>
+      <p>The group produced all chartered deliverables ahead of schedule.</p>
+    </ul>
+    <p>Such a proposal to close a group must be accompanied by rationale,
+	and the proposal must be confirmed by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⓪">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑤">W3C Decision</a>.</p>
+    <p>Closing a Working Group has implications
+	with respect to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h2 class="heading settled" data-level="5" id="decisions"><span class="secno">5. </span><span class="content"> Decisions</span><a class="self-link" href="#decisions"></a></h2>
+    <p>W3C attempts to resolve issues through dialog.
+	Individuals who disagree strongly with a decision <em class="rfc2119">should</em> register with the Chair any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑤">Formal Objections</a>.</p>
+    <h3 class="heading settled" data-level="5.1" id="decision-types"><span class="secno">5.1. </span><span class="content"> Types of Decisions</span><a class="self-link" href="#decision-types"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⓪">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①③">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑦">Interest Group</a> has the prerogative
+	to make certain decisions based on their own judgment.
+	Such decisions are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="chair-decisions">chair decisions</dfn>.</p>
+    <p>In contrast,
+	decisions taken by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②①">Chair</a> of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①④">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑧">Interest Group</a> on the basis of having assessed the <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑦">consensus</a> of the group
+	or following a vote (see <a href="#Votes">§ 5.2.3 Deciding by Vote</a>)
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="group decision | resolution" id="group-decision">group decisions</dfn> (also known as group “resolutions”).</p>
+    <p>Decisions made by members of the <a data-link-type="dfn" href="#team" id="ref-for-team⑤⑨">Team</a> in connection with this Process,
+	based on their own individual or collective judgement,
+	are called <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Team Decision | Team&apos;s Decision" data-noexport id="team-decision">Team Decisions</dfn>.</p>
+    <p>In contrast,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-w3c-decision">W3C decision</dfn> is
+	determined by the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⓪">Team</a> on behalf of the W3C community
+	by <a href="#ACReviewAfter">assessing the consensus of the W3C Community</a> after an <a href="#ACReview">Advisory Committee review</a>.</p>
+    <h3 class="heading settled" data-level="5.2" id="consensus-building"><span class="secno">5.2. </span><span class="content"> Consensus Building</span><a class="self-link" href="#consensus-building"></a></h3>
+    <h4 class="heading settled" data-level="5.2.1" id="Consensus"><span class="secno">5.2.1. </span><span class="content"> Consensus</span><a class="self-link" href="#Consensus"></a></h4>
+    <p>Consensus is a core value of W3C.
+	To promote consensus,
+	the W3C process requires Chairs to ensure
+	that groups consider all legitimate views and objections,
+	and endeavor to resolve them,
+	whether these views and objections are expressed by the active participants of the group
+	or by others
+	(e.g., another W3C group,
+	a group in another organization,
+	or the general public).
+	Decisions <em class="rfc2119">may</em> be made during meetings
+	(<a href="#ftf-meeting" id="ref-for-ftf-meeting②">face-to-face</a> or <a href="#distributed-meeting" id="ref-for-distributed-meeting">distributed</a>)
+	as well as through <a href="#discussion-archiving">persistent text-based discussions</a>.</p>
+    <p>The following terms are used in this document
+	to describe the level of support for a decision among a set of eligible individuals:</p>
+    <dl>
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Consensus">Consensus</dfn>: 
+     <dd> A substantial number of individuals in the set
+			support the decision
+			and there is no sustained objection from anybody in the set.
+			Individuals in the set <em class="rfc2119">may</em> abstain.
+			Abstention is either an explicit expression of no opinion
+			or silence by an individual in the set. 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Unanimity">Unanimity</dfn>: 
+     <dd> The particular case of <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑧">consensus</a> where all individuals in the set support the decision
+			(i.e., no individual in the set abstains). 
+     <dt><dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-Dissent">Dissent</dfn>: 
+     <dd> At least one individual in the set sustains an objection. 
+    </dl>
+    <p class="note" role="note"><span class="marker">Note:</span> A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑥">Formal Objection</a> always indicates a sustained objection,
+	but isn’t necessary to express it
+	(except in the context of formal <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①①">AC Reviews</a>).
+	Disagreement with a proposed decision,
+	however, does not always rise to the level of sustained objection,
+	as individuals could be willing to accept a decision
+	while expressing disagreement.</p>
+    <p>By default, the set of individuals eligible to participate in a decision is the set of group participants.
+	The Process Document does not require a quorum for decisions
+	(i.e., the minimal number of eligible participants required to be present before the Chair can call a question).
+	A charter <em class="rfc2119">may</em> include a quorum requirement for consensus decisions.</p>
+    <p>Where <a data-link-type="dfn" href="#def-Unanimity" id="ref-for-def-Unanimity">unanimity</a> is not possible,
+	a group <em class="rfc2119">should</em> strive to make <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus⑨">consensus</a> decisions
+	where there is significant support and few abstentions.
+	The Process Document does not require a particular percentage of eligible participants
+	to agree to a motion in order for a decision to be made.
+	To avoid decisions where there is widespread apathy,
+	(i.e., little support and many abstentions),
+	groups <em class="rfc2119">should</em> set minimum thresholds of active support before a decision can be recorded.
+	The appropriate percentage <em class="rfc2119">may</em> vary depending on the size of the group
+	and the nature of the decision.
+	A charter <em class="rfc2119">may</em> include threshold requirements for consensus decisions.
+	For instance, a charter might require a supermajority of eligible participants
+	(i.e., some established percentage above 50%)
+	to support certain types of consensus decisions.</p>
+    <div class="note" role="note">
+      Note: Chairs have substantial flexibility
+	in how they obtain and assess consensus among their groups.
+	Unless otherwise constrained by charter,
+	they can use modes including but not limited to explicit calls for consensus,
+	polls of participants,
+	“lazy consensus” in which lack of objection after sufficient notice is taken as assent;
+	they can also delegate and empower a document editor
+	to assess consensus on their behalf,
+	whether in general
+	or for specific pre-determined circumstances
+	(e.g. in non-controversial situations, for specific types of issues, etc.). 
+     <p>If questions or disagreements arise,
+	the final determination of consensus remains with the chair.</p>
+    </div>
+    <h4 class="heading settled" data-level="5.2.2" id="managing-dissent"><span class="secno">5.2.2. </span><span class="content"> Managing Dissent</span><a class="self-link" href="#managing-dissent"></a></h4>
+    <p>In some cases, even after careful consideration of all points of view,
+	a group might find itself unable to reach consensus.
+	The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②②">Chair</a> <em class="rfc2119">may</em> record a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent">dissent</a> so that the group can make progress
+	(for example, to produce a deliverable in a timely manner).
+	Dissenters cannot stop a group’s work
+	simply by saying that they cannot live with a decision.
+	When the Chair believes that the Group has duly considered
+	the legitimate concerns of dissenters as far as is possible and reasonable,
+	the group <em class="rfc2119">should</em> move on.</p>
+    <p>Groups <em class="rfc2119">should</em> favor proposals that create the weakest objections.
+	This is preferred over proposals that are supported by a large majority
+	but that cause strong objections from a few people.
+	As part of making a decision where there is <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent①">dissent</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②③">Chair</a> is expected to be aware of which participants work for the same
+	(or <a href="#MemberRelated">related</a>)
+	Member organizations and weigh their input accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Dissenters can escalate their sustained objection to a decision by registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑦">Formal Objection</a>.</p>
+    <h4 class="heading settled" data-level="5.2.3" id="Votes"><span class="secno">5.2.3. </span><span class="content"> Deciding by Vote</span><a class="self-link" href="#Votes"></a></h4>
+    <p>A group <em class="rfc2119">should</em> only conduct a vote to resolve a <em>substantive issue</em> after the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②④">Chair</a> has determined that all available means of <a href="#Consensus">reaching consensus</a> through technical discussion and compromise have failed,
+	and that a vote is necessary to break a deadlock.
+	In this case the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑤">Chair</a> <em class="rfc2119">must</em> record
+	(e.g., in the <a data-link-type="dfn" href="#minutes" id="ref-for-minutes②">minutes</a> of the meeting or in an archived email message):</p>
+    <ul>
+     <li> an explanation of the issue being voted on; 
+     <li> the decision to conduct a vote
+			(e.g., a simple majority vote) to resolve the issue; 
+     <li> the outcome of the vote; 
+     <li> any Formal Objections. 
+    </ul>
+    <p>In order to vote to resolve a substantive issue,
+	an individual <em class="rfc2119">must</em> be a group <a data-link-type="dfn" href="#participant" id="ref-for-participant①">participant</a>.
+	Each organization represented in the group <em class="rfc2119">must</em> have at most one vote,
+	even when the organization is represented by several participants in the group
+	(including Invited Experts).
+	For the purposes of voting:</p>
+    <ul>
+     <li> A Member or group of <a href="#MemberRelated">related Members</a> is considered a single organization. 
+     <li> The <a href="#Team">Team</a> is considered an organization. 
+    </ul>
+    <p>Unless the charter states otherwise, <a href="#invited-expert-wg">Invited Experts</a> <em class="rfc2119">may</em> vote.</p>
+    <p>If a participant is unable to attend a vote,
+	that individual <em class="rfc2119">may</em> authorize anyone at the meeting
+	to act as a proxy.
+	The absent participant <em class="rfc2119">must</em> inform the Chair in writing
+	who is acting as proxy, with written instructions on the use of the proxy.
+	For a Working Group or Interest Group,
+	see the related requirements regarding an individual
+	who attends a meeting as a <a href="#mtg-substitute" id="ref-for-mtg-substitute">substitute</a> for a participant.</p>
+    <p>A group <em class="rfc2119">may</em> vote for other purposes than to resolve a substantive issue.
+	For instance, the Chair often conducts a “straw poll” vote
+	as a means of determining whether there is consensus about a potential decision.</p>
+    <p>A group <em class="rfc2119">may</em> also vote to make a process decision.
+	For example,
+	it is appropriate to decide by simple majority
+	whether to hold a meeting in San Francisco or San Jose
+	(there’s not much difference geographically).
+	When simple majority votes are used to decide minor issues,
+	voters are <em class="rfc2119">not required</em> to state the reasons for votes,
+	and the group is <em class="rfc2119">not required</em> to record individual votes.</p>
+    <p>A group charter <em class="rfc2119">may</em> include formal voting procedures
+	(e.g., quorum or threshold requirements)
+	for making decisions about substantive issues.</p>
+    <h3 class="heading settled" data-level="5.3" id="formal-address"><span class="secno">5.3. </span><span class="content"> Formally Addressing an Issue</span><a class="self-link" href="#formal-address"></a></h3>
+    <p>In the context of this document,
+	a group has <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="formally-addressed">formally addressed</dfn> an issue when it has sent a public, substantive response
+	to the reviewer who raised the issue.
+	A substantive response is expected to include rationale for decisions
+	(e.g., a technical explanation, a pointer to charter scope, or a pointer to a requirements document).
+	The adequacy of a response is measured
+	against what a W3C reviewer would generally consider to be technically sound.
+	If a group believes that a reviewer’s comments result from a misunderstanding,
+	the group <em class="rfc2119">should</em> seek clarification before reaching a decision.</p>
+    <p>As a courtesy,
+	both Chairs and reviewers <em class="rfc2119">should</em> set expectations
+	for the schedule of responses and acknowledgments.
+	The group <em class="rfc2119">should</em> reply to a reviewer’s initial comments
+	in a timely manner.
+	The group <em class="rfc2119">should</em> set a time limit
+	for acknowledgment by a reviewer of the group’s substantive response;
+	a reviewer cannot block a group’s progress.
+	It is common for a reviewer to require a week or more
+	to acknowledge and comment on a substantive response.
+	The group’s responsibility to respond to reviewers
+	does not end once a reasonable amount of time has elapsed.
+	However, reviewers <em class="rfc2119">should</em> realize
+	that their comments will carry less weight
+	if not sent to the group in a timely manner.</p>
+    <p>Substantive responses <em class="rfc2119">should</em> be recorded.
+	The group <em class="rfc2119">should</em> maintain an accurate summary
+	of all substantive issues and responses to them
+	(e.g., in the form of an issues list with links to mailing list archives).</p>
+    <h3 class="heading settled" data-level="5.4" id="WGChairReopen"><span class="secno">5.4. </span><span class="content"> Reopening a Decision When Presented With New Information</span><a class="self-link" href="#WGChairReopen"></a></h3>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑥">Chair</a> <em class="rfc2119">may</em> reopen a decision
+	when presented with new information, including:</p>
+    <ul>
+     <li> additional technical information, 
+     <li> comments by email from participants who were unable to attend a scheduled meeting, 
+     <li> comments by email from meeting attendees
+			who chose not to speak out during a meeting
+			(e.g., so they could confer later with colleagues or for cultural reasons). 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑦">Chair</a> <em class="rfc2119">should</em> record
+	that a decision has been reopened,
+	and <em class="rfc2119">must</em> do so upon request from a group participant.</p>
+    <h3 class="heading settled" data-level="5.5" id="registering-objections"><span class="secno">5.5. </span><span class="bs-old-id" id="chair-decision-appeal"></span><span class="bs-old-id" id="wg-decision-appeal"></span><span class="bs-old-id" id="WGAppeals"></span><span class="bs-old-id" id="WGArchiveMinorityViews"></span><span class="content"> Registering Formal Objections</span><a class="self-link" href="#registering-objections"></a></h3>
+    <p>Any individual
+	(regardless of whether they are associated with a Member) <em class="rfc2119">may</em> appeal any decision made in connection with this Process
+	(except those having a different appeal process)
+	by registering a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="FormalObjection">Formal Objection</dfn> with the <a data-link-type="dfn" href="#team" id="ref-for-team⑥①">Team</a>.
+	Group participants <em class="rfc2119">should</em> inform
+	their <a data-link-type="dfn" href="#TeamContact" id="ref-for-TeamContact①⓪">Staff Contact</a> as well as the group’s Chair(s).
+	The Staff Contact <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑦">CEO</a> when a group participant has also raised concerns about due process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> In this document, the term <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑧">Formal Objection</a> is used to emphasize this process implication:
+	Formal Objections receive formal consideration and a formal response.
+	The word “objection” used alone has its ordinary English connotations.
+	See <a href="#consensus-building">§ 5.2 Consensus Building</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection⑨">Formal Objection</a> <em class="rfc2119">must</em> include a summary of
+	the issue (whether technical or procedural),
+	the decision being appealed,
+	and the rationale for the objection.
+	It <em class="rfc2119">should</em> cite technical arguments
+	and propose changes that would remove the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⓪">Formal Objection</a>;
+	these proposals <em class="rfc2119">may</em> be vague or incomplete. <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①①">Formal Objections</a> that do not provide substantive arguments
+	or rationale are unlikely to receive serious consideration.
+	Counter-arguments,
+	rationales,
+	and decisions <em class="rfc2119">should</em> also be recorded.</p>
+    <p>No later than when the <a href="#team-fo-mediation">relevant Council is initiated</a>,
+	a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①②">Formal Objection</a> against a decision regarding a publicly-available document <em class="rfc2119">must</em> be made <a href="#confidentiality-change">publicly available</a>;
+	likewise, a record of each <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①③">Formal Objection</a> against a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①">Member-visible</a> decision <em class="rfc2119">must</em> be made <a href="#confidentiality-change">available to Members</a>.
+	A Call for Review to the Advisory Committee <em class="rfc2119">must</em> identify any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①④">Formal Objections</a> related to that review.
+	These requirements are waived
+	if the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑤">Formal Objection</a> is resolved to the satisfaction of the objector
+	before its <a href="#confidentiality-change">confidentiality is changed</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑥">Formal Objections</a> against matter in a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①">technical report</a> <a href="#adv-verif-reqs">are expected to be fully addressed</a> before <a href="#rec-advance">requesting advancement</a> of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②">technical report</a>.</p>
+    <p>A <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑦">Formal Objection</a> filed during an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①②">Advisory Committee Review</a> is considered registered at the close of the review period.</p>
+    <p>Registering a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑧">Formal Objection</a> initiates the process of <a href="#addressing-fo">addressing the Formal Objection</a>.
+	The resolution of a recorded Formal Objection—​whether by a Council decision, adoption of a consensus proposal, retraction of the Formal Objection, etc.—​must be recorded and made available at the same level of visibility as the record of the Formal Objection itself.</p>
+    <h3 class="heading settled" data-level="5.6" id="addressing-fo"><span class="secno">5.6. </span><span class="content"> Addressing Formal Objections</span><a class="self-link" href="#addressing-fo"></a></h3>
+    <h4 class="heading settled" data-level="5.6.1" id="team-fo-mediation"><span class="secno">5.6.1. </span><span class="content"> Investigation and Mediation by the Team</span><a class="self-link" href="#team-fo-mediation"></a></h4>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑥②">Team</a> considers the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection①⑨">Formal objection</a>,
+	researches the question,
+	interviews parties,
+	and so on,
+	to make sure the problem and the various viewpoints are well understood,
+	and to the extent possible,
+	to arrive at a recommended disposition.</p>
+    <p>In parallel, the Team <em class="rfc2119">should</em> start the steps necessary
+	to <a href="#council-convention">convene</a> a Council.</p>
+    <p>If the <a data-link-type="dfn" href="#team" id="ref-for-team⑥③">Team</a> can resolve the issue
+	to the satisfaction of the individual that filed the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⓪">Formal Objection</a>,
+	the individual withdraws the objection and the disposition process terminates.</p>
+    <p>Otherwise,
+	upon concluding that consensus cannot be found,
+	and no later than 90 days after the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②①">Formal Objection</a> being registered,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑥④">Team</a> <em class="rfc2119">must</em> deliver to the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council④">Council</a> a report
+	documenting its findings and attempts to find consensus,
+	and hand over the matter to the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑤">W3C Council</a>.</p>
+    <h4 class="heading settled" data-level="5.6.2" id="council"><span class="secno">5.6.2. </span><span class="content"> W3C Council</span><a class="self-link" href="#council"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-local-lt="Council" id="w3c-council">W3C Council</dfn> is the body convened to resolve <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②②">Formal Objections</a> by combining the capabilities and perspectives of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑤">AB</a>, the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group②⑨">TAG</a>, and the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑤">Team</a>,
+	and is tasked with doing so in the best interests of the Web and W3C.</p>
+    <h5 class="heading settled" data-level="5.6.2.1" id="council-composition"><span class="secno">5.6.2.1. </span><span class="content"> Council Composition</span><a class="self-link" href="#council-composition"></a></h5>
+    <p>Each <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑥">W3C Council</a> is composed of the following members (excepting any <a href="#council-participation">renounced or dismissed</a>):</p>
+    <ul>
+     <li data-md>
+      <p>the <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑧">CEO</a> or their chosen <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑥">Team</a> delegate</p>
+     <li data-md>
+      <p>the members of the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑥">Advisory Board</a></p>
+     <li data-md>
+      <p>the elected and appointed members of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⓪">Technical Architecture Group</a></p>
+    </ul>
+    <p>Participation in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑦">W3C Council</a> <em class="rfc2119">must not</em> require attendance of <a data-link-type="dfn" href="#ftf-meeting" id="ref-for-ftf-meeting③">face-to-face meetings</a>.</p>
+    <p>A distinct instance of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑧">W3C Council</a> is convened for each decision being appealed or objected to.
+	The list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council⑨">Council</a> members evolves
+	as <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑦">AB</a> and <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③①">TAG</a> terms start and end
+	until <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed">dismissal</a> and <a data-link-type="dfn" href="#renounce" id="ref-for-renounce">renunciation</a> are concluded,
+	at which point the membership of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⓪">Council</a> is fixed.
+	However, if the number of active members in a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①①">Council</a> falls so low as to hinder effective and balanced deliberations,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair">Council Chair</a> <em class="rfc2119">should</em> dissolve the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①②">Council</a> and call for a new one to be convened.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> TAG and AB elections have no effect on the Council’s membership
+	once it is fixed.</p>
+    <p>A <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑦">Team</a> member is assigned
+	to act as the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-staff-contact"><span class="bs-old-id" id="council-team-contact"></span>Council Staff Contact</dfn>,
+	to support this Council
+	and to facilitate adherence to this Process.</p>
+    <h5 class="heading settled" data-level="5.6.2.2" id="council-delegation"><span class="secno">5.6.2.2. </span><span class="content"> Extraordinary Delegation</span><a class="self-link" href="#council-delegation"></a></h5>
+    <p>In extraordinary cases,
+	if they feel a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①③">Council</a> would not be the appropriate deciding body,
+	a member of the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑧">Team</a> (particularly the Legal Counsel) or
+	any potential Council member
+	may suggest that the decision for that specific Formal Objection be delegated
+	to the W3C Board of Directors,
+	to an officer of its corporation (such as the Legal Counsel),
+	or to one or more specific individuals from the <a data-link-type="dfn" href="#team" id="ref-for-team⑥⑨">Team</a>.
+	The potential Council members then <em class="rfc2119">may</em> confidentially discuss
+	and <em class="rfc2119">must</em> vote
+	whether to delegate the decision for that specific <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②③">Formal Objection</a>.
+	A decision to delegate <em class="rfc2119">must</em> be supported by a two-thirds supermajority vote
+	(i.e., at least twice as many votes in favor as against).
+	Delegation in such cases cannot be later revoked.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⓪">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①④">Advisory Committee</a> when a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②④">Formal Objection</a> has been delegated,
+	and to whom it has been delegated.</p>
+    <h5 class="heading settled" data-level="5.6.2.3" id="council-participation"><span class="secno">5.6.2.3. </span><span class="content"> Council Participation, Dismissal, and Renunciation</span><a class="self-link" href="#council-participation"></a></h5>
+    <p>A potential Council member may be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="dismissed | dismiss | dismissal" data-noexport id="dismissed">dismissed</dfn> from the Council.
+	In order to apply consistent criteria,
+	the potential Council members decide collectively
+	which reasons against service
+	rise to a sufficient level for a potential member to be <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed①">dismissed</a>.
+	No-one is automatically dismissed,
+	and individual recusal is not used in the Council. <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed②">Dismissal</a> applies to an individual person in the context of a specific Council,
+	and should be used rarely in order to preserve the greatest diversity on the Council.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> A W3C Council is a deliberative body whose purpose is
+	to find the best way forward for the Web and for W3C.
+	It is not a judicial body tasked with determining right or wrong.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦①">Team</a> <em class="rfc2119">must</em> draft a list of potential <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①④">Council</a> members,
+	with annotations of possible reasons for dismissal against each one.
+	The W3C community,
+	including members and team, and potential council members, <em class="rfc2119">must</em> be given an opportunity to contribute possible reasons to this list.
+	Affected members <em class="rfc2119">must</em> be given
+	an opportunity to respond to such comments about themselves.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦②">Team</a> may report comments verbatim
+	or may paraphrase them while preserving their intent;
+	they may also elide inappropriate comments,
+	such as any that violate applicable laws or the <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a>.</p>
+    <p>Before a Council forms,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑦③">Team</a> presents the entire list of potential members
+	and collected reasons and responses
+	to the potential Council members,
+	who then consider for each potential member
+	whether that individual’s participation
+	would compromise the integrity of the Council decision,
+	and vote whether to dismiss that potential member.
+	No one is allowed to vote on their own dismissal;
+	each dismissal is enacted if there are at least as many ballots for as against.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since dismissal is individual,
+	when the decision being objected to was made by the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③②">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑧">AB</a> acting as a body,
+	the entire <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③③">TAG</a> or <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board②⑨">AB</a> is not expected to be dismissed.</p>
+    <p>An individual <em class="rfc2119">may</em> also <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="renounce | renunciation" data-noexport id="renounce">renounce</dfn> their seat on a Council, for strong reason,
+	such as being forbidden by their employer to serve. The individual chooses the extent to which they explain
+	their renunciation.
+	Renunciation is disqualification from participation,
+	not abstention,
+	and <em class="rfc2119">should not</em> be used
+	to excuse an absence of participation.</p>
+    <p>Any person who has been <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed③">dismissed</a> or who <a data-link-type="dfn" href="#renounce" id="ref-for-renounce①">renounces</a> their seat
+	does not receive <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑤">Council</a> materials,
+	take part in its deliberations,
+	help in the determination of consensus,
+	or vote.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑥">W3C Council</a> <em class="rfc2110">may</em> still solicit and hear their testimony,
+	as they can of anyone else in the W3C community.</p>
+    <h5 class="heading settled" data-level="5.6.2.4" id="council-short-circuit"><span class="secno">5.6.2.4. </span><span class="content"> Short Circuit</span><a class="self-link" href="#council-short-circuit"></a></h5>
+    <p>The full Council process <em class="rfc2119">may</em> be short-circuited if
+	the Team recommends a resolution
+	and potential members of a Council who are not renouncing their seat
+	confirm it by a vote which results in both of the following:</p>
+    <ul>
+     <li data-md>
+      <p>at least 80% of them vote affirmatively to adopt this resolution</p>
+     <li data-md>
+      <p>none of them vote against adopting the resolution</p>
+    </ul>
+    <p>The request for confirmation <em class="rfc2119">must</em> be open for a period of at least two weeks,
+	or until every potential member of the Council not renouncing their seat
+	has voted,
+	whichever is shortest.</p>
+    <p>This step <em class="rfc2119">may</em> be run concurrently with <a href="#council-participation">§ 5.6.2.3 Council Participation, Dismissal, and Renunciation</a> and prior to choosing a <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair①">Chair</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This is intended for exceptional cases
+	that don’t seem to warrant a full Council response
+	because they are, for instance, too trivial, duplicative, etc.</p>
+    <h5 class="heading settled" data-level="5.6.2.5" id="council-chairing"><span class="secno">5.6.2.5. </span><span class="content"> Council Chairing</span><a class="self-link" href="#council-chairing"></a></h5>
+    <p>The <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Council Chair | Council Chair" data-noexport id="w3c-council-chair">Chair</dfn> of each W3C Council is chosen by its members,
+	by consensus if possible,
+	falling back to a vote if that fails.
+	The chair must be a member of that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑦">W3C Council</a>.
+	Chair selection happens during formation of each Council,
+	and <em class="rfc2119">must</em> be re-run
+	if requested by the <a data-link-type="dfn" href="#council-staff-contact" id="ref-for-council-staff-contact">Council Staff Contact</a> or by the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑧">Chair</a> during the Council’s operation.</p>
+    <h5 class="heading settled" data-level="5.6.2.6" id="council-convention"><span class="secno">5.6.2.6. </span><span class="content"> Convening the Council</span><a class="self-link" href="#council-convention"></a></h5>
+    <p>When <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed④">dismissal</a>, <a data-link-type="dfn" href="#renounce" id="ref-for-renounce②">renunciation</a>, and
+	appointment of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair②">W3C Council Chair</a> have concluded,
+	and the <a data-link-type="dfn" href="#team" id="ref-for-team⑦④">Team</a>’s report has been delivered,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑧">W3C Council</a> is considered to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="convened">convened</dfn> and can start <a href="#council-deliberations">deliberations</a>.</p>
+    <p>If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council①⑨">W3C Council</a> has not yet been <a data-link-type="dfn" href="#convened" id="ref-for-convened">convened</a> within 90 days of a Formal Objection
+	being <a href="#registering-objections">registered</a>,
+	the <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs②⑨">Chairs</a> of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③④">TAG</a> and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⓪">AB</a> <em class="rfc2119">may</em> take independent action to ensure
+	that the <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed⑤">dismissal</a>, <a data-link-type="dfn" href="#renounce" id="ref-for-renounce③">renunciation</a>,
+	and <a href="#council-chairing">chair selection</a> processes have been run.
+	If a report from the Team is not delivered within those 90 days,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⓪">Council</a> is considered <a data-link-type="dfn" href="#convened" id="ref-for-convened①">convened</a> upon selection of the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair③">Council Chair</a>.</p>
+    <h5 class="heading settled" data-level="5.6.2.7" id="council-deliberations"><span class="secno">5.6.2.7. </span><span class="content"> Council Deliberations</span><a class="self-link" href="#council-deliberations"></a></h5>
+    <p>Once <a data-link-type="dfn" href="#convened" id="ref-for-convened②">convened</a>,
+	the Council <em class="rfc2119">may</em> conduct additional research or analysis,
+	or request additional information or interviews from anyone,
+	including the Team.</p>
+    <p id="broker-consensus"> The Council <em class="rfc2119">may</em> further attempt to broker consensus on one or more of the formal objections,
+	which, if successful, would allow them to be resolved. </p>
+    <p>Otherwise,
+	after sufficient deliberation,
+	and with due consideration of each argument in the applicable <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑤">Formal Objections</a>,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②①">W3C Council</a> decides whether to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="affirm">affirm</dfn> or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="overturn">overturn</dfn> the decision being objected to.
+	The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②②">W3C Council</a> <em class="rfc2119">may</em> <a data-link-type="dfn" href="#affirm" id="ref-for-affirm">affirm</a> the decision
+	even if it agrees with some of the arguments made as part of a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑥">Formal Objection</a>.
+	When a decision is <a data-link-type="dfn" href="#affirm" id="ref-for-affirm①">affirmed</a>,
+	all Formal Objections against it are said to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="overrule" data-noexport id="overrule">overruled</dfn>.
+	Conversely,
+	aspects of Formal Objections that are found by the Council
+	to justify <a data-link-type="dfn" href="#overturn" id="ref-for-overturn">overturning</a> a decision
+	are said to be <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="upheld">upheld</dfn>.</p>
+    <p id="fo-mitigations"> When <a data-link-type="dfn" href="#overturn" id="ref-for-overturn①">overturning</a> a decision,
+	the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②③">Council</a> <em class="rfc2199">should</em> recommend a way forward.
+	If the overturned decision has already had consequences
+	pertaining to <a data-link-type="dfn" href="#upheld" id="ref-for-upheld">upheld</a> aspects of the Formal Objection(s)
+	(e.g., if the objection concerns material already in a published document)
+	the Council <em class="rfc2119">should</em> suggest how these consequences might be mitigated.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑤">Team</a> is responsible for making sure that adequate mitigations are enacted in a timely fashion;
+	and the <a data-link-type="dfn" href="#upheld" id="ref-for-upheld①">upheld</a> aspects of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑦">Formal Objection(s)</a> (as identified in the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report">Council Report</a>) are not considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fully-addressed">fully addressed</dfn> until then. </p>
+    <p class="note" role="note"><span class="marker">Note:</span> This does not create new powers for the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑥">Team</a>,
+	such as the ability to “unpublish” documents.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑦">Team</a>’s role is to ensure the responsible parties enact adequate mitigations,
+	by whatever means they already have at their disposal.</p>
+    <p>A Council <em class="rfc2119">may</em> form sub-groups for deliberation,
+	who may return with a recommendation,
+	but the full Council issues the final decision.
+	The decision of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②④">W3C Council</a> <em class="rfc2119">should</em> be unanimous,
+	and <em class="rfc2119">may</em> be issued under consensus.
+	However, if despite careful deliberation
+	a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑤">W3C Council</a> is unable to reach consensus,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair④">W3C Council Chair</a> may instead resort to voting.
+	In that case,
+	the decision is adopted if there are more ballots for than against;
+	in case of a tie,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑤">W3C Council Chair</a> determines the outcome.
+	However,
+	if the decision or proposal being objected to
+	originated with the TAG or AB,
+	then members of that group at the time the decision or proposal was made
+	must abstain in such a vote.
+	In case of a vote,
+	if two members of a Council who share the same affiliation cast an identical ballot,
+	then their ballots count as a one vote,
+	not two.</p>
+    <p>In the case of non-unanimous decisions,
+	members of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑥">W3C Council</a> who disagree with the Council’s decision <em class="rfc2119">may</em> write a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="minority-opinion">Minority Opinion</dfn> explaining the reason for their disagreement.</p>
+    <p>The deliberations of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑦">W3C Council</a> are confidential to that <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑧">W3C Council</a> and its <a data-link-type="dfn" href="#council-staff-contact" id="ref-for-council-staff-contact①">Council Staff Contact</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> This confidentiality requirement is put in place so that
+	the Council can receive sensitive information in confidence
+	and to enable Council members to speak freely in their individual expert capacity
+	without pressure or fear of retaliation
+	by those involved in the dispute, business relations, their employer, etc.</p>
+    <p id="45-day-update"> If a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council②⑨">W3C Council</a> is unable to come to a conclusion within 45 days of being <a data-link-type="dfn" href="#convened" id="ref-for-convened③">convened</a>,
+	the <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑥">W3C Council Chair</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑤">AC</a> of this delay
+	and of the status of the discussions.
+	The <a data-link-type="dfn" href="#w3c-council-chair" id="ref-for-w3c-council-chair⑦">W3C Council Chair</a> <em class="rfc2119">may</em> additionally make this report <a href="#confidentiality-levels">public</a>. </p>
+    <h5 class="heading settled" data-level="5.6.2.8" id="council-decision"><span class="secno">5.6.2.8. </span><span class="content"> Council Decision Report</span><a class="self-link" href="#council-decision"></a></h5>
+    <p>A <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⓪">Council</a> terminates by issuing a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="council-report">Council Report</dfn>,
+	which:</p>
+    <ul>
+     <li data-md>
+      <p><em class="rfc2119">must</em> state whether the Council <a data-link-type="dfn" href="#affirm" id="ref-for-affirm②">affirms</a> or <a data-link-type="dfn" href="#overturn" id="ref-for-overturn②">overturns</a> the decision being objected to.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> provide a rationale supporting its conclusion,
+which <em class="rfc2119">should</em> address each argument raised in the Formal Objection(s).</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include any recommendation decided by the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③①">Council</a>.</p>
+     <li data-md>
+      <p>if the decision has been <a data-link-type="dfn" href="#overturn" id="ref-for-overturn③">overturned</a>, <em class="rfc2119">must</em> identify which aspects of the Formal Objection(s) are being <a data-link-type="dfn" href="#upheld" id="ref-for-upheld②">upheld</a>, and <em class="rfc2119">should</em> include any suggested <a href="#fo-mitigations">mitigations</a>.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> include the <a data-link-type="dfn" href="#minority-opinion" id="ref-for-minority-opinion">Minority Opinion(s)</a>, if any.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of those who were <a data-link-type="dfn" href="#dismissed" id="ref-for-dismissed⑥">dismissed</a> or <a data-link-type="dfn" href="#renounce" id="ref-for-renounce④">renounced</a> their seat as well as those who were qualified to serve.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the names of the individuals who participated in the final Council decision.</p>
+     <li data-md>
+      <p><em class="rfc2119">must</em> report the number of votes for/against dismissing each participant.</p>
+     <li data-md>
+      <p><em class="rfc2119">may</em> report vote totals for the Council’s decision, if a formal vote was held.</p>
+     <li data-md>
+      <p><em class="rfc2119">must not</em> attribute any position to any individual on the Council.</p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑧">Team</a> <em class="rfc2119">must</em> maintain a <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/about/council/">public page on the W3C website</a> indexing all completed <a data-link-type="dfn" href="#council-report" id="ref-for-council-report①">Council Reports</a>.
+	If a Council decision is later overturned by an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal">AC Appeal</a>,
+	this <em class="rfc2119">must</em> also be mentioned. <a data-link-type="dfn" href="#council-report" id="ref-for-council-report②">Council Reports</a> <em class="rfc2119">must</em> be no more confidential
+	than the decision or document being objected to.</p>
+    <p>The <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③②">Council</a> <em class="rfc2119">may</em> also issue a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="supplemental-confidential-council-report">Supplemental Confidential Council Report</dfn> with a more restricted <a href="#confidentiality-levels">level of confidentiality</a> than its main report
+	when it believes that additional commentary on confidential aspects of the case
+	would be informative.
+	However, the main <a data-link-type="dfn" href="#council-report" id="ref-for-council-report③">Council Report</a> <em class="rfc2119">should</em> be self-sufficient
+	and understandable without reference to Supplemental Confidential Council Reports.</p>
+    <h5 class="heading settled" data-level="5.6.2.9" id="council-appeals"><span class="secno">5.6.2.9. </span><span class="content"> Appealing Council Decisions</span><a class="self-link" href="#council-appeals"></a></h5>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑦">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①">Advisory Committee Appeal</a> of a Council decision issued in a <a data-link-type="dfn" href="#council-report" id="ref-for-council-report④">Council Report</a>.</p>
+    <h3 class="heading settled" data-level="5.7" id="ACReview"><span class="secno">5.7. </span><span class="content"> Advisory Committee Reviews and W3C Decisions</span><a class="self-link" href="#ACReview"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑥">Advisory Committee</a> formally confers its approval
+	on <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑤">charters</a>, <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③">technical reports</a>,
+	and other matters
+	through an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee review | AC Review" id="advisory-committee-review">Advisory Committee review</dfn> and its resulting <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑥">W3C Decision</a>.</p>
+    <h4 class="heading settled" data-level="5.7.1" id="ACReviewStart"><span class="secno">5.7.1. </span><span class="content"> Initiating an Advisory Committee Review</span><a class="self-link" href="#ACReviewStart"></a></h4>
+    <p>Each <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①③">Advisory Committee review</a> period
+	begins with a Call for Review from the <a data-link-type="dfn" href="#team" id="ref-for-team⑦⑨">Team</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑦">Advisory Committee</a>.
+	The <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="reviewform">Call for Review</dfn> describes the proposal,
+	raises attention to deadlines,
+	estimates when the decision will be available,
+	and includes other practical information.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team⑧⓪">Team</a> <em class="rfc2119">may</em> share its perspective on the proposal
+	in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform">Call for Review</a>.
+	Each Member organization <em class="rfc2119">may</em> send one review,
+	which <em class="rfc2119">must</em> be returned by its <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑧">Advisory Committee representative</a>.</p>
+    <p>For clarity,
+	in the context of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①④">AC Review</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent②">dissent</a> <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑧">Formal Objection</a>.</p>
+    <p>The Team <em class="rfc2119">must</em> provide two channels for Advisory Committee review comments:</p>
+    <ol>
+     <li> an archived <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑥">Team-only</a> channel; 
+     <li> an archived <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only②">Member-only</a> channel. 
+    </ol>
+    <p>The <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform①">Call for Review</a> <em class="rfc2119">must</em> specify
+	which channel is the default for review comments on that Call.</p>
+    <p>Reviewers <em class="rfc2119">may</em> send information
+	to either or both channels.
+	A reviewer <em class="rfc2119">may</em> also share their own reviews
+	with other Members on the <a href="#ACCommunication">Advisory Committee discussion list</a>,
+	and <em class="rfc2119">may</em> also make it available to the public.</p>
+    <p>A Member organization <em class="rfc2119">may</em> modify its review
+	during a review period
+	(e.g., in light of comments from other Members).</p>
+    <h4 class="heading settled" data-level="5.7.2" id="ACReviewAfter"><span class="secno">5.7.2. </span><span class="content"> Determining the W3C Decision</span><a class="self-link" href="#ACReviewAfter"></a></h4>
+    <p>After the review period,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧①">Team</a> determines the appropriate <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑦">W3C Decision</a>,
+	which they <em class="rfc2119">must</em> announce to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑧">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em> indicate
+	the level of support for the proposal
+	(<a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⓪">consensus</a> or <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent③">dissent</a>),
+	and specifically
+	whether there were any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection②⑨">Formal Objections</a>,
+	with attention to <a href="#confidentiality-change">changing the confidentiality level</a> of the <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⓪">Formal Objections</a>.</p>
+    <p>If there were <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③①">Formal Objections</a>, at least some of which were <a data-link-type="dfn" href="#upheld" id="ref-for-upheld③">upheld</a>,
+	or if there is not <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①①">consensus</a> because of insufficient support, <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑧">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to improve the proposal. 
+     <li> The proposal is rejected. 
+    </ul>
+    <p>If the proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①②">consensus</a>,
+	or if all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③②">Formal Objections</a> are retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule">overruled</a> and the proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①③">consensus</a>,
+	this <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision⑨">W3C Decision</a> <em class="rfc2119">must</em> be one of:</p>
+    <ul>
+     <li> The proposal is adopted,
+			possibly with additional changes integrated
+			in order to address the comments of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee①⑨">AC</a> (see below). 
+     <li> The proposal is returned for additional work,
+			with a request to the initiator to make desirable changes identified during the review
+			and to resubmit. 
+    </ul>
+    <p>If the proposal is adopted with changes other than <a href="#class-1">class 1 (markup) changes</a>,
+	then those changes <em class="rfc2119">must</em> be announced to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⓪">AC</a> and to the <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group③">Group</a> that owns the document (if any).
+	Additionally, when adopting a proposal with <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①">substantive changes</a> integrated,
+	the announcement <em class="rfc2119">must</em> include rationale
+	for the substantive changes.</p>
+    <p><a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change②">Substantive changes</a> to the proposal <em class="rfc2119">may</em> be adopted
+	only if the revised proposal has <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①④">consensus</a> of the subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②①">AC</a> that voted on the initial proposal
+	(including anyone who explicitly abstained),
+	or if all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③③">Formal Objections</a> against the revised proposal are retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule①">overruled</a> and the revised proposal otherwise has sufficient support to achieve <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑤">consensus</a>.
+	For clarity,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧②">Team</a> <em class="rfc2119">should</em> seek a response from this subset of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②②">AC</a> using the same tooling and degree of formality as it did for the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑤">AC Review</a>;
+	and as is the case during <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑥">AC Reviews</a>, <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent④">dissent</a> in this context <em class="rfc2119">must</em> be expressed as a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③④">Formal Objection</a>.</p>
+    <p>Any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑤">Formal Objection</a> raised at this stage against the revised proposal
+	is handled by the same <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③③">Council</a> responsible for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑥">Formal Objections</a> raised against the initial proposal,
+	if any.</p>
+    <p>Such a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③④">Council</a> has the ability to <a data-link-type="dfn" href="#affirm" id="ref-for-affirm③">affirm</a> either the original or the revised proposal for advancement,
+	thereby <a data-link-type="dfn" href="#overrule" id="ref-for-overrule②">overruling</a> all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑦">Formal Objections</a> against the original or revised proposal,
+	respectively.</p>
+    <p>For publications which have conditions in addition to <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②③">AC</a> approval
+	for introducing <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change③">substantive changes</a> (such as <a data-link-type="dfn" href="#w3c-group" id="ref-for-w3c-group④">Group</a> consensus or implementation experience
+	or going through a patent <a data-link-type="dfn" href="https://www.w3.org/policies/patent-policy/#exclusion-opportunity" id="ref-for-exclusion-opportunity">Exclusion Opportunity</a>),
+	those other conditions must also be re-fulfilled.</p>
+    <div class="example" id="example-2c1b534e"><a class="self-link" href="#example-2c1b534e"></a> For example, if <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change④">substantive changes</a> to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④">technical report</a> are requested when assessing the transition from <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR">Candidate Recommendation</a> to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①">Recommendation</a>,
+		the technical report would need to go through a new <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests">Update Request</a> and be republished as a new <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①">Candidate Recommendation</a>;
+		that new version would then need to satisfy the criteria for advancement.
+		Alternatively, the desired changes can be introduced as non-substantive amendments
+		using the process for <a href="#revising-rec">revising a Recommendation</a>.
+		However, with the exception of the removal of at-risk features,
+		they cannot be directly integrated between <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot">CRS</a> and <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②">REC</a>,
+		because that would fail to trigger a patent exclusion opportunity. </div>
+    <p>For <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑥">charters</a>,
+	substantive changes from the initial proposal that underwent <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑦">AC Review</a> <em class="rfc2119">must not</em> include any increase to the scope.
+	If any such change is desired,
+	it <em class="rfc2119">must</em> be returned for additional work
+	and go through a complete new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑧">AC Review</a>.</p>
+    <p>This document does not specify
+	time intervals between the end of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review①⑨">Advisory Committee review</a> period
+	and the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⓪">W3C decision</a>.
+	This is to ensure that the Members and <a data-link-type="dfn" href="#team" id="ref-for-team⑧③">Team</a> have sufficient time to consider comments
+	gathered during the review.
+	The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②④">Advisory Committee</a> <em class="rfc2119">should not</em> expect an announcement
+	sooner than <span class="time-interval">two weeks</span> after the end of a review period.
+	If, after <span class="time-interval">three weeks</span>, the outcome has not been announced,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧④">Team</a> <em class="rfc2119">should</em> provide the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑤">Advisory Committee</a> with an update.</p>
+    <h3 class="heading settled" data-level="5.8" id="ACVotes"><span class="secno">5.8. </span><span class="content"> Advisory Committee Votes</span><a class="self-link" href="#ACVotes"></a></h3>
+    <p>The <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑥">Advisory Committee</a> votes in <a href="#AB-TAG-elections">elections for seats on the TAG or Advisory Board</a>,
+	and in the event of an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal②">Advisory Committee Appeal</a> achieving the required support to trigger an <a data-link-type="dfn" href="#appeal-vote" id="ref-for-appeal-vote①">appeal vote</a>.
+	Whenever the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑦">Advisory Committee</a> votes,
+	each Member or group of <a data-link-type="dfn" href="#related-member" id="ref-for-related-member④">related Members</a> has one vote.</p>
+    <h3 class="heading settled" data-level="5.9" id="ACAppeal"><span class="secno">5.9. </span><span class="content"> Appeal by Advisory Committee Representatives</span><a class="self-link" href="#ACAppeal"></a></h3>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative①⑨">Advisory Committee representatives</a> <em class="rfc2119">may</em> appeal certain decisions,
+	though appeals are only expected to occur in extraordinary circumstances.
+	For the purpose of this section, only <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⓪">Advisory Committee representatives</a> of <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member④">Members</a> in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing①">Good Standing</a> are counted.</p>
+    <p>When a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①①">W3C decision</a> is made following an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⓪">Advisory Committee review</a>, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②①">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate
+	an <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Advisory Committee Appeal|AC Appeal| Appeal" id="advisory-committee-appeal">Advisory Committee Appeal</dfn>.
+	These <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①②">W3C decisions</a> include those related to group creation and modification,
+	and transitions to new maturity stages for Recommendation Track documents
+	and the Process document.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②②">Advisory Committee representatives</a> <em class="rfc2119">may</em> also initiate an appeal
+	for decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑤">W3C Council</a>, and
+	for certain decisions that do not involve an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②①">Advisory Committee review</a>.
+	These cases are identified in the sections
+	which describe the requirements for the decision
+	and include
+	additional (non-reviewed) maturity stages of Recommendation Track documents,
+	group <a data-link-type="dfn" href="#dfn-charter-extension" id="ref-for-dfn-charter-extension">charter extensions</a> and closures,
+	and <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement">technical agreements</a>.</p>
+    <p>In all cases,
+	an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal③">appeal</a> <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the decision.</p>
+    <p>An <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②③">Advisory Committee representative</a> initiates an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal④">appeal</a> by sending a request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑤">Team</a>,
+	and should also share this request with the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑧">Advisory Committee</a>.
+	The request should say “I appeal this Decision”
+	and identify the decision,
+	and may also include their rationale for appealing the decision.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> See <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a> for a recommendation
+	on how to communicate an appeal request to the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑥">Team</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee②⑨">AC</a>.</p>
+    <p>Within one week the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑦">Team</a> <em class="rfc2119">must</em> announce the appeal process
+	to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⓪">Advisory Committee</a> and provide a mechanism for <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②④">Advisory Committee representatives</a> to respond with a statement of positive support for this appeal.
+	The archive of these statements <em class="rfc2119">must</em> be <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only③">member-only</a>.
+	If, within <span class="time-interval">one week</span> of the Team’s announcement,
+	5% or more of the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③①">Advisory Committee</a> support the appeal request,
+	the Team <em class="rfc2119">must</em> organize an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="appeal-vote">appeal vote</dfn> asking the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③②">Advisory Committee</a> “Do you approve of the Decision?”
+	together with links to the decision and the appeal support.</p>
+    <p>The ballot <em class="rfc2119">must</em> allow for three possible responses:
+	“Approve”,
+	“Reject”,
+	and “Abstain”,
+	together with Comments.</p>
+    <p>The level of support needed for an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑤">Advisory Committee Appeal</a> to pass
+	depends on the level of ballot participation 
+	(including explicit “abstain” ballots) 
+	by <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑤">Advisory Committee Representatives</a>:</p>
+    <ul>
+     <li data-md>
+      <p>if fewer than 5% participate,
+the vote fails.</p>
+     <li data-md>
+      <p>if at least 5% but no more than 15% participate,
+and the number of “Approve” ballots exceeds three times (3x) the number of “Reject” ballots,
+the vote passes.</p>
+     <li data-md>
+      <p>if more than 15% but fewer than 20% participate,
+and the number of “Approve” ballots exceeds twice (2x) the number of “Reject” ballots,
+the vote passes.</p>
+     <li data-md>
+      <p>if 20% or more participate,
+and the number of “Approve” ballots exceeds the number of “Reject” ballots,
+the vote passes.</p>
+    </ul>
+    <p>If the vote passes,
+	the decision is overturned.
+	Following such rejection,
+	those who had initiated the proposal may revise it
+	to address the causes of rejection
+	and follow the ordinary applicable process
+	to submit the revised proposal.</p>
+    <h2 class="heading settled" data-level="6" id="Reports"><span class="secno">6. </span><span class="content"> W3C Technical Reports</span><a class="self-link" href="#Reports"></a></h2>
+    <p>The W3C technical report development process is the set of steps and requirements
+	followed by W3C <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑤">Working Groups</a> to standardize Web technology.
+	The W3C technical report development process is designed to:</p>
+    <ul>
+     <li> support multiple specification development methodologies 
+     <li> maximize <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑥">consensus</a> about the content of stable technical reports 
+     <li> ensure high technical and editorial quality 
+     <li> promote consistency among specifications 
+     <li> facilitate royalty-free, interoperable implementations of Web Standards, and 
+     <li> earn endorsement by W3C and the broader community. 
+    </ul>
+    <p>See also “licensing goals for W3C Specifications”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.1" id="recs-and-notes"><span class="secno">6.1. </span><span class="content"> Types of Technical Reports</span><a class="self-link" href="#recs-and-notes"></a></h3>
+    <p>This chapter describes the formal requirements
+	for <a data-link-type="dfn" href="#publishing" id="ref-for-publishing">publishing</a> and maintaining a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③">W3C Recommendation</a>, <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑧">Note</a>,
+	or <a data-link-type="dfn" href="#registry" id="ref-for-registry">Registry</a>.</p>
+    <dl>
+     <dt>Recommendations 
+     <dd> <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑥">Working Groups</a> develop technical reports on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①">W3C Recommendation Track</a> in order to produce normative specifications or guidelines
+			as standards for the Web.
+			The <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track②">Recommendation Track</a> process incorporates requirements for <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review②">wide review</a>, <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation">adequate implementation experience</a>,
+			and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑦">consensus</a>-building,
+			and is subject to the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			under which participants commit to Royalty-Free IPR licenses for implementations.
+			See <a href="#rec-track">§ 6.3 The W3C Recommendation Track</a> for details. 
+     <dt>Notes 
+     <dd> Groups can also publish documents as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①">Group Notes</a> and <a data-link-type="dfn" href="#statement" id="ref-for-statement">W3C Statements</a>,
+			typically either to document information
+			other than technical specifications,
+			such as use cases motivating a specification
+			and best practices for its use.
+			See <a href="#note-track">§ 6.4 The Note Track (Notes and Statements)</a> for details. 
+     <dt>Registries 
+     <dd> <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group③">Chartered</a> and <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group">elected groups</a> can also publish <a data-link-type="dfn" href="#registry" id="ref-for-registry①">registries</a> in order to document collections of values or other data.
+			A registry can be published either as a distinct <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report">registry report</a>,
+			or directly within a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track③">Recommendation Track</a> document
+			as an <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry">embedded registry</a>. <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition">Defining a registry</a> requires <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review③">wide review</a> and <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑧">consensus</a>,
+			but once set up, changes to registry entries are lightweight
+			and can even be done without the initiating group’s involvement.
+			See <a href="#registries">§ 6.5 The Registry Track</a> for details. 
+    </dl>
+    <p>Individual <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑦">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG⑨">Interest Groups</a> <em class="rfc2119">should</em> adopt additional processes
+	for developing publications,
+	so long as they do not conflict with the requirements in this chapter.</p>
+    <h3 class="heading settled" data-level="6.2" id="general-requirements"><span class="secno">6.2. </span><span class="content"> General Requirements for Technical Reports</span><a class="self-link" href="#general-requirements"></a></h3>
+    <h4 class="heading settled" data-level="6.2.1" id="publication"><span class="secno">6.2.1. </span><span class="content"> Publication of Technical Reports</span><a class="self-link" href="#publication"></a></h4>
+    <p><dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="publish" data-noexport id="publishing">Publishing</dfn> as used in this document
+	refers to producing a version which is listed as a W3C <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="technical-report">Technical Report</dfn> on its <a href="https://www.w3.org/TR/">Technical Reports index at https://www.w3.org/TR</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a>.
+	Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public document.
+	W3C strives to make archival documents indefinitely available
+	at their original address in their original form.</p>
+    <p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate its <a href="#maturity-stages">maturity stage</a>,
+	and <em class="rfc2119" id="DocumentStatus">must</em> include information about the status of the document.
+	This status information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> be unique each time a specification is <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①">published</a>, 
+     <li> <em class="rfc2119">must</em> state which <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑧">Working Group</a> developed the specification, 
+     <li> <em class="rfc2119">must</em> state how to send comments or file bugs,
+			and where these are recorded, 
+     <li> <em class="rfc2119">must</em> include expectations about next steps, 
+     <li> <em class="rfc2119">should</em> explain how the technology relates to existing international standards
+			and related work inside or outside W3C,
+			and 
+     <li> <em class="rfc2119">should</em> explain
+			or link to
+			an explanation of significant changes from the previous version. 
+    </ul>
+    <p>Every Technical Report published
+	as part of the Technical Report development process
+	is edited by one or more editors
+	appointed by a Group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③⓪">Chair</a>.
+	It is the responsibility of these editors to ensure that the decisions of the Group are
+	correctly reflected in subsequent drafts of the technical report.
+	An editor <em class="rfc2119">must</em> be a participant,
+	per <a href="#group-participation">§ 3.4.2 Participation in Chartered Groups</a> in the Group responsible for the document(s) they are editing.</p>
+    <p>The Team is <em class="rfc2119">not required</em> to publish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑤">Technical Report</a> that does not conform to the Team’s <a href="https://www.w3.org/pubrules/">Publication Rules</a> <a data-link-type="biblio" href="#biblio-pubrules" title="Publication Rules">[PUBRULES]</a> (e.g., for <span id="DocumentName">naming</span>,
+	status information,
+	style,
+	and <span id="document-copyright">copyright requirements</span>).
+	These rules are subject to change by the Team from time to time.
+	The Team <em class="rfc2119">must</em> inform group <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③①">Chairs</a> and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③③">Advisory Committee</a> of any changes to these rules.</p>
+    <p>The primary language for W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑥">Technical Reports</a> is English.
+	W3C encourages the translation of its <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑦">Technical Reports</a>. <a href="https://www.w3.org/Consortium/Translation/">Information about translations of W3C technical reports</a> <a data-link-type="biblio" href="#biblio-translation" title="Translations of W3C technical reports">[TRANSLATION]</a> is available at the W3C website.</p>
+    <h4 class="heading settled" data-level="6.2.2" id="doc-reviews"><span class="secno">6.2.2. </span><span class="content"> Reviews and Review Responsibilities</span><a class="self-link" href="#doc-reviews"></a></h4>
+    <p>A document is available for review
+	from the moment it is first <a data-link-type="dfn" href="#publishing" id="ref-for-publishing②">published</a>.
+	Working Groups <em class="rfc2119">should</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed①">formally address</a> <em>any</em> substantive review comment
+	about a technical report in a timely manner.</p>
+    <p>Reviewers <em class="rfc2119">should</em> send substantive technical reviews as early as possible. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG①⑨">Working Groups</a> are often reluctant to make <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑤">substantive changes</a> to a mature document,
+	particularly if this would cause significant compatibility problems
+	due to existing implementation. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⓪">Working Groups</a> <em class="rfc2119">should</em> record substantive
+	or interesting proposals raised by reviews
+	but not incorporated into a current specification.</p>
+    <h5 class="heading settled" data-level="6.2.2.1" id="wide-review"><span class="secno">6.2.2.1. </span><span class="content"> Wide Review</span><a class="self-link" href="#wide-review"></a></h5>
+    <p>The requirements for <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="dfn-wide-review">wide review</dfn> are not precisely defined by the W3C Process.
+	The objective is to ensure that the entire set of stakeholders of the Web community,
+	including the general public,
+	have had adequate notice of the progress of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②①">Working Group</a> and were able to actually perform reviews of and provide comments on the specification.
+	A second objective is to encourage groups to request reviews
+	early enough that comments and suggested changes
+	can still be reasonably incorporated in response to the review.
+	Before approving transitions,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑧">Team</a> will consider who has been explicitly offered
+	a reasonable opportunity to review the document,
+	who has provided comments,
+	the record of requests to and responses from reviewers,
+	especially <a href="https://www.w3.org/guide/process/charter#horizontal-review">W3C Horizontal Groups</a> <a data-link-type="biblio" href="#biblio-charter" title="How to Create a Working Group or Interest Group">[CHARTER]</a> and groups identified as dependencies in the charter
+	or identified as <a href="https://www.w3.org/liaisons/">liaisons</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a>,
+	and seek evidence of clear communication to the general public
+	about appropriate times and which content to review
+	and whether such reviews actually occurred.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The Team documents <a href="https://www.w3.org/guide/documentreview/">best practices for wide review</a> in the Guidebook. <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a></p>
+    <p>For example,
+	inviting review of new or significantly revised sections published in Working Drafts,
+	and tracking those comments
+	and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②②">Working Group</a>’s responses,
+	is generally a good practice which would often be considered positive evidence of wide review. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②③">Working Groups</a> <em class="rfc2119">should</em> follow the <a href="https://www.w3.org/guide/documentreview/#how-to-get-horizontal-review">W3C Horizontal Groups</a>’ review processes,
+	and <em class="rfc2119">should</em> announce to other W3C Working Groups
+	as well as the general public,
+	especially those affected by this specification,
+	a proposal to enter <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②">Candidate Recommendation</a> (for example in approximately 28 days).
+	By contrast a generic statement in a document
+	requesting review at any time
+	is likely not to be considered as sufficient evidence
+	that the group has solicited wide review.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②④">Working Group</a> could present evidence that wide review has been received,
+	irrespective of solicitation.
+	But it is important to note that receiving many detailed reviews
+	is not necessarily the same as wide review,
+	since they might only represent comment
+	from a small segment of the relevant stakeholder community.</p>
+    <h4 class="heading settled" data-level="6.2.3" id="correction-classes"><span class="secno">6.2.3. </span><span class="content"> Classes of Changes</span><a class="self-link" href="#correction-classes"></a></h4>
+    <p>This document distinguishes the following 5 classes of changes to a document.
+	The first two classes of change are considered <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="editorial change" data-noexport id="editorial-change">editorial changes</dfn>,
+	the next two <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="substantive change" data-noexport id="substantive-change">substantive changes</dfn>,
+	and the last one <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="registry change" data-noexport id="registry-change">registry changes</dfn>.</p>
+    <dl>
+     <dt id="class-1">
+      <a class="self-link" href="#class-1"></a> 
+      <ol>
+       <li data-md>
+        <p>No changes to text content</p>
+      </ol>
+     <dd> These changes include fixing broken links, style sheets, or invalid markup. 
+     <dt id="class-2">
+      <a class="self-link" href="#class-2"></a> 
+      <ol start="2">
+       <li data-md>
+        <p>Changes that do not functionally affect interpretation of the document</p>
+      </ol>
+     <dd> For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track④">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑧">technical reports</a> specifically,
+			this constitutes changes that do not affect conformance,
+			i.e. changes that reasonable implementers
+			would not interpret as changing architectural
+			or interoperability requirements
+			or their implementation.
+			Changes which resolve ambiguities in the specification
+			are considered to change (by clarification) the implementation requirements
+			and do not fall into this class. 
+     <dd> Examples of changes in this class include
+			correcting non-normative examples
+			which clearly conflict with normative requirements,
+			clarifying various other non-normative text,
+			fixing typos or grammatical errors
+			where the change does not change requirements. 
+     <dd> If there is any doubt or disagreement
+			as to whether a change functionally affects interpretation,
+			that change does not fall into this class. 
+     <dt id="class-3">
+      <a class="self-link" href="#class-3"></a> 
+      <ol start="3">
+       <li data-md>
+        <p>Other changes that do not add new features</p>
+      </ol>
+     <dd>
+       For <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑤">Recommendation-track</a> documents,
+			these changes <em class="rfc2119">may</em> affect conformance to the specification.
+			A change that affects conformance is one that: 
+      <ul>
+       <li> makes conforming data, processors, or other conforming agents become non-conforming according to the new version,
+					or 
+       <li> makes non-conforming data, processors, or other agents become conforming,
+					or 
+       <li> clears up an ambiguity or under-specified part of the specification
+					in such a way that data,
+					a processor,
+					or an agent
+					whose conformance was once unclear
+					becomes clearly either conforming or non-conforming. 
+      </ul>
+     <dt id="class-4">
+      <a class="self-link" href="#class-4"></a> 
+      <ol start="4">
+       <li data-md>
+        <p>New features</p>
+      </ol>
+     <dd> Changes that add new functionality,
+			such as new elements, new APIs, new rules, etc. 
+     <dt id="class-5">
+      <a class="self-link" href="#class-5"></a> 
+      <ol start="5">
+       <li data-md>
+        <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table">registry table</a></p>
+      </ol>
+     <dd> Changes that add, remove, or alter <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry">registry entries</a> in a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①">registry table</a>. 
+    </dl>
+    <h4 class="heading settled" data-level="6.2.4" id="errata"><span class="secno">6.2.4. </span><span class="content"> Errata Management</span><a class="self-link" href="#errata"></a></h4>
+    <p>Tracking errors is an important part of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑤">Working Group</a>’s ongoing care of a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report⑨">technical report</a>;
+	for this reason,
+	the scope of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑥">Working Group</a> charter generally allows time
+	for work after publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④">Recommendation</a>.
+	In this Process Document,
+	the term “<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="erratum | errata" id="erratum">erratum</dfn>”
+	(plural “errata”) refers to any error
+	that can be resolved by one or more changes in classes 1-3
+	of section <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑦">Working Groups</a> <em class="rfc2119">must</em> keep
+	a public record of errors
+	that are reported by readers and implementers
+	for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤">Recommendations</a>.
+	Such error reports <em class="rfc2119">should</em> be compiled
+	no less frequently than quarterly.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑧">Working Groups</a> decide how to document errata.
+	Such documentation <em class="rfc2119">must</em> identify
+	the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⓪">technical report</a> text
+	and describe the error;
+	it <em class="rfc2119">may</em> also describe some possible solution(s).
+	Readers of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①①">technical report</a> <em class="rfc2119">should</em> be able easily
+	to find and see the errata
+	that apply to that specific <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①②">technical report</a> with their associated tests.
+	Errata <em class="rfc2119">may</em> be documented
+	in a separate errata page or tracking system.
+	They <em class="rfc2119">may</em>,
+	in addition or alternatively,
+	be annotated inline
+	alongside the affected <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①③">technical report</a> text
+	or at the start or end of the most relevant section(s).</p>
+    <h4 class="heading settled" data-level="6.2.5" id="candidate-amendments"><span class="secno">6.2.5. </span><span class="bs-old-id" id="candidate-changes"></span><span class="content"> Candidate Amendments</span><a class="self-link" href="#candidate-amendments"></a></h4>
+    <p>An <a data-link-type="dfn" href="#erratum" id="ref-for-erratum">erratum</a> <em class="rfc2119">may</em> be accompanied by a non-normative, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-correction">candidate correction</dfn> approved by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision②">group decision</a>.
+	When annotated inline,
+	errata—​including their <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction">candidate corrections</a>—​must be marked as such,
+	are treated as <a href="#correction-classes">class 2 changes</a>,
+	and are published accordingly.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Annotating changes in this way allows more mature documents
+	such as <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥">Recommendations</a> and <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR③">Candidate Recommendations</a> to be updated quickly with the Working Group’s most current thinking,
+	even when the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment">candidate amendments</a> have not yet received
+	sufficient review or implementation experience
+	to be normatively incorporated into the specification proper.</p>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-addition">candidate addition</dfn> is similar to a <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction①">candidate correction</a>,
+	except that it proposes a new feature
+	rather than an error correction.</p>
+    <p><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction②">Candidate corrections</a> and <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition">candidate additions</a> are collectively known as <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="candidate amendment" data-noexport id="candidate-amendment">candidate amendments</dfn>.</p>
+    <p>In addition to their actual <a href="#maturity-stages">maturity stage</a>, <a data-link-type="dfn" href="#publishing" id="ref-for-publishing③">published</a> <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑥">REC Track</a> documents with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment①">candidate amendments</a> are also considered,
+	for the purpose of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+	to be <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①">Working Drafts</a> with those <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment②">candidate amendments</a> treated as normative.</p>
+    <h4 class="heading settled" data-level="6.2.6" id="no-group-maintenance"><span class="secno">6.2.6. </span><span class="content"> Maintenance Without a Group</span><a class="self-link" href="#no-group-maintenance"></a></h4>
+    <p>For all <a href="#recs-and-notes">types of technical reports</a> and all <a href="#maturity-stages">maturity stages</a>,
+	if there is no <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group④">group</a> chartered to maintain a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①④">technical report</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑧⑨">Team</a> <em class="rfc2119">may</em> republish it
+	at the same <a href="#maturity-stages">maturity stage</a>,
+	integrating as needed:</p>
+    <ol>
+     <li><a href="#correction-classes">class 1 changes</a>; 
+     <li>inline <a data-link-type="dfn" href="#erratum" id="ref-for-erratum①">errata</a>; 
+     <li><a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction③">candidate corrections</a>,
+			which <em class="rfc2119">must</em> be marked as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="team-correction">Team correction</dfn>; 
+     <li><a href="#correction-classes">class 2 changes</a> other than inline <a data-link-type="dfn" href="#erratum" id="ref-for-erratum②">errata</a> and <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction">Team corrections</a>. 
+    </ol>
+    <p>To avoid any potential doubt or disagreement
+	about whether changes really do fall into <a href="#correction-classes">class 2</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⓪">Team</a> <em class="rfc2119">should</em> be conservative,
+	limiting itself to obvious and limited fixes,
+	and <em class="rfc2119">must</em> avoid substantial rephrasing,
+	even of non-normative examples and notes.
+	If any such change is desired,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨①">Team</a> <em class="rfc2119">must</em> mark it as a <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction①">Team correction</a>.</p>
+    <p><a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction②">Team corrections</a> do not constitute
+	a normative portion of the Recommendation,
+	as defined in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (i.e., they are not covered by the Patent Policy).
+	For <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR④">Candidate Recommendations</a>, <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦">W3C Recommendations</a>, <a data-link-type="dfn" href="#candidate-registry" id="ref-for-candidate-registry">Candidate Registries</a>, <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry">W3C Registries</a>,
+	as well as <a data-link-type="dfn" href="#statement" id="ref-for-statement①">W3C Statements</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨②">Team</a> <em class="rfc2119">must</em> solicit <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review④">wide review</a> on <a data-link-type="dfn" href="#team-correction" id="ref-for-team-correction③">Team corrections</a> that it produces.</p>
+    <h4 class="heading settled" data-level="6.2.7" id="contributor-license"><span class="secno">6.2.7. </span><span class="content"> License Grants from Non-Participants</span><a class="self-link" href="#contributor-license"></a></h4>
+    <p>When a party who is not already obligated under the Patent Policy
+	offers a change in class 3 or 4
+	(as described in <a href="#correction-classes">§ 6.2.3 Classes of Changes</a>) to a technical report under this process
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨③">Team</a> <em class="rfc2119">must</em> request
+	a recorded royalty-free patent commitment;
+	for a change in class 4, the Team <em class="rfc2119">must</em> secure such commitment.
+	Such commitment <em class="rfc2119">should</em> cover,
+	at a minimum,
+	all the party’s Essential Claims both in the contribution,
+	and that become Essential Claims as a result of incorporating the contribution into the draft
+	that existed at the time of the contribution,
+	on the terms specified in the “W3C Royalty-Free (RF) Licensing Requirements” section of the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h3 class="heading settled" data-level="6.3" id="rec-track"><span class="secno">6.3. </span><span class="bs-old-id" id="rec-advance"></span><span class="content"> The W3C Recommendation Track</span><a class="self-link" href="#rec-track"></a></h3>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG②⑨">Working Groups</a> create specifications and guidelines
+	to complete the scope of work envisioned by a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⓪">Working Group</a>’s <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑦">charter</a>.
+	These <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑤">technical reports</a> undergo cycles of revision and review
+	as they advance towards <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑧">W3C Recommendation</a> status.
+	Once review suggests the Working Group has met their requirements for a new standard,
+	including <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑤">wide review</a>,
+	a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑤">Candidate Recommendation</a> phase
+	allows the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③①">Working Group</a> to formally collect <a href="#implementation-experience">implementation experience</a> to demonstrate that the specification works in practice.
+	At the end of the process,
+	the Advisory Committee reviews the mature technical report,
+	and if there is support from its Membership,
+	W3C publishes it as a <a href="#RecsW3C" id="ref-for-RecsW3C⑦⑥">Recommendation</a>.</p>
+    <p>In summary, the main steps of the <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="W3C Recommendation Track | REC Track | Recommendation Track | Recommendation-track" data-noexport id="w3c-recommendation-track">W3C Recommendation Track</dfn> are:</p>
+    <ol>
+     <li>Publication of the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd①">First Public Working Draft</a>. 
+     <li>Publication of zero or more revised <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD②">Working Drafts</a>. 
+     <li>Publication of one or more <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑥">Candidate Recommendations</a>. 
+     <li>Publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑨">W3C Recommendation</a>. 
+    </ol>
+    <figure>
+     <svg viewBox="-5 30 457 175" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Basic W3C Recommendation Track</title>
+      <g role="list">
+       <g fill="#060" role="listitem">
+        <a href="#wd-1">
+         <rect fill="white" height="45" role="img" width="57" y="122">
+          <title>First Public Working Draft (FPWD) - Exclusion opportunity</title>
+         </rect>
+         <text font-size="8">
+          <tspan aria-hidden="true" x="0" y="132">First Public WD</tspan>
+          <tspan x="0" y="152">WG Decision +</tspan>
+          <tspan x="0" y="160">Team Approval</tspan>
+         </text>
+         <path d="M0,140h53" fill="none" stroke="#060"></path>
+         <polygon points="47,136 57,140 47,144"></polygon>
+        </a>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="97" cy="140" fill="#fff" id="wd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Working Draft (WD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="97" y="144">WD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Publish a new Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="97" y="100">WG Decision</tspan>
+           </text>
+           <path d="M78,124C73,114 79,104 97,104 108,104 115,108 117,114" fill="none" stroke="black" stroke-dasharray="6 2"></path>
+           <polygon points="120,114 116,124 114,113"></polygon>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Advance to Candidate Recommendation</title>
+           </g>
+           <text font-size="8" x="135" y="129">WG Decision +</text>
+           <text font-size="8" x="135" y="137">Team Approval</text>
+           <path d="M135,140h81" stroke="#060"></path>
+           <polygon points="211,136 221,140 211,144"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="260" cy="140" fill="#fff" id="cr-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Snapshot (CRS) - Patent Policy exclusion opportunity</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="144">CRS</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="232" y="118">WG</tspan>
+            <tspan x="232" y="126">Decision</tspan>
+           </text>
+           <path d="M234,127v-34" stroke="#000"></path>
+           <polygon points="234,92 230,102 238,102"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="99">WG Decision</tspan>
+            <tspan x="290" y="107">Team Approval</tspan>
+           </text>
+           <path d="M242,124C238,114 244,104 260,104 271,104 285,108 286,117" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+          </a>
+         </g>
+         <g fill="#060" role="listitem">
+          <a href="#rec-1">
+           <g role="img">
+            <title>Advance to Recommendation</title>
+           </g>
+           <text font-size="8" x="298" y="121">WG Decision +</text>
+           <text font-size="8" x="298" y="129">Team Approval +</text>
+           <text font-size="8" x="298" y="137">AC Review</text>
+           <path d="M298,140h77" stroke="#060"></path>
+           <polygon points="374,136 384,140 374,144"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="end">
+            <tspan x="228" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="228" y="165">(or Team Decision with AB+TAG Approval)</tspan>
+           </text>
+           <path d="M140,147h84" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="140,145 133,147 140,149"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#cr-1">
+         <ellipse cx="260" cy="80" fill="#fff" id="crd-1" role="img" rx="38" ry="18" stroke="black">
+          <title>Candidate Recommendation Draft (CRD)</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="260" y="84">CRD</text>
+        </a>
+        <g role="list">
+         <g role="listitem">
+          <a href="#crd-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Draft</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="259" y="41">WG Decision</tspan>
+           </text>
+           <path d="M242,64C238,54 244,44 260,44 271,44 277,48 279,54" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="282,54 277,64 275,53"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Publish revised Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8">
+            <tspan x="290" y="99">WG Decision +</tspan>
+            <tspan x="290" y="107">Team Approval</tspan>
+           </text>
+           <path d="M286,127v-34" stroke="#000"></path>
+           <polygon points="286,128 282,118 290,118"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+       <g role="listitem">
+        <a href="#rec-1">
+         <ellipse cx="413" cy="140" fill="#fff" id="rec-1" role="img" rx="28" ry="18" stroke="black" stroke-width="2">
+          <title>Recommendation</title>
+         </ellipse>
+         <text aria-hidden="true" font-size="14" font-weight="bold" text-anchor="middle" x="413" y="144">REC</text>
+        </a>
+        <g role="list">
+         <g fill="#900" role="listitem">
+          <a href="#cr-1">
+           <g role="img">
+            <title>Return to Candidate Recommendation Snapshot</title>
+           </g>
+           <text font-size="8" text-anchor="start">
+            <tspan x="342" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="342" y="165">(or Team Decision</tspan>
+            <tspan font-size="6" x="342" y="173">with AB+TAG</tspan>
+            <tspan font-size="6" x="342" y="181">Approval)</tspan>
+           </text>
+           <path d="M301,147h88" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="301,145 296,147 301,149"></polygon>
+          </a>
+         </g>
+         <g fill="#900" role="listitem">
+          <a href="#wd-1">
+           <g role="img">
+            <title>Return to Working Draft</title>
+           </g>
+           <text font-size="8" text-anchor="start">
+            <tspan x="342" y="157">WG Decision</tspan>
+            <tspan font-size="6" x="342" y="165">(or Team Decision</tspan>
+            <tspan font-size="6" x="342" y="173">with AB+TAG</tspan>
+            <tspan font-size="6" x="342" y="181">Approval)</tspan>
+           </text>
+           <path d="M339,147v41h-242v-26" fill="none" stroke="#900" stroke-dasharray="4 4"></path>
+           <polygon points="95,164 97,159 99,164"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a fill="#000" href="#rec-1">
+           <g role="img">
+            <title>Publish revised Recommendation with editorial changes</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="413" y="103">WG Decision</tspan>
+            <tspan font-size="6" x="413" y="116">(editorial)</tspan>
+           </text>
+           <path d="M395,127C391,117 397,107 413,107 424,107 430,111 432,117" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="435,117 430,127 428,116"></polygon>
+          </a>
+         </g>
+         <g role="listitem">
+          <a fill="#000" href="#rec-1">
+           <g role="img">
+            <title>Publish revised Recommendation with substantive changes</title>
+           </g>
+           <text font-size="8" text-anchor="middle">
+            <tspan x="413" y="184">WG Decision +</tspan>
+            <tspan x="413" y="192">Team Approval +</tspan>
+            <tspan x="413" y="200">AC Review</tspan>
+            <tspan font-size="6" x="413" y="169">(substantive)</tspan>
+           </text>
+           <path d="M395,155C391,166 397,176 413,176 424,176 431,173 431,165" fill="none" stroke="#000" stroke-dasharray="6 2"></path>
+           <polygon points="435,164 430,155 428,165"></polygon>
+          </a>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+     <figcaption>Non-Normative Summary of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑦">Recommendation Track</a></figcaption>
+    </figure>
+    <p>Only sufficiently technically mature work should be advanced.
+	As described in <a href="#transition-reqs">§ 6.3.3 Advancement on the Recommendation Track</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team⑨④">Team</a> will decline a request to advance in maturity stage
+	and return the specification to a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③②">Working Group</a> for further work
+	if it determines that the requirements for advancement
+	have not been met.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Should faster advancement to meet scheduling considerations be desired,
+	this can be achieved by reducing the scope of the technical report to a subset that is adequately mature and deferring
+	less stable features to other technical reports.</p>
+    <p>W3C <em class="rfc2119">may</em> <a href="#tr-end">end work on a technical report</a> at any time.</p>
+    <h4 class="heading settled" data-level="6.3.1" id="maturity-stages"><span class="secno">6.3.1. </span><span class="content"> Maturity Stages on the Recommendation Track</span><a class="self-link" href="#maturity-stages"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation Track document | REC Track document | Recommendation Track document | Recommendation-track document" id="w3c-recommendation-track-document">W3C Recommendation Track document</dfn> is any document whose current status is one of those described in this section.</p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Working Draft | Working Draft | WD" id="RecsWD">Working Draft</dfn> (<abbr>WD</abbr>) 
+     <dd>
+       A Working Draft is a document that W3C has <a data-link-type="dfn" href="#publishing" id="ref-for-publishing④">published</a> on the <a href="https://www.w3.org/TR/">W3C’s Technical Reports page</a> <a data-link-type="biblio" href="#biblio-tr" title="The W3C technical reports index">[TR]</a> for review by the community (including W3C Members), the public,
+			and other technical organizations,
+			and for simple historical reference.
+			Some, but not all, Working Drafts are meant to advance to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⓪">Recommendation</a>;
+			see the <a href="#DocumentStatus">document status section</a> of a Working Draft
+			for the group’s expectations. <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD③">Working Drafts</a> do not necessarily represent a <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus①⑨">consensus</a> of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③③">Working Group</a> with respect to their content,
+			and do not imply any endorsement by W3C
+			or its members beyond agreement to work on a general area of technology.
+			Nevertheless the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③④">Working Group</a> decided to adopt the <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD④">Working Draft</a> as the basis for their work at the time of adoption.
+			A <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑤">Working Draft</a> is suitable for gathering <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑥">wide review</a> prior to advancing to the next stage of maturity. 
+      <p>For all Working Drafts a Working Group:</p>
+      <ul>
+       <li> <em class="rfc2119">should</em> document outstanding issues,
+					and parts of the document on which the Working Group does not have consensus,
+					and 
+       <li> <em class="rfc2119">may</em> request publication of a Working Draft
+					even if its content is considered unstable
+					and does not meet all Working Group requirements. 
+      </ul>
+      <p>The first Working Draft of a technical report is called the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="fpwd">First Public Working Draft</dfn> (<abbr>FPWD</abbr>),
+			and has patent implications as defined in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Candidate Recommendation | Candidate Recommendation | CR" id="RecsCR">Candidate Recommendation</dfn> (<abbr>CR</abbr>) 
+     <dd>
+       A Candidate Recommendation is a document that satisfies the technical
+			requirements of the Working Group that produced it and their dependencies,
+			and has already received wide review.
+			W3C publishes a Candidate Recommendation to 
+      <ul>
+       <li> signal to the wider community that it is time to do a final review 
+       <li> gather <a href="#implementation-experience">implementation experience</a> 
+      </ul>
+      <p class="note" role="note"><span class="marker">Note:</span> Advancing to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑦">Candidate Recommendation</a> indicates
+			that the document is considered complete and fit for purpose,
+			and that no further refinement to the text is expected
+			without additional implementation experience and testing;
+			however, additional features might be expected in a later revision.
+			A <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑧">Candidate Recommendation</a> is expected to be as well-written,
+			detailed,
+			self-consistent,
+			and technically complete
+			as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①①">Recommendation</a>,
+			and acceptable as such
+			if and when the requirements for further advancement are met.</p>
+      <p>Candidate Recommendation publications take one of two forms:</p>
+      <dl>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Snapshot | CRS" id="candidate-recommendation-snapshot">Candidate Recommendation Snapshot</dfn> (<abbr>CRS</abbr>) 
+       <dd>
+         A Candidate Recommendation Snapshot
+					corresponds to a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts">Patent Review Draft</a> as used in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+					Publishing a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts①">Patent Review Draft</a> triggers a Call for Exclusions,
+					per “Exclusion From W3C RF Licensing Requirements”
+					in the W3C Patent Policy. 
+        <p>Publication as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①">Candidate Recommendation Snapshot</a> requires verification of either a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req">Transition Request</a> (for the first <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR⑨">Candidate Recommendation</a> publication from another maturity stage)
+					or an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①">Update Request</a> (for subsequent <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot②">Candidate Recommendation Snapshots</a>).</p>
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Candidate Recommendation Draft | CRD" id="candidate-recommendation-draft">Candidate Recommendation Draft</dfn> (<abbr>CRD</abbr>) 
+       <dd>
+         A Candidate Recommendation Draft
+					is published
+					to solicit review of intended changes from the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot③">Candidate Recommendation Snapshot</a>.
+					This allows for wider review of the changes
+					and for ease of reference to the integrated specification. 
+        <p>Any changes published directly into a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft">Candidate Recommendation Draft</a> should be at the same level of quality as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot④">Candidate Recommendation Snapshot</a>.
+					However, the process requirements are minimized
+					so that the Working Group can easily keep the specification up to date.</p>
+        <p>A <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft①">Candidate Recommendation Draft</a> <em>does not</em> provide an exclusion opportunity;
+					instead, it is considered a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑥">Working Draft</a> for the purpose of the <a href="https://www.w3.org/policies/patent-policy/">W3C Patent Policy</a> <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+      </dl>
+      <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rescinded-candidate-recommendation">Rescinded Candidate Recommendation</dfn> is a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⓪">Candidate Recommendation</a> in which significant problems have been discovered
+			such that W3C cannot endorse it or continue work on it,
+			for example due to burdensome patent claims that affect implementers and cannot be resolved
+			(see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “PAG Conclusion”).
+			There is no path to restoration for a <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a>.
+			See “W3C Royalty-Free (RF) Licensing Requirements”
+			in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> for implication on patent licensing obligations.</p>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="W3C Recommendation | Recommendation | REC" id="RecsW3C">W3C Recommendation</dfn> (<abbr>REC</abbr>) 
+     <dd>
+       A W3C Recommendation is a specification
+			or set of guidelines
+			or requirements that,
+			after extensive <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②⓪">consensus</a>-building,
+			has received the endorsement of W3C and its Members.
+			W3C recommends the wide deployment
+			of its Recommendations as standards for the Web.
+			The W3C Royalty-Free IPR licenses
+			granted under the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> apply to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①②">W3C Recommendations</a>. 
+      <p id="expandable-rec"> After its initial publication,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①③">W3C Recommendation</a> <em class="rfc2119">may</em> be revised
+			(in accordance with <a href="#revising-rec">§ 6.3.10 Revising a W3C Recommendation</a>)
+			to address <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①">editorial</a> or <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑥">substantive</a> issues
+			that are discovered later.
+			However, <a href="#class-4">new features</a> can only be added
+			if the document already identifies itself
+			as intending to <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="allow-new-features">allow new features</dfn>.
+			Adding or removing this allowance is a <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑦">substantive change</a>.
+			Such an allowance cannot be added
+			to a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑥">technical report</a> previously published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①④">Recommendation</a> that did not allow such changes;
+			this requires a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑦">technical report</a> (which could, for example, be similarly named but with an incremented version number). </p>
+      <p>As technology evolves,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑤">W3C Recommendation</a> may become:</p>
+      <dl>
+       <dt> A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsSup">Superseded Recommendation</dfn> 
+       <dd>
+         A Superseded Recommendation is a specification
+					that has been replaced by a newer version
+					that W3C recommends for new adoption.
+					An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs">Obsolete</a> or Superseded specification
+					has the same status as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑥">W3C Recommendation</a> with regards to W3C Royalty-Free IPR Licenses granted under the Patent Policy. 
+        <p class="note" role="note"><span class="marker">Note:</span> When a Technical Report which had previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑦">Recommendation</a> is again published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑧">Recommendation</a> after following the necessary steps to <a href="#revising-rec">revise</a> it,
+					the latest version replaces the previous one,
+					without the need to invoke the steps of <a href="#rec-rescind">§ 6.3.12.3 Abandoning a W3C Recommendation</a>:
+					it is the same document, updated.
+					Explicitly declaring a documented superseded, using the process documented in <a href="#rec-rescind">§ 6.3.12.3 Abandoning a W3C Recommendation</a>,
+					is intended for cases where a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C①⑨">Recommendation</a> is superseded by a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑧">Technical Report</a> (or by a document managed outside of W3C).</p>
+       <dt> An <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RecsObs">Obsolete Recommendation</dfn> 
+       <dd> An Obsolete Recommendation is a specification
+					that W3C has determined lacks sufficient market relevance
+					to continue recommending it for implementation,
+					but which does not have fundamental problems
+					that would require it to be <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec">Rescinded</a>.
+					If an Obsolete specification gains sufficient market relevance,
+					W3C may decide to restore it to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⓪">Recommendation</a> status. 
+       <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="RescindedRec">Rescinded Recommendation</dfn> 
+       <dd> A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses,
+					and believes is unlikely to ever be restored to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②①">Recommendation</a> status.
+					See also “W3C Royalty-Free (RF) Licensing Requirements”
+					in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+      </dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="discontinuedREC">Discontinued Draft</dfn> 
+     <dd> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report①⑨">technical report</a> representing the state of a Recommendation-track document
+			at the point at which work on it was discontinued.
+			See <a href="#abandon-draft">§ 6.3.12.1 Abandoning an Unfinished Recommendation</a>. 
+    </dl>
+    <p>This Process defines certain <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑧">Recommendation Track</a> publications as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="patent-review-drafts">Patent Review Drafts</dfn>.
+	Under the 2004 Patent Policy (and its 2017 update) <a data-link-type="biblio" href="#biblio-patent-policy-2004" title="The W3C 2004 Patent Policy, Updated 2017">[PATENT-POLICY-2004]</a>,
+	these correspond to “Last Call Working Draft” in the Patent Policy;
+	Starting from the 2020 Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy-2020" title="The W3C 2020 Patent Policy">[PATENT-POLICY-2020]</a>,
+	these correspond to “Patent Review Draft” in the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑤">Working Groups</a> and <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①⓪">Interest Groups</a> <em class="rfc2119">may</em> make available <a data-link-type="dfn" href="#editors-draft" id="ref-for-editors-draft">Editor’s drafts</a>. <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Editor&apos;s Draft | Editor Draft | ED" id="editors-draft">Editor’s drafts</dfn> (<abbr>ED</abbr>) have no official standing whatsoever,
+	and do not necessarily imply consensus of a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑥">Working Group</a> or <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①①">Interest Group</a>,
+	nor are their contents endorsed in any way by W3C.</p>
+    <p>When publishing an updated version of an existing <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①①">Candidate Recommendation</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②②">Recommendation</a>,
+	technical reports are expected to meet the same maturity criteria as when they are first published under that status.
+	However, in the interest of replacing stale documents with improved ones in a timely manner,
+	if flaws have been discovered in the technical report after its initial publication as a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①②">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②③">REC</a> that would have been severe enough to reject that publication had they be known in time,
+	it is also permissible to publish an updated <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①③">CR</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②④">REC</a> following the usual process,
+	even if only some of these flaws have been satisfactorily addressed.</p>
+    <h4 class="heading settled" data-level="6.3.2" id="implementation-experience"><span class="secno">6.3.2. </span><span class="content"> Implementation Experience</span><a class="self-link" href="#implementation-experience"></a></h4>
+    <p>Implementation experience is required to show that a specification is sufficiently clear,
+	complete,
+	and relevant to market needs,
+	to ensure that independent interoperable implementations
+	of each feature of the specification will be realized.
+	While no exhaustive list of requirements is provided here,
+	when assessing that there is <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="adequate-implementation">adequate implementation experience</dfn> the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑤">Team</a> will consider (though not be limited to):</p>
+    <ul>
+     <li> is each feature of the current specification implemented,
+			and how is this demonstrated? 
+     <li> are there independent interoperable implementations of the current specification? 
+     <li> are there implementations created by people other than the authors of the specification? 
+     <li> are implementations publicly deployed? 
+     <li> is there implementation experience
+			at all levels of the specification’s ecosystem
+			(authoring, consuming, publishing…)? 
+     <li> are there reports of difficulties or problems with implementation? 
+    </ul>
+    <p>Planning and accomplishing a demonstration of (interoperable) implementations can be very time consuming.
+	Groups are often able to work more effectively
+	if they plan how they will demonstrate interoperable implementations
+	early in the development process;
+	for example, developing tests in concert with implementation efforts.</p>
+    <h4 class="heading settled" data-level="6.3.3" id="transition-reqs"><span class="secno">6.3.3. </span><span class="content"> Advancement on the Recommendation Track</span><a class="self-link" href="#transition-reqs"></a></h4>
+    <p>For <em>all</em> requests to advance a specification
+	to a new maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="trans-req">Transition Requests</dfn>),
+	the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request advancement. 
+     <li id="adv-verif-reqs"><a class="self-link" href="#adv-verif-reqs"></a> <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑥">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑦">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision⑨">Team decision</a>) <em class="rfc2119">must</em> be withheld if any Process requirements are not met
+			or if there remain any unresolved Formal Objections
+			(including any aspect <a data-link-type="dfn" href="#upheld" id="ref-for-upheld④">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑥">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed">fully addressed</a>),
+			or if the document does not adequately reflect all relevant decisions of the <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑦">W3C Council</a> (or its delegates).
+			If the <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑧">Team</a> rejects a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req①">Transition Request</a> it <em class="rfc2119">must</em> indicate its rationale
+			to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③④">Advisory Committee</a> and the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑦">Working Group</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change②">editorial changes</a> have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed②">formally address</a> all issues
+			raised about the document since the previous <a href="#maturity-stages">maturity stage</a>. 
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑧">Formal Objections</a>. 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑧">Working Group</a>’s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG③⑨">Working Group</a>. 
+    </ul>
+    <p>For a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd②">First Public Working Draft</a> there is no “previous maturity stage”,
+	so many requirements do not apply,
+	and verification is normally fairly straightforward.
+	For later stages,
+	especially transitions to <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①④">Candidate</a> or <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑤">Recommendation</a>,
+	there is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p><a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req②">Transition Requests</a> to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd③">First Public Working Draft</a> or <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑤">Candidate Recommendation</a> will not normally be approved
+	while a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⓪">Working Group</a>’s <a data-link-type="dfn" href="#charter" id="ref-for-charter①⑧">charter</a> is undergoing or awaiting a decision
+	on an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②②">Advisory Committee Review</a>.</p>
+    <h4 class="heading settled" data-level="6.3.4" id="update-reqs"><span class="secno">6.3.4. </span><span class="content"> Updating Mature Publications on the Recommendation Track</span><a class="self-link" href="#update-reqs"></a></h4>
+    <p>Certain requests to re-publish a specification
+	within its current maturity stage
+	(called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="update-requests">Update Requests</dfn>)
+	require extra verification.
+	For such <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests②">update requests</a>, the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request the update. 
+     <li> <em class="rfc2119">must</em> show that the changes have received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑦">wide review</a>. 
+     <li>
+       <em class="rfc2119">must </em> obtain <a data-link-type="dfn" href="#team" id="ref-for-team⑨⑨">Team</a> verification. <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⓪">Team</a> verification (a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①⓪">Team decision</a>): 
+      <ul>
+       <li data-md>
+        <p><em class="rfc2119">should</em> be withheld
+if any Process requirements are not met,</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+in consideration of unresolved Formal Objections
+(including any aspect <a data-link-type="dfn" href="#upheld" id="ref-for-upheld⑤">upheld</a> by a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑧">Council</a> but not yet <a data-link-type="dfn" href="#fully-addressed" id="ref-for-fully-addressed①">fully addressed</a>),</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+if the document does not adequately reflect
+all relevant decisions of a <a data-link-type="dfn" href="#w3c-council" id="ref-for-w3c-council③⑨">W3C Council</a> (or its delegates),</p>
+       <li data-md>
+        <p><em class="rfc2119">may</em> be withheld
+if the Team believes the Group is not making reasonable progress
+on addressing issues raised by individuals external to the Group.</p>
+      </ul>
+      <p>If the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪①">Team</a> rejects an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests③">Update Request</a>,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④①">Working Group</a>.
+			If it waives any Process requirements,
+			it must indicate its rationale to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑤">AC</a>.</p>
+     <li> <em class="rfc2119">must</em> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection③⑨">Formal Objections</a>. 
+     <li> <em class="rfc2119 ">must</em> publicly document of all new features
+			(<a href="#correction-classes">class 4 changes</a>) to the technical report
+			since the previous publication. 
+     <li> <em class="rfc2119">must</em> publicly document if other substantive changes
+			(<a href="#correction-classes">class 3 changes</a>) have been made,
+			and <em class="rfc2119">should</em> document the details of such changes. 
+     <li> <em class="rfc2119">should</em> publicly document if <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change③">editorial changes</a> changes have been made,
+			and <em class="rfc2119">may</em> document the details of such changes. 
+     <li> <em class="rfc2119">must</em> show that the revised specification
+			meets all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④②">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">should</em> report which, if any, of the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④③">Working Group</a>’s requirements
+			for this document have changed since the previous step. 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+     <li> <em class="rfc2119">should</em> provide information about implementations known to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④④">Working Group</a>. 
+    </ul>
+    <p>There is usually a formal review meeting
+	to verify that the requirements have been met.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests④">Update request</a> verification is expected to be fairly simple
+	compared to verification of a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req③">transition request</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪②">Team</a> <em class="rfc2119">must</em> announce the publication
+	of the revised specification
+	to other W3C groups and the Public.</p>
+    <h4 class="heading settled" data-level="6.3.5" id="first-wd"><span class="secno">6.3.5. </span><span class="content"> Publishing a First Public Working Draft</span><a class="self-link" href="#first-wd"></a></h4>
+    <p>To publish the <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd④">First Public Working Draft</a> of a document,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑤">Working Group</a> <em class="rfc2119">must</em> meet the applicable <a href="#transition-reqs">requirements for advancement</a>.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪③">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑤">First Public Working Draft</a> to other W3C groups and to the public.</p>
+    <h4 class="heading settled" data-level="6.3.6" id="revising-wd"><span class="secno">6.3.6. </span><span class="bs-old-id" id="revised-wd"></span><span class="content"> Revising a Working Draft</span><a class="self-link" href="#revising-wd"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑥">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑤">publish</a> a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑦">Working Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a Working draft, a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication. <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②①">Consensus</a> is not required,
+			as this is a procedural step, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑧">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑧">Working Draft</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change④">editorial changes</a> to the technical report
+			since the previous step, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups, 
+    </ul>
+    <p>Possible next steps for any Working Draft:</p>
+    <ul>
+     <li>Revised <a href="#revising-wd">Working Draft</a> 
+     <li><a href="#transition-cr">Candidate Recommendation</a> 
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.7" id="transition-cr"><span class="secno">6.3.7. </span><span class="bs-old-id" id="candidate-rec"></span><span class="content"> Transitioning to Candidate Recommendation</span><a class="self-link" href="#transition-cr"></a></h4>
+    <p>To publish a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑥">Candidate Recommendation</a>,
+	in addition to meeting the <a href="#transition-reqs">requirements for advancement</a> a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑦">Working Group</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> show that the specification
+			has met all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑧">Working Group</a> requirements,
+			or explain why the requirements have changed or been deferred, 
+     <li> <em class="rfc2119">must</em> document changes to dependencies during the development of the specification, 
+     <li> <em class="rfc2119">must</em> document
+			how <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation①">adequate implementation experience</a> will be demonstrated, 
+     <li> <em class="rfc2119">must</em> specify the deadline for comments,
+			delineating the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="candidate-recommendation-review-period">Candidate Recommendation review period</dfn>,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">must</em> show that the specification has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑧">wide review</a>, and 
+     <li> <em class="rfc2119">may</em> identify features in the document as <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="at-risk">at risk</dfn>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑥">Recommendation</a> without requiring an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑤">Update Request</a>. 
+    </ul>
+    <p>The first Candidate Recommendation publication
+	after verification of having met the requirements for a <a data-link-type="dfn" href="#trans-req" id="ref-for-trans-req④">Transition Request</a> is always a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑤">Candidate Recommendation Snapshot</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪④">Team</a> <em class="rfc2119">must</em> announce
+	the publication of the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑥">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑦">Candidate Recommendation Snapshot</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Recommendation</a>
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <p><a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑥">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 class="heading settled" data-level="6.3.8" id="revising-cr"><span class="secno">6.3.8. </span><span class="bs-old-id" id="revised-cr"></span><span class="content"> Revising a Candidate Recommendation</span><a class="self-link" href="#revising-cr"></a></h4>
+    <h5 class="heading settled" data-level="6.3.8.1" id="publishing-crrs"><span class="secno">6.3.8.1. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑧">Candidate Recommendation Snapshot</a></span><a class="self-link" href="#publishing-crrs"></a></h5>
+    <p>If there are any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change⑨">substantive changes</a> made to a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑦">Candidate Recommendation</a> since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot⑨">Candidate Recommendation Snapshot</a> other than to remove features explicitly identified as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk">at risk</a>,
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG④⑨">Working Group</a> <em class="rfc2119">must</em> meet the requirements of an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑥">update request</a> in order to republish.</p>
+    <p>In addition the Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> specify the deadline for further comments,
+			which <em class="rfc2119">must</em> be <strong>at least</strong> 28 days after publication,
+			and <em class="rfc2119">should</em> be longer for complex documents, 
+     <li> <em class="rfc2119">may</em> identify features in the document as <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk①">at risk</a>.
+			These features <em class="rfc2119">may</em> be removed
+			before advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑦">Recommendation</a> without requiring an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑦">Update Request</a>. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑤">Team</a> <em class="rfc2119">must</em> announce
+	the publication of a revised <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⓪">Candidate Recommendation Snapshot</a> to other W3C groups
+	and to the public.</p>
+    <p>To provide timely updates and patent protection,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①①">Candidate Recommendation Snapshot</a> <em class="rfc2119">should</em> be published
+	within 24 months of the Working Group accepting
+	any proposal for a substantive change
+	(and preferably sooner).
+	To make scheduling reviews easier,
+	a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①②">Candidate Recommendation Snapshot</a> <em class="rfc2119">should not</em> be published
+	more often than approximately once every 6 months.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①⓪">Substantive changes</a> trigger a new Exclusion Opportunity
+	per “Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.8.2" id="publishing-crud"><span class="secno">6.3.8.2. </span><span class="content"> Publishing a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft②">Candidate Recommendation Draft</a></span><a class="self-link" href="#publishing-crud"></a></h5>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⓪">Working Group</a> <em class="rfc2119">should</em> <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑥">publish</a> an <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft③">Update Draft</a> to the W3C Technical Reports page
+	when there have been significant changes
+	to the previous published document
+	that would benefit from review beyond the Working Group.</p>
+    <p>To publish a revision of a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft④">Candidate Recommendation Draft</a>,
+	a Working Group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record the group’s decision to request publication, 
+     <li> <em class="rfc2119">must</em> provide public documentation
+			of <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①①">substantive changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①③">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> provide public documentation
+			of significant <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑤">editorial changes</a> to the technical report
+			since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①④">Candidate Recommendation Snapshot</a>, 
+     <li> <em class="rfc2119">should</em> document outstanding issues,
+			and parts of the document on which the Working Group does not have consensus, 
+     <li> <em class="rfc2119">should</em> report which,
+			if any,
+			of the Working Group’s requirements for this document
+			have changed since the previous step, 
+     <li> <em class="rfc2119">should</em> report any changes in dependencies with other groups. 
+    </ul>
+    <p class="note" role="note"><span class="marker">Note:</span> A Working Group <em>does not</em> need to
+	meet the requirements of a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑤">Candidate Recommendation Snapshot</a> <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑧">update request</a> in order to publish a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑤">Candidate Recommendation Draft</a>.</p>
+    <p>Possible next steps after a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑥">Candidate Recommendation Draft</a>:</p>
+    <ul>
+     <li>Return to <a href="#revising-wd">Working Draft</a>
+     <li>A revised <a href="#publishing-crrs">Candidate Recommendation Snapshot</a>
+     <li>A revised <a href="#publishing-crud">Candidate Recommendation Draft</a>
+     <li><a href="#transition-pr">Recommendation</a>,
+		if there are no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①②">substantive change</a> other than dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk②">at risk</a> features
+     <li><a href="#abandon-draft">Discontinued Draft</a>
+    </ul>
+    <h4 class="heading settled" data-level="6.3.9" id="transition-rec"><span class="secno">6.3.9. </span><span class="bs-old-id" id="transition-pr"></span><span class="bs-old-id" id="rec-pr"></span><span class="bs-old-id" id="rec-publication"></span><span class="content"> Transitioning to Recommendation</span><a class="self-link" href="#transition-rec"></a></h4>
+    <p>When a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤①">Working Group</a> estimates
+	that a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑧">Candidate Recommendation</a> has fulfilled all the relevant criteria,
+	it <em class="rfc2119">may</em> <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision③">decide</a> to request advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑧">W3C Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.1" id="transition-rec-requirements"><span class="secno">6.3.9.1. </span><span class="content"> Requirements for Transition</span><a class="self-link" href="#transition-rec-requirements"></a></h5>
+    <p>In addition to meeting the <a href="#transition-reqs">requirements for advancement</a>,
+	the Working Group:</p>
+    <ul>
+     <li>
+       <em class="rfc2119">must</em> show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation②">adequate implementation experience</a> except where an exception is approved by a <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①①">Team Decision</a>. 
+      <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑥">Team</a> <em class="rfc2119">may</em> approve a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR①⑨">Candidate Recommendation</a> with minimal <a href="#implementation-experience">implementation experience</a> where there is a compelling reason to do so.
+			In such a case, the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑦">Team</a> <em class="rfc2119">must</em> explain the reasons for that decision,
+			and that information <em class="rfc2119">must</em> be included in the <a data-link-type="dfn" href="#reviewform" id="ref-for-reviewform②">Call for Review</a> proposing advancement to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C②⑨">W3C Recommendation</a>.</p>
+     <li> <em class="rfc2119">must</em> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review⑨">wide review</a>. 
+     <li> <em class="rfc2119">must</em> show that all issues
+			raised during the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period">Candidate Recommendation review period</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed③">formally addressed</a>. 
+     <li> <em class="rfc2119">must </em>identify any substantive issues
+			raised since the close of the <a data-link-type="dfn" href="#candidate-recommendation-review-period" id="ref-for-candidate-recommendation-review-period①">Candidate Recommendation review period</a>. 
+     <li> <em class="rfc2119">must</em> identify, in the document, where errata are tracked. 
+    </ul>
+    <p>Additionally,
+	if the document has previously been published as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⓪">W3C Recommendation</a>, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤②">Working Group</a> <em class="rfc2119">must not</em> include any <a href="#correction-classes">class 4 change</a> to that publication
+	unless it was explicitly marked as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features">allowing new features</a>,
+	and <em class="rfc2119">must not</em> include any such marking
+	if not already present.</p>
+    <p>If the document’s most recent publication is a <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑦">Candidate Recommendation Draft</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑧">Team</a> <em class="rfc2119">must</em> verify
+	that it contains no changes since the previous <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑥">Candidate Recommendation Snapshot</a> other than:</p>
+    <ul>
+     <li data-md>
+      <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑥">editorial changes</a>,</p>
+     <li data-md>
+      <p>the addition or removal of a statement as to whether the document will <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features①">allow new features</a> after its publication as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③①">Recommendation</a>.</p>
+     <li data-md>
+      <p>dropping <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk③">at risk</a> features</p>
+    </ul>
+    <p>Otherwise, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤③">Working Group</a> <em class="rfc2119">must</em> republish it
+	as a <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑦">Candidate Recommendation Snapshot</a> prior to initiating the review.</p>
+    <h5 class="heading settled" data-level="6.3.9.2" id="initiating-rec-review"><span class="secno">6.3.9.2. </span><span class="content"> Initiating Review</span><a class="self-link" href="#initiating-rec-review"></a></h5>
+    <p>If all the criteria above are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①⓪⑨">Team</a> <em class="rfc2119">must</em> begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②③">Advisory Committee Review</a> on the question of whether the identified <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②⓪">Candidate Recommendation</a> is appropriate to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑦">publish</a> as a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③②">W3C Recommendation</a>.
+	The deadline for <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②④">Advisory Committee review</a> <em class="rfc2119">must</em> allow <strong>at least</strong> 28 days,
+	and <em class="rfc2119">must</em> end at least 10 days
+	after the end of the last Exclusion Opportunity
+	per ”Exclusion From W3C RF Licensing Requirements”
+	in the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.3" id="rec-review-resolution"><span class="secno">6.3.9.3. </span><span class="content"> Resolution of Review</span><a class="self-link" href="#rec-review-resolution"></a></h5>
+    <p>If there was any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④⓪">Formal Objection</a> during the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑤">Advisory Committee Review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⓪">Team</a> <em class="rfc2119">must</em> publish the substantive content of the <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑤">dissent</a> to W3C and the general public,
+	and the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③③">W3C Recommendation</a> <em class="rfc2119">must not</em> be published
+	unless all <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④①">Formal Objections</a> to the document have been retracted or <a data-link-type="dfn" href="#overrule" id="ref-for-overrule③">overruled</a> and at least 14 days have elapsed since the publication of the corresponding <a data-link-type="dfn" href="#council-report" id="ref-for-council-report⑤">Council Report</a>.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③④">Recommendation</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①③">W3C Decision</a>.
+	The <a data-link-type="dfn" href="#team" id="ref-for-team①①①">Team</a> <em class="rfc2119">must</em> announce the publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑤">W3C Recommendation</a> to the <a href="#AC">Advisory Committee</a>,
+	to other W3C groups
+	and to the public. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑥">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑥">Advisory Committee Appeal</a> of the decision to advance the technical report.</p>
+    <p>The newly published <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑥">Recommendation</a> <em class="rfc2119">must not</em> make any <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①③">substantive changes</a> to the document
+	compared to the <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑧">Candidate Recommendation Snapshot</a> submitted for AC Review,
+	other than dropping features identified <a data-link-type="dfn" href="#at-risk" id="ref-for-at-risk④">at risk</a>.</p>
+    <h5 class="heading settled" data-level="6.3.9.4" id="rec-next-steps"><span class="secno">6.3.9.4. </span><span class="content"> Next Steps from W3C Recommendation</span><a class="self-link" href="#rec-next-steps"></a></h5>
+    <p>Possible next steps:
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑦">W3C Recommendation</a> normally retains its status indefinitely.
+	However it <em class="rfc2119">may</em> be:</p>
+    <ul>
+     <li> republished as a <a href="#revising-rec">revised Recommendation</a>, or 
+     <li> republished as a <a href="#transition-cr">Candidate Recommendation</a> or <a href="#revising-wd">Working Draft</a> to be developed towards a revised <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑧">Recommendation</a>, or 
+     <li> declared <a href="#rec-rescind">superseded or obsolete</a>, or 
+     <li> <a href="#rec-rescind">rescinded</a>. 
+    </ul>
+    <h4 class="heading settled" data-level="6.3.10" id="revising-rec"><span class="secno">6.3.10. </span><span class="bs-old-id" id="revised-rec"></span><span class="bs-old-id" id="rec-modify"></span><span class="content"> Revising a W3C Recommendation</span><a class="self-link" href="#revising-rec"></a></h4>
+    <h5 class="heading settled" data-level="6.3.10.1" id="revised-rec-editorial"><span class="secno">6.3.10.1. </span><span class="bs-old-id" id="revised-rec-markup"></span><span class="content"> Revising a Recommendation: Editorial Changes</span><a class="self-link" href="#revised-rec-editorial"></a></h5>
+    <p><a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑦">Editorial changes</a> to a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C③⑨">Recommendation</a> require no technical review of the intended changes.
+	A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤④">Working Group</a>,
+	provided there are no votes against the <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision④">decision</a> to publish, <em class="rfc2119">may</em> request publication of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⓪">Recommendation</a> to make this class of change without passing through earlier maturity stages.
+	(See <a href="#class-1">class 1</a> and <a href="#class-2">class 2 changes</a>.)</p>
+    <h5 class="heading settled" data-level="6.3.10.2" id="revised-rec-substantive"><span class="secno">6.3.10.2. </span><span class="content"> Revising a Recommendation: Substantive Changes</span><a class="self-link" href="#revised-rec-substantive"></a></h5>
+    <p>Tentative corrections (see <a href="#class-3">class 3 changes</a>) <em class="rfc2119">may</em> be annotated into a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④①">Recommendation</a> using <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction④">candidate corrections</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑤">Candidate corrections</a> do not normatively modify the document;
+	they editorially indicate how one might do so.
+	They are therefore published following the provisions of <a href="#revised-rec-editorial">§ 6.3.10.1 Revising a Recommendation: Editorial Changes</a>.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-correction" id="ref-for-candidate-correction⑥">candidate correction</a> can be made normative
+	and be folded into the main text of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④②">Recommendation</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④③">Recommendation</a>,
+	including review by the community to ensure
+	its technical and editorial soundness.
+	To validate this, the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑤">Working Group</a> must request
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review">Last Call for Review of Proposed Amendments</a>,
+	followed by an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests⑨">update request</a>.
+	See <a href="#change-review">§ 6.3.10.4 Incorporating Candidate Amendments</a>.</p>
+    <p>Alternatively,
+	a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑥">Working Group</a> <em class="rfc2119">may</em> incorporate the changes
+	and <a href="#revising-wd">publish as a Working Draft</a>—​or, if the relevant criteria are fulfilled, <a href="#transition-cr">publish as a Candidate Recommendation</a>—​and advance the specification from that state.
+	(See <a href="#correction-classes">class 3 changes</a>.)</p>
+    <h5 class="heading settled" data-level="6.3.10.3" id="revised-rec-features"><span class="secno">6.3.10.3. </span><span class="content"> Revising a Recommendation: New Features</span><a class="self-link" href="#revised-rec-features"></a></h5>
+    <p>For <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④④">Recommendations</a> explicitly identified as <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features②">allowing new features</a>,
+	tentative new features (see <a href="#correction-classes">class 4 changes</a>) <em class="rfc2119">may</em> be added as <a data-link-type="dfn" href="#candidate-addition" id="ref-for-candidate-addition①">candidate additions</a> in annotations,
+	and <a href="#correction-classes">class 4 changes</a> may be normatively incorporated
+	in the same fashion as <a href="#correction-classes">class 3 changes</a> in <a href="#revised-rec-substantive">§ 6.3.10.2 Revising a Recommendation: Substantive Changes</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Limiting the addition of new features to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑤">Recommendations</a> that explicitly allow them
+	enables third parties to depend on a stable feature-set for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑥">Recommendations</a> that do not advertise that ability,
+	as was the case for all <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑦">Recommendations</a> prior to the 2020 revision of this Process.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> When a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑧">Recommendation</a> does not <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features③">allow new features</a>,
+	new features can be added by creating a new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⓪">technical report</a> and following the full process of advancing that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②①">technical report</a> to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C④⑨">Recommendation</a>—​beginning with a new <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑥">First Public Working Draft</a>.
+	Such <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②②">technical reports</a> could be written to represent
+	additional modules building on top of the original <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⓪">Recommendation</a> of the core technology,
+	or an expanded replacement of the original <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤①">Recommendation</a> of the core technology
+	(in which case the new <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②③">technical report</a> will typically have the same name as the original,
+	with an incremented version number).</p>
+    <h5 class="heading settled" data-level="6.3.10.4" id="change-review"><span class="secno">6.3.10.4. </span><span class="content"> Incorporating Candidate Amendments</span><a class="self-link" href="#change-review"></a></h5>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-review">Last Call for Review of Proposed Amendments</dfn> verifies acceptance by the W3C community of <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment③">candidate amendments</a> by combining an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑥">AC Review</a> with a patent exclusion opportunity.</p>
+    <p>The <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review①">Last Call for Review of Proposed Amendments</a> must be announced to other W3C groups, the public, and the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑦">Advisory Committee</a>.
+	The announcement <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Identify whether this is a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</dfn>, <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</dfn>,
+			or <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</dfn>. 
+     <li> Identify the specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment④">candidate amendments</a> under review
+			as <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="proposed-amendments">proposed amendments</dfn> (<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="proposed-corrections">proposed corrections</dfn>/<dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="proposed-additions"><span class="bs-old-id" id="proposed-addition"></span>proposed additions</dfn>). 
+     <li> Specify the deadline for review comments,
+			which must not be any sooner than 60 days from the Call for Review. 
+     <li> Solicit review and, if it does not already have it, implementation experience. 
+    </ul>
+    <p>The combination of the existing <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤②">Recommendation</a> with the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments">proposed amendments</a> included in the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review②">Last Call for Review of Proposed Amendments</a> is considered a <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts②">Patent Review Draft</a> for the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>.
+	Also, the review initiated by the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review③">Last Call for Review of Proposed Amendments</a> is an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑦">Advisory Committee Review</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> <a data-link-type="dfn" href="#last-call-for-review-of-proposed-additions" id="ref-for-last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a> and <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections-and-additions" id="ref-for-last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a> can only be issued for <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤③">Recommendations</a> that <a data-link-type="dfn" href="#allow-new-features" id="ref-for-allow-new-features④">allow new features</a>.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑦">Working Group</a> <em class="rfc2119">may</em> batch
+	multiple <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①">proposed amendments</a> into a single <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review④">Last Call for Review of Proposed Amendments</a>.
+	To facilitate review,
+	a <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑤">Last Call for Review of Proposed Amendments</a> on a given specification <em class="rfc2119">should not</em> be issued more frequently
+	than approximately once every 6 months.</p>
+    <p>At the end of the <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑥">Last Call for Review of Proposed Amendments</a>,
+	the <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①④">W3C Decision</a> may either be
+	to reject the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments②">proposed amendment</a>,
+	or to clear the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments③">proposed amendment</a> for advancement as is,
+	or to return the proposal to the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑧">Working Group</a> with a request to <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed④">formally address</a> comments made on the changes under review.
+	If the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑤⑨">Working Group</a> needs to amend a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments④">proposed amendment</a> in response to review feedback
+	it must issue another <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑦">Last Call for Review of Proposed Amendments</a> on the revised change
+	before it can be incorporated into the main text.</p>
+    <p>Once all comments on a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑤">proposed amendment</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑤">formally addressed</a>,
+	and after the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⓪">Working Group</a> can show <a data-link-type="dfn" href="#adequate-implementation" id="ref-for-adequate-implementation③">adequate implementation experience</a> and the fulfillment of all other requirements of Recommendation text,
+	it may incorporate the <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑥">proposed amendment</a> into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤④">Recommendation</a> by issuing an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①⓪">update request</a> for publication of the updated <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑤">Recommendation</a>.</p>
+    <p>To ensure adequate review of <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑦">proposed amendment</a> combinations,
+	only <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑧">proposed amendments</a> included in the most recent <a data-link-type="dfn" href="#last-call-review" id="ref-for-last-call-review⑧">Last Call for Review of Proposed Amendments</a> can be incorporated into the normative <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑥">Recommendation</a> text.
+	(Thus if incorporation of a <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments⑨">proposed amendment</a> is postponed,
+	it may need to be included in multiple Last Calls for Review of Proposed Amendments.)</p>
+    <h4 class="heading settled" data-level="6.3.11" id="rec-track-regression"><span class="secno">6.3.11. </span><span class="content"> Regression on the Recommendation Track</span><a class="self-link" href="#rec-track-regression"></a></h4>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥①">Working Group</a> may republish a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track⑨">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②④">technical report</a> at a lower <a href="#maturity-stages">maturity stage</a> by fulfilling the requirements to transition to that maturity stage,
+	as described above.</p>
+    <p>Additionally,
+	with the approvals (by <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑤">group decision</a>) of each of the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑤">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③①">AB</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①①②">Team</a> <em class="rfc2119">may</em> return
+	the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑤">technical report</a> to a lower <a href="#maturity-stages">maturity stage</a> in response to <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①⓪">wide review</a> or a <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④②">formal objection</a>.</p>
+    <h4 class="heading settled" data-level="6.3.12" id="tr-end"><span class="secno">6.3.12. </span><span class="content"> Retiring Recommendation Track Documents</span><a class="self-link" href="#tr-end"></a></h4>
+    <p>Work on a technical report <em class="rfc2119">may</em> cease at any time.
+	Work <em class="rfc2119 new">should</em> cease
+	if W3C or a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥②">Working Group</a> determines
+	that it cannot productively carry the work any further.</p>
+    <h5 class="heading settled" data-level="6.3.12.1" id="abandon-draft"><span class="secno">6.3.12.1. </span><span class="content"> Abandoning an Unfinished Recommendation</span><a class="self-link" href="#abandon-draft"></a></h5>
+    <p>Any <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⓪">Recommendation-track</a> <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑥">technical report</a> no longer intended
+	to advance or to be maintained,
+	and that is not being rescinded, <em class="rfc2119">should</em> be <a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑧">published</a> as a <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC">Discontinued Draft</a>,
+	with no <a data-link-type="dfn" href="#substantive-change" id="ref-for-substantive-change①④">substantive change</a> compared to the previous publication.
+	This can happen if
+	the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥③">Working Group</a> decided
+	to abandon work on the report,
+	or as the result of an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑧">AC Review</a> requiring the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥④">Working Group</a> to discontinue work on the technical report before completion.
+	If a <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑤">Working Group</a> is made to <a href="#GeneralTermination">close</a>,
+	W3C <em class="rfc2119">must</em> re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing⑨">publish</a> any unfinished <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑦">technical report</a> on the Recommendation track as <a data-link-type="dfn" href="#discontinuedREC" id="ref-for-discontinuedREC①">Discontinued Draft</a>.</p>
+    <p>Such a document should include in its status section
+	an explanation of why it was discontinued.</p>
+    <p>A <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑥">Working Group</a> <em class="rfc2119">may</em> resume work
+	on such a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑧">technical report</a> within the scope of its charter
+	at any time,
+	by re-<a data-link-type="dfn" href="#publishing" id="ref-for-publishing①⓪">publishing</a> it as a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD⑨">Working Draft</a>.</p>
+    <h5 class="heading settled" data-level="6.3.12.2" id="rescind-cr"><span class="secno">6.3.12.2. </span><span class="content"> Rescinding a Candidate Recommendation</span><a class="self-link" href="#rescind-cr"></a></h5>
+    <p>The process for rescinding a <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②①">Candidate Recommendation</a> is the same as for rescinding a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑦">Recommendation</a>.</p>
+    <h5 class="heading settled" data-level="6.3.12.3" id="rec-rescind"><span class="secno">6.3.12.3. </span><span class="content"> Abandoning a W3C Recommendation</span><a class="self-link" href="#rec-rescind"></a></h5>
+    <p>It is possible that W3C decides
+	that implementing a particular <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑧">Recommendation</a> is no longer recommended.
+	There are three designations for such specifications,
+	chosen depending on the advice W3C wishes to give about further use of the specification.</p>
+    <p>W3C <em class="rfc2119">may</em> obsolete a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑤⑨">Recommendation</a>,
+	for example if the W3C Community decides that the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⓪">Recommendation</a> no longer represents best practices,
+	or is not adopted and is not apparently likely to be adopted.
+	An <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs①">Obsolete Recommendation</a> <em class="rfc2119">may</em> be restored to normal <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥①">Recommendation</a>,
+	for example because despite marking it Obsolete the specification is later more broadly adopted.</p>
+    <p>W3C <em class="rfc2119">may</em> declare a Recommendation Superseded
+	if a newer version exists which W3C recommends for new adoption.
+	The process for declaring a Recommendation Superseded is the same as for declaring it Obsolete, below;
+	only the name and explanation change.</p>
+    <p>W3C <em class="rfc2119">may</em> rescind a Recommendation
+	if W3C believes there is no reasonable prospect of it being restored
+	for example due to burdensome patent claims that affect implementers and cannot be resolved;
+	see the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> and in particular “W3C Royalty-Free (RF) Licensing Requirements”
+	and “PAG Conclusion”.</p>
+    <p>W3C only rescinds, supersedes, or obsoletes entire Recommendations.
+	A <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥②">Recommendation</a> can be both superseded and obsolete.
+	To rescind, supersede, or obsolete some part of a Recommendation,
+	W3C follows the process for <a href="#revising-rec">modifying a Recommendation</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> For the purposes of the W3C Patent Policy, <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs②">Obsolete</a> or <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup">Superseded Recommendation</a> has the status of an active <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥③">Recommendation</a>,
+	although it is not advised for future implementation;
+	a <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec①">Rescinded Recommendation</a> ceases to be in effect
+	and no new licenses are granted under the Patent Policy.</p>
+    <figure>
+     <svg viewBox="0 0 300 135" width="100%" xmlns="http://www.w3.org/2000/svg">
+      <title>Supersede, Obsolete or Rescind a W3C Recommendation</title>
+      <g role="list">
+       <g role="listitem">
+        <ellipse cx="40" cy="50" fill="#fff" id="rec-3" role="img" rx="30" ry="20" stroke="black" stroke-width="2">
+         <title>Recommendation (Rec)</title>
+        </ellipse>
+        <text aria-hidden="true" font-size="18" stroke-width=".3" text-anchor="middle" x="40" y="55">REC</text>
+        <g role="list">
+         <g role="listitem">
+          <title>A major problem and an AC review can lead to a Recommendation being Rescinded.
+								There are no new IPR licences issued under the W3C Patent Policy,
+								and reinstating the Recommendation requires going through the full Rec-track process again.</title>
+          <path d="M40,29v-5s0,-5 5,-5h150" fill="none" stroke="black" stroke-dasharray="3 1" stroke-width="2"></path>
+          <text font-size="8" text-anchor="middle" x="105" y="16">Major problem, AC review</text>
+          <polygon points="195,16 195,22 199,19"></polygon>
+          <rect fill="#fff" height="36" id="rescinded" role="img" stroke="black" stroke-width="2" width="80" x="200" y="4"></rect>
+          <title>Rescinded Recommendation - no new IPR licenses</title>
+          <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="240" y="19">Rescinded</text>
+          <path d="M198,42l84,-40" stroke="red" stroke-width="2"></path>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="28">No new IPR licenses</text>
+          <text aria-hidden="true" font-size="8" stroke-width=".3" text-anchor="middle" x="240" y="37">No reinstatement path</text>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="black" stroke-dasharray="4 4"></path>
+           <title>With little uptake, following AC review a specification may become an Obsolete Recommendation</title>
+           <path d="M69,45h93c10,0 20,30 30,30h10" fill="none" stroke="red" stroke-dasharray="2 6" stroke-dashoffset="3"></path>
+           <polygon points="204,75 200,72 200,78"></polygon>
+           <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="42">Minimal usage, AC review</text>
+           <rect fill="#fff" height="26" id="obsolete" rx="8" stroke="black" stroke-dasharray="3 3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <title>Obsolete Recommendation</title>
+           <rect fill="none" height="26" rx="8" stroke="red" stroke-dasharray="3 3" stroke-dashoffset="3" stroke-width="2" width="75" x="205" y="66"></rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="242" y="84">Obsolete</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <path d="M204,82h-149s-5,0 -5,-5v-5" fill="none" stroke="black" stroke-dasharray="2 3"></path>
+             <title>If there is new uptake, with AC review an Obsolete Recommendation may return to normal Recommendation status</title>
+             <polygon points="50,70 47,74 53,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="115" y="79">New uptake, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+         <g role="listitem">
+          <g role="img">
+           <path d="M40,71v29s0,5 5,5h140" fill="none" stroke="black"></path>
+           <polygon points="189,105 185,102 185,108"></polygon>
+           <text font-size="8" text-anchor="middle" x="115" y="102">Replaced by a new version, AC review</text>
+           <rect fill="#fff" height="30" id="superseded" role="img" rx="3" stroke="#600" stroke-width="2" width="90" x="190" y="100">
+            <title>Superseded Recommendation</title>
+           </rect>
+           <text aria-hidden="true" font-size="16" stroke-width=".3" text-anchor="middle" x="235" y="119">Superseded</text>
+          </g>
+          <g role="list">
+           <g role="listitem">
+            <g role="img">
+             <title>A Superseded Recommendation can become a normal Recommendation with AC review</title>
+             <path d="M189,125h-154s-5,0 -5,-5v-52" fill="none" stroke="black" stroke-dasharray="1 4"></path>
+             <polygon points="30,70 27,74 33,74"></polygon>
+             <text aria-hidden="true" font-size="8" text-anchor="middle" x="110" y="122">Oops! The Web still needs this, AC review</text>
+            </g>
+           </g>
+          </g>
+         </g>
+        </g>
+       </g>
+      </g>
+     </svg>
+     <figcaption>Non-Normative Summary of the Paths to Retiring a W3C Recommendation</figcaption>
+    </figure>
+    <h5 class="heading settled" data-level="6.3.12.4" id="deactivation"><span class="secno">6.3.12.4. </span><span class="content"> Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation</span><a class="self-link" href="#deactivation"></a></h5>
+    <p>The process of rescinding, obsoleting,
+	superseding,
+	or restoring
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥④">Recommendation</a> can be initiated
+	either by a request from the <a data-link-type="dfn" href="#team" id="ref-for-team①①③">Team</a> or via a request from any of the following:</p>
+    <ul>
+     <li> The <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑦">Working Group</a> who produced,
+			or is chartered to maintain,
+			the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑤">Recommendation</a> 
+     <li> The <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑥">TAG</a>, if there is no such <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑧">Working Group</a> 
+     <li> Any individual who made a request to the relevant <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑥⑨">Working Group</a> as described above,
+			or the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑦">TAG</a> if such a group does not exist, to obsolete, rescind, supersede, or restore a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑥">Recommendation</a>,
+			where the request was not answered within 90 days 
+     <li> 5% of <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑦">Advisory Committee representatives</a> of <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑤">Members</a> in <a data-link-type="dfn" href="#good-standing" id="ref-for-good-standing②">Good Standing</a> 
+    </ul>
+    <p id="proposed-rescinded-rec">The <a data-link-type="dfn" href="#team" id="ref-for-team①①④">Team</a> <em class="rfc2119">must</em> then
+	submit the request to the <a href="#AC">Advisory Committee</a> for review.
+	For any <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review②⑨">Advisory Committee review</a> of a proposal to
+	rescind,
+	obsolete,
+	supersede,
+	or restore
+	a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑦">Recommendation</a> the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑤">Team</a> <em class="rfc2119">must</em>: </p>
+    <ul>
+     <li> announce the proposal to all <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⓪">Working Group</a> <a data-link-type="dfn" href="#GeneralChairs" id="ref-for-GeneralChairs③②">Chairs</a>,
+			and to the Public,
+			as well as to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑧">Advisory Committee</a> 
+     <li> indicate that this is a proposal to
+			Rescind,
+			Obsolete,
+			Supersede,
+			or restore,
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑧">Recommendation</a> as appropriate 
+     <li> identify the <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑥⑨">Recommendation</a> by URL 
+     <li> publish a rationale for the proposal 
+     <li> identify known dependencies
+			and solicit review from all dependent <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦①">Working Groups</a> 
+     <li> solicit public review 
+     <li> specify the deadline for review comments,
+			which <em class="rfc2119">must</em> be at least 28 days
+			after the announcement 
+    </ul>
+    <p>and <em class="rfc2119">should</em></p>
+    <ul>
+     <li> identify known implementations. 
+    </ul>
+    <p>If there was any <a data-link-type="dfn" href="#def-Dissent" id="ref-for-def-Dissent⑥">dissent</a> in the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⓪">Advisory Committee review</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑥">Team</a> <em class="rfc2119">must</em> publish
+	the substantive content of the dissent to W3C <strong>and the public</strong>,
+	and <em class="rfc2119">must</em> <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑥">formally address</a> the dissent
+	at least 14 days
+	before publication as an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs③">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec②">Rescinded Recommendation</a>.</p>
+    <p>The <a href="#AC">Advisory Committee</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑦">Advisory Committee Appeal</a> of the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑦">Team</a>’s decision.</p>
+    <p>W3C <em class="rfc2119">must</em> publish an <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs④">Obsolete</a> or <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec③">Rescinded Recommendation</a> 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 <em class="rfc2119">should</em> link
+	to the explanation of <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">Obsoleting and Rescinding W3C Specifications</a> <a data-link-type="biblio" href="#biblio-obs-resc" title="Obsoleting and Rescinding W3C Specifications">[OBS-RESC]</a> as appropriate.</p>
+    <p>Once W3C has published a Rescinded Recommendation,
+	future W3C technical reports <em class="rfc2119">must not</em> include normative references
+	to that technical report.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> W3C strives to ensure that all Technical Reports
+	will continue to be available at their version-specific URL.</p>
+    <h3 class="heading settled" data-level="6.4" id="note-track"><span class="secno">6.4. </span><span class="content"> The Note Track (Notes and Statements)</span><a class="self-link" href="#note-track"></a></h3>
+    <h4 class="heading settled" data-level="6.4.1" id="Note"><span class="secno">6.4.1. </span><span class="content"> Group Notes</span><a class="self-link" href="#Note"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Group Note | Note" id="WGNote">Group Note</dfn> (<abbr>NOTE</abbr>)
+	is published
+	to provide a stable reference for a useful document
+	that is not intended to be a formal standard.</p>
+    <p><a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦②">Working Groups</a>, <a data-link-type="dfn" href="#GroupsIG" id="ref-for-GroupsIG①②">Interest Groups</a>,
+	the <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑧">TAG</a> and the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③②">AB</a> <em class="rfc2119">may</em> publish work as <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote②">Notes</a>.
+	Examples include:</p>
+    <ul>
+     <li> supporting documentation for a specification,
+			such as explanations of design principles
+			or use cases and requirements 
+     <li> non-normative guides to good practices 
+    </ul>
+    <p>Some <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote③">Notes</a> are developed through successive <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Note Draft" data-noexport id="note-draft"><span class="bs-old-id" id="draft-note"></span>Note Drafts</dfn> before publication as a full <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote④">Notes</a>,
+	while others are <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①①">published</a> directly as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑤">Note</a>.
+	There are few formal requirements to <a data-link-type="dfn" href="#publishing" id="ref-for-publishing①②">publish</a> a document as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑥">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft">Note Draft</a>,
+	and they have no standing as a recommendation of W3C
+	but are simply documents preserved for historical reference.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> does not apply any licensing requirements or commitments for <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑦">Notes</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft①">Note Drafts</a>.</p>
+    <h4 class="heading settled" data-level="6.4.2" id="publishing-notes"><span class="secno">6.4.2. </span><span class="content"> Publishing Notes</span><a class="self-link" href="#publishing-notes"></a></h4>
+    <p>In order to publish a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑧">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft②">Note Draft</a>,
+	the group:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> record their decision
+			to request publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote⑨">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft③">Note Draft</a>, and 
+     <li> <em class="rfc2119">should</em> publish documentation
+			of significant changes to the technical report
+			since any previous publication. 
+    </ul>
+    <p>Both <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⓪">Notes</a> and <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft④">Note Drafts</a> can be updated by republishing
+	as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①①">Note</a> or <a data-link-type="dfn" href="#note-draft" id="ref-for-note-draft⑤">Note Draft</a>.
+	A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report②⑨">technical report</a> <em class="rfc2119">may</em> remain
+	a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①②">Note</a> indefinitely.</p>
+    <h4 class="heading settled" data-level="6.4.3" id="w3c-statement"><span class="secno">6.4.3. </span><span class="bs-old-id" id="memo"></span><span class="content"> Elevating Group Notes to W3C Statement status</span><a class="self-link" href="#w3c-statement"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-lt="Statement | W3C Statement" data-noexport id="statement">W3C Statement</dfn> is a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①③">Note</a> that has been endorsed by W3C as a whole.
+	In order to elevate a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①④">Note</a> to <a data-link-type="dfn" href="#statement" id="ref-for-statement②">W3C Statement</a> status,
+	A group <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> show that the document has received <a data-link-type="dfn" href="#dfn-wide-review" id="ref-for-dfn-wide-review①①">wide review</a>. 
+     <li> record the group’s decision to request publication as a <a data-link-type="dfn" href="#statement" id="ref-for-statement③">W3C Statement</a>. 
+     <li> show that all issues raised against the document
+			since its first publication as a <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑤">Note</a> have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑦">formally addressed</a>. 
+     <li> provide public documentation of any <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④③">Formal Objections</a>. 
+    </ul>
+    <p>A <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑥">Note</a> specifying implementable technology <em class="rfc2119">should not</em> be elevated to <a data-link-type="dfn" href="#statement" id="ref-for-statement④">W3C Statement</a> status;
+	if it does,
+	the request to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑤">Statement</a> <em class="rfc2119">must</em> include rationale
+	for why it should be elevated,
+	and why it is not on the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①①">Recommendation track</a>.</p>
+    <p>Once these conditions are fulfilled,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①①⑧">Team</a> <em class="rfc2119">must</em> then
+	begin an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③①">Advisory Committee Review</a> on the question of
+	whether the document is appropriate to publish as a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑥">W3C Statement</a>.
+	During this review period,
+	the <a data-link-type="dfn" href="#WGNote" id="ref-for-WGNote①⑦">Note</a> <em class="rfc2119">must not</em> be updated.</p>
+    <p>The decision to advance a document to <a data-link-type="dfn" href="#statement" id="ref-for-statement⑦">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑤">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑧">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑧">Advisory Committee Appeal</a> of the decision.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①①⑨">Team</a> must announce the publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑧">W3C Statement</a> to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee③⑨">Advisory Committee</a>, other W3C groups, and the public.</p>
+    <h4 class="heading settled" data-level="6.4.4" id="revising-memo"><span class="secno">6.4.4. </span><span class="content"> Revising W3C Statements</span><a class="self-link" href="#revising-memo"></a></h4>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑥">group decision</a> to do so,
+	groups can request publication of a <a data-link-type="dfn" href="#statement" id="ref-for-statement⑨">W3C Statement</a> with <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑧">editorial changes</a>—​including <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑤">candidate amendment</a>—​without any additional process.</p>
+    <p>A <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑥">candidate amendment</a> can be folded into the main text of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①⓪">W3C Statement</a>,
+	once it has satisfied all the same criteria
+	as the rest of the <a data-link-type="dfn" href="#statement" id="ref-for-statement①①">Statement</a>,
+	including review by the community to ensure
+	the substantive and editorial soundness of the <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑦">candidate amendments</a>.
+	To validate this, the group must request
+	an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③②">Advisory Committee review</a> of the changes it wishes to incorporate.
+	The specific <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑧">candidate amendments</a> under review <em class="rfc2119">must</em> be identified as <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①⓪">proposed amendments</a> just as in a <a data-link-type="dfn" href="#last-call-for-review-of-proposed-corrections" id="ref-for-last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a>.</p>
+    <p>The decision to incorporate <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①①">proposed amendments</a> into <a data-link-type="dfn" href="#statement" id="ref-for-statement①②">W3C Statement</a> is a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑥">W3C Decision</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative②⑨">Advisory Committee representatives</a> may initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal⑨">Advisory Committee Appeal</a> of the decision.</p>
+    <h3 class="heading settled" data-level="6.5" id="registries"><span class="secno">6.5. </span><span class="content"> The Registry Track</span><a class="self-link" href="#registries"></a></h3>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry">registry</dfn> documents a data set
+	consisting of one or more <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry table" id="registry-table">registry tables</dfn>,
+	each table representing an updatable collection
+	of logically independent, consistently-structured <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="registry entry" id="registry-entry">registry entries</dfn>.
+	A registry consists of:</p>
+    <ul>
+     <li>the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①">registry definition</a>, defining how the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②">registry tables</a> are structured and maintained 
+     <li>one or more <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table③">registry tables</a>, holding the data set represented by the <a data-link-type="dfn" href="#registry" id="ref-for-registry②">registry</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data">registry data</dfn>) 
+    </ul>
+    <p>The purposes of maintaining a <a data-link-type="dfn" href="#registry" id="ref-for-registry③">registry</a> can include:</p>
+    <dl>
+     <dt>non-collision 
+     <dd> Avoiding the problem
+			of two entities using the same value with different semantics. 
+     <dt>non-duplication 
+     <dd> Avoiding the problem
+			of having two or more different values in use with the same semantics. 
+     <dt>information 
+     <dd> Providing a central index
+			where anyone can find out
+			what a value means
+			and what its formal definition is
+			(and where it is). 
+     <dt>submission 
+     <dd> Ease of adding new terms,
+			including by stakeholders external to the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian">custodian</a> organization. 
+     <dt>consensus 
+     <dd> Promoting a clear consensus of the community on the terms. 
+    </dl>
+    <p>This section of the W3C Process provides a specialized process
+	facilitating the publication and maintenance of such <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table④">registry tables</a>,
+	particularly those required by or closely related to <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦⓪">W3C Recommendations</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Not every table in a specification is a potential registry.
+	If the intent or effect is that the table enumerates
+	all the possibilities the authors of the specification expect or envisage,
+	then the table by itself is enough.
+	Similarly, if the table is managed by the Working Group
+	and only updated as part of specification update,
+	then the complexities of registry management are not needed.</p>
+    <h4 class="heading settled" data-level="6.5.1" id="reg-def"><span class="secno">6.5.1. </span><span class="content"> Registry Definitions</span><a class="self-link" href="#reg-def"></a></h4>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-definition">registry definition</dfn> defines what each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑤">registry table</a> is and how it is maintained.
+	It <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Define the scope and purpose of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑥">registry table</a>. 
+     <li> Define the fields of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑦">registry table</a> and their constraints
+			(e.g. values must be drawn from a defined set, or be unique,
+			or only reference publicly available resources,
+			etc.) 
+     <li>
+       Define the policy for changes to existing entries, such as 
+      <ul>
+       <li>whether entries can be deleted or deprecated 
+       <li>whether entries can be changed after being published, and what kinds of changes are allowed 
+       <li>whether previously-deleted unique identifiers can be re-used, or are reserved indefinitely 
+      </ul>
+     <li> Define the method and criteria by which changes are proposed, approved, and incorporated.
+			(For example, a <a data-link-type="dfn" href="#registry" id="ref-for-registry④">registry</a> could define
+			that changes to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry①">registry entries</a> can be proposed using a particular web form or email address,
+			that they must be accompanied by certain background information,
+			or that they do or do not need to be approved by any member of a particular Working Group.) 
+     <li>
+       Identify the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="custodian">custodian</dfn> of the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑧">registry table</a>:
+			the entity to which requests for <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change">registry changes</a> must be sent,
+			and which is responsible for evaluating whether such requests
+			satisfy the criteria defined in the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition②">registry definition</a>. 
+      <p>The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian①">custodian</a> may be the initiating group, the <a data-link-type="dfn" href="#team" id="ref-for-team①②⓪">Team</a>, or a delegated entity.
+			The <a data-link-type="dfn" href="#custodian" id="ref-for-custodian②">custodian</a> for all <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table⑨">registry tables</a> in a single <a data-link-type="dfn" href="#registry" id="ref-for-registry⑤">registry</a> <em class="rfc2119">should</em> generally be the same entity.</p>
+      <p>If the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian③">custodian</a> of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⓪">registry table</a> ceases to exist or to operate as a custodian
+			(e.g., the relevant group is disbanded, or 
+			the custodian is unresponsive to repeated attempts to make contact),
+			and the <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group⑤">chartered</a> or <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group①">elected group</a> that owns the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition③">registry definition</a> is itself <a href="#GeneralTermination">closed</a> or 
+			unresponsive,
+			the <a data-link-type="dfn" href="#team" id="ref-for-team①②①">Team</a> <em class="rfc2119">should</em> propose replacing the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian④">custodian</a>,
+			which <em class="rfc2119">must</em> be confirmed
+			by an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③③">AC Review</a> as a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑦">W3C Decision</a>.</p>
+    </ul>
+    <h4 class="heading settled" data-level="6.5.2" id="reg-pub"><span class="secno">6.5.2. </span><span class="content"> Publishing Registries</span><a class="self-link" href="#reg-pub"></a></h4>
+    <p>A <a data-link-type="dfn" href="#chartered-group" id="ref-for-chartered-group⑥">chartered</a> or <a data-link-type="dfn" href="#elected-group" id="ref-for-elected-group②">elected group</a> can publish a <a data-link-type="dfn" href="#registry" id="ref-for-registry⑥">registry</a> as a stand-alone <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⓪">technical report</a> on the <a data-link-type="dfn" href="#registry-track" id="ref-for-registry-track">Registry Track</a>,
+	where it is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-report">registry report</dfn>. <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦③">Working Groups</a> have the additional option of
+	incorporating a <a data-link-type="dfn" href="#registry" id="ref-for-registry⑦">registry</a> as part of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦①">Recommendation</a>,
+	as an <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="embedded-registry"><span class="bs-old-id" id="registry-section"></span>embedded registry</dfn>.</p>
+    <p>The <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report①">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry①">embedded registry</a> <em class="rfc2119">must</em>:</p>
+    <ul>
+     <li> Clearly label the <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report②">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry②">embedded registry</a>,
+			its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①①">tables</a>,
+			and its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition④">registry definitions</a> as such,
+			including a link to <a href="#registries">§ 6.5 The Registry Track</a> in this Process. 
+     <li> Include the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑤">registry definition</a> for each of its <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①②">registry tables</a>. 
+     <li>
+       Provide the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data">registry data</a> by either: 
+      <ul>
+       <li> Including the entire contents of each <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①③">registry table</a>,
+					either inline in the report
+					(e.g. formatted as a table, or list, or other appropriate representation),
+					or in a machine-readable file published as part of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③①">technical report</a>,
+					or (preferably) both. 
+       <li> Linking to one or more standalone <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report">Registry Data Reports</a> containing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①④">registry tables</a> in human-readable form, machine-readable form,
+					or (preferably) both. 
+      </ul>
+     <li> Include, if the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑤">registry table</a> is provided in a machine-readable file,
+			a definition of the format of that file. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②②">Team</a> <em class="rfc2119">must</em> make available
+	a means for interested parties to be notified of any updates to a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑥">registry table</a>.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> Since the Process does not impose requirements
+	on changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑦">registry table</a> other than those imposed by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑥">registry definition</a>,
+	acceptance of proposed <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change①">registry changes</a> on behalf of the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian⑤">custodian</a> and
+	publication of an updated <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report③">registry report</a> that contains
+	only <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change②">registry changes</a> since the previous publication
+	can be automated
+	if satisfaction of those rules can be automatically verified.</p>
+    <p>Rules for publication and advancement on the <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-track">Registry Track</dfn> are identical to that of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①②">Recommendation Track</a> with the following exceptions:</p>
+    <ul>
+     <li> <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report④">Registry reports</a> are not subject to the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>,
+			and therefore none of their publications correspond,
+			to <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑦">First Public Working Draft</a>, <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①⓪">Working Draft</a>,
+			or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts③">Patent Review Draft</a> for the purposes of the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a>. 
+     <li> For the same reason,
+			there is no equivalent to <a data-link-type="dfn" href="#RescindedRec" id="ref-for-RescindedRec④">Rescinded Recommendation</a> nor to <a data-link-type="dfn" href="#rescinded-candidate-recommendation" id="ref-for-rescinded-candidate-recommendation①">Rescinded Candidate Recommendation</a> for <a data-link-type="dfn" href="#registry" id="ref-for-registry⑧">Registries</a>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①①">Working Draft</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="registry-draft"><span class="bs-old-id" id="draft-registry"></span>Registry Draft</dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsCR" id="ref-for-RecsCR②②">Candidate Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry">Candidate Registry</dfn>,
+			with <a data-link-type="dfn" href="#candidate-recommendation-snapshot" id="ref-for-candidate-recommendation-snapshot①⑨">Candidate Recommendation Snapshot</a> and <a data-link-type="dfn" href="#candidate-recommendation-draft" id="ref-for-candidate-recommendation-draft⑧">Candidate Recommendation Draft</a> corresponding to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-snapshot">Candidate Registry Snapshot</dfn> and <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="candidate-registry-draft">Candidate Registry Draft</dfn>. 
+     <li> The equivalent of <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦②">W3C Recommendation</a> is called <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="w3c-registry">W3C Registry</dfn>; <a data-link-type="dfn" href="#RecsObs" id="ref-for-RecsObs⑤">Obsolete Recommendation</a> and <a data-link-type="dfn" href="#RecsSup" id="ref-for-RecsSup①">Superseded Recommendation</a> correspond to <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="obsolete-registry">Obsolete Registry</dfn> and <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="superseded-registry">Superseded Registry</dfn>. 
+     <li> Changes that add new features (i.e., <a href="#correction-classes">class 4 changes</a>) are allowed
+			in all <a data-link-type="dfn" href="#w3c-registry" id="ref-for-w3c-registry①">W3C Registries</a>,
+			without needing them to explicitly indicate that this is allowed. 
+    </ul>
+    <h4 class="heading settled" data-level="6.5.3" id="reg-table-update"><span class="secno">6.5.3. </span><span class="content"> Updating Registry Tables</span><a class="self-link" href="#reg-table-update"></a></h4>
+    <p>Changes to the contents of a <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑧">registry table</a> that are in accordance with the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑦">registry definition</a>,
+	(i.e. <a href="#correction-classes">Class 5 changes</a>)
+	can be made by re-publishing the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③②">technical report</a> that contains the affected table,
+	without needing to satisfy any other requirements for the publication
+	(not even a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑦">group decision</a>, unless this is required by the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑧">registry definition</a>).
+	Such <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change③">registry changes</a> do not trigger new <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③④">Advisory Committee Reviews</a>,
+	nor Exclusion Opportunities,
+	and do not require verification via an <a data-link-type="dfn" href="#update-requests" id="ref-for-update-requests①①">update request</a>,
+	even for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③③">technical reports</a> at maturities where this would normally be expected.
+	Such publications can be made
+	even in the absence of a group chartered to maintain the registry
+	when the <a data-link-type="dfn" href="#custodian" id="ref-for-custodian⑥">custodian</a> is another entity.</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The custodian is only empowered to make <a data-link-type="dfn" href="#registry-change" id="ref-for-registry-change④">registry changes</a>.
+	If the group establishing the registry wishes
+	to empower the custodian to add commentary on individual entries,
+	this needs to be part of the registry table’s definition.
+	If other changes are desired,
+	they need to be requested of the group responsible for maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition⑨">registry definition</a>—​or in the absence of such a group, of the Team.</p>
+    <p>Changes to the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table①⑨">registry tables</a> made in accordance with <a data-link-type="dfn" href="#candidate-amendment" id="ref-for-candidate-amendment⑨">candidate</a> or <a data-link-type="dfn" href="#proposed-amendments" id="ref-for-proposed-amendments①②">proposed amendments</a> to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⓪">registry definition</a> which would not be allowed by the unamended <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①①">registry definition</a> <em class="rfc2119">must</em> be identified as such.</p>
+    <h4 class="heading settled" data-level="6.5.4" id="reg-data-reports"><span class="secno">6.5.4. </span><span class="content"> Registry Data Reports</span><a class="self-link" href="#reg-data-reports"></a></h4>
+    <p>When the <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data①">registry data</a> is published in a separate <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③④">technical report</a> from its <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①②">registry definition</a>,
+	that <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑤">report</a> is called a <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="registry-data-report">Registry Data Report</dfn>.
+	This <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑥">technical report</a>:</p>
+    <ul>
+     <li> <em class="rfc2119">Must</em> link to the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①③">registry definition</a> establishing the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②⓪">registry tables</a> that it contain. 
+     <li> <em class="rfc2119">May</em> contain non-normative introductory text, examples, and notes
+			about the <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②①">registry tables</a> and <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry②">entries</a> that it contains.
+			(Changes to these parts are deemed to be <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change⑨">editorial changes</a>). 
+    </ul>
+    <p><a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report①">Registry Data Reports</a> do not have maturity stages in and of themselves;
+	The maturity stage of the <a data-link-type="dfn" href="#registry" id="ref-for-registry⑨">registry</a> whose <a data-link-type="dfn" href="#registry-data" id="ref-for-registry-data②">data</a> they record
+	is that of the <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑦">technical report</a> holding the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①④">registry definition</a>.</p>
+    <p>Anytime a change is made to a <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑤">registry definition</a>,
+	the group maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑥">registry definition</a> <em class="rfc2119">must</em> update and republish
+	any document holding the corresponding <a data-link-type="dfn" href="#registry-table" id="ref-for-registry-table②②">registry tables</a> to make it consistent with these changes.</p>
+    <p>Given a recorded <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑧">group decision</a> to do so,
+	the group maintaining the <a data-link-type="dfn" href="#registry-definition" id="ref-for-registry-definition①⑦">registry definition</a> <em class="rfc2119">may</em> republish the <a data-link-type="dfn" href="#registry-data-report" id="ref-for-registry-data-report②">Registry Data Report</a> to incorporate <a data-link-type="dfn" href="#editorial-change" id="ref-for-editorial-change①⓪">editorial changes</a>.</p>
+    <h4 class="heading settled" data-level="6.5.5" id="reg-ref-specifications"><span class="secno">6.5.5. </span><span class="content"> Specifications that Reference Registries</span><a class="self-link" href="#reg-ref-specifications"></a></h4>
+    <p>Registries document values,
+	they do not define any architectural or interoperability requirements
+	related to those values.
+	All architectural and interoperability requirements
+	pertaining to <a data-link-type="dfn" href="#registry-entry" id="ref-for-registry-entry③">registry entries</a> <em class="rfc2119">must</em> be contained in the specifications that reference the registry,
+	and are therefore subject to the processes
+	(including approval and intellectual property provisions)
+	applicable to those referencing specifications.</p>
+    <p>If there are entries that must be implemented,
+	or any other such restrictions,
+	they <em class="rfc2119">must</em> be defined or documented
+	in the referencing specification
+	without dependency on the registry.</p>
+    <div class="example" id="example-87a6a8f6"><a class="self-link" href="#example-87a6a8f6"></a> For example, <span class="allow-2119">“All implementations must implement the <code>Basic-Method</code> as defined in the registry”</span> is not acceptable because
+		a change to the definition of the <code>Basic-Method</code> in the registry would then affect conformance.
+		Instead, the requirement has to be complete in the specification,
+		directly or by reference to another specification.
+		For example <span class="allow-2119">“All implementations must recognize the name <code>Basic-Method</code>,
+		and implement it as defined by section yy of IETF RFC xxxx”</span>.
+		(The Registry is nonetheless expected to contain <code>Basic-Method</code> as an entry.) </div>
+    <h4 class="heading settled" data-level="6.5.6" id="reg-pat"><span class="secno">6.5.6. </span><span class="content"> Registries and Patents</span><a class="self-link" href="#reg-pat"></a></h4>
+    <p>A <a data-link-type="dfn" href="#registry-report" id="ref-for-registry-report⑤">registry report</a> or <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry③">embedded registry</a> is not subject to the W3C Patent Policy,
+	and <em class="rfc2119">must not</em> define any requirements on implementations.
+	For the purposes of the Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a> (only),
+	any <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry④">embedded registry</a> in a <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①③">Recommendation track</a> document
+	is not a normative portion of that specification.</p>
+    <h3 class="heading settled" data-level="6.6" id="switching-tracks"><span class="secno">6.6. </span><span class="content"> Switching Tracks</span><a class="self-link" href="#switching-tracks"></a></h3>
+    <p>Given a <a data-link-type="dfn" href="#group-decision" id="ref-for-group-decision⑨">Group decision</a> to do so, <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦④">Working Groups</a> can republish a <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑧">technical report</a> on a different track than the one it is on,
+	under the following restrictions:</p>
+    <ul>
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report③⑨">technical report</a> that is or was
+			a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦③">W3C Recommendation</a>, <a data-link-type="dfn" href="#statement" id="ref-for-statement①③">W3C Statement</a>, or <a data-link-type="dfn" href="#patent-review-drafts" id="ref-for-patent-review-drafts④">Patent Review Draft</a> cannot switch tracks. 
+     <li> A <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④⓪">technical report</a> should not switch away from the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①④">Recommendation Track</a> without due consideration of the Patent Policy implications
+			and approval of W3C’s legal counsel
+			if the <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑤">Working Group</a> envisions a likelihood of returning to it later. 
+    </ul>
+    <p><a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④①">Technical reports</a> that switch tracks start at
+	their new track’s initial maturity stage,
+	while retaining any established identity (url, shortname, etc.).</p>
+    <p class="note" role="note"><span class="marker">Note:</span> The initial maturity stage of the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⑤">Recommendation track</a> is <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①②">Working Draft</a>. <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑧">First Public Working Draft</a> designates a specific type of <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①③">Working Draft</a> and is not a separate maturity stage.
+	A document which switches to the <a data-link-type="dfn" href="#w3c-recommendation-track" id="ref-for-w3c-recommendation-track①⑥">Recommendation track</a> is only published as a <a data-link-type="dfn" href="#fpwd" id="ref-for-fpwd⑨">First Public Working Draft</a> if it was never previously published as such;
+	otherwise, it is simply a <a data-link-type="dfn" href="#RecsWD" id="ref-for-RecsWD①④">Working Draft</a>.</p>
+    <h3 class="heading settled" data-level="6.7" id="further-reading"><span class="secno">6.7. </span><span class="content"> Further reading</span><a class="self-link" href="#further-reading"></a></h3>
+    <p>Refer to <a href="https://www.w3.org/guide/transitions/">"How to Organize a Recommendation Track Transition"</a> <a data-link-type="biblio" href="#biblio-transition" title="Organize a Technical Report Transition">[TRANSITION]</a> in the <a href="https://www.w3.org/guide/">Art of Consensus</a> <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a> for practical information about preparing for the reviews
+	and announcements of the various steps,
+	and <a href="https://www.w3.org/guide/standards-track/rec-tips">tips on getting to Recommendation faster</a> <a data-link-type="biblio" href="#biblio-rec-tips" title="Tips for Getting to Recommendation Faster">[REC-TIPS]</a>.
+	Please see also the <a href="https://www.w3.org/guide/standards-track/republishing">Requirements for modification of W3C Technical Reports</a> <a data-link-type="biblio" href="#biblio-republishing" title="In-place modification of W3C Technical Reports">[REPUBLISHING]</a>.</p>
+    <h2 class="heading settled" data-level="7" id="dissemination"><span class="secno">7. </span><span class="content"> <span id="chapterDissemination"></span> Dissemination Policies</span><a class="self-link" href="#dissemination"></a></h2>
+    <h3 class="heading settled" data-level="7.1" id="pub-com"><span class="secno">7.1. </span><span class="content"> Public Communication</span><a class="self-link" href="#pub-com"></a></h3>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②③">Team</a> is responsible for managing communication within W3C
+	and with the general public
+	(e.g., news services, press releases, managing the website and access privileges, and managing calendars).
+	Members <em class="rfc2119">should</em> solicit review by the Team
+	prior to issuing press releases about their work within W3C.</p>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②④">Team</a> makes every effort to ensure the persistence and availability of the following public information:</p>
+    <ul>
+     <li> <a href="#Reports">W3C technical reports</a> whose publication has been approved.
+			Per <a data-biblio-display="inline" data-link-type="biblio" href="https://www.w3.org/policies/"><cite>W3C IPR Policies</cite></a>,
+			W3C technical reports (and software) are available free of charge to the general public. 
+     <li> A <a href="https://www.w3.org/mission/">mission statement</a> <a data-link-type="biblio" href="#biblio-mission" title="The W3C Mission statement">[MISSION]</a> that explains the purpose and mission of W3C,
+			the key benefits for Members,
+			and the organizational structure of W3C. 
+     <li> Legal documents,
+			including <a href="https://www.w3.org/membership/agreement/">Membership Agreements</a> <a data-link-type="biblio" href="#biblio-member-agreement" title="W3C Membership Agreement">[MEMBER-AGREEMENT]</a> and documentation of any legal commitments W3C has with other entities. 
+     <li> The Process Document. 
+     <li> Public results of W3C activities and <a href="#GAEvents">Workshops</a>. 
+    </ul>
+    <p>To keep the Members abreast of W3C meetings, <a data-link-type="dfn" href="#EventsW" id="ref-for-EventsW③">Workshops</a>,
+	and review deadlines,
+	the Team provides them with a regular (e.g., weekly) news service
+	and maintains a <a href="https://www.w3.org/events/">calendar</a> <a data-link-type="biblio" href="#biblio-calendar" title="Calendar of all scheduled official W3C events">[CALENDAR]</a> of official W3C events.
+	Members are encouraged to send schedule and event information to the Team for inclusion on this calendar.</p>
+    <h3 class="heading settled" data-level="7.2" id="confidentiality-levels"><span class="secno">7.2. </span><span class="content"> Confidentiality Levels</span><a class="self-link" href="#confidentiality-levels"></a></h3>
+    <p>There are three principal levels of access to W3C information
+	(on the W3C website, in W3C meetings, etc.):
+	public,
+	Member-only,
+	and Team-only.</p>
+    <p>While much information made available by W3C is public,
+	“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Member-Only" id="Member-only">Member-only</dfn>” information
+	is available to authorized parties only,
+	including representatives of Member organizations, <a href="#invited-expert-wg">Invited Experts</a> (as described in <a href="https://www.w3.org/invited-experts/#memaccess">https://www.w3.org/invited-experts/#memaccess</a>),
+	the Advisory Board,
+	the TAG,
+	and the Team.
+	For example,
+	the <a href="#WGCharter">charter</a> of some Working Groups <em class="rfc2119">may</em> specify a <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only④">Member-only</a> confidentiality level for group proceedings.</p>
+    <p>“<dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="Team-Only" id="Team-only">Team-only</dfn>” information
+	is available to the Team and other authorized parties.</p>
+    <p>Those authorized to access <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑤">Member-only</a> and <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only①">Team-only</a> information:</p>
+    <ul>
+     <li> <em class="rfc2119">must</em> treat the information as confidential within W3C, 
+     <li> <em class="rfc2119">must</em> use reasonable efforts to preserve that confidentiality, and 
+     <li> <em class="rfc2119">must not</em> release this information to the general public or press,
+			nor beyond the designated level of access. 
+    </ul>
+    <p>The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑤">Team</a> <em class="rfc2119">must</em> provide mechanisms
+	to protect the confidentiality of <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑥">Member-only</a> information
+	and ensure that authorized parties have proper access to this information.
+	Documents <em class="rfc2119">should</em> clearly indicate
+	whether they require <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑦">Member-only</a> confidentiality.
+	Individuals uncertain of the confidentiality level of a piece of information <em class="rfc2119">should</em> contact the Team.</p>
+    <p><a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⓪">Advisory Committee representatives</a> <em class="rfc2119">may</em> authorize <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑧">Member-only</a> access to <a href="#member-rep">Member representatives</a> and other individuals employed by the Member
+	who are considered appropriate recipients.
+	For instance,
+	it is the responsibility of the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③①">Advisory Committee representative</a> and other employees
+	and official representatives of the organization
+	to ensure that Member-only news announcements
+	are distributed for internal use only within their organization.
+	Information about Member mailing lists is available
+	in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> <a data-link-type="biblio" href="#biblio-intro" title="Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)">[INTRO]</a>.</p>
+    <h3 class="heading settled" data-level="7.3" id="confidentiality-change"><span class="secno">7.3. </span><span class="content"> Changing Confidentiality Level</span><a class="self-link" href="#confidentiality-change"></a></h3>
+    <p>As a benefit of membership,
+	W3C provides some <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only②">Team-only</a> and <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only⑨">Member-only</a> channels
+	for certain types of communication.
+	For example, <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③②">Advisory Committee representatives</a> can send <a href="#ACReview">reviews</a> to a <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only③">Team-only</a> channel.
+	However, for W3C processes with a significant public component,
+	such as the technical report development process,
+	it is also important for information that affects decision-making to be publicly available.
+	The Team <em class="rfc2119">may</em> need to communicate <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only④">Team-only</a> information to a Working Group or the public.
+	Similarly, a Working Group whose proceedings are <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①⓪">Member-only</a> <em class="rfc2119">must</em> make public
+	information pertinent to the technical report development process.</p>
+    <p>This document clearly indicates which information <em class="rfc2119">must</em> be available to Members or the public,
+	even though that information was initially communicated on <a data-link-type="dfn" href="#Team-only" id="ref-for-Team-only⑤">Team-only</a> or <a data-link-type="dfn" href="#Member-only" id="ref-for-Member-only①①">Member-only</a> channels.
+	Only the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑥">Team</a> and parties authorized by the Team
+	may change the level of confidentiality of this information.
+	When doing so:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑦">Team</a> <em class="rfc2119">must</em> use a version of the information
+			that was expressly provided by the author for the new confidentiality level.
+			In Calls for Review and other similar messages,
+			the Team <em class="rfc2119">should</em> remind recipients to provide such alternatives. 
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①②⑧">Team</a> <em class="rfc2119">must not</em> attribute the version
+			for the new confidentiality level to the author without the author’s consent. 
+     <li> If the author has not conveyed to the <a data-link-type="dfn" href="#team" id="ref-for-team①②⑨">Team</a> a version
+			that is suitable for another confidentiality level,
+			the Team <em class="rfc2119">may</em> make available a version that reasonably communicates what is required,
+			while respecting the original level of confidentiality,
+			and without attribution to the original author. 
+    </ol>
+    <h2 class="heading settled" data-level="8" id="Liaisons"><span class="secno">8. </span><span class="content"> Liaisons</span><a class="self-link" href="#Liaisons"></a></h2>
+    <p>W3C uses the term <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="liaison">liaison</dfn> 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 <a data-link-type="dfn" href="#team" id="ref-for-team①③⓪">Team</a> due to requirements for public communication;
+	patent,
+	copyright,
+	and other IPR policies;
+	confidentiality agreements;
+	and mutual membership agreements.</p>
+    <p>W3C <em class="rfc2119">may</em> negotiate <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①">technical agreements</a> with another organization.
+	For purposes of the W3C Process,
+	a <dfn class="dfn-paneled" data-dfn-type="dfn" data-local-lt="agreement" data-noexport id="technical-agreement">technical agreement</dfn> is a formal contract,
+	or a Memorandum of Understanding (<abbr>MoU</abbr>),
+	or a similar document,
+	between W3C and another party or parties,
+	that relates to the technical activity of the Consortium
+	(e.g., its publications, groups, or liaisons).
+	It specifies rights and obligations of each party toward the others.
+	These rights and obligations <em class="rfc2119">may</em> include joint deliverables,
+	an agreed share of technical responsibilities with due coordination,
+	and/or considerations for confidentiality and specific IPR.</p>
+    <p>Non-technical agreements, including
+	those between W3C and its <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑥">Members</a> for the purposes of membership,
+	between W3C and its Partners for the purposes of partnership <a data-link-type="biblio" href="#biblio-bylaws" title="Amended and Restated Bylaws of World Wide Web Consortium, Inc.">[BYLAWS]</a>,
+	and other agreements related to the operation of the Consortium
+	or to the ordinary provision of services,
+	are not subject to these Process provisions.</p>
+    <p>When considering a <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement②">technical agreement</a> (i.e., before the decision whether to sign is made),
+	the Team <em class="rfc2119">should</em> provide
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④⓪">Advisory Committee</a> with a draft of the proposed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement③">agreement</a>,
+	along with an explanation of how W3C would benefit from signing this <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement④">agreement</a>,
+	for their review and discussion.
+	After addressing any comments,
+	and subject to any management or governance procedures that apply
+	(e.g., formal review of proposed contracts by legal counsel or by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑦">Board</a>),
+	if the <a data-link-type="dfn" href="#team-decision" id="ref-for-team-decision①②">Team decides</a> to proceed with signing the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑤">agreement</a>,
+	the Team <em class="rfc2119">must</em> announce the intent to sign,
+	and provide the final text of the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑥">agreement</a>,
+	with an explanation of signing rationale, to
+	the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④①">Advisory Committee</a>. <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③③">Advisory Committee representatives</a> <em class="rfc2119">may</em> initiate an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①⓪">Advisory Committee Appeal</a> of the decision to sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑦">agreement</a>.
+	If the proposal is rejected on <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①①">appeal</a>,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③①">Team</a> <em class="rfc2119">must not</em> sign the <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑧">agreement</a> on behalf of W3C
+	unless directed to do so by the <a data-link-type="dfn" href="#bod" id="ref-for-bod⑧">Board</a>.
+	A signed <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement⑨">agreement</a> <em class="rfc2119">should</em> be made public.</p>
+    <p>Information about <a href="https://www.w3.org/liaisons/">W3C liaisons with other organizations</a> <a data-link-type="biblio" href="#biblio-liaison" title="W3C liaisons with other organizations">[LIAISON]</a> and the guidelines W3C follows when creating a liaison is available on the Web.</p>
+    <h2 class="heading settled" data-level="9" id="Submission"><span class="secno">9. </span><span class="bs-old-id" id="SubmissionNo"></span><span class="bs-old-id" id="SubmissionYes"></span><span class="bs-old-id" id="TeamSubmissionRights"></span><span class="bs-old-id" id="SubmissionScope"></span><span class="bs-old-id" id="SubmissionRights"></span><span class="content"> Member Submissions</span><a class="self-link" href="#Submission"></a></h2>
+    <p>A <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="MemberSubmission">Member Submission</dfn> is a document or set of documents
+	developed outside of W3C,
+	and submitted to W3C
+	by one or more <a data-link-type="dfn" href="#w3c-member" id="ref-for-w3c-member⑦">Members</a> (the <dfn class="dfn-paneled" data-dfn-type="dfn" data-export data-lt="submitter" id="submitter">Submitter(s)</dfn>)
+	to propose technology or other ideas.
+	After review,
+	the <a data-link-type="dfn" href="#team" id="ref-for-team①③②">Team</a> <em class="rfc2119">may</em> make the material available at the W3C website.</p>
+    <p>Making a <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission">Member Submission</a> available at the W3C website
+	does not indicate endorsement, acceptance, or adoption by W3C,
+	its Team, or its Members.
+	The <a data-link-type="dfn" href="#acknowledged" id="ref-for-acknowledged">acknowledgment</a> of a Submission request
+	does not imply that any action will be taken by W3C.
+	It merely records publicly
+	that the Submission has been made by the Submitter(s).
+	A Member Submission made available by W3C
+	is not a W3C <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④②">technical report</a> and <em class="rfc2119">must not</em> be referred to as
+	an output or “work in progress” of W3C.</p>
+    <p>The <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission①">Member Submission</a> process consists of the following steps:</p>
+    <dl>
+     <dt>Submission 
+     <dd> One of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter">Submitters</a>,
+			copying the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③④">Advisory Committee representatives</a> of the other <a data-link-type="dfn" href="#submitter" id="ref-for-submitter①">Submitters</a> (if any),
+			sends a request to the Team to acknowledge the Submission request.
+			The <a data-link-type="dfn" href="#team" id="ref-for-team①③③">Team</a> and <a data-link-type="dfn" href="#submitter" id="ref-for-submitter②">Submitter(s)</a> communicate to ensure that the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission②">Member Submission</a> is complete. 
+     <dt>Review 
+     <dd>
+       The <a data-link-type="dfn" href="#team" id="ref-for-team①③④">Team</a> reviews the Submission
+			to evaluate its scope, quality, and compliance with the Submission requirements,
+			including licensing requirements: 
+      <ul>
+       <li> The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter③">Submitter(s)</a> and any other authors of the submitted material <em class="rfc2119">must</em> agree
+					to license the Submission under the <a href="https://www.w3.org/copyright/document-license-2023/">W3C Document License</a> <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a>. 
+       <li> The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments
+					in <a href="https://www.w3.org/policies/patent-policy/#sec-submissions">The W3C Patent Policy § sec-submissions</a>. 
+      </ul>
+      <p>Detailed procedures and requirements are defined by the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑤">Team</a> and documented in the “<a href="https://www.w3.org/submissions/guide/">Member submissions guidebook</a>” <a data-link-type="biblio" href="#biblio-member-sub" title="Member submissions guidebook">[MEMBER-SUB]</a>.</p>
+     <dt>Decision 
+     <dd>
+       After review, the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑥">Team</a> <em class="rfc2119">must</em> either <a data-link-type="dfn" href="#acknowledged" id="ref-for-acknowledged①">acknowledge</a> or <a data-link-type="dfn" href="#rejected" id="ref-for-rejected">reject</a> the Submission request. 
+      <ul>
+       <li> If <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="acknowledged">acknowledged</dfn>,
+					the Team <em class="rfc2119">must</em> make the <a data-link-type="dfn" href="#MemberSubmission" id="ref-for-MemberSubmission③">Member Submission</a> available
+					at the public W3C website
+					alongside other <a href="https://www.w3.org/submissions/">acknowledged Member Submissions</a> <a data-link-type="biblio" href="#biblio-submission-list" title="The list of acknowledged Member Submissions">[SUBMISSION-LIST]</a>. 
+       <li> If <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rejected">rejected</dfn>,
+					the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑦">Team</a> <em class="rfc2119">must</em> inform the <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⑤">Advisory Committee representative(s)</a> of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter④">Submitter(s)</a>,
+					and <em class="rfc2119">must</em> provide rationale if requested by the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑤">Submitter(s)</a>.
+					The <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑥">Submitter(s)</a> <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals③">Submission Appeal</a>. 
+      </ul>
+    </dl>
+    <p>The <a data-link-type="dfn" href="#advisory-committee-representative" id="ref-for-advisory-committee-representative③⑥">Advisory Committee representative(s)</a> of the <a data-link-type="dfn" href="#submitter" id="ref-for-submitter⑦">Submitter(s)</a> <em class="rfc2119">may</em> initiate a <a data-link-type="dfn" href="#submission-appeals" id="ref-for-submission-appeals④">Submission Appeal</a>.
+	The procedure for handling <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="submission-appeals">Submission Appeals</dfn> is the same as for <a data-link-type="dfn" href="#FormalObjection" id="ref-for-FormalObjection④④">Formal Objections</a>,
+	except that an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①②">AC Appeal</a> is not possible
+	and both the Formal Objection and the <a data-link-type="dfn" href="#council-report" id="ref-for-council-report⑥">Council Report</a> are confidential to the <a data-link-type="dfn" href="#team" id="ref-for-team①③⑧">Team</a>, <a data-link-type="dfn" href="#technical-architecture-group" id="ref-for-technical-architecture-group③⑨">TAG</a>, and <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③③">AB</a>.</p>
+    <h2 class="heading settled" data-level="10" id="GAProcess"><span class="secno">10. </span><span class="content"> Process Evolution</span><a class="self-link" href="#GAProcess"></a></h2>
+    <p>Revision of the W3C Process and related documents (see below) undergoes similar <a data-link-type="dfn" href="#def-Consensus" id="ref-for-def-Consensus②②">consensus</a>-building processes as for <a data-link-type="dfn" href="#technical-report" id="ref-for-technical-report④③">technical reports</a>,
+	with the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③④">Advisory Board</a> acting as the sponsoring <a data-link-type="dfn" href="#GroupsWG" id="ref-for-GroupsWG⑦⑥">Working Group</a>.
+	The documents may be developed by the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑤">AB</a> or by another group to whom the <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑥">AB</a> has delegated development.
+	Review includes
+	soliciting input from the W3C community,
+	and in particular the Team.</p>
+    <p>The documents covered by this section are:</p>
+    <ul>
+     <li data-md>
+      <p>the W3C Process (this document)</p>
+     <li data-md>
+      <p>the W3C Patent Policy <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">[PATENT-POLICY]</a></p>
+     <li data-md>
+      <p>the W3C Code of Conduct <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">[COC]</a></p>
+     <li data-md>
+      <p>The W3C Document License <a data-link-type="biblio" href="#biblio-doc-license" title="W3C Document License">[DOC-LICENSE]</a></p>
+    </ul>
+    <p>The <a data-link-type="dfn" href="#advisory-board" id="ref-for-advisory-board③⑦">Advisory Board</a> initiates review as follows:</p>
+    <ol>
+     <li> The <a data-link-type="dfn" href="#team" id="ref-for-team①③⑨">Team</a> sends a Call for Review to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④②">Advisory Committee</a> and other W3C groups. 
+     <li> After comments have been <a data-link-type="dfn" href="#formally-addressed" id="ref-for-formally-addressed⑧">formally addressed</a> and the document possibly modified,
+			the Team seeks endorsement from the Members by initiating an <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑤">Advisory Committee review</a>.
+			The review period <em class="rfc2119">must</em> last at least <span class="time-interval">28 days</span>. 
+     <li> <a href="#ACReviewAfter">After the Advisory Committee review</a>,
+			following a <a data-link-type="dfn" href="#def-w3c-decision" id="ref-for-def-w3c-decision①⑧">W3C decision</a> to adopt the document(s),
+			the Team does so
+			and sends an announcement to the <a data-link-type="dfn" href="#advisory-committee" id="ref-for-advisory-committee④③">Advisory Committee</a>.
+			Advisory Committee representatives <em class="rfc2119">may</em> initiate
+			an <a data-link-type="dfn" href="#advisory-committee-appeal" id="ref-for-advisory-committee-appeal①③">Advisory Committee Appeal</a> to W3C. 
+    </ol>
+    <p class="note" role="note"><span class="marker">Note:</span> As of June 2020,
+	the <a data-link-type="biblio" href="#biblio-patent-policy" title="The W3C Patent Policy">Patent Policy</a> is developed in the <a href="https://www.w3.org/2004/pp/psig/">Patents and Standards Interest Group</a>,
+	the <a data-link-type="biblio" href="#biblio-coc" title="W3C Code of Conduct">Code of Conduct</a> in the <a href="https://www.w3.org/community/pwe/">Positive Work Environment Community Group</a>,
+	and the Process in the <a href="https://www.w3.org/community/w3process/">W3C Process Community Group</a>.</p>
+    <h2 class="non-normative nonum heading settled" id="old-terms"><span class="content"> Appendix A: Retired Terminology</span><a class="self-link" href="#old-terms"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>Previous versions of this process defined and used various concepts and document statuses
+	that have since been retired or renamed.
+	For ease of reference,
+	this appendix lists the more notable ones,
+	and it links to the the definition or relevant section
+	in the most recent version of the Process that used them,
+	and gives the more recent equivalent term when there is one.</p>
+    <dl>
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="rec-amended">Amended Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2020/Process-20200915/#rec-amended">in section 6.2.1 of the 2020 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="edited-recommendation">Edited Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2019/Process-20190301/#maturity-levels">in section 6.1.2 of the 2019 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="last-call">Last Call</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2005/10/Process-20051014/tr.html#last-call">in section 7.4.2 of the 2005 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="maturity-levels">Maturity level</dfn> (renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#maturity-levels">in section 6.3.1 of the 2021 Process</a>,
+			now called <a href="#maturity-stages">maturity stage</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="fdn-member-consortium">Member Consortium</dfn>, plural: Member Consortia
+			(renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#fdn-member-consortium">in section 2.1.2.1 of the 2021 Process</a>,
+			now called <a data-link-type="dfn" href="#member-association" id="ref-for-member-association⑥">Member Association</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="mou">Memorandum of Understanding</dfn>, plural: Memoranda of Understanding, abbreviation: MoU
+			(renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2021/Process-20211102/#mou">in section 9 of the 2021 Process</a>,
+			now called <a data-link-type="dfn" href="#technical-agreement" id="ref-for-technical-agreement①⓪">technical agreement</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="other-charter">Other Charter</dfn> (renamed term) 
+     <dd> Last used <a href="https://www.w3.org/2020/Process-20200915/#other-charter">in section 5.2.6 of the 2020 Process</a>,
+			now called <a data-link-type="dfn" href="#exclusion-draft-charter" id="ref-for-exclusion-draft-charter">Exclusion Draft Charter</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="RecsPR">Proposed Recommendation</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/policies/process/20231103/#RecsPR">in section 6.3.1 of the 2023 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="TeamSubmission">Team Submissions</dfn> (retired term) 
+     <dd> Last defined <a href="https://www.w3.org/2019/Process-20190301/#TeamSubmission">in section 2.2.1 of the 2019 Process</a>. 
+     <dt> <dfn class="dfn-paneled" data-dfn-type="dfn" data-noexport id="def-W3CChair">W3C Chair</dfn> (renamed term) 
+     <dd> Last defined <a href="https://www.w3.org/2014/Process-20140801/#def-W3CChair">in section 2.2 of the 2014 Process</a>,
+			now called <a data-link-type="dfn" href="#ceo" id="ref-for-ceo⑨">CEO</a>. 
+    </dl>
+    <h2 class="non-normative nonum heading settled" id="acks"><span class="content"> Appendix B: Acknowledgments</span><a class="self-link" href="#acks"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <p>The editors are grateful to the following people,
+	who as interested individuals and/or with the affiliation(s) listed,
+	have contributed to this proposal for a revised Process:
+	Adam Basha,
+	Anna Weinberg (Apple)
+	Charles McCathie Nevile,
+	Chris Lilley (W3C),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	Coralie Mercier (W3C),
+	David W. Singer (Apple),
+	Denis Ah-Kang (W3C),
+	Dominique Hazael-Massieux (W3C),
+	Ian Jacobs (W3C),
+	Jeffrey Yasskin (Google),
+	Jill Schmidt (Apple),
+	Marcos Cáceres (Apple),
+	Mark Nottingham,
+	Martin Thomson (Mozilla),
+	Michael Champion,
+	Michael Sirtori (Intel),
+	Mike Smith (W3C),
+	Nick Doty (Center for Democracy and Technology),
+	Nigel Megitt (BBC),
+	Philippe Le Hégaret (W3C),
+	Sam Sneddon (Apple),
+	Shawn Lawton Henry (W3C),
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Theresa O’Connor (Apple),
+	Vivien Lacourba (W3C).</p>
+    <p>The editors are sorry for forgetting any names,
+	and grateful to those who have listened patiently to conversations about this document
+	without feeling a need to add more.</p>
+    <p>The following individuals contributed to the development of earlier versions of the Process:
+	Alex Russell (Google),
+	Andreas Tai (Institut fuer Rundfunktechnik),
+	Andrew Betts (Fastly),
+	Ann Bassetti (The Boeing Company),
+	Anne van Kesteren,
+	Art Barstow (Nokia, unaffiliated),
+	Bede McCall (MITRE),
+	Ben Wilson,
+	Brad Hill (Facebook),
+	Brian Kardell (JQuery, Igalia),
+	Carine Bournez (W3C),
+	Carl Cargill (Netscape, Sun Microsystems, Adobe),
+	Charles McCathie Nevile (ConsenSys),
+	Chris Lilley (W3C),
+	Chris Needham (BBC),
+	Chris Wilson (Google),
+	Claus von Riegen (SAP AG),
+	Coralie Mercier (W3C),
+	Cullen Jennings (Cisco),
+	Dan Appelquist (Telefonica, Samsung),
+	Dan Connolly (W3C),
+	Daniel Dardailler (W3C),
+	Daniel Glazman (Disruptive Innovations),
+	David Baron (Mozilla),
+	David Fallside (IBM),
+	David W. Singer (Apple),
+	David Singer (IBM),
+	Delfí Ramírez,
+	Dominique Hazaël-Massieux (W3C),
+	Don Brutzman (Web3D),
+	Don Deutsch (Oracle),
+	Eduardo Gutentag (Sun Microsystems),
+	Elika J. Etemad <abbr title="also known as">aka</abbr> fantasai,
+	Florian Rivoal,
+	Fuqiao Xue (W3C),
+	Geoffrey Creighton (Microsoft),
+	Giri Mandyam (Qualcomm),
+	Gregg Kellogg,
+	Hadley Beeman,
+	Håkon Wium Lie (Opera Software),
+	Helene Workman (Apple),
+	Henri Sivonen (Mozilla),
+	Ian Hickson (Google),
+	Ian Jacobs (W3C),
+	Ivan Herman (W3C),
+	J Alan Bird (W3C),
+	Jay Kishigami 岸上順一 (NTT),
+	Jean-Charles Verdié (MStar),
+	Jean-François Abramatic (IBM, ILOG, W3C),
+	Jeff Jaffe (W3C),
+	Jeffrey Yasskin (Google),
+	Jim Bell (HP),
+	Jim Miller (W3C),
+	Joe Hall (CDT),
+	John Klensin (MCI),
+	Josh Soref (BlackBerry, unaffiliated),
+	Judy Brewer (W3C),
+	Judy Zhu 朱红儒 (Alibaba),
+	Kari Laihonen (Ericsson),
+	Karl Dubost (Mozilla),
+	Ken Laskey (MITRE),
+	Kevin Fleming (Bloomberg),
+	Klaus Birkenbihl (Fraunhofer Gesellschaft),
+	Larry Masinter (Adobe Systems),
+	Lauren Wood (unaffiliated),
+	Léonie Watson (The Paciello Group),
+	Liam Quin (W3C),
+	Marcos Cáceres (Mozilla),
+	Maria Courtemanche (IBM),
+	Mark Crawford (SAP),
+	Mark Nottingham,
+	Michael Champion (Microsoft),
+	Michael Geldblum (Oracle),
+	Mike West (Google),
+	Mitch Stoltz (EFF),
+	Natasha Rooney (GSMA),
+	Nigel Megitt (BBC),
+	Olle Olsson (SICS),
+	Ora Lassila (Nokia),
+	Paul Cotton (Microsoft),
+	Paul Grosso (Arbortext),
+	Peter Linss,
+	Peter Patel-Schneider,
+	Philippe Le Hégaret (W3C),
+	Qiuling Pan (Huawei),
+	Ralph Swick (W3C),
+	Renato Iannella (IPR Systems),
+	Rigo Wenning (W3C),
+	Rob Sanderson (J Paul Getty Trust),
+	Robin Berjon (W3C),
+	Sally Khudairi (W3C),
+	Sam Ruby (IBM),
+	Sam Sneddon,
+	Samuel Weiler (W3C),
+	Sandro Hawke (W3C),
+	Sangwhan Moon (Odd Concepts),
+	Scott Peterson (Google),
+	Shawn Lawton Henry,
+	Steve Holbrook (IBM),
+	Steve Zilles (Adobe Systems)
+	Steven Pemberton (CWI),
+	TV Raman (Google),
+	Tantek Çelik (Mozilla),
+	Ted Thibodeau Jr (OpenLink Software),
+	Terence Eden (Her Majesty’s Government),
+	Thomas Reardon (Microsoft),
+	Tim Berners-Lee (W3C),
+	Tim Krauskopf (Spyglass),
+	Travis Leithead (Microsoft),
+	Virginia Fournier (Apple),
+	Virginie Galindo (Gemalto),
+	Wayne Carr (Intel),
+	Wendy Fong (Hewlett-Packard),
+	Wendy Seltzer (W3C),
+	Yves Lafon (W3C).</p>
+    <h2 class="non-normative nonum heading settled" id="changes"><span class="content"> Appendix C: Changes</span><a class="self-link" href="#changes"></a></h2>
+    <p><em>This section is non-normative.</em></p>
+    <h3 class="no-num heading settled" id="changes-2025"><span class="content"> Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></span><a class="self-link" href="#changes-2025"></a></h3>
+    <p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
+	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2Fsnapshots%2F2025-08-18">diff from Process 2023 to this latest version</a>,
+	as well as
+	a <a href="https://github.com/w3c/process/compare/p2023_1...p2025">detailed log of all changes since then</a> are available. </p>
+    <p>In addition to a number of editorial adjustments and minor tweaks, the following is a summary of the main differences:</p>
+    <dl>
+     <dt id="changes-2025-tr"><a class="self-link" href="#changes-2025-tr"></a>Changes to technical reports and their publication 
+     <dd>
+      <ul>
+       <li> <strong> Retire the Proposed Recommendation phase of the Recommendation track. </strong> It was only used as a short-lived transition
+					during which various verifications and votes about CR were done.
+					These can be done on a CR
+					without having to republish it as a separate thing.
+					This simplifies the Process without changing the actual quality or consensus expectations.
+					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>) 
+       <li id="streamlined-update"><a class="self-link" href="#streamlined-update"></a> Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
+					This was meant to enable REC track publication with fewer/faster approval steps
+					when some stricter than usual criteria were fulfilled.
+					However, regular REC track publication have improved enough
+					that this became unnecessary,
+					and nobody was using it.
+					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>) 
+       <li> Add a requirement to make progress on external issues for update requests
+					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>) 
+       <li> Drop the requirement to publish every 6 months if nothing has changed.
+					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>) 
+       <li> Enable Team to replace defunct registry custodians when no-one else can.
+					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>) 
+       <li> Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
+					in addition to Working Groups.
+					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>) 
+       <li> Rename “registry sections” to <a data-link-type="dfn" href="#embedded-registry" id="ref-for-embedded-registry⑤">embedded registries</a> to avoid confusion over whether they can be split across multiple sections of a <a data-link-type="dfn" href="#RecsW3C" id="ref-for-RecsW3C⑦④">Recommendation</a>.
+					(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>) 
+       <li> Rename "Draft Note" into "Note Draft",
+					and "Draft Registry" into "Registry Draft"
+					to be consistent with other statuses that uses the word "Draft",
+					and to make that word stand out more.
+					(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>) 
+       <li> Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
+					and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>). 
+       <li> Consolidate and harmonize into <a href="#no-group-maintenance">one section</a> the various parts of the Process
+					that described whether and how the Team can maintain technical reports
+					that no longer have a Group chartered to maintain them.
+					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>) 
+      </ul>
+     <dt id="changes-2025-charter"><a class="self-link" href="#changes-2025-charter"></a>Changes to chartering 
+     <dd>
+      <ul>
+       <li> <strong> Introduce a formal <a data-link-type="dfn" href="#charter-refinement" id="ref-for-charter-refinement①②">Charter Refinement</a> phase prior to the <a data-link-type="dfn" href="#advisory-committee-review" id="ref-for-advisory-committee-review③⑥">AC Review</a>. </strong> (See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>) 
+       <li> Be more specific about which types of changes to a charter must go through AC Review.
+					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>) 
+       <li> Require Chairs to be listed in Charters.
+					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>) 
+       <li> Reorganize and rephrase <a href="#CharterReview">§ 4.4 Charter Review and Approval</a> for readability and ease of understanding.
+					This change, while moderate in size, is purely editorial.
+					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>) 
+      </ul>
+     <dt id="changes-2025-decisions"><a class="self-link" href="#changes-2025-decisions"></a>Changes to formal decision making and escalation 
+     <dd>
+      <ul>
+       <li> Adjust the rules guiding initiation of Councils,
+					to make the deadline strict,
+					and to provide a fallback mechanism if they are not met.
+					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>) 
+       <li> Make the Council’s short-circuit a little more flexible.
+					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>) 
+       <li> Exclude TAG/AB Members from voting on TAG/AB proposals in Councils.
+					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>) 
+       <li> Limit the involvement of Tim Berners-Lee to the TAG proper,
+					not including the Council.
+					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>) 
+       <li> Council dismissal vote counts must be reported.
+					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>) 
+       <li> Require documentation of how Formal Objections get resolved.
+					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>) 
+       <li> Put constraints on the timing of making Formal Objections public.
+					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>) 
+       <li> Fine-tune the rules about
+					how changes can be incorporated into a proposal
+					following an AC Review.
+					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>) 
+       <li> Adjust AC appeal vote threshold based on participation,
+					aligning with the thresholds and super majority requirements
+					for "Requisite Member Vote" from the W3C Bylaws.
+					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>) 
+       <li> Let the originator of a proposal decide whether to try again
+					after addressing feedback
+					following an AC Appeal.
+					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>) 
+       <li> Simplify provisions regarding substitute representatives and proxies.
+					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>) 
+      </ul>
+     <dt id="changes-other"><a class="self-link" href="#changes-other"></a>Other changes 
+     <dd>
+      <ul>
+       <li> Reuse the bylaws’ notion of Good Standing,
+					and restrict TAG and AB elections
+					as well as AC Votes where a decision is made based on counting ballots
+					to Members in Good Standing.
+					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a> and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>) 
+       <li> The section on Member Submissions was significantly shortened and simplified,
+					reducing the complexity under formal Process authority,
+					and shifting much of the material to /Guide,
+					under Team authority.
+					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a> and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>) 
+       <li> Clarify how the outcome of certain ballots are determined.
+					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>) 
+       <li> Stop citing the superseded TAG charter.
+					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>) 
+       <li> Clarify amount of leeway around incomplete nominations to TAG or AB elections.
+					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>) 
+       <li> Shift most of the non-normative discussion about Workshops to <a data-link-type="biblio" href="#biblio-guide" title="The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators">[GUIDE]</a>,
+					and reorganize the remaining normative requirements.
+					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>) 
+       <li> The URL of this document was changed
+					from /Consortium/Process/ to /policies/process/
+					for better integration in the W3C website architecture. 
+      </ul>
+      <h3 class="no-num heading settled" id="changes-previous"><span class="bs-old-id" id="changes-2017"></span><span class="bs-old-id" id="changes-2018"></span><span class="bs-old-id" id="changes-2019"></span><span class="bs-old-id" id="changes-2020"></span><span class="bs-old-id" id="changes-2021"></span><span class="bs-old-id" id="changes-2023"></span><span class="bs-old-id" id="changes-2023-1"></span><span class="content"> Changes since earlier versions</span><a class="self-link" href="#changes-previous"></a></h3>
+      <p>Changes since earlier versions of the Process are detailed
+	in the <a href="https://www.w3.org/policies/process/20231103/#changes">changes section of the previous version</a> of the Process.</p>
+    </dl>
+   </main>
+   <script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script>
+  </main>
+  <h2 class="no-num no-ref heading settled" id="index"><span class="content">Index</span><a class="self-link" href="#index"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="index-defined-here"><span class="content">Terms defined by this specification</span><a class="self-link" href="#index-defined-here"></a></h3>
+  <ul class="index">
+   <li><a href="#advisory-board">AB</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">AC</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">AC Appeal</a><span>, in § 5.9</span>
+   <li><a href="#acknowledged">acknowledged</a><span>, in § 9</span>
+   <li><a href="#advisory-committee-representative">AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">AC Review</a><span>, in § 5.7</span>
+   <li><a href="#adequate-implementation">adequate implementation experience</a><span>, in § 6.3.2</span>
+   <li><a href="#adopted-draft">Adopted Draft</a><span>, in § 4.3</span>
+   <li><a href="#advisory-board">Advisory Board</a><span>, in § 3.3.1.1</span>
+   <li><a href="#advisory-committee">Advisory Committee</a><span>, in § 3.2.1</span>
+   <li><a href="#advisory-committee-appeal">Advisory Committee Appeal</a><span>, in § 5.9</span>
+   <li><a href="#advisory-committee-representative">Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#advisory-committee-review">Advisory Committee review</a><span>, in § 5.7</span>
+   <li><a href="#affirm">affirm</a><span>, in § 5.6.2.7</span>
+   <li><a href="#technical-agreement">agreement</a><span>, in § 8</span>
+   <li><a href="#allow-new-features">allow new features</a><span>, in § 6.3.1</span>
+   <li><a href="#alternate-ac-representative">alt AC rep</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate AC representative</a><span>, in § 3.2.2</span>
+   <li><a href="#alternate-ac-representative">alternate Advisory Committee representative</a><span>, in § 3.2.2</span>
+   <li><a href="#rec-amended">Amended Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#advisory-committee-appeal">Appeal</a><span>, in § 5.9</span>
+   <li><a href="#appeal-vote">appeal vote</a><span>, in § 5.9</span>
+   <li><a href="#at-risk">at risk</a><span>, in § 6.3.7</span>
+   <li><a href="#bod">Board</a><span>, in § 2.2</span>
+   <li><a href="#bod">Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#bod">BoD</a><span>, in § 2.2</span>
+   <li><a href="#reviewform">Call for Review</a><span>, in § 5.7.1</span>
+   <li><a href="#candidate-addition">candidate addition</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-amendment">candidate amendment</a><span>, in § 6.2.5</span>
+   <li><a href="#candidate-correction">candidate correction</a><span>, in § 6.2.5</span>
+   <li><a href="#RecsCR">Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">Candidate Recommendation Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-review-period">Candidate Recommendation review period</a><span>, in § 6.3.7</span>
+   <li><a href="#candidate-recommendation-snapshot">Candidate Recommendation Snapshot</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-registry">Candidate Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-draft">Candidate Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#candidate-registry-snapshot">Candidate Registry Snapshot</a><span>, in § 6.5.2</span>
+   <li><a href="#ceo">CEO</a><span>, in § 2.2</span>
+   <li><a href="#GeneralChairs">Chair</a><span>, in § 3.4.1</span>
+   <li><a href="#chair-decisions">chair decisions</a><span>, in § 5.1</span>
+   <li><a href="#charter">charter</a><span>, in § 4.3</span>
+   <li><a href="#charter-draft">charter draft</a><span>, in § 4.1</span>
+   <li><a href="#chartered-group">chartered groups</a><span>, in § 3.4</span>
+   <li><a href="#dfn-charter-extension">charter extension</a><span>, in § 4.6</span>
+   <li><a href="#chartering-facilitator">Chartering Facilitator</a><span>, in § 4.2</span>
+   <li><a href="#charter-refinement">charter refinement</a><span>, in § 4.2</span>
+   <li><a href="#charter-review-notice">charter review notice</a><span>, in § 4.1</span>
+   <li><a href="#def-Consensus">Consensus</a><span>, in § 5.2.1</span>
+   <li><a href="#convened">convened</a><span>, in § 5.6.2.6</span>
+   <li><a href="#w3c-council">Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#council-report">Council Report</a><span>, in § 5.6.2.8</span>
+   <li><a href="#council-staff-contact">Council Staff Contact</a><span>, in § 5.6.2.1</span>
+   <li><a href="#RecsCR">CR</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-draft">CRD</a><span>, in § 6.3.1</span>
+   <li><a href="#candidate-recommendation-snapshot">CRS</a><span>, in § 6.3.1</span>
+   <li><a href="#custodian">custodian</a><span>, in § 6.5.1</span>
+   <li><a href="#discontinuedREC">Discontinued Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#dismissed">dismiss</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissal</a><span>, in § 5.6.2.3</span>
+   <li><a href="#dismissed">dismissed</a><span>, in § 5.6.2.3</span>
+   <li><a href="#def-Dissent">Dissent</a><span>, in § 5.2.1</span>
+   <li><a href="#distributed-meeting">distributed meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#editors-draft">ED</a><span>, in § 6.3.1</span>
+   <li><a href="#edited-recommendation">Edited Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#editors-draft">Editor Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#editorial-change">editorial change</a><span>, in § 6.2.3</span>
+   <li><a href="#editors-draft">Editor's Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#elected-group">elected groups</a><span>, in § 3.3</span>
+   <li><a href="#embedded-registry">embedded registry</a><span>, in § 6.5.2</span>
+   <li><a href="#erratum">errata</a><span>, in § 6.2.4</span>
+   <li><a href="#erratum">erratum</a><span>, in § 6.2.4</span>
+   <li><a href="#exclusion-draft">Exclusion Draft</a><span>, in § 4.3</span>
+   <li><a href="#exclusion-draft-charter">Exclusion Draft Charter</a><span>, in § 4.3</span>
+   <li><a href="#ftf-meeting">face-to-face meeting</a><span>, in § 3.1.2</span>
+   <li><a href="#fpwd">First Public Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#formally-addressed">formally addressed</a><span>, in § 5.3</span>
+   <li><a href="#FormalObjection">Formal Objection</a><span>, in § 5.5</span>
+   <li><a href="#fully-addressed">fully addressed</a><span>, in § 5.6.2.7</span>
+   <li><a href="#good-standing">Good Standing</a><span>, in § 2.1.3</span>
+   <li><a href="#w3c-group">group</a><span>, in § 3</span>
+   <li><a href="#group-decision">group decision</a><span>, in § 5.1</span>
+   <li><a href="#WGNote">Group Note</a><span>, in § 6.4.1</span>
+   <li><a href="#GroupsIG">Interest Groups</a><span>, in § 3.4</span>
+   <li><a href="#invited-expert-in-an-interest-group">Invited Expert in an Interest Group</a><span>, in § 3.4.3.4</span>
+   <li><a href="#invited-expert-in-a-working-group">Invited Expert in a Working Group</a><span>, in § 3.4.3.3</span>
+   <li><a href="#last-call">Last Call</a><span>, in § Unnumbered section</span>
+   <li><a href="#last-call-for-review-of-proposed-additions">Last Call for Review of Proposed Additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-review">Last Call for Review of Proposed Amendments</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections">Last Call for Review of Proposed Corrections</a><span>, in § 6.3.10.4</span>
+   <li><a href="#last-call-for-review-of-proposed-corrections-and-additions">Last Call for Review of Proposed Corrections and Additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#liaison">liaison</a><span>, in § 8</span>
+   <li><a href="#maturity-levels">Maturity level</a><span>, in § Unnumbered section</span>
+   <li><a href="#w3c-member">Member</a><span>, in § 2.1</span>
+   <li><a href="#member-association">Member Association</a><span>, in § 2.1.2.1</span>
+   <li><a href="#member-association">Member Associations</a><span>, in § 2.1.2.1</span>
+   <li><a href="#fdn-member-consortium">Member Consortium</a><span>, in § Unnumbered section</span>
+   <li><a href="#Member-only">Member-Only</a><span>, in § 7.2</span>
+   <li><a href="#member-representative-in-an-interest-group">Member representative in an Interest Group</a><span>, in § 3.4.3.2</span>
+   <li><a href="#member-representative-in-a-working-group">Member representative in a Working Group</a><span>, in § 3.4.3.1</span>
+   <li><a href="#MemberSubmission">Member Submission</a><span>, in § 9</span>
+   <li><a href="#mou">Memorandum of Understanding</a><span>, in § Unnumbered section</span>
+   <li><a href="#minor-changes">minor changes</a><span>, in § 4.4.2</span>
+   <li><a href="#minority-opinion">Minority Opinion</a><span>, in § 5.6.2.7</span>
+   <li><a href="#minutes">minutes</a><span>, in § 3.1.2.2</span>
+   <li><a href="#WGNote">Note</a><span>, in § 6.4.1</span>
+   <li><a href="#note-draft">Note Draft</a><span>, in § 6.4.1</span>
+   <li><a href="#not-required">not required</a><span>, in § Unnumbered section</span>
+   <li><a href="#RecsObs">Obsolete Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#obsolete-registry">Obsolete Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#other-charter">Other Charter</a><span>, in § Unnumbered section</span>
+   <li><a href="#overrule">overrule</a><span>, in § 5.6.2.7</span>
+   <li><a href="#overturn">overturn</a><span>, in § 5.6.2.7</span>
+   <li><a href="#participant">participant</a><span>, in § 3</span>
+   <li><a href="#igparticipant">participants in an Interest Group</a><span>, in § 3.4.2</span>
+   <li><a href="#wgparticipant">participants in a Working Group</a><span>, in § 3.4.2</span>
+   <li><a href="#inv-expert-info">participate in a Working Group as an Invited Expert</a><span>, in § 3.4.3.3</span>
+   <li><a href="#patent-review-drafts">Patent Review Drafts</a><span>, in § 6.3.1</span>
+   <li><a href="#primary-affiliation">primary affiliation</a><span>, in § 3.3.3.3</span>
+   <li><a href="#proposed-additions">proposed additions</a><span>, in § 6.3.10.4</span>
+   <li><a href="#proposed-amendments">proposed amendments</a><span>, in § 6.3.10.4</span>
+   <li><a href="#proposed-corrections">proposed corrections</a><span>, in § 6.3.10.4</span>
+   <li><a href="#RecsPR">Proposed Recommendation</a><span>, in § Unnumbered section</span>
+   <li><a href="#public-participant-ig">public participants</a><span>, in § 3.4.2</span>
+   <li><a href="#publishing">publish</a><span>, in § 6.2.1</span>
+   <li><a href="#RecsW3C">REC</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsW3C">Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track">Recommendation-track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">Recommendation Track document</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track-document">Recommendation-track document</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">REC Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">REC Track document</a><span>, in § 6.3.1</span>
+   <li><a href="#registry">registry</a><span>, in § 6.5</span>
+   <li><a href="#registry-change">registry change</a><span>, in § 6.2.3</span>
+   <li><a href="#registry-data">registry data</a><span>, in § 6.5</span>
+   <li><a href="#registry-data-report">Registry Data Report</a><span>, in § 6.5.4</span>
+   <li><a href="#registry-definition">registry definition</a><span>, in § 6.5.1</span>
+   <li><a href="#registry-draft">Registry Draft</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-entry">registry entry</a><span>, in § 6.5</span>
+   <li><a href="#registry-report">registry report</a><span>, in § 6.5.2</span>
+   <li><a href="#registry-table">registry table</a><span>, in § 6.5</span>
+   <li><a href="#registry-track">Registry Track</a><span>, in § 6.5.2</span>
+   <li><a href="#rejected">rejected</a><span>, in § 9</span>
+   <li><a href="#related-member">Related Member</a><span>, in § 2.1.2.2</span>
+   <li><a href="#renounce">renounce</a><span>, in § 5.6.2.3</span>
+   <li><a href="#renounce">renunciation</a><span>, in § 5.6.2.3</span>
+   <li><a href="#rescinded-candidate-recommendation">Rescinded Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#RescindedRec">Rescinded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#group-decision">resolution</a><span>, in § 5.1</span>
+   <li><a href="#TeamContact">Staff Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#statement">Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#submission-appeals">Submission Appeals</a><span>, in § 9</span>
+   <li><a href="#submitter">submitter</a><span>, in § 9</span>
+   <li><a href="#subsidiary">subsidiary</a><span>, in § 2.1.2.2</span>
+   <li><a href="#substantive-change">substantive change</a><span>, in § 6.2.3</span>
+   <li><a href="#mtg-substitute">substitute</a><span>, in § 3.4.2</span>
+   <li><a href="#RecsSup">Superseded Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#superseded-registry">Superseded Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#supplemental-confidential-council-report">Supplemental Confidential Council Report</a><span>, in § 5.6.2.8</span>
+   <li><a href="#technical-architecture-group">TAG</a><span>, in § 3.3.2.1</span>
+   <li><a href="#team">Team</a><span>, in § 2.2</span>
+   <li><a href="#team-contact">Team Contact</a><span>, in § 3.4.1</span>
+   <li><a href="#team-correction">Team correction</a><span>, in § 6.2.6</span>
+   <li><a href="#team-decision">Team Decision</a><span>, in § 5.1</span>
+   <li><a href="#Team-only">Team-Only</a><span>, in § 7.2</span>
+   <li><a href="#team-representative-in-an-interest-group">Team representative in an Interest Group</a><span>, in § 3.4.3.6</span>
+   <li><a href="#team-representative-in-a-working-group">Team representative in a Working Group</a><span>, in § 3.4.3.5</span>
+   <li><a href="#team-decision">Team's Decision</a><span>, in § 5.1</span>
+   <li><a href="#TeamSubmission">Team Submissions</a><span>, in § Unnumbered section</span>
+   <li><a href="#technical-agreement">technical agreement</a><span>, in § 8</span>
+   <li><a href="#technical-architecture-group">Technical Architecture Group</a><span>, in § 3.3.2.1</span>
+   <li><a href="#technical-report">Technical Report</a><span>, in § 6.2.1</span>
+   <li><a href="#trans-req">Transition Requests</a><span>, in § 6.3.3</span>
+   <li><a href="#def-Unanimity">Unanimity</a><span>, in § 5.2.1</span>
+   <li><a href="#update-requests">Update Requests</a><span>, in § 6.3.4</span>
+   <li><a href="#upheld">upheld</a><span>, in § 5.6.2.7</span>
+   <li><a href="#bod">W3C Board of Directors</a><span>, in § 2.2</span>
+   <li><a href="#RecsCR">W3C Candidate Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#def-W3CChair">W3C Chair</a><span>, in § Unnumbered section</span>
+   <li><a href="#w3c-council">W3C Council</a><span>, in § 5.6.2</span>
+   <li><a href="#w3c-council-chair">W3C Council Chair</a><span>, in § 5.6.2.5</span>
+   <li><a href="#def-w3c-decision">W3C decision</a><span>, in § 5.1</span>
+   <li><a href="#fellows">W3C Fellows</a><span>, in § 2.2</span>
+   <li><a href="#w3c-group">W3C Group</a><span>, in § 3</span>
+   <li><a href="#w3c-member">W3C Member</a><span>, in § 2.1</span>
+   <li><a href="#RecsW3C">W3C Recommendation</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-recommendation-track">W3C Recommendation Track</a><span>, in § 6.3</span>
+   <li><a href="#w3c-recommendation-track-document">W3C Recommendation Track document</a><span>, in § 6.3.1</span>
+   <li><a href="#w3c-registry">W3C Registry</a><span>, in § 6.5.2</span>
+   <li><a href="#statement">W3C Statement</a><span>, in § 6.4.3</span>
+   <li><a href="#team">W3C Team</a><span>, in § 2.2</span>
+   <li><a href="#RecsWD">W3C Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#RecsWD">WD</a><span>, in § 6.3.1</span>
+   <li><a href="#dfn-wide-review">wide review</a><span>, in § 6.2.2.1</span>
+   <li><a href="#RecsWD">Working Draft</a><span>, in § 6.3.1</span>
+   <li><a href="#GroupsWG">Working Groups</a><span>, in § 3.4</span>
+   <li><a href="#EventsW">Workshop</a><span>, in § 2.1.1</span>
+  </ul>
+  <h3 class="no-num no-ref heading settled" id="index-defined-elsewhere"><span class="content">Terms defined by reference</span><a class="self-link" href="#index-defined-elsewhere"></a></h3>
+  <ul class="index">
+   <li>
+    <a data-link-type="biblio">[W3C-PATENT-POLICY]</a> defines the following terms:
+    <ul>
+     <li><span class="dfn-paneled" id="33fd2aef">Exclusion Opportunity</span>
+     <li><span class="dfn-paneled" id="74c78a1e">Patent Advisory Group</span>
+    </ul>
+  </ul>
+  <h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
+  <h3 class="no-num no-ref heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
+  <dl>
+   <dt id="biblio-coc">[COC]
+   <dd><a href="https://www.w3.org/policies/code-of-conduct/"><cite>W3C Code of Conduct</cite></a>. URL: <a href="https://www.w3.org/policies/code-of-conduct/">https://www.w3.org/policies/code-of-conduct/</a>
+   <dt id="biblio-collaborators-agreement">[COLLABORATORS-AGREEMENT]
+   <dd><a href="https://www.w3.org/invited-experts/agreement-2023/"><cite>Invited expert and collaborators agreement</cite></a>. URL: <a href="https://www.w3.org/invited-experts/agreement-2023/">https://www.w3.org/invited-experts/agreement-2023/</a>
+   <dt id="biblio-conflict-policy">[CONFLICT-POLICY]
+   <dd><a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/"><cite>Conflict of Interest Policy for the W3C Team</cite></a>. URL: <a href="https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/">https://www.w3.org/policies/conflict-of-interest-policy-for-w3c-team/</a>
+   <dt id="biblio-doc-license">[DOC-LICENSE]
+   <dd><a href="https://www.w3.org/copyright/document-license-2023/"><cite>W3C Document License</cite></a>. URL: <a href="https://www.w3.org/copyright/document-license-2023/">https://www.w3.org/copyright/document-license-2023/</a>
+   <dt id="biblio-patent-policy">[PATENT-POLICY]
+   <dd><a href="https://www.w3.org/policies/patent-policy/"><cite>The W3C Patent Policy</cite></a>. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
+   <dt id="biblio-patent-policy-2004">[PATENT-POLICY-2004]
+   <dd><a href="https://www.w3.org/Consortium/Patent-Policy-20170801/"><cite>The W3C 2004 Patent Policy, Updated 2017</cite></a>. URL: <a href="https://www.w3.org/Consortium/Patent-Policy-20170801/">https://www.w3.org/Consortium/Patent-Policy-20170801/</a>
+   <dt id="biblio-patent-policy-2020">[PATENT-POLICY-2020]
+   <dd><a href="https://www.w3.org/policies/patent-policy/20200915/"><cite>The W3C 2020 Patent Policy</cite></a>. URL: <a href="https://www.w3.org/policies/patent-policy/20200915/">https://www.w3.org/policies/patent-policy/20200915/</a>
+   <dt id="biblio-pubrules">[PUBRULES]
+   <dd><a href="https://www.w3.org/pubrules/"><cite>Publication Rules</cite></a>. URL: <a href="https://www.w3.org/pubrules/">https://www.w3.org/pubrules/</a>
+   <dt id="biblio-rfc2119">[RFC2119]
+   <dd>S. Bradner. <a href="https://datatracker.ietf.org/doc/html/rfc2119"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. March 1997. Best Current Practice. URL: <a href="https://datatracker.ietf.org/doc/html/rfc2119">https://datatracker.ietf.org/doc/html/rfc2119</a>
+   <dt id="biblio-rfc3797">[RFC3797]
+   <dd>D. Eastlake 3rd. <a href="https://www.rfc-editor.org/rfc/rfc3797"><cite>Publicly Verifiable Nominations Committee (NomCom) Random Selection</cite></a>. June 2004. Informational. URL: <a href="https://www.rfc-editor.org/rfc/rfc3797">https://www.rfc-editor.org/rfc/rfc3797</a>
+   <dt id="biblio-w3c-patent-policy">[W3C-PATENT-POLICY]
+   <dd>Wendy Seltzer. <a href="https://www.w3.org/policies/patent-policy/"><cite>W3C Patent Policy</cite></a>. 15 September 2020. URL: <a href="https://www.w3.org/policies/patent-policy/">https://www.w3.org/policies/patent-policy/</a>
+  </dl>
+  <h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
+  <dl>
+   <dt id="biblio-ab-hp">[AB-HP]
+   <dd><a href="https://www.w3.org/2002/ab/"><cite>The Advisory Board home page</cite></a>. URL: <a href="https://www.w3.org/2002/ab/">https://www.w3.org/2002/ab/</a>
+   <dt id="biblio-ac-meeting">[AC-MEETING]
+   <dd><a href="https://www.w3.org/events/ac/"><cite>Advisory Committee meetings (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/events/ac/">https://www.w3.org/events/ac/</a>
+   <dt id="biblio-bg-cg">[BG-CG]
+   <dd><a href="https://www.w3.org/community/about/process/"><cite>Community and Business Group Process</cite></a>. URL: <a href="https://www.w3.org/community/about/process/">https://www.w3.org/community/about/process/</a>
+   <dt id="biblio-bylaws">[BYLAWS]
+   <dd><a href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf"><cite>Amended and Restated Bylaws of World Wide Web Consortium, Inc.</cite></a>. URL: <a href="https://www.w3.org/2024/09/25-w3c-bylaws.pdf">https://www.w3.org/2024/09/25-w3c-bylaws.pdf</a>
+   <dt id="biblio-calendar">[CALENDAR]
+   <dd><a href="https://www.w3.org/events/"><cite>Calendar of all scheduled official W3C events</cite></a>. URL: <a href="https://www.w3.org/events/">https://www.w3.org/events/</a>
+   <dt id="biblio-chair">[CHAIR]
+   <dd><a href="https://www.w3.org/guide/chair/role"><cite>W3C Working/Interest Group Chair</cite></a>. URL: <a href="https://www.w3.org/guide/chair/role">https://www.w3.org/guide/chair/role</a>
+   <dt id="biblio-charter">[CHARTER]
+   <dd><a href="https://www.w3.org/guide/process/charter"><cite>How to Create a Working Group or Interest Group</cite></a>. URL: <a href="https://www.w3.org/guide/process/charter">https://www.w3.org/guide/process/charter</a>
+   <dt id="biblio-council-report-index">[COUNCIL-REPORT-INDEX]
+   <dd><a href="https://www.w3.org/about/council/"><cite>Council Report Index</cite></a>. URL: <a href="https://www.w3.org/about/council/">https://www.w3.org/about/council/</a>
+   <dt id="biblio-current-ac">[CURRENT-AC]
+   <dd><a href="https://www.w3.org/Member/ACList"><cite>Current Advisory Committee representatives (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/ACList">https://www.w3.org/Member/ACList</a>
+   <dt id="biblio-decision-appeal">[DECISION-APPEAL]
+   <dd><a href="https://www.w3.org/guide/process/ac-appeal"><cite>Appealing a W3C Decision</cite></a>. URL: <a href="https://www.w3.org/guide/process/ac-appeal">https://www.w3.org/guide/process/ac-appeal</a>
+   <dt id="biblio-election-howto">[ELECTION-HOWTO]
+   <dd><a href="https://www.w3.org/guide/process/election"><cite>How to Organize an Advisory Board or TAG election</cite></a>. URL: <a href="https://www.w3.org/guide/process/election">https://www.w3.org/guide/process/election</a>
+   <dt id="biblio-fellows">[FELLOWS]
+   <dd><a href="https://www.w3.org/careers/fellows/"><cite>W3C Fellows Program</cite></a>. URL: <a href="https://www.w3.org/careers/fellows/">https://www.w3.org/careers/fellows/</a>
+   <dt id="biblio-group-mail">[GROUP-MAIL]
+   <dd><a href="https://www.w3.org/groups/"><cite>Group mailing lists</cite></a>. URL: <a href="https://www.w3.org/groups/">https://www.w3.org/groups/</a>
+   <dt id="biblio-guide">[GUIDE]
+   <dd><a href="https://www.w3.org/guide/"><cite>The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators</cite></a>. URL: <a href="https://www.w3.org/guide/">https://www.w3.org/guide/</a>
+   <dt id="biblio-intro">[INTRO]
+   <dd><a href="https://www.w3.org/Member/Intro"><cite>Process, Patent Policy, Finances, Specs management, Strategic vision (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/Intro">https://www.w3.org/Member/Intro</a>
+   <dt id="biblio-join">[JOIN]
+   <dd><a href="https://www.w3.org/membership/join/"><cite>How to Join W3C</cite></a>. URL: <a href="https://www.w3.org/membership/join/">https://www.w3.org/membership/join/</a>
+   <dt id="biblio-liaison">[LIAISON]
+   <dd><a href="https://www.w3.org/liaisons/"><cite>W3C liaisons with other organizations</cite></a>. URL: <a href="https://www.w3.org/liaisons/">https://www.w3.org/liaisons/</a>
+   <dt id="biblio-member-agreement">[MEMBER-AGREEMENT]
+   <dd><a href="https://www.w3.org/membership/agreement/"><cite>W3C Membership Agreement</cite></a>. URL: <a href="https://www.w3.org/membership/agreement/">https://www.w3.org/membership/agreement/</a>
+   <dt id="biblio-member-hp">[MEMBER-HP]
+   <dd><a href="https://www.w3.org/Member/"><cite>Member website (Member-only access)</cite></a>. URL: <a href="https://www.w3.org/Member/">https://www.w3.org/Member/</a>
+   <dt id="biblio-member-list">[MEMBER-LIST]
+   <dd><a href="https://www.w3.org/membership/list/"><cite>The list of current W3C Members</cite></a>. URL: <a href="https://www.w3.org/membership/list/">https://www.w3.org/membership/list/</a>
+   <dt id="biblio-member-sub">[MEMBER-SUB]
+   <dd><a href="https://www.w3.org/submissions/guide/"><cite>Member submissions guidebook</cite></a>. URL: <a href="https://www.w3.org/submissions/guide/">https://www.w3.org/submissions/guide/</a>
+   <dt id="biblio-mission">[MISSION]
+   <dd><a href="https://www.w3.org/mission/"><cite>The W3C Mission statement</cite></a>. URL: <a href="https://www.w3.org/mission/">https://www.w3.org/mission/</a>
+   <dt id="biblio-obs-resc">[OBS-RESC]
+   <dd><a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded"><cite>Obsoleting and Rescinding W3C Specifications</cite></a>. URL: <a href="https://www.w3.org/guide/process/obsolete-rescinded-supserseded">https://www.w3.org/guide/process/obsolete-rescinded-supserseded</a>
+   <dt id="biblio-rec-tips">[REC-TIPS]
+   <dd><a href="https://www.w3.org/guide/standards-track/rec-tips"><cite>Tips for Getting to Recommendation Faster</cite></a>. URL: <a href="https://www.w3.org/guide/standards-track/rec-tips">https://www.w3.org/guide/standards-track/rec-tips</a>
+   <dt id="biblio-republishing">[REPUBLISHING]
+   <dd><a href="https://www.w3.org/guide/standards-track/republishing"><cite>In-place modification of W3C Technical Reports</cite></a>. URL: <a href="https://www.w3.org/guide/standards-track/republishing">https://www.w3.org/guide/standards-track/republishing</a>
+   <dt id="biblio-submission-list">[SUBMISSION-LIST]
+   <dd><a href="https://www.w3.org/submissions/"><cite>The list of acknowledged Member Submissions</cite></a>. URL: <a href="https://www.w3.org/submissions/">https://www.w3.org/submissions/</a>
+   <dt id="biblio-tag-hp">[TAG-HP]
+   <dd><a href="https://www.w3.org/2001/tag/"><cite>The TAG home page</cite></a>. URL: <a href="https://www.w3.org/2001/tag/">https://www.w3.org/2001/tag/</a>
+   <dt id="biblio-team-contact">[TEAM-CONTACT]
+   <dd><a href="https://www.w3.org/guide/teamcontact/role"><cite>Role of the Team Contact</cite></a>. URL: <a href="https://www.w3.org/guide/teamcontact/role">https://www.w3.org/guide/teamcontact/role</a>
+   <dt id="biblio-tr">[TR]
+   <dd><a href="https://www.w3.org/TR/"><cite>The W3C technical reports index</cite></a>. URL: <a href="https://www.w3.org/TR/">https://www.w3.org/TR/</a>
+   <dt id="biblio-transition">[TRANSITION]
+   <dd><a href="https://www.w3.org/guide/transitions/"><cite>Organize a Technical Report Transition</cite></a>. URL: <a href="https://www.w3.org/guide/transitions/">https://www.w3.org/guide/transitions/</a>
+   <dt id="biblio-translation">[TRANSLATION]
+   <dd><a href="https://www.w3.org/Consortium/Translation/"><cite>Translations of W3C technical reports</cite></a>. URL: <a href="https://www.w3.org/Consortium/Translation/">https://www.w3.org/Consortium/Translation/</a>
+   <dt id="biblio-w3c-ipr">[W3C-IPR]
+   <dd><a href="https://www.w3.org/policies/"><cite>W3C IPR Policies</cite></a>. URL: <a href="https://www.w3.org/policies/">https://www.w3.org/policies/</a>
+  </dl>
+<script>/* Boilerplate: script-dom-helper */
+"use strict";
+function query(sel) { return document.querySelector(sel); }
+
+function queryAll(sel) { return [...document.querySelectorAll(sel)]; }
+
+function iter(obj) {
+	if(!obj) return [];
+	var it = obj[Symbol.iterator];
+	if(it) return it;
+	return Object.entries(obj);
+}
+
+function mk(tagname, attrs, ...children) {
+	const el = document.createElement(tagname);
+	for(const [k,v] of iter(attrs)) {
+		if(k.slice(0,3) == "_on") {
+			const eventName = k.slice(3);
+			el.addEventListener(eventName, v);
+		} else if(k[0] == "_") {
+			// property, not attribute
+			el[k.slice(1)] = v;
+		} else {
+			if(v === false || v == null) {
+        continue;
+      } else if(v === true) {
+        el.setAttribute(k, "");
+        continue;
+      } else {
+  			el.setAttribute(k, v);
+      }
+		}
+	}
+	append(el, children);
+	return el;
+}
+
+/* Create shortcuts for every known HTML element */
+[
+  "a",
+  "abbr",
+  "acronym",
+  "address",
+  "applet",
+  "area",
+  "article",
+  "aside",
+  "audio",
+  "b",
+  "base",
+  "basefont",
+  "bdo",
+  "big",
+  "blockquote",
+  "body",
+  "br",
+  "button",
+  "canvas",
+  "caption",
+  "center",
+  "cite",
+  "code",
+  "col",
+  "colgroup",
+  "datalist",
+  "dd",
+  "del",
+  "details",
+  "dfn",
+  "dialog",
+  "div",
+  "dl",
+  "dt",
+  "em",
+  "embed",
+  "fieldset",
+  "figcaption",
+  "figure",
+  "font",
+  "footer",
+  "form",
+  "frame",
+  "frameset",
+  "head",
+  "header",
+  "h1",
+  "h2",
+  "h3",
+  "h4",
+  "h5",
+  "h6",
+  "hr",
+  "html",
+  "i",
+  "iframe",
+  "img",
+  "input",
+  "ins",
+  "kbd",
+  "label",
+  "legend",
+  "li",
+  "link",
+  "main",
+  "map",
+  "mark",
+  "meta",
+  "meter",
+  "nav",
+  "nobr",
+  "noscript",
+  "object",
+  "ol",
+  "optgroup",
+  "option",
+  "output",
+  "p",
+  "param",
+  "pre",
+  "progress",
+  "q",
+  "s",
+  "samp",
+  "script",
+  "section",
+  "select",
+  "small",
+  "source",
+  "span",
+  "strike",
+  "strong",
+  "style",
+  "sub",
+  "summary",
+  "sup",
+  "table",
+  "tbody",
+  "td",
+  "template",
+  "textarea",
+  "tfoot",
+  "th",
+  "thead",
+  "time",
+  "title",
+  "tr",
+  "u",
+  "ul",
+  "var",
+  "video",
+  "wbr",
+  "xmp",
+].forEach(tagname=>{
+	mk[tagname] = (...args) => mk(tagname, ...args);
+});
+
+function* nodesFromChildList(children) {
+	for(const child of children.flat(Infinity)) {
+		if(child instanceof Node) {
+			yield child;
+		} else {
+			yield new Text(child);
+		}
+	}
+}
+function append(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		if(el instanceof Node) el.appendChild(child);
+		else el.push(child);
+	}
+	return el;
+}
+
+function insertAfter(el, ...children) {
+	for(const child of nodesFromChildList(children)) {
+		el.parentNode.insertBefore(child, el.nextSibling);
+	}
+	return el;
+}
+
+function clearContents(el) {
+	el.innerHTML = "";
+	return el;
+}
+
+function parseHTML(markup) {
+	if(markup.toLowerCase().trim().indexOf('<!doctype') === 0) {
+		const doc = document.implementation.createHTMLDocument("");
+		doc.documentElement.innerHTML = markup;
+		return doc;
+	} else {
+		const el = mk.template({});
+		el.innerHTML = markup;
+		return el.content;
+	}
+}</script>
+<script>/* Boilerplate: script-dfn-panel */
+"use strict";
+{
+let dfnPanelData = {
+"33fd2aef": {"dfnID":"33fd2aef","dfnText":"Exclusion Opportunity","external":true,"refSections":[{"refs":[{"id":"ref-for-exclusion-opportunity"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
+"74c78a1e": {"dfnID":"74c78a1e","dfnText":"Patent Advisory Group","external":true,"refSections":[{"refs":[{"id":"ref-for-patent-advisory-group"}],"title":"4.7. \nChartered Group Closure"}],"url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
+"EventsW": {"dfnID":"EventsW","dfnText":"Workshop","external":false,"refSections":[{"refs":[{"id":"ref-for-EventsW"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-EventsW\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-EventsW\u2461"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-EventsW\u2462"}],"title":"7.1. \nPublic Communication"}],"url":"#EventsW"},
+"FormalObjection": {"dfnID":"FormalObjection","dfnText":"Formal Objection","external":false,"refSections":[{"refs":[{"id":"ref-for-FormalObjection"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-FormalObjection\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-FormalObjection\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-FormalObjection\u2462"},{"id":"ref-for-FormalObjection\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-FormalObjection\u2464"}],"title":"5. \nDecisions"},{"refs":[{"id":"ref-for-FormalObjection\u2465"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-FormalObjection\u2466"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-FormalObjection\u2467"},{"id":"ref-for-FormalObjection\u2468"},{"id":"ref-for-FormalObjection\u2460\u24ea"},{"id":"ref-for-FormalObjection\u2460\u2460"},{"id":"ref-for-FormalObjection\u2460\u2461"},{"id":"ref-for-FormalObjection\u2460\u2462"},{"id":"ref-for-FormalObjection\u2460\u2463"},{"id":"ref-for-FormalObjection\u2460\u2464"},{"id":"ref-for-FormalObjection\u2460\u2465"},{"id":"ref-for-FormalObjection\u2460\u2466"},{"id":"ref-for-FormalObjection\u2460\u2467"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-FormalObjection\u2460\u2468"},{"id":"ref-for-FormalObjection\u2461\u24ea"},{"id":"ref-for-FormalObjection\u2461\u2460"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2461"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2462"},{"id":"ref-for-FormalObjection\u2461\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2464"},{"id":"ref-for-FormalObjection\u2461\u2465"},{"id":"ref-for-FormalObjection\u2461\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-FormalObjection\u2461\u2468"},{"id":"ref-for-FormalObjection\u2462\u24ea"},{"id":"ref-for-FormalObjection\u2462\u2460"},{"id":"ref-for-FormalObjection\u2462\u2461"},{"id":"ref-for-FormalObjection\u2462\u2462"},{"id":"ref-for-FormalObjection\u2462\u2463"},{"id":"ref-for-FormalObjection\u2462\u2464"},{"id":"ref-for-FormalObjection\u2462\u2465"},{"id":"ref-for-FormalObjection\u2462\u2466"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2462\u2468"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u24ea"},{"id":"ref-for-FormalObjection\u2463\u2460"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2461"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2462"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-FormalObjection\u2463\u2463"}],"title":"9. \nMember Submissions"}],"url":"#FormalObjection"},
+"GeneralChairs": {"dfnID":"GeneralChairs","dfnText":"Chair","external":false,"refSections":[{"refs":[{"id":"ref-for-GeneralChairs"}],"title":"3.1.1.2. \nConflict of Interest Policy"},{"refs":[{"id":"ref-for-GeneralChairs\u2460"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-GeneralChairs\u2461"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-GeneralChairs\u2462"},{"id":"ref-for-GeneralChairs\u2463"},{"id":"ref-for-GeneralChairs\u2464"},{"id":"ref-for-GeneralChairs\u2465"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-GeneralChairs\u2466"},{"id":"ref-for-GeneralChairs\u2467"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GeneralChairs\u2468"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u24ea"},{"id":"ref-for-GeneralChairs\u2460\u2460"},{"id":"ref-for-GeneralChairs\u2460\u2461"},{"id":"ref-for-GeneralChairs\u2460\u2462"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2464"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2465"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2466"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GeneralChairs\u2460\u2467"},{"id":"ref-for-GeneralChairs\u2460\u2468"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u24ea"},{"id":"ref-for-GeneralChairs\u2461\u2460"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2461"},{"id":"ref-for-GeneralChairs\u2461\u2462"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2463"},{"id":"ref-for-GeneralChairs\u2461\u2464"}],"title":"5.2.3. \nDeciding by Vote"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2465"},{"id":"ref-for-GeneralChairs\u2461\u2466"}],"title":"5.4. \nReopening a Decision When Presented With New Information"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2467"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-GeneralChairs\u2461\u2468"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-GeneralChairs\u2462\u24ea"},{"id":"ref-for-GeneralChairs\u2462\u2460"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-GeneralChairs\u2462\u2461"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#GeneralChairs"},
+"GroupsIG": {"dfnID":"GroupsIG","dfnText":"Interest Groups","external":false,"refSections":[{"refs":[{"id":"ref-for-GroupsIG"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-GroupsIG"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-GroupsIG\u2460"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GroupsIG\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-GroupsIG\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-GroupsIG\u2463"},{"id":"ref-for-GroupsIG\u2464"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GroupsIG\u2465"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-GroupsIG\u2466"},{"id":"ref-for-GroupsIG\u2467"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GroupsIG\u2468"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-GroupsIG\u2460\u24ea"},{"id":"ref-for-GroupsIG\u2460\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsIG\u2460\u2461"}],"title":"6.4.1. \nGroup Notes"}],"url":"#GroupsIG"},
+"GroupsWG": {"dfnID":"GroupsWG","dfnText":"Working Groups","external":false,"refSections":[{"refs":[{"id":"ref-for-GroupsWG"},{"id":"ref-for-GroupsWG\u2460"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-GroupsWG\u2461"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-GroupsWG\u2462"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-GroupsWG"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-GroupsWG\u2463"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-GroupsWG\u2464"},{"id":"ref-for-GroupsWG\u2465"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-GroupsWG\u2466"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-GroupsWG\u2467"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-GroupsWG\u2468"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u24ea"},{"id":"ref-for-GroupsWG\u2460\u2460"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2461"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2462"},{"id":"ref-for-GroupsWG\u2460\u2463"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2464"}],"title":"6. \nW3C Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2465"},{"id":"ref-for-GroupsWG\u2460\u2466"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2467"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-GroupsWG\u2460\u2468"},{"id":"ref-for-GroupsWG\u2461\u24ea"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2460"},{"id":"ref-for-GroupsWG\u2461\u2461"},{"id":"ref-for-GroupsWG\u2461\u2462"},{"id":"ref-for-GroupsWG\u2461\u2463"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2464"},{"id":"ref-for-GroupsWG\u2461\u2465"},{"id":"ref-for-GroupsWG\u2461\u2466"},{"id":"ref-for-GroupsWG\u2461\u2467"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-GroupsWG\u2461\u2468"},{"id":"ref-for-GroupsWG\u2462\u24ea"},{"id":"ref-for-GroupsWG\u2462\u2460"},{"id":"ref-for-GroupsWG\u2462\u2461"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2462\u2462"},{"id":"ref-for-GroupsWG\u2462\u2463"},{"id":"ref-for-GroupsWG\u2462\u2464"},{"id":"ref-for-GroupsWG\u2462\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2462\u2466"},{"id":"ref-for-GroupsWG\u2462\u2467"},{"id":"ref-for-GroupsWG\u2462\u2468"},{"id":"ref-for-GroupsWG\u2463\u24ea"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2460"},{"id":"ref-for-GroupsWG\u2463\u2461"},{"id":"ref-for-GroupsWG\u2463\u2462"},{"id":"ref-for-GroupsWG\u2463\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2464"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2465"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2466"},{"id":"ref-for-GroupsWG\u2463\u2467"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2463\u2468"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u24ea"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2460"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2461"},{"id":"ref-for-GroupsWG\u2464\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2463"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2464"},{"id":"ref-for-GroupsWG\u2464\u2465"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-GroupsWG\u2464\u2466"},{"id":"ref-for-GroupsWG\u2464\u2467"},{"id":"ref-for-GroupsWG\u2464\u2468"},{"id":"ref-for-GroupsWG\u2465\u24ea"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2460"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2461"}],"title":"6.3.12. \nRetiring Recommendation Track Documents"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2462"},{"id":"ref-for-GroupsWG\u2465\u2463"},{"id":"ref-for-GroupsWG\u2465\u2464"},{"id":"ref-for-GroupsWG\u2465\u2465"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2465\u2466"},{"id":"ref-for-GroupsWG\u2465\u2467"},{"id":"ref-for-GroupsWG\u2465\u2468"},{"id":"ref-for-GroupsWG\u2466\u24ea"},{"id":"ref-for-GroupsWG\u2466\u2460"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2461"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2462"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2463"},{"id":"ref-for-GroupsWG\u2466\u2464"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-GroupsWG\u2466\u2465"}],"title":"10. \nProcess Evolution"}],"url":"#GroupsWG"},
+"Member-only": {"dfnID":"Member-only","dfnText":"Member-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Member-only"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-Member-only"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-Member-only"},{"id":"ref-for-Member-only"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-Member-only"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-Member-only\u2460"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-Member-only\u2461"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Member-only\u2462"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-Member-only\u2463"},{"id":"ref-for-Member-only\u2464"},{"id":"ref-for-Member-only\u2465"},{"id":"ref-for-Member-only\u2466"},{"id":"ref-for-Member-only\u2467"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Member-only\u2468"},{"id":"ref-for-Member-only\u2460\u24ea"},{"id":"ref-for-Member-only\u2460\u2460"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Member-only"},
+"MemberSubmission": {"dfnID":"MemberSubmission","dfnText":"Member Submission","external":false,"refSections":[{"refs":[{"id":"ref-for-MemberSubmission"},{"id":"ref-for-MemberSubmission\u2460"},{"id":"ref-for-MemberSubmission\u2461"},{"id":"ref-for-MemberSubmission\u2462"}],"title":"9. \nMember Submissions"}],"url":"#MemberSubmission"},
+"RecsCR": {"dfnID":"RecsCR","dfnText":"Candidate Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsCR"},{"id":"ref-for-RecsCR\u2460"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-RecsCR\u2461"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-RecsCR\u2462"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsCR\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-RecsCR\u2464"},{"id":"ref-for-RecsCR\u2465"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2466"},{"id":"ref-for-RecsCR\u2467"},{"id":"ref-for-RecsCR\u2468"},{"id":"ref-for-RecsCR\u2460\u24ea"},{"id":"ref-for-RecsCR\u2460\u2460"},{"id":"ref-for-RecsCR\u2460\u2461"},{"id":"ref-for-RecsCR\u2460\u2462"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2463"},{"id":"ref-for-RecsCR\u2460\u2464"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2467"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2460\u2468"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-RecsCR\u2461\u24ea"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-RecsCR\u2461\u2460"}],"title":"6.3.12.2. \nRescinding a Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsCR\u2461\u2461"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsCR"},
+"RecsObs": {"dfnID":"RecsObs","dfnText":"Obsolete Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsObs"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsObs\u2460"},{"id":"ref-for-RecsObs\u2461"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsObs\u2462"},{"id":"ref-for-RecsObs\u2463"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RecsObs\u2464"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsObs"},
+"RecsPR": {"dfnID":"RecsPR","dfnText":"Proposed Recommendation","external":false,"refSections":[],"url":"#RecsPR"},
+"RecsSup": {"dfnID":"RecsSup","dfnText":"Superseded Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsSup"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsSup\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RecsSup"},
+"RecsW3C": {"dfnID":"RecsW3C","dfnText":"W3C Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsW3C"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-RecsW3C"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-RecsW3C\u2460"},{"id":"ref-for-RecsW3C\u2461"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-RecsW3C\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-RecsW3C\u2463"},{"id":"ref-for-RecsW3C\u2464"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-RecsW3C\u2465"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsW3C\u2466"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-RecsW3C\u2467"},{"id":"ref-for-RecsW3C"},{"id":"ref-for-RecsW3C\u2468"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2460\u24ea"},{"id":"ref-for-RecsW3C\u2460\u2460"},{"id":"ref-for-RecsW3C\u2460\u2461"},{"id":"ref-for-RecsW3C\u2460\u2462"},{"id":"ref-for-RecsW3C\u2460\u2463"},{"id":"ref-for-RecsW3C\u2460\u2464"},{"id":"ref-for-RecsW3C\u2460\u2465"},{"id":"ref-for-RecsW3C\u2460\u2466"},{"id":"ref-for-RecsW3C\u2460\u2467"},{"id":"ref-for-RecsW3C\u2460\u2468"},{"id":"ref-for-RecsW3C\u2461\u24ea"},{"id":"ref-for-RecsW3C\u2461\u2460"},{"id":"ref-for-RecsW3C\u2461\u2461"},{"id":"ref-for-RecsW3C\u2461\u2462"},{"id":"ref-for-RecsW3C\u2461\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2464"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2467"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2461\u2468"},{"id":"ref-for-RecsW3C\u2462\u24ea"},{"id":"ref-for-RecsW3C\u2462\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2461"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2462"},{"id":"ref-for-RecsW3C\u2462\u2463"},{"id":"ref-for-RecsW3C\u2462\u2464"},{"id":"ref-for-RecsW3C\u2462\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2466"},{"id":"ref-for-RecsW3C\u2462\u2467"}],"title":"6.3.9.4. \nNext Steps from W3C Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2462\u2468"},{"id":"ref-for-RecsW3C\u2463\u24ea"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-RecsW3C\u2463\u2460"},{"id":"ref-for-RecsW3C\u2463\u2461"},{"id":"ref-for-RecsW3C\u2463\u2462"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-RecsW3C\u2463\u2463"},{"id":"ref-for-RecsW3C\u2463\u2464"},{"id":"ref-for-RecsW3C\u2463\u2465"},{"id":"ref-for-RecsW3C\u2463\u2466"},{"id":"ref-for-RecsW3C\u2463\u2467"},{"id":"ref-for-RecsW3C\u2463\u2468"},{"id":"ref-for-RecsW3C\u2464\u24ea"},{"id":"ref-for-RecsW3C\u2464\u2460"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2461"},{"id":"ref-for-RecsW3C\u2464\u2462"},{"id":"ref-for-RecsW3C\u2464\u2463"},{"id":"ref-for-RecsW3C\u2464\u2464"},{"id":"ref-for-RecsW3C\u2464\u2465"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2466"}],"title":"6.3.12.2. \nRescinding a Candidate Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2464\u2467"},{"id":"ref-for-RecsW3C\u2464\u2468"},{"id":"ref-for-RecsW3C\u2465\u24ea"},{"id":"ref-for-RecsW3C\u2465\u2460"},{"id":"ref-for-RecsW3C\u2465\u2461"},{"id":"ref-for-RecsW3C\u2465\u2462"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2465\u2463"},{"id":"ref-for-RecsW3C\u2465\u2464"},{"id":"ref-for-RecsW3C\u2465\u2465"},{"id":"ref-for-RecsW3C\u2465\u2466"},{"id":"ref-for-RecsW3C\u2465\u2467"},{"id":"ref-for-RecsW3C\u2465\u2468"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u24ea"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2460"},{"id":"ref-for-RecsW3C\u2466\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2462"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-RecsW3C\u2466\u2463"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#RecsW3C"},
+"RecsWD": {"dfnID":"RecsWD","dfnText":"Working Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-RecsWD"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-RecsWD\u2460"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-RecsWD\u2461"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-RecsWD\u2462"},{"id":"ref-for-RecsWD\u2463"},{"id":"ref-for-RecsWD\u2464"},{"id":"ref-for-RecsWD\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RecsWD\u2466"},{"id":"ref-for-RecsWD\u2467"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-RecsWD\u2468"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-RecsWD\u2460\u24ea"},{"id":"ref-for-RecsWD\u2460\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-RecsWD\u2460\u2461"},{"id":"ref-for-RecsWD\u2460\u2462"},{"id":"ref-for-RecsWD\u2460\u2463"}],"title":"6.6. \nSwitching Tracks"}],"url":"#RecsWD"},
+"RescindedRec": {"dfnID":"RescindedRec","dfnText":"Rescinded Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-RescindedRec"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-RescindedRec\u2460"}],"title":"6.3.12.3. \nAbandoning a W3C Recommendation"},{"refs":[{"id":"ref-for-RescindedRec\u2461"},{"id":"ref-for-RescindedRec\u2462"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-RescindedRec\u2463"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#RescindedRec"},
+"Team-only": {"dfnID":"Team-only","dfnText":"Team-only","external":false,"refSections":[{"refs":[{"id":"ref-for-Team-only"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-Team-only"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-Team-only\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-Team-only\u2461"},{"id":"ref-for-Team-only\u2462"},{"id":"ref-for-Team-only\u2463"},{"id":"ref-for-Team-only\u2464"}],"title":"7.3. \nChanging Confidentiality Level"}],"url":"#Team-only"},
+"TeamContact": {"dfnID":"TeamContact","dfnText":"Staff Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-TeamContact"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-TeamContact\u2460"},{"id":"ref-for-TeamContact\u2461"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2462"}],"title":"3.4.2. \nParticipation in Chartered Groups"},{"refs":[{"id":"ref-for-TeamContact\u2463"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2464"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-TeamContact\u2465"},{"id":"ref-for-TeamContact\u2466"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-TeamContact\u2467"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-TeamContact\u2468"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-TeamContact\u2460\u24ea"}],"title":"5.5. \nRegistering Formal Objections"}],"url":"#TeamContact"},
+"TeamSubmission": {"dfnID":"TeamSubmission","dfnText":"Team Submissions","external":false,"refSections":[],"url":"#TeamSubmission"},
+"WGNote": {"dfnID":"WGNote","dfnText":"Group Note","external":false,"refSections":[{"refs":[{"id":"ref-for-WGNote"}],"title":"3.4. \nChartered Groups: Working Groups and Interest Groups"},{"refs":[{"id":"ref-for-WGNote"},{"id":"ref-for-WGNote\u2460"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-WGNote\u2461"},{"id":"ref-for-WGNote\u2462"},{"id":"ref-for-WGNote\u2463"},{"id":"ref-for-WGNote\u2464"},{"id":"ref-for-WGNote\u2465"},{"id":"ref-for-WGNote\u2466"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-WGNote\u2467"},{"id":"ref-for-WGNote\u2468"},{"id":"ref-for-WGNote\u2460\u24ea"},{"id":"ref-for-WGNote\u2460\u2460"},{"id":"ref-for-WGNote\u2460\u2461"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-WGNote\u2460\u2462"},{"id":"ref-for-WGNote\u2460\u2463"},{"id":"ref-for-WGNote\u2460\u2464"},{"id":"ref-for-WGNote\u2460\u2465"},{"id":"ref-for-WGNote\u2460\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#WGNote"},
+"acknowledged": {"dfnID":"acknowledged","dfnText":"acknowledged","external":false,"refSections":[{"refs":[{"id":"ref-for-acknowledged"},{"id":"ref-for-acknowledged\u2460"}],"title":"9. \nMember Submissions"}],"url":"#acknowledged"},
+"adequate-implementation": {"dfnID":"adequate-implementation","dfnText":"adequate implementation experience","external":false,"refSections":[{"refs":[{"id":"ref-for-adequate-implementation"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-adequate-implementation\u2460"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-adequate-implementation\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-adequate-implementation\u2462"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#adequate-implementation"},
+"adopted-draft": {"dfnID":"adopted-draft","dfnText":"Adopted Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-adopted-draft"}],"title":"4.3. \nContent of a Charter"}],"url":"#adopted-draft"},
+"advisory-board": {"dfnID":"advisory-board","dfnText":"Advisory Board","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-board"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-advisory-board\u2460"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-advisory-board\u2461"},{"id":"ref-for-advisory-board\u2462"},{"id":"ref-for-advisory-board\u2463"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2464"},{"id":"ref-for-advisory-board\u2465"},{"id":"ref-for-advisory-board\u2466"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2467"}],"title":"3.3.1.3. \nCommunications of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-board\u2468"},{"id":"ref-for-advisory-board\u2460\u24ea"},{"id":"ref-for-advisory-board\u2460\u2460"}],"title":"3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2461"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2462"},{"id":"ref-for-advisory-board\u2460\u2463"},{"id":"ref-for-advisory-board\u2460\u2464"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2465"},{"id":"ref-for-advisory-board\u2460\u2466"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2467"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-advisory-board\u2460\u2468"}],"title":"3.3.3.5. \nVerifiable Random Selection Procedure"},{"refs":[{"id":"ref-for-advisory-board\u2461\u24ea"},{"id":"ref-for-advisory-board\u2461\u2460"},{"id":"ref-for-advisory-board\u2461\u2461"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2462"},{"id":"ref-for-advisory-board\u2461\u2463"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2464"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2465"},{"id":"ref-for-advisory-board\u2461\u2466"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-advisory-board\u2461\u2467"},{"id":"ref-for-advisory-board\u2461\u2468"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-advisory-board\u2462\u24ea"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2460"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2461"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2462"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-advisory-board\u2462\u2463"},{"id":"ref-for-advisory-board\u2462\u2464"},{"id":"ref-for-advisory-board\u2462\u2465"},{"id":"ref-for-advisory-board\u2462\u2466"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-board"},
+"advisory-committee": {"dfnID":"advisory-committee","dfnText":"Advisory Committee","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee"}],"title":"2.1. \nMembers"},{"refs":[{"id":"ref-for-advisory-committee\u2460"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee\u2461"},{"id":"ref-for-advisory-committee\u2462"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-advisory-committee\u2463"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-advisory-committee\u2464"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-advisory-committee\u2465"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-advisory-committee\u2466"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-advisory-committee\u2467"},{"id":"ref-for-advisory-committee\u2468"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u24ea"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2460"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2461"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2462"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2463"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2464"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2465"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2466"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee\u2460\u2467"},{"id":"ref-for-advisory-committee\u2460\u2468"},{"id":"ref-for-advisory-committee\u2461\u24ea"},{"id":"ref-for-advisory-committee\u2461\u2460"},{"id":"ref-for-advisory-committee\u2461\u2461"},{"id":"ref-for-advisory-committee\u2461\u2462"},{"id":"ref-for-advisory-committee\u2461\u2463"},{"id":"ref-for-advisory-committee\u2461\u2464"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-advisory-committee\u2461\u2465"},{"id":"ref-for-advisory-committee\u2461\u2466"}],"title":"5.8. \nAdvisory Committee Votes"},{"refs":[{"id":"ref-for-advisory-committee\u2461\u2467"},{"id":"ref-for-advisory-committee\u2461\u2468"},{"id":"ref-for-advisory-committee\u2462\u24ea"},{"id":"ref-for-advisory-committee\u2462\u2460"},{"id":"ref-for-advisory-committee\u2462\u2461"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2462"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2463"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2464"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2465"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2466"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2467"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee\u2462\u2468"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee\u2463\u24ea"},{"id":"ref-for-advisory-committee\u2463\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee\u2463\u2461"},{"id":"ref-for-advisory-committee\u2463\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-committee"},
+"advisory-committee-appeal": {"dfnID":"advisory-committee-appeal","dfnText":"Advisory Committee Appeal","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-appeal"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2461"}],"title":"5.8. \nAdvisory Committee Votes"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2462"},{"id":"ref-for-advisory-committee-appeal\u2463"},{"id":"ref-for-advisory-committee-appeal\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2468"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u24ea"},{"id":"ref-for-advisory-committee-appeal\u2460\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u2461"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-advisory-committee-appeal\u2460\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#advisory-committee-appeal"},
+"advisory-committee-representative": {"dfnID":"advisory-committee-representative","dfnText":"representative","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-representative"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460"}],"title":"3.1.1.3. \nIndividuals Representing a Member Organization"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461"},{"id":"ref-for-advisory-committee-representative\u2462"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2463"},{"id":"ref-for-advisory-committee-representative\u2464"}],"title":"3.2.2. \nParticipation in the Advisory Committee"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2465"},{"id":"ref-for-advisory-committee-representative\u2466"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2467"},{"id":"ref-for-advisory-committee-representative\u2468"},{"id":"ref-for-advisory-committee-representative\u2460\u24ea"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2460"}],"title":"3.4.3.1. \nMember Representative in a Working Group"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2461"}],"title":"3.4.3.2. \nMember Representative in an Interest Group"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2462"},{"id":"ref-for-advisory-committee-representative\u2460\u2463"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2464"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2465"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2466"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2467"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2460\u2468"},{"id":"ref-for-advisory-committee-representative\u2461\u24ea"},{"id":"ref-for-advisory-committee-representative\u2461\u2460"},{"id":"ref-for-advisory-committee-representative\u2461\u2461"},{"id":"ref-for-advisory-committee-representative\u2461\u2462"},{"id":"ref-for-advisory-committee-representative\u2461\u2463"},{"id":"ref-for-advisory-committee-representative\u2461\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2465"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2461\u2468"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u24ea"},{"id":"ref-for-advisory-committee-representative\u2462\u2460"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2461"}],"title":"7.3. \nChanging Confidentiality Level"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2462"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-advisory-committee-representative\u2462\u2463"},{"id":"ref-for-advisory-committee-representative\u2462\u2464"},{"id":"ref-for-advisory-committee-representative\u2462\u2465"}],"title":"9. \nMember Submissions"}],"url":"#advisory-committee-representative"},
+"advisory-committee-review": {"dfnID":"advisory-committee-review","dfnText":"Advisory Committee review","external":false,"refSections":[{"refs":[{"id":"ref-for-advisory-committee-review"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460"},{"id":"ref-for-advisory-committee-review\u2461"},{"id":"ref-for-advisory-committee-review\u2462"},{"id":"ref-for-advisory-committee-review\u2463"},{"id":"ref-for-advisory-committee-review\u2464"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-advisory-committee-review\u2465"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-advisory-committee-review\u2466"},{"id":"ref-for-advisory-committee-review\u2467"},{"id":"ref-for-advisory-committee-review\u2468"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u24ea"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2460"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2461"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2462"},{"id":"ref-for-advisory-committee-review\u2460\u2463"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2460\u2464"},{"id":"ref-for-advisory-committee-review\u2460\u2465"},{"id":"ref-for-advisory-committee-review\u2460\u2466"},{"id":"ref-for-advisory-committee-review\u2460\u2467"},{"id":"ref-for-advisory-committee-review\u2460\u2468"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u24ea"},{"id":"ref-for-advisory-committee-review\u2461\u2460"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2462"},{"id":"ref-for-advisory-committee-review\u2461\u2463"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2465"},{"id":"ref-for-advisory-committee-review\u2461\u2466"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2467"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-review\u2461\u2468"},{"id":"ref-for-advisory-committee-review\u2462\u24ea"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2461"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2462"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2463"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2464"}],"title":"10. \nProcess Evolution"},{"refs":[{"id":"ref-for-advisory-committee-review\u2462\u2465"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#advisory-committee-review"},
+"affirm": {"dfnID":"affirm","dfnText":"affirm","external":false,"refSections":[{"refs":[{"id":"ref-for-affirm"},{"id":"ref-for-affirm\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-affirm\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-affirm\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"#affirm"},
+"allow-new-features": {"dfnID":"allow-new-features","dfnText":"allow new features","external":false,"refSections":[{"refs":[{"id":"ref-for-allow-new-features"},{"id":"ref-for-allow-new-features\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-allow-new-features\u2461"},{"id":"ref-for-allow-new-features\u2462"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-allow-new-features\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#allow-new-features"},
+"alternate-ac-representative": {"dfnID":"alternate-ac-representative","dfnText":"alternate","external":false,"refSections":[],"url":"#alternate-ac-representative"},
+"appeal-vote": {"dfnID":"appeal-vote","dfnText":"appeal vote","external":false,"refSections":[{"refs":[{"id":"ref-for-appeal-vote"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-appeal-vote\u2460"}],"title":"5.8. \nAdvisory Committee Votes"}],"url":"#appeal-vote"},
+"at-risk": {"dfnID":"at-risk","dfnText":"at risk","external":false,"refSections":[{"refs":[{"id":"ref-for-at-risk"},{"id":"ref-for-at-risk\u2460"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-at-risk\u2461"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-at-risk\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-at-risk\u2463"}],"title":"6.3.9.3. \nResolution of Review"}],"url":"#at-risk"},
+"bod": {"dfnID":"bod","dfnText":"W3C Board of Directors","external":false,"refSections":[{"refs":[{"id":"ref-for-bod"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-bod\u2460"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-bod\u2461"},{"id":"ref-for-bod\u2462"},{"id":"ref-for-bod\u2463"},{"id":"ref-for-bod\u2464"},{"id":"ref-for-bod\u2465"}],"title":"3.3.1.4. \nLiaisons between the Advisory Board and the Board of Directors"},{"refs":[{"id":"ref-for-bod\u2466"},{"id":"ref-for-bod\u2467"}],"title":"8. \nLiaisons"}],"url":"#bod"},
+"candidate-addition": {"dfnID":"candidate-addition","dfnText":"candidate addition","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-addition"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-addition\u2460"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"}],"url":"#candidate-addition"},
+"candidate-amendment": {"dfnID":"candidate-amendment","dfnText":"candidate amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-amendment"},{"id":"ref-for-candidate-amendment\u2460"},{"id":"ref-for-candidate-amendment\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-amendment\u2462"},{"id":"ref-for-candidate-amendment\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-candidate-amendment\u2464"},{"id":"ref-for-candidate-amendment\u2465"},{"id":"ref-for-candidate-amendment\u2466"},{"id":"ref-for-candidate-amendment\u2467"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-candidate-amendment\u2468"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#candidate-amendment"},
+"candidate-correction": {"dfnID":"candidate-correction","dfnText":"candidate correction","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-correction"},{"id":"ref-for-candidate-correction\u2460"},{"id":"ref-for-candidate-correction\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-candidate-correction\u2462"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-candidate-correction\u2463"},{"id":"ref-for-candidate-correction\u2464"},{"id":"ref-for-candidate-correction\u2465"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"}],"url":"#candidate-correction"},
+"candidate-recommendation-draft": {"dfnID":"candidate-recommendation-draft","dfnText":"Candidate Recommendation Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-draft"},{"id":"ref-for-candidate-recommendation-draft\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2461"},{"id":"ref-for-candidate-recommendation-draft\u2462"},{"id":"ref-for-candidate-recommendation-draft\u2463"},{"id":"ref-for-candidate-recommendation-draft\u2464"},{"id":"ref-for-candidate-recommendation-draft\u2465"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2466"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-candidate-recommendation-draft\u2467"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#candidate-recommendation-draft"},
+"candidate-recommendation-review-period": {"dfnID":"candidate-recommendation-review-period","dfnText":"Candidate Recommendation review period","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-review-period"},{"id":"ref-for-candidate-recommendation-review-period\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"}],"url":"#candidate-recommendation-review-period"},
+"candidate-recommendation-snapshot": {"dfnID":"candidate-recommendation-snapshot","dfnText":"Candidate Recommendation Snapshot","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-recommendation-snapshot"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460"},{"id":"ref-for-candidate-recommendation-snapshot\u2461"},{"id":"ref-for-candidate-recommendation-snapshot\u2462"},{"id":"ref-for-candidate-recommendation-snapshot\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2464"},{"id":"ref-for-candidate-recommendation-snapshot\u2465"},{"id":"ref-for-candidate-recommendation-snapshot\u2466"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2467"},{"id":"ref-for-candidate-recommendation-snapshot\u2468"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u24ea"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2460"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2461"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2462"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2463"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2464"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2465"},{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2466"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2467"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-candidate-recommendation-snapshot\u2460\u2468"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#candidate-recommendation-snapshot"},
+"candidate-registry": {"dfnID":"candidate-registry","dfnText":"Candidate Registry","external":false,"refSections":[{"refs":[{"id":"ref-for-candidate-registry"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#candidate-registry"},
+"candidate-registry-draft": {"dfnID":"candidate-registry-draft","dfnText":"Candidate Registry Draft","external":false,"refSections":[],"url":"#candidate-registry-draft"},
+"candidate-registry-snapshot": {"dfnID":"candidate-registry-snapshot","dfnText":"Candidate Registry Snapshot","external":false,"refSections":[],"url":"#candidate-registry-snapshot"},
+"ceo": {"dfnID":"ceo","dfnText":"CEO","external":false,"refSections":[{"refs":[{"id":"ref-for-ceo"}],"title":"2.1.2.1. \nMembership Associations"},{"refs":[{"id":"ref-for-ceo\u2460"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-ceo\u2461"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-ceo\u2462"}],"title":"3.1.1.3. \nIndividuals Representing a Member Organization"},{"refs":[{"id":"ref-for-ceo\u2463"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-ceo\u2464"},{"id":"ref-for-ceo\u2465"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-ceo\u2466"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-ceo\u2467"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-ceo\u2468"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#ceo"},
+"chair-decisions": {"dfnID":"chair-decisions","dfnText":"chair decisions","external":false,"refSections":[],"url":"#chair-decisions"},
+"charter": {"dfnID":"charter","dfnText":"charter","external":false,"refSections":[{"refs":[{"id":"ref-for-charter"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-charter\u2460"},{"id":"ref-for-charter\u2461"},{"id":"ref-for-charter\u2462"},{"id":"ref-for-charter\u2463"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-charter\u2464"},{"id":"ref-for-charter\u2465"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter\u2466"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-charter\u2467"},{"id":"ref-for-charter\u2468"},{"id":"ref-for-charter\u2460\u24ea"},{"id":"ref-for-charter\u2460\u2460"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-charter\u2460\u2461"},{"id":"ref-for-charter\u2460\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-charter\u2460\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-charter\u2460\u2464"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-charter\u2460\u2465"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-charter\u2460\u2466"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-charter\u2460\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"}],"url":"#charter"},
+"charter-draft": {"dfnID":"charter-draft","dfnText":"charter draft","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-draft"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-draft\u2460"},{"id":"ref-for-charter-draft\u2461"},{"id":"ref-for-charter-draft\u2462"},{"id":"ref-for-charter-draft\u2463"}],"title":"4.2. \nCharter Refinement"}],"url":"#charter-draft"},
+"charter-refinement": {"dfnID":"charter-refinement","dfnText":"charter refinement","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-refinement"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-charter-refinement\u2460"},{"id":"ref-for-charter-refinement\u2461"},{"id":"ref-for-charter-refinement\u2462"},{"id":"ref-for-charter-refinement\u2463"},{"id":"ref-for-charter-refinement\u2464"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-refinement\u2465"},{"id":"ref-for-charter-refinement\u2466"},{"id":"ref-for-charter-refinement\u2467"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-charter-refinement\u2468"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-charter-refinement\u2460\u24ea"},{"id":"ref-for-charter-refinement\u2460\u2460"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-charter-refinement\u2460\u2461"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#charter-refinement"},
+"charter-review-notice": {"dfnID":"charter-review-notice","dfnText":"charter review notice","external":false,"refSections":[{"refs":[{"id":"ref-for-charter-review-notice"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-charter-review-notice\u2460"}],"title":"4.2. \nCharter Refinement"}],"url":"#charter-review-notice"},
+"chartered-group": {"dfnID":"chartered-group","dfnText":"chartered groups","external":false,"refSections":[{"refs":[{"id":"ref-for-chartered-group"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-chartered-group\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-chartered-group\u2461"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-chartered-group\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-chartered-group\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-chartered-group\u2464"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-chartered-group\u2465"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#chartered-group"},
+"chartering-facilitator": {"dfnID":"chartering-facilitator","dfnText":"Chartering Facilitator","external":false,"refSections":[{"refs":[{"id":"ref-for-chartering-facilitator"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-chartering-facilitator\u2460"},{"id":"ref-for-chartering-facilitator\u2461"},{"id":"ref-for-chartering-facilitator\u2462"}],"title":"4.2. \nCharter Refinement"}],"url":"#chartering-facilitator"},
+"convened": {"dfnID":"convened","dfnText":"convened","external":false,"refSections":[{"refs":[{"id":"ref-for-convened"},{"id":"ref-for-convened\u2460"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-convened\u2461"},{"id":"ref-for-convened\u2462"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#convened"},
+"council-report": {"dfnID":"council-report","dfnText":"Council Report","external":false,"refSections":[{"refs":[{"id":"ref-for-council-report"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-council-report\u2460"},{"id":"ref-for-council-report\u2461"},{"id":"ref-for-council-report\u2462"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-council-report\u2463"}],"title":"5.6.2.9. \nAppealing Council Decisions"},{"refs":[{"id":"ref-for-council-report\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-council-report\u2465"}],"title":"9. \nMember Submissions"}],"url":"#council-report"},
+"council-staff-contact": {"dfnID":"council-staff-contact","dfnText":"Council Staff Contact","external":false,"refSections":[{"refs":[{"id":"ref-for-council-staff-contact"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-council-staff-contact\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#council-staff-contact"},
+"custodian": {"dfnID":"custodian","dfnText":"custodian","external":false,"refSections":[{"refs":[{"id":"ref-for-custodian"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-custodian\u2460"},{"id":"ref-for-custodian\u2461"},{"id":"ref-for-custodian\u2462"},{"id":"ref-for-custodian\u2463"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-custodian\u2464"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-custodian\u2465"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#custodian"},
+"def-Consensus": {"dfnID":"def-Consensus","dfnText":"Consensus","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Consensus"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-def-Consensus\u2460"},{"id":"ref-for-def-Consensus\u2461"},{"id":"ref-for-def-Consensus\u2462"},{"id":"ref-for-def-Consensus\u2463"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-def-Consensus\u2464"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-def-Consensus\u2465"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-def-Consensus\u2466"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-def-Consensus\u2467"},{"id":"ref-for-def-Consensus\u2468"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u24ea"},{"id":"ref-for-def-Consensus\u2460\u2460"},{"id":"ref-for-def-Consensus\u2460\u2461"},{"id":"ref-for-def-Consensus\u2460\u2462"},{"id":"ref-for-def-Consensus\u2460\u2463"},{"id":"ref-for-def-Consensus\u2460\u2464"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2465"}],"title":"6. \nW3C Technical Reports"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2466"},{"id":"ref-for-def-Consensus\u2460\u2467"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-def-Consensus\u2460\u2468"},{"id":"ref-for-def-Consensus\u2461\u24ea"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-def-Consensus\u2461\u2460"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-def-Consensus\u2461\u2461"}],"title":"10. \nProcess Evolution"}],"url":"#def-Consensus"},
+"def-Dissent": {"dfnID":"def-Dissent","dfnText":"Dissent","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Dissent"},{"id":"ref-for-def-Dissent\u2460"}],"title":"5.2.2. \nManaging Dissent"},{"refs":[{"id":"ref-for-def-Dissent\u2461"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-def-Dissent\u2462"},{"id":"ref-for-def-Dissent\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-Dissent\u2464"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-def-Dissent\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#def-Dissent"},
+"def-Unanimity": {"dfnID":"def-Unanimity","dfnText":"Unanimity","external":false,"refSections":[{"refs":[{"id":"ref-for-def-Unanimity"}],"title":"5.2.1. \nConsensus"}],"url":"#def-Unanimity"},
+"def-W3CChair": {"dfnID":"def-W3CChair","dfnText":"W3C Chair","external":false,"refSections":[],"url":"#def-W3CChair"},
+"def-w3c-decision": {"dfnID":"def-w3c-decision","dfnText":"W3C decision","external":false,"refSections":[{"refs":[{"id":"ref-for-def-w3c-decision"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-def-w3c-decision\u2461"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-def-w3c-decision\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-def-w3c-decision\u2463"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-def-w3c-decision\u2464"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-def-w3c-decision\u2465"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-def-w3c-decision\u2466"},{"id":"ref-for-def-w3c-decision\u2467"},{"id":"ref-for-def-w3c-decision\u2468"},{"id":"ref-for-def-w3c-decision\u2460\u24ea"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2460"},{"id":"ref-for-def-w3c-decision\u2460\u2461"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2462"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2463"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2464"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2465"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2466"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-def-w3c-decision\u2460\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#def-w3c-decision"},
+"dfn-charter-extension": {"dfnID":"dfn-charter-extension","dfnText":"extensions","external":false,"refSections":[{"refs":[{"id":"ref-for-dfn-charter-extension"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"}],"url":"#dfn-charter-extension"},
+"dfn-wide-review": {"dfnID":"dfn-wide-review","dfnText":"wide review","external":false,"refSections":[{"refs":[{"id":"ref-for-dfn-wide-review"}],"title":"4. \nLifecycle of Chartered Groups"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-dfn-wide-review\u2461"},{"id":"ref-for-dfn-wide-review\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-dfn-wide-review\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-dfn-wide-review\u2464"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2465"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2466"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2467"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-dfn-wide-review\u2468"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460\u24ea"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-dfn-wide-review\u2460\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"}],"url":"#dfn-wide-review"},
+"discontinuedREC": {"dfnID":"discontinuedREC","dfnText":"Discontinued Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-discontinuedREC"},{"id":"ref-for-discontinuedREC\u2460"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"}],"url":"#discontinuedREC"},
+"dismissed": {"dfnID":"dismissed","dfnText":"dismissed","external":false,"refSections":[{"refs":[{"id":"ref-for-dismissed"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-dismissed\u2460"},{"id":"ref-for-dismissed\u2461"},{"id":"ref-for-dismissed\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-dismissed\u2463"},{"id":"ref-for-dismissed\u2464"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-dismissed\u2465"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#dismissed"},
+"distributed-meeting": {"dfnID":"distributed-meeting","dfnText":"distributed meeting","external":false,"refSections":[{"refs":[{"id":"ref-for-distributed-meeting"}],"title":"5.2.1. \nConsensus"}],"url":"#distributed-meeting"},
+"edited-recommendation": {"dfnID":"edited-recommendation","dfnText":"Edited Recommendation","external":false,"refSections":[],"url":"#edited-recommendation"},
+"editorial-change": {"dfnID":"editorial-change","dfnText":"editorial changes","external":false,"refSections":[{"refs":[{"id":"ref-for-editorial-change"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-editorial-change\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2462"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-editorial-change\u2463"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-editorial-change\u2464"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-editorial-change\u2465"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-editorial-change\u2466"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-editorial-change\u2467"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-editorial-change\u2468"},{"id":"ref-for-editorial-change\u2460\u24ea"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#editorial-change"},
+"editors-draft": {"dfnID":"editors-draft","dfnText":"Editor\u2019s drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-editors-draft"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"}],"url":"#editors-draft"},
+"elected-group": {"dfnID":"elected-group","dfnText":"elected groups","external":false,"refSections":[{"refs":[{"id":"ref-for-elected-group"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-elected-group\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-elected-group\u2461"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#elected-group"},
+"embedded-registry": {"dfnID":"embedded-registry","dfnText":"embedded registry","external":false,"refSections":[{"refs":[{"id":"ref-for-embedded-registry"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-embedded-registry\u2460"},{"id":"ref-for-embedded-registry\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-embedded-registry\u2462"},{"id":"ref-for-embedded-registry\u2463"}],"title":"6.5.6. \nRegistries and Patents"},{"refs":[{"id":"ref-for-embedded-registry\u2464"}],"title":"\nChanges since the 3 November 2023 Process"}],"url":"#embedded-registry"},
+"erratum": {"dfnID":"erratum","dfnText":"erratum","external":false,"refSections":[{"refs":[{"id":"ref-for-erratum"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-erratum\u2460"},{"id":"ref-for-erratum\u2461"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#erratum"},
+"exclusion-draft": {"dfnID":"exclusion-draft","dfnText":"Exclusion Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-exclusion-draft"},{"id":"ref-for-exclusion-draft\u2460"}],"title":"4.3. \nContent of a Charter"}],"url":"#exclusion-draft"},
+"exclusion-draft-charter": {"dfnID":"exclusion-draft-charter","dfnText":"Exclusion Draft Charter","external":false,"refSections":[{"refs":[{"id":"ref-for-exclusion-draft-charter"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#exclusion-draft-charter"},
+"fdn-member-consortium": {"dfnID":"fdn-member-consortium","dfnText":"Member Consortium","external":false,"refSections":[],"url":"#fdn-member-consortium"},
+"fellows": {"dfnID":"fellows","dfnText":"W3C Fellows","external":false,"refSections":[{"refs":[{"id":"ref-for-fellows"}],"title":"2.1.1. \nRights of Members"},{"refs":[{"id":"ref-for-fellows"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}],"url":"#fellows"},
+"formally-addressed": {"dfnID":"formally-addressed","dfnText":"formally addressed","external":false,"refSections":[{"refs":[{"id":"ref-for-formally-addressed"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-formally-addressed\u2460"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-formally-addressed\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-formally-addressed\u2462"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-formally-addressed\u2463"},{"id":"ref-for-formally-addressed\u2464"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-formally-addressed\u2465"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-formally-addressed\u2466"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-formally-addressed\u2467"}],"title":"10. \nProcess Evolution"}],"url":"#formally-addressed"},
+"fpwd": {"dfnID":"fpwd","dfnText":"First Public Working Draft","external":false,"refSections":[{"refs":[{"id":"ref-for-fpwd"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-fpwd\u2460"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-fpwd\u2461"},{"id":"ref-for-fpwd\u2462"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-fpwd\u2463"},{"id":"ref-for-fpwd\u2464"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-fpwd\u2465"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-fpwd\u2466"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-fpwd\u2467"},{"id":"ref-for-fpwd\u2468"}],"title":"6.6. \nSwitching Tracks"}],"url":"#fpwd"},
+"ftf-meeting": {"dfnID":"ftf-meeting","dfnText":"face-to-face meeting","external":false,"refSections":[{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"5.2.1. \nConsensus"},{"refs":[{"id":"ref-for-ftf-meeting"}],"title":"5.6.2.1. \nCouncil Composition"}],"url":"#ftf-meeting"},
+"fully-addressed": {"dfnID":"fully-addressed","dfnText":"fully addressed","external":false,"refSections":[{"refs":[{"id":"ref-for-fully-addressed"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-fully-addressed\u2460"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#fully-addressed"},
+"good-standing": {"dfnID":"good-standing","dfnText":"Good Standing","external":false,"refSections":[{"refs":[{"id":"ref-for-good-standing"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-good-standing\u2460"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-good-standing\u2461"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"}],"url":"#good-standing"},
+"group-decision": {"dfnID":"group-decision","dfnText":"group decisions","external":false,"refSections":[{"refs":[{"id":"ref-for-group-decision"},{"id":"ref-for-group-decision\u2460"}],"title":"3.1.2.2. \nMeeting Minutes"},{"refs":[{"id":"ref-for-group-decision\u2461"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-group-decision\u2462"}],"title":"6.3.9. \nTransitioning to Recommendation"},{"refs":[{"id":"ref-for-group-decision\u2463"}],"title":"6.3.10.1. \nRevising a Recommendation: Editorial Changes"},{"refs":[{"id":"ref-for-group-decision\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-group-decision\u2465"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-group-decision\u2466"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-group-decision\u2467"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-group-decision\u2468"}],"title":"6.6. \nSwitching Tracks"}],"url":"#group-decision"},
+"igparticipant": {"dfnID":"igparticipant","dfnText":"participants in an Interest Group","external":false,"refSections":[{"refs":[{"id":"ref-for-igparticipant"}],"title":"3. \nGroups and Participation"},{"refs":[{"id":"ref-for-igparticipant"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#igparticipant"},
+"inv-expert-info": {"dfnID":"inv-expert-info","dfnText":"participate in a Working Group as an Invited Expert","external":false,"refSections":[{"refs":[{"id":"ref-for-inv-expert-info"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-inv-expert-info"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"}],"url":"#inv-expert-info"},
+"invited-expert-in-a-working-group": {"dfnID":"invited-expert-in-a-working-group","dfnText":"Invited Expert in a Working Group","external":false,"refSections":[{"refs":[{"id":"ref-for-invited-expert-in-a-working-group"}],"title":"3.4.3.3. \nInvited Expert in a Working Group"},{"refs":[{"id":"ref-for-invited-expert-in-a-working-group\u2460"}],"title":"3.4.3.4. \nInvited Expert in an Interest Group"}],"url":"#invited-expert-in-a-working-group"},
+"invited-expert-in-an-interest-group": {"dfnID":"invited-expert-in-an-interest-group","dfnText":"Invited Expert in an Interest Group","external":false,"refSections":[],"url":"#invited-expert-in-an-interest-group"},
+"last-call": {"dfnID":"last-call","dfnText":"Last Call","external":false,"refSections":[],"url":"#last-call"},
+"last-call-for-review-of-proposed-additions": {"dfnID":"last-call-for-review-of-proposed-additions","dfnText":"Last Call for Review of Proposed Additions","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-additions"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-for-review-of-proposed-additions"},
+"last-call-for-review-of-proposed-corrections": {"dfnID":"last-call-for-review-of-proposed-corrections","dfnText":"Last Call for Review of Proposed Corrections","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-corrections"}],"title":"6.4.4. \nRevising W3C Statements"}],"url":"#last-call-for-review-of-proposed-corrections"},
+"last-call-for-review-of-proposed-corrections-and-additions": {"dfnID":"last-call-for-review-of-proposed-corrections-and-additions","dfnText":"Last Call for Review of Proposed Corrections and Additions","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-for-review-of-proposed-corrections-and-additions"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-for-review-of-proposed-corrections-and-additions"},
+"last-call-review": {"dfnID":"last-call-review","dfnText":"Last Call for Review of Proposed Amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-last-call-review"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-last-call-review\u2460"},{"id":"ref-for-last-call-review\u2461"},{"id":"ref-for-last-call-review\u2462"},{"id":"ref-for-last-call-review\u2463"},{"id":"ref-for-last-call-review\u2464"},{"id":"ref-for-last-call-review\u2465"},{"id":"ref-for-last-call-review\u2466"},{"id":"ref-for-last-call-review\u2467"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"}],"url":"#last-call-review"},
+"liaison": {"dfnID":"liaison","dfnText":"liaison","external":false,"refSections":[],"url":"#liaison"},
+"maturity-levels": {"dfnID":"maturity-levels","dfnText":"Maturity level","external":false,"refSections":[],"url":"#maturity-levels"},
+"member-association": {"dfnID":"member-association","dfnText":"Member Association","external":false,"refSections":[{"refs":[{"id":"ref-for-member-association"},{"id":"ref-for-member-association\u2460"},{"id":"ref-for-member-association\u2461"},{"id":"ref-for-member-association\u2462"},{"id":"ref-for-member-association\u2463"},{"id":"ref-for-member-association\u2464"}],"title":"2.1.2.1. \nMembership Associations"},{"refs":[{"id":"ref-for-member-association\u2465"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#member-association"},
+"member-representative-in-a-working-group": {"dfnID":"member-representative-in-a-working-group","dfnText":"Member representative in a Working Group","external":false,"refSections":[],"url":"#member-representative-in-a-working-group"},
+"member-representative-in-an-interest-group": {"dfnID":"member-representative-in-an-interest-group","dfnText":"Member representative in an Interest Group","external":false,"refSections":[{"refs":[{"id":"ref-for-member-representative-in-an-interest-group"}],"title":"3.4.3.2. \nMember Representative in an Interest Group"}],"url":"#member-representative-in-an-interest-group"},
+"minor-changes": {"dfnID":"minor-changes","dfnText":"minor changes","external":false,"refSections":[{"refs":[{"id":"ref-for-minor-changes"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-minor-changes\u2460"},{"id":"ref-for-minor-changes\u2461"},{"id":"ref-for-minor-changes\u2462"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#minor-changes"},
+"minority-opinion": {"dfnID":"minority-opinion","dfnText":"Minority Opinion","external":false,"refSections":[{"refs":[{"id":"ref-for-minority-opinion"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#minority-opinion"},
+"minutes": {"dfnID":"minutes","dfnText":"minutes","external":false,"refSections":[{"refs":[{"id":"ref-for-minutes"}],"title":"3.1.2.1. \nMeeting Scheduling and Announcements"},{"refs":[{"id":"ref-for-minutes\u2460"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-minutes\u2461"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#minutes"},
+"mou": {"dfnID":"mou","dfnText":"Memorandum of Understanding","external":false,"refSections":[],"url":"#mou"},
+"mtg-substitute": {"dfnID":"mtg-substitute","dfnText":"substitute","external":false,"refSections":[{"refs":[{"id":"ref-for-mtg-substitute"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#mtg-substitute"},
+"not-required": {"dfnID":"not-required","dfnText":"not required","external":false,"refSections":[],"url":"#not-required"},
+"note-draft": {"dfnID":"note-draft","dfnText":"Note Drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-note-draft"},{"id":"ref-for-note-draft\u2460"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-note-draft\u2461"},{"id":"ref-for-note-draft\u2462"},{"id":"ref-for-note-draft\u2463"},{"id":"ref-for-note-draft\u2464"}],"title":"6.4.2. \nPublishing Notes"}],"url":"#note-draft"},
+"obsolete-registry": {"dfnID":"obsolete-registry","dfnText":"Obsolete Registry","external":false,"refSections":[],"url":"#obsolete-registry"},
+"other-charter": {"dfnID":"other-charter","dfnText":"Other Charter","external":false,"refSections":[],"url":"#other-charter"},
+"overrule": {"dfnID":"overrule","dfnText":"overruled","external":false,"refSections":[{"refs":[{"id":"ref-for-overrule"},{"id":"ref-for-overrule\u2460"},{"id":"ref-for-overrule\u2461"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-overrule\u2462"}],"title":"6.3.9.3. \nResolution of Review"}],"url":"#overrule"},
+"overturn": {"dfnID":"overturn","dfnText":"overturn","external":false,"refSections":[{"refs":[{"id":"ref-for-overturn"},{"id":"ref-for-overturn\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-overturn\u2461"},{"id":"ref-for-overturn\u2462"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#overturn"},
+"participant": {"dfnID":"participant","dfnText":"participant","external":false,"refSections":[{"refs":[{"id":"ref-for-participant"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-participant\u2460"}],"title":"5.2.3. \nDeciding by Vote"}],"url":"#participant"},
+"patent-review-drafts": {"dfnID":"patent-review-drafts","dfnText":"Patent Review Drafts","external":false,"refSections":[{"refs":[{"id":"ref-for-patent-review-drafts"},{"id":"ref-for-patent-review-drafts\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-patent-review-drafts\u2461"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-patent-review-drafts\u2462"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-patent-review-drafts\u2463"}],"title":"6.6. \nSwitching Tracks"}],"url":"#patent-review-drafts"},
+"primary-affiliation": {"dfnID":"primary-affiliation","dfnText":"primary affiliation","external":false,"refSections":[{"refs":[{"id":"ref-for-primary-affiliation"},{"id":"ref-for-primary-affiliation\u2460"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-primary-affiliation\u2461"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"}],"url":"#primary-affiliation"},
+"proposed-additions": {"dfnID":"proposed-additions","dfnText":"proposed additions","external":false,"refSections":[],"url":"#proposed-additions"},
+"proposed-amendments": {"dfnID":"proposed-amendments","dfnText":"proposed amendments","external":false,"refSections":[{"refs":[{"id":"ref-for-proposed-amendments"},{"id":"ref-for-proposed-amendments\u2460"},{"id":"ref-for-proposed-amendments\u2461"},{"id":"ref-for-proposed-amendments\u2462"},{"id":"ref-for-proposed-amendments\u2463"},{"id":"ref-for-proposed-amendments\u2464"},{"id":"ref-for-proposed-amendments\u2465"},{"id":"ref-for-proposed-amendments\u2466"},{"id":"ref-for-proposed-amendments\u2467"},{"id":"ref-for-proposed-amendments\u2468"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-proposed-amendments\u2460\u24ea"},{"id":"ref-for-proposed-amendments\u2460\u2460"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-proposed-amendments\u2460\u2461"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#proposed-amendments"},
+"proposed-corrections": {"dfnID":"proposed-corrections","dfnText":"proposed corrections","external":false,"refSections":[],"url":"#proposed-corrections"},
+"public-participant-ig": {"dfnID":"public-participant-ig","dfnText":"public participants","external":false,"refSections":[{"refs":[{"id":"ref-for-public-participant-ig"}],"title":"4.3. \nContent of a Charter"}],"url":"#public-participant-ig"},
+"publishing": {"dfnID":"publishing","dfnText":"Publishing","external":false,"refSections":[{"refs":[{"id":"ref-for-publishing"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-publishing\u2460"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-publishing\u2461"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-publishing\u2462"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-publishing\u2463"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-publishing\u2464"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-publishing\u2465"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-publishing\u2466"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-publishing\u2467"},{"id":"ref-for-publishing\u2468"},{"id":"ref-for-publishing\u2460\u24ea"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-publishing\u2460\u2460"},{"id":"ref-for-publishing\u2460\u2461"}],"title":"6.4.1. \nGroup Notes"}],"url":"#publishing"},
+"rec-amended": {"dfnID":"rec-amended","dfnText":"Amended Recommendation","external":false,"refSections":[],"url":"#rec-amended"},
+"registry": {"dfnID":"registry","dfnText":"registry","external":false,"refSections":[{"refs":[{"id":"ref-for-registry"},{"id":"ref-for-registry\u2460"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry\u2461"},{"id":"ref-for-registry\u2462"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry\u2463"},{"id":"ref-for-registry\u2464"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry\u2465"},{"id":"ref-for-registry\u2466"},{"id":"ref-for-registry\u2467"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry\u2468"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry"},
+"registry-change": {"dfnID":"registry-change","dfnText":"registry changes","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-change"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-change\u2460"},{"id":"ref-for-registry-change\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-change\u2462"},{"id":"ref-for-registry-change\u2463"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#registry-change"},
+"registry-data": {"dfnID":"registry-data","dfnText":"registry data","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-data"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-data\u2460"},{"id":"ref-for-registry-data\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-data"},
+"registry-data-report": {"dfnID":"registry-data-report","dfnText":"Registry Data Report","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-data-report"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-data-report\u2460"},{"id":"ref-for-registry-data-report\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-data-report"},
+"registry-definition": {"dfnID":"registry-definition","dfnText":"registry definition","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-definition"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry-definition\u2460"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry-definition\u2461"},{"id":"ref-for-registry-definition\u2462"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-definition\u2463"},{"id":"ref-for-registry-definition\u2464"},{"id":"ref-for-registry-definition\u2465"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-definition\u2466"},{"id":"ref-for-registry-definition\u2467"},{"id":"ref-for-registry-definition\u2468"},{"id":"ref-for-registry-definition\u2460\u24ea"},{"id":"ref-for-registry-definition\u2460\u2460"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-registry-definition\u2460\u2461"},{"id":"ref-for-registry-definition\u2460\u2462"},{"id":"ref-for-registry-definition\u2460\u2463"},{"id":"ref-for-registry-definition\u2460\u2464"},{"id":"ref-for-registry-definition\u2460\u2465"},{"id":"ref-for-registry-definition\u2460\u2466"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-definition"},
+"registry-draft": {"dfnID":"registry-draft","dfnText":"Registry Draft","external":false,"refSections":[],"url":"#registry-draft"},
+"registry-entry": {"dfnID":"registry-entry","dfnText":"registry entries","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-entry"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-registry-entry\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-entry\u2461"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-registry-entry\u2462"}],"title":"6.5.5. \nSpecifications that Reference Registries"}],"url":"#registry-entry"},
+"registry-report": {"dfnID":"registry-report","dfnText":"registry report","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-report"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-registry-report\u2460"},{"id":"ref-for-registry-report\u2461"},{"id":"ref-for-registry-report\u2462"},{"id":"ref-for-registry-report\u2463"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-report\u2464"}],"title":"6.5.6. \nRegistries and Patents"}],"url":"#registry-report"},
+"registry-table": {"dfnID":"registry-table","dfnText":"registry tables","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-table"},{"id":"ref-for-registry-table\u2460"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-registry-table\u2461"},{"id":"ref-for-registry-table\u2462"},{"id":"ref-for-registry-table\u2463"}],"title":"6.5. \nThe Registry Track"},{"refs":[{"id":"ref-for-registry-table\u2464"},{"id":"ref-for-registry-table\u2465"},{"id":"ref-for-registry-table\u2466"},{"id":"ref-for-registry-table\u2467"},{"id":"ref-for-registry-table\u2468"},{"id":"ref-for-registry-table\u2460\u24ea"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-registry-table\u2460\u2460"},{"id":"ref-for-registry-table\u2460\u2461"},{"id":"ref-for-registry-table\u2460\u2462"},{"id":"ref-for-registry-table\u2460\u2463"},{"id":"ref-for-registry-table\u2460\u2464"},{"id":"ref-for-registry-table\u2460\u2465"},{"id":"ref-for-registry-table\u2460\u2466"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-registry-table\u2460\u2467"},{"id":"ref-for-registry-table\u2460\u2468"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-registry-table\u2461\u24ea"},{"id":"ref-for-registry-table\u2461\u2460"},{"id":"ref-for-registry-table\u2461\u2461"}],"title":"6.5.4. \nRegistry Data Reports"}],"url":"#registry-table"},
+"registry-track": {"dfnID":"registry-track","dfnText":"Registry Track","external":false,"refSections":[{"refs":[{"id":"ref-for-registry-track"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#registry-track"},
+"rejected": {"dfnID":"rejected","dfnText":"rejected","external":false,"refSections":[{"refs":[{"id":"ref-for-rejected"}],"title":"9. \nMember Submissions"}],"url":"#rejected"},
+"related-member": {"dfnID":"related-member","dfnText":"related","external":false,"refSections":[{"refs":[{"id":"ref-for-related-member"}],"title":"2.1.2.2. \nRelated Members"},{"refs":[{"id":"ref-for-related-member\u2460"}],"title":"2.1.3. \nGood Standing"},{"refs":[{"id":"ref-for-related-member\u2461"},{"id":"ref-for-related-member\u2462"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-related-member\u2463"}],"title":"5.8. \nAdvisory Committee Votes"}],"url":"#related-member"},
+"renounce": {"dfnID":"renounce","dfnText":"renounce","external":false,"refSections":[{"refs":[{"id":"ref-for-renounce"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-renounce\u2460"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-renounce\u2461"},{"id":"ref-for-renounce\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-renounce\u2463"}],"title":"5.6.2.8. \nCouncil Decision Report"}],"url":"#renounce"},
+"rescinded-candidate-recommendation": {"dfnID":"rescinded-candidate-recommendation","dfnText":"Rescinded Candidate Recommendation","external":false,"refSections":[{"refs":[{"id":"ref-for-rescinded-candidate-recommendation"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-rescinded-candidate-recommendation\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#rescinded-candidate-recommendation"},
+"reviewform": {"dfnID":"reviewform","dfnText":"Call for Review","external":false,"refSections":[{"refs":[{"id":"ref-for-reviewform"},{"id":"ref-for-reviewform\u2460"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-reviewform\u2461"}],"title":"6.3.9.1. \nRequirements for Transition"}],"url":"#reviewform"},
+"statement": {"dfnID":"statement","dfnText":"W3C Statement","external":false,"refSections":[{"refs":[{"id":"ref-for-statement"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-statement\u2460"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-statement\u2461"},{"id":"ref-for-statement\u2462"},{"id":"ref-for-statement\u2463"},{"id":"ref-for-statement\u2464"},{"id":"ref-for-statement\u2465"},{"id":"ref-for-statement\u2466"},{"id":"ref-for-statement\u2467"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-statement\u2468"},{"id":"ref-for-statement\u2460\u24ea"},{"id":"ref-for-statement\u2460\u2460"},{"id":"ref-for-statement\u2460\u2461"}],"title":"6.4.4. \nRevising W3C Statements"},{"refs":[{"id":"ref-for-statement\u2460\u2462"}],"title":"6.6. \nSwitching Tracks"}],"url":"#statement"},
+"submission-appeals": {"dfnID":"submission-appeals","dfnText":"Submission Appeals","external":false,"refSections":[{"refs":[{"id":"ref-for-submission-appeals"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-submission-appeals\u2460"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-submission-appeals\u2461"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-submission-appeals\u2462"},{"id":"ref-for-submission-appeals\u2463"}],"title":"9. \nMember Submissions"}],"url":"#submission-appeals"},
+"submitter": {"dfnID":"submitter","dfnText":"Submitter(s)","external":false,"refSections":[{"refs":[{"id":"ref-for-submitter"},{"id":"ref-for-submitter\u2460"},{"id":"ref-for-submitter\u2461"},{"id":"ref-for-submitter\u2462"},{"id":"ref-for-submitter\u2463"},{"id":"ref-for-submitter\u2464"},{"id":"ref-for-submitter\u2465"},{"id":"ref-for-submitter\u2466"}],"title":"9. \nMember Submissions"}],"url":"#submitter"},
+"subsidiary": {"dfnID":"subsidiary","dfnText":"subsidiary","external":false,"refSections":[{"refs":[{"id":"ref-for-subsidiary"},{"id":"ref-for-subsidiary\u2460"}],"title":"2.1.2.2. \nRelated Members"}],"url":"#subsidiary"},
+"substantive-change": {"dfnID":"substantive-change","dfnText":"substantive changes","external":false,"refSections":[{"refs":[{"id":"ref-for-substantive-change"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-substantive-change\u2460"},{"id":"ref-for-substantive-change\u2461"},{"id":"ref-for-substantive-change\u2462"},{"id":"ref-for-substantive-change\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-substantive-change\u2464"}],"title":"6.2.2. \nReviews and Review Responsibilities"},{"refs":[{"id":"ref-for-substantive-change\u2465"},{"id":"ref-for-substantive-change\u2466"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-substantive-change\u2467"}],"title":"6.3.6. \nRevising a Working Draft"},{"refs":[{"id":"ref-for-substantive-change\u2468"},{"id":"ref-for-substantive-change\u2460\u24ea"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2460"},{"id":"ref-for-substantive-change\u2460\u2461"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2462"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-substantive-change\u2460\u2463"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"}],"url":"#substantive-change"},
+"superseded-registry": {"dfnID":"superseded-registry","dfnText":"Superseded Registry","external":false,"refSections":[],"url":"#superseded-registry"},
+"supplemental-confidential-council-report": {"dfnID":"supplemental-confidential-council-report","dfnText":"Supplemental Confidential Council Report","external":false,"refSections":[],"url":"#supplemental-confidential-council-report"},
+"team": {"dfnID":"team","dfnText":"Team","external":false,"refSections":[{"refs":[{"id":"ref-for-team"},{"id":"ref-for-team\u2460"},{"id":"ref-for-team\u2461"}],"title":"1. \nIntroduction"},{"refs":[{"id":"ref-for-team\u2462"},{"id":"ref-for-team\u2463"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-team\u2464"},{"id":"ref-for-team\u2465"},{"id":"ref-for-team\u2466"}],"title":"3.1.1.2. \nConflict of Interest Policy"},{"refs":[{"id":"ref-for-team\u2467"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-team\u2468"},{"id":"ref-for-team\u2460\u24ea"}],"title":"3.1.4. \nResignation from a Group"},{"refs":[{"id":"ref-for-team\u2460\u2460"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-team\u2460\u2461"},{"id":"ref-for-team\u2460\u2462"},{"id":"ref-for-team\u2460\u2463"}],"title":"3.2.3. \nAdvisory Committee Mailing Lists"},{"refs":[{"id":"ref-for-team\u2460\u2464"},{"id":"ref-for-team\u2460\u2465"},{"id":"ref-for-team\u2460\u2466"}],"title":"3.2.4. \nAdvisory Committee Meetings"},{"refs":[{"id":"ref-for-team\u2460\u2467"}],"title":"3.3.1.2. \nComposition of the Advisory Board"},{"refs":[{"id":"ref-for-team\u2460\u2468"}],"title":"3.3.1.3. \nCommunications of the Advisory Board"},{"refs":[{"id":"ref-for-team\u2461\u24ea"},{"id":"ref-for-team\u2461\u2460"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-team\u2461\u2461"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-team\u2461\u2462"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-team\u2461\u2463"},{"id":"ref-for-team\u2461\u2464"},{"id":"ref-for-team\u2461\u2465"},{"id":"ref-for-team\u2461\u2466"},{"id":"ref-for-team\u2461\u2467"},{"id":"ref-for-team\u2461\u2468"},{"id":"ref-for-team\u2462\u24ea"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-team\u2462\u2460"},{"id":"ref-for-team\u2462\u2461"},{"id":"ref-for-team\u2462\u2462"},{"id":"ref-for-team\u2462\u2463"},{"id":"ref-for-team\u2462\u2464"},{"id":"ref-for-team\u2462\u2465"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-team\u2462\u2466"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-team\u2462\u2467"},{"id":"ref-for-team\u2462\u2468"},{"id":"ref-for-team\u2463\u24ea"}],"title":"3.4.1. \nRequirements for All Chartered Groups"},{"refs":[{"id":"ref-for-team\u2463\u2460"},{"id":"ref-for-team\u2463\u2461"},{"id":"ref-for-team\u2463\u2462"},{"id":"ref-for-team\u2463\u2463"},{"id":"ref-for-team\u2463\u2464"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-team\u2463\u2465"},{"id":"ref-for-team\u2463\u2466"},{"id":"ref-for-team\u2463\u2467"},{"id":"ref-for-team\u2463\u2468"},{"id":"ref-for-team\u2464\u24ea"},{"id":"ref-for-team\u2464\u2460"},{"id":"ref-for-team\u2464\u2461"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-team\u2464\u2462"}],"title":"4.4.1. \nNew Charters and Major Changes"},{"refs":[{"id":"ref-for-team\u2464\u2463"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-team\u2464\u2464"}],"title":"4.5. \nCall for Participation in a Chartered Group"},{"refs":[{"id":"ref-for-team\u2464\u2465"},{"id":"ref-for-team\u2464\u2466"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-team\u2464\u2467"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-team\u2464\u2468"},{"id":"ref-for-team\u2465\u24ea"}],"title":"5.1. \nTypes of Decisions"},{"refs":[{"id":"ref-for-team\u2465\u2460"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-team\u2465\u2461"},{"id":"ref-for-team\u2465\u2462"},{"id":"ref-for-team\u2465\u2463"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-team\u2465\u2464"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-team\u2465\u2465"},{"id":"ref-for-team\u2465\u2466"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-team\u2465\u2467"},{"id":"ref-for-team\u2465\u2468"},{"id":"ref-for-team\u2466\u24ea"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-team\u2466\u2460"},{"id":"ref-for-team\u2466\u2461"},{"id":"ref-for-team\u2466\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-team\u2466\u2463"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-team\u2466\u2464"},{"id":"ref-for-team\u2466\u2465"},{"id":"ref-for-team\u2466\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-team\u2466\u2467"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-team\u2466\u2468"},{"id":"ref-for-team\u2467\u24ea"}],"title":"5.7.1. \nInitiating an Advisory Committee Review"},{"refs":[{"id":"ref-for-team\u2467\u2460"},{"id":"ref-for-team\u2467\u2461"},{"id":"ref-for-team\u2467\u2462"},{"id":"ref-for-team\u2467\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-team\u2467\u2464"},{"id":"ref-for-team\u2467\u2465"},{"id":"ref-for-team\u2467\u2466"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-team\u2467\u2467"}],"title":"6.2.2.1. \nWide Review"},{"refs":[{"id":"ref-for-team\u2467\u2468"},{"id":"ref-for-team\u2468\u24ea"},{"id":"ref-for-team\u2468\u2460"},{"id":"ref-for-team\u2468\u2461"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-team\u2468\u2462"}],"title":"6.2.7. \nLicense Grants from Non-Participants"},{"refs":[{"id":"ref-for-team\u2468\u2463"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-team\u2468\u2464"}],"title":"6.3.2. \nImplementation Experience"},{"refs":[{"id":"ref-for-team\u2468\u2465"},{"id":"ref-for-team\u2468\u2466"},{"id":"ref-for-team\u2468\u2467"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2468\u2468"},{"id":"ref-for-team\u2460\u24ea\u24ea"},{"id":"ref-for-team\u2460\u24ea\u2460"},{"id":"ref-for-team\u2460\u24ea\u2461"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2462"}],"title":"6.3.5. \nPublishing a First Public Working Draft"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2463"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2464"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2465"},{"id":"ref-for-team\u2460\u24ea\u2466"},{"id":"ref-for-team\u2460\u24ea\u2467"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-team\u2460\u24ea\u2468"}],"title":"6.3.9.2. \nInitiating Review"},{"refs":[{"id":"ref-for-team\u2460\u2460\u24ea"},{"id":"ref-for-team\u2460\u2460\u2460"}],"title":"6.3.9.3. \nResolution of Review"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2461"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2462"},{"id":"ref-for-team\u2460\u2460\u2463"},{"id":"ref-for-team\u2460\u2460\u2464"},{"id":"ref-for-team\u2460\u2460\u2465"},{"id":"ref-for-team\u2460\u2460\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-team\u2460\u2460\u2467"},{"id":"ref-for-team\u2460\u2460\u2468"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-team\u2460\u2461\u24ea"},{"id":"ref-for-team\u2460\u2461\u2460"}],"title":"6.5.1. \nRegistry Definitions"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2462"},{"id":"ref-for-team\u2460\u2461\u2463"}],"title":"7.1. \nPublic Communication"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2464"}],"title":"7.2. \nConfidentiality Levels"},{"refs":[{"id":"ref-for-team\u2460\u2461\u2465"},{"id":"ref-for-team\u2460\u2461\u2466"},{"id":"ref-for-team\u2460\u2461\u2467"},{"id":"ref-for-team\u2460\u2461\u2468"}],"title":"7.3. \nChanging Confidentiality Level"},{"refs":[{"id":"ref-for-team\u2460\u2462\u24ea"},{"id":"ref-for-team\u2460\u2462\u2460"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-team\u2460\u2462\u2461"},{"id":"ref-for-team\u2460\u2462\u2462"},{"id":"ref-for-team\u2460\u2462\u2463"},{"id":"ref-for-team\u2460\u2462\u2464"},{"id":"ref-for-team\u2460\u2462\u2465"},{"id":"ref-for-team\u2460\u2462\u2466"},{"id":"ref-for-team\u2460\u2462\u2467"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-team\u2460\u2462\u2468"}],"title":"10. \nProcess Evolution"}],"url":"#team"},
+"team-contact": {"dfnID":"team-contact","dfnText":"Team Contact","external":false,"refSections":[],"url":"#team-contact"},
+"team-correction": {"dfnID":"team-correction","dfnText":"Team correction","external":false,"refSections":[{"refs":[{"id":"ref-for-team-correction"},{"id":"ref-for-team-correction\u2460"},{"id":"ref-for-team-correction\u2461"},{"id":"ref-for-team-correction\u2462"}],"title":"6.2.6. \nMaintenance Without a Group"}],"url":"#team-correction"},
+"team-decision": {"dfnID":"team-decision","dfnText":"Team Decisions","external":false,"refSections":[{"refs":[{"id":"ref-for-team-decision"}],"title":"2.2. \nThe W3C Team"},{"refs":[{"id":"ref-for-team-decision\u2460"},{"id":"ref-for-team-decision\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-team-decision\u2462"},{"id":"ref-for-team-decision\u2463"},{"id":"ref-for-team-decision\u2464"},{"id":"ref-for-team-decision\u2465"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-team-decision\u2466"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-team-decision\u2467"}],"title":"4.6. \nCharter Extension"},{"refs":[{"id":"ref-for-team-decision\u2468"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-team-decision\u2460\u24ea"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-team-decision\u2460\u2460"}],"title":"6.3.9.1. \nRequirements for Transition"},{"refs":[{"id":"ref-for-team-decision\u2460\u2461"}],"title":"8. \nLiaisons"}],"url":"#team-decision"},
+"team-representative-in-a-working-group": {"dfnID":"team-representative-in-a-working-group","dfnText":"Team representative in a Working Group","external":false,"refSections":[],"url":"#team-representative-in-a-working-group"},
+"team-representative-in-an-interest-group": {"dfnID":"team-representative-in-an-interest-group","dfnText":"Team representative in an Interest Group","external":false,"refSections":[],"url":"#team-representative-in-an-interest-group"},
+"technical-agreement": {"dfnID":"technical-agreement","dfnText":"technical agreement","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-agreement"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-technical-agreement\u2460"},{"id":"ref-for-technical-agreement\u2461"},{"id":"ref-for-technical-agreement\u2462"},{"id":"ref-for-technical-agreement\u2463"},{"id":"ref-for-technical-agreement\u2464"},{"id":"ref-for-technical-agreement\u2465"},{"id":"ref-for-technical-agreement\u2466"},{"id":"ref-for-technical-agreement\u2467"},{"id":"ref-for-technical-agreement\u2468"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-technical-agreement\u2460\u24ea"}],"title":"\nAppendix A: Retired Terminology"}],"url":"#technical-agreement"},
+"technical-architecture-group": {"dfnID":"technical-architecture-group","dfnText":"TAG","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-architecture-group"}],"title":"3.1.1.1. \nExpectations and Discipline"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460"}],"title":"3.3. \nElected Groups: The AB and the TAG"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461"},{"id":"ref-for-technical-architecture-group\u2462"},{"id":"ref-for-technical-architecture-group\u2463"},{"id":"ref-for-technical-architecture-group\u2464"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2465"},{"id":"ref-for-technical-architecture-group\u2466"}],"title":"3.3.2.2. \nComposition of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2467"},{"id":"ref-for-technical-architecture-group\u2468"},{"id":"ref-for-technical-architecture-group\u2460\u24ea"},{"id":"ref-for-technical-architecture-group\u2460\u2460"}],"title":"3.3.2.3. \nCommunications of the Technical Architecture Group"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2461"}],"title":"3.3.3.1. \nExpectations for Elected Groups Participants"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2462"}],"title":"3.3.3.2. \nElected Groups Participation Constraints"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2463"},{"id":"ref-for-technical-architecture-group\u2460\u2464"}],"title":"3.3.3.3. \nAdvisory Board and Technical Architecture Group Elections"},{"refs":[{"id":"ref-for-technical-architecture-group\u2460\u2465"},{"id":"ref-for-technical-architecture-group\u2460\u2466"},{"id":"ref-for-technical-architecture-group\u2460\u2467"},{"id":"ref-for-technical-architecture-group\u2460\u2468"},{"id":"ref-for-technical-architecture-group\u2461\u24ea"},{"id":"ref-for-technical-architecture-group\u2461\u2460"}],"title":"3.3.3.4. \nTechnical Architecture Group Appointments"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2461"}],"title":"3.3.3.5. \nVerifiable Random Selection Procedure"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2462"},{"id":"ref-for-technical-architecture-group\u2461\u2463"},{"id":"ref-for-technical-architecture-group\u2461\u2464"},{"id":"ref-for-technical-architecture-group\u2461\u2465"}],"title":"3.3.3.6. \nElected Groups Vacated Seats"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2466"},{"id":"ref-for-technical-architecture-group\u2461\u2467"}],"title":"4.7. \nChartered Group Closure"},{"refs":[{"id":"ref-for-technical-architecture-group\u2461\u2468"}],"title":"5.6.2. \nW3C Council"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u24ea"},{"id":"ref-for-technical-architecture-group\u2462\u2460"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2461"},{"id":"ref-for-technical-architecture-group\u2462\u2462"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2463"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2465"},{"id":"ref-for-technical-architecture-group\u2462\u2466"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2467"}],"title":"6.4.1. \nGroup Notes"},{"refs":[{"id":"ref-for-technical-architecture-group\u2462\u2468"}],"title":"9. \nMember Submissions"}],"url":"#technical-architecture-group"},
+"technical-report": {"dfnID":"technical-report","dfnText":"Technical Report","external":false,"refSections":[{"refs":[{"id":"ref-for-technical-report"}],"title":"4.3. \nContent of a Charter"},{"refs":[{"id":"ref-for-technical-report\u2460"},{"id":"ref-for-technical-report\u2461"}],"title":"5.5. \nRegistering Formal Objections"},{"refs":[{"id":"ref-for-technical-report\u2462"}],"title":"5.7. \nAdvisory Committee Reviews and W3C Decisions"},{"refs":[{"id":"ref-for-technical-report\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-technical-report\u2464"},{"id":"ref-for-technical-report\u2465"},{"id":"ref-for-technical-report\u2466"}],"title":"6.2.1. \nPublication of Technical Reports"},{"refs":[{"id":"ref-for-technical-report\u2467"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-technical-report\u2468"},{"id":"ref-for-technical-report\u2460\u24ea"},{"id":"ref-for-technical-report\u2460\u2460"},{"id":"ref-for-technical-report\u2460\u2461"},{"id":"ref-for-technical-report\u2460\u2462"}],"title":"6.2.4. \nErrata Management"},{"refs":[{"id":"ref-for-technical-report\u2460\u2463"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-technical-report\u2460\u2464"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2460\u2465"},{"id":"ref-for-technical-report\u2460\u2466"},{"id":"ref-for-technical-report\u2460\u2467"},{"id":"ref-for-technical-report\u2460\u2468"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2461\u24ea"},{"id":"ref-for-technical-report\u2461\u2460"},{"id":"ref-for-technical-report\u2461\u2461"},{"id":"ref-for-technical-report\u2461\u2462"}],"title":"6.3.10.3. \nRevising a Recommendation: New Features"},{"refs":[{"id":"ref-for-technical-report\u2461\u2463"},{"id":"ref-for-technical-report\u2461\u2464"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-technical-report\u2461\u2465"},{"id":"ref-for-technical-report\u2461\u2466"},{"id":"ref-for-technical-report\u2461\u2467"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-technical-report\u2461\u2468"}],"title":"6.4.2. \nPublishing Notes"},{"refs":[{"id":"ref-for-technical-report\u2462\u24ea"},{"id":"ref-for-technical-report\u2462\u2460"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-technical-report\u2462\u2461"},{"id":"ref-for-technical-report\u2462\u2462"}],"title":"6.5.3. \nUpdating Registry Tables"},{"refs":[{"id":"ref-for-technical-report\u2462\u2463"},{"id":"ref-for-technical-report\u2462\u2464"},{"id":"ref-for-technical-report\u2462\u2465"},{"id":"ref-for-technical-report\u2462\u2466"}],"title":"6.5.4. \nRegistry Data Reports"},{"refs":[{"id":"ref-for-technical-report\u2462\u2467"},{"id":"ref-for-technical-report\u2462\u2468"},{"id":"ref-for-technical-report\u2463\u24ea"},{"id":"ref-for-technical-report\u2463\u2460"}],"title":"6.6. \nSwitching Tracks"},{"refs":[{"id":"ref-for-technical-report\u2463\u2461"}],"title":"9. \nMember Submissions"},{"refs":[{"id":"ref-for-technical-report\u2463\u2462"}],"title":"10. \nProcess Evolution"}],"url":"#technical-report"},
+"trans-req": {"dfnID":"trans-req","dfnText":"Transition Requests","external":false,"refSections":[{"refs":[{"id":"ref-for-trans-req"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2460"},{"id":"ref-for-trans-req\u2461"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2462"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-trans-req\u2463"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"}],"url":"#trans-req"},
+"update-requests": {"dfnID":"update-requests","dfnText":"Update Requests","external":false,"refSections":[{"refs":[{"id":"ref-for-update-requests"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-update-requests\u2460"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-update-requests\u2461"},{"id":"ref-for-update-requests\u2462"},{"id":"ref-for-update-requests\u2463"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"},{"refs":[{"id":"ref-for-update-requests\u2464"}],"title":"6.3.7. \nTransitioning to Candidate Recommendation"},{"refs":[{"id":"ref-for-update-requests\u2465"},{"id":"ref-for-update-requests\u2466"}],"title":"6.3.8.1. \nPublishing a Candidate Recommendation Snapshot"},{"refs":[{"id":"ref-for-update-requests\u2467"}],"title":"6.3.8.2. \nPublishing a Candidate Recommendation Draft"},{"refs":[{"id":"ref-for-update-requests\u2468"}],"title":"6.3.10.2. \nRevising a Recommendation: Substantive Changes"},{"refs":[{"id":"ref-for-update-requests\u2460\u24ea"}],"title":"6.3.10.4. \nIncorporating Candidate Amendments"},{"refs":[{"id":"ref-for-update-requests\u2460\u2460"}],"title":"6.5.3. \nUpdating Registry Tables"}],"url":"#update-requests"},
+"upheld": {"dfnID":"upheld","dfnText":"upheld","external":false,"refSections":[{"refs":[{"id":"ref-for-upheld"},{"id":"ref-for-upheld\u2460"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-upheld\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-upheld\u2462"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-upheld\u2463"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-upheld\u2464"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#upheld"},
+"w3c-council": {"dfnID":"w3c-council","dfnText":"W3C Council","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-council"},{"id":"ref-for-w3c-council\u2460"}],"title":"3.3.1.1. \nRole of the Advisory Board"},{"refs":[{"id":"ref-for-w3c-council\u2461"}],"title":"3.3.2.1. \nRole of the Technical Architecture Group"},{"refs":[{"id":"ref-for-w3c-council\u2462"}],"title":"4.2. \nCharter Refinement"},{"refs":[{"id":"ref-for-w3c-council\u2463"},{"id":"ref-for-w3c-council\u2464"}],"title":"5.6.1. \nInvestigation and Mediation by the Team"},{"refs":[{"id":"ref-for-w3c-council\u2465"},{"id":"ref-for-w3c-council\u2466"},{"id":"ref-for-w3c-council\u2467"},{"id":"ref-for-w3c-council\u2468"},{"id":"ref-for-w3c-council\u2460\u24ea"},{"id":"ref-for-w3c-council\u2460\u2460"},{"id":"ref-for-w3c-council\u2460\u2461"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2462"}],"title":"5.6.2.2. \nExtraordinary Delegation"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2463"},{"id":"ref-for-w3c-council\u2460\u2464"},{"id":"ref-for-w3c-council\u2460\u2465"}],"title":"5.6.2.3. \nCouncil Participation, Dismissal, and Renunciation"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2466"}],"title":"5.6.2.5. \nCouncil Chairing"},{"refs":[{"id":"ref-for-w3c-council\u2460\u2467"},{"id":"ref-for-w3c-council\u2460\u2468"},{"id":"ref-for-w3c-council\u2461\u24ea"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-w3c-council\u2461\u2460"},{"id":"ref-for-w3c-council\u2461\u2461"},{"id":"ref-for-w3c-council\u2461\u2462"},{"id":"ref-for-w3c-council\u2461\u2463"},{"id":"ref-for-w3c-council\u2461\u2464"},{"id":"ref-for-w3c-council\u2461\u2465"},{"id":"ref-for-w3c-council\u2461\u2466"},{"id":"ref-for-w3c-council\u2461\u2467"},{"id":"ref-for-w3c-council\u2461\u2468"}],"title":"5.6.2.7. \nCouncil Deliberations"},{"refs":[{"id":"ref-for-w3c-council\u2462\u24ea"},{"id":"ref-for-w3c-council\u2462\u2460"},{"id":"ref-for-w3c-council\u2462\u2461"}],"title":"5.6.2.8. \nCouncil Decision Report"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2462"},{"id":"ref-for-w3c-council\u2462\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2464"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2465"},{"id":"ref-for-w3c-council\u2462\u2466"}],"title":"6.3.3. \nAdvancement on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-council\u2462\u2467"},{"id":"ref-for-w3c-council\u2462\u2468"}],"title":"6.3.4. \nUpdating Mature Publications on the Recommendation Track"}],"url":"#w3c-council"},
+"w3c-council-chair": {"dfnID":"w3c-council-chair","dfnText":"Chair","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-council-chair"}],"title":"5.6.2.1. \nCouncil Composition"},{"refs":[{"id":"ref-for-w3c-council-chair\u2460"}],"title":"5.6.2.4. \nShort Circuit"},{"refs":[{"id":"ref-for-w3c-council-chair\u2461"},{"id":"ref-for-w3c-council-chair\u2462"}],"title":"5.6.2.6. \nConvening the Council"},{"refs":[{"id":"ref-for-w3c-council-chair\u2463"},{"id":"ref-for-w3c-council-chair\u2464"},{"id":"ref-for-w3c-council-chair\u2465"},{"id":"ref-for-w3c-council-chair\u2466"}],"title":"5.6.2.7. \nCouncil Deliberations"}],"url":"#w3c-council-chair"},
+"w3c-group": {"dfnID":"w3c-group","dfnText":"W3C Group","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-group"}],"title":"3.1.2. \nMeetings"},{"refs":[{"id":"ref-for-w3c-group\u2460"}],"title":"3.1.3. \nTooling and Archiving for Discussions and Publications"},{"refs":[{"id":"ref-for-w3c-group\u2461"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-w3c-group\u2462"},{"id":"ref-for-w3c-group\u2463"}],"title":"5.7.2. \nDetermining the W3C Decision"}],"url":"#w3c-group"},
+"w3c-member": {"dfnID":"w3c-member","dfnText":"W3C Members","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-member"}],"title":"2.1.3. \nGood Standing"},{"refs":[{"id":"ref-for-w3c-member\u2460"}],"title":"3.2.1. \nRole of the Advisory Committee"},{"refs":[{"id":"ref-for-w3c-member\u2461"},{"id":"ref-for-w3c-member\u2462"}],"title":"4.1. \nInitiating Charter Refinement"},{"refs":[{"id":"ref-for-w3c-member\u2463"}],"title":"5.9. \nAppeal by Advisory Committee Representatives"},{"refs":[{"id":"ref-for-w3c-member\u2464"}],"title":"6.3.12.4. \nProcess for Rescinding, Obsoleting, Superseding, Restoring a Recommendation"},{"refs":[{"id":"ref-for-w3c-member\u2465"}],"title":"8. \nLiaisons"},{"refs":[{"id":"ref-for-w3c-member\u2466"}],"title":"9. \nMember Submissions"}],"url":"#w3c-member"},
+"w3c-recommendation-track": {"dfnID":"w3c-recommendation-track","dfnText":"W3C Recommendation Track","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-recommendation-track"}],"title":"4.4.2. \nMinor Changes to Active Charters"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460"},{"id":"ref-for-w3c-recommendation-track\u2461"},{"id":"ref-for-w3c-recommendation-track\u2462"}],"title":"6.1. \nTypes of Technical Reports"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2463"},{"id":"ref-for-w3c-recommendation-track\u2464"}],"title":"6.2.3. \nClasses of Changes"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2465"}],"title":"6.2.5. \nCandidate Amendments"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2466"}],"title":"6.3. \nThe W3C Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2467"}],"title":"6.3.1. \nMaturity Stages on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2468"}],"title":"6.3.11. \nRegression on the Recommendation Track"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u24ea"}],"title":"6.3.12.1. \nAbandoning an Unfinished Recommendation"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2460"}],"title":"6.4.3. \nElevating Group Notes to W3C Statement status"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2461"}],"title":"6.5.2. \nPublishing Registries"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2462"}],"title":"6.5.6. \nRegistries and Patents"},{"refs":[{"id":"ref-for-w3c-recommendation-track\u2460\u2463"},{"id":"ref-for-w3c-recommendation-track\u2460\u2464"},{"id":"ref-for-w3c-recommendation-track\u2460\u2465"}],"title":"6.6. \nSwitching Tracks"}],"url":"#w3c-recommendation-track"},
+"w3c-recommendation-track-document": {"dfnID":"w3c-recommendation-track-document","dfnText":"W3C Recommendation Track document","external":false,"refSections":[],"url":"#w3c-recommendation-track-document"},
+"w3c-registry": {"dfnID":"w3c-registry","dfnText":"W3C Registry","external":false,"refSections":[{"refs":[{"id":"ref-for-w3c-registry"}],"title":"6.2.6. \nMaintenance Without a Group"},{"refs":[{"id":"ref-for-w3c-registry\u2460"}],"title":"6.5.2. \nPublishing Registries"}],"url":"#w3c-registry"},
+"wgparticipant": {"dfnID":"wgparticipant","dfnText":"participants in a Working Group","external":false,"refSections":[{"refs":[{"id":"ref-for-wgparticipant"}],"title":"3. \nGroups and Participation"},{"refs":[{"id":"ref-for-wgparticipant"}],"title":"4.4.2. \nMinor Changes to Active Charters"}],"url":"#wgparticipant"},
+};
+
+document.addEventListener("DOMContentLoaded", ()=>{
+    genAllDfnPanels();
+
+    document.body.addEventListener("click", (e) => {
+        // If not handled already, just hide all dfn panels.
+        hideAllDfnPanels();
+    });
+});
+
+window.addEventListener("resize", () => {
+    // Pin any visible dfn panel
+    queryAll(".dfn-panel.on, .dfn-panel.activated").forEach(el=>positionDfnPanel(el));
+});
+
+function genAllDfnPanels() {
+    for(const panelData of Object.values(dfnPanelData)) {
+        const dfnID = panelData.dfnID;
+        const dfn = document.getElementById(dfnID);
+        if(!dfn) {
+            console.log(`Can't find dfn#${dfnID}.`, panelData);
+            continue;
+        }
+        dfn.panelData = panelData;
+        insertDfnPopupAction(dfn);
+    }
+}
+
+function genDfnPanel(dfn, { dfnID, url, dfnText, refSections, external }) {
+    const dfnPanel = mk.aside({
+        class: "dfn-panel on",
+        id: `infopanel-for-${dfnID}`,
+        "data-for": dfnID,
+        "aria-labelled-by":`infopaneltitle-for-${dfnID}`,
+        },
+        mk.span({id:`infopaneltitle-for-${dfnID}`, style:"display:none"},
+            `Info about the '${dfnText}' ${external?"external":""} reference.`),
+        mk.a({href:url, class:"dfn-link"}, url),
+        refSections.length == 0 ? [] :
+            mk.b({}, "Referenced in:"),
+            mk.ul({},
+                ...refSections.map(section=>
+                    mk.li({},
+                        ...section.refs.map((ref, refI)=>
+                            [
+                                mk.a({ href: `#${ref.id}` },
+                                    (refI == 0) ? section.title : `(${refI + 1})`
+                                ),
+                                " ",
+                            ]
+                        ),
+                    ),
+                ),
+            ),
+        genLinkingSyntaxes(dfn),
+    );
+
+    dfnPanel.addEventListener('click', (event) => {
+        if (event.target.nodeName == 'A') {
+            scrollToTargetAndHighlight(event);
+            pinDfnPanel(dfnPanel);
+        }
+        event.stopPropagation();
+        refocusOnTarget(event);
+    });
+    dfnPanel.addEventListener('keydown', (event) => {
+        if(event.keyCode == 27) { // Escape key
+            hideDfnPanel({dfnPanel});
+            event.stopPropagation();
+            event.preventDefault();
+        }
+    });
+
+    dfnPanel.dfn = dfn;
+    dfn.dfnPanel = dfnPanel;
+    return dfnPanel;
+}
+
+
+
+function hideAllDfnPanels() {
+    // Delete the currently-active dfn panel.
+    queryAll(".dfn-panel").forEach(dfnPanel=>hideDfnPanel({dfnPanel}));
+}
+
+function showDfnPanel(dfn) {
+    hideAllDfnPanels(); // Only display one at a time.
+
+    dfn.setAttribute("aria-expanded", "true");
+
+    const dfnPanel = genDfnPanel(dfn, dfn.panelData);
+
+    // Give the dfn a unique tabindex, and then
+    // give all the tabbable panel bits successive indexes.
+    let tabIndex = 100;
+    dfn.tabIndex = tabIndex++;
+    const tabbable = dfnPanel.querySelectorAll(":is(a, button)");
+    for (const el of tabbable) {
+        el.tabIndex = tabIndex++;
+    }
+
+    append(document.body, dfnPanel);
+    positionDfnPanel(dfnPanel);
+}
+
+function positionDfnPanel(dfnPanel) {
+    const dfn = dfnPanel.dfn;
+    const dfnPos = getBounds(dfn);
+    dfnPanel.style.top = dfnPos.bottom + "px";
+    dfnPanel.style.left = dfnPos.left + "px";
+
+    const panelPos = dfnPanel.getBoundingClientRect();
+    const panelMargin = 8;
+    const maxRight = document.body.parentNode.clientWidth - panelMargin;
+    if (panelPos.right > maxRight) {
+        const overflowAmount = panelPos.right - maxRight;
+        const newLeft = Math.max(panelMargin, dfnPos.left - overflowAmount);
+        dfnPanel.style.left = newLeft + "px";
+    }
+}
+
+function pinDfnPanel(dfnPanel) {
+    // Switch it to "activated" state, which pins it.
+    dfnPanel.classList.add("activated");
+    dfnPanel.style.position = "fixed";
+    dfnPanel.style.left = null;
+    dfnPanel.style.top = null;
+}
+
+function hideDfnPanel({dfn, dfnPanel}) {
+    if(!dfnPanel) dfnPanel = dfn.dfnPanel;
+    if(!dfn) dfn = dfnPanel.dfn;
+    dfn.dfnPanel = undefined;
+    dfnPanel.dfn = undefined;
+    dfn.setAttribute("aria-expanded", "false");
+    dfn.tabIndex = undefined;
+    dfnPanel.remove()
+}
+
+function toggleDfnPanel(dfn) {
+    if(dfn.dfnPanel) {
+        hideDfnPanel(dfn);
+    } else {
+        showDfnPanel(dfn);
+    }
+}
+
+function insertDfnPopupAction(dfn) {
+    dfn.setAttribute('role', 'button');
+    dfn.setAttribute('aria-expanded', 'false')
+    dfn.tabIndex = 0;
+    dfn.classList.add('has-dfn-panel');
+    dfn.addEventListener('click', (event) => {
+        toggleDfnPanel(dfn);
+        event.stopPropagation();
+    });
+    dfn.addEventListener('keypress', (event) => {
+        const kc = event.keyCode;
+        // 32->Space, 13->Enter
+        if(kc == 32 || kc == 13) {
+            toggleDfnPanel(dfn);
+            event.stopPropagation();
+            event.preventDefault();
+        }
+    });
+}
+
+function refocusOnTarget(event) {
+    const target = event.target;
+    setTimeout(() => {
+        // Refocus on the event.target element.
+        // This is needed after browser scrolls to the destination.
+        target.focus();
+    });
+}
+
+// TODO: shared util
+// Returns the root-level absolute position {left and top} of element.
+function getBounds(el, relativeTo=document.body) {
+    const relativeRect = relativeTo.getBoundingClientRect();
+    const elRect = el.getBoundingClientRect();
+    const top = elRect.top - relativeRect.top;
+    const left = elRect.left - relativeRect.left;
+    return {
+        top,
+        left,
+        bottom: top + elRect.height,
+        right: left + elRect.width,
+    }
+}
+
+function scrollToTargetAndHighlight(event) {
+    let hash = event.target.hash;
+    if (hash) {
+        hash = decodeURIComponent(hash.substring(1));
+        const dest = document.getElementById(hash);
+        if (dest) {
+            dest.classList.add('highlighted');
+            setTimeout(() => dest.classList.remove('highlighted'), 1000);
+        }
+    }
+}
+
+// Functions, divided by link type, that wrap an autolink's
+// contents with the appropriate outer syntax.
+// Alternately, a string naming another type they format
+// the same as.
+function needsFor(type) {
+    switch(type) {
+        case "descriptor":
+        case "value":
+        case "element-attr":
+        case "attr-value":
+        case "element-state":
+        case "method":
+        case "constructor":
+        case "argument":
+        case "attribute":
+        case "const":
+        case "dict-member":
+        case "event":
+        case "enum-value":
+        case "stringifier":
+        case "serializer":
+        case "iterator":
+        case "maplike":
+        case "setlike":
+        case "state":
+        case "mode":
+        case "context":
+        case "facet": return true;
+
+        default: return false;
+    }
+}
+function refusesFor(type) {
+    switch(type) {
+        case "property":
+        case "element":
+        case "interface":
+        case "namespace":
+        case "callback":
+        case "dictionary":
+        case "enum":
+        case "exception":
+        case "typedef":
+        case "http-header":
+        case "permission": return true;
+
+        default: return false;
+    }
+}
+function linkFormatterFromType(type) {
+    switch(type) {
+        case 'scheme':
+        case 'permission':
+        case 'dfn': return (text) => `[=${text}=]`;
+
+        case 'abstract-op': return (text) => `[\$${text}\$]`;
+
+        case 'function':
+        case 'at-rule':
+        case 'selector':
+        case 'value': return (text) => `''${text}''`;
+
+        case 'http-header': return (text) => `[:${text}:]`;
+
+        case 'interface':
+        case 'constructor':
+        case 'method':
+        case 'argument':
+        case 'attribute':
+        case 'callback':
+        case 'dictionary':
+        case 'dict-member':
+        case 'enum':
+        case 'enum-value':
+        case 'exception':
+        case 'const':
+        case 'typedef':
+        case 'stringifier':
+        case 'serializer':
+        case 'iterator':
+        case 'maplike':
+        case 'setlike':
+        case 'extended-attribute':
+        case 'event':
+        case 'idl': return (text) => `{{${text}}}`;
+
+        case 'element-state':
+        case 'element-attr':
+        case 'attr-value':
+        case 'element': return (element) => `<{${element}}>`;
+
+        case 'grammar': return (text) => `${text} (within a <pre class=prod>)`;
+
+        case 'type': return (text)=> `<<${text}>>`;
+
+        case 'descriptor':
+        case 'property': return (text) => `'${text}'`;
+
+        default: return;
+    };
+};
+
+function genLinkingSyntaxes(dfn) {
+    if(dfn.tagName != "DFN") return;
+
+    const type = dfn.getAttribute('data-dfn-type');
+    if(!type) {
+        console.log(`<dfn> doesn't have a data-dfn-type:`, dfn);
+        return [];
+    }
+
+    // Return a function that wraps link text based on the type
+    const linkFormatter = linkFormatterFromType(type);
+    if(!linkFormatter) {
+        console.log(`<dfn> has an unknown data-dfn-type:`, dfn);
+        return [];
+    }
+
+    let ltAlts;
+    if(dfn.hasAttribute('data-lt')) {
+        ltAlts = dfn.getAttribute('data-lt')
+            .split("|")
+            .map(x=>x.trim());
+    } else {
+        ltAlts = [dfn.textContent.trim()];
+    }
+    if(type == "type") {
+        // lt of "<foo>", but "foo" is the interior;
+        // <<foo/bar>> is how you write it with a for,
+        // not <foo/<bar>> or whatever.
+        for(var i = 0; i < ltAlts.length; i++) {
+            const lt = ltAlts[i];
+            const match = /<(.*)>/.exec(lt);
+            if(match) { ltAlts[i] = match[1]; }
+        }
+    }
+
+    let forAlts;
+    if(dfn.hasAttribute('data-dfn-for')) {
+        forAlts = dfn.getAttribute('data-dfn-for')
+            .split(",")
+            .map(x=>x.trim());
+    } else {
+        forAlts = [''];
+    }
+
+    let linkingSyntaxes = [];
+    if(!needsFor(type)) {
+        for(const lt of ltAlts) {
+            linkingSyntaxes.push(linkFormatter(lt));
+        }
+    }
+    if(!refusesFor(type)) {
+        for(const f of forAlts) {
+            linkingSyntaxes.push(linkFormatter(`${f}/${ltAlts[0]}`))
+        }
+    }
+    return [
+        mk.b({}, 'Possible linking syntaxes:'),
+        mk.ul({},
+            ...linkingSyntaxes.map(link => {
+                const copyLink = async () =>
+                    await navigator.clipboard.writeText(link);
+                return mk.li({},
+                    mk.div({ class: 'link-item' },
+                        mk.button({
+                            class: 'copy-icon', title: 'Copy',
+                            type: 'button',
+                            _onclick: copyLink,
+                            tabindex: 0,
+                        }, mk.span({ class: 'icon' }) ),
+                        mk.span({}, link)
+                    )
+                );
+            })
+        )
+    ];
+}
+}
+</script>
+<script>/* Boilerplate: script-ref-hints */
+"use strict";
+{
+let refsData = {
+"#EventsW": {"displayText":"workshop","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"workshop","type":"dfn","url":"#EventsW"},
+"#FormalObjection": {"displayText":"formal objection","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"formal objection","type":"dfn","url":"#FormalObjection"},
+"#GeneralChairs": {"displayText":"chair","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chair","type":"dfn","url":"#GeneralChairs"},
+"#GroupsIG": {"displayText":"interest groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"interest groups","type":"dfn","url":"#GroupsIG"},
+"#GroupsWG": {"displayText":"working groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"working groups","type":"dfn","url":"#GroupsWG"},
+"#Member-only": {"displayText":"member-only","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member-only","type":"dfn","url":"#Member-only"},
+"#MemberSubmission": {"displayText":"member submission","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member submission","type":"dfn","url":"#MemberSubmission"},
+"#RecsCR": {"displayText":"candidate recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation","type":"dfn","url":"#RecsCR"},
+"#RecsObs": {"displayText":"obsolete recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"obsolete recommendation","type":"dfn","url":"#RecsObs"},
+"#RecsSup": {"displayText":"superseded recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"superseded recommendation","type":"dfn","url":"#RecsSup"},
+"#RecsW3C": {"displayText":"w3c recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c recommendation","type":"dfn","url":"#RecsW3C"},
+"#RecsWD": {"displayText":"working draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"working draft","type":"dfn","url":"#RecsWD"},
+"#RescindedRec": {"displayText":"rescinded recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rescinded recommendation","type":"dfn","url":"#RescindedRec"},
+"#Team-only": {"displayText":"team-only","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team-only","type":"dfn","url":"#Team-only"},
+"#TeamContact": {"displayText":"staff contact","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"staff contact","type":"dfn","url":"#TeamContact"},
+"#WGNote": {"displayText":"note","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"note","type":"dfn","url":"#WGNote"},
+"#acknowledged": {"displayText":"acknowledged","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"acknowledged","type":"dfn","url":"#acknowledged"},
+"#adequate-implementation": {"displayText":"adequate implementation experience","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"adequate implementation experience","type":"dfn","url":"#adequate-implementation"},
+"#adopted-draft": {"displayText":"adopted draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"adopted draft","type":"dfn","url":"#adopted-draft"},
+"#advisory-board": {"displayText":"ab","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ab","type":"dfn","url":"#advisory-board"},
+"#advisory-committee": {"displayText":"advisory committee","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"advisory committee","type":"dfn","url":"#advisory-committee"},
+"#advisory-committee-appeal": {"displayText":"ac appeal","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ac appeal","type":"dfn","url":"#advisory-committee-appeal"},
+"#advisory-committee-representative": {"displayText":"advisory committee representative","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"advisory committee representative","type":"dfn","url":"#advisory-committee-representative"},
+"#advisory-committee-review": {"displayText":"ac review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ac review","type":"dfn","url":"#advisory-committee-review"},
+"#affirm": {"displayText":"affirm","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"affirm","type":"dfn","url":"#affirm"},
+"#allow-new-features": {"displayText":"allow new features","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"allow new features","type":"dfn","url":"#allow-new-features"},
+"#appeal-vote": {"displayText":"appeal vote","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"appeal vote","type":"dfn","url":"#appeal-vote"},
+"#at-risk": {"displayText":"at risk","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"at risk","type":"dfn","url":"#at-risk"},
+"#bod": {"displayText":"board","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"board","type":"dfn","url":"#bod"},
+"#candidate-addition": {"displayText":"candidate addition","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate addition","type":"dfn","url":"#candidate-addition"},
+"#candidate-amendment": {"displayText":"candidate amendment","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate amendment","type":"dfn","url":"#candidate-amendment"},
+"#candidate-correction": {"displayText":"candidate correction","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate correction","type":"dfn","url":"#candidate-correction"},
+"#candidate-recommendation-draft": {"displayText":"candidate recommendation draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation draft","type":"dfn","url":"#candidate-recommendation-draft"},
+"#candidate-recommendation-review-period": {"displayText":"candidate recommendation review period","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate recommendation review period","type":"dfn","url":"#candidate-recommendation-review-period"},
+"#candidate-recommendation-snapshot": {"displayText":"crs","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"crs","type":"dfn","url":"#candidate-recommendation-snapshot"},
+"#candidate-registry": {"displayText":"candidate registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"candidate registry","type":"dfn","url":"#candidate-registry"},
+"#ceo": {"displayText":"ceo","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"ceo","type":"dfn","url":"#ceo"},
+"#charter": {"displayText":"charter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter","type":"dfn","url":"#charter"},
+"#charter-draft": {"displayText":"charter draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter draft","type":"dfn","url":"#charter-draft"},
+"#charter-refinement": {"displayText":"charter refinement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter refinement","type":"dfn","url":"#charter-refinement"},
+"#charter-review-notice": {"displayText":"charter review notice","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter review notice","type":"dfn","url":"#charter-review-notice"},
+"#chartered-group": {"displayText":"chartered groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chartered groups","type":"dfn","url":"#chartered-group"},
+"#chartering-facilitator": {"displayText":"chartering facilitator","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"chartering facilitator","type":"dfn","url":"#chartering-facilitator"},
+"#convened": {"displayText":"convened","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"convened","type":"dfn","url":"#convened"},
+"#council-report": {"displayText":"council report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council report","type":"dfn","url":"#council-report"},
+"#council-staff-contact": {"displayText":"council staff contact","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council staff contact","type":"dfn","url":"#council-staff-contact"},
+"#custodian": {"displayText":"custodian","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"custodian","type":"dfn","url":"#custodian"},
+"#def-Consensus": {"displayText":"consensus","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"consensus","type":"dfn","url":"#def-Consensus"},
+"#def-Dissent": {"displayText":"dissent","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"dissent","type":"dfn","url":"#def-Dissent"},
+"#def-Unanimity": {"displayText":"unanimity","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"unanimity","type":"dfn","url":"#def-Unanimity"},
+"#def-w3c-decision": {"displayText":"w3c decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c decision","type":"dfn","url":"#def-w3c-decision"},
+"#dfn-charter-extension": {"displayText":"charter extension","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"charter extension","type":"dfn","url":"#dfn-charter-extension"},
+"#dfn-wide-review": {"displayText":"wide review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"wide review","type":"dfn","url":"#dfn-wide-review"},
+"#discontinuedREC": {"displayText":"discontinued draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"discontinued draft","type":"dfn","url":"#discontinuedREC"},
+"#dismissed": {"displayText":"dismissal","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"dismissal","type":"dfn","url":"#dismissed"},
+"#editorial-change": {"displayText":"editorial change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"editorial change","type":"dfn","url":"#editorial-change"},
+"#editors-draft": {"displayText":"editor's draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"editor's draft","type":"dfn","url":"#editors-draft"},
+"#elected-group": {"displayText":"elected groups","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"elected groups","type":"dfn","url":"#elected-group"},
+"#embedded-registry": {"displayText":"embedded registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"embedded registry","type":"dfn","url":"#embedded-registry"},
+"#erratum": {"displayText":"erratum","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"erratum","type":"dfn","url":"#erratum"},
+"#exclusion-draft": {"displayText":"exclusion draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"exclusion draft","type":"dfn","url":"#exclusion-draft"},
+"#exclusion-draft-charter": {"displayText":"exclusion draft charter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"exclusion draft charter","type":"dfn","url":"#exclusion-draft-charter"},
+"#formally-addressed": {"displayText":"formally addressed","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"formally addressed","type":"dfn","url":"#formally-addressed"},
+"#fpwd": {"displayText":"first public working draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"first public working draft","type":"dfn","url":"#fpwd"},
+"#ftf-meeting": {"displayText":"face-to-face meeting","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"face-to-face meeting","type":"dfn","url":"#ftf-meeting"},
+"#fully-addressed": {"displayText":"fully addressed","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"fully addressed","type":"dfn","url":"#fully-addressed"},
+"#good-standing": {"displayText":"good standing","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"good standing","type":"dfn","url":"#good-standing"},
+"#group-decision": {"displayText":"group decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"group decision","type":"dfn","url":"#group-decision"},
+"#invited-expert-in-a-working-group": {"displayText":"invited expert in a working group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"invited expert in a working group","type":"dfn","url":"#invited-expert-in-a-working-group"},
+"#last-call-for-review-of-proposed-additions": {"displayText":"last call for review of proposed additions","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed additions","type":"dfn","url":"#last-call-for-review-of-proposed-additions"},
+"#last-call-for-review-of-proposed-corrections": {"displayText":"last call for review of proposed corrections","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed corrections","type":"dfn","url":"#last-call-for-review-of-proposed-corrections"},
+"#last-call-for-review-of-proposed-corrections-and-additions": {"displayText":"last call for review of proposed corrections and additions","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed corrections and additions","type":"dfn","url":"#last-call-for-review-of-proposed-corrections-and-additions"},
+"#last-call-review": {"displayText":"last call for review of proposed amendments","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"last call for review of proposed amendments","type":"dfn","url":"#last-call-review"},
+"#member-association": {"displayText":"member association","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member association","type":"dfn","url":"#member-association"},
+"#member-representative-in-an-interest-group": {"displayText":"member representative in an interest group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member representative in an interest group","type":"dfn","url":"#member-representative-in-an-interest-group"},
+"#minor-changes": {"displayText":"minor changes","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minor changes","type":"dfn","url":"#minor-changes"},
+"#minority-opinion": {"displayText":"minority opinion","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minority opinion","type":"dfn","url":"#minority-opinion"},
+"#minutes": {"displayText":"minutes","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"minutes","type":"dfn","url":"#minutes"},
+"#note-draft": {"displayText":"note draft","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"note draft","type":"dfn","url":"#note-draft"},
+"#overrule": {"displayText":"overrule","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"overrule","type":"dfn","url":"#overrule"},
+"#overturn": {"displayText":"overturn","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"overturn","type":"dfn","url":"#overturn"},
+"#participant": {"displayText":"participant","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"participant","type":"dfn","url":"#participant"},
+"#patent-review-drafts": {"displayText":"patent review drafts","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"patent review drafts","type":"dfn","url":"#patent-review-drafts"},
+"#primary-affiliation": {"displayText":"primary affiliation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"primary affiliation","type":"dfn","url":"#primary-affiliation"},
+"#proposed-amendments": {"displayText":"proposed amendments","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"proposed amendments","type":"dfn","url":"#proposed-amendments"},
+"#publishing": {"displayText":"publish","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"publish","type":"dfn","url":"#publishing"},
+"#registry": {"displayText":"registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry","type":"dfn","url":"#registry"},
+"#registry-change": {"displayText":"registry change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry change","type":"dfn","url":"#registry-change"},
+"#registry-data": {"displayText":"registry data","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry data","type":"dfn","url":"#registry-data"},
+"#registry-data-report": {"displayText":"registry data report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry data report","type":"dfn","url":"#registry-data-report"},
+"#registry-definition": {"displayText":"registry definition","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry definition","type":"dfn","url":"#registry-definition"},
+"#registry-entry": {"displayText":"registry entry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry entry","type":"dfn","url":"#registry-entry"},
+"#registry-report": {"displayText":"registry report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry report","type":"dfn","url":"#registry-report"},
+"#registry-table": {"displayText":"registry table","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry table","type":"dfn","url":"#registry-table"},
+"#registry-track": {"displayText":"registry track","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"registry track","type":"dfn","url":"#registry-track"},
+"#rejected": {"displayText":"rejected","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rejected","type":"dfn","url":"#rejected"},
+"#related-member": {"displayText":"related member","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"related member","type":"dfn","url":"#related-member"},
+"#renounce": {"displayText":"renunciation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"renunciation","type":"dfn","url":"#renounce"},
+"#rescinded-candidate-recommendation": {"displayText":"rescinded candidate recommendation","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rescinded candidate recommendation","type":"dfn","url":"#rescinded-candidate-recommendation"},
+"#reviewform": {"displayText":"call for review","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"call for review","type":"dfn","url":"#reviewform"},
+"#statement": {"displayText":"w3c statement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c statement","type":"dfn","url":"#statement"},
+"#submission-appeals": {"displayText":"submission appeals","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"submission appeals","type":"dfn","url":"#submission-appeals"},
+"#submitter": {"displayText":"submitter","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"submitter","type":"dfn","url":"#submitter"},
+"#subsidiary": {"displayText":"subsidiary","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"subsidiary","type":"dfn","url":"#subsidiary"},
+"#substantive-change": {"displayText":"substantive change","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"substantive change","type":"dfn","url":"#substantive-change"},
+"#team": {"displayText":"team","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team","type":"dfn","url":"#team"},
+"#team-correction": {"displayText":"team correction","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team correction","type":"dfn","url":"#team-correction"},
+"#team-decision": {"displayText":"team decision","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"team decision","type":"dfn","url":"#team-decision"},
+"#technical-agreement": {"displayText":"technical agreement","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"technical agreement","type":"dfn","url":"#technical-agreement"},
+"#technical-architecture-group": {"displayText":"tag","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"tag","type":"dfn","url":"#technical-architecture-group"},
+"#technical-report": {"displayText":"technical report","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"technical report","type":"dfn","url":"#technical-report"},
+"#trans-req": {"displayText":"transition requests","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"transition requests","type":"dfn","url":"#trans-req"},
+"#update-requests": {"displayText":"update requests","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"update requests","type":"dfn","url":"#update-requests"},
+"#upheld": {"displayText":"upheld","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"upheld","type":"dfn","url":"#upheld"},
+"#w3c-council": {"displayText":"w3c council","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c council","type":"dfn","url":"#w3c-council"},
+"#w3c-council-chair": {"displayText":"council chair","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"council chair","type":"dfn","url":"#w3c-council-chair"},
+"#w3c-group": {"displayText":"w3c group","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c group","type":"dfn","url":"#w3c-group"},
+"#w3c-member": {"displayText":"member","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"member","type":"dfn","url":"#w3c-member"},
+"#w3c-recommendation-track": {"displayText":"rec track","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"rec track","type":"dfn","url":"#w3c-recommendation-track"},
+"#w3c-registry": {"displayText":"w3c registry","export":true,"for_":[],"level":"","normative":true,"shortname":"process","spec":"process","status":"local","text":"w3c registry","type":"dfn","url":"#w3c-registry"},
+"https://www.w3.org/policies/patent-policy/#exclusion-opportunity": {"displayText":"Exclusion Opportunity","export":false,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"exclusion opportunity","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#exclusion-opportunity"},
+"https://www.w3.org/policies/patent-policy/#patent-advisory-group": {"displayText":"Patent Advisory Group","export":true,"for_":[],"level":"1","normative":true,"shortname":"w3c-patent-policy","spec":"w3c-patent-policy","status":"current","text":"patent advisory group","type":"dfn","url":"https://www.w3.org/policies/patent-policy/#patent-advisory-group"},
+};
+
+function mkRefHint(link, ref) {
+    const linkText = link.textContent;
+    let dfnTextElements = '';
+    if (ref.displayText.toLowerCase() != linkText.toLowerCase()) {
+        // Give the original term if it's being displayed in a different way.
+        // But allow casing differences, they're insignificant.
+        dfnTextElements =
+            mk.li({},
+                mk.b({}, "Term: "),
+                mk.span({}, ref.displayText)
+            );
+    }
+    const forList = ref.for_;
+    let forListElements;
+    if(forList.length == 0) {
+        forListElements = [];
+    } else if(forList.length == 1) {
+        forListElements = mk.li({},
+            mk.b({}, "For: "),
+            mk.span({}, forList[0]),
+        );
+    } else {
+        forListElements = mk.li({},
+            mk.b({}, "For: "),
+            mk.ul({},
+                ...forList.map(forItem =>
+                    mk.li({},
+                        mk.span({}, forItem)
+                    ),
+                ),
+            ),
+        );
+    }
+    const url = ref.url;
+    const safeUrl = encodeURIComponent(url);
+    const hintPanel = mk.aside({
+        class: "ref-hint",
+        id: `ref-hint-for-${safeUrl}`,
+        "data-for": url,
+        "aria-labelled-by": `ref-hint-for-${safeUrl}`,
+    },
+        mk.ul({},
+            dfnTextElements,
+            mk.li({},
+                mk.b({}, "URL: "),
+                mk.a({ href: url, class: "ref" }, url),
+            ),
+            mk.li({},
+                mk.b({}, "Type: "),
+                mk.span({}, `${ref.type}`),
+            ),
+            mk.li({},
+                mk.b({}, "Spec: "),
+                mk.span({}, `${ref.spec ? ref.spec : ''}`),
+            ),
+            forListElements
+        ),
+    );
+    hintPanel.forLink = link;
+    setupRefHintEventListeners(link, hintPanel);
+    return hintPanel;
+}
+
+function hideAllRefHints() {
+    queryAll(".ref-hint").forEach(el=>hideRefHint(el));
+}
+
+function hideRefHint(refHint) {
+    const link = refHint.forLink;
+    link.setAttribute("aria-expanded", "false");
+    if(refHint.teardownEventListeners) {
+        refHint.teardownEventListeners();
+    }
+    refHint.remove();
+}
+
+function showRefHint(link) {
+    if(link.classList.contains("dfn-link")) return;
+    const url = link.getAttribute("href");
+    const refHintKey = link.getAttribute("data-refhint-key");
+    let key = url;
+    if(refHintKey) {
+        key = refHintKey + "_" + url;
+    }
+    const ref = refsData[key];
+    if(!ref) return;
+
+    hideAllRefHints(); // Only display one at this time.
+
+    const refHint = mkRefHint(link, ref);
+    append(document.body, refHint);
+    link.setAttribute("aria-expanded", "true");
+    positionRefHint(refHint);
+}
+
+function setupRefHintEventListeners(link, refHint) {
+    if (refHint.teardownEventListeners) return;
+    // Add event handlers to hide the refHint after the user moves away
+    // from both the link and refHint, if not hovering either within one second.
+    let timeout = null;
+    const startHidingRefHint = (event) => {
+        if (timeout) {
+            clearTimeout(timeout);
+        }
+        timeout = setTimeout(() => {
+            hideRefHint(refHint);
+        }, 1000);
+    }
+    const resetHidingRefHint = (event) => {
+        if (timeout) clearTimeout(timeout);
+        timeout = null;
+    };
+    link.addEventListener("mouseleave", startHidingRefHint);
+    link.addEventListener("mouseenter", resetHidingRefHint);
+    link.addEventListener("blur", startHidingRefHint);
+    link.addEventListener("focus", resetHidingRefHint);
+    refHint.addEventListener("mouseleave", startHidingRefHint);
+    refHint.addEventListener("mouseenter", resetHidingRefHint);
+    refHint.addEventListener("blur", startHidingRefHint);
+    refHint.addEventListener("focus", resetHidingRefHint);
+
+    refHint.teardownEventListeners = () => {
+        // remove event listeners
+        resetHidingRefHint();
+        link.removeEventListener("mouseleave", startHidingRefHint);
+        link.removeEventListener("mouseenter", resetHidingRefHint);
+        link.removeEventListener("blur", startHidingRefHint);
+        link.removeEventListener("focus", resetHidingRefHint);
+        refHint.removeEventListener("mouseleave", startHidingRefHint);
+        refHint.removeEventListener("mouseenter", resetHidingRefHint);
+        refHint.removeEventListener("blur", startHidingRefHint);
+        refHint.removeEventListener("focus", resetHidingRefHint);
+    };
+}
+
+function positionRefHint(refHint) {
+    const link = refHint.forLink;
+    const linkPos = getBounds(link);
+    refHint.style.top = linkPos.bottom + "px";
+    refHint.style.left = linkPos.left + "px";
+
+    const panelPos = refHint.getBoundingClientRect();
+    const panelMargin = 8;
+    const maxRight = document.body.parentNode.clientWidth - panelMargin;
+    if (panelPos.right > maxRight) {
+        const overflowAmount = panelPos.right - maxRight;
+        const newLeft = Math.max(panelMargin, linkPos.left - overflowAmount);
+        refHint.style.left = newLeft + "px";
+    }
+}
+
+// TODO: shared util
+// Returns the root-level absolute position {left and top} of element.
+function getBounds(el, relativeTo=document.body) {
+    const relativeRect = relativeTo.getBoundingClientRect();
+    const elRect = el.getBoundingClientRect();
+    const top = elRect.top - relativeRect.top;
+    const left = elRect.left - relativeRect.left;
+    return {
+        top,
+        left,
+        bottom: top + elRect.height,
+        right: left + elRect.width,
+    }
+}
+
+function showRefHintListener(e) {
+    // If the target isn't in a link (or is a link),
+    // just ignore it.
+    let link = e.target.closest("a");
+    if(!link) return;
+
+    // If the target is in a ref-hint panel
+    // (aka a link in the already-open one),
+    // also just ignore it.
+    if(link.closest(".ref-hint")) return;
+
+    // Otherwise, show the panel for the link.
+    showRefHint(link);
+}
+
+function hideAllHintsListener(e) {
+    // If the click is inside a ref-hint panel, ignore it.
+    if(e.target.closest(".ref-hint")) return;
+    // Otherwise, close all the current panels.
+    hideAllRefHints();
+}
+
+document.addEventListener("DOMContentLoaded", () => {
+    document.body.addEventListener("mousedown", showRefHintListener);
+    document.body.addEventListener("focus", showRefHintListener);
+
+    document.body.addEventListener("click", hideAllHintsListener);
+});
+
+window.addEventListener("resize", () => {
+    // Hide any open ref hint.
+    hideAllRefHints();
+});
+}
+</script>

From ebbdcdae9e7d31eae3925a2da1f2ef436be3253d Mon Sep 17 00:00:00 2001
From: Florian Rivoal <git@florian.rivoal.net>
Date: Wed, 23 Jul 2025 17:36:08 +0200
Subject: [PATCH 237/237] Start a new cycle of the Process

---
 index.bs | 264 +++++++------------------------------------------------
 1 file changed, 31 insertions(+), 233 deletions(-)

diff --git a/index.bs b/index.bs
index b71e146c..ab27b945 100644
--- a/index.bs
+++ b/index.bs
@@ -29,7 +29,7 @@ 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/20231103/
+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
@@ -50,7 +50,7 @@ Abstract:
 	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/20231103/">3 November 2023 Process</a>,
+	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>,
@@ -5472,42 +5472,16 @@ Appendix B: Acknowledgments</h2>
 	The editors are grateful to the following people,
 	who as interested individuals and/or with the affiliation(s) listed,
 	have contributed to this proposal for a revised Process:
-	Adam Basha,
-	Anna Weinberg (Apple)
-	Charles McCathie Nevile,
-	Chris Lilley (W3C),
-	Chris Needham (BBC),
-	Chris Wilson (Google),
-	Coralie Mercier (W3C),
-	David W. Singer (Apple),
-	Denis Ah-Kang (W3C),
-	Dominique Hazael-Massieux (W3C),
-	Ian Jacobs (W3C),
-	Jeffrey Yasskin (Google),
-	Jill Schmidt (Apple),
-	Marcos Cáceres (Apple),
-	Mark Nottingham,
-	Martin Thomson (Mozilla),
-	Michael Champion,
-	Michael Sirtori (Intel),
-	Mike Smith (W3C),
-	Nick Doty (Center for Democracy and Technology),
-	Nigel Megitt (BBC),
-	Philippe Le Hégaret (W3C),
-	Sam Sneddon (Apple),
-	Shawn Lawton Henry (W3C),
-	Tantek Çelik (Mozilla),
-	Ted Thibodeau Jr (OpenLink Software),
-	Theresa O'Connor (Apple),
-	Vivien Lacourba (W3C).
+
+	<i>pending…</i>
 
 	<!--
 		* After publication merge the list above in the one below,
 		  and start it anew
 		* the following command can be helpful to find contributors since a particular version
-		(in this example, starting from the p2023_1 tag):
+		(in this example, starting from the p2025 tag):
 
-		git log  p2023_1.. | grep -i author | sed "s/^[^:]*: //" | sed "s/ <.*>//" | sort -u
+		git log  p2025.. | grep -i author | sed "s/^[^:]*: //" | sed "s/ <.*>//" | sort -u
 	-->
 
 	The editors are sorry for forgetting any names,
@@ -5515,10 +5489,12 @@ Appendix B: Acknowledgments</h2>
 	without feeling a need to add more.
 
 	The following individuals contributed to the development of earlier versions of the Process:
+	Adam Basha,
 	Alex Russell (Google),
 	Andreas Tai (Institut fuer Rundfunktechnik),
 	Andrew Betts (Fastly),
 	Ann Bassetti (The Boeing Company),
+	Anna Weinberg (Apple)
 	Anne van Kesteren,
 	Art Barstow (Nokia, unaffiliated),
 	Bede McCall (MITRE),
@@ -5527,7 +5503,7 @@ Appendix B: Acknowledgments</h2>
 	Brian Kardell (JQuery, Igalia),
 	Carine Bournez (W3C),
 	Carl Cargill (Netscape, Sun Microsystems, Adobe),
-	Charles McCathie Nevile (ConsenSys),
+	Charles McCathie Nevile,
 	Chris Lilley (W3C),
 	Chris Needham (BBC),
 	Chris Wilson (Google),
@@ -5540,9 +5516,10 @@ Appendix B: Acknowledgments</h2>
 	Daniel Glazman (Disruptive Innovations),
 	David Baron (Mozilla),
 	David Fallside (IBM),
-	David W. Singer (Apple),
 	David Singer (IBM),
+	David W. Singer (Apple),
 	Delfí Ramírez,
+	Denis Ah-Kang (W3C),
 	Dominique Hazaël-Massieux (W3C),
 	Don Brutzman (Web3D),
 	Don Deutsch (Oracle),
@@ -5566,6 +5543,7 @@ Appendix B: Acknowledgments</h2>
 	Jean-François Abramatic (IBM, ILOG, W3C),
 	Jeff Jaffe (W3C),
 	Jeffrey Yasskin (Google),
+	Jill Schmidt (Apple),
 	Jim Bell (HP),
 	Jim Miller (W3C),
 	Joe Hall (CDT),
@@ -5582,15 +5560,19 @@ Appendix B: Acknowledgments</h2>
 	Lauren Wood (unaffiliated),
 	Léonie Watson (The Paciello Group),
 	Liam Quin (W3C),
-	Marcos Cáceres (Mozilla),
+	Marcos Cáceres,
 	Maria Courtemanche (IBM),
 	Mark Crawford (SAP),
 	Mark Nottingham,
-	Michael Champion (Microsoft),
+	Martin Thomson (Mozilla),
+	Michael Champion,
 	Michael Geldblum (Oracle),
+	Michael Sirtori (Intel),
+	Mike Smith (W3C),
 	Mike West (Google),
 	Mitch Stoltz (EFF),
 	Natasha Rooney (GSMA),
+	Nick Doty (Center for Democracy and Technology),
 	Nigel Megitt (BBC),
 	Olle Olsson (SICS),
 	Ora Lassila (Nokia),
@@ -5612,20 +5594,22 @@ Appendix B: Acknowledgments</h2>
 	Sandro Hawke (W3C),
 	Sangwhan Moon (Odd Concepts),
 	Scott Peterson (Google),
-	Shawn Lawton Henry,
+	Shawn Lawton Henry (W3C),
 	Steve Holbrook (IBM),
 	Steve Zilles (Adobe Systems)
 	Steven Pemberton (CWI),
-	TV Raman (Google),
 	Tantek Çelik (Mozilla),
 	Ted Thibodeau Jr (OpenLink Software),
 	Terence Eden (Her Majesty's Government),
+	Theresa O'Connor (Apple),
 	Thomas Reardon (Microsoft),
 	Tim Berners-Lee (W3C),
 	Tim Krauskopf (Spyglass),
 	Travis Leithead (Microsoft),
+	TV Raman (Google),
 	Virginia Fournier (Apple),
 	Virginie Galindo (Gemalto),
+	Vivien Lacourba (W3C),
 	Wayne Carr (Intel),
 	Wendy Fong (Hewlett-Packard),
 	Wendy Seltzer (W3C),
@@ -5636,211 +5620,25 @@ Appendix C: Changes</h2>
 
 	<em>This section is non-normative.</em>
 
-<h3 id=changes-2025 class=no-num>
-Changes since the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a></h3>
+<h3 id=changes-since-2025 class=no-num>
+Changes since the <a href="https://www.w3.org/policies/process/20231103/">18 August 2025 Process</a></h3>
 
-	<p>This document is based on the <a href="https://www.w3.org/policies/process/20231103/">3 November 2023 Process</a>.
-	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+2024%2F2025%22+is%3Aclosed">list of issues addressed</a>,
-	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2F">diff from Process 2023 to this latest version</a>,
+	<p>This document is based on the <a href="https://www.w3.org/policies/process/20250818/">18 August 2025 Process</a>.
+	A <a href="https://github.com/w3c/process/issues?q=milestone%3A%22Process+Next%22+is%3Aclosed">list of issues addressed</a>,
+	a <a href="https://services.w3.org/htmldiff?doc1=&amp;doc2=https%3A%2F%2Fwww.w3.org%2Fpolicies%2Fprocess%2Fdrafts%2F">diff from that version of the Process to this latest version</a>,
 	as well as
-	a <a href="https://github.com/w3c/process/compare/p2023_1...main">detailed log of all changes since then</a>
+	a <a href="https://github.com/w3c/process/compare/p2025...main">detailed log of all changes since then</a>
 	are available.
 
 	In addition to a number of editorial adjustments and minor tweaks, the following is a summary of the main differences:
 
-	<dl>
-		<dt id=changes-2025-tr>Changes to technical reports and their publication
-		<dd>
-			<ul>
-				<li>
-					<strong>
-					Retire the Proposed Recommendation phase of the Recommendation track.
-					</strong>
-					It was only used as a short-lived transition
-					during which various verifications and votes about CR were done.
-					These can be done on a CR
-					without having to republish it as a separate thing.
-					This simplifies the Process without changing the actual quality or consensus expectations.
-					(See <a href="https://github.com/w3c/process/issues/861">Issue 861</a>)
-
-				<li id="streamlined-update">
-					Retire “<a href="https://www.w3.org/policies/process/20231103/#streamlined-update">Streamlined Publication Approval</a>”.
-					This was meant to enable REC track publication with fewer/faster approval steps
-					when some stricter than usual criteria were fulfilled.
-					However, regular REC track publication have improved enough
-					that this became unnecessary,
-					and nobody was using it.
-					(See <a href="https://github.com/w3c/process/issues/856">Issue 856</a>)
-
-				<li>
-					Add a requirement to make progress on external issues for update requests
-					(See <a href="https://github.com/w3c/process/issues/781">Issue 781</a>)
-
-				<li>
-					Drop the requirement to publish every 6 months if nothing has changed.
-					(See <a href="https://github.com/w3c/process/issues/1013">Issue 1013</a>)
-
-				<li>
-					Enable Team to replace defunct registry custodians when no-one else can.
-					(See <a href="https://github.com/w3c/process/issues/699">Issue 699</a>)
-
-				<li>
-					Allow registries to be published by Interest Groups, the Advisory Board, and the TAG,
-					in addition to Working Groups.
-					(See <a href="https://github.com/w3c/process/issues/902">Issue 902</a>)
-
-				<li>
-					Rename “registry sections” to [=embedded registries=]
-					to avoid confusion over whether they can be split across multiple sections of a [=Recommendation=].
-					(See <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
-
-				<li>
-					Rename "Draft Note" into "Note Draft",
-					and "Draft Registry" into "Registry Draft"
-					to be consistent with other statuses that uses the word "Draft",
-					and to make that word stand out more.
-					(See <a href="https://github.com/w3c/process/issues/779">Issue 779</a>)
-
-				<li>
-					Clarify the definition of a Registry (see <a href="https://github.com/w3c/process/issues/800">Issue 800</a>)
-					and of Recommendation Track Documents (see <a href="https://github.com/w3c/process/pull/831">Pull Request 831</a>).
-
-				<li>
-					Consolidate and harmonize into <a href="#no-group-maintenance">one section</a>
-					the various parts of the Process
-					that described whether and how the Team can maintain technical reports
-					that no longer have a Group chartered to maintain them.
-					(See <a href="https://github.com/w3c/process/pull/860">Pull Request 860</a>)
-			</ul>
-
-		<dt id=changes-2025-charter>Changes to chartering
-		<dd>
-			<ul>
-				<li>
-					<strong>
-					Introduce a formal [=Charter Refinement=] phase prior to the [=AC Review=].
-					</strong>
-					(See <a href="https://github.com/w3c/process/issues/580">Issue 580</a>)
-
-				<li>
-					Be more specific about which types of changes to a charter must go through AC Review.
-					(See <a href="https://github.com/w3c/process/pull/1042">Pull Request 1042</a>)
-
-				<li>
-					Require Chairs to be listed in Charters.
-					(See <a href="https://github.com/w3c/process/issues/823">Issue 823</a>)
-
-				<li>
-					Reorganize and rephrase [[#CharterReview]] for readability and ease of understanding.
-					This change, while moderate in size, is purely editorial.
-					(See <a href="https://github.com/w3c/process/pull/850">Pull Request 850</a>)
-			</ul>
-
-		<dt id=changes-2025-decisions>Changes to formal decision making and escalation
-		<dd>
-			<ul>
-				<li>
-					Adjust the rules guiding initiation of Councils,
-					to make the deadline strict,
-					and to provide a fallback mechanism if they are not met.
-					(See <a href="https://github.com/w3c/process/pull/925">Pull Request 925</a>)
-
-				<li>
-					Make the Council's short-circuit a little more flexible.
-					(See <a href="https://github.com/w3c/process/issues/852">Issue 852</a>)
-
-				<li>
-					Exclude TAG/AB Members from voting on TAG/AB proposals in Councils.
-					(See <a href="https://github.com/w3c/process/issues/749">Issue 749</a>)
-
-				<li>
-					Limit the involvement of Tim Berners-Lee to the TAG proper,
-					not including the Council.
-					(See <a href="https://github.com/w3c/process/pull/792">Pull Request 792</a>)
-
-				<li>
-					Council dismissal vote counts must be reported.
-					(See <a href="https://github.com/w3c/process/issues/748">Issue 748</a>)
-
-				<li>
-					Require documentation of how Formal Objections get resolved.
-					(See <a href="https://github.com/w3c/process/issues/953">Issue 953</a>)
-
-				<li>
-					Put constraints on the timing of making Formal Objections public.
-					(See <a href="https://github.com/w3c/process/issues/735">Issue 735</a>)
-
-				<li>
-					Fine-tune the rules about
-					how changes can be incorporated into a proposal
-					following an AC Review.
-					(See <a href="https://github.com/w3c/process/issues/825">Issue 825</a>)
-
-				<li>
-					Adjust AC appeal vote threshold based on participation,
-					aligning with the thresholds and super majority requirements
-					for "Requisite Member Vote" from the W3C Bylaws.
-					(See <a href="https://github.com/w3c/process/issues/886">Issue 886</a>)
-
-				<li>
-					Let the originator of a proposal decide whether to try again
-					after addressing feedback
-					following an AC Appeal.
-					(See <a href="https://github.com/w3c/process/issues/844">Issue 844</a>)
-
-				<li>
-					Simplify provisions regarding substitute representatives and proxies.
-					(See <a href="https://github.com/w3c/process/issues/373">Issue 373</a>)
-			</ul>
-
-		<dt id=changes-other>Other changes
-		<dd>
-			<ul>
-				<li>
-					Reuse the bylaws’ notion of Good Standing,
-					and restrict TAG and AB elections
-					as well as AC Votes where a decision is made based on counting ballots
-					to Members in Good Standing.
-					(See <a href="https://github.com/w3c/process/issues/935">Issue 935</a>
-					and <a href="https://github.com/w3c/process/issues/954">Pull Request 954</a>)
-
-				<li>
-					The section on Member Submissions was significantly shortened and simplified,
-					reducing the complexity under formal Process authority,
-					and shifting much of the material to /Guide,
-					under Team authority.
-					(See <a href="https://github.com/w3c/process/issues/421">Issue 412</a>
-					and <a href="https://github.com/w3c/process/issues/936">Pull Request 936</a>)
-
-				<li>
-					Clarify how the outcome of certain ballots are determined.
-					(See <a href="https://github.com/w3c/process/issues/836">Issue 836</a>, <a href="https://github.com/w3c/process/pull/838">Issue 838</a>)
-
-				<li>
-					Stop citing the superseded TAG charter.
-					(See <a href="https://github.com/w3c/process/issues/794">Issue 794</a>)
-
-				<li>
-					Clarify amount of leeway around incomplete nominations to TAG or AB elections.
-					(See <a href="https://github.com/w3c/process/issues/464">Issue 464</a>)
-
-				<li>
-					Shift most of the non-normative discussion about Workshops to [[GUIDE]],
-					and reorganize the remaining normative requirements.
-					(See <a href="https://github.com/w3c/process/pull/876">Pull Request 876</a>)
-
-				<li>
-					The URL of this document was changed
-					from /Consortium/Process/ to /policies/process/
-					for better integration in the W3C website architecture.
-			</ul>
-
+	<i>None yet</i>
 
-<h3 id=changes-previous class=no-num oldids="changes-2023-1, changes-2023, changes-2021, changes-2020, changes-2019, changes-2018, changes-2017">
+<h3 id=changes-previous class=no-num oldids="changes-2023-1, changes-2023, changes-2021, changes-2020, changes-2019, changes-2018, changes-2017, changes-2025, changes-2025-tr, streamlined-update, changes-2025-charter, changes-2025-decisions, changes-other">
 Changes since earlier versions</h3>
 
 	Changes since earlier versions of the Process are detailed
-	in the <a href="https://www.w3.org/policies/process/20231103/#changes">changes section of the previous version</a>
+	in the <a href="https://www.w3.org/policies/process/20250818/#changes">changes section of the previous version</a>
 	of the Process.
 
 <pre class=biblio>
